All smart home troubleshooting and repair guides
If your Shelly relay repeatedly drops from Wi‑Fi or your smart home platform, the fix usually involves stabilizing its power supply, switching to a 2.4 GHz network exclusively, or updating its firmware. Below you’ll find a diagnostic checklist, then targeted fixes for each cause – backed by real behavior you can observe. Start With a Quick…
If your Shelly smart relay, switch, or sensor refuses to pair with the Shelly Smart Control app (or a third‑party platform), the fix is almost always tied to Wi‑Fi band selection, app‑side timeout, or a stale device state. This guide walks you through the exact checks and steps that resolve the vast majority of “won’t…
If your Shelly device shows “Updating…” in the app for more than 10–15 minutes, a weak or unstable 2.4 GHz Wi‑Fi connection is the most likely suspect. Shelly relays and sensors do not support 5 GHz networks, and a poor signal or crowded channel will stall the OTA process. Before assuming the device is bricked,…
If your Sonoff device drops off the network repeatedly, the root cause is almost always weak 2.4 GHz Wi‑Fi, a borderline power supply, or a firmware quirk that kills the connection after a few hours. Below is a repair flow that starts with the quickest checks and moves into deeper fixes. Pay attention to the branch…
If your Sonoff device refuses to pair with the eWeLink app or your smart home platform, the issue is almost always one of three things: the device is stuck in an incomplete pairing state, your phone is on the wrong Wi‑Fi network, or the router is blocking the 2.4 GHz connection Sonoff needs. Let’s rule out…
If your Sonoff smart switch or plug is stuck mid‑update—showing a solid red light, flashing blue light that never stops, or the eWeLink app reports “Updating…” for hours—the most common cause is an unstable Wi‑Fi connection or an interrupted power supply during the flash process. Before you assume the device is bricked, start with these…
The short answer: your Zigbee device is often offline because it’s out of range of the mesh, blocked by materials like metal or concrete, hit by Wi‑Fi interference on the same 2.4 GHz band, or its battery is dead. But before you dig into settings, try the most likely fix in 30 seconds. First, Try This…
Most pairing failures are not a hardware defect. The problem is usually distance, radio interference, or a trivial setting that changed without you noticing. The most overlooked cause: a silent Zigbee channel shift triggered by a recent firmware update, a new Wi‑Fi router, or even plugging in a Matter‑over‑Thread device. Below are the quick triage…
A Z-Wave device showing as offline usually means it has lost communication with the hub due to range limits, a dead battery, a failed node in the mesh, or signal interference. Before you factory reset anything, start with the simplest checks—your hub and the device itself—because most offline issues resolve without re-pairing. Start With These…
Before you reach for the paperclip to factory reset, stop. Most Z-Wave pairing failures aren’t hardware defects. The device is still holding a Node ID from a previous hub, or the S2 security handshake times out due to radio interference or weak power. The counter-intuitive fix: force exclusion first, factory reset last. Here’s the exact…
