Hello,
I have problems to make my echo4 to my first thread network. I can see my eco4 but i cant edit sth.
I try to send the credentials with my HA Assistant App, but it isnt working. I Try this with an Android and IOS phone.
Android say: “You have no login data for importing”
IOS say: “No prefered network found”
My Home Assistant VM running on a proxmoxx Server.
Have someone a Idea?
Or didnt support HA Amazon Echo4?
The Thread panel shows the Thread Border Routers detected on the network. However, it cannot directly get credentials from them.
To get the credentials you need to synchronize throuhg your phone. The Home Assistant App uses the Android frameworks Thread Network APIs.
Now I am not familiar with Amazon ecosystem or the Alexa Echo 4 specifically, but what is needed for Home Assistant App to make use of it is that they synchronize/add the Thread border router to the Android Thread Network store… I’d expect if you use their App, that they will do this.
What happens if you just try to add a Matter over Thread device?
Hello,
I try the synchronization with android and Apple, but it is not working and i dont no why. I get the following messages in my HA App:
Android say: “You have no login data for importing”
IOS say: “No prefered network found”
I have a Matter over Thread device. A connection to HA is only possible with a border Router. This Matter over Thread device is connect with my Amazon Echo4. The Border Router from my Echo is running.
And i see this Border Router in my Home Assitant. But only under other networks
Yes, this means that Amazon/Alexa Echo 4 did not add the Thread credentials to the Android (technically Google Play Services) provided API. You need to check with the Amazon apps if/how to do that.
Technically, Home Assistnat does not need to know the Thread credentials for the network to be useful.
Try to add the Matter Thread device to Amazon Alexa Echo 4 first, then share it with Home Assistant. In that case, the Amazon apps will setup the Thread credentials on the device. Think of Thread like WiFi: Once it is setup for a device, it will able to use the network. When you then share the device on Matter level, it will continue that network.
I dont found a way to do that. Also on Google, there is no answer. I install the Alexa app new and restart my echo. But without any result.
I can connect Matter over wifi and Matter over Thread devices with alexa. Luckely I have both type of devices. So I can share Matter over Wifi devices to Home Assistant. But with Matter over thread devices, it isn´t working.
That should be working, if the device is on the Thread network, it will transparently route to Home Assistant too.
What happens exactly when you try?
Are you using bridged networking?
No, because i need a thread border Router. Matter over thread and Matter over wifi is not the same.
The device is connected over Matter Thread with Alexa. Alexa is the Thread border router. But i can´t set this border Router in Home Assiatnt to my preffered network.
“adding the device failed”
No I use Thread.
Correct.
But communicating with a Thread device is no different than communicating with a WiFi device if the device is on the Thread network. And since you have that Thread device added to Alexa, the device is already on the Thread network. At this point, Thread and WiFi Matter devices are essentially the same from the perspective of Home Assistant.
Home Assistant doesn’t need to know about the Thread network/its credentials if it is not the first Matter controller onboarding the device.
By Bridging I mean is the network of your VM bridged with the physical Ethernet interface of your VM host? This is a requirement in order for your VM to receive the IPv6 ND router advertisements your Thread Border router sends.
My Home Assistant have a IPv6 connection. I check it also with a ping test.
Yesterday, i seperate my wifi network into 5GHz and 2,4GHz and connect Alexa and my phone to the 2,4GHz network. But the result is the same, i cant connect the Thread network to my Home Assistant.
But my Home Assistant working only with a LAN Connection, no wifi. Maybe i need a 2.4GHZ wifi Connection?
Or my second idea is, that i prepare/flash a stick with matter and connect this stick to my HA as a border Router. And connect this Stick to Alexa Thread network. But i am not if it working or not.
Today, I try the same with my raspberry 4. I change this summer to proxmoxx, so my raspberry with home assistant was running after a short update in my network.
Now i try again to connect my ECHO4 Border Router to Home Assistant. But i have the same problem again. No different between Raspberry and Proxmoxx VM.
I think, it is a Home Assistant problem, not my Proxmoxx VM.
No one using Alexa Border Router???
No one have an Idea???
Can mostly only repeat what I said before: To onboard a device to Home Assistant, you don’t need to “add” the Thread border router. Thread is like WiFi: It is just the network layer. You don’t need to “add” your thread border router to Home Assistant to connect to a device on WiFi…
Today, the onboarding happens on the phone, so you phone needs to know about the Thread network.
What phone (Android/iOS?) did you use when adding a Matter over Thread device worked?
I suggest using that same phone/same configuration, and try adding to Home Assistant.
Alternatively, it might be possible to add to Alexa first, and then share the device from Alexa (which should generate a code you then can enter in Home Assistant when adding a Matter device which is already paired with another platform). This uses the multi-admin feature of Matter. In this case too, Home Assistant does not need to know about the Thread network: Home Assistant will be able to communicate to your device using IPv6 routing information.
What you can try is enabling IPv6 on your router, as some have said this made things work (that said, technically this should not be necessary as every Thread BR should assign a routable ULA IPv6 address to your Home Assistant device).
Hello Agners,
Sorry, but this is wrong. I must connect the border Router with Home Assistant. Matter over Thread and Matter over wifi are not the same. Without Border Router, it is not possible to connect Matterover Thread devices with Home Assistant.
The Home Assistant team wrote exactly the same in their documentation.
I use Android. Not the phone is connect to the Matter devices. Alexa is connect to the matter devices. I did the same test with an IOS phone. But the result was the same.
This is not a alternative. I did this test. I can share Matter over wifi devices from Alexa to Home Assistant. But i cant share Matter over thread devices to Home Assistant, because Home Assistant need a connection to a Thread Border Router.
IPv6 is enable. All devices have a IPv6 adress/connection.
You have to give me a bit more credit: I maintain the OpenThread Border Router add-on, and I am an active contributor to the OpenThread POSIX project. So I know a thing or two about Thread 
With that said…
I did not say they are the same. I said they are alike. Check this excellent Matter primer from Google:
In the first graphic you see that Thread and WiFi are on the network layer. They largely are independent of the higher layer from a communication perspective: It is all just pure IPv6, and IPv6 Neighbor Discovery Protocol to find the BRs.
What are you referring to here exactly? If you use our OpenThread Border Router, then yes, you need to have the credentials in Home Assistant and sync it to the phones.
However, you try to use a third party border router. In that case the credentials are not something which needs handling from Home Assistant. It is a Amazon/Alexa/Android thing. Think of it who knows your WiFi password…
Sharing a Thread device which works on Alexa with Home Assistant Core should work without Home Assistant knowing about the BR. I’ve done the same with Apple Home the other day: Add it to Apple Home with their BR, and then simply share with Home Assistant. There is no need to add the BR to Home Assistant with that use case as the (Matter over) Thread device is already on the network. The Matter controller in Home Assistant will use IPv6 Neighbor Discovery Protocol to find the device.
So can you try sharing from Alexa again and adding to Home Assistant (via setup code)? And if it doesn’t’ work, please share exactly (step by step, ideally with screenshots) what you do, along with the logs of the Matter Server add-on.
Ok, i will show you my steps. I create a share Code in my Alexa App. Alexa is connect in my 2,4GHz Wifi.
More Screenshots in the following Posts, because its only allowed to share one Image in a post
Now i can share all the logs from today:
2024-09-24 14:11:20.032 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:157115960 on exchange 45932i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-09-24 14:11:23.105 (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:11:39.847 (Dummy-2) CHIP_ERROR [chip.native.CTL] Discovery timed out
2024-09-24 14:11:39.848 (Dummy-2) CHIP_ERROR [chip.native.ZCL] Secure Pairing Failed
2024-09-24 14:11:39.848 (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:11:39.848 (MainThread) ERROR [matter_server.server.client_handler] [140614952909648] Error while handling: commission_with_code: Commission with code failed for node 11.
2024-09-24 14:15:25.120 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 12.
2024-09-24 14:15:34.811 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:157115961 on exchange 45933i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-09-24 14:15:38.399 (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:15:55.129 (Dummy-2) CHIP_ERROR [chip.native.CTL] Discovery timed out
2024-09-24 14:15:55.129 (Dummy-2) CHIP_ERROR [chip.native.ZCL] Secure Pairing Failed
2024-09-24 14:15:55.129 (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:15:55.129 (MainThread) ERROR [matter_server.server.client_handler] [140614952909648] Error while handling: commission_with_code: Commission with code failed for node 12.
(Englisch: Yes, the device is already connect with another controller)