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

If you've ever opened Home Assistant and seen half your Zigbee devices marked unavailable, you know how frustrating it is. I went through this myself a few months back, losing motion sensors and plugs at random, sometimes for hours at a time. Here's what I learned tracking it down, in case it saves someone else the same headache. Start with the network map, not the device My first instinct was to reboot the offline device. That almost never fixed anything. What actually helped was pulling up the network map in Zigbee2MQTT (or the visualization in ZHA) and looking at how that device was routing. Devices that had lost their route to a router, or were trying to hop through a router that had itself gone flaky, were the ones dropping out. The map told me where the actual problem was instead of me guessing device by device. Battery devices are not the same problem as mains-powered ones I used to lump all my offline devices into one bucket, but battery sensors and mains-powered plugs fail for completely different reasons. Battery devices sleep most of the time and only report in on a schedule or when triggered, so a sensor that looks offline might just be low on battery or waiting for its next check-in. Mains-powered devices, on the other hand, are always-on routers for the mesh, so when one of those goes offline it can take a chunk of your network down with it since other devices were relying on it to relay. Interference was my actual culprit In my case, the real issue was my Zigbee coordinator sitting a few inches from a USB 3.0 hub. USB 3.0 is a known noise source in the 2.4GHz range, and it was quietly wrecking my signal without any obvious symptom other than random dropouts. Moving the coordinator onto a USB extension cable, away from the hub and my router, cleared up most of my problems immediately. Channel congestion sneaks up on you I also checked my Zigbee channel against my Wi-Fi channels, since overlap between the two causes intermittent packet loss that looks exactly like random offline devices. Switching to a Zigbee channel that didn't overlap with my 2.4GHz Wi-Fi channel helped stabilize the last few stragglers. Give the mesh time before you panic After making any change, whether it's adding a router device, moving the coordinator, or switching channels, I had to resist the urge to judge results immediately. The mesh needs time to rebuild its routes, sometimes several hours. I made the mistake of assuming a fix didn't work after ten minutes, when really the network just hadn't finished reorganizing yet. What actually fixed it for me, in order Moved my coordinator away from USB 3.0 interference Added two router devices in the areas where I was seeing the most dropouts Switched to a less congested Zigbee channel Let the mesh sit overnight before checking again Between those four changes, my offline device count went from a near-daily annoyance to essentially zero. If you're chasing the same problem, I'd start with the network map and the coordinator placement before touching anything else. Those two things caused the majority of my issues.

I see this question pop up a lot, so figured I'd break down how I think about it after running both ZHA and Z2M on different setups. Zigbee itself Zigbee isn't software you choose, it's the wireless protocol your devices speak. Every bulb, sensor, and plug that says "Zigbee" on the box is talking the same low-power mesh protocol regardless of what's running on your Home Assistant server. The protocol handles the radio layer, pairing, and mesh routing between devices. What you do choose is the software that sits between your Zigbee coordinator (the USB stick or gateway) and Home Assistant, translating Zigbee traffic into something HA understands. That's where ZHA and Z2M come in. ZHA (Zigbee Home Automation) ZHA is Home Assistant's built-in integration. No separate app, no extra container, no MQTT broker to manage. You plug in a coordinator, add the integration, and pair devices straight from the HA UI. What I like about it: Setup is genuinely the fastest of the two. Fewer moving parts means fewer things to misconfigure. Device support is handled through quirks, community-contributed device profiles that patch weird or non-standard implementations. Everything lives inside HA, so there's no second web UI to check when something's not reporting. Where it falls short: Network visibility is limited. There's no built-in map showing which devices are routing through which repeaters, so diagnosing mesh problems is more guesswork. Some devices get supported later than they do on Z2M, since the quirks system depends on community contributions catching up. Zigbee2MQTT (Z2M) Z2M runs as a separate add-on (or standalone service) and talks to HA over MQTT rather than being built into HA directly. What I like about it: The network map in the Z2M frontend is genuinely useful. You can see LQI (link quality) between every device and repeater, which makes tracking down a flaky sensor way faster than guessing. Broader and often faster device support, especially for newer or less common devices. More granular control over channel settings, reporting intervals, and per-device configuration. Where it falls short: You're now running MQTT as a dependency, which is one more thing that can go wrong or need troubleshooting. Slightly more setup overhead upfront, especially if you've never touched an MQTT broker before. So which one do you pick? If you want the simplest possible setup and don't care about deep network diagnostics, ZHA is the easier starting point. If you've got a larger mesh, want to actually see what's happening between your coordinator and your devices, or you're chasing down flaky connections, Z2M's visibility is worth the extra setup step. I run Z2M mainly because I lean on the network map constantly when troubleshooting range issues, but I know plenty of people happily running dozens of devices on ZHA without ever needing that level of detail. Neither one is "wrong," they're just optimized for different priorities. Curious what others are running and why you landed where you did.

