Develco siren SIRZB-110 #4432

tyr84 · 2021-02-16T19:22:34Z

Describe the bug

I've added the siren, and it shows up as a light. However, I can only activate the siren through the deconz interface:

I've tried the same method as the develco smoke alarms, setting state-alert to select or lselect, both in the api, and through the deconz.configure service in home assistant, but there is no response from the siren.

Am I doing something wrong, also is it possible to reach the deconz functionality shown in the first screenshot through the api? (selecting warning mode etc)

By further testing and referencing #3232 in addition to the tech-manual referenced above, I've come to the conclusion that the bit mapping is off for this device

Warning mode 2 and 3 seems to act as the 2-bits controlling siren level, while siren level 0, 1 and strobe is somehow mapping to the 4-bits that control warning mode. The exact mapping is unclear for me

Steps to reproduce the behavior

Expected behavior

Screenshots

Environment

Host system: Raspberry Pi
Running method: Home Assistant deCONZ Add-on
Firmware version: 26580700
deCONZ version: 2.7.1
Device: ConBee II
Do you use an USB extension cable: yes
Is there any other USB or serial devices connected to the host system? If so: Aeotec Z-wave

deCONZ Logs

Additional context

SwoopX · 2021-02-16T20:07:47Z

Hm, it seems that the correct settings for Develco devices somehow got lost almost a year ago... Gotta check that on my smoke sensors as well.

The mapping of any bits isn't that hard as the specs define it (see #1593 (comment)). However, finding out what the device supports is a bit challenging.

Can you pleae check if Warning Mode 1 + Strobe + Siren 1 makes "some noise"?

tyr84 · 2021-02-18T14:19:31Z

No sound, just an error (see screenshot)

SwoopX · 2021-02-18T20:07:38Z

I assume this is due to a duration of 0 seconds?

tyr84 · 2021-02-19T07:54:45Z

Doesn't seem so:

Just to make sure there is nothing else wrong. This works (makes sound):

SwoopX · 2021-02-20T10:41:47Z

Ok, so I just checked the SMSZB smoke detector. The "old" version back in the days seemed to be rather sensitive on the combination to pick so that any audio alert goes off. Now I only have the newer ones and they pretty much work with an arbitraty combination.

The siren apparently is also a bit sensitive. Could you check once again if this combination gives you some audio?

tyr84 · 2021-02-20T21:06:15Z

Yep, it gives some sort of siren, pretty low "taaa-daaa-taaa-daaa" kinda sounds like a fire truck siren :-)

Warning mode seems to control siren level, Selecting Warning mode 2 and 3 seems to give high level
This seems to be in accordance with the tech manual:

[https://www.elektroimportoren.no/docs/lib/4514809-Manual-18.pdf]

As far as I understand your code, the bitmap is controlled by:

deconz-rest-plugin/general.xml

Lines 3049 to 3067 in 5b8d1a6

    
           <payload> 
        
           	<attribute id="0x00" type="bmp8" name="Options" required="m"> 
        
           		<value name="Siren level 0" value="0"></value> 
        
           		<value name="Siren level 1" value="1"></value> 
        
           		<value name="Strobe" value="2"></value> 
        
           		<value name="Warning mode 0" value="4"></value> 
        
           		<value name="Warning mode 1" value="5"></value> 
        
           		<value name="Warning mode 2" value="6"></value> 
        
           		<value name="Warning mode 3" value="7"></value> 
        
           	</attribute> 
        
           	<attribute id="0x01" type="u16" name="Warning duration" required="m"></attribute> 
        
           	<attribute id="0x02" type="u8" name="Strobe duty cycle" required="m" default="0x00"></attribute> 
        
           	<attribute id="0x00" type="enum8" name="Strobe level" required="m"> 
        
           		<value name="Low" value="0x00"></value> 
        
           		<value name="Medium" value="0x01"></value> 
        
           		<value name="High" value="0x02"></value> 
        
           		<value name="Very high" value="0x03"></value> 
        
           	</attribute> 
        
           </payload>

Which seems to flip the Warning mode and siren level

As far as I can tell Develco implements the zigbee standard for this command:

Disclaimer: I might be totally wrong, since I can't find any info on the bmp8 format

SwoopX · 2021-02-20T22:22:08Z

@tyr84
Gee, the first documentation from them I haven't checked for those details, as none of them has a solid info about that and then it turns out to be decent... first-world problems. However, they still got those challenges all over their docs ;)

Regardless, so it seems like the device doesn't support strobe and is allergic to using it. What actually controls the loudness is the siren level and not the warning mode (-> error in Develco documentation). So I'd let it go of on Burglar on highest audio level then.

tyr84 · 2021-02-21T10:49:56Z

Cool!

While on the subject, has there been any discussion to expanding the "alert" parameter?

It bugs me that this implementation "dumbs down" the siren to only one setting with short and long duration.

Given the IAS WD spec something like:
alert: { warning_mode: (int), strobe: (bool), siren_level: (int), warning_duration: (int), strobe_duty_cycle: (int), strobe_level: (int), }
or if complexity of classes is an issue, mapping warning mode to brightness, and siren level to saturation or something similar.

ebaauw · 2021-02-21T11:20:32Z

As far as I understand your code, the bitmap is controlled by:

The definition of the payload defines Warning Mode, Strobe, and Siren Level as separate uint4 and uint2 attributes, packed into a map8. There's more places in the ZCL standard where they do this, but the GUI doesn't support it. Hence I decided to expose the individual bits, so you get to play assembler yourself.

Note that Bitron devices seem to implement the bit order backwards (e.g. Siren Level is bits 6 and 7 instead of 0 and 1).

Different devices might define Siren Level values differently (particularly whether 0 is no sound vs low sound).

While on the subject, has there been any discussion to expanding the "alert" parameter?

My bad, today I would probably have exposed the sound as state.howl and the light as state.strobe, rather than re-(ab-)using state.alert. Duration can be set through state.ontime. I have yet to see a siren that uses different sound patterns for different Warning Mode values, and different sound volumes for different Siren Level values, hence no effort to expose these. The Heiman siren supports Stobe Duty Cycle, but I haven't seen any others that do, and mine broke.

You can set the following state.alert values:

Value	Warning Mode	Strobe	Siren Level	Comments
`none`	0	0	0	Alarm off
`select`	1	1	3	Alarm for 1 sec.
`lselect`	1	1	3	Alarm for 5 minutes*.
`blink`	0	1	0	Blink for 5 minutes*.
`all`	1	1	3	Alarm for 1 sec*, broadcasted to all devices.

*) Use state.ontime to set a different Duration.

