Obtaining historical values after replacing an inverter #907
jschmitz-de
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I am becoming increasingly enthusiastic about the FoxEss extension because the Modbus integration is extremely stable, and the community is highly competent and active.
Last week, I replaced my H3-Pro 15 with an H3-Pro 20, and, of course, I updated the firmware.
Version: BMS 1 Master: 2.06
Version: Manager: 1.38
Version: Master: 1.68
Version: Slave: 1.06
Two problems arose during the change:
1.) The scaling for the total and today values changed from 0.1 to 0.01. This change is already included in commit 3f7145f 🥇
2.) My history Values are all back to 0. 👎
I have mitigated this issue by adding the last known values for the entity to the "_total" queries in "entity_descriptions.py":
post_process = lambda x: x + "_battery_charge_total_history_offset"
( but I entered the real value, not a variable. :-))
So - my suggestion - because I Think i´m not the only one who will change the Inverter in his Lifetime:
Is it possible to store such an offset "permanently" in the total values so that it is not overwritten with every update? And - how could this be done with variables, which could then perhaps be stored in a Configuration.yaml file? ?
Thanks for your great work
Joerg
Beta Was this translation helpful? Give feedback.
All reactions