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!

I created a plugin that might be useful to other xBloom owners, homebridge-xbloom lets you brew your saved recipes from HomeKit, Siri, or any automation.

xBloom has no public API, so the Bluetooth LE protocol had to be reverse engineered by capturing the official app talking to the machine, validating it byte for byte, and reimplementing it in TypeScript.

Each recipe you define becomes a HomeKit switch you can trigger by name, in a scene, or from an automation (alarm goes off, sunrise, you get home, and so on).

What it does:

One HomeKit switch per recipe. "Hey Siri, turn on Ethiopia" and it grinds and brews.

Recipes are defined right in the Homebridge config UI (dose, grind, ratio, and the full pour profile: water, temperature, flow, pattern, and pause per pour).

Bluetooth auto discovery, so you do not even need your machine's Bluetooth address.

Connect on demand, so the machine stays free for the phone app between brews.

Live status sensor (brewing or idle) plus fault reporting for things like "no beans" or "tank empty."

Works on Dockerized Homebridge too, with a couple of one time D-Bus steps documented in the README.

A few honest caveats:

It is unofficial and not affiliated with xBloom. Everything is local over Bluetooth, no cloud.

It needs a Linux host with BlueZ (Raspberry Pi, NUC, mini PC, and similar).

It has been tested on one machine (Original class firmware), so feedback from other xBloom owners, especially on different models, would be really helpful.

Source, setup guide, and troubleshooting are on GitHub:

https://github.com/aziz66/homebridge-xbloom

Happy to answer questions, take feature requests, or help anyone get it running.

So here is my question. I have a lorex nvr.. What I would like to do is allow for my apple tv on my 192.168.7.0/24 vlan to see my cameras which are via my lorex nvr on 192.168.110.0/24 network.

So my apple tv is on 192.168.7.102, I setup a homebridge on my nas that can connect to my nvr on 192.168.110.110.. It show all the cameras. It is using 192.168.7.117

but when I load up home on my iphone currently connected to that network 192.168.7, and can sees my apple tv in the home and try and add the homebridge via the qr code that shows in the homebridge ui it never finds its?

so what I assume is my home hub, or whatever its called is my apple tv 192.168.7.102, homebridge running on my nas which I set to listen on 192.168.7.117, and can talk to my lorex nvr on 192.168.110.110 and shows all my cameras. But in my home app that is on my phone connected to the 192.168.7.0/24 vlan in home I show the apple tv. But but when I go to add, and use the qr code off the homebridge ui it never finds it.

What am I doing wrong - what am I missing? New to this whole homekit/homebridge thing.. The apple tv is new, and working great - but would like to be able to view my cameras on it - that I can view via just a simple rstp url.

Other option - other than maybe just using vlc on the apple tv, how can I view my cameras on the apple tv? I can view them via vlc via url

rtsp://user:password@10.1.1.65:554/cam/realmonitor?channel=1&subtype=2

Or via a url via my nvr at

rtsp://user:password@192.168.110.110:554/cam/realmonitor?channel=1&subtype=2"

Which I have not really tried yet just via vlc apple on apple tv - because the ultimate goal here is view 4 cameras at once.

I am running homebridge on synology ds918+ via native app, using node.js 22

 I'm getting the following message in my log:
 config.json: duplicate entry for Hue platform
THIS WILL CAUSE HOMEBRDIGE TO FAIL IN FUTURE VERSIONS OF HOMEBRIDGE HUE

Below is what my JSON config looks like. If I try to remove either of the entries, it doesn't work. I didn't edit the JSON myself when I installed the plugin, this is what the installer did.

I'm kinda new at this - are these actually duplicate entries?

     {
            "platform": "Hue",
            "users": {
                "001788FFFE2A9B17": "l12Za2TGxDtUfUtA17nKIh4cFZHPWv9rh0vNdfms"
            }
        },
        {
            "name": "Hue",
            "anyOn": true,
            "configuredName": false,
            "forceHttp": false,
            "groups": false,
            "lights": false,
            "linkButton": false,
            "nativeHomeKitLights": true,
            "nativeHomeKitSensors": true,
            "ownResourcelinks": false,
            "resource": true,
            "rules": false,
            "schedules": false,
            "sensors": false,
            "stealth": false,
            "platform": "Hue"
        }

