Download

TP-Link / Kasa devices were recently discovered to have a vulnerability CVE-2026-76784, and they released a firmware update for several devices.

In my home setup I have 4 Kasa KL125 smart bulbs. Two of them seem to have self updated their firmware to 1.1.1 in the last two days and I can no longer control them from HimeBridge or HomeKit / Apple Home app.

I reset the two bulbs and re-joined them to my home network with the Kasa app and I can control them fine in the Kasa app, but they do not appear in homebridge or the home app.

I am running HomeBridge 2 with the HomeBridge TPlink Smarthome plugin v8.0.4, which does not even seem to be able to find these two bulbs on my network. My WiFi and router both show the bulbs on the network and they have been assigned valid IP addresses. Even entering these IP addresses as manual discovery they still do not show up as homebridge accessories, and do not appear in Apple Home app.

Not sure how to fix this at this point, the bulbs don’t seem to support rolling back the firmware (not that that would be a good idea anyway).

Hey everyone,

Like a few others here, I ran into the issue where the newer tablet-less Advantage Air MyPlaceIQ systems couldn't talk to the legacy Homebridge integrations.

Thanks to the WebSocket reverse-engineering work done by anwickes (Adam Wickes) on the Home Assistant side, I’ve ported the login protocol and data mapping over to Node.js and published a full native Homebridge platform plugin!

It exposes each of your A/C zones as an individual Thermostat tile in HomeKit, automatically handles system-wide controls via non-closable zones, and supports Dry/Fan modes.

• NPM: https://www.npmjs.com/package/homebridge-myplaceiq
• GitHub: https://github.com/ben-burt/homebridge-myplaceiq

If you have a MyPlaceIQ system, please give it a test run. You will need to extract your hub's clientId and clientSecret via a Wireshark capture from your official mobile app. Instructions on how to fetch those credentials are included in the README.

Open to any feedback, issues, or PRs!

Tried to change the names in homebridge ui and it also reset back to default if I refresh the page

I am having some difficulties getting this to work. I am using v2.1.2 of the arlo plugin but it doesn't seem to want to establish a connection. Does anyone here have it working and could give me a helping hand here?

I have not upgraded to Homebridge 2.0 yet. I have two Ring spotlight cam 4K Pros running on the Ring plugin. I would like to confirm from someone else that they work correctly and that you can activate both the light and siren on them from Homebridge.

I have them connected to a switch on a gate and have an automation that if it is after midnight it set the alarm off. I just want to confirm with someone else that it works.

Installed a Mr Cool Split A/C unit in the mancave…

Really wanted to incorporate it into HomeKit, instead of the standalone app.

Found the SLWF-01Pro USB from Cloudfree.shop. <$20.
Direct swap for the USB WIFI stick that comes with the Mr. Cool A/C unit

Homebridge has a plugin.

Totally easy and now I have environmental control over the mancave. Window open? Then the AC doesn’t turn on…

Wonderful!

Hi

I already have one HB (latest) running on a RPi, with a number og plugins and devices attached.

I have another RPI with Zigbee2mqtt and Msoquitto and also a number of devices here. I would like to expose those devices to Apple Home also, so i installed HB on this PI. Went well but i can't add this new one to Apple Home, just times out. I also see this new install detects the already running HB with IP and ID.

Any special tricks to get this working?

Not really interrested in installing Zigbee2mqtt on the original PI ;-)

br

Has anyone here had success accessing the Eufy e21 cameras via Apple home using homebridge? Set up went fine for me, but homebridge is consistently unable to access the devices when trying to discover them.

Thought I would share some screen shots from the new smart automation module, and this is the Door Ajar automation being tested.

Naming of the alert is clumsy, as it is a combination of Home and Room then the second line is Room and device. I had named the sensor ‘Ajar Garage Door’

Looking good so far

All my accessories are working in the homebridge ui but it shows “No response” on my Home app.
Any fix please?

Hey!
I want to connect my entire house using Homebridge so I can control it from a wall-mounted iPad. I'm planning to use a Raspberry pi but I don't know which model to get.

Can you help me out?
Thanks guys

I'm running Homebridge on a Raspberry Pi.

Im getting the following error in the log every minute...

[26/08/2026, 18:24:58] [Homebridge UI] Failed login attempt.

