#Cannot add this matter device

1 messages · Page 1 of 1 (latest)

pseudo scroll
#

Hello! it was recommended that I move my post from #1284965172053807145 over to here. Here is the original post:

I got a Matter compatible LED light strip (Govee) and when I first got it, after a bit of trial and error, I got it to successfully connect.
However, recently, it disconnected itself and I havent been able to reconnect it since. I have factory reset the device, reconnected it to the Govee app, etc. I am able to add it to Apple Home flawlessly first try but cannot add it to Home Assistant--even when sharing the device from Apple Home. Here is the error in the Matter Server Logs when trying to comission the device:

2025-02-21 20:03:25.256 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 26.
2025-02-21 20:03:55.257 (Dummy-2) CHIP_ERROR [chip.native.CTL] Discovery timed out
2025-02-21 20:03:55.258 (Dummy-2) CHIP_ERROR [chip.native.ZCL] Secure Pairing Failed
2025-02-21 20:03:55.258 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to establish secure session to device: src/controller/python/ChipDeviceController-ScriptDevicePairingDelegate.cpp:96: CHIP Error 0x00000003: Incorrect state
2025-02-21 20:03:55.258 (MainThread) ERROR [matter_server.server.client_handler] [139917235263040] Error while handling: commission_with_code: Commission with code failed for node 26.

(this is when sharing the device from Apple Home)

I have been able to connect other Matter devices that still work perfectly fine. If you need any additional information, feel free to ask. Thank you in advance!

(full log attached in .txt file)

📎 core_matter_server_2025-02-22T01-09-17.439Z.log
errant flint
#

I had a similar issue and ultimately had to run the matter container outside haos in its own docker. Additionally ran the following two commands in my hostos and it paired immediately

#

sysctl -w net.ipv6.conf.br0.accept_ra=2
sysctl -w net.ipv6.conf.eth0.accept_ra=2 (it would be whatever interface you’re actually running the container off of)

#

I chalk it up to odd network topologies and too much abstraction through vms/docker.

errant flint
pseudo scroll
#

Hmmm. Even though I already have 2 matter devices connected successfully?