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

Apple has finally released HomeView, a smart home screen it has been working on for years. It was announced on October 13, 2026. In simple words: it's a small touchscreen that sits on your kitchen counter (or hangs on your wall) and lets you control your whole smart home, make video calls, play music, and more. The big question: is it worth $299? Here's everything you need to know, explained simply. Price and release date Price: $299 in the US Pre-orders: open now Arrives in stores: November 13, 2026 Europe: not available at launch. Apple's new Siri isn't ready in Europe yet, so HomeView has to wait too. What you need to set it up: an iPhone with iOS 27.2 or an iPad with iPadOS 27.2. If your phone can't update to that version, you can't set it up. Two versions to choose from Both cost the same $299. 1. Countertop version The screen sits on a round metal base that also holds the speakers You can tilt the screen to get a better view Colors: Silver, Starlight, Rose Pink, Space Gray The power cable matches the color 2. Wall version Just the screen, no speaker base Hangs flat on your wall Colors: Silver and Space Gray The wall mount is sold separately, so budget extra The screen Size: 7 inches, square shape Sharpness: 1088 × 1088 pixels, sharp enough for photos and video calls Brightness: goes very bright for sunny kitchens, and very dim at night so it won't light up your bedroom True Tone: the colors adjust to match the light in your room, so it's easier on the eyes Smart layout: from across the room, it shows big, simple information like the time or weather. Walk closer and it shows more detail. The brain: chip and Siri It runs on the A18 chip, the same chip used in the iPhone 16. That means it should feel fast. It uses Siri AI, Apple's new, smarter Siri. You can ask it questions, find music, and control your home just by talking. If you start a conversation with Siri on HomeView, you can continue it on your iPhone, iPad, Mac, or Apple Watch. Have you tried the new Siri yet? Better or still frustrating? What it does for your smart home This is the main job of HomeView: being the control center of your home. Control your devices: turn on lights, lock doors, change the thermostat, set timers. Use your voice or tap the screen. Watch your cameras: see up to 9 security cameras at once on one screen Quick device panel: one tap to reach your most-used devices Works as a home hub: a "home hub" is the device that keeps your automations running and lets you control your home when you're away. HomeView can do this for HomeKit and Matter devices. Quick explainer: HomeKit = Apple's smart home system Matter = a newer standard that lets devices from different brands work together Apple also announced its own smart door lock, security cameras, and video doorbell at the same time, clearly built to work with HomeView. Sound, mics, and camera Speakers Both versions have 2 speakers in the screen The countertop version adds a bass speaker in the base for fuller sound Supports Spatial Audio with Dolby Atmos (sound that feels like it surrounds you) It adjusts its sound to fit your room automatically Microphones 4 microphones designed to hear you from across the room Camera 12MP front camera for FaceTime calls Center Stage: the camera follows you as you move, so you stay in the picture while cooking or walking around Safety bonus: HomeView can hear smoke and carbon monoxide alarms and alert you. That's a quietly useful feature, especially if you're not home. Made for the whole family This is the biggest difference from other smart screens. Recognizes up to 6 people by their face Each person gets their own Home Screen with their own apps and widgets Your private info stays private. Your messages and calendar only show up when HomeView sees your face AND your iPhone is nearby and recently unlocked. Both have to match. Shared stuff for everyone: create shared photo albums and music playlists that the whole family (and even guests) can enjoy Apps and everyday use Built-in apps include: Calendar, Reminders, Notes Messages and FaceTime Photos (great as a digital photo frame) Music and Podcasts Find My (find your lost iPhone or AirPods) Other things it can do: Step-by-step recipes, perfect for the kitchen Watch videos from Apple TV and other compatible apps on your iPhone What we still don't know Apple hasn't answered these yet: Is it a Thread border router? (Thread is a fast, low-power way for smart devices to connect. Not confirmed yet.) Will there be third-party apps? No developer tools have been announced, so there's no HomeView App Store for now. How does it work with your HomePod or Apple TV if you already use one as your home hub? When is it coming to Europe? If you find answers to any of these, share them below! And if you get one after November 13, come back and share your setup. Real experiences will help everyone decide.

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'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've been reworking the cameras around my place over the last few weeks, and it made me realise how differently everyone seems to approach this. Picking a homekit camera sounds simple until you actually try it, and then you find there are really three separate routes with very different trade-offs. So I'm curious: which HomeKit cameras are you running, and how did you get them into Apple Home? Here's how I see the three camps, and where I've landed so far: 1. Native HomeKit cameras These are the ones you scan with the Home app and you're done. No extra hardware, no plugins. • Setup takes minutes and they tend to stay paired • Live view, notifications and automations work out of the box • The catch is choice: the list of native models is short, and outdoor and PoE options are thin I started here with an Aqara Camera Hub G2H Pro in the hallway. It has been the least trouble of anything I own, but I ran out of options quickly once I wanted something outside. 2. HomeKit Secure Video (HKSV) models This is where it gets interesting for recording. Footage is analysed locally on your home hub, then stored end to end encrypted in iCloud. • You need a home hub (Apple TV or HomePod) and an iCloud+ plan • The plan tier sets how many cameras can record, so check that before you buy a fifth camera • Recordings don't count against your iCloud storage • Person, pet, vehicle and package detection, plus activity zones, are handled in the Home app What I like is having one timeline in one app. What I don't like is that recording tops out at 1080p even on a higher resolution camera, and clips sometimes take a while to load when I'm away from home. 3. Bridge-based setups (Homebridge, Scrypted, RTSP) This is the route for cameras that were never meant to work with HomeKit. If the camera exposes an RTSP or ONVIF stream, you can usually bring it in. • Opens up far more hardware, including PoE and proper outdoor cameras • Scrypted can add HKSV support to cameras that don't have it natively • Homebridge with a camera plugin works well for live view and motion alerts • The trade-off is that you are now running a server, so updates, codecs and stream settings become your job My outdoor camera is a Reolink E1 Outdoor Pro coming in over RTSP through Scrypted. It took an evening of fiddling with stream settings before it loaded quickly, but it has been steady since. What I'd love to hear from you • Which cameras are you running, and which of the three routes are they on? • If you use HKSV, how reliable are the notifications and the detection? • For the bridge crowd: Homebridge or Scrypted, and what hardware is it running on? • Any camera you regretted buying, and why? • Has anyone mixed all three in one home without it turning into a mess? For transparency, I'm on the forum team here, but I'm asking this one as someone still trying to sort out their own setup.

