v2.0.0 – Multi-Instance, Re-Auth, Device Registry, ENUM Sensors
What's new in v2.0.0
Multi-instance support
Multiple Jackery devices can now be integrated simultaneously. Each config entry is identified by its device serial number. Existing single-device installations are migrated automatically on first startup — entity IDs and HA history are preserved.
Re-authentication flow
If the device reports a token mismatch (MQTT type-123 / errorCode 401), Home Assistant now shows a persistent notification prompting you to re-enter the token — no need to remove and re-add the integration.
Device card: model and firmware version
The HA device card now shows the device model (DIY3 for SolarVault 3 Pro Max) and the current firmware version, extracted from incoming MQTT messages.
Human-readable ENUM status sensors
Device Status, OnGrid Status, CT Status, and Grid Meter Link now display human-readable labels (e.g. "Normal", "Connected") instead of raw integers. Translated into English, German, and French.
New sensor: Max Feed Grid Power
max_feed_grid_power (maxFeedGrid, from type-106) exposes the device-side feed-in limit for diagnostics. May differ from the writable maxOutPw setting.
Smart Plug commMode guard
MQTT switch commands to smart plugs are now blocked when the plug is in cloud-relay mode (commMode=2). Home Assistant shows a persistent notification; extra_state_attributes expose commMode, commMode_label, and mqtt_controllable for diagnostics and automations.
Bug fix: Auto Standby select state revert
Writing a new value via the Auto Standby select reverted to the old value on the next MQTT event (~10 s). Fixed by patching the coordinator cache after the write (v1.3.1 pattern).
See CHANGELOG.md for the full history.
Upgrade note: After updating via HACS, an HA restart is required (not just integration reload) to apply the entity unique ID migration and updated translation files.