Just wanted to follow-up and say thanks to @garrett.kranz for some suggestions to get my system back online. Not sure what caused it, but Alexa kept telling me “the server is unresponsive”. Disabling the skill from Alexa and enabling it again brought everything back and also kept my routines and groups intact.
5 Likes
Event history is critical for automation debugging.
for example. I have a situation where a relais is being switched off after les then 30 minutes of inactivity and when the motion sensor has a gone through a sequence (motion, no-motion, motion) while the condition in the automation is switch off after 30 minutes of no-motion. It’s kind of hard to deal with this if you have to wait 9-14 hours on the exact time-stamps of the trigger events.
Generally speaking, I find event history to be largely informative and/or diagnostic. Yes, it can be used by apps like webCoRE for more exotic conditions but is that really what it is designed for?
If I look at the event history there are two broad possibilities:
- Event history is working as intended and so what I am seeing, or not seeing, is meaningful.
- Event history is not working as intended so I can’t rely on what I am seeing, or not seeing, so I’ll have to come back another time.
In terms of the implications:
- is obviously what we are all aiming for.
- is an inconvenience.
The problem can be knowing if it is 1) or 2). Not knowing can mean me wasting my time, but a status message could mean tea and a biscuit.
@garrett.kranz, The lag of the history is decreasing, it has gone from 16 hours to 1 hours at this time.
in case you need any feedback to confirm the progress of the actions taken
1 Like
Yes lag is at 1 hour now, but do you see missing chunk of history between 2 ago, and 6 hours ago? 4 hours missing.
@Alwas, I have everything history until 5 minutos ago
History got worse again, 1 hour delay