|

Wyze Sensor Not Reporting to Home Assistant: Overview

ByAlex Turner

A Wyze sensor that stops reporting to Home Assistant is almost never a “dead sensor” problem. It’s usually a protocol mismatch, a stale entity state, or a connection that Home Assistant silently dropped. Here’s how to find which one you’re dealing with.

First: Know Which Integration You’re Actually Using

Wyze sensors don’t speak Zigbee, Z-Wave, Matter, or Thread natively. They use a proprietary protocol that only talks to the Wyze Bridge or Wyze Hub. That means Home Assistant never talks to the sensor directly — it talks to the Wyze cloud (via the Wyze Home Assistant Integration) or to the bridge’s local API (via Wyze Bridge local control).

This distinction matters because the fix is different for each path:

Integration Path How HA Connects Typical Failure Point
Wyze Home Assistant Integration (cloud) Wyze API → Wyze Cloud → Your Account API token expiry, cloud outage, rate limiting
Wyze Bridge local control HA → Bridge on LAN IP change, bridge firmware update, mDNS failure
Wyze app only (no HA integration) N/A — sensor never reaches HA Integration not installed or not configured

The counter-intuitive part: The sensor is probably reporting fine — to Wyze. The problem is almost always that Home Assistant lost its connection to Wyze, not that the sensor lost its connection to the bridge. Check the Wyze app first. If the sensor shows a recent reading there, your hardware is fine and the issue is in the HA integration layer.

Check the Wyze App First (60 Seconds)

Open the Wyze app and look at the sensor’s last reading and battery level.

  • If the app shows a recent timestamp and live data, the sensor, bridge, and Wyze cloud are healthy. The problem is between HA and Wyze.
  • If the app shows “offline” or a stale timestamp, the problem is in the sensor-to-bridge or bridge-to-Wi-Fi path. Fix that first — no HA configuration will help until the sensor reports to Wyze again.

This single check saves you from restarting HA, re-authenticating, and rebuilding automations for a sensor that was never the problem.

Branch point: If the Wyze app shows the sensor online but HA shows it as unavailable, skip straight to the integration fixes below. If the Wyze app shows the sensor offline, jump to the sensor-side section instead. The two paths don’t overlap — trying HA fixes on a sensor that’s offline in Wyze will waste 20 minutes and change nothing.

Ordered Fixes for the HA Side

Work through these in order. Each step is faster than the one after it.

1. Restart the Wyze Integration (Not the Whole System)

In Home Assistant, go to Settings → Devices & Services → Wyze Home Assistant Integration → Configure → Reload. This refreshes the integration’s connection to the Wyze API without restarting HA.

If that doesn’t work, restart HA itself via Settings → System → Restart. A full restart is slower but clears any stuck entity state.

2. Re-authenticate the Wyze Integration

Wyze API tokens expire. If the integration shows an error like `401 Unauthorized` or `Authentication failed`, you need to re-link your account.

In the integration’s configuration page, remove the account and re-add it with your Wyze credentials. This is the most common fix for a sensor that worked for weeks then stopped.

3. Check for Rate Limiting

Wyze’s free API tier throttles requests. If you have many Wyze devices, or if your HA polling interval is set too aggressively, the API can temporarily block your account. The integration logs will show `429 Too Many Requests` or similar.

Fix: reduce the integration’s scan interval (if configurable) or remove Wyze devices you don’t actually use in HA. The Wyze integration polls each device, so fewer devices means fewer API calls.

4. Verify Entity State, Not Just the Device

A sensor can be “connected” in HA but stuck on an old value. Check Settings → Devices & Services → Entities and look at the sensor’s `last_changed` timestamp. If it’s hours or days old, the entity is stale even though the integration shows no errors.

Force a refresh by calling the `homeassistant.update_entity` service on that entity from Developer Tools → Services. If the value updates, the integration is fine and the issue was a missed poll.

Verification step: After applying any fix above, watch the entity’s `last_changed` timestamp for two full reporting intervals. For a motion sensor, that means 5–10 minutes. For a temperature sensor, that means at least one full poll cycle (typically 30–60 seconds). If the timestamp advances, the fix worked. If it stays frozen, move to the next step — don’t assume the restart alone solved it.

If You’re Using Wyze Bridge Local Control

