Alarm-System in Home Assistant

KingDando · February 11, 2026, 7:24pm

Has anyone found a way to integrate the Aqara alarm system, which is also displayed in HomeKit, into Home Assistant? I have already connected both hubs (Hub M3 & Doorbell Camera Hub G410) to HA via Matter. So far, all Zigbee devices and Matter-exposed states are shown to me there (exclude the camera stream, but it doesn’t matter).

This is the security system which I mean:

Marc3k · February 12, 2026, 3:17am

Hi! Matter does not currently support alarm systems.
So for now, the only way to make it work with Home Assistant is through HomeKit integration.
Hope that helps clarify things

KingDando · February 12, 2026, 7:18am

Yes, I already knew that. Thought maybe someone managed to solve the problem by detours.

JohnD · February 12, 2026, 7:40am

I now have several Aqara hubs, including the G3. As I didn’t have any devices connected to the hub via Zigbee, and I wanted to display the camera image in Home Assistant, I removed the hub from Apple Home and connected it directly to Home Assistant.

A HomeKit connection can only exist with one system, so you must first remove the hub from Apple Home. However, this will also remove all sub-devices from the hub in Apple Home. This is, of course, irrelevant if there are no sub-devices.

However, if you have sub-devices or want the camera image in Apple Home too, you can reconnect the hub to Apple Home via HomeKit Device Integration.
The connection would then be:

Aqara Hub → HomeKit (connection) → Home Assistant → HomeKit → Apple Home Hub

Once the hub is connected directly to Home Assistant via HomeKit, you can also use the alarm system. And since the other hubs are connected to Aqara Home and Apple Home, I can activate and deactivate the alarm system on all three systems simultaneously.

At the moment, I’m not sure whether the alarm system will also be passed on via the HA HomeKit connection in Apple Home. Probably yes, so it could also work with just one hub.

This is how it looks in my dashboard:

Appearance and details can be adjusted.

Check out this post, it might be interesting too:

KingDando · February 12, 2026, 10:08am

Yes, I’ve already looked at the way, but my plan was to somehow get it done without having to remove it in HomeKit.

JohnD · February 12, 2026, 10:37am

Okay, then of course there’s still the option of Advanced Matter Bridging.

In the Aqara app, create a scene for each alarm mode, e.g., activate night alarm and deactivate night alarm, etc.
Then go to Profiles → Connect to Ecosystems → Matter → Scene and Signal Sync → Scene Sync → Create all the scenes as Matter signals.
Since you already have the hubs in Home Assistant, the scenes should then be available there as switches.
To know the status of the alarm system in HA, you need to go to Aqara App → Profile → Connect to Ecosystems → Matter → Scene and Signal Sync → Signal Management → Plus button at the top right → then under IF → Add → Alarm System → select Mode (Home/Away/Night) → Arm → then follow the instructions until the signal has been created.
The signals should then appear as Occupancy sensors and be displayed as occupied whenever the respective alarm is active and as unoccupied when disarmed.

You can then build something for your dashboard yourself using the switches and occupancy sensors in HA, and of course you can use it in automations.

KingDando · February 12, 2026, 10:56am

That’s a good idea. I think I try it.

pmacpherson · March 4, 2026, 6:13pm

hi there… doing it this way, can you also change alarm system status in HA that reflect in the aqara system (ie. in the reverse), or is it one way only?

JohnD · March 4, 2026, 6:21pm

Yes, it works both ways!

HA → Aqara: You use the switches (Matter Scenes) in Home Assistant to trigger the alarm modes in the Aqara system.
Aqara → HA: The Occupancy sensors provide the feedback so Home Assistant always knows which mode is currently active.

It’s a full loop: you can control the alarm status from HA, and HA reflects any changes made directly in the Aqara app.

pmacpherson · March 5, 2026, 5:55am

KingDando:

Ok… i think i found a way - I have a similar setup as you, an M3 hub and g410 camera hub. the best part is you wont need to setup scenes or any automation for this solution, which i think is elegant and works best.

