Velux Active & Polisy

[redridge]

Due to hail damage (little bumps on my skylight aluminum parts), and insurance, our re-roof turned into a free skylights upgrade.  The roofer had shown up on the job with (6) manual openers but when I told him all of ours were motorized via infrared control he arrived with the new solar models a few days later.  We were completely surprised as the last re-roof job they were just re-flashed.   So free $1000+ each skylights....sure we'll take them!  They are very impressive, but rf/wifi/bluetooth controlled.   I purchased the Velux Active starter kit and the Gateway module synched in with the Eero mesh wifi effortlessly.  Furthermore with IOS 14 they showed up in Homekit and I was able to expand into scenes somewhat like in the ISY for more flexible group controls.  Even Siri perked up and responds to verbal open/close/scene commands.  My Ecobee stat showed up there too.

But as usual I don't have a clue, other than reverting back to my old X-10 tricks to interface to these skylights via the ISY (I'm still stuck in the 90's). Velux has the current KLF200 (ordered) that accepts inputs from relays. There is still no relay module available for ISY (asking too much), other than buying into an entire alarm system with ugly keypads.  Will Polisy ever come to the rescue with the Velux skylights & blinds?

[lilyoyo1]

53 minutes ago, redridge said:

Due to hail damage (little bumps on my skylight aluminum parts), and insurance, our re-roof turned into a free skylights upgrade.  The roofer had shown up on the job with (6) manual openers but when I told him all of ours were motorized via infrared control he arrived with the new solar models a few days later.  We were completely surprised as the last re-roof job they were just re-flashed.   So free $1000+ each skylights....sure we'll take them!  They are very impressive, but rf/wifi/bluetooth controlled.   I purchased the Velux Active starter kit and the Gateway module synched in with the Eero mesh wifi effortlessly.  Furthermore with IOS 14 they showed up in Homekit and I was able to expand into scenes somewhat like in the ISY for more flexible group controls.  Even Siri perked up and responds to verbal open/close/scene commands.  My Ecobee stat showed up there too.

But as usual I don't have a clue, other than reverting back to my old X-10 tricks to interface to these skylights via the ISY (I'm still stuck in the 90's). Velux has the current KLF200 (ordered) that accepts inputs from relays. There is still no relay module available for ISY (asking too much), other than buying into an entire alarm system with ugly keypads.  Will Polisy ever come to the rescue with the Velux skylights & blinds?

That would depend on whether or not they have an open API for a developer to develop a nodeserver for it. A developer would also have to decide its something they want to take on as well.

[redridge]

Thank you again lilyoyo1.  That is why I included the short story mentioning the success with Homekit. Aren't they well on their way since Homekit picked it up so easily, and the fact that Velux is such a large player?

[bgrubb1]

If you have Zwave I use a Fortress Mimo2 plus as relays  super reliable compared to the smarthome IOLinc

 

[lilyoyo1]

3 hours ago, redridge said:

Thank you again lilyoyo1.  That is why I included the short story mentioning the success with Homekit. Aren't they well on their way since Homekit picked it up so easily, and the fact that Velux is such a large player?

No. Having homekit support means they added homekit support. Not that they have an API that someone can use to developer a nodeserver for

[redridge]

thank you bgrubb1, catchy name(fortrezz).  I will look into it.  Somehow I just can't see myself with a row of IOLincs!

Edited November 22, 2020 by redridge

[asbril]

4 hours ago, bgrubb1 said:

If you have Zwave I use a Fortress Mimo2 plus as relays  super reliable compared to the smarthome IOLinc

 

I have had 2 Mimo-lites for some three years to control automatic curtains and they have never failed me.

[redridge]

The Velux HA module appears to have separate trip inputs for open and close, and reacts differently depending on time length of the closure.  If I minimize and group I can get that down to three skylight scenes X2, requiring 6 inputs.  Do the Mimo2's also have spdt output relays? If so I would require two of them, if not three of them.  

[inovermyhead]

