Local automations not so local?

[orangebucket (Graham)]

@Andreas_Roedl

Usually when you disconnect the Ethernet cable, the IP address remains assigned to the interface. But there’s a DHCP client (and network manager) running on the hub that detects that the link is down and deletes the IP address.

What if for whatever reason this IP address is used for the Thread network? This is pretty common when there’s a bridge interface (br0) is used instead of classic routing.

@h0ckeysk8er

Now, there is some probability that the TBR logic might expect there to be an IPv4 address, but if the ethernet interface is plugged into just a hub where no DHCP server exists and Thread still works, that kinda kills that idea.

All that sort of thing was where I was going with ‘So is this inevitable?’. It might be a knock on effect of the ethernet interface going down. Possibly/probably something that could be worked around if it was seen as a serious problem.

[mocelet]

@orangebucket

Possibly/probably something that could be worked around if it was seen as a serious problem

I don’t expect them prioritizing it, nor do I want to! There are many more quality of life improvements and features worth addressing first, like local control from the app or Matter enhancements to drivers and capabilities that I’ve been requesting.

Thinking about the future, with the advent of more smartphones including Thread radio and, hopefully, an eventual SmartThings app that can communicate locally with the hub, maybe it will be fixed naturally. If Thread becomes a first-class citizen at home, the hub will not care if other links are down.

[h0ckeysk8er (Bruce Pinsky)]

@mocelet

I don’t expect them prioritizing it, nor do I want to! There are many more quality of life improvements and features worth addressing first, like local control from the app or Matter enhancements to drivers and capabilities that I’ve been requesting.

Thinking about the future, with the advent of more smartphones including Thread radio and, hopefully, an eventual SmartThings app that can communicate locally with the hub, maybe it will be fixed naturally. If Thread becomes a first-class citizen at home, the hub will not care if other links are down.

Thread on your phone only works when you’re in proximity to the Thread network. You’ll still need some form of hardware-based TBR and remote connection service when you’re not.