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
Problem with sound "speak_on /speak_off"
Moderators: leecollings, htilburgs, robgeerts
-
- Posts: 41
- Joined: Thursday 04 February 2021 8:10
- Target OS: Linux
- Domoticz version: Beta
- Location: Belgium
- Contact:
Problem with sound "speak_on /speak_off"
Linux Debian 12 Server: Domoticz beta + Dashticz beta + Node-Red + Homebridge
-
- Posts: 41
- Joined: Thursday 04 February 2021 8:10
- Target OS: Linux
- Domoticz version: Beta
- Location: Belgium
- Contact:
Re: Problem with sound "speak_on /speak_off"
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
Linux Debian 12 Server: Domoticz beta + Dashticz beta + Node-Red + Homebridge
-
- Posts: 2291
- Joined: Monday 29 August 2016 22:40
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Problem with sound "speak_on /speak_off"
Currently a Domoticz device is considered as changed when the LastUpdate value of the device changes.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
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.
Who is online
Users browsing this forum: No registered users and 1 guest