Domoticz

Posted: **Saturday 20 November 2021 7:03**

Hello, I have been using Dashticz for years and find it very good.
Thanks to those who are working on it.
I have noticed an inconsistent behavior on the "speak_on" and "speak_off" commands. The sound is triggered even if the state has not been changed which creates unwanted alerts. Could you not set a simple rule so that the sound only triggers when the state goes from on to off or from off to on and ignored the rest?

Thank you

Posted: **Saturday 20 November 2021 7:09**

a good example is an RGB lamp, when changing the color or dimming the speak_on call is sent, while the state is always on

Posted: **Sunday 21 November 2021 12:47**

Renber wrote: ↑Saturday 20 November 2021 7:03 Hello, I have been using Dashticz for years and find it very good.
Thanks to those who are working on it.
I have noticed an inconsistent behavior on the "speak_on" and "speak_off" commands. The sound is triggered even if the state has not been changed which creates unwanted alerts. Could you not set a simple rule so that the sound only triggers when the state goes from on to off or from off to on and ignored the rest?

Thank you

Currently a Domoticz device is considered as changed when the LastUpdate value of the device changes.
So indeed if a light is on, and then receives an additional 'on' command then this will trigger the speak_on or speak_off events in Dashticz.

I'm not sure whether this should be changed, because probably some users (including me) make use to this.

I'll think of a clean solution to prevent regression. Suggestions are welcome.

Domoticz

Problem with sound "speak_on /speak_off"

Problem with sound "speak_on /speak_off"

Re: Problem with sound "speak_on /speak_off"

Re: Problem with sound "speak_on /speak_off"