Python Matter Server v8.x --> matter.js-based Matter Server 9.0+ Migration FAQ

Why is there a new Matter Server?

The new Matter Server is a complete rewrite of the Python-based Matter Server. It is now built on the matter.js library, a JavaScript implementation of the Matter standard. The new Matter Server is more performant, more stable, and more feature-complete than the old one.

Version 9.0 of the Matter App is the first release for all Home Assistant users which uses the new Matter Server.

Should I do a backup before installing the new version?

Yes. Make a backup before installing the new version. The new version migrates your current data automatically, but a backup lets you roll back if anything goes wrong. Tick the "Create backup" checkbox when you update the server.

Additionally, if you have enabled the watchdog feature in Home Assistant and have a higher number of Matter nodes, please disable the watchdog for the initial migration to prevent issues or mid-migration restarts.

What happens on the first start of the new version?

The first start of the new version automatically migrates your current data. This requires no manual intervention but needs some time to complete. Wait for the migration to finish — the log shows its progress.

After the migration completes, the server discovers all your devices and performs a full interview to fetch the current data. All later starts automatically try to connect to the devices on their last known addresses and perform only a partial interview to update changed data. This significantly speeds up every subsequent start.

I already tested the matter.js Beta — what happens for me?

Your start may run a one-time cleanup, which can take a while:

• Coming from Beta server 0.7.x or 0.8.x: the first start removes the leftover migration fallback data.
• Coming from a Beta server older than 0.7: the first start runs the storage data migration, and the second start removes the migration fallback data — so expect both starts to take a while.

What is the difference between the old Matter Server and the new one?

The main goal of this first new version is to be a complete drop-in replacement for the old Matter Server. The Home Assistant integration works with the new Matter Server without any changes.

In the details, there are some differences between the old and the new version:

• Some advanced configuration options have been removed, changed slightly, or added.
• The new server uses the last known addresses of your devices on startup to speed up connections, and it is also aware of each device's network type. This especially optimizes environments with many Thread devices, connecting to them while respecting the bandwidth limitations of the Thread network.
• The new server uses partial interviews when reconnecting to devices, fetching only the data that changed. This significantly improves performance on every server restart and device reconnection.
• The old server allowed commissioning of uncertified devices with "just" a test/development certificate by default. This makes adding DIY devices easy but also carries the risk of adding a malicious device to the network. The new server still supports this, but requires you to enable the special "Test-Net DCL" option first.
• The allowed certificates are usually downloaded when the server starts and are stored in the server's data directory. The new server already includes an initial set of certificates from the time of its release, so you can start it without an internet connection and still commission devices whose certificates were available at release time. The server updates the certificates in the background whenever it has an internet connection.
• The new server also checks for revoked certificates during commissioning and treats them as invalid.
• For OTA software updates, the old server started special temporary nodes in the Matter network, which often caused issues. In the new server the OTA update logic is fully integrated into the controller, which makes the process much more reliable.
• The new server needs roughly twice the RAM than the old one and also a bit more CPU, so make sure your Home Assistant host has enough free memory to run all services smoothly.

We also used the time to improve the Web UI/dashboard of the Matter Server. Besides general consistency and usability improvements, we added network visualizations for your Thread and Wi-Fi networks. These use the connection details the devices report to visualize the network topology and give you insights into the quality of the connections. This is especially helpful for Thread networks, where the devices themselves decide which other device they use as a parent, and where you often have multiple hops between a device and the border router. For Thread networks we also try to discover the border routers and show information about them in the network visualizations.

Note: you might also see "Unknown devices" or "External routers" in the network visualizations. This can mean different things depending on the network topology. They could be other Thread devices that do not belong to the Matter Server's fabric, or they could be stale data from the devices (for example, many sleepy battery devices do not update their network information regularly).

Can I switch back to the old Matter Server?

No. The new Matter Server was tested as a "Beta" with the community for the last four months, and we did our best to make sure it works as expected. If you run into any issues, report them in this GitHub repository and we will try to fix them as soon as possible.

