u/NorthernMan5

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.

https://preview.redd.it/xzexze5rhfzg1.png?width=2140&format=png&auto=webp&s=d3f1b28e7bb791e6827d015dcfa1f1f7cad9bfa1

Not sure if I posted this here already, but this is something from my archives, when I was diving and we shot the same turtle from slightly different angles.

Camera on the left is a DJI Osmo Action 5 Pro, and the right is a GoPro 11, with a red filter. As the GoPro does not have on camera colour correction, without the red filter it is truly awful.

We are at slightly different angles to the turtle, so there are some color differences there due to that.

So thought I would share this to help people with a real world example of DJI vs GoPro, and let them see.

edited: minor grammar

Homebridge 2.0 is here! Before you make the jump to hyperspace, here are a few good hygiene steps to take before upgrading.

1. Download a Backup

Before any major upgrade, take a fresh backup of your Homebridge environment. Head to **Settings > Backup & Restore** and hit **Backup Now** to generate and download an up-to-date backup file to your local machine. Keep it somewhere safe.

2. Run the v2 Readiness Check

In the **Update Information** section, click the orange **ⓘ** icon next to Homebridge to see how your plugins stack up against v2. Green checks are good to go, amber question marks are worth investigating before you upgrade.

3. Check your Readiness Check results

If you have any amber question marks from step 1, check with the individual plugin authors for v2 compatibility updates before proceeding. When in doubt, hold off a little — the Rebellion will still be here.

Once you're satisfied everything is in order, you're clear for launch. May the 4th be with you.

For those who want to stay on v1 for now — the Outer Rim dwellers, the ones still flying a perfectly good Millennium Falcon — we've got you covered.

You won't be bombarded with update notifications pestering you to upgrade. In the Homebridge UI, head to the Update Information section and select Homebridge and enable Ignore Major Versions. This will hide notifications for the v1 to v2 upgrade, but you'll still receive minor and patch updates to keep your v1 install happy and secure.

No pressure, no rush. The Rebellion will still be here when you're ready.

https://preview.redd.it/adjfpukqviyg1.png?width=798&format=png&auto=webp&s=52350dc30071af1aaf0529e5ee51e8f1dd8c6384

May the 4th be with you.

A few weeks back we announced Homebridge 2.0 and the initial Matter support coming with it. 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.

We got a lot of questions about why Matter, and what it actually means for Homebridge — so here's a bit more context.

There are two use cases we're targeting:

Use case 1 — Filling gaps in HomeKit device support

Apple has started using Matter for new device types rather than adding them to HomeKit directly. Vacuums are a recent example — Apple added vacuum support to the Home app, but via Matter, not HomeKit. Our goal is to bridge that gap so Homebridge plugins can deliver full functionality for these device types. We think this is very achievable and the more immediate target.

Use case 2 — Using other Matter controllers with Homebridge plugins

This would allow your Homebridge plugins to be accessible from other Matter controllers, like the Aqara app for example. This one is more of a longer term effort — it will require individual plugin updates to support, so expect this to roll out gradually over time.

Our goal remains a single platform that supports both HomeKit and Matter, backed by our existing ecosystem of 4000+ plugins.

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

Hopefully that clears up the direction we're heading. As always, happy to answer questions below.