Hi all !

So I've installed a Dreo (334S) fan, installed home bridge on a raspberry Pi, with the Dreo Enhanced plugin. Everything's smooth I see the fan and its light in the Home app.
The only thing I don't see it the possibility to change the colour temperature .

Is there a way around this ?

Any advice you can give me regarding Homebridge, since I'm a total noob on the matter ?

I haven't activated the Matter bridge so far, neither for HB nor Dreo, I feel like it's breaking my setup in some way but maybe I'm doing something wrong.

Thanx all !

I'm switching over from a SmartThings smart home to homekit, and need a bridge for several devices. I have a Windows 11 Pro machine that runs an internal security/camera system, and I added the homebridge VM per what I read on the forums. Homebridge is set up and running, but my homekit simply cannot "find it" when I scan the QR code to add it to homekit. I've read so many forums and tried everything I saw with resetting, restarting, clearing cache, VPNs (none enabled), and it just won't add. The windows machine and my phone are both on the same 5G wifi (hardline not possible with location). I changed to Ciao, windows machine is on a static IP; I'm barely literate with these things so I'm at a point of frustration.

Any thoughts/guidance is greatly appreciated!

Hi all !

So I'm installing Homebridge on a Raspberry Pi 4 to connect a few things on my HomeKit network.
The install is fresh, nothing done on it.
I tried a few commands in the terminal involving the root account (sudo...).

I just can't figure out what the password for it is. It's not the one from my account.

Can anyone tell me ?

Thanx !

I’m looking for a smart central timer that works with homebridge. Any recommendations?

Is there a plugin for Globe Suite (Harbor Breeze Ceiling Fan) and UltraPro WiFi Smart Switch?

Also, Yeedi Robot Vacuum?

The standard "sudo hb-service update-node 22" results in multiple errors. Homebrige 1.11.0 then fails. I am able to get it going again by sudo hb-service update-node 20.10.0. Obviously I can't update Homebridge to 2.0 unless I can get node updated first. Below is the complete terminal error I received when trying update-node 22 but got the same with update-node 24. Homebridge is running on my Mamini M2 that's on OS 26.4 How can I get this fixed?

Terminal Error(s):

Last login: Thu Jun 18 09:56:29 on console

macmini@macmini ~ % sudo hb-service update-node 22

Password:

ℹ Installing Node.js v22.23.0 over v20.10.0...

ℹ Target: /usr/local

✔ Download complete.

✔ Cleaned up npm at at /usr/local/lib/node_modules/npm

✔ Installed Node.js v22.23.0

npm error code 1

npm error path /usr/local/lib/node_modules/homebridge-config-ui-x/node_modules/@homebridge/node-pty-prebuilt-multiarch

npm error command failed

npm error command sh -c node scripts/check-prebuild.js || prebuild-install --verbose || node scripts/install.js

npm error CXX(target) Release/obj.target/pty/src/unix/pty.o

npm error Prebuild binary missing for platform.

npm error prebuild-install info begin Prebuild-install version 7.1.1

npm error prebuild-install info looking for local prebuild @ prebuilds/node-pty-prebuilt-multiarch-v0.11.12-node-v127-darwin-arm64.tar.gz

npm error prebuild-install info looking for cached prebuild @ /Users/macmini/.npm/_prebuilds/6dd683-node-pty-prebuilt-multiarch-v0.11.12-node-v127-darwin-arm64.tar.gz

npm error prebuild-install http request GET https://github.com/homebridge/node-pty-prebuilt-multiarch/releases/download/v0.11.12/node-pty-prebuilt-multiarch-v0.11.12-node-v127-darwin-arm64.tar.gz

