Skip to content
Home Assistant TestFlight
Energy

myenergi

CJNE/ha-myenergi · v0.2.0

HACSCloud polling

Home Assistant integration for MyEnergi devices

In Apple Home through HomeKit Bridge

What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.

EntityShows up asNote
switchSwitch or outlet
binary_sensorSensor (motion, contact, leak, smoke…)
sensorSensor (temperature, humidity, air quality…)
selectMode picker (as switches)

What people report

Zappi, Eddi and Libbi chargers/batteries are supported via the myenergi cloud API; update-available sensors exist only where the API exposes firmware flags.

  • Partly works2
  • Requested1
DeviceIn Home AssistantIn Apple HomeWhat they saidSource
myenergi EddiPartly works CloudFirmware sensor works; no update-available binary sensor, API lacks the field
Saved copy
Create a binary sensor for Libbi and Eddi when a new version of software is available. This sensor exists for Zappi but not for Libbi or Eddi, I think the Libbi and Eddi API supports this. This would provide consistency across the Myenergi products Describe the solution you'd like Binary sensors similar to the existing one for Zappi 'binary_sensor.myenergi_zappi_xxxxx_update_available' Describe alternatives you've considered use the firmware version senso and compare that to the version listed on the Myenergi website

Excerpt saved from GitHub on 2026-10-23.

Issue #694 · 2025-10
myenergi Zappi EV chargerPartly works CloudCharge mode select can revert at next poll after change; fix pending
Saved copy
Problem Fixes the symptom in #611. You change the Zappi charge mode in HA, the select shows the new mode, and at the next poll it reverts to the old one. Sometimes the change never takes effect at all. The mode command (`/cgi-zappi-mode-…`) is fire-and-forget. The API returns `{"status":0}` once the command is queued, and myenergi's servers pass it on to the Zappi afterwards (see the myenergi staff quote in this comment). Until the Zappi applies it, `/cgi-jstatus-*` still reports the old `zmo`. `ZappiChargeModeSelect` currently: 1. sends the command, writes the new mode locally and shows it …

Excerpt saved from GitHub on 2026-10-23.

PR #800 · 2026-10
myenergi Libbi batteryRequested CloudUpdate-available sensor requested; Libbi API has newAppAvailable flag, not planned
Saved copy
Create a binary sensor for Libbi and Eddi when a new version of software is available. This sensor exists for Zappi but not for Libbi or Eddi, I think the Libbi and Eddi API supports this. This would provide consistency across the Myenergi products Describe the solution you'd like Binary sensors similar to the existing one for Zappi 'binary_sensor.myenergi_zappi_xxxxx_update_available' Describe alternatives you've considered use the firmware version senso and compare that to the version listed on the Myenergi website

Excerpt saved from GitHub on 2026-10-23.

Issue #694 · 2025-10

Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.

How it connects

Cloud polling

Goes through the maker’s cloud, asking it for updates every so often. Needs the internet and an account.

Details

Installs (analytics)3,924 (0.55%)
GitHub stars217
Latest version0.2.0 (2026-10-16)
Set up in the UIYes
Maintainers@cjne, @g6ejd, @AJediIAm
LicenseMIT

Notable forks

Forks with stars, or with code pushed at least 90 days after the original’s last push. Useful when the original goes quiet.

ForkStarsLast pushDescription
G6EJD/ha-myenergi★ 32026-06-16Home Assistant integration for MyEnergi devices

In ReReHome

Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.

Bridges get their own settings page listing the accessories behind them.