nymea-plugins/everest
Simon Stürz d3bfa39aee EVerest: Update EV charger interface to use double 2026-01-07 16:11:05 +01:00
..
jsonrpc Update license text and add SPDX identifier 2025-11-17 16:36:48 +01:00
mqtt Update license text and add SPDX identifier 2025-11-17 16:36:48 +01:00
translations EVerest: Update translations 2024-12-11 10:32:04 +01:00
README.md Continue implementation of RPC module 2025-09-09 16:44:59 +02:00
everest.png Update plugin structure and distinguish between mqtt and jsonrpc 2025-06-25 15:31:27 +02:00
everest.pro Implement thing evse mapping and add init mechanism for charger things 2025-06-25 15:32:09 +02:00
integrationplugineverest.cpp Update license text and add SPDX identifier 2025-11-17 16:36:48 +01:00
integrationplugineverest.h Update license text and add SPDX identifier 2025-11-17 16:36:48 +01:00
integrationplugineverest.json EVerest: Update EV charger interface to use double 2026-01-07 16:11:05 +01:00
meta.json New plugin: Add EVerest EV charger plugin 2024-09-23 15:41:49 +02:00

README.md

nymea-plugin-everest

This nymea integration plugin allows to connect to any EVerest instance in the network or on localhost.

Using the RpcApi module

By default the integration requires the use of the RpcApi module, which provides a JSON RPC interface based on a websocket communication to the EVerest core.

Using the MQTT based API module

If required, the MQTT based API module of everest can be used.

By default the MQTT API module will not be initialized unless explictily enabled by creating following file

touch /etc/nymea/everest-mqtt

Each connector has to be added manually using the discovery. Once added, the integration creates an EV charger within nymea which makes it available to the energy manager and the overall nymea eco system.

Known issues:

  • There is currently no method available on the EVerest API module to switch phases
  • There are no additional information which could be used to identify the instance, like serialnumber, manufacturer or model
  • The action execution is not very clean implemented. There is no feedback if the execution was successfully