[Device Support Request] SZ-SRN12N Sercomm Corp.

[salopette]

Can you please add SmartThing siren!

[salopette]

do you need more info?

[Smanar]

I think it's enought, but no user motivated ^^.
You can try yourself. You have 2 situations, the device is standard and you have already a siren that work like yours, so you just have somes lines to change on the code or you can have an exotic device and need to use so much workaround.

If you wana try your luck, I can explain you how to make modification on the code, but I can't promise you it will working.

BTW are you sure it 's not supported (Some device are working by defaut) ?

you have take a look in the API ?

On deconz, on the cluster 0502, you will find some action to test it.

[salopette]

Hi, I think the device itself is problematic.
When I reset it and relearn it, it is connected for a short time and then the connection breaks off.

[Smanar]

Ha ok, so not the same problem, harder.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[salopette]

Why closed?
Please add the device.

[Smanar]

It's a bot that close issue if no one is using it.

But ATM if the device can't be include in deconz, It's harder. You need someone with a sniffer take a look on trafiic to see the problem

When I reset it and relearn it, it is connected for a short time and then the connection breaks off.

As you are the owner, I think you can re-open it.

[beneffm]

Hi all!
I also have the device here, experiencing the same issue. Is there any chance to get it running? How can I help :) ?

[paulmann1590]

The sirene is at the moment quite cheap available for 6 euros, so is there any chance to get it running? :)

[SwoopX]

The device is supported out of the box as far as I can tell. However. for the pairing to be successful, it is required to apply a configuration change in deconz GUI. For that, go to Edit -> Network settings -> Endpoints (or press F9 -> Endpoints) and add 0x0502 to the Out clusters of endpoint 0x01.

When the device has been paired, it is further (currently) required to manually enroll it to the coordinator. Again from deconz GUI, select the IAS Zone cluster of the device and first check the current status by reading the attributes. If the attribute IAS_CIE_Address still contains only zeros, enter the MAC address of your coordinator by double clicking on the value field (must be entered with a leading "0x"). If that is not done and the device looses power, it leaves the network and gets reset when connected to power again.

EDIT:
The device now enrolls automatically.

[ebaauw]

When the device has been paired, it is further (currently) required to manually enroll it to the coordinator.

@SwoopX you need to whitelist the device so a ZHAAlarm /sensors resource is created, for the REST API plugin will do the IAS Zone enrollment. Check the code for the Heiman siren.

The device doesn’t seem to have a backup battery, so the ZHAAlarm will be useless otherwise.

[SwoopX]

@ebaauw Pretty sure it did that during the tests, but let me double check it again. Thanks for the hint. There's always one more place to whitelist...

[SwoopX]

@SwoopX you need to whitelist the device so a ZHAAlarm /sensors resource is created, for the REST API plugin will do the IAS Zone enrollment. Check the code for the Heiman siren.

The reason actually was that the device is NOT IAS zone, but IAS warning device. The logic didn't handle that. It's fixed now and works smoothly.

[Greglog]

Hey guys,

I am trying to get the siren working. Its visible in the Phoscon App, but I am not able to switch on the siren - neither directly in the app nor via OpenHab.
The strange thing is: on the setting page, when trying to change the name, it goes on and make the alarm-sound
Any ideas? What could I check?

[SwoopX]

It can be triggered via REST API only and works with values select and lselect on parameter alert for the lights resource.

[Greglog]

Ahh - thanks
It works...