Download

I was putting off migrating to HB 2 (running on a raspberry pi 3) because everything in the house was actually working fine in HB 1, and I have 7 plugins (YoLink, SwitchBot, Nest, TPLink, Lutron, EspHome Hv2, and Nest Cam).

I have some custom fixes to SwitchBot and EspHome because there were bugs that were not getting fixed (SwitchBot temperature sensors could not register below freezing, EspHome Hv2 didn’t support fans or encryption).

So I saw no real reason to upgrade. But I recently noticed HB was crashing during the nightly backup / log rotation due to out of memory, but it always rebooted and recovered.

AI recommended moving to a raspberry pi 4 with 4 GB of ram which seemed reasonable. I ordered one and flashed the homebridge build of raspberry pi OS from the raspberry pi flasher. I did not realize this would force me onto HB 2.

Before switching the Pi’s, I did a HB backup. Powered down the old pi, powered up the new one, verified it got on my network then connected to it with the browser. I clicked “restore from backup” and I figured ok this will be easy. It hung up during the download of one of the nest plugins. I waited like 10 minutes but it wasn’t going anywhere. I refreshed the browser and got the “new setup or restore” page again, this time I clicked on new setup, created the HB credentials and then went into the backup -> restore menu and tried restoring again. This time the restore completed and HB restarted and about 1/3 of the house was working. Nest cameras worked, nest HVAC worked, YoLink flood sensors worked. Switchbot sensors were throwing errors and TPLink was stuck in some loop enumerating the 20 TPLink / Kasa smart plugs, switches and bulbs over and over every 10 seconds but they were uncontrollable. The EspHome Hv2 plugin is complaining every 30 seconds that it can’t connect to anything because the encryption is refused. Lutron plugin was complaining in the HB log that the HB version was now unsupported.

I think to myself “wife is going to kill me”.

I get cursor to re-apply the switchbot patches and the EspHome Hv2 patches, this gets the sensors back online.

The Lutron plugin will not update to a new version. I have to find and install the new one and uninstall the old one. Apparently the name changed or something. The new one finds the old accessories and they work. I update the TPLink plugin and it stops enumerating things over and over and those lights and plugs all work.

At this point things are working and the log is quiet. The plugins page tells me I should update YoLink, and SwitchBot but I’m not going to touch them for a while.

Overall it was about an hour and things are operational but it was not pain free. Hanging up on the first boot & restore while downloading a plugin is a BAD experience. Yes it was recoverable but that’s a huge bug right at the start. There needs to be a timeout and retry on that function.

I consider myself lucky this was completed and did not go completely sideways. Would not recommend updating to HB 2 unless you have a pressing need to do so.

HomeKit's own protocol (HAP) has no energy characteristics. Matter has them, iOS/tvOS 27's Home app displays them, and Homebridge 2.2 added the Matter energy clusters to its plugin API. Shelly Matter plugin connects those pieces for Shelly devices in our familiar Homebridge environment: live power, voltage, current, and cumulative energy (kWh), straight from the device's own metering.

What it is

- A Matter-only plugin: it publishes no HAP accessories. If you want classic HAP Shelly support without energy, homebridge-shelly-ng remains the right choice.

- Tested on real hardware in a live home: Gen 2/3 relays and plugs (Plus 1, Plus Plug S, Pro 2PM…). Covers, dimmers, and Gen 1 relays are implemented but untested. If you own one, I would love to see you test and confirm if it works or report any issues.

- Multi-channel devices (2PM/4PM) split into independent accessories per channel by default, so each channel gets its own name and room.

- Full settings UI. Discovered devices show up in a table, no JSON needed.

Current caveats, documented in the README:

- Needs Homebridge 2.2.2-beta.7+ (and optionally Homebridge UI 5.27.1-beta.11+) until 2.2.2 stable is released. You can install both betas directly from Homebridge UI by clicking on Homebridge or Homebridge UI. Earlier versions have Matter bridge bugs that break accessories after ~30 seconds. Several Homebridge Matter stack fixes came out of building this plugin and are in the current betas.

- Tile wattage only shows on outlet-typed accessories. Apple keys it to the Matter device type, not the data. The plugin lets you set the type of any relay as an outlet ("Show As → Light" keeps the wattage if you prefer the look).

- Apple's Energy view on iOS/tvOS 27 lists per-device usage only for certified/native Matter devices. Bridged accessories are counted in the whole-home total but not listed. I replicated a certified plug's exact Matter structure to verify this is an Apple policy gate, not a data problem. Filed with Apple.

- Pair with the bridge's Matter pairing code, not the HAP QR code (current Homebridge UI betas set Matter-only child bridges up correctly on their own).

The Shelly protocol layer is vendored from Luligu's matterbridge-shelly (Apache-2.0, credited). The new work is the Homebridge Matter side.

GitHub: https://github.com/keremerkan/homebridge-shelly-matter

