Quick question: How do you avoid the status of the respective items going to UNDEF when the PV modules don’t deliver any power / the inverter goes into hibernation?
In my case, outside of the times when the inverter is powered on (see example below)…
… the state of the items goes to UNDEF, which does not look nice in dashboards (more a cosmetic problem)…
… but also causes problems when using the values as input for calculations in rules.
I read found this thread here but was wondering whether there’s a better way to do this? This thread here would solve the problem for “current power”, but overwriting e.g. “daily energy” to zero if the inverter goes down would simply produce wrong results.
Any ideas?
From what I can see, the easiest fix would be if openDTU would continue to submit the last value, even if the inverter goes down?
It depends on different things:
Persistence strategy, whether the inverter does reply on messages after sunset etc. My inverter/s are set to be silent at night. This+persistence helps me to get no false values. I do reset certain values at midnight using a rule.
I am using an HM-600. From what I can see, there is no way for me to change the behavior of the inverter.
If your inverter is set to be silent at night, you should be having the same problem I’m having (no response from the inverter → UNDEF in openHAB)?
Update: Maybe I’m looking at an MQTT problem / integration problem into openHAB. When running mosquitto_sub -h 192.168.0.150 -u username -P password -v -t solar/# the output shows the desired values even if the inverter is down (at night), so I have to check the MQTT channel tomorrow.
Solution: The flag “enable expiration” has to be disabled for the items to contain data without gaps when the inverter is switched off. I found the solution here on openDTUs Github page.
