Smarthome Forum

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

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

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 te

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.

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 H

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

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 w

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 s