That device doesn’t support S0 or S2 security so I have no clue why it’s displaying that message, but instead of using the “Scan Nearby” method to join it you should try choosing Dome from the brand list and then select the siren.
If the device doesn’t get assigned the handler automatically you’ll need to open it from the IDE and change the Type field to the custom handler, but after doing that make sure you go into the device settings from the mobile app and change any setting. That will force it to initialize all the attribute values.
I realized my Samsung account was not registered under US, so I raised a ticket to change it to US. After that, there was an update on the app. Ok, so I deleted the siren from the app, deleted device handler code and restarted ST hub before reading Dome siren (choosing Dome from brand list), reading device handling code, reading the GitHub repository and republishing. During siren installation process I got an error message and after adjusting device type at IDE I got the same status; I can’t change any setting
Remove the device and hold the action button for at least 10 seconds to factory reset it.
If you run into the same problem after doing that then try joining the device without my handler installed.
The built-in handler for that device is “Z-Wave Siren” so if it doesn’t get assigned that handler during inclusion and the raw description is still showing 0000 then it’s either a problem with the device or the hub so you’ll need to contact SmartThings or Dome.
Ok, same result after default factory reset, with and without your handler installed.
I had just ordered a replacement, I’ll keep you posted when I get the new dome siren.
Thanks a lot for your support so far!
Hello! I have a DMS01 Dome Siren/Strobe.
I believe I have this DTH installed correctly as I followed the instructions carefully and I see what I believe is the new UI. But something is not quite right:
I can’t get it to just strobe the LED. If I go into the device, in the “Alarm type” box, if I select (Strobe), the button “spins” for a few moments but then the siren AND the strobe go off and the (Siren and strobe) button lights up as if it had been that button I pressed. Pressing the (Siren) and (Siren and strobe) buttons behave as expected.
Also, if I set up an automation to trigger the strobe and/or the chime it doesn’t work (nothing happens). If I set the same “If” to “then” trigger a siren instead, it does work.
I’m not ruling out me having done something wrong (in fact, I rather hope that’s the case and someone can help me figure out what). Where do we start?
I believe that I asked this question previously but I am unable to find it in the thread. Have you or will you be developing an Edge Driver to port the capabilities of this Custom Device Handler over to the new architecture?
That’s awesome! Thank you Kevin! Where can we look to check and see if it’s available?
Also, I’ve been wanting to learn the new architecture. I have looked for links to good documentation, but found it seemed to go to the old stuff. Do you have any links to a good source of documentation on the new stuff? - Jonathan