I am guessing you select “Yes. It’s already in use.” when the question “Is your device already added to another Matter controller?” appears, then “Other controllers” to enter the setup code? These are the correct steps.
There seem to be no response from the device, this can have several reason:
Home Assistant talks to the wrong device. I’ve seen that previously with Thread devices when multiple thread devices have been shared (the discriminator is rather short with the setup code, so there might be conflicting mDNS entries or stale ones from previous tries). To combat this, try restarting the Thread Border Router (Alexa Echo 4 router), and the Matter Server add-on. Then try again (with a new setup code from the Alexa app).
The device’s setup code is no longer valid or wrong. In that case the device simply doesn’t respond to requests which leads to this error. Make sure to get a fresh code and use it within 5 minutes.
There is some other communication issue between the Thread device and Home Assistant. These are bit harder to debug. If you use Unify gear, make sure to disable Multicast optiomizations etc.
I make the restarts and create a new fresh share code. Here the logs incl. the restart.
[14:42:18] INFO: Starting Matter Server...
s6-rc: info: service legacy-services successfully started
[14:42:19] INFO: Using 'enp0s18' as primary network interface.
[14:42:19] INFO: Successfully send discovery information to Home Assistant.
2024-09-24 14:42:20.626 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging...
2024-09-24 14:42:20.626 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Controller Stack...
[1727181740.650901][126:126] CHIP:CTL: Setting attestation nonce to random value
[1727181740.651183][126:126] CHIP:CTL: Setting CSR nonce to random value
[1727181740.651983][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1727181740.652101][126:126] CHIP:DL: writing settings to file (/tmp/chip_kvs-PF3DiL)
[1727181740.652176][126:126] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
[1727181740.652370][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1727181740.652498][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1727181740.652555][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1727181740.652709][126:126] CHIP:DL: writing settings to file (/data/chip_counters.ini-W3GUnK)
[1727181740.652869][126:126] CHIP:DL: renamed tmp file to file (/data/chip_counters.ini)
[1727181740.652891][126:126] CHIP:DL: NVS set: chip-counters/reboot-count = 15 (0xF)
[1727181740.653233][126:126] CHIP:DL: Got Ethernet interface: enp0s18
[1727181740.653388][126:126] CHIP:DL: Found the primary Ethernet interface:enp0s18
[1727181740.653816][126:126] CHIP:DL: Failed to get WiFi interface
[1727181740.653829][126:126] CHIP:DL: Failed to reset WiFi statistic counts
2024-09-24 14:42:20.654 (MainThread) INFO [chip.storage] Initializing persistent storage from file: /data/chip.json
2024-09-24 14:42:20.654 (MainThread) INFO [chip.storage] Loading configuration from /data/chip.json...
2024-09-24 14:42:20.720 (MainThread) INFO [chip.CertificateAuthority] Loading certificate authorities from storage...
2024-09-24 14:42:20.720 (MainThread) INFO [chip.CertificateAuthority] New CertificateAuthority at index 1
2024-09-24 14:42:20.721 (MainThread) INFO [chip.CertificateAuthority] Loading fabric admins from storage...
2024-09-24 14:42:20.721 (MainThread) INFO [chip.FabricAdmin] New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2024-09-24 14:42:20.721 (MainThread) INFO [matter_server.server.stack] CHIP Controller Stack initialized.
2024-09-24 14:42:20.722 (MainThread) INFO [matter_server.server.server] Starting the Matter Server...
2024-09-24 14:42:20.725 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Skip fetching certificates (already fetched within the last 24h).
2024-09-24 14:42:20.725 (MainThread) INFO [chip.FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
2024-09-24 14:42:20.790 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage.
2024-09-24 14:42:20.794 (MainThread) INFO [matter_server.server.vendor_info] Loaded 247 vendors from storage.
2024-09-24 14:42:20.794 (MainThread) INFO [matter_server.server.vendor_info] Fetching the latest vendor info from DCL.
2024-09-24 14:42:21.012 (MainThread) INFO [matter_server.server.vendor_info] Fetched 245 vendors from DCL.
2024-09-24 14:42:21.012 (MainThread) INFO [matter_server.server.vendor_info] Saving vendor info to storage.
2024-09-24 14:42:21.016 (MainThread) INFO [matter_server.server.device_controller] Loaded 0 nodes from stored configuration
2024-09-24 14:42:21.022 (MainThread) INFO [matter_server.server.server] Matter Server successfully initialized.
2024-09-24 14:43:07.270 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 13.
2024-09-24 14:43:17.428 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:35538673 on exchange 446i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-09-24 14:43:20.548 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33
2024-09-24 14:43:37.288 (Dummy-2) CHIP_ERROR [chip.native.CTL] Discovery timed out
2024-09-24 14:43:37.288 (Dummy-2) CHIP_ERROR [chip.native.ZCL] Secure Pairing Failed
2024-09-24 14:43:37.288 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to establish secure session to device: src/controller/python/ChipDeviceController-ScriptDevicePairingDelegate.cpp:89: CHIP Error 0x00000003: Incorrect state
2024-09-24 14:43:37.289 (MainThread) ERROR [matter_server.server.client_handler] [139712196198288] Error while handling: commission_with_code: Commission with code failed for node 13.
Hm, so a clean start still causes the same issue It seems that there is some kind of network/communication issue.
What Thread device is this?
One thing you can do is check if there is indeed a commissionable Matter device visible in your network using a mDNS browser. When you share the device in your Alexa app, the device should appear with the service _matterc._udp (e.g. use the mDNS Discovery app from Play store, simply enter matterc there and search).
Next you can set the “Matter SDK Log Level” in the add-on configuration to “progress”. This will give you more information. Especially, if you try to commission once again, this should show what IPv6 address it tires to reach. This should match the IP address you see above in your mDNS Discovery app.
On the HAOS system shell (Proxmox console) you can use login to get to the underlying OS shell. From there you can try to ping that address. You can also try to inspect the routing table (ip -6 route). There should be an entry for the IPv6 network the device address is in.
Ok I will check it. But i make a ping test to my Home Assistant and it was running.
But i will also give the Echo 4 back to Amazon and change to the new Google TV Streamer. The Thread problem is not the main reason, i have more for it
When i go other forums or blogs, there are more people with Alexa Matter Thread problems.
Hello together,
Are there news on this topic? Iam in the same boot. I already have a thread border router, but i want to add my new Alexa Echo 4 to my already existing network. I had the same problems as “DerCedrik”. I found no way to send the credential from alexa app to homeassistant,
I had the same issue and found this thread through searching.
I connected an Aqara P2 sensor to my Echo Studio and wanted to make it visible in HomeAssistant.
I tried sharing the device in the Alexa App, but the code didn’t work in HA.
I tested the mDNS Discovery app as suggested by user agners, and could see the device after generating the code in the Alexa App. It showed the IPv6 address there. This gave me an idea…
Cause and Solution: IPv6 was disabled in the HA system settings.
After enabling IPv6 in HA, the integration using the code from the Alexa App worked immediately.
Thats different,
You have add a device which is already connected to alexa in addition to home assistant. Our issue is that we want to add the alexa echo 4 itself as additional thread border router. I found no way so far.
It seems that there is some kind of network/communication issue.
