logoalt Hacker News

ketzu • today at 5:56 PM • 2 replies • view on HN

Similar, just with "Matter" instead of Zigbee.


Replies

microtonal • today at 6:46 PM

Thread over Matter is not fully local. In Thread < 1.4, devices can connect to internet servers through NAT64. Most Thread Border Routers (AFAIR Home Assistant + OTBR is the main exception) do not allow you to disable NAT64.

In Thread >= 1.4, devices can request globally routable IPv6 addresses. The Thread 1.4 white paper does not hide the intentions:

The Thread 1.4 Border Router acts as the IPv6 router between the Thread network and external networks, including the user's home network and the larger internet. It is by default configured to support external communication [...]

Cloud Connectivity: Direct internet connectivity enables Thread devices to easily connect to cloud services. This facilitates remote monitoring, control, and firmware updates, enhancing the user experience and enabling remote device management capabilities. Device vendors can now directly service and support their deployed fleet of devices, regardless of which application ecosystem each device is integrated with.

https://threadgroup.org/Portals/0/Documents/Thread_1.4_Featu...

This is what you get when you let Google, Amazon, Apple, and Samsung design a smart home standard. They'll use every opportunity extract analytics and increase control. You'll own nothing and be happy.

Zigbee, Z-Wave, and ESPHome over WiFi/Thread are the only major modern local and privacy-preserving smart home standards.

Matter over WiFi is also not fully local for obvious reasons (though you can try to block them on the router/firewall and/or put them on a separate VLAN).

➕ show 4 replies
Spivak • today at 6:14 PM

Do you mean Thread or do you use Matter over Wi-Fi?

➕ show 1 reply