I'm facing the same problem - and was feeling less than enthused with the complexity of a MIMO2,  EZIO8SA or multiple IOLincs to control the skylight functions (2 opening skylights both with blinds)    Especially since Velux has opened an alternate way to control the KLF 200 by publishing the API (https://velcdn.azureedge.net/~/media/com/api/klf200/technical specification for klf 200 api-ver3-16.pdf)  With this it seems that it should be straightforward to write a node server.  My coding skills aren't advanced enough for this (I've looked at the node.js template node server) but I would be happy to help and/or test beta versions.  I do have a KLF 200 and installed skylights.  

[redridge]

On 11/22/2020 at 4:05 PM, inovermyhead said:

I'm facing the same problem - and was feeling less than enthused with the complexity of a MIMO2,  EZIO8SA or multiple IOLincs to control the skylight functions (2 opening skylights both with blinds)    Especially since Velux has opened an alternate way to control the KLF 200 by publishing the API (https://velcdn.azureedge.net/~/media/com/api/klf200/technical specification for klf 200 api-ver3-16.pdf)  With this it seems that it should be straightforward to write a node server.  My coding skills aren't advanced enough for this (I've looked at the node.js template node server) but I would be happy to help and/or test beta versions.  I do have a KLF 200 and installed skylights.  

     Thank you for that Velux API link.  My KLF200 just arrived today, very clean little unit with multiple references to input 3 which "as default, io-homecontrol° channel 3 is used used for communication and no signals are blocked".  Is that referring to the native language I've already used for the basic enrollment with the paper clip and the blinking LED on the gateway?  I suspect so.  And that API link would expand upon that?  Wouldn't that API already work with the Velux Gateway without the KLF200? Except for it's output relay?  I have a buddy that could maybe help us out.  I'll have to check with him on what kind of time he has.  He usually only wants twelve-packs of Coors Lite but maybe more for something like this!

[inovermyhead]

I think that the "channel 3" reference refers to the channel, as defined by the IO-homecontrol standard, used between the KLF 200 and other Velux products like the skylights or the KLR 200 remote control.  My understanding of the API is it is the instruction set for non-IO-homecontrol products to communicate with the KLF 200 via the ethernet connection on the unit.  So what we need is a nodeserver written to address the API instructions.   I'll happily contribute if your friend can do or help with this (although I'm in Boulder CO, so my contribution might have to be towards a good microbrew!)

You should also check to make sure that your KLF 200 is upgraded to firmware version 2.0.0.71.   Earlier versions apparently do not have the ability to be controlled via the API (mine was not updated as received.)  I can't immediately find & point to the instructions for updating the firmware but will search more carefully and report back.

[inovermyhead]

Updating the firmware requires logging into the KLF200 via its wifi network - the LAN port cannot be used.  The wifi SSID and password are given on the sticker on the bottom of the unit.   Once you're connected, go the listed URL, then login with the password shown there as well.  This should bring up the web interface; under "connections" there is a tab for "software update"

[inovermyhead]

Revisiting this thread - I would really like to have a Velux nodeserver - I've found a potentially useful bit of info:  OpenHab does have a binding for Velux and the KLF200 (https://www.openhab.org/addons/bindings/velux/)   I assume that a "binding" is similar in principle to a polyglot nodeserver, if different in actual form?  Might this be useful in putting together a Velux nodeserver?  I've started watching the "Developing Your First Node Server" videos from sjpbailey but am still feeling at a bit of a loss as to where to start.   Suggestions for a novice would be most appreciated.    

)  

[bpwwer]

it looks like there are both Python and node.js modules available that implement the API. I'd suggest looking over those and maybe experimenting with them first to understand better how to interact with the KLF200.

Then you have to decide what information is important to both for display and commands.  Use that to define what you want the nodes to look like on the admin console.  From there you can create the profile files and start creating a node server from the template available. 

Based on what little I've looked at, the KLF200 is a controller that supports a number of different devices, that means creating nodes with status/commands for all the different supported devices so it sounds like a fairly complex node server.

Another consideration at this point is that PG3 has just started alpha testing.  It's not ready yet to start developing node servers for it, but it will be soon.  It may not make sense to put in a lot of effort creating a new PG2 based node server and then more effort to convert it to PG3.

[inovermyhead]

bpwwer, thank for your suggestions - but of course they lead to more questions: You found the Python and node.js modules in the OpenHab binding?  I assume to experiment with these, I could load them onto an rPi and run them in Python?  And could and possibly communicate with them from the ISY using network resources?  Finally, PG3 is likely to require extensive redesign of (all?) current PG2 node servers?   Thanks   Novices need lots of hand-holding!

[bpwwer]

No not OpenHab, I just searched on github and npm for projects related to velux.  The ones I found provide simple examples to create a program that uses the module to communicate with the KLF200.   

The first one I found on github looked like you could load it on an rPi via PIP and create a simple python program that used it.    That's where I'd start just to get an idea on how to use the module.  Maybe look at more than one and pick the one that works best.  At this stage, not even trying to do any integration with ISY.

We're still working to define the PG3 API's, but there's no expectation that existing PG2 node server will run as-is on PG3.   How much effort will be needed to migrate a node server is still unknown.

[inovermyhead]

bpwwer,   Thanks, I will start with the GitHub and npm modules.