Hi all, this is a genuine discussion question, not an announcement. Nothing to sell and no links to follow. iOS 27 has been out for a few weeks now, and HomeKit Secure Video got more attention in this release than it has in years. I've read plenty of feature lists, but feature lists don't tell you how it holds up on a real front porch with a real camera. So I'd like to hear from people who are living with it. The redesigned camera experience The Home app now handles recordings differently. Clips it considers important are pulled to the top, and related alerts are bundled into one notification that updates as things happen. Does the new layout make it faster to find the clip you want, or are you scrubbing more than before? Are the "important" clips actually the important ones? Has the notification bundling cut the noise, or have you missed something because of it? 4K cameras The 1080p cap on HomeKit Secure Video is finally gone, as long as the camera supports it. Is anyone actually recording in 4K yet? Which camera, and did it need a firmware update first? Can you see a real difference on faces and number plates, or only when you zoom in? Any impact on your Wi-Fi, upload speed, or how smoothly clips load? Apple Intelligence summaries and natural-language search This is the part I'm most curious about. The Home app can now describe what happened in a clip before you open it, and you can search recordings by typing what you're looking for. How accurate are the summaries? Useful, or confidently wrong? Has natural-language search found things for you that scrolling would not have? What did you search for? Did your iPhone, home hub, or iCloud+ plan stop you from turning any of this on? What I'd love to know Your camera model and home hub (Apple TV or HomePod) The one change you'd keep and the one you'd undo Anything that broke or got worse after updating Short replies are welcome. "Nothing changed for me" is a useful answer too, especially if you can say what setup you're on. Thanks in advance. I'll be reading and replying in the thread.

