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've been poking around the Home Hubs screen in the Home app more than usual lately, and with Apple reportedly about to show off its long-delayed home hub, it feels like the right time to ask: what are you all running as your apple homekit hub right now, and what would actually make you switch? My current setup • HomePod mini in the living room acting as the connected hub • Apple TV 4K in the bedroom sitting on standby • Home Assistant running alongside, with my Zigbee network on an SLZB-06M and a handful of sensors exposed to Apple Home through the HomeKit Bridge integration It works well most days. But living with it has shown me exactly where the gaps are. Where my hub setup falls short today • No say in which device is the hub. Apple picks it for you. When my HomePod mini had a Wi-Fi hiccup, remote control and a couple of automations stalled until the Apple TV took over. • Thread is a black box. Both devices are Thread border routers, but the Home app tells me almost nothing about which one my Matter over Thread devices are actually using or how healthy that network is. • No good wall control. I have an old iPad on a kitchen stand, but iPads can't act as a home hub under the newer Home architecture, so it's just a remote with a battery I keep forgetting to charge. • Bridged devices feel second class. My Zigbee sensors show up fine, but there's no glanceable view that pulls everything together in one place. What's been reported about Apple's new hub Nothing is official until Apple announces it, so treat all of this as rumour for now: • A roughly 6 to 7 inch square display • Two versions: a countertop model with a design that reportedly nods to the old iMac G4, and a wall mount version that needs to stay plugged in • A front camera for FaceTime, plus voice and face recognition to show personalised content to whoever walks up • A new Siri AI based operating system with Apple's own apps built in, but no App Store at launch • Price talk in the region of $350 • A new HomePod mini and Apple TV 4K expected alongside it My wishlist • Let me choose the primary hub. Even a simple "prefer this device" toggle would save a lot of head scratching. • Thread border router and Matter controller built in, with real diagnostics. Show me which devices route through what. • Local first. Automations should keep running when the internet drops, full stop. • A wall mount without a dangling cable. Power over Ethernet would be a dream, a tidy in-wall option would be fine. • A proper device dashboard, including Matter and bridged devices, not just Apple widgets. • Privacy controls I can see. Face recognition processed on device and a physical way to kill the camera. • A price that makes sense. If it lands near $350, it has to do a lot more than an Echo Show or Nest Hub to earn a spot on my counter. Over to you • Which device is your HomeKit hub right now: HomePod, HomePod mini, or Apple TV? • Anyone else running Home Assistant or Homebridge alongside Apple Home? How are you bridging things in? • Day one buy, wait for reviews, or skip? • If you could add one feature to Apple's hub, what would it be? Curious to see what everyone's running. Drop your setup below, even if it's just one HomePod mini doing all the heavy lifting. For transparency, I'm on the forum staff team here, but genuinely asking this as someone trying to sort out their own setup!

I picked up the SONOFF Bridge Max (model Bridge-M) to replace an aging gateway, and wanted to share some honest impressions for anyone weighing it as their next Zigbee hub or a way into Matter without a full ecosystem swap. What it actually is Bridge Max is positioned as an all-in-one Matter Bridge and Zigbee gateway. It runs on a SigmaStar SSD2351Q chip paired with an EFR32MG21 for the Zigbee radio, supports both 2.4GHz and 5GHz Wi-Fi plus Ethernet (RJ45), and powers over USB-C at 5V/1A. It's small, just 82x82x28mm, so it tucks away easily near your router or wherever your mesh is centered. Setup and first impressions You can power it up over Wi-Fi through the eWeLink app or just plug in Ethernet for zero-config networking, which I'd recommend if you want the most reliable backbone for your mesh There's a local web interface too, so you can bridge devices over LAN without touching the cloud at all. That's a genuinely useful option if privacy or offline reliability matters to you If you're migrating from a ZBBridge Pro, there's a one-step transfer for devices, scenes, and security settings, which saves you from re-pairing everything. Worth noting it currently only supports migrating from the ZBBridge-P, not the Ultra or an iHost Pairing new Zigbee devices through the app was straightforward. Nothing fancy, just the standard scan-and-join flow Zigbee performance SONOFF rates the Bridge Max for up to 128 Zigbee devices for stable performance, with more technically possible but at some cost to reliability. That's a reasonable ceiling for most home setups, though anyone running a large mesh with dozens of routers and sensors will want to plan around it. One thing worth flagging before you buy: some reviewers have reported devices dropping off if they're more than a couple meters away with obstacles in between. SONOFF's own guidance here is to check each device's RSSI (anything below -65 is a weak signal) and add a Zigbee repeater if you're seeing drops. That's standard mesh advice, but it means this isn't a bridge you can treat as plug-and-forget in a larger or more spread-out home. Budget for a router device or two if your layout has any dead zones. The Matter Bridge piece This is really the headline feature. Bridge Max can take Zigbee, BTHome, and eWeLink devices and expose them to Apple Home, Alexa, Google Home, SmartThings, and Home Assistant through Matter. A couple of practical notes: The web interface is Matter-setup only. You can't control devices directly from it, so day-to-day control still goes through the eWeLink app or whichever Matter platform you bridged into If you're already running Home Assistant, you can skip Matter entirely and sync Zigbee devices over MQTT instead Who this makes sense for Anyone wanting a single box that bridges Zigbee devices into Apple Home or another Matter ecosystem without buying a dedicated Matter hub Anyone upgrading from a ZBBridge Pro who wants a clean, one-step migration Home Assistant users who want the option of both an eWeLink/Matter path and a straight MQTT sync Where it falls short 128 devices is the practical ceiling for stable operation, so larger networks will want a dedicated coordinator instead The local web console is setup-only, not a full control dashboard, which might frustrate anyone expecting to manage devices from it Range with obstacles is a real consideration. Don't expect it to cover a sprawling floor plan without help from routers Buy here: https://zigbeehubs.com/shop/products/sonoff-bridge-max-bridge-m/