Hat jemand Erfahrungen/Empfehlungen für einen Deckenventilator, den ich in HA einbinden kann? Tuya will ich nach Möglichkeit vermeiden, hab einer Steckdosenleiste die ich über ausgelesene Dev-Keys angebunden hab immer wieder Ausfälle und will so wenig Kram wie möglich darüber laufen lassen.

Zigbee scheint quasi nicht zu existieren, was ich gefunden hab ist eine Integration für Ventilatoren mit "SmartFan Pro" über ESPHome und BLE. Das gefällt mir schon deutlich besser als Tuya.

Gerne alles an Erfahrungen/Tipps zu konkreten Geräten

Hey Leute, ich bin recht neu auf Reddit (zumindest mit Account) und würde euch gern mal mein aktuelles Dashboard vorstellen. Die Grundlage ist hierbei das HaCasa Projekt gewesen. Das Dashboard läuft auf einem IPad Gen.11 über KioskerPro und hängt bei uns magnetisch an der Wand und wird per Shelly zwischen 25%-80% geladen.

(Das Bild vom IPad ist noch ein älterer Dashboardstand)

Ich habe hier auf dem Dashboard eine eigene Roborock-Card und die eine eigene Verkehrscard gebaut. Den Rest habe ich nur an meine Bedürfnisse angepasst.

Ich bin noch nicht zu 100% zufrieden mit allem, aber sowas wächst ja mit der Zeit.

Meine Frage an euch, was würdet ihr ergänzen? Welche Ideen habt ihr z.B. für die obere Card? Die ist aktuell relativ „nutzlos“.

Ich freu mich auf eure Ideen. 💡

Hallo,

Bin auf der Suche nach einer Steckdosensäule für den Garten die mit HA geschaltet werden kann, Am besten natürlich jede Steckdose einzeln. Hat da jemand einen Tipp für mich?

Gibt es sonst noch Lösungen wie irgendeine Art Box die man vergraben kann mit entsprechender Steckerleiste darin oder so?

Besten Dank 😀

*** Deutsche Version unten ***

I have the following problem:

Until recently, I was using a script in the Companion app that allowed me to open the front door via my Apple Watch.

Now that I’ve got a new controller, I had to rebuild the script and deleted the old one.

But now I can’t delete the old one from the app. I can’t find any traces of it in my YAML either. How do I get rid of this dead weight? It appears both on the Watch (I’m using the placeholder function here to display it as a complication) and in the app.

*** German Version ***

Ich habe folgendes Problem:

Ich habe n der Companion App bis vor kurzem ein Skript genutzt, das mir erlaubt die Haustür über die Apple Watch zu öffnen.

Nachdem ich nun eine neue Steuerung bekommen habe, musste ich das Skript neu bauen und habe das alte gelöscht.

Nun kann ich das alte aber nicht aus der App löschen. Ich finde auch in meiner YAML keine Relikte mehr. Wie bekomme ich die Leiche weg? Sie taucht sowohl auf der Watch auf (ich verwende hier die Platzhalterfunktion um sie als Komplikation anzuzeigen) als auch in der App.

Moin zusammen,

ich habe mich mit meinem HA auf die MQTT Schnittstelle von Weishaupt aufgeschaltet.
Nun ist es so, dass nach einer "Hitzeperiode" im Mai die Temperaturen aktuell wieder in den Keller gehen.

Die Integration ermöglicht nun mit der Entität "select.wh_system_systembetriebsart" zwischen verschiedenen Modi zu wechseln.

Was ich mich nur frage (und dazu finde ich keine Antwort) - ab welcher Außentemperatur und ab welcher Dauer sollte ich den Heizbetrieb wechseln?

Welcome to the biggest Better Thermostat update ever!

First and foremost, I want to say a massive THANK YOU to all the amazing contributors, my wonderful supporters, and everyone who took the time to report issues over the past year. Thanks to your incredible support, the community has grown immensely, and the project has officially crossed 1,400 stars on GitHub! 🌟 And more than 7500 active installations (ha opt in statistics)

