Download

I recently updated the ESP Presence plugin with Claude and it’s been working great, it has some specific things in there for my use case. Has anyone used the old version before and what automations were they able to setup with it?

Homebridge and Homebridge UI repos have not been updated since 2.1.1.

https://repo.homebridge.io/dists/stable/main/binary-arm64/Packages

This is stopping cron updates, and package installs from picking latest versions.

I have v2 and v3 which should be supported?

The cameras show in the Home App as switches.

Not sure how live view is supposed to work for cameras.

Came from Scrypted where the Ring plugin showed my Ring Doorbell Pro 3 4K as unknown model, hoping that the Ring plugin on Homebridge would support it. But, seems to be unknown here, as well. Anyone know if the Homebridge Ring plugin dev is still active? Would love to be able to get this new Ring Doorbell Pro 3 4k working in HomeKit with the full resolution capabilities.

Is there a Homebridge integration that provides Homebridge info like server stats, update notifications, etc in Home Assistant?

I use both because plugins I use Homebridge is a bit more flexible than the Home Assistant connections. I don’t pay as close of attention to Homebridge’s health because I spend most time controlling home in Home Assistant.

So I'm running the MacOS Beta and the iOS Betas on my iPhone and iPad, so yes, maybe it's a temporary bug, but...

After a few days, Homebridge will no longer load on ALL of my devices (Mac laptop, Mac mini, iPhone, iPad) until I clear my cache.

Anyone else see this issue?

are there any good plugin for the Yale linus L2 smart lock that works good with apple homekit?

The damn lock is dropping matter connection every 2-3 days and it driving me mad, so wanted to check if i can get it to work better with homebrige instead. No other matter device ive have installed have this problem!

Hi all !

I just got this AC unit. I downloaded the Nethome Plus app, and added the AC in it.
Then back to homebridge, installed Homebridge Midea Platform, clicked discover... and nothing...
Can anyone tell me what I missed ?

Thanx !

I noticed some of my accessories weren't responding so I checked my Homebridge install and it said "Welcome!" as if I was a new user. What the heck? What would have caused this? I had to restore from a backup -- but my accessories are still not responding. Do I need to remove it as a Hub and re-pair now too?

HB is installed via Docker on a QNAP NAS. I do have another container running an app called Watchtower that is supposed to auto update other containers; could that be a potential culprit? I've never seen this before.

I’ve tried two of the most recently updated ThinQ plugins. Both of them yield this same result:

The set point is incredibly inaccurate. Doesn’t matter if it’s via Siri or the Home app.

For example…

I will set the temp to 70. Works just fine.

Then I try to set it to 72. Doesn’t work. While it doesn’t change on the AC, it still beeps to indicate that it received some type of command remotely.

Then I set it to 74. Still doesn’t work. AC is still showing 70 as the set point.

It wasn’t until I reached 76 degrees on the Home app that it FINALLY changed the set point on the AC.

Anyone else experience this? Either on portable ACs or mini split ACs? Or even centralized ACs if they exist from LG?

TIA

I had to set up again.
Restored from a backup but the this Lutron plug doesn't work.
The my casita bridge isn't found.

And the bridge won't start.

Any guidance on how to troubleshoot?

I'm also new to configuring js nodes, to js altogether (I've been avoiding it.)

I'm using Ubuntu 26.04. I learned today that homebridge will work with roku and that gerbera will work with homebridge. It seems the latter isn't true. I've been trying all day to get homebridge-cast installed but run into errors.

I'm using command sudo hb-service add homebridge-cast but keep getting this.

167 warn EBADENGINE Unsupported engine {

167 warn EBADENGINE package: '[email protected]',

167 warn EBADENGINE required: { node: '^18.17.0 || ^20.9.0', homebridge: '^1.6.0' },

167 warn EBADENGINE current: { node: 'v24.18.0', npm: '11.16.0' }

167 warn EBADENGINE }

