If somebody from SmartThings reads this, did you teams missed the (Smoke Sensor) Zigbee Siren to be run as a local DTH?? Its running on cloud! (Edit: yes its there in the github public repo, but no local exec).
This means for example if STHM (which I understand is local, might be wrong) triggers because of a break-in, but they cut the fiber optic/coaxial/phone cable for the internet, the alarms/sirens will not sound??
Can you please put the Native Zigbee siren DTH into the local execution?
Thanks @JDRoberts , yes I contemplated all those options (I might try the on/off trick), that’s why I’m eager for the 0.35.x firmware to release (local automations code feature flag).
The problems I have/had are that:
SmartLighting doesn’t exist here (NZ)
zigbee outlets natively supported are nowhere to be found (SmartThings outlets one are due on march in AUS (FINALLY after YEARS), to ship to NZ from AUS),
Outdoor alarms are practically non-existent for Zigbee (a few models here and there, but REALLY hard to get them),
There’s only 1 model Z-Wave outdoor siren in AUS for the AUS/NZ/Brazil z-wave spectrum (which I’m not sure it’ll even work local, and its freaking EXPENSIVE+shipping)
Aeotec is CRAZILY expensive here (chinese plug xiaomi outlet: 15/20 nzd, smartthings outlet 45+ship, aeotec 105)
And the only reason I’m still sticking with ST and not go the hubitat way (yeah yeah I know), its because I’m heavily invested in Samsung and have the damned Arlo cameras. (and got other reasons why I would like to shift that’ll be happy to share privately), but for now I’m stuck.
Not a fan of Z-Wave, had very bad experience in ICS (Industrial) with that ugly ‘not sharing my standard’ protocol.
It is also worth noting that there is some other SmartThings branded devices which are also cloud execution like the SmartThings ZigBee power monitoring plug, however I would imagine with the push for local execution with the new.API solutions (RulesAPI) these will get a local execution soon.
Just an FYI some devices can be switched to local execution via changing the DTH to another standard DTH or adding the “runlocally: true” in the definition of the DTH works in some cases
Smoke sensor is a whole different device class. A Siren can be activated (made to sound) from the network, but a smoke sensor typically cannot (except for test mode). So the switch option doesn’t work.
I’ve known about the runlocally: true + executeCommandsLocally: true + genericHandler: “Zigbee”, but as you mentioned its a lottery to know when it’ll work or not, as it is not yet clear to me which cases are those (I’m guessing depending on the code you run (how ‘standard’ vs ‘custom’ it is, or maybe depends on capabilities?) the runlocally flag will ‘probably’ copy the groovy code into the local JVM of the hub (which I’m guessing at this point is what the IDE does after IF controls).
Its still a swamp to me to know when a custom DTH ‘might’ run locally, and if it doesn’t, what does the device do (revert to a generic handler, “genericHandler: “Zigbee”” might just do that, and ‘flag’ the device to use standard zigbee Java/Groovy ST methods like on() off(), but this is also still an unknown (no documentation reference).
Long story short, too many unknowns yet on what runs local, and what doesn’t (this might mean ill use some off time to prove when it does/doesn’t and create a post about it )
One of the problems to solve because of that is that my mum and grandma are deaf (so if the siren (edit: i’ve done it again , i mean smoke sensor) is triggered she will not know), so in this example I wanted to trigger a strobing light in a specific pattern (which is what we do for the bell for my grandma) when the smoke alarm sound lets say at night when people are sleeping.
I hear your pain as it is also mine as one of the users in NZ! Which Zigbee Smoke Sensor are you using? I was planning to go for Z-Wave ones from Heimann. Also, have you looked at the indoor Z-Wave sirens (not smoke sensors)?
The Heiman Zigbee HS1-SA is actually sold here in NZ which means it should have passed certification, and is compliant with BS EN 14604 as required by law (The newer HS3’s zigbee 3.0 ones are compliant with the standard also supposedly, but havent seen them yet around).
For the Z-Wave ones I haven’t seen them sold here (at least where I looked) so careful with the frequency (I’ve heard one case where RSM has gone to a home where they used a US Z-Wave device, and asked politely to turn off the device).
Edit: As for the internal alarms (sirens (properly named now :P)), I’ve been using some Tuya zigbee TS0216 (little (7cm diameter, 3.5cm tall) loud (roughly 85~100db) nice ones with light and internal battery, and the volume is controllable (need to publish the DTH yet). For outdoors, the only available thing is the ZM1621BR that smarthome.co.au sells which is Z-wave (AU/NZ compliant).
I’ve actually got them directly from china (one came defective), but they are (overly expensive) sold here in NZ, under the ‘Trust Smart Home’ brand, with model ZSDR-850 (They are actually the HS1-SA’s)
You might find the conversation in this thread develops in an interesting fashion, if I haven’t already mentioned it before:
This dates from a time when if you pasted code with ‘runlocally: true’ into the IDE, you would get a cryptic error as it wasn’t actually allowed for the community. Then suddenly it was. I always thought warning people about the error message would have been a more comprehensible solution.
Oh and my understanding is that the local handlers are part of the firmware download. So nothing dynamic is happening.