-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid state #27
Comments
This will be due to #24 and now throwing an error in the log. If you dont need these entries anymore, I recommend using MQTT Explorer to delete these from your broker. Otherwise, locate/add them to Lovelace and "press" them which will update the stored format. You could also use this script to update your existing entries |
Hi When i look into the bug, i see the fix is merged, how come its still present then? |
The card was updated, but your existing entries still contain the old timestamp value which is invalid (from a HA perspective) which is why the HA log is showing you an error. With the check button card, you can long press to "define" when the value (as opposed to setting the value to 0) so do this to reset the time back to the current value, but updated to be correctly supported by HA |
Hi
Im getting following errors
Invalid state message '{"timestamp":1624002370,"timestamp_friendly":"6/18/2021, 9:46:10 AM","severity":[{"value":"12 months","color":"Red","seconds":31556952},{"value":"11 months","color":"Orange","seconds":28927206}]}' from 'homeassistant/sensor/ontkalker/state'
Not sure why it happens with some and some not.
If i look at those that show the error, the state is unknown, although its been 12 months since the button was pushed..
Any ideas?
The text was updated successfully, but these errors were encountered: