Hub Firmware Beta Group | Local Execution for Lighting Groups is Ready for Testing

[mocelet]

@jnettleton

It looks like you verified that you have local devices

Thanks, eventually found the issue. The light group does indeed work locally for on and off… but not if you disconnect the Ethernet cable which is how I was testing it .

Wrote a whole post about the topic, the hub stops running automations won’t communicate with Thread devices if the cable is disconnected, even if all the devices belong to the hub (Zigbee and Thread) and the automation is local:

Local automations not so local?

Let’s say you have only one SmartThings hub, which is also the only Thread border router and Zigbee coordinator. You create an automation so a Zigbee button turns on a Thread light. All is connected directly to the hub and the automation is as local as it gets, so it should always work. However… if you disconnect the Ethernet cable of the hub, the automation stops working. Is that expected? I could understand it in case it was a external Thread border router or WiFi devices were involved and whatnot, but in this case there’s no need to reach outside the hub to run the automation.

Edit: Forgot I did more testing, it’s not that the hub stops running automations, Zigbee-only ones will keep working with no Ethernet cable plugged, but not Thread ones (again, even if the hub is the only Thread border router and there’s no need to use Ethernet at all).

Anyway, it’s not a problem with the groups local feature but Thread handling. The execution location incorrectly displaying Cloud in the advanced website has also been fixed.

P.D: Please make the toggle local too so I can remove the “if light on turn off group” and “if light off turn on group” in my button routines . I know the light group has no state but I guess it can just check if any of the lights is on and then turn the group off or, otherwise, on.