Hacker News new | ask | show | jobs
by manv1 1280 days ago
Yeah,it's going to be tough. However, the one good thing about Z-Wave (even relative to zigbee) is interoperability - devices pretty much work for the most part, even with generic drivers.

At some point there'll be a matter/thread bridge to z-wave.

The big question about matter/thread devices is cost.

The second is going to be security. If they're IPv6 then they're globally addressable, which is bad bad bad. How is that going to be mitigated? Is the hub going to be the router for those devices and block all incoming connections?

I'm sure this is all in the docs somewhere.

2 comments

> If they're IPv6 then they're globally addressable, which is bad bad bad. How is that going to be mitigated?

I think you need to read up on IPv6 a bit. There are whole IPv6 ranges set aside that are not globally routable / part of the global unicast range[1].

Thread has link-local and mesh-local addresses. The global is only gained through SLAAC/DHCP or manual configuration by an administrator so by default no, your devices aren't accessible to the outside world. And if you do have routable IPv6 in your network, you should already have a firewall on your network edge for this because all your existing devices would already be exposed. The addressing primer[2] for Thread also applies to Matter for further details.

[1]: https://www.iana.org/assignments/ipv6-address-space/ipv6-add...

[2]: https://openthread.io/guides/thread-primer/ipv6-addressing

> If they're IPv6 then they're globally addressable

All ipv6 addresses are routeable but that doesn't mean reachable. Link local and Unique local addresses are examples of non-global ipv6 addresses.

https://en.wikipedia.org/wiki/Unique_local_address