Distinct consumer questions
Smart-home troubleshooting
Browse smart home by the symptom the customer actually sees. Each record has its own observation, isolation test, correction, verification and stop condition; manufacturer names are not swapped into generic copy.
Browse by platform
656 complete records in this directoryAlexa routine runs only sometimes
Intermittent routines usually fail at the trigger, one action, device reachability or timing condition. The activity history shows where the chain stopped.
Open record Smart home · alarmsConnected smoke or carbon-monoxide alarm behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates connected smoke or carbon-monoxide alarm through local alarm sensor/power versus network, notification and account.
Open record Smart home · alarmsConnected smoke or carbon-monoxide alarm is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates connected smoke or carbon-monoxide alarm through local alarm sensor/power versus network, notification and account.
Open record Smart home · alarmsConnected smoke or carbon-monoxide alarm is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates connected smoke or carbon-monoxide alarm through local alarm sensor/power versus network, notification and account.
Open record Smart home · alarmsConnected smoke or carbon-monoxide alarm keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates connected smoke or carbon-monoxide alarm through local alarm sensor/power versus network, notification and account.
Open record Smart home · alarmsConnected smoke or carbon-monoxide alarm stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates connected smoke or carbon-monoxide alarm through local alarm sensor/power versus network, notification and account.
Open record Smart home · alarmsConnected smoke or carbon-monoxide alarm works for one member, room, routine or controller only
A smart-home failure limited to one member, room, automation or controller belongs to that ownership or execution path. This record isolates connected smoke or carbon-monoxide alarm through local alarm sensor/power versus network, notification and account.
Open record Smart home · contact sensorDoor or window sensor says open when it is closed
A contact sensor can misread when magnet alignment, gap, orientation, battery or mounting has changed. Move the magnet near the sensor before deleting it from the system.
Open record Smart home · voice processingGoogle Home keeps saying something went wrong
That response can mean internet loss, account/service trouble, unsupported command or one linked provider failure. A basic time/weather request separates core assistant access from a linked service.
Open record Smart home · HomePodHomePod plays music but will not control the smart home
Music playback proves speaker and some network access, while home control also depends on the Home membership, hub state, accessory reachability and account permissions.
Open record Smart home · MatterMatter controller commissioning behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates Matter controller commissioning through controller/hub eligibility versus Bluetooth, Thread/Wi-Fi and prior commissioning.
Open record Smart home · MatterMatter controller commissioning is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates Matter controller commissioning through controller/hub eligibility versus Bluetooth, Thread/Wi-Fi and prior commissioning.
Open record Smart home · MatterMatter controller commissioning is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates Matter controller commissioning through controller/hub eligibility versus Bluetooth, Thread/Wi-Fi and prior commissioning.
Open record Smart home · MatterMatter controller commissioning keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates Matter controller commissioning through controller/hub eligibility versus Bluetooth, Thread/Wi-Fi and prior commissioning.
Open record Smart home · MatterMatter controller commissioning stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates Matter controller commissioning through controller/hub eligibility versus Bluetooth, Thread/Wi-Fi and prior commissioning.
Open record Smart home · MatterMatter controller commissioning works for one member, room, routine or controller only
A smart-home failure limited to one member, room, automation or controller belongs to that ownership or execution path. This record isolates Matter controller commissioning through controller/hub eligibility versus Bluetooth, Thread/Wi-Fi and prior commissioning.
Open record Smart home · Matter setupMatter setup code is not working
A Matter code can fail because the accessory is already commissioned, not in pairing mode, too far from Bluetooth/thread infrastructure, or being added to the wrong home/admin ecosystem.
Open record Smart home · thermostatsRemote thermostat temperature sensor behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates remote thermostat temperature sensor through sensor placement/battery versus pairing, averaging and HVAC airflow.
Open record Smart home · thermostatsRemote thermostat temperature sensor is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates remote thermostat temperature sensor through sensor placement/battery versus pairing, averaging and HVAC airflow.
Open record Smart home · thermostatsRemote thermostat temperature sensor is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates remote thermostat temperature sensor through sensor placement/battery versus pairing, averaging and HVAC airflow.
Open record Smart home · thermostatsRemote thermostat temperature sensor keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates remote thermostat temperature sensor through sensor placement/battery versus pairing, averaging and HVAC airflow.
Open record Smart home · thermostatsRemote thermostat temperature sensor stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates remote thermostat temperature sensor through sensor placement/battery versus pairing, averaging and HVAC airflow.
Open record Smart home · thermostatsRemote thermostat temperature sensor works for one member, room, routine or controller only
A smart-home failure limited to one member, room, automation or controller belongs to that ownership or execution path. This record isolates remote thermostat temperature sensor through sensor placement/battery versus pairing, averaging and HVAC airflow.
Open record Smart home · night visionSecurity camera night vision is blinded by a window
Infrared light reflects from glass back into the lens, so an indoor camera aimed through a window may show glare instead of outdoors. Turn off IR or mount outside using an outdoor-rated model.
Open record Smart home · camerasSecurity-camera motion detection behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates security-camera motion detection through capture timing versus notification delay, lighting, battery sleep and zone geometry.
Open record Smart home · camerasSecurity-camera motion detection is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates security-camera motion detection through capture timing versus notification delay, lighting, battery sleep and zone geometry.
Open record Smart home · camerasSecurity-camera motion detection is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates security-camera motion detection through capture timing versus notification delay, lighting, battery sleep and zone geometry.
Open record Smart home · camerasSecurity-camera motion detection keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates security-camera motion detection through capture timing versus notification delay, lighting, battery sleep and zone geometry.
Open record Smart home · camerasSecurity-camera motion detection stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates security-camera motion detection through capture timing versus notification delay, lighting, battery sleep and zone geometry.
Open record Smart home · camerasSecurity-camera motion detection works for one member, room, routine or controller only
A smart-home failure limited to one member, room, automation or controller belongs to that ownership or execution path. This record isolates security-camera motion detection through capture timing versus notification delay, lighting, battery sleep and zone geometry.
Open record Smart home · camerasSecurity-camera night vision behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates security-camera night vision through camera sensor versus IR source, glass, nearby wall and external lighting.
Open record Smart home · camerasSecurity-camera night vision is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates security-camera night vision through camera sensor versus IR source, glass, nearby wall and external lighting.
Open record Smart home · camerasSecurity-camera night vision is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates security-camera night vision through camera sensor versus IR source, glass, nearby wall and external lighting.
Open record Smart home · camerasSecurity-camera night vision keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates security-camera night vision through camera sensor versus IR source, glass, nearby wall and external lighting.
Open record Smart home · camerasSecurity-camera night vision stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates security-camera night vision through camera sensor versus IR source, glass, nearby wall and external lighting.
Open record Smart home · camerasSecurity-camera night vision works for one member, room, routine or controller only
A smart-home failure limited to one member, room, automation or controller belongs to that ownership or execution path. This record isolates security-camera night vision through camera sensor versus IR source, glass, nearby wall and external lighting.
Open record Smart home · camerasSecurity-camera Wi-Fi connection behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates security-camera Wi-Fi connection through camera power versus band/security, signal, upload and cloud service.
Open record Smart home · camerasSecurity-camera Wi-Fi connection is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates security-camera Wi-Fi connection through camera power versus band/security, signal, upload and cloud service.
Open record Smart home · camerasSecurity-camera Wi-Fi connection is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates security-camera Wi-Fi connection through camera power versus band/security, signal, upload and cloud service.
Open record Smart home · camerasSecurity-camera Wi-Fi connection keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates security-camera Wi-Fi connection through camera power versus band/security, signal, upload and cloud service.
Open record Smart home · camerasSecurity-camera Wi-Fi connection stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates security-camera Wi-Fi connection through camera power versus band/security, signal, upload and cloud service.
Open record Smart home · camerasSecurity-camera Wi-Fi connection works for one member, room, routine or controller only
A smart-home failure limited to one member, room, automation or controller belongs to that ownership or execution path. This record isolates security-camera Wi-Fi connection through camera power versus band/security, signal, upload and cloud service.
Open record Smart home · lightingSmart bulb stays offline after a power outage
After an outage, the bulb, bridge, router and cloud connection may recover in the wrong order. Confirm local power and bridge status before resetting the bulb.
Open record Smart home · camerasSmart camera records only after the motion has passed
Late clips can result from battery sleep, motion-zone placement, sensitivity, cooldown, weak Wi-Fi or cloud delay. Live view timing and event timestamp separate capture from notification delay.
Open record Smart home · garageSmart garage-door controller behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates smart garage-door controller through opener mechanics/safety beam versus controller sensor, Wi-Fi and account.
Open record Smart home · garageSmart garage-door controller is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates smart garage-door controller through opener mechanics/safety beam versus controller sensor, Wi-Fi and account.
Open record Smart home · garageSmart garage-door controller is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates smart garage-door controller through opener mechanics/safety beam versus controller sensor, Wi-Fi and account.
Open record Smart home · garageSmart garage-door controller keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates smart garage-door controller through opener mechanics/safety beam versus controller sensor, Wi-Fi and account.
Open record Smart home · garageSmart garage-door controller stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates smart garage-door controller through opener mechanics/safety beam versus controller sensor, Wi-Fi and account.
Open record Smart home · garageSmart garage-door controller works for one member, room, routine or controller only
A smart-home failure limited to one member, room, automation or controller belongs to that ownership or execution path. This record isolates smart garage-door controller through opener mechanics/safety beam versus controller sensor, Wi-Fi and account.
Open record Smart home · locksSmart lock reports jammed or will not turn
A jammed smart lock is often mechanical alignment, bolt friction, weak batteries or calibration—not app connectivity. Test with the door open before forcing the motor.
Open record Smart home · smart plugSmart plug turns off by itself
Unexpected shutoff can come from schedules, energy limits, overload/overheat protection, button presses or connectivity—not necessarily a cloud command.
Open record Smart home · HVAC configurationSmart thermostat runs heat when cooling is selected
Opposite operation can come from heat-pump reversing-valve configuration, mislabeled wiring or equipment fault. Turn the system off; repeated testing can heat or damage the home.
Open record Smart home · HVACSmart thermostat says heating but the furnace is not running
A heat call on screen does not prove the HVAC received power/control. Check mode, setpoint, equipment delay, breaker/service switch and furnace fault light without bypassing controls.
Open record Smart home · invitationsSmart-home invitation stays pending or never arrives
Invitations depend on the recipient’s exact account, cloud sync, supported region/version and home-owner permissions. Repeated invites to aliases can create confusion.
Open record Smart home · presenceSmart-home presence and geofence behaves incorrectly or produces the wrong result
A wrong result requires checking inputs, mode, calibration and output separately; a working control path can still be configured for the wrong state. This record isolates smart-home presence and geofence through phone permission/background state versus account membership and overlapping occupants.
Open record Smart home · presenceSmart-home presence and geofence is not working
A complete failure should be separated into power or eligibility, the external path, and the component itself before any reset. This record isolates smart-home presence and geofence through phone permission/background state versus account membership and overlapping occupants.
Open record Smart home · presenceSmart-home presence and geofence is unusually slow or delayed
A delay can come from capacity, weak signal, background work, protection or a service wait; measuring the exact stage prevents the wrong repair. This record isolates smart-home presence and geofence through phone permission/background state versus account membership and overlapping occupants.
Open record Smart home · presenceSmart-home presence and geofence keeps disconnecting or working intermittently
Intermittent behavior is diagnosed by the trigger—movement, heat, load, sleep, distance or time—not by repeating broad resets. This record isolates smart-home presence and geofence through phone permission/background state versus account membership and overlapping occupants.
Open record Smart home · presenceSmart-home presence and geofence stopped working after an update, outage or hardware change
A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates smart-home presence and geofence through phone permission/background state versus account membership and overlapping occupants.
Open recordStructured depth, not empty permutations
Every published record carries a direct answer, scope, ordered fixes, risk notes and sources.
Device and manufacturer hubs share a consistent record system, but each answer carries the relevant controls, fault boundaries, consequences and official support entry point for that platform.
See the publication gate