setup the g410 camera hub to homekit only. you get the benefit of HKSV camera, motion sensor, and all the built-in functionality. if youve got it routed through HA, remove it from HA and put it back to HK. you wont need it at all in HA for alarm control.
if you already have the m3 hub setup in homekit, then remove it from there
add the m3 hub to HA as a homekit device
add the now present “Aqara alarm card” for the alarm states in HA - make sure to enable all four alarm states in the config
now add the m3 hub back to homekit via HA’s homekit bridge - I wont go into all the details of this but there are tutorials for doing this - you basically need to create a homekit bridge that contains only the M3 as a single device in accessory mode (select alarm system for the bridge/then change it from exclude to include and accessory - then select the M3)
confirm you can see M3 hub and its alarm states in homekit
add the alarm card in Aqara app on the main dashboard - “select edit and add the alarm card” (and go through the initalization / guard mode process) *** THIS IS SUPER CRITICAL as it links all your alarms together ***

thats it.

both the G410 and M3 alarm states are now in sync. now on HA you can put the m3 alarm in any mode (night/away/home/disarm) and it will immediately reflect in aqara app and homekit as well. (in homekit you will see both G410 and M3 get the same alarm states) which is what i think you are looking for. this also works in any direction - you can control both from aqara app via the alarm card, or via homekit by changing the alarm state in either the G410 or M3!

this opens up many possibilities now in HA as you can create all kinds of automations that will control the alarm state to a fine degree without the use of any automations or scenes in HK or Aqara. I plan to build out some pretty sophisticated ones with some aqara motion sensors, some ikea door/window sensors and geolocation in HA.

Good luck! let us know how it goes.

KingDando · March 5, 2026, 2:49pm

@JohnD I hab das was mir mir empfohlen hast vor ein paar Tagen umgesetzt. Home Assistant kann den Modus vom Alarmsystem easy ändern und das funktioniert auch super schnell. Aus irgendeinem Grund funktionieren die Sensoren zur Erkennung welcher Mode aktiv ist, nicht oder nur sehr unzuverlässig. Den Alarm ausgelöst konnte ich noch nicht testen, weil der Alarm bei uns schon lange nicht mehr ausgelöst hat.

Hast du eine Idee was ich anders machen kann?

@pmacpherson , integrating the Aqara Hub(s) via HomeKit Device to HomeAssistant is certainly an option, but I prefer not to do so because the Aqara Hubs are already integrated into Apple Home with all the Zigbee devices and automations.

JohnD · March 5, 2026, 4:02pm

Ich nutze das ja nicht so. Ich nutze meinen G3 Hub über die HomeKit-Verbindung in Home Assistant, wie im ersten Beitrag beschrieben.

Aber ich werde meinen Nachtalarm als Matter-Signal einrichten und testen. Mal sehen, ob es bei mir funktioniert oder ob auch ich Probleme habe. Da es eigentlich recht unkompliziert ist, gehe ich davon aus, dass man bei der Einrichtung des Signals auch nicht wirklich etwas falsch machen kann. Ich melde mich in ein paar Tagen wieder.

JohnD · March 6, 2026, 8:25am

Zwischenstand: Es funktioniert bisher zuverlässig, egal ob der Nachtalarm über Siri, Szenen, HomeAssistant, Aqara App oder Zeitsteuerung aktiviert/deaktiviert wird.

Zum Vergleich das Log aus der Aqara App (erstes Bild links oder oben, je nach Bildschimbreite) und die History aus Home Assistant (zweites Bild rechts oder unten):

Mein Setup besteht aus einem G5 Pro Kamera Hub als Matter-Controller mit eingerichtetem Matter-Signal. Hier ist noch ein Screenshot vom Matter-Signal aus der Aqara-App (im Grunde ganz simpel):

KingDando · March 6, 2026, 3:17pm

@JohnD Danke dir. Ich hab jetzt auch nochmal nachgeschaut bei mir. Wenn ich den Alarm Mode ändere (hab jetzt nur in der Home App getestet aber die Automationen über Buttons laufen auch über HomeKit (größtenteils) deswegen passt das. Bei mir werden die „Belegungen“ in Home Assistant auch als „Belegt“ angezeigt nach dem Wechsel.

Was man jetzt aber auch sieht, das der Home Modus Belegung in Home Assistant irgendwann kein Bock mehr hat und aus geht bzw als „Frei“ anzeigt.

Den Alarm ausgelöst konnte ich nicht testen, weil sonst alle alarmiert werden. Das mache ich wann anders.

KingDando · March 9, 2026, 7:20pm

@JohnD Ich hab jetzt mal ein paar Tage vergehen lassen und dann vorhin gerade nochmal in Home Assistant reingeschaut und hab gesehen das es A) ein Update für den Matter Server gibt und
B) die Sensoren über den Home-/Away-/Night-Mode zum Teil einfach falsch sind.

Vorhin war der Anwesenheitsmodus in Aqara Home und Apple Home aktiviert. Aus irgendeinem Grund meint Home Assistant aber, dass der Nachtmodus aktiv sei. Dachte erst das ich die Matter Sensoren oder wie die bei Aqara heißen falsch eingestellt hab und nochmal gecheckt, hat aber alles gepasst. Jetzt weiß ich auch nicht mehr…

JohnD · March 9, 2026, 10:06pm

Schau mal unter Einstellungen → App (früher Add-Ons) → Matter Server → Konfiguration

Steht das „Matter SDK Log Level“ auf „error“?

Falls ja, dann schau mal unter „Protokoll“, ob du irgendwelche Fehler siehst?

Alternativ: Bei Amazon gibt es den E1 Hub grade im Angebot für ca. 20 Euro oder den M100 für ca. 25 Euro. Die könntest du dann in Home Assistant direkt einbinden.

KingDando · March 11, 2026, 6:17pm

Ich hatte tatsächlich schon die gleiche Idee einen Aqara Hub Stick nur für HA zu kaufen. Ich hab aber nicht rausfinden können ob die an die FritzBox angeschlossen werden können und dann LAN nutzen bzw Internet über USB (Fritz!Box unterstützt das nämlich).

Ich hab dir hier noch ein Ausschnitt vom Matter Server Error Log (ziemlich viele Fehler habe hoffentlich nix geleakt)