When I started moving my heating over to Zigbee, I assumed choosing a thermostat would be the easy part. Pick one with good reviews, pair it, done. It turned out the thermostat itself mattered a lot less than whether it actually matched my heating system and my hub. I ended up returning one before I got it right, so here’s what I learned along the way. Start with your heating system, not the brand This was my first mistake. Not every Zigbee thermostat works with every type of heating, and the categories are pretty different: Central HVAC (24V): your typical furnace or heat pump setup. Most wall thermostats are built for this. Electric baseboard or radiant floor (line voltage): needs a thermostat rated for high voltage. A standard 24V unit will not work here and can be dangerous to wire in. Water radiators: you don’t need a wall thermostat at all. A Zigbee TRV (thermostatic radiator valve) mounts directly on each radiator and gives you room by room control. If you only check one thing before buying, check this. Check for a C-wire A lot of 24V thermostats want constant power through a C-wire. My hallway didn’t have one. Your options if you’re in the same boat: Go with a battery-powered model Use a thermostat that ships with a power extender kit Run a new wire if you’re comfortable doing it (or get an electrician) Make sure your hub actually supports it Zigbee thermostats don’t connect to your router, they join your mesh through a coordinator. I run Home Assistant, and most of the models I looked at work through either Z2M or ZHA, but device support isn’t identical between the two. Before buying, I’d search the Z2M supported devices list or the ZHA quirks for the exact model number. Zigbee 3.0 certified devices generally give you the fewest headaches. Why I went Zigbee instead of Wi-Fi Schedules and automations keep running locally when the internet drops Mains-powered thermostats act as routers, so they actually strengthen the mesh Response to automations felt noticeably quicker than the cloud-based unit I had before One heads up: if your thermostat is battery powered, it’s an end device, not a router. It won’t help your mesh, and it needs a decent router nearby to stay reliable. Worth checking the LQI after pairing. Models worth a look While researching, I found this breakdown of the best zigbee thermostats really useful because it splits recommendations by heating type instead of just ranking everything together. A few that stood out for different setups: Sinope TH1124ZB: for electric baseboard heating, also reports energy usage SONOFF TRV: for radiator systems, works well with Home Assistant Centralite Pearl: a budget-friendly option for standard 24V systems Aqara W100: if you’re already in the Aqara ecosystem Third Reality: simple battery-powered option with a local LCD readout Note that the Stelpro KI, which a lot of older threads recommend for baseboard heaters, has been discontinued, so don’t count on finding it new. My quick checklist before buying Confirm heating type (24V, line voltage, or radiators) Check whether you have a C-wire Look up the exact model in Z2M or ZHA support Decide if you want it acting as a router (mains powered) or not Curious what everyone else is running. Has anyone had trouble getting a thermostat’s setpoint or mode to sync properly in Z2M? That’s the one area where I’ve seen the most inconsistency between models.

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.

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.