[26/08/2026, 18:24:58] [Homebridge UI] If you have forgotten your password, you can reset to the default of admin/admin by deleting the "auth.json" file at /var/lib/homebridge/auth.json and then restarting Homebridge.

Eventually this then happens...

[26/08/2026, 18:21:57] [Homebridge UI] Too many failed login attempts for 'REDACTED' - temporarily locked out.

The username is an old one I used when I first set up the Homebridge. After some issues I reset it all and set it up with a different user name - the one being reported above is not present on the account.

So, something, every minute, is attempting to login. I'm guessing it's not malicious and is something on my network but have no idea why. I don't have any third party apps set up for Homebridge and don't use anything like Home Assistant.

Anybody have any idea on how I can track down and resolve this?

Hi everyone! 👋

I’ve released Homebridge MOVA 1.2.0-beta.1, a new compatibility-testing beta for MOVA robot vacuums.

What’s new:

• Recognition of 25 MOVA product groups with 60 known model identifiers
• Human-readable product names in the Homebridge log
• Safe read-only diagnostic mode for unverified models
• No commands are sent and no Matter accessory is published in diagnostic mode
• Sanitized compatibility reports without credentials, device IDs, custom device names, or room names

Important: these additional models are currently known test candidates, not confirmed compatible devices. Tested support remains limited to the MOVA E40 Ultra (r9504a and r5732a).

If you own another MOVA model—especially a P10 Pro Ultra Gen 2, P50, P60, P70, V50, Z60, Z70, S70, E20s, or E30—I’d really appreciate your help testing it safely.

Install the beta:

npm install -g homebridge-mova@beta

GitHub release:
https://github.com/Gh0str1s3n/homebridge-mova/releases/tag/v1.2.0-beta.1

npm:
https://www.npmjs.com/package/homebridge-mova/v/1.2.0-beta.1

Submit a sanitized model report:
https://github.com/Gh0str1s3n/homebridge-mova/issues/new?template=new-mova-model.yml

Homebridge MOVA is a verified, community-maintained plugin and is not affiliated with MOVA. Thanks to the F1nn-T/dreame-ha community project for its public model catalogue.

Feedback and testers are very welcome! 🤖

Hi everyone! 👋
I’ve released Homebridge MOVA, a verified community plugin that exposes supported MOVA robot vacuums to Apple Home as native Matter robotic vacuum cleaners.
Stable version 1.0.1 currently supports the MOVA E40 Ultra (mova.vacuum.r9504a and mova.vacuum.r5732a) with:
• Vacuum, Mop, and Vacuum + Mop modes
• Single- and multi-room selection
• Start, pause, resume, and return to dock
• Live battery and operational status
I’m now looking for owners of other MOVA models to help expand compatibility. The beta version 1.2.0-beta.0 can detect unknown mova.vacuum.* models and generate a sanitized, read-only diagnostic report.
In diagnostic mode, the plugin sends no control commands and publishes no Matter accessory. Reports exclude credentials, device IDs, custom device names, and room names.
GitHub: https://github.com/Gh0str1s3n/homebridge-mova
npm: https://www.npmjs.com/package/homebridge-mova
New model support form: https://github.com/Gh0str1s3n/homebridge-mova/issues/new?template=new-mova-model.yml
This is an unofficial, community-maintained, cloud-based integration and is not affiliated with MOVA. Feedback and testers are very welcome!

Hey everyone,

I successfully added my TCL Google TV to Homebridge using the homebridge-adb plugin (powering it on and off works great). Now I’d like to switch between HDMI inputs (HDMI 1, 2, 3) directly inside the Apple Home app, but I’m not sure how to set up the config properly.

Switching inputs works fine via the official TCL Home app on my phone, but I can't get it working with ⁠homebridge-adb⁠.

Hi I am new here. how can I make my apple tv to wake up and show my ring doorbell 4k cam when the ring doorbell is rang? Thank you!

As part of improving Homebridge, we are looking to include an automation engine within the UI that will make common smart-home routines easier to create and manage.

We’d love to hear your ideas for useful automation rules.

For example, Door Left Ajar:

Select a door and create a virtual “Ajar” contact sensor. If the door remains open for more than X minutes, trigger the sensor and retrigger it every Y minutes until the door is closed.