There's been a lot of discussion lately about what's holding Apple's smart home platform back. The community complaints are surprisingly consistent. Poll options: list itemSiri reliability — "When I yell 'HEY SIRI,' I just want a damn response" list itemCamera support — Most good security cameras don't support HomeKit Secure Video, forcing users to juggle multiple apps list itemHome hub reliability — Hubs failing to consistently serve as home hubs, causing accessories to show "No Response" list itemDevice compatibility — Still too many devices that require workarounds to work with Apple Home list itemAutomation depth — "We haven't seen any new automations. We haven't seen any new conditions. We haven't seen any real new product categories come to HomeKit in a few years" I'm curious which one is the real dealbreaker for people. For me, it's the hub reliability I can work around Siri being dumb, but if the hub itself can't stay connected, nothing else matters. What's yours, and why?

I've integrated about a dozen non-native devices into Apple Home over the past two years, and the honest answer is: it works, but only if you go in with realistic expectations. The core principle is simple: a non-HomeKit device can be added to Apple Home only if it has a supported plugin, integration, API, hub, Matter bridge, or some indirect control method. If the device is completely closed, no API, no third-party control, no plugin, it can't be bridged no matter what software you use. For most people, Homebridge is the starting point. It's an open-source Node.js server that runs locally on your network and presents non-certified devices to the Home app as if they were native accessories. The plugin library is genuinely large Eufy cameras, Xiaomi robot vacuums, Tuya-based smart plugs, Nest thermostats, LIFX bulbs, Broadlink IR blasters, and hundreds more. Here's what nobody tells you before you start: The mDNS problem will eat your afternoon. If you're running Homebridge in Docker with the default bridge network, multicast traffic is silently blocked. iOS never sees the accessory. The Home app shows nothing. No error, no log entry just absence. You need host networking or macvlan. Zigbee and Z-Wave devices need their own hubs. A Raspberry Pi running Homebridge won't magically make Zigbee devices work. They need a Zigbee coordinator (like a Conbee II or Hubitat) or a bridge that speaks their protocol. Once it works, don't touch it. The most common advice from long-term users: "Once it is stable I just don't bother with updates. I have to reboot the system maybe once every six months". Every major iOS update is a gamble. Matter is changing the game slowly. Some newer devices now support Matter natively, which means direct integration without a bridge. But "Matter-compatible" doesn't always mean what you think, especially with Thread devices across multiple ecosystems. My verdict: Homebridge is the path of least resistance for most non-native devices. But go in knowing you're building a small server that needs maintenance, not installing a plug-and-play solution. The community plugins are your lifeline stick to ones with high download counts and recent update dates

I've seen this question come up quite a few times, and the answers online seem to be all over the place. Some people say Nest cameras work with Apple Home, while others say they don't. So, what's the real answer? From what I've found, Nest cameras do not support Apple HomeKit natively. If you buy a Nest Cam or Nest Doorbell today, you won't be able to scan a HomeKit code and have it appeared in the Apple Home app. That said, plenty of people are successfully using Nest cameras with Apple Home by using a bridge or software solution. Some of the most common options are: Starling Home Hub for a simple plug and play experience. Homebridge if you don't mind a bit of setup. Scrypted for users who want advanced camera features and low latency. For those already running one of these solutions: Which method are you using? How reliable has it been? Are live streams fast and responsive? Does two-way audio work well? If you're using HomeKit Secure Video, which Nest camera model are you using? I'm also curious whether anyone has switched between Starling, Homebridge, and Scrypted. Was the change worth it? It seems like the biggest point of confusion is that people assume Matter has solved this problem. From what I understand, Matter still doesn't support security cameras, so a bridge is still required if you want to view Nest cameras inside Apple Home. Find more: How to add Nest cameras with Apple HomeKit I'd love to hear some real-world experiences before recommending one solution over another. Which setup has worked best for you?

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/

I've been researching Yale smart locks recently, and one thing keeps coming up. There seems to be a lot of confusion about which Yale Assure locks actually work with Apple Home. Some people say the Yale Assure Lock supports HomeKit, while others say it doesn't. After digging into it, it looks like both answers can be correct depending on the model. From what I understand: Yale Assure Lock 2 supports Apple Home out of the box through Bluetooth. Yale Assure Lock 2 Plus also supports Apple Home Key, so you can unlock your door with your iPhone or Apple Watch. Older first-generation Yale Assure locks usually need a compatible HomeKit module, such as the Yale iM1 module. If they have a Zigbee or Z-Wave module instead, they won't appear in Apple Home. That seems to be where most of the confusion comes from. Many listings simply say "Yale Assure Lock" without mentioning the generation or included module. For those who own one: Which Yale model are you using? Was pairing with Apple Home straightforward? Have you experienced any connection or reliability issues? If you were buying today, would you choose the Assure Lock 2, the Assure Lock 2 Plus, or a different HomeKit-compatible lock altogether? I think this could be a useful thread for anyone shopping for a Yale lock, especially since older models are still widely available online and can be easy to confuse with the newer versions. I'd love to hear everyone's real-world experiences before I make a decision.

