Releases: marq24/ha-senec-v3
Ensure that 'spare_capacity' is a number - Solve Issue #118
SENEC Local: Support for NPU image version 2411 [+more debug logging]
SENEC Local
With the latest NPU image version 2411 (and related new Web frontend) the lala.cgi provide a cookie with each response. This build makes sure that this new cookie functionality is implemented also inside the web-session that will be used by HA when your SENEC system will be accessed.
SENEC Local: Support for NPU image version 2411
SENEC Local
With the latest NPU image version 2411 (and related new Web frontend) the lala.cgi provide a cookie with each response. This build makes sure that this new cookie functionality is implemented also inside the web-session that will be used by HA when your SENEC system will be accessed.
SENEC Local: Support for NPU image version 2408 / Cell Voltages 15+16
SENEC Local
NPU image 2408
With the recently forced update to NPU Image 2408, SENEC has introduced new problems - at least for me.
When I want to release/use the previously loaded power, after I have load the battery with power from the grid (when the price was low) via the corresponding maintenance function of the build in web frontend (that can be accessed via the switch.senec_safe_charge), then in almost every case (once the switch is set to OFF) the SENEC System will FAIL with some sync job (that I assume was introduced with the new firmware):
As result power usage from the battery will be almost immediately cancelled after few seconds and the battery module will try to recover something. The device logs show an continues loop of 'recovery something' entries. Once in this fuckup-state it seams to be almost impossible to get the battery back in "regular operation mode". Sometimes I could recover the situation when I had physically shut down the system and hard disconnected the unit from the grid (by pulling the plugs)... But this did not solve the problem always. Another 'solution' would had been to call the support of the company installed the unit here - and after some 'magic' happened in the background my unit come back to normal operation. Obviously I does not consider this approach as a solution - or even an acceptable workaround.
Making use of the 'save charge' switch is a operation every owner of a SENEC can trigger without any login/password requirements - so that this functionality is now broken is just one more entry in the long records of SENEC's software fails. I can't express how frustrating this is for somebody with an experience of +40 years in software development projects.
So instead of hoping for help/support from SENEC I fired the web-inspector up again on Friday evening and found some new fields available from the 2408 firmware. One of the new ones, allows you to request a REBOOT of the system. So this option can now be triggered from a new BUTTON entity inside HA [only available if the integration detect the NPU version 2408 (or higher)]. I must monitor in the next couple of days, if using this new function allows me to get over the fatal recovery-attempt-endless-loop.
WTF! Adding missing CellVoltages [A-D] Sensors 15+16
- added the missing 15 & 16 cell voltages (for A-D)
- set default display unit to VOLT
SENEC Local: Support for NPU image version 2408
SENEC Local
With the recently forced update to NPU Image 2408, SENEC has introduced new problems - at least for me.
When I want to release/use the previously loaded power, after I have load the battery with power from the grid (when the price was low) via the corresponding maintenance function of the build in web frontend (that can be accessed via the switch.senec_safe_charge), then in almost every case (once the switch is set to OFF) the SENEC System will FAIL with some sync job (that I assume was introduced with the new firmware):
As result power usage from the battery will be almost immediately cancelled after few seconds and the battery module will try to recover something. The device logs show an continues loop of 'recovery something' entries. Once in this fuckup-state it seams to be almost impossible to get the battery back in "regular operation mode". Sometimes I could recover the situation when I had physically shut down the system and hard disconnected the unit from the grid (by pulling the plugs)... But this did not solve the problem always. Another 'solution' would had been to call the support of the company installed the unit here - and after some 'magic' happened in the background my unit come back to normal operation. Obviously I does not consider this approach as a solution - or even an acceptable workaround.
Making use of the 'save charge' switch is a operation every owner of a SENEC can trigger without any login/password requirements - so that this functionality is now broken is just one more entry in the long records of SENEC's software fails. I can't express how frustrating this is for somebody with an experience of +40 years in software development projects.
So instead of hoping for help/support from SENEC I fired the web-inspector up again on Friday evening and found some new fields available from the 2408 firmware. One of the new ones, allows you to request a REBOOT of the system. So this option can now be triggered from a new BUTTON entity inside HA [only available if the integration detect the NPU version 2408 (or higher)]. I must monitor in the next couple of days, if using this new function allows me to get over the fatal recovery-attempt-endless-loop.
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
Contributors
Assets 2
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
Contributors
Assets 2
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.