Been meaning to write this up because I see the same question pop up every few weeks: "my Zigbee devices near the edge of the house keep going unresponsive, but everything close to the coordinator is fine." I ran into this myself with a contact sensor on my back gate, about 40ft and two walls from the coordinator. It would work fine for a day or two, then just drop off and need re-pairing. Here's what I learned digging into it. The mesh isn't as smart as people assume Zigbee mesh networking sounds great on paper: routers repeat the signal, end devices hop through them to reach the coordinator. But it only works if you actually have routers in the right spots. A lot of people don't realize: Battery-powered devices (sensors, most buttons) are almost always "end devices," not routers. They don't repeat signal for anyone else. Only mains-powered devices (smart plugs, some bulbs, in-wall switches) act as routers. If your edge-of-house devices are all battery sensors with no mains-powered Zigbee device nearby, there's nothing to relay them. They're relying on a direct, weak hop straight back to the coordinator. What actually fixed it for me I added a Zigbee smart plug about halfway between the coordinator and the back gate, specifically as a repeater. Within a day the contact sensor's LQI/RSSI reading jumped noticeably and it hasn't dropped since. A few other things worth checking if you're in this situation: Route table health: some coordinators/hubs let you see routing paths in their diagnostics. If a device is hopping through 3+ routers, that's a sign your mesh has gaps. Channel interference: Zigbee channels 15, 20, 25 overlap with 2.4GHz Wi-Fi. If your router's on a busy channel, that can look like a range problem when it's actually noise. Firmware: some manufacturers have quietly improved mesh healing behavior in updates. The takeaway Zigbee range problems are usually a topology problem, not a raw distance problem. A $15 to $20 mains-powered plug positioned as a repeater will usually do more for your edge devices than moving the coordinator around. Curious if others have run into this. Did adding routers fix it for you, or was it something else (channel, firmware, specific brand)?

I've been running Zigbee2MQTT for a while now, and after a few rounds of drop-outs and slow-to-respond devices, I went through and tightened things up properly. Sharing what actually made a difference, in case it saves someone else the trial and error. Use the built-in Network Map This is the single most useful tool Z2M gives you and a lot of people never open it. In the frontend, go to the Network Map view and generate a fresh map. It shows every device, how it's connecting, and the link quality (LQI) between hops. Anything showing LQI under 50 is a weak link worth fixing. I found two sensors on the far side of my house limping along through a single weak hop, and that's exactly where I focused first. Don't lean on smart bulbs as your main routers Bulbs do act as Zigbee routers, but they're not always reliable ones. Some go into low power states or firmware behaviors that make them flaky relay points. I swapped a few "router" duties over to smart plugs instead, which stay powered and active consistently. Plugs are cheap and make solid dedicated routers. Pick your channel deliberately, not by default Zigbee and Wi-Fi both live in the 2.4 GHz band, so channel overlap is a real problem. Z2M lets you set the channel in the configuration, and it's worth checking what Wi-Fi channels your router is using first, then picking a Zigbee channel that avoids overlapping. Channels 15, 20, and 25 tend to have the least overlap with common Wi-Fi channel choices, but check your own network before assuming. Coordinator placement and cabling matter more than people expect Keep the coordinator central in the house, elevated off the floor, and away from USB 3.0 ports or hubs if you can, since USB 3.0 is a known source of 2.4 GHz interference. A short shielded USB extension cable to get the coordinator away from the router or PC chassis helps more than it seems like it should. Add routers before you need them, not after The mesh gets more reliable the more routers it has, roughly one router per room or every 10 to 15 meters is a reasonable rule of thumb. Pair routers first, then pair your end devices near their final location so they associate with the nearest strong router from the start, rather than pairing everything near the coordinator and hoping it re-routes later. Keep an eye on firmware, but read release notes first Z2M has moved fast with the 2.x releases, and some changes (legacy API removal, action sensor defaults) can break automations that depended on old behavior. Before updating, skim the release notes so you're not caught off guard if entity names or payload formats shift. Rebuild the mesh after a big change If you've added several routers or repositioned the coordinator, give it real time, sometimes a day or more, for the mesh to reorganize itself and settle into new routes. Don't judge the result after five minutes. None of this was a single fix. It was going through the network map, cleaning up weak links one at a time, and being deliberate about router placement instead of just adding devices as I bought them. Happy to answer questions if anyone's fighting a flaky mesh right now.