If you're planning to add unsupported smart home devices to Apple Home, one of the first decisions you'll make is whether to build your own Homebridge server or buy a pre-built bridge. Both options let you run Homebridge and connect non-HomeKit devices to Apple Home. The biggest differences are the amount of setup, ongoing maintenance, and overall convenience. This guide explains the pros and cons of each approach so you can decide which one fits your needs. Quick Comparison Feature DIY Homebridge Pre-Built Bridge Initial Cost Usually lower if you already own compatible hardware Higher upfront cost Setup Requires installation and configuration Ready to use out of the box Maintenance You manage updates and troubleshooting Usually simpler to maintain Flexibility Excellent Good Technical Knowledge Recommended Minimal What Is a DIY Homebridge Server? A DIY Homebridge server is hardware that you configure yourself to run Homebridge. Common choices include: Raspberry Pi Mini PC Intel NUC Thin client NAS Always-on Linux computer You install the operating system, Homebridge, plugins, and future updates yourself. Pros Lower cost if you already have suitable hardware Complete control over your operating system and plugins Easy to expand with Home Assistant, Docker, Zigbee2MQTT, MQTT, or Node-RED Great for users who enjoy learning and customizing Cons Initial setup takes more time You are responsible for backups and recovery Hardware compatibility varies Troubleshooting requires some technical knowledge What Is a Pre-Built Homebridge Bridge? A pre-built bridge includes compatible hardware with Homebridge already installed like ATHBridge. Most of the initial configuration is complete, so you can begin adding plugins and devices almost immediately. Pros Quick and easy setup No operating system installation required Hardware has already been tested for compatibility Good choice for beginners Less time spent troubleshooting Cons Higher purchase price Hardware upgrades may be more limited Less flexibility than a fully custom build Performance For most homes, performance differences are small. Even entry-level hardware can comfortably run Homebridge with dozens of plugins and many HomeKit accessories. If you also plan to run services such as Home Assistant, Zigbee2MQTT, Z-Wave JS, Frigate, MQTT, Docker containers, or Node-RED, a more powerful mini PC may provide a better long-term experience. Reliability Reliability depends more on good hardware and regular maintenance than whether your system is DIY or pre-built. To improve stability: Use a quality power supply. Choose reliable storage such as an SSD whenever possible. Create regular Homebridge backups. Update plugins carefully instead of updating everything at once. Consider using a UPS if power outages are common. Which Option Should You Choose? Choose DIY if you: Enjoy learning and experimenting Already own compatible hardware Want maximum flexibility Plan to run multiple smart home services Choose a Pre-Built Bridge if you: Want the easiest possible setup Prefer spending your time using your smart home instead of configuring it Want a ready-to-use solution Are new to Homebridge Frequently Asked Questions Is DIY still cheaper? In many cases, yes. If you already own compatible hardware, building your own Homebridge server is usually the more affordable option. If you need to purchase everything from scratch, the price difference becomes much smaller. Does a pre-built bridge perform better? Not necessarily. Performance depends on the hardware specifications rather than whether the device is pre-built or assembled yourself. Can I migrate from DIY to a pre-built bridge later? Yes. Homebridge includes backup and restore features that make moving your configuration between compatible systems straightforward. Does Matter replace Homebridge? Not yet. Matter has improved compatibility between smart home ecosystems, but many devices and advanced integrations still depend on Homebridge plugins or Home Assistant. Final Thoughts There is no single answer that works for everyone. A DIY Homebridge server is ideal if you enjoy customization, already have suitable hardware, and want complete control over your smart home. A pre-built bridge is a better fit if you want a simple installation, less maintenance, and a faster path to getting your devices into Apple Home. I'm especially interested in hearing from people with larger Apple Home setups. Are you still running a DIY Homebridge server? Have you moved to a pre-built bridge? Has Matter reduced your need for Homebridge, or do you still rely on plugins? If you were starting from scratch today, which route would you choose and why? I'd love to hear some real-world experiences the successes, the frustrations, and any lessons learned that could help someone deciding between DIY hardware and a pre-built solution.

