I have the problem that one of my dimmers doesn't automatically give a reply if it is set to another value. This is especially bad if you push one of the +, - or on/off buttons for a dimming channel in WebKNX - so the user doesn't see if the bulb is switched on or off or the dimming level.
For this reason, I added 3 rules (not elegant, but at this time I had my problems with "or"-logik):
I can see that the shell command is beeing triggered, but what happens is that if you push for instance the "on/off" button, the light is beeing switched off (for instance) and the rule is beeing started very quickly. But as the dimming is soft, the dimmer replies with its actual value while dimming down - This means that if I switch out the light, KnxWeb still displays a dimming value of about 48 % even if the light is switched off.
What I could do is to write a little shell script which waits for two seconds and then starts the read command, but I wonder if there is a more elegant solution within linknx or knxweb.
Thank you and regards,
Stefan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I have the problem that one of my dimmers doesn't automatically give a reply if it is set to another value. This is especially bad if you push one of the +, - or on/off buttons for a dimming channel in WebKNX - so the user doesn't see if the bulb is switched on or off or the dimming level.
For this reason, I added 3 rules (not elegant, but at this time I had my problems with "or"-logik):
I can see that the shell command is beeing triggered, but what happens is that if you push for instance the "on/off" button, the light is beeing switched off (for instance) and the rule is beeing started very quickly. But as the dimming is soft, the dimmer replies with its actual value while dimming down - This means that if I switch out the light, KnxWeb still displays a dimming value of about 48 % even if the light is switched off.
What I could do is to write a little shell script which waits for two seconds and then starts the read command, but I wonder if there is a more elegant solution within linknx or knxweb.
Thank you and regards,
Stefan
Sorry, the title should have been:
Sending a delayed telegram for correct acknowledgment
It's a shame that I cannot change it ;)
Hi,
There is a simple solution to this problem:
<action type="shell-cmd" cmd="/usr/bin/groupread ip:127.0.0.1 2/0/2" delay="2"/>
The delay parameter is configured in seconds, (it's in minutes if the number is directly followed by letter m or hours if followed by h)
Regards,
Jean-François
Hey Jean-François,
thanks for the reply. I supposed that there would be an easy solution in linknx -- and there it is!
Cheers,
Stefan