I'd been running a handful of smart plugs and bulbs through their own apps for a while, and honestly, it was a mess. Four different apps, four different accounts, and none of them talked to each other. That's what finally pushed me to set up Zigbee with Home Assistant. Here's how the first weekend went, mistakes included. Picking a Coordinator The first decision I had to make was which Zigbee coordinator to buy. There are a lot of options, and it's easy to get stuck comparing spec sheets forever. I ended up going with a USB coordinator based on the Silicon Labs chipset, mainly because it had strong community support and good documentation for flashing custom firmware later on if I needed it. If you're just starting out, my advice is to not overthink this step. Any well-supported coordinator will get you running. You can always upgrade later once you know what you actually need. Choosing Between ZHA and Zigbee2MQTT This was the decision that took me the longest. ZHA is built into Home Assistant, so it's the path of least resistance. Zigbee2MQTT (Z2M) requires a bit more setup since it runs as a separate add-on and talks to Home Assistant over MQTT, but it has broader device support and more detailed configuration options. I went with Z2M in the end. I have a mix of devices from different brands, and I wanted the flexibility to tweak things like reporting intervals and device-specific settings that ZHA didn't expose at the time. If your setup is simpler, ZHA is a perfectly reasonable choice and it's less to manage. Pairing My First Devices Once the coordinator was plugged in and Z2M was running, I started pairing devices one at a time. A tip that saved me a lot of frustration: pair devices starting closest to the coordinator and work your way outward. This helps build a stronger mesh from the start, since router-capable devices near the coordinator extend range for devices further away. My first pair was a smart plug, since those tend to be reliable Zigbee routers. After that I added a couple of bulbs and a door sensor. Watching them show up in the Z2M interface for the first time felt like a small win. Where I Ran Into Trouble Not everything went smoothly. A couple of lessons from that first weekend: I initially placed my coordinator right next to my Wi-Fi router, which caused interference. Moving it just a few feet away, and away from USB 3.0 ports and cables, made pairing and stability noticeably better. I paired too many devices too quickly without giving the mesh time to settle. Zigbee networks take a bit of time to build stable routes between devices, so pairing everything in one sitting and expecting it to behave perfectly right away wasn't realistic. I didn't check firmware versions on my devices before pairing. A couple of older bulbs needed updates before they'd report data reliably. What I'd Tell Someone Starting Today Start small. Pair a handful of devices, let the network settle for a day or two, then keep expanding. Pay attention to coordinator placement early, since it saves you troubleshooting later. And don't be afraid to spend a bit of time deciding between ZHA and Z2M, since switching later is possible but adds friction you can avoid by choosing carefully up front. That first weekend of setup is what got me hooked on the smart home rabbit hole. Happy to answer questions if anyone's just getting started and hitting similar snags

