Skip to content

Battery Mode Labels Fixed & Firmware notification fixes

Pre-release
Pre-release

Choose a tag to compare

View all tags
@smcneece smcneece released this 09 Apr 14:46
v2026.04.1
6fa3b8d

Battery Mode Labels Now Match SunStrong App

User reports confirmed the battery mode labels were wrong. The SunStrong app shows exactly three modes: Self Supply, Cost Savings, and Reserve. Based on observed behavior, the varserver TARIFF_OPTIMIZER value corresponds to SunStrong's "Reserve" mode, not a user-selectable "Tariff Optimizer" option.

Changes:

  • "Tariff Optimizer" renamed to "Reserve"
  • "Emergency Reserve" removed (BACKUP_ONLY does not appear to be a real user-facing mode)

Breaking change: If you have HA automations using option: "Tariff Optimizer" or option: "Emergency Reserve", update them to option: "Reserve".

Two New Read-Only Battery Sensors

The PVS varserver has two separate battery mode fields:

  • control_mode - the mode configured via the varserver config path
  • opMode - what the battery firmware is actually doing right now

Previously the Battery Control Mode select entity was reading opMode instead of control_mode. These may differ when the battery firmware temporarily overrides the mode at SOC limits.

Two new sensors are now visible on your battery device:

  • ESS Configured Mode: The polled control_mode value
  • ESS Operating Mode: The real-time opMode value

Watching both sensors will help confirm whether they differ and when.

Startup Log Cleanup

Transient connection failures during startup now log as WARNING instead of ERROR, reducing alarming red entries in HA logs when the PVS briefly takes a moment to accept connections at startup.

Bug Fix: False "PVS Firmware Upgraded" Notification

Some users were receiving a nightly "PVS FIRMWARE UPGRADED: x.x.x.x -> Unknown" notification even though no firmware upgrade actually occurred.

When the PVS varserver temporarily omits the firmware version from its response (which can happen during nightly operations such as cloud sync or internal service restarts), the integration was defaulting to the string "Unknown" instead of blank. The firmware change detector then saw your real version change to "Unknown" and fired the upgrade alert. Since this only happens once per night and recovers by the next poll, it repeated every night indefinitely.

Fixed. The missing value now defaults to blank so the guard that suppresses empty values works correctly.

No configuration changes required for most users. Update via HACS.

Note on mode writes: Whether HA can successfully change battery modes depends on the PVS accepting the varserver write commands. This is still being verified with users who have SunVault hardware. If clicking a mode in HA does not change anything, please report in the GitHub discussions.

Assets 2
Loading