Entity Friendly Name Fix

Entity Friendly Name Fix

A very old bug was present in the entity friendly name calculation, that should be fixed in all my integrations.

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.

If you haven't starred this integration in Github yet - please do so - TIA

Enable/disable OCPP

Implemented feature request

With this release the feature request #143 have been implemented - it's now possible to enable/disable OCPP support of your wallbox via the HA integration. (no further support for additional OCPP attributes is currently planed)

My latest HA-Integration... (some sort of advertisement)

If you have some investments in ETF's (in €) and you want to see the development of different ISIN in near real time (of course only during trading hours), then I would kindly ask you to try my latest HA integration: ha-justetf-live and provide some feedback - The integration have it's focus on daily/monthly changes. TIA

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.

If you haven't starred this integration in Github yet - please do so - TIA

CORE always return adi = true

CORE Charger adjustment

Looks like, that the new CORE is returning always true for the adi - this had the result, that the 16A limit was always applied. This is fixed in this release - details can be found in #142

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.

If you haven't starred this integration in Github yet - please do so - TIA

Show in DeviceInfo if 16A limiter is active

Charger Device Info show [16A limited]

Re: #141
When your changer indicates, that a 16A limit should be applied, the integration will decrease all MAX Ampere values from 32A to 16A.
Possible reasons:

• You have configures the Integration with a 16A limit
• The API returns the value 11 for var
• The API returns true for adi

If one of this is true, the 16A limit will be applied.

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.

If you haven't starred this integration in Github yet - please do so - TIA

Possible fix for unavailable Sensors

Possible fix for unavailable Sensors

I have found a possible reason that could cause sensors becoming unavailable. We will see, if my assumption was/is correct - I'll keep my fingers crossed.

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.

If you haven't starred this integration in Github yet - please do so - TIA

Fix for Force Configuration Update Button (when using WebSocket)

Force Configuration Update Button

When using the WebSocket connection, pressing the Force Config Update Button had no effect, since the ws_data container was not updated with the new values. So IF we have the situation, that some data is updating internally in your wallbox (like frc) but for what ever reason this new data does not arrive via the WebSocket, then using now the force update button will show you the new values. When you enable the debug log, you should be able to see, which fields/sensors will be updated by the button action.

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.

If you haven't starred this integration in Github yet - please do so - TIA

2026.4.4

Reduce data update frequency to at least one second

As mentioned in #135 the WebSocket can create some states to change very frequent (technically every 300ms) and this could overload your HA states db (details can be found in #135). With this new release the integration makes sure, that the minimum data update interval (no matter how fast data arrives via the WebSocket) will be one second.

Additional configuration setting

If you enable the new Apply 'Polling Interval' also to WebSocket updates option, the sensors will only be updated at the configured update interval - even when used the WebSocket connection.

E.g. when you have selected 10sec for the polling-data-from-your-goe-device, then the data in HA will be also updated (just) every 10 seconds, even if the integration has received multiple updates via the established WebSocket connection. Of course only the latest data will be populated to your HA .

Completed migration to CoordinatorEntities

I have fully transitioned the integrations DataUpdateCoordinator to utilize the CoordinatorEntity pattern. As part of this update, all "classic" polling logic—specifically individual async_update methods within each entity—has been completely removed.

Key Improvements:

• State Consistency: All entities update simultaneously as soon as the coordinator receives new data, ensuring a unified state across the dashboard.
• Modern Standards: By removing legacy polling logic from individual sensors, the codebase is now cleaner, more maintainable, and fully aligned with current Home Assistant Best Practices.

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.

If you haven't starred this integration in Github yet - please do so - TIA

`fst` can now be a negative number [fixed]

This release will implemented the enhancements suggested in #134 - allow negative values for fst (JFYI: sensor is not active by default)

Note for myself - don't do released shortly after 7am!

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.

If you haven't starred this integration in Github yet - please do so - TIA

`fst` can now be a negative number

This release will implemented the enhancements suggested in #134 - allow negative values for fst (JFYI: sensor is not active by default)

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.

If you haven't starred this integration in Github yet - please do so - TIA

RoundingMode is writeable & German Translation adjustments

This release will implemented the enhancements suggested in #127 & #128. In order to avoid a breaking change with #128 the previous sensor for the tag frm still exists - so you have the value now twice - once as readonly and a second select.

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.

If you haven't starred this integration in Github yet - please do so - TIA