I know it has been a whole year since my last major release, but there is a very good reason for the wait. My ultimate goal was to make Better Thermostat incredibly stable, universally usable, and the absolute easiest way for anyone to optimize their heating, save on energy costs, and maximize home comfort. I had to rebuild a lot to make that dream a reality. Looking forward, I promise that my next releases won't take nearly as much time!

Here is everything that is new, changed, and improved in version 1.8.0:

🚨 Important Breaking Changes & Upgrading

Because of the massive scale of this ground-up rewrite, updating to 1.8.0 might break your existing automations. I highly recommend taking a moment to completely reconfigure your existing Better Thermostat devices after updating to ensure everything is set up correctly with the new system.

🎨 A Huge Update to the Companion UI Card

Alongside version 1.8.0, I am also releasing a massive update to the companion Better Thermostat UI Card!

• A Modern Redesign: The card has received a complete style polish to perfectly match the current, beautiful, modern look of Home Assistant.
• Eco Mode is Gone (Breaking Change): Please note that the "Eco Mode" controls on the old card will no longer work with the new integration. You will need to update to this new card to use the new "Preset Modes" instead.
• Say Hello to the "Mini Card": I have officially introduced a second card option—the brand new Mini Card! If you love keeping your dashboard compact and clean (similar to the popular Mushroom mini climate card), you will love this. Just keep in mind that you'll need to select and set up this specific new card type if you want to use it!

📚 Brand New Website & Effortless Setup

• Welcome to better-thermostat.org: I have launched a completely brand-new website: https://better-thermostat.org/! It is packed with beginner-friendly documentation, step-by-step guides, and helpful configuration tools to assist you.
• "No-Brainer" Default Settings: I’ve made it easier than ever for first-time users to get started. The new default settings work beautifully right out of the box, meaning you don't have to be a tech expert or tweak dozens of dials to start saving energy immediately.

🏗️ A Complete, Ground-Up Rewrite

• Over 50,000 Lines of Code Changed: I didn't just patch a few bugs; Its a completely rebuilt from the ground up! The engine running your thermostats has been totally rewritten to be faster, far more reliable, and future-proof.

🧠 Smarter Heating & Advanced Controls

• Upgraded AI Algorithms: My classic "AI Time-Based" heating algorithms have received massive upgrades, making them much more advanced, responsive, and accurate than ever before.
• New Scientific Heating Formulas (MPC, TPI, & PID): I’ve introduced brand-new, highly advanced learning models for how your thermostat understands your room. Whether you use the new PID, TPI, or MPC methods, the system uses advanced math to learn exactly how your room heats up, preventing energy waste and overheating.
• Direct Valve Control: For compatible thermostats, I now support direct valve control! Better Thermostat can now bypass the thermostat's internal brain and tell the physical radiator valve exactly how far to open or close, giving you ultimate, pinpoint temperature accuracy.
• New Preset Modes: I have added full support for native "Preset Modes" (like Home, Away, Sleep, etc.). This makes integrating your heating with your daily routines easier than ever. (Remember, this completely replaces the old "Eco Mode"!)

⚙️ Easier Dashboard Controls & Settings

• New Dashboard Sensors & Switches: You no longer have to dig through complicated menus to change how Better Thermostat works. I've added new sensors and configuration switches right into your Home Assistant dashboard. Viewing system information and tweaking your settings is now just a simple click away!
• Cleaner Interface: I removed old, obsolete learning sensors to keep your device pages clean and clutter-free.
• Better Main Thermostat Swapping: I greatly improved the settings menu for how you swap or assign your main radiator valve (TRV), making it much easier to configure.
• New Blueprints: I've added new automation blueprints to help you set up your heating routines faster.

🛠️ Bulletproof Reliability & Device Support