I kept searching “does Ring work with HomeKit” because I wanted to use my Ring doorbell with Apple Home. I couldn’t find a native HomeKit option for my Ring setup, so I started looking at other ways to connect it. Here are a few methods I tried. Homebridge Homebridge was the first option I tried. I already had a Raspberry Pi, so it was a good place to start. I installed the Ring plugin and connected it to Apple Home. The setup took a little time, but once everything was connected, I could see my Ring device in the Home app. The main downside for me was not having HomeKit Secure Video. Home Assistant I also tried Home Assistant because I was already using it for other smart home devices. I connected Ring to Home Assistant and then used HomeKit Bridge to bring it into Apple Home. It worked for basic use, but the Ring integration still relies on Ring’s cloud connection. HomeKit Secure Video isn’t supported through the Home Assistant HomeKit Bridge either. Scrypted Then I looked at Scrypted. It supports HomeKit Secure Video, which made it an interesting option for using cameras with Apple Home. The setup was a little more involved than the other options, but it’s worth looking at if HomeKit Secure Video is important to you. For me, there still isn’t one simple solution that does everything. These workarounds gave me a few different ways to bring Ring and Apple Home together. Has anyone here found another good way to use Ring with Apple Home? I’d like to know what worked for you.

If you're wondering whether you can connect Amazon Alexa with Apple HomeKit, the short answer is yes, but not directly. Alexa doesn't natively control Apple HomeKit devices. However, there are several methods that let you use both ecosystems together. Below are the most common options. Method 1: Add Devices to Both Alexa and Apple Home This is the easiest solution if your smart device supports both platforms. Steps Set up the device using the manufacturer's app. Add the device to Apple Home using the Home app. Open the Alexa app. Enable the manufacturer's Alexa Skill. Link your account and discover devices. Your device will now appear in both Apple Home and Alexa, allowing you to control it with Siri or Alexa independently. Best for: Philips Hue, TP-Link Kasa, Meross, Ecobee, SwitchBot, and other devices that officially support both ecosystems. Method 2: Use Matter If your smart device supports Matter, you can share it between Apple Home and Alexa using Matter's Multi-Admin feature. Steps Add the Matter device to Apple Home. Generate the Matter pairing code (or Multi-Admin code). Open the Alexa app. Add a new Matter device. Scan the Matter code. Finish the setup. The same device can now be controlled from both Apple Home and Alexa. Best for: New Matter-compatible smart home devices. Method 3: Use Homebridge If you have HomeKit devices that Alexa cannot see, Homebridge can expose many of them to Alexa. What you'll need A computer, Raspberry Pi, or dedicated Homebridge server Homebridge installed The appropriate Alexa/Homebridge plugin Your Apple Home hub (HomePod or Apple TV if required by your setup) Basic Setup Install Homebridge. Install the Alexa integration plugin. Link your Amazon account. Select which HomeKit accessories you want Alexa to access. Discover devices from the Alexa app. After setup, Alexa will be able to control many of your HomeKit accessories using voice commands. Which Method Should You Use? Situation Recommended Method Device supports both Alexa and HomeKit Add it to both platforms separately Device supports Matter Use Matter Multi-Admin HomeKit-only accessories Use Homebridge Mixed smart home with many brands Homebridge + Matter where available Things to Keep in Mind Alexa cannot directly control Apple Home itself. Not every HomeKit accessory can be exposed through Homebridge. Matter support depends on the device manufacturer. Homebridge requires a device that stays powered on 24/7.

