You open the smart home app. A device shows offline. You tap it anyway. It responds normally. You toggle the light, the light toggles. The status updates to online. A few hours later, it shows offline again. The pattern repeats. The device is clearly working, but the app keeps thinking it is not.
How online status is determined
Each ecosystem decides a device is online based on heartbeat signals. The device sends a periodic message to the hub or cloud (“I am here, I am alive”). The system marks the device offline if it has not received a heartbeat within a configured window.
Different protocols have different heartbeat patterns:
- Zigbee mains-powered: sends heartbeats every few minutes
- Zigbee battery: sends heartbeats rarely (every hour or more) to save battery
- Z-Wave: heartbeats every 15-60 minutes depending on device class
- Wi-Fi devices: heartbeats via TCP keepalive or application-level pings
- Matter: subscription-based, with timeouts
If the heartbeat interval is longer than the offline timeout, the device appears offline even when healthy.
The battery sensor case
The most common false-offline case: battery-powered Zigbee sensors. The sensor reports every hour to save battery. The hub’s offline timeout is 30 minutes. Between heartbeats, the sensor appears offline. When it sends its hourly heartbeat, it appears online again.
Fix: extend the offline timeout in the hub. For battery sensors, 2 hours is appropriate. see our Aqara sensor guide for the detail on this for specific brands.
The hub-side cache issue
Sometimes the device sends heartbeats correctly but the hub’s status cache is stale. The hub knows the device is online but the app shows it as offline because the app pulled stale data.
Force-quit the app and reopen. The fresh app load pulls current data. If the device now shows online, the cache was stale.
The cloud delay
Cloud-based status (Alexa, Google Home) lags behind the hub’s local status by 30 seconds to several minutes. A device that just went online may still show offline in the cloud-aware app even though the hub knows it is online.
Wait 5 minutes after a connectivity event before judging cloud status.
The MAC address change
If your router uses MAC randomization (default on iOS 14+ and Android 10+) or your Wi-Fi devices change MACs for any reason, the hub’s identification of devices can drift. The hub sees a new MAC and thinks the old MAC is offline.
For IoT devices on Wi-Fi, disable MAC randomization. For your home network specifically. On iPhone: Settings, Wi-Fi, tap the i next to your network, Private Wi-Fi Address off.
The intermittent network issue
If your Wi-Fi is weak where the device is located, the device may be marginally connected. It works for short periods, drops, reconnects. The status oscillates.
Check the device’s signal strength in the manufacturer app if available. If signal is consistently weak (RSSI worse than -75 dBm), improve the Wi-Fi coverage in that area.
The Zigbee mesh weakness
If your Zigbee device routes through a weak path, its messages may arrive late or not at all. The hub may flag it offline based on missed heartbeats even though the device itself is working.
Improve the mesh routing. Add a Zigbee router (smart plug, mains-powered bulb) between the weak device and the hub.
The hub firmware bug
Some hub firmware versions have known false-offline issues. Check release notes and community forums for the specific hub model and firmware version.
Updates often fix these issues. If you are on an older firmware, update.
The two-cloud sync issue
If your device is integrated through a manufacturer cloud to a voice ecosystem (Hue cloud to Alexa), and the manufacturer cloud thinks the device is online but the voice ecosystem thinks it is offline, the integration sync is the issue.
Refresh by saying “Alexa, discover my devices” or by toggling the integration in the voice ecosystem’s settings.
The device that genuinely disconnects briefly
Some devices disconnect briefly during routine internal operations. A smart camera switching from streaming to standby may briefly go offline from the network’s perspective. A smart thermostat doing a Wi-Fi reassociation may drop for 30 seconds.
These brief disconnects are technically correct (the device is offline for those seconds). The annoyance is that the status flapping is visible to you.
Some hubs allow status smoothing: only show offline if disconnected for more than X minutes. Enable if available.
The status check by polling versus push
Some integrations poll the device or the manufacturer cloud periodically to check status. Polls happen at fixed intervals (5 minutes, 15 minutes). Between polls, status changes are not seen.
If your device changed connection state in the last 5 minutes, the integration may not know yet. Wait for the next poll.
The accept and ignore approach
For devices that consistently false-offline but actually work, the practical answer is to ignore the offline status. The device still responds. Your automations that target the device still execute. The visual status is wrong but harmless.
You can hide the device’s offline alerts in the app’s notification settings if they are annoying.
When the offline status affects automations
If your automation has a condition like “only fire if device is online”, false-offline status breaks the automation. The device’s reported status is offline, the condition fails, the automation does not fire.
Remove the “is online” condition. Trust that the device will receive the command if it is reachable. The downside: if the device is genuinely offline, the action is silently lost. The upside: false-offline does not block legitimate automations.
The hardware actually failing case
Some “false offline” is actually the device being on its way to dying. Intermittent disconnects can be a sign of:
- Battery low (for battery devices) before it is detected by the battery indicator
- Failing Wi-Fi chipset
- Power supply issues
If a device that was reliable for years starts false-offline frequently, the device may genuinely be failing. Replace if available.
The hub-vs-app source of truth
When a device shows offline in one app but online in another, trust the hub or manufacturer app. Voice ecosystem apps cache aggressively and their status can lag by several minutes. If the Hue app says the bulb is online and the Alexa app says it is offline, the bulb is online.
This rule saves time when diagnosing. Always verify in the most-local app before troubleshooting the device. The wider topic of state divergence is in our device status guide.