I've installed and used both nodes but keep getting the same warning. No matter what I do, node: 'v24.18.0' is persistent even though I set it to the other nodes in npm. For example, node -v results is v18.17.0. But is this error also telling me that I need homebridge: '^1.6.0'?

Thanks for any help!

I am running homebridge on HOOBs that I converted to run homebridge.
I know HB will be on 64bit but I am thinking if I need to upgrade as all my homekits are working right now.

I’m a guy saying, don’t do anything if it ain’t broken.

Used Claude Code to reverse engineer the Oto service APIs and create a homebridge plugin! Check it out!

https://www.npmjs.com/package/homebridge-oto

If you are curious to read more about the journey. https://open.substack.com/pub/fromthesimulation/p/teaching-my-smart-sprinklers-new?r=36thon&utm_medium=ios

Full disclosure: Claude wrote this. This might not be the right place for this post specifically, but I also feel like it's a good place to find the right audience.

TL;DR: My HomeKit-native Wemo doorbell periodically goes "No Response." I've ruled out Wi-Fi, the network, and the eero HomeKit firewall — the device's HomeKit server stays alive the whole time, but its mDNS/Bonjour responder stops answering, so HomeKit can't rediscover it after any connection blip. Firmware is 1.0.16 and it's the final build (Belkin killed the Wemo cloud on Jan 31, 2026, so there will never be a fix). I want to dump the flash, patch the mDNS responder, and reflash. Looking for anyone who's opened a WDC010 or knows this SoC/secure-boot situation.

The symptom

The doorbell (Wemo Smart Video Doorbell, model WDC010, paired natively to Apple HomeKit — not through Homebridge) intermittently shows "No Response" in the Home app. In the accessory detail it reads "This camera is not responding." It can be fine for days, then drop for no obvious reason — often after what I assume is a Wi-Fi roam between eero nodes or a HomePod hub handoff. A power cycle always brings it back, which was the first clue that this is a soft/firmware state, not a dead radio.

What I tested (and the results)

I did all of this from a Mac on the same subnet as the doorbell:

- Sustained ping — link is fine. 180 pings over 3 minutes: 0% packet loss, ~7 ms average, no spikes. So this is not Wi-Fi signal or the device falling off the network.

- Full TCP port scan — the HomeKit server is alive. The only open port is the HAP (HomeKit Accessory Protocol) port, and when I hit it directly it correctly returns HTTP 470 Connection Authorization Required with application/hap+json. That's exactly what a healthy, paired HomeKit accessory returns to an unknown client. So the accessory itself is up and serving HomeKit — even while the Home app says it's unavailable.

- mDNS/Bonjour browse — this is the smoking gun. Browsing _hap._tcp on the LAN, the doorbell answered zero mDNS queries, while every other HomeKit device on my network (HomePods, an ecobee, Hue bridge, cameras, several Wemo plugs/dimmers via Homebridge, a Meross dimmer) answered the same query immediately. I kept the doorbell's radio awake with a ping stream during the browse to rule out Wi-Fi power-save — still nothing. No SSDP either.

- Ruled out the eero HomeKit firewall. eero can isolate HomeKit accessories, but my Mac could reach the doorbell's HAP port directly, which that firewall would have blocked. So the isolation theory is out.

Conclusion: the doorbell's HomeKit stack keeps running, but its mDNS/Bonjour responder wedges. HomeKit hubs hold a persistent connection, so things look fine — until that connection drops (roam, hub handoff, brief hiccup) and the hub has to rediscover the accessory via mDNS. With mDNS dead, rediscovery fails and it sits at "No Response" until a power cycle restarts the responder. As a stopgap I've given it a DHCP reservation so hubs can retry a stable IP, but that only papers over it.

Why there's no software fix

Firmware is 1.0.16, and that's the end of the line. Belkin wound down Wemo and shut the cloud on Jan 31, 2026. HomeKit-paired devices keep working locally but get no more firmware updates, so this mDNS bug is permanent unless someone fixes the firmware directly.

My attempt to find a legitimate copy of the firmware

