You notice that several smart devices show as offline when you wake up. They were online when you went to bed. By morning, they have reconnected on their own. The pattern is consistent enough to feel intentional. If this matches your home, your mesh Wi-Fi system is most likely running a nightly maintenance cycle that briefly takes the network offline, and your smart devices are slow to recover.
The mesh maintenance cycle
Many consumer mesh Wi-Fi systems run nightly maintenance: firmware update checks, channel optimization, mesh topology rebalancing. The maintenance often happens between 2 and 4 AM by default, when household activity is lowest.
During maintenance, the mesh may briefly disconnect (5 to 30 seconds) as it reconfigures. Wi-Fi clients reconnect automatically. Most clients reconnect within seconds. Some IoT devices take much longer or do not reconnect at all without intervention.
Identify if your mesh does this
Check your mesh router’s admin app. Look for a setting called “Auto Channel Optimization”, “Maintenance Window”, “Scheduled Reboot”, or similar.
- Eero: scheduled reboots and channel optimization in the app’s Settings.
- Google Nest Wifi: auto-channel and scheduled maintenance in advanced settings.
- TP-Link Deco: auto-reboot schedule under maintenance.
- Netgear Orbi: automatic firmware updates can include reboots.
- Asus ZenWiFi: maintenance schedule in advanced settings.
Note the configured time. If it matches when your devices go offline, you have your answer.
The IoT slow-reconnect problem
Even brief outages affect IoT devices more than other clients. Reasons:
- IoT devices often use older Wi-Fi chipsets with longer reconnect timers
- Many IoT devices use static DHCP leases that need to be re-validated after a router reboot
- Some IoT devices interpret a brief outage as a sign to enter low-power mode, requiring more activity to wake
While your phone reconnects in seconds, your smart bulbs may take 30 minutes or never reconnect without a power cycle.
Disable the auto-maintenance
The simplest fix: disable or reschedule auto-maintenance.
If your mesh router allows it, change the maintenance window to a time when devices being offline does not matter. 4 AM is bad if your motion sensors trigger important automations. 8 AM may be more acceptable.
If your router does not let you reschedule, disable the auto-maintenance entirely. You will need to manually update firmware periodically.
Use static IPs for IoT
If your IoT devices have DHCP-assigned IPs that change after router reboot, set static IPs (DHCP reservations) in your router. With static IPs, the device’s IP does not change after reboot, and reconnection is faster.
Most consumer routers support DHCP reservations: identify the device’s MAC address, assign a permanent IP. Reboot the device once to apply.
Separate IoT to a different SSID
If your main network needs auto-maintenance for performance but your IoT network needs stability, separate them.
- Main network on 5 GHz, auto-channel enabled
- IoT network on 2.4 GHz, fixed channel, no auto-maintenance
The IoT network does not need the optimization. The main network gets the benefit without disrupting your devices.
The DNS lookup pause
If your DNS resolver changes during maintenance (some routers rotate DNS), IoT devices may briefly fail to resolve their cloud endpoints. This causes apparent device-cloud disconnects even when the local network is healthy.
Use a stable external DNS (1.1.1.1 or 8.8.8.8) configured on your router rather than the ISP-provided DNS that may rotate.
The DHCP pool exhaustion
If your DHCP pool is small (default in many routers is 100 addresses), and you have many devices that come and go, the pool can exhaust. New connection attempts get no IP.
Increase the DHCP pool size in your router. 200 addresses is reasonable for a typical smart home.
The channel change cascade
Auto-channel optimization changes Wi-Fi channels based on observed interference. If your IoT devices were on channel 6 and the router moves to channel 11, IoT devices may not handle the channel change gracefully. They drop and need to find the new channel.
Lock the Wi-Fi channel manually. Auto-channel often picks well at setup time and rarely needs to change after.
Mesh node sync issues
If your mesh has multiple nodes, they sync configuration periodically. During sync, a node may briefly drop. Clients on that node drop with it.
Sync schedules are often not user-configurable. The fix is to ensure your IoT devices have good fallback connectivity to another mesh node.
The router reboot schedule fix
If you have a scheduled router reboot (some users do this as a stability measure), schedule it when you can tolerate downtime.
Friday at 3 AM may be the wrong time if your morning routine is critical. Schedule for a midday window when you are awake to verify recovery.
Add reconnect logic on IoT devices
Some IoT devices have reconnect timer configurations. If your devices allow it, set an aggressive reconnect schedule (every 30 seconds when offline). This recovers faster after brief outages.
Few consumer IoT devices expose this. For those that do, it makes a noticeable difference.
The 2.4 GHz channel optimization specifically
The 2.4 GHz band has only 3 non-overlapping channels (1, 6, 11). If your router is in a dense Wi-Fi environment (apartment building), auto-channel can flip between these aggressively.
Lock 2.4 GHz to a specific channel. Picking the least-congested one once and sticking with it is usually fine even if it is technically not optimal at every moment.
Monitor with a uptime tool
If you want to confirm the pattern, set up an uptime monitor: a script or smart home automation that pings each device every minute and logs when they go offline.
After a week of data, you can see the pattern clearly. If offline events cluster at 2 AM every night, the mesh maintenance is confirmed.
When devices simply do not recover
Some IoT devices have firmware that does not recover from network outages. They go offline and stay offline until manually power-cycled.
For these, the only fix is to put them on a smart plug schedule that power-cycles them daily. The smart plug is on a different network (your main one) and survives the maintenance, then power-cycles the IoT device, which then reconnects cleanly.
This is an ugly workaround for a fundamental device firmware bug, but it works.
The mesh-friendly device threshold
Mesh routers handle a few dozen devices well. Beyond about sixty connected devices, the mesh management overhead grows and brief disconnections become more common during topology rebalancing. Most consumer mesh systems do not advertise this threshold.
If you have many smart devices and your mesh keeps dropping them at maintenance time, the answer might be a more capable router rather than tuning the existing one. The wider topic of network capacity for IoT-heavy homes is in our dedicated IoT network guide.
