Matthias Marquardt

IMHO (who ever cares) it does not make much sense to try to use this (or any fork) as source for a Senec V4 HA integration - If there is...

Of course that can be done/implemented too - with the down side, that the data first goes from your home to the senec servers and then from there you collect...

@Ich-h4lt - thanks for sharing the postman res... Looking at the JSON content making me to run away FAST... Great mixture of German and English - IMHO classic fail -...

I just can guess, that the panel you found is some sort of similar to the "patch-field" build into the v3 (as documented in the install instructions)...  There are...

> ...the v3 has the workaround “emergency charging” via http request... in my fork (obviously for v3) I have integrated this as ha-switch... [called 'safety charging' (will also "respect" the...

@klaus1956 I "just" own a V3 hybrid duo - to my best knowledge the interface have not been changed (could be that additional fields are present in v3 that does...

FUNNY - while I am tyring - you already provide the info... the values (that are still available in my environment) are constantly growing - so there is no need...

added workaround information in the initial post

Please note, there was a typo in my provided configuration.yaml in the `senec_grid_total_export_fb` the source has to be: `source: sensor.senec_grid_exported_power` (and not `source: sensor.senec_senec_grid_exported_power`) - sorry...

Since here (locally) I still have the http version - I am able to compare the values [created via the `integration` platform vs data from the senec statistics json data]...