Automation troubleshooting playbook, what do you check first? what shows up when stuff goes wrong?

[Alan]

End of January 2026 check in for the Home Automation Forum. I want to build a community “support playbook” for those moments when automations start getting flaky. Stuff like missed triggers, random delays, or the classic “why did it do that” behavior. A lot of threads end up with people rebuilding everything, when there’s usually a few quick checks that can narrow it down fast.

When your setup starts acting weird, what do you check first, and what logs or signals do you rely on? Share your routine, like checking device availability, event history, Zigbee or Z-Wave health, WiFi strength, time windows, or whether a cloud service is having a bad day. If you have a habit that prevents flakiness in the first place, drop that too.

 

[VanderMueller]

I try to split it into two buckets. Did the event happen but the network didn’t deliver it, or did the event arrive and the logic didn’t do what I thought. So I’ll check event logs and then check mesh health next. Zigbee or Z-Wave route changes and a missing repeater can look like “random delays” even when nothing else changed.

 

[PeppyBlueBear]

My order is device availability, then mesh health, then automation logic. If Zigbee or Z-Wave is weak, everything looks random even when the rule is correct. Logs I rely on are event history plus any message like “device unavailable” or delayed commands.