If you’ve set up local control via the Wyze Bridge (using the `wyze_bridge` project or similar), the failure points are different:

  • IP address change: Bridges often get a new DHCP lease. If HA has the old IP cached, it can’t reach the bridge. Set a DHCP reservation in your router for the bridge’s MAC address.
  • Firmware update: Wyze occasionally pushes bridge firmware that breaks local API access. Check the bridge’s firmware version in the Wyze app and compare it to what your local control method supports.
  • mDNS failure: Local control relies on mDNS discovery. If you have VLANs or AP isolation enabled, the bridge and HA may be on different broadcast domains. Put them on the same subnet.

Failure mode to watch for: The most common recurrence pattern with local control is a bridge firmware update that silently breaks the local API while the Wyze app keeps working. The symptom is that HA loses the sensor, but the Wyze app shows everything healthy. If you see this pattern, check the bridge firmware version against the changelog for your local control method before touching any HA configuration. Downgrading bridge firmware is rarely possible, so the practical move is to wait for the local control project to catch up, or fall back to the cloud integration temporarily.

When to Suspect the Sensor Itself

If the Wyze app shows the sensor offline, the issue is in the sensor-to-bridge link. Common causes:

  • Battery: Wyze sensors use CR1632 or CR2450 cells depending on the model. A low battery often causes intermittent reporting before the sensor goes fully offline. Replace the battery and wait 5–10 minutes for the sensor to rejoin.
  • Range: Wyze sensors use a sub-GHz protocol to talk to the bridge, but walls and metal appliances still reduce range. Move the sensor closer to the bridge temporarily to test.
  • Bridge saturation: The Wyze Bridge supports a limited number of devices. If you’ve added many sensors, the bridge may drop older ones. Check the Wyze app’s device list to confirm the sensor is still paired.

One more failure pattern: A sensor that reports fine for months, then starts dropping updates every few days, is usually a battery issue — even if the Wyze app still shows 20–30% remaining. The sub-GHz radio needs more current as the cell degrades, and the sensor will miss wake windows before the battery reads as fully dead. Replace the battery before you suspect the bridge or integration. This is the cheapest fix and the one most people skip.

Expert Tips for Wyze Sensor Reliability in HA

1. Create a watchdog automation that alerts you to stale entities. Use a `template` sensor that compares the Wyze sensor’s `last_updated` timestamp to `now()`. If the difference exceeds your expected reporting interval (e.g., 30 minutes), send a notification. This catches failures within minutes instead of days. Common mistake: relying on HA’s built-in “device offline” indicators, which only trigger when the integration itself fails — not when a single entity goes stale.

2. Use the Wyze integration’s “scan interval” setting deliberately. The default polling interval balances freshness against API rate limits. If you need faster updates, lower the interval for critical sensors — but know that Wyze’s API will throttle you if you go too aggressive. A reasonable floor is 30 seconds; below that, you’ll start seeing 429 errors. Common mistake: setting all sensors to 10-second polls and then wondering why the integration stops working entirely.

3. Keep a spare sensor paired but unassigned. Wyze sensors are inexpensive, and having a known-good spare lets you A/B test quickly. When a sensor stops reporting, swap in the spare. If the spare works, the original sensor is faulty. If the spare also fails, the problem is in the bridge or integration. Common mistake: assuming a sensor is dead and buying a replacement, only to discover the bridge needed a power cycle.

Escalation Signals

Stop troubleshooting and escalate when you see any of these:

  • The Wyze app shows the sensor offline AND a new battery doesn’t fix it within 30 minutes.
  • The HA integration logs show `401` errors even after re-authentication.
  • Multiple Wyze sensors stop reporting at the same time — this points to a bridge or account issue, not individual sensors.
  • The bridge’s LED is off or blinking in a pattern you don’t recognize. Check Wyze’s documentation for LED status meanings before assuming a software fix will help.

Success Check

Your Wyze sensor is fully working when:

  • The Wyze app shows a recent timestamp (within the last 5 minutes for a motion sensor, or within the reporting interval for a temp/humidity sensor).
  • The HA entity’s `last_changed` timestamp updates within your expected interval.
  • Your watchdog automation (if you set one up) stays quiet for 24 hours.

If you’ve gone through all the steps above and the sensor still isn’t reporting, the issue is likely hardware — either the sensor or the bridge. Wyze sensors are inexpensive enough that replacing the sensor is a reasonable next step, but only after you’ve confirmed the bridge is healthy and the integration is authenticated.

<!– cluster-navigation –>

Explore This Topic

Related guides in this cluster: