Domoticz

Barry wrote: ↑Friday 24 September 2021 14:48 I updated Domoticz today to the latets beta, did load the new firmware on the Doorbell/Alarm 6, excluded and included the device but there is no difference. It still does not work.

Barry wrote: ↑Thursday 13 January 2022 20:09 I am using firmware ZW164_Siren 6_EU_V1_06. The volume and tones are not configurable via Domoticz, but if you pre-set them as described by yourself earlier in this post using Z-Wave PC Controller then it is usable. Domoticz creates 8 different buttons to trigger 8 different sounds which all individually can have a melody and volume. For me that is more than sufficient. I only need three of them.

Hencor wrote: ↑Friday 14 January 2022 10:33

Barry wrote: ↑Thursday 13 January 2022 20:09 I am using firmware ZW164_Siren 6_EU_V1_06. The volume and tones are not configurable via Domoticz, but if you pre-set them as described by yourself earlier in this post using Z-Wave PC Controller then it is usable. Domoticz creates 8 different buttons to trigger 8 different sounds which all individually can have a melody and volume. For me that is more than sufficient. I only need three of them.

I just did some research again. Volume and tones should be configurable via the OZW Controlpanel inside Domoticz (I did not test it by myself for now). And this should also be changeable via JSON calls. So it should be easy make a virtual switch to mute the doorbell for example.

My scenario: Mute the doorbell when the children are asleep. Or at least turn down the volume.

Can I ask in which scenarios you are playing the different sounds?

Barry wrote: ↑Saturday 15 January 2022 12:58 With the beta I am running right now the OZW Control Panel seems to have disappeared, not sure why but I cannot access it at this moment.

Hencor wrote: ↑Tuesday 03 September 2019 21:07 I just managed to configure the volume and the tone witch is trigged with the button.

Its a solution past domoticz. I used the windows software "Z-Wave PC Controller 5" to send the right commands to the doorbell. I just downloaded the software and plugged my Aeotec Z-Stick in. So I could communicate with each device in my Zwave network. With the help of the Aeotec Engineering Specifications (from the 2019-01-17) it's easily possible to detect the right command (classes) to configure each tone and volume for each trigger (Button 1-3, Tamperalarm, Zwave Alarm, etc).

Well, I just forgot to make some screenshots...

waltervl wrote: ↑Tuesday 29 March 2022 9:37 You could try to move to ZwaveJS2MQTT as it is the current preferred gateway for Zwave in Domoticz...
OpenZwave is being deprecated in Domoticz because there is no development anymore in OZW.

lost wrote: ↑Tuesday 29 March 2022 12:17

waltervl wrote: ↑Tuesday 29 March 2022 9:37 You could try to move to ZwaveJS2MQTT as it is the current preferred gateway for Zwave in Domoticz...
OpenZwave is being deprecated in Domoticz because there is no development anymore in OZW.

Would prefer to send back problematic hardware to vendor than changing z-wave backend, with almost everything to rebuild up from the ground!
All these MQTT driven stuff also looks to need a learning curve as it's mostly external to Domoticz and far from tight integration offered by OZW library.

And, did not dig into this for now & tell me if I'm wrong there... but looks strong advice is to use some containerization for mosquito and all clients (zwave, zigbee...) that directly connect to it: Issue is that's not only adding to the (formerly unneeded) learning curve but IMO most of the times is an external sign of a melting pot software done quick&dirty, reusing many avoidable dependencies & of course not willing to deal with the associated nightmare of managing them over time! Really don't like this kind of approach to SW.