01

Layered diagnosis

Do not factory-reset first

A reset erases useful evidence and can create a second setup problem. First decide whether one device, one automation, one platform, or the whole home is affected. Note the last known working time and any router, account, household, firmware, bridge, or controller change near that time.

If electrical equipment is unpowered or behaving unsafely, stop and follow its manufacturer instructions or seek qualified help. The diagnostic path below is for control behavior, not electrical repair.

02

Layered diagnosis

Test from the device outward

  1. Physical control: if it fails, inspect safe power and device conditions first.
  2. Manufacturer app: if direct control works, the device and its immediate connection are probably intact.
  3. Control platform: test the device manually. Failure here points toward account linking, permissions, a bridge, controller, or platform support.
  4. Automation action: run each action alone. A bad action can make a healthy starter look broken.
  5. Starter and conditions: trigger manually if possible, then inspect schedule, sensor, presence, household, and time-zone state.
  6. Infrastructure: confirm controller, bridge, Thread border router, IP network, and cloud availability as applicable.
03

Layered diagnosis

Read the symptom as a layer clue

SymptomInspect next
Works in manufacturer app onlyAccount link, permission, bridge, or receiving-platform support.
Manual platform control works; schedule does notStarter, condition, time zone, presence, or disabled rule.
Thread devices fail togetherBorder router, controller, IP network, or recent router change.
Action happens twice or reversesDuplicate or opposing rules across apps.
Only remote control failsInternet, cloud authorization, or home-controller availability.
04

Layered diagnosis

Change one thing, then retest

Make one targeted change and repeat the same test before moving to another layer. Google exposes automation logs for supported scripted automations; use available history rather than guessing. If escalation is needed, provide the exact model, software version, platform, symptom, recent changes, and tests already completed.

Only reset after model-specific support instructions make it the next justified step and you have the setup code, owner account, and rebuilding plan.

Evidence boundary

Recheck mutable platform details

Platform features, supported device types, account behavior, and exact-product roles can change with software, model, region, and subscription state. Confirm current documentation for your exact setup. Use manufacturer instructions and qualified help for mains electrical or HVAC work.

Primary sources

Official documentation used for technical boundaries

Continue the lifecycle