I have an input boolean that has not changed state for a long time. On the main page it shows that it’s in current state for a 4 weeks, but history is empty.
Then, if I change it’s state, the first change reason wouldn’t get to the history at all. It shows when the state was changed on the graph, but not the reason for it.
Ok, but my post is not about it. I just changed the state 2 times. Both of them are shown on the graph, but history shows only second one. Both happened in the last minute
UPD: i’ve tested it a few times on different input booleans I didn’t touch in a while and it works like this every one of them.
Everything looks correct based on the images you’ve shown. You see the on state in the logbook and history. The off state was the previous state. The context for that state wasn’t known because it happened outside the history window that you have.
It was OFF, I turn it ON, history shows that it became ON, but does’t show who or what did this change
It’s now ON, I turn it OFF. Now history shows not only time of this change, but that Admin cnanged the state
The point of this whole thing is not about 10 days history. It is about (just please, look at the 15 seconds video) that I do 2 state changes right now recording this and see only 1 of them in the history
Ok, here’s another similar input boolean I still haven’t touched. HA def knows it’s state, so it’s sertainly not “nothing”.
Anyway, how can I “fix” this annoying issue without setting purge_keep_days to 10k and killing my ssd after a few months? What’s the workaround? Next time something really important changes state after a long time, I need to know why it did this.
Every state change is important. Every single one. I just can’t understand how is this not a bug that state change is not logged anywhere. HA knows the current state, nevermind the history.