tyr84 · 2021-02-22T12:25:36Z

Thanks for the reply!

Actually, playing around with the GUI settings on the Develco siren i get at least 3 different sounds, but since either the Develco device or GUI is not complying with ZCL (bits seems reversed, with siren level controlling warning mode and vice versa) it's non-trivial to exhaust the modes specified in the Develco manual.

Do you know if the GUI is compliant with ZCL? Looks like the Develco manual is. My impression is that warning mode 1-4 should represent individual bits in the uint4?

Mimiix · 2021-05-10T09:34:03Z

Re-opened on request of @tyr84

tyr84 · 2021-05-10T13:53:22Z

This was not fixed.

Currently running 2.10.4, which should include the bugfix.

Current state is that both "lselect" and "select" gives of a short, low volume beep

github-actions · 2021-06-01T05:01:16Z

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

github-actions · 2021-06-09T02:39:51Z

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.

jarlesb · 2021-08-17T20:50:02Z

The Develco Siren is still not working any chance you could look at it again?

This seems to be better aligned with the Develco spec, or did I miss something? Sorry does not seem that I manage to get the code properly formatted...

tyr84 added the Bug report label Feb 16, 2021

SwoopX mentioned this issue Feb 22, 2021

Various smaller bugfixes #4454

Merged

SwoopX linked a pull request Feb 22, 2021 that will close this issue

Various smaller bugfixes #4454

Merged

manup closed this as completed in #4454 Mar 3, 2021

Smanar mentioned this issue Mar 26, 2021

Tuya siren(TS0216) doesn't expose options to Home Assistant #4510

Closed

This was referenced May 9, 2021

Develco Siren still not working #4851

Closed

Develco SIRZB-110 #4852

Closed

Mimiix reopened this May 10, 2021

github-actions bot added the stale label Jun 1, 2021

github-actions bot closed this as completed Jun 9, 2021

jarlesb mentioned this issue Aug 18, 2021

Correct attributes of Zigbee siren / IAS WD device #5219

Closed

Smanar mentioned this issue Aug 2, 2022

Aqara smart smoke detector - JY-GZ-01AQ #5864

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Develco siren SIRZB-110 #4432

Develco siren SIRZB-110 #4432

tyr84 commented Feb 16, 2021

SwoopX commented Feb 16, 2021

tyr84 commented Feb 18, 2021

SwoopX commented Feb 18, 2021

tyr84 commented Feb 19, 2021

SwoopX commented Feb 20, 2021

tyr84 commented Feb 20, 2021

SwoopX commented Feb 20, 2021 •

edited

Loading

tyr84 commented Feb 21, 2021

ebaauw commented Feb 21, 2021 •

edited

Loading

tyr84 commented Feb 22, 2021

Mimiix commented May 10, 2021

tyr84 commented May 10, 2021

github-actions bot commented Jun 1, 2021

github-actions bot commented Jun 9, 2021

jarlesb commented Aug 17, 2021 •

edited

Loading

Develco siren SIRZB-110 #4432

Develco siren SIRZB-110 #4432

Comments

tyr84 commented Feb 16, 2021

Describe the bug

Steps to reproduce the behavior

Expected behavior

Screenshots

Environment

deCONZ Logs

Additional context

SwoopX commented Feb 16, 2021

tyr84 commented Feb 18, 2021

SwoopX commented Feb 18, 2021

tyr84 commented Feb 19, 2021

SwoopX commented Feb 20, 2021

tyr84 commented Feb 20, 2021

SwoopX commented Feb 20, 2021 • edited Loading

tyr84 commented Feb 21, 2021

ebaauw commented Feb 21, 2021 • edited Loading

tyr84 commented Feb 22, 2021

Mimiix commented May 10, 2021

tyr84 commented May 10, 2021

github-actions bot commented Jun 1, 2021

github-actions bot commented Jun 9, 2021

jarlesb commented Aug 17, 2021 • edited Loading

SwoopX commented Feb 20, 2021 •

edited

Loading

ebaauw commented Feb 21, 2021 •

edited

Loading

jarlesb commented Aug 17, 2021 •

edited

Loading