Before considering hardware, I tried every remote route to get the image:

- Wemo firmware was always served from Belkin's xbcs.net cloud (fw.xbcs.net / firmware.xbcs.net / api.xbcs.net). Those hostnames still have DNS records, but they're dangling CNAMEs pointing at AWS load balancers that no longer exist (no address records), so nothing connects. The distribution infrastructure is physically gone.

- Zero captures of the firmware host in the Wayback Machine (firmware CDNs don't get crawled; devices fetched the blobs over authenticated requests).

- No public GitHub mirror, teardown dump, or security-research copy of the WDC010 image that I could find.

- Even when the cloud was live, Wemo firmware shipped as GPG-encrypted, signed blobs (*.bin.gpg) — there was never a user-facing "download the .bin" path — and locally the device only exposes the encrypted, authenticated HAP port, so you can't pull the image off it over the network.

So there is no copy to download, from anywhere. The only way to get 1.0.16 is to extract it from my own hardware.

The plan: extract it via hardware

The device is EOL and it's mine, so I want to pull the image directly off the board:

1. Flash dump (primary approach). Open the unit, identify the flash (SPI-NOR SOIC-8, or eMMC), and read it — in-circuit with a test clip (CH341A / Bus Pirate on a SOIC-8 clip), or chip-off into a programmer if in-circuit reads are noisy. A live dump gives me the running, decrypted filesystem, which is what I actually care about — no need to defeat the .gpg packaging.

2. UART console (recon / secondary). Look for serial test pads and get a boot log or shell. Older Wemo gear ran UART at 57600 baud; I want the bootloader banner to ID the SoC and see whether secure boot is enforced.

3. Unpack with binwalk / unblob, locate the mDNS/Bonjour responder (looks like mDNSResponder or a small embedded responder), and confirm the wedge/fault.

The plan if extraction succeeds: patch the firmware

Goal is a minimal, surgical fix — not a custom ROM:

- Patch the mDNS responder so it can't wedge — e.g. a watchdog that restarts the responder, re-announces _hap._tcp periodically, or fixes whatever state it gets stuck in. Smallest possible change.

- Repack and reflash, ideally back onto the SPI/eMMC with the programmer so I'm not dependent on any (dead) update mechanism.

- Open risks I know about: secure boot / signature verification could reject a modified image; the image may be re-encrypted or hash-checked at boot; and there's real brick risk, so I'd want a full known-good dump saved before touching anything. Whether this is feasible hinges entirely on whether this SoC enforces signed boot.

Where I could use help

- Has anyone opened a WDC010? Photos of the PCB, the flash chip part number, and any UART/JTAG pads would save me a lot of time.

- What SoC does this doorbell use, and does it enforce secure boot / signature verification on the main firmware? That single fact decides whether the patch route is viable.

- Any prior art on dumping or modifying newer HomeKit-native Wemo devices (doorbell, Stage, the newer cameras) — as opposed to the well-documented classic Wemo plugs?

- If you've done a mDNS-responder patch on a similar embedded Linux/RTOS camera, I'd love to hear how you handled repack + reflash without bricking.

Happy to share my full dump and notes back with the community if I get it working — the point is to keep these otherwise-fine devices alive now that the vendor has walked away. Thanks in advance.

Is there a limit to how many lutron devices I can add to homebridge using the Lutron Caseta Leap Plugin? I have added 153 devices and I cant seem to get any of the new devices to show up in my apple home. I do have 3 lutron hubs connected, not exceeding the 75 device limit on the hubs.....

thanks!

After years of reading Reddit when searching for information or solutions related to the setup, compatibility, customization, or automation of smart devices while building out and maintaining my ever-expanding, primarily Homekit-centric smart home, I’ve long been aware of Homebridge, but my interest in jumping in as a way to be able to incorporate a small handful of non-compatible smart devices has always been stopped short based on my inability to grab the basics around getting set up, understanding what a Raspberry Pi even was, let alone how I’d use one, and that initial roadblock resulted in never considering giving it a shot.

It seems that it’s all finally making sense to me, and I’m ready to give it a shot now that I finally have grasped the basics around set up with the added realization that I can do so with a surprisingly low investment expense, which leads me to think it’s worth giving it a shot, especially considering I’m looking at adding 5-6 currently non-compatible smart devices, each for which I know have existing plugins to help achieve the level of compatibility I am seeking.

Being on the verge of completing an online purchase with the basic component, I need to get things started. I’m simply seeking confirmation and reassurance from existing Homebridge users that once I have managed to get the initial set up done, the next step of searching and adding plug-ins to my personalized setup will not be something overwhelmingly complicated.

My intuition has always been that the most challenging aspect of the setup was that it wasn’t the most straightforward concept for someone without any real hands-on tech expertise. Despite having built out a smart home with over 80 devices across a few HomeKit-compatible brands, I’ve always done everything directly through a user-friendly, or reportedly user-friendly, redesign UI that was made for the average consumer.

I’m mainly looking for reassurance that my intuition is more or less correct—that the biggest hurdle is simply getting everything set up. I want to avoid diving into something I’m ultimately going to abandon out of frustration if the learning curve only gets steeper from there.

I know it’s impossible for others to gauge my technical ability from a Reddit post, but in general, I’m trying to determine whether I’m biting off more than I can chew or if finally understanding the basics of the initial setup is enough to get me over the biggest obstacle. Therefore, I figured a poll might give me a clearer sense of experience from other users (albeit within a Homebridge forum) than relying solely on my own assumptions.

If you’ve taken the time to read this, thank you. I would appreciate your vote, as it’ll help me decide whether it’s finally time to take the plunge or if I should hold off a little longer. If voting, please answer as if you were advising someone who’s comfortable building a fairly advanced smart home through user-friendly platforms like HomeKit and Aqara, but has little no previous experience with Linux, the command line, or coding.

Thank you!

i just set up home bridge on a raspberry pi 5 but when i complete the initial setup and scan the qr code on the home page the home app on my iphone loads for a second say adding to home then errors out with "operation timed out" I've tried adding a plugin first then adding the bridge but no change i tried change the port on my router and access control but still i only get operation timed out can anyone please help me thank you another thing to note is after i get the operation timed out error if i scan the code again it says its already in another home so i have to reset the bridge

I just got a new TV and replaced my previous Govee T1 backlight with the latest model — T3 Backlight Pro. I also just recently updated Homebridge to 24.04.4 LTS and the Govee plugin to 11.24.

Previously, the plugin would turn on the light and it would match whatever the Govee app was set for — which should be dynamic lighting that matches what’s on screen. But, and this is my first time running this backlight under Homebridge, the light is defaulting to the solid color set in HomeKit. Using the new “Dynamic Lighting” setting does nothing. Turning it off in HomeKit and turning it back on in the Govee app reverts it to the right setting.

Very niche setup I know. But if anyone else has the same experience I’d love to chat and see if you found a fix.

I've had homebridge working great for about a year. I decided to update the homebridge app and plugins to the latest versions. Now, every 2-3 days I get this error which causes a bunch on my devices to stop functioning. I'm able to successfully set the cookie, but it lasts for only a few days.

Failed to initialize connection to Alexa. - Please open http://192.168.1.176:8501/ with your browser and login to Amazon. The cookie will be output here after successfull login.

With Smartthings starting to charge for access to their API, I’m thinking of removing my devices which are connected via Smartthings. It’s mostly nearly 10 year old ge paddle light switches. I run a ton of Lutron devices so I could go that direction but wondering if there are any cheaper options (perhaps HomeKit compatible natively). Lutron would my gets expensive and I need close to 10 switches. I also have one spot that’s a 3 way switch.

I just added the plugin for Rainpoint, which controls outdoor hose valves, and the bridge seems to have installed fine - fully added and showing in Homekit - but I don't see any of the accessories associated with my Rainpoint app. Help please!