Yes but in order to communicate with your IoT thread devices, you need a WiFi border router. If your WiFi network goes down, then your controlling devices cannot communicate with your IoT Thread devices. I can sometimes use Bluetooth to communicate with bulbs for example, but this is slow and sometimes unreliable. The Zigby bridge was not able to communicate to Hue bulbs on the other side of the house. So I switched to Thread. WiFi is good and ok in our home as we have a mesh network and thread is more robust as we have thread bulbs throughout the home. Our mesh network (Plume) has a 2.4ghz onboarding mode for IoT devices which works well.
A minor thing, but the reason I am a fan of wifi is specifically because it isn't a single point of failure. If your running multiple access points then you have redundancy. Plus you can replace your whole network setup and as long as your using the same ssid and password it will all just work. The nightmare of thread/zigbee was the single point of failure and repairing devices, the mesh doesn't fix that. (I am aware that matter addresses this with multiple border routers, but I am unsure if that works if using thread) But hands down ethernet over everything else. :)
Yeah you have a good point. I glossed over a mesh WiFi network which moves to two or three points of failure but if your main router goes out you are still toast. And hub/bridges are a single point of failure as you mention. I love Ethernet too! Apple home can switch between home hubs if one goes down but based on my experience I’m not sure if that’s actually changing the main Matter controller for Matter devices.
Great video as always! Question: what is the assumed max distance between thread devices? I tend to use WIFi instead of thread as I have plaster over lathe walls as well as a full brick exterior. My WiFi is strong with a mesh network but often struggle with thread even with 3 Apple TV 4Ks and 4 HomePod Minis. Thanks again for the video.
Yes and I think while the total addressable market remains smaller than WiFi it makes it harder to justify. I like the sound of what LIFX is doing this year with WiFi and Thread in the same chip and each user picks the best.
I’m fairly sure matter forms its own ipv6 network and does not require your home network to support ipv6. The matter controller bridges between your matter network and your home network and can use what’s called link-local ipv6. 5:30 timestamp for reference.
In my experience I need to have IPv6 on for my WiFi network with a couple different vendors over the years and same for my parents’ eero, otherwise adding WiFi Matter devices to Apple Home will fail (eg TP-Link). I haven’t retested this recently so perhaps it’s an apple Home bug they fixed. I know Thread uses IPv6 regardless.
I didn’t understand the last point for 2.4ghz wifi. Should i always have 2.4ghz wifi signal On? Or combine with 2.4 and 5ghz after connecting a new device?
I’ve found devices struggle to connect in setup when your iPhone happens to be using the 5GHz band of your Wi-Fi and trying to share that info with a smart home device that only connects over 2.4GHz. So if you see this issue, I think having a 2.4GHz only SSID can solve this.
Well i bought 2 different Thread Matter only devices both never connected to my Aqara M3 hub, Nest Display Hub, Samsung TV SmartThings. Zigbee devices works perfectly
This Matter Over Thread thing has taken seemingly at least 5 years too long to come to market. Maybe it comes down to marketing. If matter over thread really is the gold standard, they need to call that a specific cool name. Like MaxThread or something
They are both the same. Hubless tech that each individual device has to be commissioned and recommissioned on its own with any change in your network. I recently switched from Spectrum to GFiber. I had to recommission ALL my Matter thread and wifi devices even though I still used the same SSID and password. I personally feel Zigbee bridged to Matter with HUE, IKEA or Third Reality hubs are superior to Matter Thread/wifi.
I think nobody should care... - a good solid WiFi is a foundation for any smart home. I have Wifi in my garden, close to my swmming pool ... even close to the garbage boxes shelter. no point for Thread coverage and mesh - no smart home communication is Thread to Thread ... if you evaluate the reactivity of a Thread device when turning it on from your phone for instance, half the path is already WiFi ... it makes little difference vs phone to Wifi device ... no point for Thread latency - with Thread a single point of failure also exists, it's the border router. Whereas with a good meshed WiFi, even if an access point fails there's little chance that the closest one will be reachable even with low throughput - WiFi has also become cheap, maybe cheaper than Thread thanks to those chinese Esperssif ESP32 microcontrolers The only value of Thread is low power making battery operation possible
Yes but in order to communicate with your IoT thread devices, you need a WiFi border router. If your WiFi network goes down, then your controlling devices cannot communicate with your IoT Thread devices. I can sometimes use Bluetooth to communicate with bulbs for example, but this is slow and sometimes unreliable. The Zigby bridge was not able to communicate to Hue bulbs on the other side of the house. So I switched to Thread. WiFi is good and ok in our home as we have a mesh network and thread is more robust as we have thread bulbs throughout the home. Our mesh network (Plume) has a 2.4ghz onboarding mode for IoT devices which works well.
I’ve noticed some manufacturers have moved on from *Matter over Thread* to *Matter over WIFI.* Example at 2:41 Nanoleaf Smart Bulbs
A minor thing, but the reason I am a fan of wifi is specifically because it isn't a single point of failure. If your running multiple access points then you have redundancy. Plus you can replace your whole network setup and as long as your using the same ssid and password it will all just work.
The nightmare of thread/zigbee was the single point of failure and repairing devices, the mesh doesn't fix that.
(I am aware that matter addresses this with multiple border routers, but I am unsure if that works if using thread)
But hands down ethernet over everything else. :)
Yeah you have a good point. I glossed over a mesh WiFi network which moves to two or three points of failure but if your main router goes out you are still toast. And hub/bridges are a single point of failure as you mention. I love Ethernet too! Apple home can switch between home hubs if one goes down but based on my experience I’m not sure if that’s actually changing the main Matter controller for Matter devices.
The audio track in Portuguese was very good!!!
Excelente!
@@EricWelander Yes, Eric, I'm from 🇧🇷 and I watch the videos and now in Portuguese you can understand better. Thank you very much.
@ Yes, Eric, I'm from 🇧🇷 and I watch the videos and now in Portuguese you can understand better. Thank you very much.
Great video as always! Question: what is the assumed max distance between thread devices? I tend to use WIFi instead of thread as I have plaster over lathe walls as well as a full brick exterior. My WiFi is strong with a mesh network but often struggle with thread even with 3 Apple TV 4Ks and 4 HomePod Minis. Thanks again for the video.
The answer is simple: device availability. Threads device marked is currenly very small.
Chicken and the egg argument.
Yes and I think while the total addressable market remains smaller than WiFi it makes it harder to justify. I like the sound of what LIFX is doing this year with WiFi and Thread in the same chip and each user picks the best.
I’m fairly sure matter forms its own ipv6 network and does not require your home network to support ipv6. The matter controller bridges between your matter network and your home network and can use what’s called link-local ipv6. 5:30 timestamp for reference.
In my experience I need to have IPv6 on for my WiFi network with a couple different vendors over the years and same for my parents’ eero, otherwise adding WiFi Matter devices to Apple Home will fail (eg TP-Link). I haven’t retested this recently so perhaps it’s an apple Home bug they fixed. I know Thread uses IPv6 regardless.
The answer is easy for me. I can’t get upgrade to IPv6. I have two hubs and everything else is thread.
I didn’t understand the last point for 2.4ghz wifi. Should i always have 2.4ghz wifi signal On? Or combine with 2.4 and 5ghz after connecting a new device?
I’ve found devices struggle to connect in setup when your iPhone happens to be using the 5GHz band of your Wi-Fi and trying to share that info with a smart home device that only connects over 2.4GHz. So if you see this issue, I think having a 2.4GHz only SSID can solve this.
@@EricWelander I wish everything used the 5Gz this has caused me many pain points the last 5 years
Well i bought 2 different Thread Matter only devices both never connected to my Aqara M3 hub, Nest Display Hub, Samsung TV SmartThings. Zigbee devices works perfectly
This Matter Over Thread thing has taken seemingly at least 5 years too long to come to market. Maybe it comes down to marketing. If matter over thread really is the gold standard, they need to call that a specific cool name. Like MaxThread or something
Haha yeah maybe a marketing face lift would help. It’s already shipping but the true vision of a seamless smart home hasn’t arrived in most homes.
They are both the same. Hubless tech that each individual device has to be commissioned and recommissioned on its own with any change in your network. I recently switched from Spectrum to GFiber. I had to recommission ALL my Matter thread and wifi devices even though I still used the same SSID and password. I personally feel Zigbee bridged to Matter with HUE, IKEA or Third Reality hubs are superior to Matter Thread/wifi.
My bridge devices have always been solid. Lutron, yolink (lora) aqara
I think nobody should care...
- a good solid WiFi is a foundation for any smart home. I have Wifi in my garden, close to my swmming pool ... even close to the garbage boxes shelter. no point for Thread coverage and mesh
- no smart home communication is Thread to Thread ... if you evaluate the reactivity of a Thread device when turning it on from your phone for instance, half the path is already WiFi ... it makes little difference vs phone to Wifi device ... no point for Thread latency
- with Thread a single point of failure also exists, it's the border router. Whereas with a good meshed WiFi, even if an access point fails there's little chance that the closest one will be reachable even with low throughput
- WiFi has also become cheap, maybe cheaper than Thread thanks to those chinese Esperssif ESP32 microcontrolers
The only value of Thread is low power making battery operation possible