So I finally got my Aqara U400 working reliably in HomeKit after weeks of it constantly showing "Not Responding." I tried a bunch of stuff that didn't work, then a few things that actually did. Figured I'd write this down in case anyone else is dealing with the same frustration. The Hardware Stuff First When I opened it up, I found the internal data cable was slightly pressing against the deadbolt. Nothing crazy, but enough that it was straining a bit. I gently tucked it away and that helped with responsiveness. Some people in the Aqara forums actually chiseled a tiny channel inside the door pocket to give the cable more room — didn't need to go that far, but worth knowing if you're desperate. Also verify the tailpiece is centered. Open your battery cover, remove the battery, manually turn the knob. If it's grinding or sticking, the tailpiece might be off-center in the deadbolt hole. Loosening the mounting plate screws and adjusting its position fixed that for me. And make sure the deadbolt isn't rubbing against your door's strike plate. Obvious but it happens. The Calibration Loop If your Aqara Home app keeps saying "Unknown" status and asking you to recalibrate constantly: Easy way: Open Aqara Home app > Settings > Door Lock Calibration > close the door (keep it unlocked) > tap Start. Let it map the orientation. Offline way (if your WiFi is being weird): Remove battery cover, press Set button once, press 5 on the keypad, follow the voice prompts. This actually worked better for me than the app method. The Big One: "No Response" in HomeKit This is what was killing me. The lock works fine in the Aqara app but HomeKit just spins forever. The fix that actually worked: I completely unaired the lock and re-added it in a specific order. Remove it from HomeKit entirely Scan the Matter QR code directly in the Apple Home app FIRST (let it join Thread natively) Wait like 5-10 minutes for it to stabilize THEN go back and add it as a secondary bridge through the Aqara app (generate a new pairing code in HomeKit settings, copy it to Aqara Home, bridge to Hub M3) Sounds complicated but the order matters. HomeKit direct first, Aqara app second. That sequence fixed it for me. Also — and this might sound weird — I disabled my 5GHz WiFi band temporarily during setup. Just 2.4GHz + the Thread network. Once it was stable, I turned 5GHz back on. I have a UniFi network and apparently that was interfering. Keep the lock within like 3-5 meters of your Thread Border Router or Hub M3. Weak mesh signals cause constant dropping. UWB Unlock on Approach Not Working? Don't use HomeKit's auto-lock toggle. Turn that OFF and instead use the Aqara Home app's auto-lock feature. HomeKit's timer apparently doesn't know when the door is still open, so it'll lock while you're approaching. The Aqara app version is better. Also make sure "Unlock on Approach" is toggled ON in your Apple Wallet for the digital key. Sounds obvious but I forgot to check. Nuclear Option: Hard Reset If the firmware is completely stuck: Remove the rear battery cover Press and hold the Reset key for 5 seconds Verify your admin password when it asks on the keypad Lock clears everything Used this once when the firmware locked up. Worked. Quick Note: Aqara U50 If you're looking at the Aqara U50 (the Zigbee variant), just be aware some U50 models are hybrid Zigbee + Matter. Double-check yours actually supports native Matter/Thread in HomeKit or you might need a hub bridge. The U400 doesn't have this problem, it's just Matter/Thread. Anyway that's what worked for me. Is anyone else dealing with this? Curious what fixed it for you guys or if you found other solutions I'm missing. Sources: https://store-support.aqara.com/products/smart-lock-u400 https://eu.manuals.plus/aqara/u400-uwb-smart-lock-manual

