Remix.run Logo
jauntywundrkind 7 hours ago

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.

richwater 5 hours ago | parent [-]

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

denkmoon 41 minutes ago | parent | next [-]

Do you have any smarthome stuff? Standing around waiting 30 seconds for your light to come on would be moronic. A complete regression over the electric switch invented in 1884. I'd rip everything out right then and there. Your home should be reliable, smart or no.

4chandaily 5 hours ago | parent | prev | next [-]

Standing outside with an armfull of groceries, and a door is now our of range of your hub temporarily due to the failed node. 30s can seem like quite a while standing in the rain.

AlotOfReading 4 hours ago | parent [-]

Not exactly a strong argument if you need like 5 qualifications to demonstrate the issue. If the right node fails, if it happens right as you walk up, if it's raining, if your porch is uncovered, if your door doesn't have an immediate fallback... I'm sure someone will be affected because of the law of large numbers, but it seems like an unlikely scenario to base a purchasing decision on.

codeflo an hour ago | parent [-]

A light switch not working for 30 seconds, or a door not opening for 30 seconds, even if only sporadically, is a significant loss of life quality, no qualifiers needed.

alexjurkiewicz 3 hours ago | parent | prev [-]

Because IOT devices are cheap and networks are ad hoc, flaky connectivity is a likely occurrence. Thread must be reliable in these situations.