One reason for these messages is, that probably during startup, or network glitch situations your meter gets a value ‘undefined’, ‘unknown’ etc. and thus generates an error. However, then it probably shouldn’t read ‘low > low’ ?
I have got this type of messages often, and always during power cut, restart, network glitch or similar situations
Logger: homeassistant.components.integration.sensor
Source: components/integration/sensor.py:258
Integration: integration (documentation, issues)
First occurred: 05:14:12 (46 occurrences)
Last logged: 16:22:22
Invalid state ( > 926.1): [<class 'decimal.ConversionSyntax'>]
Invalid state ( > 3986.35): [<class 'decimal.ConversionSyntax'>]
Invalid state ( > -3986.35): [<class 'decimal.ConversionSyntax'>]
Invalid state ( > 0.0): [<class 'decimal.ConversionSyntax'>]
Invalid state ( > 0): [<class 'decimal.ConversionSyntax'>]
The left side of ‘>’ is always empty, and these readings come from different meters. Also, I do not have any comparisons, at least in config.yaml templates that could explain the syntax?
So. I basically know what causes the errors (or at least I think so), but cannot trace them to any particular entities.
My question is, what are or should be the readings on the both sides of ‘>’ ? In another words, what is the explanation/ syntax of:
The utility meter does not generate errors for these states. In fact those states are required to prevent huge jumps back to the previous total when a sensor has been offline.
Hmmm… It could be remotely interesting to check whether people find the topic and even better, then knew the answer, but I do not think I’ll bother. It’s not that important.