ST does not allow you to use status of multiple zones in a single routine as a trigger (any/all). For that you will need Sharptools with some JSON parsing or setup some virtual devices to mimic status of multiple zone configurations.
I have an exhasut fan I want to turn on for whenever someone is in my bath OR my shower. I have them as separate zones.
I realize I could combine them as they are adjacent in my use case, but I may figure out other routines I want them separate for. And for someone with a different bathroom configuration where they aren’t adjacent, it may not make any damn sense to combine them if they are not adjacent and want to define some other zone that separates them intentionally for some other use, like triggereing vanity lights.
With them configured as 2 zones, I can’t tell ST to turn the fan on if ANY of those 2 specific zones are occupied as a routine only allows you to select one zone.
Everyone has different use cases. It would be much more flexible in ST if there was the option to allow selection of multiple zones for single routines. It seems unnecessary to require me to create Sharptools rules or virtual devices to do something for a device that presents basically child devices with each zone that can be triggers.
Two zones, two routines.
Are you overthinking it?
3 Likes
It’s more related to reliably turning the fan off, and on when either zone is occupied and unoccupied with a delay to allow the fan to clear the space
Still two almost identical routines.
And nope, zones are not child devices. That would make it even more complicated. My power strips are one main device + four child devices each. That makes sense, because the amount won’t change.
Zones can be configured at any time with an external app. Imagine devices suddenly disappearing…
Sure, but since zones can act as triggers, each basically can be used as a device. Since you can configure multiple devices to be triggers, it makes sense to me to allow multiple zones to be set as triggers in an ANY/ALL fashion, just like you can with regular devices.
I will do some testing again with simple routines, but I recall it being glitchy when I tried it before. And it may have just been that since the zone boundary definitions are not as granular as I need that I was sometimes getting some false turn-on events when walking by the front of either my shower to bathtub, so I wanted a “stays this status for how long? = 3 seconds” and that isn’t possible in ST as 1 minute is the minimum duration for this setting.
So as I started working through it in Sharptools to get this start delay, I was having some difficulty with the programming of those rules where this functionality I’m talking about would have simplified the routine because only the pure JSON code of zone status is visible in Sharptools.
…and crap, I just now realized the customize allows me to do seconds!!! dammit! 
2 Likes
You are the one who doesn’t know how to do the right automations. All your examples are easily done in SmartThings routines, you don’t even need virtual devices, which greatly expands the complexity of automations.
1 Like
Agreed!!! For some reason, this one had me screwed up and I simply missed the customize option on the delay for the trigger. now where is that facepalm emoji??
1 Like
The FP2 has exactly one component (main) and one capability for presenceSensor that reports for all zones. (Haven’t seen the logs in a while, but that’s basically how it works). If each zone would be it’s own component and/or capability, it would be possible to do what you want. Take a temperature/humidity sensor for example:
Same device, different capabilities. Other devices have multiple components with the same capabilities.
It would be possible to have child devices with its own presenceSensor capability for every zone, but that opens a can of worms. Devices would be deleted, created whenever the device is configured through a third-party app… Kind of ugly. Maybe it would make sense if the FP2 had a fixed amount of zones.
1 Like