29.03.2021, 20:05 (This post was last modified: 30.03.2021, 00:10 by Paddyb.)
Hi, just wondering if anyone ever found a solution for this? I have a need to control some somfy blinds on a new project... Or alternatively is there any kind of gateway software/hardware to convert somfy tahoma to Mqtt, making control trivial from LM...
EDIT: So far I have this solution, but it involves a few steps... It's actually just the blinds I need to control rather than Tahoma itself. If the blind motors are the newer Somfy IO control models, It seems like the KLF-200 Gateway mentioned elsewhere on this form (a velux product but is IO-homecontrol compatible, so will pair with the somfy motors also) might work in conjunction with this docker image that exposes it via MQTT..
It needs a bit more hardware than I'd like (to run the docker container...maybe a din rail mounted RPI...) but it might be easier than figuring out the KLF200s API, or converting the Home Assistant Python or Node JS examples to LUA... (which is beyond my coding abilities)
If anyone has a more elegant solution please shout!
(29.03.2021, 20:05)Paddyb Wrote: Hi, just wondering if anyone ever found a solution for this? I have a need to control some somfy blinds on a new project... Or alternatively is there any kind of gateway software/hardware to convert somfy tahoma to Mqtt, making control trivial from LM...
EDIT: So far I have this solution, but it involves a few steps... It's actually just the blinds I need to control rather than Tahoma itself. If the blind motors are the newer Somfy IO control models, It seems like the KLF-200 Gateway mentioned elsewhere on this form (a velux product but is IO-homecontrol compatible, so will pair with the somfy motors also) might work in conjunction with this docker image that exposes it via MQTT..
It needs a bit more hardware than I'd like (to run the docker container...maybe a din rail mounted RPI...) but it might be easier than figuring out the KLF200s API, or converting the Home Assistant Python or Node JS examples to LUA... (which is beyond my coding abilities)
If anyone has a more elegant solution please shout!
Hi, I'm currently trying to work with KLF-200, but it's kinda early version. Currently it authorizes with KLF-200 and recognizes next confirmations and notifications: GW_PASSWORD_ENTER_CFM, GW_GET_STATE_CFM, GW_GET_ALL_NODES_INFORMATION_CFM, GW_GET_ALL_NODES_INFORMATION_CFM, GW_GET_ALL_NODES_INFORMATION_NTF, GW_GET_NODE_INFORMATION_NTF, GW_GET_ALL_NODES_INFORMATION_FINISHED_NTF and GW_COMMANDS_SEND_CFM. Also there's a function for GW_COMMAND_SEND_REQ which controls devices.
Wow! nice, I will take some time and try to understand your code, and will read it in conjunction with the official API documentation... At first glance, I understand more of what your code is doing rather than understanding the instructions in the Velux docs!... Your code is probably my rosetta stone! Thanks for posting, really appreciate it
(30.03.2021, 11:30)Paddyb Wrote: Wow! nice, I will take some time and try to understand your code, and will read it in conjunction with the official API documentation... At first glance, I understand more of what your code is doing rather than understanding the instructions in the Velux docs!... Your code is probably my rosetta stone! Thanks for posting, really appreciate it
Don't forget to upload velux-cert to LM with FTP. You can take it from Node JS github or get it by yourself with instruction.
(30.03.2021, 11:30)Paddyb Wrote: Wow! nice, I will take some time and try to understand your code, and will read it in conjunction with the official API documentation... At first glance, I understand more of what your code is doing rather than understanding the instructions in the Velux docs!... Your code is probably my rosetta stone! Thanks for posting, really appreciate it
I added some commands, getting statuses and moved functions to a library. Now it uses storage to save statuses, nodes and queue of commands. There's examples for event scripts but some comments in Russian, sorry =)
03.08.2021, 08:32 (This post was last modified: 03.08.2021, 08:41 by cumulusnimbus.)
(01.04.2021, 13:29)Snoolik Wrote:
(30.03.2021, 11:30)Paddyb Wrote: Wow! nice, I will take some time and try to understand your code, and will read it in conjunction with the official API documentation... At first glance, I understand more of what your code is doing rather than understanding the instructions in the Velux docs!... Your code is probably my rosetta stone! Thanks for posting, really appreciate it
I added some commands, getting statuses and moved functions to a library. Now it uses storage to save statuses, nodes and queue of commands. There's examples for event scripts but some comments in Russian, sorry =)
Great work @Snoolik! I have tried to get it working now. Seems its working 99%... I get Unknown command 211.. In the docs I cannot find 211 0xD3 or something siliar. It's not in the list in user.velux.lua either.. Any idea what this is? This command is from Velux to client right? I'll try to plough trough the python version from Velux to see if I can sort it out.
I'm running firmware 0.2.0.0.71.0.
Update:
Seems I was a little bit hasty.. its 0x211 and its GW_NODE_STATE_POSITION_CHANGED_NTF. Handler is not implemented. I will look into it.