Smarthome Forum — Smart Home Community for Matter, Zigbee & HomeKit

One of the most common frustrations in the Home Assistant community right now: Zigbee devices that pair fine, work for a day or two, then drop off and show as unavailable, sometimes coming back on their own, sometimes not.
The generic answer you'll find everywhere is "improve your mesh." That's not wrong, but it's not useful on its own. Here's what's actually worth checking, in order:

1. Coordinator placement first, mesh second
   The coordinator is the root of the entire Zigbee mesh. If it's plugged directly into a USB port on your Home Assistant machine, USB 3.0 interference is a likely culprit. It broadcasts in the 2.4GHz range and drowns out Zigbee signals. Fix: use a USB 2.0 extension cable (1–2 metres) to move the coordinator away from the machine. This alone solves the problem for a large number of people.

2. Powered devices vs. battery devices
   Battery-powered devices (sensors, buttons) are end devices — they don't route traffic. Only mains-powered devices (plugs, bulbs) act as routers and extend your mesh. If most of your devices are battery-powered, your mesh has almost no routing capacity. Add at least 2–3 mains-powered devices within range of the coordinator before assuming anything else is broken.

3. Channel conflicts with Wi-Fi
   Zigbee and 2.4GHz Wi-Fi share spectrum. Zigbee channels 11–13 overlap heavily with Wi-Fi channel 1; Zigbee channels 25–26 overlap with Wi-Fi channel 11. If you haven't set your Zigbee channel deliberately, check what your Wi-Fi is using and pick a Zigbee channel that doesn't overlap. Zigbee channel 15, 20, or 25 are usually the safest depending on your Wi-Fi setup.

4. ZHA vs. Zigbee2MQTT coordinator handling
   Both ZHA and Zigbee2MQTT handle coordinator recovery differently after a Home Assistant restart or power cut. If devices drop specifically after HA restarts, check whether your coordinator firmware is current — outdated firmware on Sonoff Zigbee 3.0 USB dongles in particular is a known cause of post-restart drops.

5. Check LQI before assuming range
   In Zigbee2MQTT, go to the map view and look at the LQI (Link Quality Indicator) values on the connections to your dropping devices. Anything below 50 is weak; below 20 is effectively broken. This tells you whether it's a range/routing problem or something else entirely.

What coordinator are you running, and are the drops happening on specific device types or randomly across the mesh? Drop your setup below, happy to help diagnose.

I've been going through everything Apple announced for the Home app at WWDC, and the camera changes are the most interesting thing HomeKit has done in years. But I want to argue about the part nobody's really pinning down: does this actually match the paid cloud tiers, or just look like it does?

What's actually coming

Confirmed for the fall releases (iOS 27 / tvOS 27 / HomePod 27):

• AI-written summaries — instead of "motion detected," you get "a person walked up to the door" or "a dog was in the yard." Toggleable per camera.
• Cross-camera event grouping driveway cam + doorbell cam get stitched into one event with one summary, automatically. No manual linking.
• Rolling notifications — related alerts collapse into a single notification that updates in real time instead of blowing up your lock screen.
• Searchable footage — type "package delivery" and it jumps to the clip instead of you scrubbing a 3-hour timeline.
• Long-press previews + 4K recording (4K doesn't even need Apple Intelligence).

On paper, that's feature parity with Nest Aware and Ring Protect's "smart" tiers.

Here's where I want to push back on the hype

Two things I keep seeing repeated that aren't quite right:

1. "It's all local, no cloud." Not exactly. The AI runs through your home hub (Apple TV or HomePod), not purely on your phone and HomeKit Secure Video still needs an iCloud+ subscription. So it's "on your hardware" but it is not subscription-free. You're still paying Apple monthly; the money just goes to iCloud instead of Ring.

2. Nobody's tested the accuracy yet. These features ship in the fall — everything floating around right now is announcement footage, not real-world review. Google shipped near-identical AI summaries last year and raised prices, and reviewers still griped about wrong summaries. Apple gets no free pass here until people actually run it.

The actual debate

So the real question isn't "are these cool" (they are). It's:

If HomeKit Secure Video now does named people, package detection, multi-cam event stitching, and natural-language search all bundled into an iCloud+ plan you probably already pay for what's left justifying a separate Ring or Nest subscription?

Counter-argument I keep landing on: the iCloud+ camera limits are stingy (50GB = one camera, 200GB = five), and Nest/Ring still win on hardware range and battery cameras.

Where do you land? Specifically:

• Anyone in the beta actually seeing the AI summaries fire yet? How accurate?
• Is the iCloud+ per-tier camera cap a dealbreaker vs. a flat Nest Aware plan?
• Does "processed on my own Apple TV" actually matter to you privacy-wise, or is that overrated when the footage is in iCloud anyway?