Skip to content

⚠️ IMPORTANT FOR BATTERY USERS - PLEASE READ

Choose a tag to compare

View all tags
@smcneece smcneece released this 12 Apr 19:00
v2026.04.3
a47e5aa

⚠️ IMPORTANT FOR BATTERY USERS - PLEASE READ

This release fixes a bug introduced in v2026.04.1. If you upgraded to v2026.04.1 or v2026.04.2, the "Reserve" battery mode option was writing the wrong value to your PVS. v2026.04.3 corrects this.

If you have automations that set battery mode to "Reserve", they will now work correctly after this update. No changes to your automation labels are needed - the "Reserve" label stays the same, it now just writes the correct value.

⚠️ STILL APPLIES FROM v2026.04.1 - ACTION REQUIRED IF YOU HAVEN'T ALREADY

If you are upgrading from v2026.03.x or earlier and have battery automations, you must update them:

Old label -> New label:

  • "Tariff Optimizer" -> "Reserve"
  • "Emergency Reserve" -> "Reserve"

What to do: Search your automations and scripts for option: "Tariff Optimizer" or option: "Emergency Reserve" and change them to option: "Reserve".

Bug Fix: "Reserve" Battery Mode Was Writing Wrong Value to PVS

In v2026.04.1, the "Reserve" Battery Control Mode option was incorrectly mapped to the varserver value TARIFF_OPTIMIZER. The correct varserver value for Reserve mode is BACKUP_ONLY.

This meant:

  • Selecting "Reserve" from the dropdown was writing TARIFF_OPTIMIZER to the PVS instead of BACKUP_ONLY
  • A battery already in BACKUP_ONLY (Reserve) mode would show as "unknown" in the dropdown

TARIFF_OPTIMIZER is a firmware-internal holding state the battery enters automatically at SOC limits (full charge or reserve floor). It is not a user-selectable mode. The confusion came from the fact that TARIFF_OPTIMIZER frequently appears when the battery is near reserve, making it look like it was the "Reserve" mode value.

Fixed. "Reserve" now correctly reads and writes BACKUP_ONLY.

Thanks to CASHIH90 for the screenshots that pinpointed the bug.

All Other Changes Since v2026.03.x

Startup Crash Fix (v2026.04.2)

Some PVS firmware versions do not expose the /sys/pvs/flashwear_type_b varserver variable and hang indefinitely on the request. Added a 15-second timeout to every varserver request so a non-responsive PVS variable can no longer block integration startup.

Battery Mode Labels Now Match SunStrong App (v2026.04.1)

  • "Tariff Optimizer" renamed to "Reserve"
  • "Emergency Reserve" removed

Two New Read-Only Battery Sensors (v2026.04.1)

  • ESS Configured Mode: Shows control_mode (what you have set)
  • ESS Operating Mode: Shows opMode (what the battery firmware is actually doing)

False Firmware Upgrade Notification Fixed (v2026.04.1)

Nightly "PVS FIRMWARE UPGRADED -> Unknown" notifications were caused by a default value bug. Fixed.

Startup Log Cleanup (v2026.04.1)

Transient connection failures during startup now log as WARNING instead of ERROR.

No configuration changes required. Update via HACS.

Assets 2
Loading