I finally pulled the trigger on the Inovelli Blue Series Zigbee fan switch after seeing it mentioned a few times in this community, and I wanted to write up my honest experience now that it's been running for a while. What it actually is The VZM35-SN is an in-wall fan switch, not a canopy module. It replaces your existing wall switch and gives you variable fan speed control for AC fan motors, though it's not compatible with DC motor fans. If your fan also has a light kit, this specific switch won't handle that. Inovelli's line has a separate Fan/Light Canopy Module for fans that need both fan and light control from one device. Inovelli Inovelli Installation This is an in-wall install, and a neutral wire is required for proper operation ZWaveProducts If you're not comfortable with electrical work, I'd second Inovelli's own recommendation and get an electrician involved Max load is rated at 2.5 amps, and Inovelli specifically says not to run more than two identical fans off one switch, and not to exceed that resistive load Inovelli Help Center It is not rated for lighting loads like LED, CFL, or incandescent, so don't try to sneak a light circuit onto it Pairing and hub compatibility Paired cleanly on my Zigbee2MQTT setup through my SLZB-06M. Inovelli confirms support across SmartThings, Home Assistant ZHA, Home Assistant Zigbee2MQTT, Hubitat, and Amazon Echo, so compatibility isn't a concern regardless of what you're running. Inovelli Help Center Speed control in Z2M This is where the switch earns its reputation. Because it implements the actual Zigbee Fan Control cluster rather than just basic on/off commands, it exposes real discrete speed levels instead of just a single toggle. In Z2M this shows up cleanly as a proper fan entity with distinct speed steps, not the flaky pseudo-dimming you get from some cheaper AC fan controllers that just chop the sine wave. Alibaba The parameter depth is the real story This is the part that separates it from generic Zigbee fan modules: There's a Breeze Mode feature that cycles between Low, Medium, and High to simulate natural airflow, and the same mechanism can be flipped around into a "Wind Down Mode" that ramps the fan down from High to Low over a set time Inovelli Help Center There's a Fan Module Binding Control option that lets you use the config or favorites button as a binding endpoint, handy if you want a second physical control point without adding another device Inovelli Help Center Overall the switch ships with dozens of tunable parameters, which is more than I've seen on any other Zigbee fan device Zigbee mesh impact Since it's mains powered it acts as a router on the mesh. After adding it I checked my network map and it picked up a solid LQI link back to the coordinator, and it's now sitting as a hop point for a couple of battery sensors nearby, similar to what I've seen with other in-wall Inovelli switches. A few caveats If your fan has an integrated light, this specific switch is the wrong pick. Look at the canopy module instead Neutral wire is mandatory, so older homes without one at the switch box are out of luck unless you can pull new wire This works with Inovelli's own Aux Switch or another Inovelli smart switch for multi-way setups, but it will not work paired with an existing dumb switch, so plan your wiring accordingly if you have a 3-way setup Inovelli Bottom line If you want proper multi-speed Zigbee fan control with real automation depth rather than a basic on/off relay, this is the switch to get. The parameter list alone makes it worth the price over cheaper alternatives, and the fact that it plays nicely with Z2M and ZHA without quirks or custom converters made setup painless. My only real regret is not doing this years ago.

I had two devices in my house that refused to join the smart home party: a window AC unit and a ceiling fan, both only controllable by their little IR remotes. I didn't want another app, another remote, or a bunch of tape holding a remote hostage in front of the unit. So I picked up a Zigbee IR blaster and got them both onto my existing mesh. Here's how it went. Why a Zigbee IR blaster instead of a standalone WiFi one I already run Zigbee2MQTT on an SLZB-06M, so this was less about the tech and more about not wanting a third ecosystem in the house. No separate app or cloud account Joins the same mesh as the rest of my routers and sensors, so LQI and coverage benefit from devices I already have One coordinator to manage instead of juggling WiFi devices with their own quirks Setup, start to finish Paired it in Z2M like any other device (put it in pairing mode, hit permit join, it showed up within a few seconds) Placed it with a clear line of sight to both the AC and the fan, about 2 meters from each, since IR still needs line of sight even though the mesh side is wireless Used the "learn" function in Z2M to capture each button from the original remotes, one at a time (power, temp up/down, fan speed, swing) Named each captured command something sane in Z2M so I wasn't guessing which "IR code 4" did what six months later The line-of-sight gotcha nobody warns you about Zigbee mesh doesn't care about walls and IR very much does. I first put the blaster on a shelf that had a clean shot to the fan but was partially blocked from the AC by a bookshelf. Commands to the fan worked instantly, the AC would randomly miss maybe 1 in 5 commands. Moving the blaster about a foot to clear the sightline fixed it completely. Worth testing each command a few times right after setup rather than assuming it works because it worked once. What this actually got me in Home Assistant AC now turns off automatically when a window sensor in that room opens Fan speed ties into a temperature automation instead of me getting up to adjust it Both show up in the same dashboard as everything else, no separate card for "the IR stuff" A couple of things I'd tell someone starting this Capture every button you think you might ever want before you put the original remote in a drawer. I had to dig mine back out once because I forgot to capture "swing mode." If you have more than one IR device in the same room, check for command collisions. Universal remote codes sometimes overlap between brands. Anyone else running old AC units or fans through Zigbee IR blasters? Curious what devices you've resurrected this way.

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 found this article very helpful when I was working through it: https://zigbeehubs.com/blog/zigbee2mqtt/