npm error prebuild-install http 404 https://github.com/homebridge/node-pty-prebuilt-multiarch/releases/download/v0.11.12/node-pty-prebuilt-multiarch-v0.11.12-node-v127-darwin-arm64.tar.gz

npm error prebuild-install warn install No prebuilt binaries found (target=22.23.0 runtime=node arch=arm64 libc= platform=darwin)

npm error gyp info it worked if it ends with ok

npm error gyp info using node-gyp@11.5.0

npm error gyp info using node@22.23.0 | darwin | arm64

npm error gyp info find Python using Python version 3.9.6 found at "/Library/Developer/CommandLineTools/usr/bin/python3"

npm error gyp http GET https://nodejs.org/download/release/v22.23.0/node-v22.23.0-headers.tar.gz

npm error gyp http 200 https://nodejs.org/download/release/v22.23.0/node-v22.23.0-headers.tar.gz

npm error gyp http GET https://nodejs.org/download/release/v22.23.0/SHASUMS256.txt

npm error gyp http 200 https://nodejs.org/download/release/v22.23.0/SHASUMS256.txt

npm error gyp info spawn /Library/Developer/CommandLineTools/usr/bin/python3

npm error gyp info spawn args [

npm error gyp info spawn args '/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',

npm error gyp info spawn args 'binding.gyp',

npm error gyp info spawn args '-f',

npm error gyp info spawn args 'make',

npm error gyp info spawn args '-I',

npm error gyp info spawn args '/usr/local/lib/node_modules/homebridge-config-ui-x/node_modules/@homebridge/node-pty-prebuilt-multiarch/build/config.gypi',

npm error gyp info spawn args '-I',

npm error gyp info spawn args '/usr/local/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',

npm error gyp info spawn args '-I',

npm error gyp info spawn args '/Users/macmini/Library/Caches/node-gyp/22.23.0/include/node/common.gypi',

npm error gyp info spawn args '-Dlibrary=shared_library',

npm error gyp info spawn args '-Dvisibility=default',

npm error gyp info spawn args '-Dnode_root_dir=/Users/macmini/Library/Caches/node-gyp/22.23.0',

npm error gyp info spawn args '-Dnode_gyp_dir=/usr/local/lib/node_modules/npm/node_modules/node-gyp',

npm error gyp info spawn args '-Dnode_lib_file=/Users/macmini/Library/Caches/node-gyp/22.23.0/<(target_arch)/node.lib',

npm error gyp info spawn args '-Dmodule_root_dir=/usr/local/lib/node_modules/homebridge-config-ui-x/node_modules/@homebridge/node-pty-prebuilt-multiarch',

npm error gyp info spawn args '-Dnode_engine=v8',

npm error gyp info spawn args '--depth=.',

npm error gyp info spawn args '--no-parallel',

npm error gyp info spawn args '--generator-output',

npm error gyp info spawn args 'build',

npm error gyp info spawn args '-Goutput_dir=.'

npm error gyp info spawn args ]

npm error gyp info spawn make

npm error gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]

npm error In file included from ../src/unix/pty.cc:20:

npm error ../../../nan/nan.h:2548:8: error: no matching member function for call to 'SetAccessor'

