Closed gcoan closed 5 months ago
I've pushed a fix to main to:
thanks, I'll give it a test and see how it behaves. Is the error attribute set only on this error or is it more general set when there's a predbat failure, and I assume the attribute is cleared if Predbat gets to the end of a normal run?
It's just a binary true/false for any type of error so it should be false for normal runs
thanks, I have updated my automation to use this error attribute and added details of using it to the documentation
Describe the bug The wi-fi node in my garage lost connection this afternoon so the inverters went offline. Predbat started reporting errors with time being incorrect and REST failing & would be disabled, but because predbat.status changed every 5 minutes the script I have to detect a Predbat failure occuring for a period of time couldn't be triggered.
history of predbat.status:
and carries on like this for the next 2 hours
![image](https://github.com/springfall2008/batpred/assets/142018870/25cd3658-34da-4911-b6fb-79b05371e52e)
Expected behavior
I suspect the REST issue is what caused the second issue. Might be that the errors were coming from the balance inverter code?
Predbat version 7.16.3
Environment details HAOS, 2x 5kW hybrid inverters
Log file logfile extract: