If @hizo doesn’t know how to retrieve the info, yes
I’ll send you the info in a DM
1 Like
@pierre-gilles I’m just checking in…
I did receive the siren but it’s not simple because my dongle that I use for my tests (conbeeII) detects the siren very poorly and once detected can’t control it from zigbee2mqtt…
In my production Gladys with a SONOF key there’s no problem. However, not all parameters are taken into account. For example, it’s possible to choose the alarm tone but that doesn’t work. In that mode only the STOP or BURGLAR command works.
@Hizo Can you also not change the type of alarm tone from the zigbee2mqtt interface?
I’ll try as soon as I can to send the MQTT command manually with MQTT Explorer and see if it works better… To be continued
So I ordered another Zigbee dongle for my tests… it’ll be simpler and I’ll put my conbeeII key up for sale.
1 Like
That triggers it if it’s not ‹ stop ›, but there’s no change in the alarm type.
Yes, same as me then. I’ll make sure we can at least trigger it from Gladys.
1 Like
I received my new dongle; I’ll be able to watch this weekend.
1 Like
Okay, I made some progress by adding detection of whether the siren is connected to mains power and of volume changes.
Now I’ll look into the ‹ Warning › expose but personally I don’t like this siren. It’s very temperamental and we often get errors on the zigbee2mqtt side.
Also the parameters of this Warning have practically no effect via zigbee2mqtt
Personally I do not recommend this siren at all.
Cool if you were able to take a look 
keep us posted !
Ah 
if it’s really not great, I can contact Domadoo support for a return and get you another one if you want?
I’m still working on it a bit, but I think you’ll be able to return it to Domadoo.
No need to order another one because I ordered the siren below at the same time as my new Zigbee USB stick. It is not yet fully supported in Gladys. I’ll take care of adding the missing features for it later (melody type, battery level…).
On the zigbee2mqtt side you have to play with the expose « warning » parameters to activate the alarm. As I said these parameters have almost no effect
Only the mode works partially. That is to say all choices produce the same sound and « stop » does stop the siren.
The other parameters level, strobe level, strobe, strobe duty cycle and duration have no effect.
So I tried sending the command to activate the alarm manually with MQTT Explorer.
So you need to send the payload below and modify the different parameters
{
"warning": {
"mode": "burglar",
"level": "low",
"strobe_level": "low",
"strobe": true,
"strobe_duty_cycle": 10,
"duration": 10
}
}
Same result as zigbee2mqtt.
You can therefore reduce the payload to {"warning":""} to activate
and
{
"warning": {
"mode": "stop"
}
}
to stop the alarm before the defined time ends.
And manually, as in zigbee2mqtt, sometimes it takes a while before it works.
3 Likes
Ah great, I have that model too.
I could test it if needed.
Ok, as you wish, keep me posted
Yes, I’ll keep you posted but the point is that @Hizo can still operate their siren, that’s why I want to continue anyway.
2 Likes
I also have this model, it’s cool!!
2 Likes
I haven’t made much progress on this topic this week, but I could use some help because I don’t see how to handle the expose that is of type composite. No problem with the other exposes but I’m a bit stuck on this one.
It therefore contains other exposes of type enum, binary, numeric
@pierre-gilles or @AlexTrovato if you could point me in the right direction
{
"access":2,
"features":
[
{
"access":2,
"description":"Mode of the warning (sound effect)",
"label":"Mode",
"name":"mode",
"property":"mode",
"type":"enum",
"values":["stop","burglar","fire","emergency","police_panic","fire_panic","emergency_panic"]
},
{
"access":2,
"description":"Sound level",
"label":"Level",
"name":"level",
"property":"level",
"type":"enum",
"values":["low","medium","high","very_high"]
},
{
"access":2,
"description":"Intensity of the strobe",
"label":"Strobe level",
"name":"strobe_level",
"property":"strobe_level",
"type":"enum",
"values":["low","medium","high","very_high"]
},
{
"access":2,
"description":"Turn on/off the strobe (light) during warning",
"label":"Strobe","name":"strobe",
"property":"strobe",
"type":"binary",
"value_off":false,
"value_on":true
},
{
"access":2,
"description":"Length of the flash cycle",
"label":"Strobe duty cycle",
"name":"strobe_duty_cycle",
"property":"strobe_duty_cycle",
"type":"numeric",
"value_max":10,
"value_min":0
},
{
"access":2,
"description":"Duration in seconds of the alarm",
"label":"Duration",
"name":"duration",
"property":"duration",
"type":"numeric",
"unit":"s"
}
],
"label":"Warning",
"name":"warning",
"property":"warning",
"type":"composite"
},
Hi, as far as I remember, you can take inspiration from the « color » exposé (RGB…) which is also a composite.
If I turn on the computer this weekend I’ll give you more details.
1 Like
I think I understood after looking into how the expose « color_xy » was formed.
Thanks.
EDIT: I managed to send the correct command from Gladys
; functionally it looks good to me, I just want to check the « melody » enum part to see if the code is in the spirit of the integration or if we can do it differently
No problem.