Devices Offline Error

[creativedm0031]

i connected the Hub to my HomeKit and some of my lamps are going offline sometimes like for 10-20 sec and turn online for a few seconds again before they went offline again.

i attached my log

491eb00d_hamh_2026-01-05T12-38-55.055Z.log

[jjanssen95]

I experience something similar, connected to Google Home. All devices appear offline since Yesterday. Tried without succes: restart Add-on, restart Home Assistant, remove Matter setup to re-setup it fresh.

When trying to start fresh I can't seem to save/submit it wil result in a doctype error.

[miwi73]

Same here. In the Alexa app the devices are online for few seconds and then disappear. After ~ 1 minute some of them come back before same thing repeats.

[TwinForce]

Since today, i think i got the same issue and Google Home shows devices as offline and try to switch something throws the error “Something went wrong” for Matter devices.

I removed the Matter hub from Google Home and completely reset the Matter configuration in Home Assistant. After re-commissioning, all devices were discovered successfully but initially appeared offline. After ~2 minutes they became online and worked for ~3 minutes, then the error returned.

After another ~20 minutes, the devices briefly came online again. However, when attempting to control any actuator (e.g. switching a light or a switch), Google Home immediately shows “Something went wrong”, and all lights and switches go offline at once, while sensors remain online.

Interestingly, some state updates still work: sensor values (e.g. humidity) continue to update in the Google Home app, and changes such as brightness updates made in Home Assistant are reflected in Google Home. Only sending commands (on/off, toggling) seems to fail and triggers the offline state for actuators.

Additionally, at seemingly random times, all Matter devices switch to offline in Google Home and come back online later without any user interaction. This behavior has been observed repeatedly at irregular intervals of approximately 5 to 15 minutes over a monitoring period of about 2 hours.

The Matter add-on and Matter Server logs do not show any obvious errors at the time the issue occurs. Devices remain fully controllable in Home Assistant.

Environment:

• Home Assistant OS running as a VM on Proxmox
• Google Nest Mini used as Matter controller (worked fine with matterhub for months before)
• IPv6 link-local (fe80::) is used for internet access IPv4
• FRITZ!Box 7490 (FRITZ!OS last updated 2025-10-24)
• No Home Assistant updates were installed before the issue occurred

I am not sure if this is related, but during approximately 4 hours of observation I found the following log entry 6 times in the Matter Hub logs:

2026-01-21 22:46:47.511 ERROR PeerSet Failed to discover peer@1:0xa132bac4 after resubmission started. [implementation] Cannot discover operational device because scanner is closing.
at MdnsScanner.findOperationalDevice (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/protocol/dist/esm/mdns/MdnsScanner.js:399:13)
at #handleResubmissionStarted (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/protocol/dist/esm/peer/PeerSet.js:610:49)
at emitNext (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/general/dist/esm/util/Observable.js:109:20)
at BasicObservable.emit (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/general/dist/esm/util/Observable.js:137:12)
at Object.resubmissionStarted (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/protocol/dist/esm/protocol/ExchangeManager.js:326:75)
at #retransmitMessage (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/protocol/dist/esm/protocol/MessageExchange.js:412:20)
at StandardTimer.callback (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/protocol/dist/esm/protocol/MessageExchange.js:336:38)
at Timeout._onTimeout (file:///usr/local/lib/node_modules/home-assistant-matter-hub/node_modules/@matter/general/dist/esm/time/Time.js:135:12)
at listOnTimeout (node:internal/timers:588:17)
at process.processTimers (node:internal/timers:523:7)
2026-01-21 22:48:56.174 INFO MdnsScanner MDNS Scan targets updated : commissionable = true Targets:
html
head title 504 Gateway Time-out /title /head
body
center h1 504 Gateway Time-out /h1 /center
hr center openresty /center
/body
/html
!-- a padding to disable MSIE and Chrome friendly error page --
!-- a padding to disable MSIE and Chrome friendly error page --
!-- a padding to disable MSIE and Chrome friendly error page --
!-- a padding to disable MSIE and Chrome friendly error page --
!-- a padding to disable MSIE and Chrome friendly error page --
!-- a padding to disable MSIE and Chrome friendly error page --

No wonder i have to remove the "<" and ">" quotes so the log wont show as html here on github.