Skip to content

HA 2026.2 adjustments (patched) / Revised Wallbox Handling - Senec V4/P4 support - U-Turn / +Patch

Choose a tag to compare

View all tags
@marq24 marq24 released this 03 Feb 19:34
2026.2.2
44e1ea9

HA 2026.2 adjustments

The upcoming release of HA 2026.2 requires an update of this integration. That's why it's so important, that an integration will be actively maintained.

Wallbox support for Senec V4/P4 Systems

Honestly I can't emphasize this enough Big Kudos Julian R. All the latest changes would not had been possible without Julians patience and support.

Changes in this new release

  • Each Wallbox (and the corresponding entities) will now show up in HA as a own device - this makes all the Wallbox I, Wallbox II,... prefixes in the entity names obsolete (but of course they are still present in the entity_id)
  • Wallbox entities are enabled by default, if during the launch of the integration a wallbox is detected
  • Wallbox mode Select 'refactored' (see details below)

U-Turn in wallbox mode handling

In the SenecApp you have the possibility to toggle between the different wallbox modes [FAST, SOLAR, COMFORT (P4 only)] and then once a mode is selected you have in the app additional Expert Settings (for the selected mode). In previous releases I have tried to integrate all the different expert settings also in the main wallbox-mode-select entity. That approach has worked some sort of, but at the end of the day I came to the conclusion to stick more to the default behavior of the SenecApp.

The main reason for this decision is the fact, that the handling of the different toggle options SenecApp are not consistent at all. Specially when comparing Android and iOS SenecApp side by side. In fact: While the Android SenecApp showed an option enabled, the iOS SenecApp showed the same option disabled. Even if both apps have been restarted and a sync with the backend system had been enforced. So at the end of the day it's impossible for me to decide, WHEN a switch can be considered as been "turned" ON or OFF.

So to get out of this dilemma, all the different switches are now available as separate switch entities (and showing the state as the Android SenecApp does). The different switches are only enabled, if the corresponding mode is selected. I am not sure, if an automation is able to toggle a disabled entity or not - I am sure you will figure this out.

Before you start to freak out - the origin wallbox mode selector is still present - the name has just changed - if you want the previous wallbox mode selector entity back, just enable the wallbox_1_mode_legacy (but I can't promise to keep the functionality).

All previous wallbox modes have been renamed (all got the prefix legacy_) and the wallbox_1_state modes attribute will contain now also the integration_legacy and restore_legacy information as well.

Changes in the previous (pre) release

  • Support the additional 'Comfort' Wallbox mode for Senec V4/P4 Systems
  • Using alternative endpoints to switch between the different Wallbox modes (I hope this will also work with V2/V3 systems)
  • Using an alternative endpoint to fetch Wallbox energy consumption. You might need to make use of the button.[your-name]_delete_cache (Delete session data button) to reset your statics.
  • Solar-optimized: compatibility aka prevent charge interruptions aka continuous charging mode revised. This is really a quite sad story. In the SenecApp the Solar Optimized Expert Setting is called Ladeunterbrechung verhindern - but the corresponding attributes in JSON content are really really confusing and the SenecApp itself seams to have an issued with toggling this switch. So I just can keep my fingers crossed

That's how I spend my weekends

I really had different plans - but turned out that some simple tasks are not that simple at all... specially when you don't have any control over the backend (already some sort of logging would had been great) - sigh

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

GithubSponsor Revolut Wero PayPal BuyMeCoffee Github Stars
If you haven't starred this integration in Github yet - please do so - TIA

Assets 3
Loading