This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

Alexa and windows control
#1
As any one been able to control properly a window through Alexa?

The problem I am facing is that when I ask Alexa to close the window, I get on the bus a 0 sent to the group address.
Unfortunately, in KNX a 0 means go "up" when you control a window, which opens it.

I do use the Power State skill, as it is the only one I think that deals with bits.

It looks like I need to invert somehow the given value to get the proper results when dealing with windows. 
Any suggestions on how to do it properly?

Thanks.
Michel.
Reply
#2
You could create a virtual object that receives the command from Alexa and control the actual window object from there with this event based script:
Code:
grp.checkwrite('1/1/1', not event.getvalue())
This command will send a inverted value to your bit object
Reply
#3
Or your just create a custom Command in the Alexa App. There you can complete the sentence Close the Window or Shut down the Window. then just choose send 1 and done.
Reply
#4
Thanks for the support, I will test both solutions.
Reply
#5
(16.10.2020, 08:06)MichelDeLigne Wrote: Thanks for the support, I will test both solutions.

FYI, checkwrite is not the best approach: If someone moves partially the window, it does not use the same group address to do so.
Because of this, LM does not detect a change of value and does not send anything when the order comes from Alexa, because he thinks the window is still in the original position.

The proper solution is to use an instruction that always sends the value to the group address, like: 

Code:
grp.write('13/0/5', not event.getvalue())

This works fine in any cases.
Michel
Reply


Forum Jump: