A device is offline or unavailable
Use the device-offline path first so power, radio, network, and integration checks stay in the right order before resets start.
Problem-first browse layer
Home automation problems: start here
Use this page when the automation system is the problem but the right next page is not obvious yet. Start from the symptom you actually see, then move into the calmest guide or flow.
Use this page when
- The smart-home problem is real but the right page is not obvious yet
- You want the symptom path before the setup and buying pages
- You need a calmer entry point than the whole automation library
- You want to move from symptom to the right next step without guessing
Best first clicks
Start with the clearest automation symptom, not the fix idea
An automation did not run the way I expected
Start with the live automation flow when the trace is the next best clue, then move into the beginner automation guide if the bigger setup still needs simplification.
Zigbee devices will not pair or stay stable
Separate first-time pairing trouble from later reliability trouble so channel, distance, and coordinator checks stay sane.
I think the overall setup choice is the real issue
Switch to the onboarding and planning layer when the symptom really points to the bigger platform, host, or starter-device path.
Pick the symptom you actually see
Common home-automation problem patterns
A device shows offline or unavailable
Separate power, radio, network, and integration-path problems before resetting the whole system.
An automation did not run
Start with traces and recent changes before rewriting the automation logic.
A Zigbee device will not pair
Use the pairing path before changing channels, rebuilding the network, or trying random resets.
Zigbee devices keep dropping later
Switch to the reliability path when the issue is not first-time pairing anymore.
I think the setup choice is the real problem
Move into the planning and comparison layer when the symptom points to the bigger platform or device path.
I need a useful first device or automation path
Switch to the beginner guide layer when the issue is really about choosing a cleaner starting point.
Use the library that fits the moment
Start with the symptom, not the fix idea
Choose the page that matches what you can actually observe right now. That usually gets you to the right troubleshooting flow faster than guessing the protocol or device type first.