What automation rules would you find useful? Please share the trigger, any conditions, and the desired action.

Can somebody help me keep my home settings?

Node.js v24.19.0
[21/08/2026, 02:16:49] [HB Supervisor] Homebridge process ended. Code: 1, signal: null.
[21/08/2026, 02:16:54] [HB Supervisor] Restarting Homebridge...
[21/08/2026, 02:16:54] [HB Supervisor] Started Homebridge v2.4.0 with PID: 6077.
node:internal/modules/esm/resolve:201
const resolvedOption = FSLegacyMainResolve(pkgPath, packageConfig.main, baseStringified);
^

Error: Cannot find package '/var/lib/homebridge/node_modules/homebridge/node_modules/commander/index.js' imported from /var/lib/homebridge/node_modules/homebridge/dist/cli.js
at legacyMainResolve (node:internal/modules/esm/resolve:201:26)
at packageResolve (node:internal/modules/esm/resolve:778:12)
at moduleResolve (node:internal/modules/esm/resolve:859:18)
at defaultResolve (node:internal/modules/esm/resolve:992:11)
at #cachedDefaultResolve (node:internal/modules/esm/loader:701:20)
at #resolveAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:721:38)
at ModuleLoader.resolveSync (node:internal/modules/esm/loader:759:56)
at #resolve (node:internal/modules/esm/loader:683:17)
at ModuleLoader.getOrCreateModuleJob (node:internal/modules/esm/loader:603:35)
at ModuleJob.syncLink (node:internal/modules/esm/module_job:163:33) {
code: 'ERR_MODULE_NOT_FOUND'

[18/08/2026, 09:52:23] [Homebridge UI] Multiple instances of Homebridge were found, see https://homebridge.io/w/JJSgm for help.

[18/08/2026, 09:52:23] [Homebridge UI] /var/lib/homebridge/node_modules/homebridge

[18/08/2026, 09:52:23] [Homebridge UI] /opt/homebridge/lib/node_modules/homebridge

Anyone else see this? I am confident it's not a Node problem after troubleshooting it myself (with some CoPilot help 😄 )

looking for beta testers for a plugin that uses Google Cast, Android TV Protocol v2 and ADB protocols for adding, remote controlling and synchronizing playback status of google Chromecast/ android TVs.

sudo npm install -g github:vivekanandbv/Homebridge-ADB-Cast

Disclosure up front: I make BetterKey, the iOS app this bridges from.

I wanted to bring the passive automations from BetterKey into my smart home. I found that Home Arrival was something I would actually use and allowed the app to have a deeper integration for connected car/home automation enthusiasts. Sharing in case it's useful to others who would also be interested in BetterKey.

What it does:

• One motion sensor per vehicle, named {Vehicle} Parked at Home.
• Each time BetterKey confirms the car parked inside a home area you drew on the map, the sensor flips to "motion detected" for about 30 seconds and then back to "no motion." That's enough for Apple Home to run an automation like "when Forester Parked at Home detects motion after sunset, turn on the driveway lights."
• Dynamic platform, so vehicles are added and removed automatically as they show up in BetterKey.
• Polls the BetterKey API on a configurable interval (default 60s, range 30 to 600s). Confirmed arrivals persist server side for 24h, so a Homebridge restart during that window will still catch the event.
• Verbose logging option that records event ids and dispatch outcomes. The API key is never logged.

A few things worth calling out up front:

• Requires an active BetterKey subscription and the iOS BetterKey app with Home Arrival turned on (feature overview at https://betterkey.xyz/home-arrival). If you are not already a BetterKey user, this plugin will not be useful on its own.
• Arrival only. It never reports "away" or "not parked," and if iOS suspends BetterKey in the background a specific park can be missed. A missed trigger is inconvenient rather than unsafe, since nothing downstream is treating the sensor as authoritative presence.
• The comparison between "where the car is" and "the home area you drew" happens entirely on the iPhone. Only a short-lived arrival event (id, vehicle, timestamp) leaves the device for this plugin to poll. No coordinates, no radius, no vehicle location.

Install from the Homebridge UI by searching for BetterKey, or from the CLI:

npm install -g homebridge-betterkey

Repo, config, and troubleshooting: https://github.com/CMLabsLLC/homebridge-betterkey

Happy to answer questions or take device reports in the thread.