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

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'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.

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

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?