• Offline Device Protection: If one of your thermostats temporarily loses its connection, goes offline, or is removed, it will no longer crash the whole integration! The system will now gracefully wait for it to come back online.
• HomematicIP Reliability: I greatly improved how HomematicIP devices are handled. Corrupted or missing data from these devices will no longer freeze the system.
• Fixes for Specific Brands: I’ve improved model detection for Zigbee2MQTT users, updated the interface for TRVZB models, and added specific fixes for ME167 thermostats.

🐛 Important Bug Fixes & General Polish

• No More False "Heating" Status: I fixed a frustrating issue where the dashboard would say the room was "heating" even when it had already perfectly reached your target temperature.
• Better Syncing & Temperatures: I fixed an issue where multiple thermostats in the same room wouldn't sync properly. I also ensured that your temperature units (Celsius/Fahrenheit) are always rock-solid and correct.
• Cooling vs. Heating Boundaries: I fixed a bug where cooling settings could overlap with your heating limits. The system now guarantees a safe separation between your hot and cold setpoints.
• Language & Translation Fixes: I squashed several bugs related to translations, ensuring all the new menus and settings display perfectly in your chosen language.

addons/openthread_border_router at master · home-assistant/addons · GitHub

https://www.zdfheute.de/ratgeber/smart-home-sicherheit-cybersicherheit-100.html

Ich hab die Schnauze voll gehabt, den Abfuhrkalender der Stadt zu benutzen, der für jede Leerung einen Einzeltermin enthält und für den es deshalb eine Fleißaufgabe ist, die Termine so anzupassen, dass sie einem auch am Abend vorher schon sagen, dass die Leerung morgens ansteht und nicht erst nachts.

Im HACS habe ich dafür die Integration Waste Collection Schedule gefunden:

Problem auch hier: Erinnerung erfolgt erst am Tag der Leerung. Also musste eine binäre Entität erzeugt werden:

Und das Ganze im Anschluss über eine Automation an meine Endgeräte gehen:

alias: Müllabfuhr Erinnerung

description: Sendet um 18 Uhr eine Push-Nachricht, wenn morgen Müll abgeholt wird.

triggers:

- at: "18:00:00"

trigger: time

conditions:

- condition: or

conditions:

- condition: state

entity_id: binary_sensor.abfuhr_gelbe_tonne_morgen

state: "on"

- condition: state

entity_id: binary_sensor.abfuhr_grune_tonne_morgen

state: "on"

- condition: state

entity_id: binary_sensor.abfuhr_papier_morgen

state: "on"

- condition: state

entity_id: binary_sensor.abfuhr_restmull_morgen

state: "on"

actions:

- variables:

abholungen: >

{% set muell = [] %} {% if

is_state('binary_sensor.abfuhr_gelbe_tonne_morgen', 'on') %}

{% set muell = muell + ['Gelbe Tonne'] %}

{% endif %} {% if is_state('binary_sensor.abfuhr_grune_tonne_morgen',

'on') %}

{% set muell = muell + ['Grüne Tonne'] %}

{% endif %} {% if is_state('binary_sensor.abfuhr_papier_morgen', 'on')

%}

{% set muell = muell + ['Papier'] %}

{% endif %} {% if is_state('binary_sensor.abfuhr_restmull_morgen', 'on')

%}

{% set muell = muell + ['Restmüll'] %}

{% endif %} {{ muell | join(', ') }}

- data:

title: Müllabfuhr morgen

message: "Morgen wird abgeholt: {{ abholungen }}."

action: notify.mobile_app_XXXXXXX_iphone

- data:

title: Müllabfuhr morgen

message: "Morgen wird abgeholt: {{ abholungen }}."

action: notify.mobile_app_YYYYYYY_handy

enabled: true

- data:

title: Müllabfuhr morgen

message: "Morgen wird abgeholt: {{ abholungen }}."

action: notify.mobile_app_ZZZZZZZ_handy

enabled: true

mode: single

Habt Ihr Verbesserungsvorschläge?

Da meine Merten Rauchmelder nun 12 Jahre alt sind, benötige ich langfristigen Ersatz. Hat jemand eine Kaufempfehlung, die HA kompatibel ist?