Most guides on switching from ZHA to Zigbee2MQTT assume you're using a USB coordinator and tell you to re-pair every device from scratch. If you're running a SLZB-06M ethernet gateway, there's a lower-effort path that a few people in the Home Assistant community forum have pieced together, though it's still light on detail, so treat this as a starting point rather than a guaranteed walkthrough. Why the naive approach fails Just deleting the ZHA integration and spinning up Z2M on the same gateway doesn't work by default. Your Zigbee devices are bound to a specific PAN ID and extended PAN ID. If Z2M starts a fresh network with different IDs, your devices simply won't recognize the new controller and every one of them has to be factory reset and re-joined. The workaround Update your SLZB-06M firmware first. Firmware 2.7.1 and later added the ability for the gateway to associate with more than one client at once, which is what makes this approach possible at all. Back up your ZHA coordinator configuration before touching anything. This is your safety net if the migration goes sideways. Copy your ZHA network settings into Z2M. Instead of letting Z2M generate a new network, configure it with the same PAN ID, extended PAN ID, and network key that ZHA is already using. This is the step that avoids the re-pairing problem entirely. Export your ZHA device list and use it to build your Z2M device configuration. This saves you from manually re-entering every device. Run "interview" on each device from the Z2M UI. This is what lets Z2M actually recognize and populate details for devices it didn't originally pair. Once you've confirmed everything shows up correctly in Z2M, disable the ZHA integration. Running both at once will give you duplicate entities for every device. A safer alternative if you don't want to risk your live network If you'd rather not experiment directly on your working setup, one option is to temporarily move ZHA onto a cheaper secondary coordinator, freeing up the SLZB-06M to become your fresh Z2M coordinator. You can then repurpose the original USB coordinator as a dedicated Zigbee router afterward instead of letting it go to waste. A word of caution This method hasn't been fully documented step by step by anyone who's actually done it end to end. The one person who described it didn't go into detail on how the "interview" step behaves in practice, so budget time for trial and error, and definitely don't skip the backup step. Has anyone here actually completed this migration on a SLZB-06M? Curious what the interview step looked like in practice and whether all device types carried over cleanly.

My Zigbee network used to have a dead zone at the far end of the house, a couple of sensors would drop out constantly, and the garage door sensor was basically useless. After a few weekends of tinkering, I finally got full, reliable coverage everywhere. Here's what actually made the difference, combining a few different fixes rather than one silver bullet. Added more mains-powered routers Zigbee is a mesh network, and battery devices (like most sensors) don't repeat signal, only mains-powered ones do. I added a couple of cheap plug-in smart outlets in the hallway and garage specifically to act as routers. That alone filled in a lot of the gaps. Repositioned the coordinator My hub was originally tucked inside a media cabinet next to the router and a bunch of other electronics. Moving it out into the open, up on a shelf and away from Wi-Fi gear, made a noticeable difference. Zigbee and Wi-Fi both use the 2.4GHz band, so proximity to your router can cause real interference. Picked a clean Zigbee channel I checked which Wi-Fi channels my router was using and picked a Zigbee channel (in the Zigbee 2.4GHz range) that overlapped as little as possible. Less contention means fewer dropped packets. Let the mesh rebuild After making these changes, I gave the network a day or two to let devices re-route through the new mesh paths rather than force-repairing everything at once. Route optimization isn't instant. The combination of these fixes took my Zigbee network from "flaky at the edges" to rock solid, including the garage sensor that used to fail constantly. If you're dealing with a dead zone, I'd start with router placement (#1) since it usually gives the biggest bang for the buck.

