Live data from Hacker News

Zigbee vs. Matter over Thread:Understanding IoT Protocol Performance in Practice

arxiv.org

1–10 of 103 posts

Re: Zigbee vs. Matter over Thread:Understanding IoT Protocol Performance in Practice

#3
A lot of graphs where OpenThread & zigbee dance around each other, are within 2x of each other.

Two huge notables to me: message throughput for openthreads scales up, zigbee seems to hit a wall early. Not sure when that matters but very clear. The last table was a fright through: it takes half a minute for OpenThreads to recover after a node drops where-as Zigbee a quarter second! Wow.

Re: Zigbee vs. Matter over Thread:Understanding IoT Protocol Performance in Practice

#5
post #2

These protocols add so much complications it makes wifi/tcp/ip a blaze They fix some problems but add more, you endup just like that xckd about protocols

Having switched to zigbee devices recently I regret trying to start with WiFi. While I'm not sure how it looks under the hood, adding devices with home assistant was miles easier.

Re: Zigbee vs. Matter over Thread:Understanding IoT Protocol Performance in Practice

#6
post #5
post #2

These protocols add so much complications it makes wifi/tcp/ip a blaze They fix some problems but add more, you endup just like that xckd about protocols

Having switched to zigbee devices recently I regret trying to start with WiFi. While I'm not sure how it looks under the hood, adding devices with home assistant was miles easier.

I've helped lots of people with home automation Network build outs l; the biggest factor is the RF environment.

If you're fortunate enough to not be battery constrained at most endpoints and can put a high quality Wi-Fi access point in an optimal location than Wi-Fi is incredibly reliable.

The tooling for inspecting all layers of a Wi-Fi network is infinitely more accessible and mature and that certainly helps; I can't go to My local big box store and get a USB thread dongle for 20 bucks that will just work on a Lennox computer and integrate nicely with Wireshark out of the box...

Re: Zigbee vs. Matter over Thread:Understanding IoT Protocol Performance in Practice

#8
post #5

Earlier quoted context omitted.

Having switched to zigbee devices recently I regret trying to start with WiFi. While I'm not sure how it looks under the hood, adding devices with home assistant was miles easier.

I've helped lots of people with home automation Network build outs l; the biggest factor is the RF environment. If you're fortunate enough to not be battery constrained at most endpoints and can put a high quality Wi-Fi access point in an optimal location than Wi-Fi is incredibly reliable. The tooling for inspecting all layers of a Wi-Fi network is infinitely more accessible and mature and that certainly helps; I can…

No, you have to order it from Mouser for $16 instead.

Fixed link: https://www.mouser.com/en/ProductDetail/Nordic-Semiconductor...

And there’s a little configuration: https://wiki.makerdiary.com/nrf52840-mdk-usb-dongle/guides/n...

Re: Zigbee vs. Matter over Thread:Understanding IoT Protocol Performance in Practice

#9
post #5
post #2

These protocols add so much complications it makes wifi/tcp/ip a blaze They fix some problems but add more, you endup just like that xckd about protocols

Having switched to zigbee devices recently I regret trying to start with WiFi. While I'm not sure how it looks under the hood, adding devices with home assistant was miles easier.

Thread is fairly similar to Zigbee, just standardized and doesn't require brand specific hubs. You can actually control thread devices direct from an iphone with no hub at all.

Wifi for anything but cameras is a mistake, it only exists for maximum compatibility since everyone has wifi already.

Re: Zigbee vs. Matter over Thread:Understanding IoT Protocol Performance in Practice

#10

A lot of graphs where OpenThread & zigbee dance around each other, are within 2x of each other. Two huge notables to me: message throughput for openthreads scales up, zigbee seems to hit a wall early. Not sure when that matters but very clear. The last table was a fright through: it takes half a minute for OpenThreads to recover after a node drops where-as Zigbee a quarter second! Wow.

Is there a situation in which your smarthome taking 30s to recover from a node failure is impacting your life? Seems like a distinction without a difference
Post reply on HN