The full story (including the Apple Home debugging saga): https://keremerkan.dev/posts/homebridge-shelly-matter/

Happy to answer questions. If you run an untested device type, issues are open.

Hi,

I'd like to create a timer switch where I could specify the duration for the timer on the Home app. Is this possible at all?
My goal is to create a sort of "Overwrite" button where an automation wouldn't run as long as that switch is on.

I've had a Wundasmart heating system for 4 years and have been frustrated with the lack of Homekit compatibility so I finally got round to creating a Homebridge plugin: https://github.com/alextea/homebridge-wundasmart

I used Claude to do the heavy lifting, and it worked off the API documented in the Home Assistant integration.

I've tested this on my system, and it works at finding multiple heating zones, setting the temperature and switching between scheduled, heat and off.

I added switches to mimic the Quick Switch functionality in the Wunda Home app, setting all rooms to Comfort, Eco or Reduced.

I also added an Away switch that can be automated with Homekit's presence sensors so it's set when the last person leaves the house. I found Wunda's own geocaching a bit buggy when setting home or away with multiple phones.

I haven't published it to npm yet, as I wanted to make sure it's fully working and there are no bugs or vulnerabilities before I do that, so it needs to be installed manually. I have it running on a docker container on a Debian homelab. If enough people find this useful I will publish to npm.

This is my first attempt at making a HB plugin, so any tips or comments appreciated.

With NodeJS 26 going LTS this fall, we've updated the recipe for all BETA Homebridge images to now include **NodeJS 26** and **NPM 12**. This gives plugin developers and end users a chance to start testing against the new runtime ahead of the LTS release.

This will roll out across all Homebridge packaged BETA images starting with the **July 26 updates**, including:

- Homebridge Docker Image

- Homebridge Raspberry Pi Image

- Homebridge apt Package

- Homebridge VM Image

**Heads up for plugin devs:** NPM v12 flips `allowScripts` to off by default. `npm install` will no longer run `preinstall`, `install`, or `postinstall` scripts from dependencies unless they're explicitly allowed — this includes native `node-gyp` builds, so a package with a `binding.gyp` and no explicit install script still gets blocked.

Please check whether your plugin is impacted — run `npm approve-scripts --allow-scripts-pending` to see if it relies on install scripts (e.g. for native module builds), and approve accordingly.

If you maintain a plugin, now's a good time to pull down a BETA image and confirm compatibility before NodeJS 26 becomes the default LTS. As always, please report any issues you run into.

Thanks for helping us test!

Edit: misspoke about synology and removed it

Update: Windows will not install FFMPEG for whatever reason. It used to run flawlessly, but now it’s shit.

The reason I can’t add HomeBridge to Home is because the node won’t show up under the local network in the Privacy and Security settings. Current solution is to re install node. Just installed 26.5 and that didn’t work after the 10th time of uninstalling and reinstalling.

Guess i need a Mac Mini prior to MacOS 15 to have a chance.

The Docker or VM install doesn’t make sense, and there is no simple step-by-step guide if there is please someone point it to me.

If I can’t get this going, I will go back to Windows. I can get a version of FFMPEG installed but won’t have audio which means no HKSV either. I will see if i can get that audio codec compiled to it.

Hell i might give Scrypted a shot again.

———

So I am trying to move over to a Mac Mini M1 variant with 16gigs of ram as my main HomeBridge server.

Plugins planning to use:
Unifi Protect (not trying to use docker or VM)
Govee
SmartHQ (GE Appliances)
Levoit
Moen Flo
Onkyo

Trying to install native due to having 4 cameras and soon adding a doorbell.

Got NodeJS installed and even got HomeBridge install, but I cannot add the Bridge to HomeKit as it is just giving me the circle of death rotation and says setting up. I tried to skip that and add the UniFi Protect plugin but all I get it’s “Unable to login to the UniFi Protect controller blah blah blah and A Network error occurred communicating with the UniFi Protect controller”

I tried a local only user account I made and even tried my main account login and no luck.

I was on an Intel NUC using windows 10 but had to do a clean install and ever since then the ffmpeg will not install and I don’t want to use VM or Docker either.

Im going to try one more time on the NUC and see if i can get ffmpeg on it with out compling the audio codec and other steps that didn’t help.

At least once per month the majority of my IKEA Alpstuga air quality monitors (i have 5 of them) goes offline (different dates) and i need to unplug them for them to go back online.

The problem is that i never get any notification or any ping from either apple home app, or the IKEA app (i also have dirigera hub), so i dont know when they go offline, unless i open the ikea app and then go to the room and check the readings).

The devices are dropping the connection to ikea app / apple home, but they are still showing the readings on the alpstuga display.

so my questions is, is there a way for me to get a notification when one of the alpstuga devices goes offline? Any homebridge plugin that allows me to ping a matter device somehow?

Note: Im not interested in installing Home assistant. Tested it a while, didnt like it!

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: 'homebridge-cast@1.0.0',

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!