Hello I currently have the V2 hub, and it fits my needs great, but I recently tried to add the eufy c34 lock. It said it was compatablie with smarthings, going to connect was a different story. When I try to connect it says it will not connect with matter over wifi and that i need a thread border router. It looks like everything else I have don’t have the thread border either, including echo’s theromstat, tv’s and so on. Is there a gateway or something that I can just buy as a add on for the thread border router like this . Amazon.com: Matter Smart Home Hub, Thread & Tuya Zigbee 3.0, Control Your Connected Devices (M1 - Zigbee&Thread) : Tools & Home Improvement
or do i just need to suck it up and buy a new echo or shomething?
If the Eufy C34 lock is Matter over WiFi … add it to the Eufy app. Then you should be able to generate a Matter code or QR code you can enter into the ST app. Add Device > Add Partner device > Matter
According to the CSA site the Eufy C34 is Matter over Thread, but it happens to have WiFi just for cloud access, quite weird.
There are many options indeed. While a natural option is the V3 / Aeotec or the SmartThings Station, from the technical point of view any Thread border router (TBR) will do as long you can get the credentials since the V2 will ask for them.
Even if you didn’t know them (they can be easily extracted with a Nanoleaf Matter over Thread bulb), in the case of, let’s say, an Echo 4, or the Tuya or the Aqara M100 (another cheap alternative) or even the IKEA Dirigera you could add the device to those platforms (Alexa, Tuya, Aqara) and then “share it” to SmartThings, which is a feature called Matter multi-admin.
If you know the credentials of the Thread network then you don’t need the other platforms for the initial setup and can setup the device right from SmartThings.
Are you seriously trying to tell me what SmartThings hubs are TBRs?
This is about the fact that Matter/Thread devices can’t reach the Internet. Some TBRs support NAT64, SmartThings hubs do not. If a device like the Nuki Ultra is connected to a TBR that doesn’t NAT64, it needs an alternative route to the Internet - WiFi, for example. Choice is good…
Apologies, I was trying to comment on the original post and just replied in the wrong place.
You are of course right that the original project chip specification did not require NAT64 in thread border routers, and instead made the assumption that all matter set ups would support IPv6 one way or another.
That’s why Meross, for example, published its own page to allow people to check whether the network their matter device would be connecting to supported IP V6 or only IPv4.
From the beginning, matter required IPv6 for all the apps connecting to it for additional security reasons. Google still notes this requirement:
But then real life happened, and a lot of people, particularly in Europe, discovered that their Internet provider only offered IPv4.
So the CSA had two options. Continue to say that IPv6 support would be required for all matter implementations and frustrate consumers further.
Or allow device manufacturers to include their own Wi-Fi connections in thread devices to cover situations where the local network didn’t handle IPv6 to IPv4 address conversion. As the locks you mentioned do.
It can work, but personally, I think it’s still confusing.
Again, though, my apologies for misdirecting my previous reply and confusing things even further! Thanks for the correction.
