Connecting Velux Active KIX 300

[laursen (Jacob Laursen)]

@Sprocket1979

How did you manage to get the sign_key_id for opening windows.

I’m also interested in this, as well as some examples. I never managed to set the home/away status, this would be the absolutely most interesting thing for me.

[ulrichpa]

@ulrichpa

Hi,

thanks for all your contributions! I can now control my windows with the methode desicbed by @brusch , thanks also to @pierlomb65.

However, I’m struggling to get the exec thing to work. I implemented everything as desribed, and my python command to open the windows works perfectly if executed in the terminal directly:

python -m homekit.put_characteristic -f velux -a velux -c 3.11 0 -c 5.11 0

But executing the exec binding brings the following error/warning:

2023-05-07 12:57:46.602 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'Windows_Open' predicted to become ON
2023-05-07 12:57:46.606 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Windows_Open' changed from OFF to ON
==> /var/log/openhab/openhab.log <==
2023-05-07 12:57:46.607 [DEBUG] [ng.exec.internal.handler.ExecHandler] - Passing to shell for parsing command.
2023-05-07 12:57:46.608 [DEBUG] [ng.exec.internal.handler.ExecHandler] - OS: *NIX (Linux)
2023-05-07 12:57:46.616 [INFO ] [org.openhab.core.model.script.test  ] - executed
2023-05-07 12:57:47.077 [DEBUG] [ng.exec.internal.handler.ExecHandler] - Exec [OUTPUT]: 'Could not open "velux" because it does not exist'
2023-05-07 12:57:47.174 [DEBUG] [ng.exec.internal.handler.ExecHandler] - Transformed response is 'Could not open "velux" because it does not exist'

The thing is defined as follow:

Thing exec:command:Velux_Windows_Open "Velux_Windows_Open" [command="python -m homekit.put_characteristic -f velux -a velux -c 3.11 100 -c 5.11 100", interval=0, timeout=5, autorun=false]

I assume there is an issue with the role of pyhton. I already tried to execute it as sudo -u openhab python… but with no success.

@rlkoshak maybe you have an idea here?

Many thanks!

Any ideas on this?

[macIsle (Christoph)]

If you still struggle with setting up your Thing:
The definition file is (if you created it with the help of the above mentioned tutorial) not located in the folder where the EXEC is running. Therefore change the Thing command to where the file is (probably standard startup of SSH)

python -m homekit.put_characteristic -f /home/openhabian/velux -a velux -c 3.11 0 -c 5.11 0

[markusta (Markus Tallén)]

Hello!

Do you know where I can find “sign_key_id” and “sign_key_id”?

/Markus

[Wolfgang_S]

@markusta

Do you know where I can find “sign_key_id” and “sign_key_id”?

I think it is required to sniff the network traffic of the app as desribed in post 11

[markusta (Markus Tallén)]

Found the “SignKeyId” and the “HashSignKey”, when calculating the “hash_target_position” according to GitHub - ZTHawk/velux_active_patches I get Error 9 when sending. Anyone has some idea what might cause that?

[DanVer (Daniele Veronesi)]

Hello,

I am trying to use the solution based on the “HomeKit” approach, as explained above.

I am executing the following command inside a rule

var String veluxShutter
veluxShutter = "2.11"
var int position
position = "50"

val String Answer = executeCommandLine(Duration.ofSeconds(2),"python3","-m","homekit.put_characteristic","-f","/home/openhabian/velux","-a","velux","-c",veluxShutter,position)

logInfo("shutters", "Result:" + Answer)

When I trigger the concerned rule an error is triggered and the outcome in the log is the following:

Result:/usr/bin/python3: Error while finding module specification for 'homekit.put_characteristic' (ModuleNotFoundError: No module named 'homekit')

I understand that the execution folder of the “executeCommandLine()” is not the one where the module is stored. However, I am not able to address the execution to a diffrent folder.

Anyone would have an idea on how to make it?

---

Comment added later:

I realized that the user for the executeCommandLine() is : “openhab” and the module homekit is not available for this user. (sudo -u openhab pip list)

In this page: https://github.com/jlusiardi/homekit_python#installation

The installation makes use of the key “- -user”

I run again the installation of the homekit module with
sudo pip3 install homekit…
and now the module is available also for the user openhab.

Issue solved!