WebAPI: Adjustments since SENEC have shut down an v1 API endpoint [updated 2]

WebAPI

Since "today" (1'st of November) the WebAPI Integration can not fetch any updates for the total statistic values (accuimport_total, accuexport_total, gridimport_total, gridexport_total, powergenerated_total, consumption_total). So the integration was adjusted to fetch this data now from a API v2 endpoint [https://app-gateway.prod.senec.dev/v2/senec/systems/YOUR_SENEC_SYSTEM/measurements?resolution=YEAR]

But SENEC would not be SENEC, if these different enpoints would not return different values - so don't be surprised, when some of your sensors have jumps in your dashboards!

Local Senec

With 2024.10.0 a issue was introduced that was reported #109 - thanks @neubi4 -> the parser changes could not handle "empty valued" - this is fixed now

Local Inverter

Fix for the Inverter fix introduced with 2014.10.0

WebAPI: Adjustments since SENEC have shut down an v1 API endpoint [updated]

WebAPI

Since "today" (1'st of November) the WebAPI Integration can not fetch any updates for the total statistic values (accuimport_total, accuexport_total, gridimport_total, gridexport_total, powergenerated_total, consumption_total). So the integration was adjusted to fetch this data now from a API v2 endpoint [https://app-gateway.prod.senec.dev/v2/senec/systems/YOUR_SENEC_SYSTEM/measurements?resolution=YEAR]

But SENEC would not be SENEC, if these different enpoints would not return different values - so don't be surprised, when some of your sensors have jumps in your dashboards!

Local

With 2024.10.0 a issue was introduced that was reported #109 - thanks @neubi4 -> the parser changes could not handle "empty valued" - this is fixed now

WebAPI: Adjustments since SENEC have shut down an v1 API endpoint

Since "today" (1'st of November) the WebAPI Integration can not fetch any updates for the total statistic values (accuimport_total, accuexport_total, gridimport_total, gridexport_total, powergenerated_total, consumption_total). So the integration was adjusted to fetch this data now from a API v2 endpoint [https://app-gateway.prod.senec.dev/v2/senec/systems/YOUR_SENEC_SYSTEM/measurements?resolution=YEAR]

But SENEC would not be SENEC, if these different enpoints would not return different values - so don't be surprised, when some of your sensors have jumps in your dashboards!

Bugfix for buildIn Inverter support

bugfixes

• BuildIn Inverter code stopped working with recent HA update
• SGReady switch was not working (cause of changes in SENEC 'API')
• removed references to hass.helpers #104
• minor adjustments after LFP change

Supporting default HA sensor customization's

By default HA sensors can be customized by the user [mainly this are unit factor's and the display precision]. This feature was totally ignored by previous implementations of this integration and with this release its finally supported.

The change implies, that for some of the existing sensors the default display (precision) have been adjusted - if you dislike the new display format you can now simply adjust it the sensor settings.

Simple WebAPI SGReady Implementation

This release adds support to read the SGReady Mode via the WebAPI - the value value will be provided in text and in "code" format (the code sensor is much better to use with automations - since you do not have to parse a language dependant string.

Also SGReady can be enabled/disabled via a switch entity.

Since the SENEC SGReady support is an ADDON-Service you must order @ SENEC the new sensors are disabled by default and must be enabled. Nevertheless the integration checks, if your account have these additional settings available.

Thanks @wersim for your suggestion - I hope this version will fit your needs.

Fallback if [BMS][MODULES_CONFIGURED] not available

Could be that older firmware's does not provide the BMS MODULES_CONFIGURED attribute - so there must be an additional check, if this is the case. That might be the root cause for #100

Fix for #96 - Patch of aiohttp impl is not required... (with HA 2024.8.x)

This update is only required for the WebAPI-part of the Integration. The update ensures, that the aiohttp lib (cookie handling) will be only patched, when the lib version is lower then 3.9. Cause I am still a Python noob, the version check was insufficient and my included lib patch is incompatible with the latest version of the aiohttp lib. The lib update was included with the HA update from 2024.7.x to 2024.8. So this release fix the usage of the version comparison code and so the internal lib patch will finally only applied when it's really required - thanks @KalleRau for reporting this issue.

Bugfix: Checking number of configured BMS modules (before accessing array)

This release fix an issue, when the number of installed modules to the BMS will change (e.g. when they will be replaced by LFP versions)
See also #96

The new release will check the number of configured modules before accessing the array @ the module index.

Bugfix for WEBAPI setup when using aiohttp 3.10.0

Fixing issue #95