2026-03-10 19:17:14.826 (Dummy-2) CHIP_ERROR [chip.native.CTL] Remove Current Fabric Failed : src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-10 19:17:14.826 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to unpair device: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-10 19:17:14.827 (MainThread) WARNING [matter_server.server.device_controller] Removing current fabric from device failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-10 19:17:16.163 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:164i with Node: <0000000000000023, 1> S:1836 M:119242298] (S) Msg Retransmission to 1:0000000000000023 failure (max retries:4)
2026-03-10 19:17:40.955 (Dummy-2) CHIP_ERROR [chip.native.DMG] Time out! failed to receive report data from Exchange: 164i with Node: <0000000000000023, 1>
2026-03-10 19:17:40.956 (MainThread) ERROR [matter_server.server.client_handler] [547397532656] Error while handling: read_attribute (node 35): src/app/ReadClient.cpp:745: CHIP Error 0x00000032: Timeout
2026-03-10 19:18:11.957 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-03-10 19:18:25.957 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000023]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-10 19:18:25.958 (MainThread) ERROR [matter_server.server.client_handler] [547397532656] Error while handling: read_attribute (node 35): src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-10 19:18:56.960 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-03-10 19:19:10.960 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000023]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-10 19:19:10.960 (MainThread) ERROR [matter_server.server.client_handler] [547397532656] Error while handling: read_attribute (node 35): src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-10 19:19:41.965 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-03-10 19:19:55.961 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000023]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-10 19:19:55.961 (MainThread) ERROR [matter_server.server.client_handler] [547397532656] Error while handling: read_attribute (node 35): src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-10 19:20:26.967 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-03-10 19:20:40.962 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000023]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-10 19:20:40.963 (MainThread) ERROR [matter_server.server.client_handler] [547397532656] Error while handling: read_attribute (node 35): src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-10 19:21:11.972 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-03-10 19:21:25.963 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000023]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-10 19:21:25.964 (MainThread) ERROR [matter_server.server.client_handler] [547397532656] Error while handling: read_attribute (node 35): src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-10 19:21:56.967 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-03-10 19:22:10.966 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000023]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-10 19:22:10.966 (MainThread) ERROR [matter_server.server.client_handler] [547397532656] Error while handling: read_attribute (node 35): src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-10 19:22:41.972 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-03-10 19:22:55.967 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000023]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-10 19:22:55.969 (MainThread) ERROR [matter_server.server.client_handler] [547397532656] Error while handling: read_attribute (node 35): src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-10 19:49:20.043 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0xb8aeee8f, Peer = 01:000000000000001A
2026-03-10 19:49:20.045 (MainThread) INFO [matter_server.server.device_controller] <Node:26> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-03-10 19:49:23.307 (MainThread) INFO [matter_server.server.device_controller] <Node:26> Re-Subscription succeeded
2026-03-10 20:58:29.964 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x6177f117, Peer = 01:000000000000001C
2026-03-10 20:58:29.966 (MainThread) INFO [matter_server.server.device_controller] <Node:28> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-03-10 20:58:34.285 (MainThread) INFO [matter_server.server.device_controller] <Node:28> Re-Subscription succeeded
2026-03-11 01:00:22.577 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x16ca5cf6, Peer = 01:0000000000000019
2026-03-11 01:00:22.578 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-03-11 01:00:25.267 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:3084r with Node: <000000000000001A, 1> S:1843 M:267763367] (S) Msg Retransmission to 1:000000000000001A failure (max retries:4)
2026-03-11 01:00:53.588 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-03-11 01:01:07.578 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000019]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-11 01:01:07.578 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-03-11 01:01:07.579 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 1
2026-03-11 01:01:35.143 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0xa4e25abf, Peer = 01:000000000000001A
2026-03-11 01:01:35.145 (MainThread) INFO [matter_server.server.device_controller] <Node:26> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-03-11 01:01:38.402 (MainThread) INFO [matter_server.server.device_controller] <Node:26> Re-Subscription succeeded
2026-03-11 01:01:44.912 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-03-11 01:01:58.906 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000019]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-11 01:01:58.906 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-03-11 01:01:58.907 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 2
2026-03-11 01:01:58.907 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Marked node as unavailable
2026-03-11 01:02:36.677 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-03-11 01:02:50.680 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000019]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-11 01:02:50.681 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-03-11 01:02:50.681 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 3
2026-03-11 01:03:15.168 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:18435r with Node: <000000000000001C, 1> S:1844 M:253028771] (S) Msg Retransmission to 1:000000000000001C failure (max retries:4)
2026-03-11 01:03:41.506 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-03-11 01:03:55.504 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000019]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-11 01:03:55.505 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-03-11 01:03:55.505 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 4
2026-03-11 01:04:41.309 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-03-11 01:04:55.305 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000019]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-11 01:04:55.305 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-03-11 01:04:55.306 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 5
2026-03-11 01:05:24.737 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x8dd79e30, Peer = 01:0000000000000006
2026-03-11 01:05:24.739 (MainThread) INFO [matter_server.server.device_controller] <Node:6> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-03-11 01:05:42.241 (MainThread) INFO [matter_server.server.device_controller] <Node:6> Re-Subscription succeeded
2026-03-11 01:05:59.594 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-03-11 01:06:13.590 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000019]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-11 01:06:13.590 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-03-11 01:06:13.591 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 6
2026-03-11 01:07:09.987 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-03-11 01:07:23.980 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000019]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-11 01:07:23.981 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-03-11 01:07:23.981 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 7
2026-03-11 01:09:28.899 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-03-11 01:09:42.897 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000019]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-11 01:09:42.897 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-03-11 01:09:42.898 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 8
2026-03-11 01:11:24.922 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-03-11 01:11:38.917 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000019]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-11 01:11:38.918 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-03-11 01:11:38.918 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 9
2026-03-11 01:17:00.474 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-03-11 01:17:14.472 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000019]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-11 01:17:14.473 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-03-11 01:17:14.474 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 10
2026-03-11 01:26:06.806 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-03-11 01:26:20.804 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000019]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-11 01:26:20.805 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-03-11 01:26:20.805 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 11
2026-03-11 01:39:51.412 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-03-11 01:40:05.407 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000019]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-03-11 01:40:05.407 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2026-03-11 01:40:05.408 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 12
2026-03-11 01:40:05.408 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Node considered offline, shutdown subscription
2026-03-11 05:30:47.947 (MainThread) INFO [matter_server.server.device_controller.mdns] <Node:25> Discovered on mDNS
2026-03-11 05:30:47.947 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Setting-up node...
2026-03-11 05:30:48.298 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Setting up attributes and events subscription.
2026-03-11 05:30:49.413 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Subscription succeeded with report interval [1, 60]
2026-03-11 05:32:16.580 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:18799r with Node: <000000000000001C, 1> S:1844 M:253029105] (S) Msg Retransmission to 1:000000000000001C failure (max retries:4)
2026-03-11 05:32:25.134 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:2699r with Node: <000000000000001D, 1> S:1824 M:105856582] (S) Msg Retransmission to 1:000000000000001D failure (max retries:4)
2026-03-11 05:32:37.824 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0xdf3ac7c9, Peer = 01:0000000000000019
2026-03-11 05:32:37.826 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-03-11 05:32:38.491 (MainThread) INFO [matter_server.server.device_controller] <Node:25> Re-Subscription succeeded
2026-03-11 05:33:26.437 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x6b9fc2de, Peer = 01:000000000000001C
2026-03-11 05:33:26.439 (MainThread) INFO [matter_server.server.device_controller] <Node:28> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-03-11 05:33:31.093 (MainThread) INFO [matter_server.server.device_controller] <Node:28> Re-Subscription succeeded
2026-03-11 05:33:35.520 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x35e77cde, Peer = 01:000000000000001D
2026-03-11 05:33:35.521 (MainThread) INFO [matter_server.server.device_controller] <Node:29> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-03-11 05:33:40.621 (MainThread) INFO [matter_server.server.device_controller] <Node:29> Re-Subscription succeeded
2026-03-11 05:36:33.793 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x05a32a3a, Peer = 01:0000000000000006
2026-03-11 05:36:33.795 (MainThread) INFO [matter_server.server.device_controller] <Node:6> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-03-11 05:36:51.860 (MainThread) INFO [matter_server.server.device_controller] <Node:6> Re-Subscription succeeded
2026-03-11 07:14:45.279 (MainThread) INFO [matter_server.server.device_controller] <Node:4> No new update found.
2026-03-11 07:14:45.280 (MainThread) INFO [matter_server.server.device_controller] <Node:28> No new update found.
2026-03-11 07:14:45.290 (MainThread) INFO [matter_server.server.device_controller] <Node:30> No new update found.
2026-03-11 07:14:45.291 (MainThread) INFO [matter_server.server.device_controller] <Node:26> No new update found.
2026-03-11 07:14:45.292 (MainThread) INFO [matter_server.server.device_controller] <Node:29> No new update found.
2026-03-11 07:14:45.315 (MainThread) INFO [matter_server.server.device_controller] <Node:5> No new update found.
2026-03-11 07:14:45.318 (MainThread) INFO [matter_server.server.device_controller] <Node:33> No new update found.
2026-03-11 07:14:45.320 (MainThread) INFO [matter_server.server.device_controller] <Node:32> No new update found.
2026-03-11 07:14:45.321 (MainThread) INFO [matter_server.server.device_controller] <Node:25> No new update found.
2026-03-11 07:14:45.322 (MainThread) INFO [matter_server.server.device_controller] <Node:11> No new update found.
2026-03-11 07:14:45.322 (MainThread) INFO [matter_server.server.device_controller] <Node:6> No new update found.
2026-03-11 07:14:45.323 (MainThread) INFO [matter_server.server.device_controller] <Node:24> No new update found.
2026-03-11 07:14:45.323 (MainThread) INFO [matter_server.server.device_controller] <Node:31> No new update found.
2026-03-11 07:14:45.323 (MainThread) INFO [matter_server.server.device_controller] <Node:22> No new update found.
2026-03-11 07:14:45.323 (MainThread) INFO [matter_server.server.device_controller] <Node:9> No new update found.
2026-03-11 07:14:45.323 (MainThread) INFO [matter_server.server.device_controller] <Node:40> No new update found.
2026-03-11 07:14:45.323 (MainThread) INFO [matter_server.server.device_controller] <Node:34> No new update found.
2026-03-11 08:04:30.902 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x11f31d6d, Peer = 01:0000000000000021
2026-03-11 08:04:30.904 (MainThread) INFO [matter_server.server.device_controller] <Node:33> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-03-11 08:04:33.211 (MainThread) INFO [matter_server.server.device_controller] <Node:33> Re-Subscription succeeded
2026-03-11 10:30:45.839 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0xb0dda7f3, Peer = 01:0000000000000006
2026-03-11 10:30:45.840 (MainThread) INFO [matter_server.server.device_controller] <Node:6> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-03-11 10:31:00.778 (MainThread) INFO [matter_server.server.device_controller] <Node:6> Re-Subscription succeeded
2026-03-11 12:40:49.418 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x9f7fd987, Peer = 01:0000000000000016
2026-03-11 12:40:49.420 (MainThread) INFO [matter_server.server.device_controller] <Node:22> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-03-11 12:40:54.407 (MainThread) INFO [matter_server.server.device_controller] <Node:22> Re-Subscription succeeded
2026-03-11 13:31:00.014 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x4fe4cb8a, Peer = 01:0000000000000006
2026-03-11 13:31:00.016 (MainThread) INFO [matter_server.server.device_controller] <Node:6> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-03-11 13:31:18.111 (MainThread) INFO [matter_server.server.device_controller] <Node:6> Re-Subscription succeeded
2026-03-11 14:12:51.692 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0xed9f4a4e, Peer = 01:000000000000001A
2026-03-11 14:12:51.694 (MainThread) INFO [matter_server.server.device_controller] <Node:26> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-03-11 14:12:55.078 (MainThread) INFO [matter_server.server.device_controller] <Node:26> Re-Subscription succeeded
2026-03-11 17:02:37.720 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0x1ed4fab6, Peer = 01:000000000000001D
2026-03-11 17:02:37.721 (MainThread) INFO [matter_server.server.device_controller] <Node:29> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2026-03-11 17:02:41.580 (MainThread) INFO [matter_server.server.device_controller] <Node:29> Re-Subscription succeeded
2026-03-11 17:21:49.453 (MainThread) ERROR [matter_server.server] Error doing task: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/matter_server/server/client_handler.py", line 213, in _run_handler
    raise err
  File "/usr/local/lib/python3.12/site-packages/matter_server/server/client_handler.py", line 196, in _run_handler
    result = await result
             ^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/matter_server/server/device_controller.py", line 717, in send_device_command
    return await self._chip_device_controller.send_command(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/matter_server/server/sdk.py", line 308, in send_command
    return await self._chip_controller.SendCommand(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/chip/ChipDeviceCtrl.py", line 1552, in SendCommand
    return await future
           ^^^^^^^^^^^^
chip.interaction_model.InteractionModelError: InteractionModelError: Failure (0x1)

JohnD · March 12, 2026, 8:44am

@KingDando wenn du solche Log’s etc. hast, dann verwende doch bitte “Preformattet text” (Strg + e)

Es wäre ganz gut, wenn du mir sagen könntest, was welcher Node ist bzw. welcher Node-Nummer haben die Matter-Signale bekommen?

Also Subscription failed ...Timeout, resubscription attempt könnte schon mal ein wichtiger Hinweis sein. Wenn sich diese Fehler auf die Matter-Signale beziehen, dann ist klar, dass du Probleme hast.

Timeout waiting for mDNS resolution. ist auf jeden Fall auch kein gutes Zeichen. Schreib mir am besten eine persönliche Nachricht, dann können wir das gemeinsam durchgehen. Welchen Internet-Router hast du?

KingDando · March 12, 2026, 11:56am

Oh stimmt. Ja danke für den Hinweis nochmal. Normalerweise mach ich das schon aber hab den Button gestern nicht gefunden. War versteckt.

JohnD · March 12, 2026, 12:13pm

Das funktioniert leider nicht.

Dem Hub fehlt schlichtweg die erforderliche Hardware-Logik, um über USB Daten zu senden oder zu empfangen. Der USB-Anschluss dient ausschließlich der Stromversorgung.

Und zum Anderen, nutzt die FRITZ!Box Standardtreiber für bestimmte Geräteklassen wie Drucker (Printer → LPD/IPP), Festplatten und USB-Sticks (Mass Storage → MSC), UMTS/LTE-Sticks oder Smartphones im Tethering-Modus (Mobile Broadband → CDC-NCM/QMI). Ich wüste gar nicht mit welche Geräteklasse der Hub sich per USB bei der Box melden könnte! Netzwerkkarte vielleicht? Na wie auch immer, ohne Hardware die das unterstützt und ohne Treiber für die Hardware ist das nicht möglich.