I’ll let @Will_71 answer you, he’s the one who developed this PR 
@Hizo I’ll reply as soon as I can.
1 Like
@Hizo, here is my feedback. For many of the attributes of this siren, they are in zigbee2mqtt but it doesn’t do much. This siren is not the best siren.
Below is the detail:
Same for me. It has no effect in zigbee2mqtt. I added it in case another device needs this attribute.
That’s true, I will change it. This attribute was already in Gladys, I didn’t touch it. I will look into modifying it but it will not affect only this siren.
I hadn’t noticed the maximum value though. And we have the default value from Gladys.
Same for me. It’s the same reaction from the siren if you send the command manually with an external tool like MQTT explorer.
I didn’t modify the calculation of the signal intensity. It’s the same for all devices exposed in Gladys.
When you say it doesn’t change anything for you but triggers the alarm. What does that mean? Because as you said, it activates the alarm by changing the mode. That’s the official way to do it.
Yes, putting it in stop mode stops the alarm. That’s the only way to stop it. Same in zigbee2mqtt.
To activate the alarm from scenes, you need to control the alert mode. As in zigbee2mqtt.
A value greater than 0 activates it and 0 deactivates it.
I can look into adding the text found in the dashboard and in zigbee2mqtt
Same for me. It’s the same reaction from the siren if you send the command manually with an external tool like MQTT explorer.
I missed this attribute. I’ll add it.
I also need to rebase the PR with all the latest dev. I’ll let you know when a new image is ready.
Thanks for your tests.
I added the volume.
I’ll look at the other points tomorrow.
It’s always the same alert that is triggered.
But indeed, all behaviors in Gladys corresponded to those in z2m with this basic siren.
For real tests, a more qualitative one offering the different options would be needed.
I have no action to propose to control the siren:
Select a device first
I didn’t understand what you’re asking for.
I just discovered that if you don’t give a coin to a device, it is nowhere to be found in the state change block?!!!
@pierre-gilles: Is this expected behavior?
Now I can see the actions.
I just discovered that if you don’t give a coin to a device, it is nowhere to be found in the state change block?!!!
@pierre-gilles: Is this expected behavior?
Now I can see the actions.
I modified the max value and it’s a bit better for the adjustment
I also tried with the numerical value but it’s not suitable for large values either
One of the two displays needs to be modified as neither is suitable for large values.
Or we create a new control that combines the two
I also modified the scenes to display text values and not numerical values.
1 Like
The idea of the new is not bad visually.
The display of texts is infinitely more user-friendly!
That’s a good idea
Exactly, that’s the current behavior, but I agree that it’s not very intuitive. I’ve also been caught out several times too! 
I created a ticket:
1 Like
@Hizo, I just restarted the build for a new image
willde71/gladys-test:woox-siren
Hey, I don’t see any difference, I must have missed something:
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
0bf90d634994 willde71/gladys-test:woox-siren "docker-entrypoint.s…" 4 hours ago Up 4 hours gladys-siren-test
docker pull willde71/gladys-test:woox-siren
woox-siren: Pulling from willde71/gladys-test
Digest: sha256:0da2f8a8cdf45a982d6939ccd33508dd7b06535d824563ab15aa09baf4c8ecf8
Status: Image is up to date for willde71/gladys-test:woox-siren
docker stop gladys-siren-test
gladys-siren-test
docker rm gladys-siren-test
docker run -d --log-driver json-file --log-opt max-size=10m --cgroupns=host --restart=always --privileged --network=host --name gladys-siren-test -e NODE_ENV=production -e SERVER_PORT
=8001 -e TZ=Europe/Paris -e SQLITE_FILE_PATH=/var/lib/gladysassistant/gladys-production.db -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/gladysassistant_siren_test:/var/lib/gla
dysassistant -v /dev:/dev -v /run/udev:/run/udev:ro willde71/gladys-test:woox-siren
I can access the version of gladys but the same version as tested previously.
Hi, I didn’t have time to check this weekend, I’ll let you know during the week.
@Hizo, I just restarted a build, I hadn’t pushed to GitHub before starting it.
Not bad
However, if I click in the duration input and then click elsewhere, it triggers the alarm
Same thing if I’m inside and switch tabs in my browser.
The loss of focus shouldn’t trigger it