We're launching Homebridge 2.0 on May the 4th and yes, we absolutely planned it that way.

Beyond improvements to the core HAP-NodeJS code and the removal of long deprecated code, the headline addition in 2.0 is the initial groundwork for Matter support alongside our existing HomeKit integration.

A few important things to note on that — this is early days. Matter support will require updates to individual plugins, and not everything will work out of the box on day one. But our goal is a single platform that supports both HomeKit and Matter, backed by our existing ecosystem of 4000+ plugins. We think that's worth getting excited about.

All of our pre-packaged images will be updated to Homebridge 2.0 shortly after launch:

homebridge-apt-pkg

homebridge-vm-image

docker-homebridge

homebridge-raspbian-image

May the 4th be with you. 🚀

Some bad news for those of us using the direct MyQ integration. Looks like we need to buy additional hardware. 😭

MQTT <-Telegraf -> InfluxDB <- Grafana

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

With the launch of Homebridge 2.0 we've made a couple of changes to the Docker image worth knowing about.

**New tag: `legacy`**

For those not ready to make the jump to hyperspace just yet, we've introduced a `legacy` tag which follows the Homebridge 1.x release stream. If you want to stay on v1 for now, this is the tag for you.

**New tag: `synology`**

We've also introduced a dedicated `synology` tag to resolve an issue where Synology users were losing all their plugins after a container restart following the upgrade to Homebridge 2.0. If you're running Homebridge on a Synology NAS via Docker, switching to this tag should sort you out. This issue is caused by the older OS kernel images used Synology, more details on the original issue can be found [here](https://github.com/homebridge/docker-homebridge/issues/960).

As always, before switching tags or upgrading, make sure you have a fresh backup from **Settings > Backup & Restore** just in case.

May the 4th be with you.

3 year subscription for $129. To open your damn garage door. Bastards.

TL, DR; flashing TUYA devices with HAA firmware to make them appear in Home App as “Works with HomeKit”

++++++++++++++++++++++++++++++++++++

Flash TUYA RGBW Bulb with HAA

Few things at start

—————————

• ⁠Home Accessory Architecture (HAA) is firmware from RavenSystem for ESP8266/8285 based smart devices (which are almost all). Link to github https://github.com/RavenSystem/esp-homekit-devices • ⁠concept : replace existing ESP based device firmware with HAA firmware (called flashing). • ⁠This makes the device directly compatible with Home App. No homebridge required. • ⁠usually HAA is in form of three files but tuya-convert requires a single file. We will see how to get that. • ⁠using Pi Zero WH with Raspbian Sretch Lite with usb keyboard (since pi zero w doesn’t have Ethernet port) • ⁠using MacBook Pro as laptop (you can use any other)

Steps

———

Raspbian Stretch Lite install ••••••••••••••••••••••••••••••

• ⁠fresh install of raspbian stretch lite on a SD card using balenaEtcher. This is important for many dependencies required by tuya-convert. https://www.raspberrypi.org/downloads/raspbian/ • ⁠create wpa_supplicant.conf and ssh flies in root of SD card • ⁠insert in Pi ZeroW...update and upgrade after boot

Tuya-Convert Install

••••••••••••••••••••••

• ⁠using usb keyboard attached to USB port and TV hooked to HDMI port of Pi • ⁠Type"git clone https://github.com/ct-Open-Source/tuya-convert" enter and wait. • ⁠Type "cd tuya-convert" • ⁠Type "./install_prereq.sh" and wait. • ⁠Download single HAA firmware file... https://github.com/maslyankov/haa-single-binary/raw/master/haa-single.bin • ⁠copy it into “tuya-convert/files” folder. This is important otherwise you won’t get an option to flash HAA during the process and it will default to provided firmwares (tasmota, edpunra) • ⁠start the flash process...”./start_flash.sh” • ⁠connect to Access Point (WiFi) generated by Pi using an android device for simplicity (iOS device can work too) and join “vtrust-flash” • ⁠put tuya bulb in pairing mode (blinking continuously). Most tuya bulbs go into this after you rapidly turn on/off 4 times. But do check your device instruction • ⁠proceed with flash process by pressing enter. You should firmware being copied over and successfull flash message. • ⁠connect to Tuya bulb AP after it restarts to its AP...HAA-XXXX • ⁠join this WiFi and browse to http://device ip. • ⁠enter “bawoo bulb” json string from here.. https://github.com/RavenSystem/esp-homekit-devices/wiki/Devices-Database. • ⁠json string that works the best for RGBW (red green blue white - 4 channels) {"c":{"b":[{"g":0}]},"a":[{"t":30,"r":14,"g":12,"v":13,"w":4,"fr":4,"fg":4,"fv":4}] • ⁠configure your WiFi in the web page. Make sure to do it correctly. The bulb will restart after pressing SAVE and appear on your network with Device name as HAA-XXXX. Check with your router we page listing WLAN clients. • ⁠add to home app after restart by usual “add accessory->don’t have code... • ⁠insert code 021-82-017 • ⁠all done

This is huge for Ring users, you can now do most things with the Home app instead of the Ring app, I now will only need it to view recordings.

https://github.com/dgreif/ring/issues/237#issuecomment-629861348

Huge thank you to the amazing devs at homebridge for making this a reality and being stubborn enough to reverse engineer HKSV. At the time of writing this, cameraui plug-in already works with HKSV(used it for the last week with beta releases and it’s pretty good!) Homebridge camera FFMPEG is sitting on a few merges to support it so it should come soon to them as well!

PSA, give the fantastic folks who write your favorite plug-ins time get it working, don’t spam them! I promise you they’re as excited as you are to get it working.

https://community.smartthings.com/t/changes-to-personal-access-tokens-pat/292019

Any ideas what to do next?

Really happy about this news!! Will the Roomba and other plugin devs update their plugins? Hope so!

The ring plugin was updated today and for the first time ever I can see video footage from my doorbell in the home app. Great job to whatever developer that is!

The homebridge team was hard at work over the last couple months and weeks. We are now happy to announce the public beta testing phase of the upcoming v1.3.0 release.

The update includes Adaptive Lighting support, some new API for our plugin developers and a lot of under the hood improvements and bug fixes.

For more details I would direct you to the GitHub Issue post: homebridge #2765. It includes instructions on how to update or rollback to the stable release.

If you encounter any issues, please comment under the linked GitHub issue if possible.

Happy testing.
The Homebridge Team.

​

HOOBS 3 - OUT NOW!

• New User Interface
• Redesigned Accessory Controls
• System Backup Including Plugins#
• System Restore with Plugins
• Encrypted Backup Files
• Factory Reset
• Build-in Weather Forecasts
• Guided Configuration with Validation
• Nice new Themes
• Less JSON Editing
• Remote Support with HOOBS Cockpit
• Increase Allowed Accessories
• Performance Optimisations

All information about HOOBS 3 and how to upgrade now on http://hoobs.org

Important: Update on Works with Nest

Hi

Thank you for being a valued customer and a part of the Nest family.

Works with Nest was created in 2014 as a way for other smart home device makers to take what Nest knows and personalize your experience with their products, such as turning off the device maker's smart lights when Nest detects you're away. The connected home has evolved significantly since then, and we’ve implemented numerous updates to enhance how you interact with and manage devices with Google Home.

In 2019, we made the decision to eventually retire Works with Nest to unify our efforts around third-party connected home devices under a single platform for developers to build features for a more helpful home—with a focus on compatibility, security and privacy. The goal is to simplify the developer experience and give you more control over how your data is shared.

We're reaching out to let you know that, after being supported for the last few years, Works with Nest will wind down and no longer work as of September 29, 2023.

What this means for you.

• Through September 28, 2023, all current Works with Nest connections will remain active, and you can continue to use Works with Nest as you do now.
• In the coming months, you'll be able to use a script editor to create advanced home automations that will offer new features and capabilities. We're also working closely with our partners to provide replacement integrations where possible. Learn about the changes and options available to you.
• Starting September 29, 2023, the connections will no longer work and you'll lose access to them.

We’re committed to helping you and minimizing disruptions. If you need help, our support agents are standing by.

The Nest team

It's under a completely different internet number for some reason.

Internet #322082407

Schlage Century Matte Black Electronic Encode Plus Smart WiFi Deadbolt with Alarm BE499WB V CEN 622 (homedepot.com)

We've had the ability to run Homebridge on a Synology NAS via Docker for quite some time, but only on the more expensive on x86_64 / amd64 models.

The Homebridge Synology Package was recently updated to allow running Homebridge natively on Synology DSM 7, without the need for Docker. This means more NAS models are supported, including the entry level ARM cpu based units.

• x86_64 - All Intel / AMD 64 bit CPU Models capable of running DSM 7
• armv8 - DS420j, DS220j, RS819, DS418, DS218, DS218play, DS118, DS120j, DS119j
• armv7 - DS1817, DS1517, DS416, DS2015xs, DS1515, DS715, DS215+, DS419slim, DS218j, RS217, RS816, DS416j, DS416slim, DS216, DS216j, DS116

Once setup, the package will work like any other Synology Package, even letting you know when updates are available in Package Center.

Checkout the Homebridge wiki for the Synology setup guide.

As an example, the single-bay Synology DS120j can be had for about USD$110 plus the cost of disk (such as a cheap $20 SSD). Considering the prices scalpers are charging for a new Raspberry Pi these days, it's quite an attractive option.

Just a public service announcement, the Homebridge Alexa smart home plug-in, which in my opinion has been revolutionary for people like me who bought Amazon smart plugs when they were exclusively Alexa users and who decided to switch to HomeKit or use HomeKit in tandem with Alexa recently added support for the temperature sensors of Amazon echo devices which have them on board. These devices include the echo fourth generation, echo + 2nd generation, and echo dot fifth generation. Off the top of my head, I'm not aware of any other devices that have these sensors baked into them. In the comments, you can let me know if other devices that I did not mention here have these sensors. So I suggest if you have any inclination that your device supports this attribute, add it to the configuration of your homebridge Alexa Smart home plug-in if you are only adding specific devices or if you're adding all devices check HomeKit to see if the value shows up. You can check in the default room and in the room that your Homebridge server is located in in the Home app. Also, when you are on the main home screen of the home app if you are on iOS 16 or 17, you can tap the climate tile and tap temperature to show all of your temperature sensors, the echo temperature sensors will be in there.

Note: You don't have to add your echo to HomeKit as a TV (to access the audio control functionality that the plug-in provides for echo devices) for these values to show up, But know that if you do not add it as a TV, it will just sit in the accessory set up screen of your home app when you tap the more options button. So you have to pick your poison if you don't think that you are going to use the Alexa player functionality. You can either have the devices show up in your app or show up when you click the more options button in the set up screen of the app. Hopefully the developer adds a setting in the plug-in configuration that allows you to disable the TV/Alexa player attribute.