Zigbee is one of the most reliable protocols for smart home devices, but a lot of people run into flaky connections or dropped devices because of a few common mistakes. Here's how to get the most out of it: Build a strong mesh network Zigbee is a mesh protocol — mains-powered devices (smart plugs, bulbs, in-wall switches) act as routers and extend your network. Battery devices (sensors, buttons) don't. Aim for a good spread of mains-powered devices throughout your home so signal has multiple paths to travel. Avoid Wi-Fi channel overlap Zigbee operates in the 2.4GHz band, same as Wi-Fi. If your Zigbee network feels unstable, set your Wi-Fi router to channels 1, 6, or 11 and pick a Zigbee channel that doesn't overlap (e.g. channel 25 or 26). Don't overload a single hub Most Zigbee coordinators can handle 50-200 devices depending on hardware, but performance degrades if you cram too many onto one hub without any routers. Spread devices out and let mains-powered ones do their job as repeaters. Keep your coordinator central and elevated Place your Zigbee hub/coordinator in a central location, elevated off the floor, and away from metal objects, mirrors, or thick concrete walls that can block signal. Update firmware regularly Zigbee firmware updates often fix bugs related to pairing, range, and interference. Check your hub manufacturer's app periodically for updates. Use pairing correctly Always factory reset a device before pairing it to a new network, and pair devices one at a time and close to the coordinator initially — you can move them to their final location afterward once they've joined the mesh. Group similar devices logically Use rooms/zones and groups in your hub software so scenes and automations are easier to manage and troubleshoot later. Following these basics will get you a Zigbee network that stays online and responsive instead of one that needs constant re-pairing. Happy to answer questions if anyone's running into specific issues.

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: 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. 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. 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. 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. 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: "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. 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?

This is an automated test reply from the Knovik MCP.

This topic was created by the Knovik MCP integration test suite and will be deleted immediately.

This topic was created by the Knovik MCP integration test suite and will be deleted immediately.

Testing lock/unlock via MCP.

Testing pin/unpin via MCP.

This is an automated test reply from the Knovik MCP.

This topic was created by the Knovik MCP integration test suite and will be deleted immediately.

The shift from traditional television to Smart TVs is one of the clearest examples of how consumer technology has evolved into a fully connected ecosystem. What used to be a passive viewing device has now become an interactive entertainment hub, blending streaming, apps, voice control, and smart home integration into a single platform. Traditional TVs were essentially display units. Their function was limited to receiving signals from cable, satellite, or external devices like DVD players and set-top boxes. The user experience was linear and static — you watched what was broadcast at a scheduled time, with very little control beyond channel switching. Smart TVs, on the other hand, represent a completely different philosophy. By integrating operating systems similar to those found in smartphones, they allow users to install applications, access streaming services, browse the internet, and even control smart home devices. Platforms like Netflix, YouTube, Disney+, and other OTT services have effectively replaced traditional broadcast consumption for many users. One of the most important advantages of Smart TVs is their connectivity. Through Wi-Fi or Ethernet, they become part of a larger digital ecosystem. This enables features such as voice assistants (Google Assistant, Alexa), content recommendations powered by AI, and seamless integration with smartphones and tablets. In many households, the TV is no longer just a screen — it is a control center for the entire smart home environment. Another major difference lies in interactivity. Traditional TVs offered no personalization, while Smart TVs adapt to user behavior. They suggest content based on viewing history, allow multi-user profiles, and support cloud-based synchronization across devices. This creates a much more dynamic and tailored entertainment experience. Interestingly, this evolution of digital platforms is not limited to streaming media. The broader online entertainment industry has followed a similar path of personalization, accessibility, and mobile integration. For example, gaming and entertainment ecosystems such as https://parimatchh.pl reflect how digital services are increasingly designed around user convenience, real-time interaction, and cross-device compatibility. This mirrors the same technological principles driving Smart TV development. Another key development is the rise of streaming devices and TV sticks. Products like Chromecast, Fire TV Stick, and similar solutions have made it possible to turn almost any traditional television into a Smart TV. This has accelerated adoption globally, especially in regions where users prefer upgrading existing hardware rather than purchasing entirely new devices. Looking forward, Smart TVs are expected to become even more integrated with artificial intelligence and smart environments. Features like predictive content delivery, gesture control, and deeper IoT connectivity will likely redefine how people interact with home entertainment systems. TVs may eventually act less like standalone devices and more like intelligent nodes within a fully connected digital home. In conclusion, the transition from traditional to Smart TVs is not just a hardware upgrade — it represents a broader transformation in how media is consumed, personalized, and integrated into daily life.