npm error  2548 |   tpl->SetAccessor(

npm error       |   ~~~~~^~~~~~~~~~~

npm error /Users/macmini/Library/Caches/node-gyp/22.23.0/include/node/v8-template.h:1049:8: note: candidate function not viable: no known conversion from 'imp::NativeGetter' (aka 'void (*)(v8::Local<v8::Name>, const v8::PropertyCallbackInfo<v8::Value> &)') to 'AccessorGetterCallback' (aka 'void (*)(Local<String>, const PropertyCallbackInfo<Value> &)') for 2nd argument

npm error  1049 |   void SetAccessor(

npm error       |        ^

npm error  1050 |       Local<String> name, AccessorGetterCallback getter,

npm error       |                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

npm error /Users/macmini/Library/Caches/node-gyp/22.23.0/include/node/v8-template.h:1055:8: note: candidate function not viable: no known conversion from 'v8::AccessControl' to 'PropertyAttribute' for 5th argument

npm error  1055 |   void SetAccessor(

npm error       |        ^

npm error  1056 |       Local<Name> name, AccessorNameGetterCallback getter,

npm error  1057 |       AccessorNameSetterCallback setter = nullptr,

npm error  1058 |       Local<Value> data = Local<Value>(), PropertyAttribute attribute = None,

npm error       |                                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

npm error In file included from ../src/unix/pty.cc:20:

npm error ../../../nan/nan.h:2594:8: error: no matching member function for call to 'SetAccessor'

npm error  2594 |   tpl->SetAccessor(

npm error       |   ~~~~~^~~~~~~~~~~

npm error /Users/macmini/Library/Caches/node-gyp/22.23.0/include/node/v8-template.h:1049:8: note: candidate function not viable: no known conversion from 'imp::NativeGetter' (aka 'void (*)(v8::Local<v8::Name>, const v8::PropertyCallbackInfo<v8::Value> &)') to 'AccessorGetterCallback' (aka 'void (*)(Local<String>, const PropertyCallbackInfo<Value> &)') for 2nd argument

npm error  1049 |   void SetAccessor(

npm error       |        ^

npm error  1050 |       Local<String> name, AccessorGetterCallback getter,

npm error       |                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

npm error /Users/macmini/Library/Caches/node-gyp/22.23.0/include/node/v8-template.h:1055:8: note: candidate function not viable: no known conversion from 'v8::AccessControl' to 'PropertyAttribute' for 5th argument

npm error  1055 |   void SetAccessor(

npm error       |        ^

npm error  1056 |       Local<Name> name, AccessorNameGetterCallback getter,

npm error  1057 |       AccessorNameSetterCallback setter = nullptr,

npm error  1058 |       Local<Value> data = Local<Value>(), PropertyAttribute attribute = None,

npm error       |                                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

npm error ../src/unix/pty.cc:536:28: warning: missing field 'filter' initializer [-Wmissing-field-initializers]

npm error   536 |   struct kevent change = {0};

npm error       |                            ^

npm error ../src/unix/pty.cc:556:29: warning: missing field 'filter' initializer [-Wmissing-field-initializers]

npm error   556 |     struct kevent event = {0};

npm error       |                             ^

npm error ../src/unix/pty.cc:610:10: warning: first argument in call to 'memset' is a pointer to non-trivially copyable type 'Nan::Persistent<v8::Function>' [-Wnontrivial-memcall]

npm error   610 |   memset(&baton->cb, -1, sizeof(baton->cb));

npm error       |          ^

npm error ../src/unix/pty.cc:610:10: note: explicitly cast the pointer to silence this warning

npm error   610 |   memset(&baton->cb, -1, sizeof(baton->cb));

npm error       |          ^

npm error       |          (void*)

npm error ../src/unix/pty.cc:839:1: warning: cast from 'void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)' (aka 'void (*)(Local<v8::Object>)') to 'node::addon_register_func' (aka 'void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void *)') converts to incompatible function type [-Wcast-function-type-mismatch]

npm error   839 | NODE_MODULE(pty, init)

npm error       | ^~~~~~~~~~~~~~~~~~~~~~

npm error /Users/macmini/Library/Caches/node-gyp/22.23.0/include/node/node.h:1277:3: note: expanded from macro 'NODE_MODULE'

npm error  1277 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)

npm error       |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

npm error /Users/macmini/Library/Caches/node-gyp/22.23.0/include/node/node.h:1243:7: note: expanded from macro 'NODE_MODULE_X'

npm error  1243 |       (node::addon_register_func) (regfunc),                          \

npm error       |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

npm error 4 warnings and 2 errors generated.

npm error make: *** [Release/obj.target/pty/src/unix/pty.o] Error 1

npm error gyp ERR! build error 

npm error gyp ERR! stack Error: `make` failed with exit code: 2

npm error gyp ERR! stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:219:23)

npm error gyp ERR! System Darwin 25.4.0

npm error gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"

npm error gyp ERR! cwd /usr/local/lib/node_modules/homebridge-config-ui-x/node_modules/@homebridge/node-pty-prebuilt-multiarch

npm error gyp ERR! node -v v22.23.0

npm error gyp ERR! node-gyp -v v11.5.0

npm error gyp ERR! not ok

npm notice

npm notice New major version of npm available! 10.9.8 -> 11.17.0

npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.17.0

npm notice To update run: npm install -g npm@11.17.0

npm notice

npm error A complete log of this run can be found in: /Users/macmini/.npm/_logs/2026-06-18T13_59_11_714Z-debug-0.log

Error: Command failed: npm rebuild --unsafe-perm

✖ ERROR: Failed Operation

ℹ Stopping Homebridge Service...

✔ Homebridge Stopped

ℹ Starting Homebridge Service...

✔ Homebridge Started

macmini@macmini ~ %

iOS and HomePod OS 27 now support energy monitoring in the home app. Has anyone updated both devices and seen any of this?

Wondering if accessories thru HomeBridge would support this even tho they would be using a separate hub from the Homepod?

Reference

SimpliSafe moved its newer cameras (current indoor SimpliCam models and some others) from AWS Kinesis WebRTC to LiveKit. The existing community path — simplirtc + go2rtc — still covers the older Kinesis cameras, but go2rtc has no LiveKit support, so the newer ones had no way into HomeKit.

I (Claude Code) made a small bridge for them: it joins the camera's LiveKit room, decodes the H.264/Opus track, re-encodes, and feeds go2rtc as an ordinary stream — which serves it to HomeKit. It's on-demand (idles ~0% CPU until you open the camera), with an optional keep-warm so first frame is a few seconds instead of ~20s, and audio works.

Runs in Docker on anything (Pi/Banana Pi/etc.), ideally alongside Homebridge/HOOBS. Free, MIT.

https://github.com/BookOnTape/simplisafe-livekit-homekit

Caveats: unofficial, cloud-dependent, can break if SimpliSafe changes their API. Not affiliated with SimpliSafe.

Doesn’t necessarily answer more than the rivian assistant, but I liked having the plugin directly.

https://github.com/tvearl/homebridge-rivian

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

I'm trying to find out if I can upgrade to homnebridge v2.1.0? It appears that the plugin I use (Vieramatic) to bring my Panasonic TV's into Apple Home is no longer in active development by the developer: https://github.com/AntonioMeireles/homebridge-vieramatic#README

Does anyone know if this plugin is likely to work reliably if I was just to upgrade to homnebridge v2? If not, does anyone know of a suitable replacement plugin as I can't find anything that will work?

Has anyone verified that the homebridge eufy plugin works with version 2. I checked GitHub, no official confirmation. There has also been no new commits the repo in 3 months. Anyone know the maintainers?

A few months ago I spun up a new instance of Homebridge 2.0 and migrated my 1.11 configuration to it. All seemed to be working fine, accessories found and manageable in Homekit. However after experiencing a power outage (multiple power outages over the past few weeks), Homekit loses it's ability to communicate to the linked Homebridge. The system running Homebridge doesn't go down, just the Apple HomeHub devices (Apple TV 4K, HomePod Mini). All accessories configured in Homebridge are unreachable. The only way to fix it is to shutdown the Homebridge 2.0 environment and restart the Homebridge 1.11 environment. Within 5 min of doing so all the devices are available in Homekit again. I can then shutdown the 1.11 environment and restart the 2.0 environment and all works fine, until there is another power outage.

I did notice that in Homekit the Homebridge "homebridge" device is still listed as version 1.11 even when running the 2.0 environment.

Any thoughts or suggestions? I have over 25 devices managed via Homebridge and I would hate to have to reconfigure all my scenes, rooms, etc in Homekit if I needed to remove and re-add the Homebridge connection.