Energy Delivered sensor — Fixed incorrect energy tracking in the Home Assistant Energy Dashboard. The sensor now correctly reports a session reset when the value drops to 0, ensuring accurate daily and monthly energy statistics.
Integration setup failure — Fixed NoneType can't be used in 'await' expression error that prevented new installations from completing, caused by incorrectly awaiting the Modbus client close call during connection validation in config_flow.py.
EOF
After upgrading from v0.1.x, a duplicate “ABB Terra AC Charger” device will appear in Home Assistant. The old device (with no entities) can now be deleted via Settings → Devices & Services → ABB Terra AC Modbus → old device → Delete. This is a one-time migration — future upgrades will no longer cause duplicate devices.
New Features
Orphaned device removal — Home Assistant now allows deleting old or duplicate charger devices directly from the UI.
Fallback limit restored to last known valid value — Previously, the fallback limit was always reset to a hardcoded 6A after a firmware bug triggered an invalid value. It is now restored to the last known valid value set by the user.
Fallback limit minimum set to 0A — The fallback limit slider now allows 0A as a minimum value. Setting 0A triggers a pause state on communication loss, allowing the charging session to resume automatically once communication is restored.
Charging current slider maximum is now dynamic — The maximum value of both the charging current and fallback limit sliders now reflects the user_settable_max_current register from the charger, which represents the maximum current configured in the Terra Config app.
Improvements
Full English codebase — All code comments, log messages, and docstrings have been translated to English, making the integration more accessible to the wider Home Assistant community. A Slovenian translation remains available for the UI.
Robust Modbus client close — Both __init__.py and config_flow.py now use a safe close helper that correctly handles different pymodbus versions regardless of whether close() is awaitable or not.
Stable device identifier — The charger device is now identified by the config entry ID instead of the serial number, preventing duplicate devices on future upgrades.
Hi, is it possibile to have two wallbox Connected with RS485 to the same Rs485 to eth device? (an unique integration, with slave 1 and slave 2).
Thanks for the support.
For using with this integration you must have charger WITH LCD and own IP addres. So you add IP of your charger to this APP.
Or IP TCP RS485 module. You buy Modbus with more inputs with own IP RS
input
Thanks for your answer First of all. I followed instructions written above (with DR134 adapter). It works fine but just for one wallbox even of rs485 has been Connected in both wallbox. Is it there the possibility to have both instances on home assistant with an unique adapter?
Thanks
It should be possible to add multiple chargers, but every charger must have its own IP, integration connects to. But integration “only” connects charger to home assistant. It does not manage your charging. For managing charging you must set up automations or integration.
Upgrade Notice