I am planning to get roller shutters and the 1st offer consists of using Somfy motors: io Homecontrol. I have read this can be challenging, but there is no-one else I can ask for her/his experience. Eventually I would like to integrate it in a stable matter in Openhab. No stable integration would mean an issue.
What I have found so far:
the Tahoma (switch of V2) can be integrated but this is a cloud based solution. Meaning a connection towards internet is necessary. I’ve read that in the past Somfy can be strict regarding the connection (to many usage can result in a ban).
the Velux KLF-200 is also a solution which can work properly. Advantage is that it is a ‘local’ / own network solution (no internet connection is necessary nor is an account necessary with a supplier)
I prefer the KLF200 solution, since it is a NON cloud solution (on my own premises).
I also read some stories regarding issues while pairing, missing functionality upto even locking the motor controls.
Is anyone willing to share her/his experience? Also the steps needed to pair the somfy with the KLF200?
My experience is as follows:
IO is a very closed protocol. Using a Tahoma-box to connect to openhab works but it’s a bit the opposite of what you are usually trying to achieve with openhab: you have an additional gateway which needs a permanent cloud connection.
I decided for Somfy RTS shutters because they can be controlled directly by openhab with an rfxtrx or an rf-link. I moved all my shutters to rfxtrx and got rid of the annoying Tahoma-box.
Downside is that RTS is not bidirectional but I don’t really care. Sending shutters to certain positions is realized in my openhab with timers and works like a charm.
I’m not sure whether the KLF 200 can operate somfy io shutters. At least the description in the internet says it cannot connect to somfy.
If I would buy new shutters now I think I would consider standard shutters with shelly switches.
Hi Larsen,
Thx for sharing your experience. I, however, like the feedback of the position and are using it right now (on the old shutters by using fibaro zwave switches). I found: Setting up a Velux KLF-200 io-homecontrol gateway which states it should be working but also found many sites which state it doesn’t. That’s why I asked if someone on this forum has made some experience.
I absolutely agree with your remarks regarding the tahoma option. Therefor the KLF sounds interesting.
I probably will order via internet, which allows me to return it, if it’s not working as expected.
Best regards.
I am using Somfy IO shutters and awnings around the house and have been controlling them with openhab for 3 years now.
I own a conexxoon for the cloud connection. I own a RFXcom aswell but opted for IO because or the secure(r) coms and the ability to send and read percentages to my shutters and awnings.
Yes, it’s a cloud connection which is not my preference when it comes to integration of products into my home. It is however a alternative to open your shutters if all else fails.
The somfy IO binding goes down once or twice a year because of some sort of rate limiting on the somfy side. I made a small rule that detects the bridge being logged out, dis and enables it in an hour so in the event it does go down the system recovers on its own.
Basicly in my opinion the ONLY downside is the cloud connection. Controlling the units does work beautifully though!
Somfy io can be discovered by the KLF200. My house started out with two Velux windows, of which the flat roof window was electric for opening and a curtain. Since then added solarpowered sunshade to the flat roof window and electrified the slanted roof window with opening motor, sunshade and curtain, all io protocol.
Two years ago I had a Somfy awning and screen installed. These were discovered by my Velux tablet remotes and I could also discover them with the KLF200. I am controlling all items with openhab (started at version 2.5 but am now on version 3) with rules based on sun position and inclination, amount of light, wind, etc.
I have never encountered the reported ghost state of the KLF200. Works perfectly in my case.
The IO awning gets picked up by the Somfy / Tahoma bridge and works 100%. The 12 RTS blinds I’ve managed to accurately automate their position effectively through rules and now control them primarily through Alexa voice control.
It’s still uses the Somfy / Tahoma bridge to execute the movements; like others I’ve had very few issues with using that API.
I created a proxy item to hold the time taken for a full blind movement, another proxy item for the required position which also has semantic attributes so that it shows in the main UI and is controllable via the OH / Alexa skill, and two further proxy items for the total blind cycles/operations to give an estimated battery level and low battery alarm; and finally the dimmer item to receive commands for UP / DOWN and STOP
It’s tuned to respond to movements to the nearest 10% and the program will use the opportunity when the blind is moving from a ‘Nearly Closed’ or ‘Nearly Open’ position to re-sync it’s actually position so in rooms with multiple blinds they don’t get out of step.
The blind cycles / battery calculation works great; and Alexa lets me know when a group of blinds is likely to require recharging. Obviously it is all based on the blind calibration proxy time being correct, but if you get that right you would think the motor was an IO rather than RTS!
I’m more than happy to send copies of a the code - it would give you a good starting point.
Whilst I’m very happy with my solution, I do like none cloud options, so reading Larsen’s comments above makes me think I’ll investigate that in the future too.
Hi,
sorry for posting in this “old” thread but I think here are the right people
I read something about a limit of 5 units per KLF200… Does anybody control more than 5 units ?
Is there a second (third) KLF 200 needed if I increase the number of IO shutters afterwards?
Thanks a lot for sharing your experience.
/Mav
The limit of 5 units is for “physical” control, meaning you can attach five physical switches to control items. The KLF200 can control a lot of units. I have 8 units: two Velux sunscreens, two Velux windows, two Velux “curtains” and two Somfy screen/sunshades.
The maximum amount of units will be some binary number like 128 or 256.
Read this thread much earlier and now I take the time to setup the klf200 obtained recently.
My issue appeared even before integrating it to openhab. I hope that experts here would like to help to resolve my “off-topic” set-up problem.
Anything works following the velux instruction B Wifi) and A up to the registration using a somfy situo. In point 5 the LED remains flashing, which indicates, that the configuration of the klf is not finalised. Even worse: The situo is out of function and I cannot move the rollershutter anymore
Thanks for any relevant clue in advance
What do you mean by this? Has it been erased? Is it dead (no lights at all anymore)?
Point 5 where? Did you know that with manual B you can get in the (local) “web” portal of the KLF200? In there you have several menu’s. In one of them you can instruct to receive items from a i/o remote control device, so without the need of using a “paperclip” to reset the device to receive or having to use short-circuiting one of the connector wires? That last method (paperclip and short-circuit) is if you want to connect a physical switch to the KLF200 to command your device.
So get into your device via the local portal (as instructed in manual B) and check the various menu’s in there if any device has been paired. It will show if it has. In that case things will be easy and you can just control via openhab (and probably even copy back the rollershutter to a situo or other remote).
If not, and your situo has just been “erased” you can repair your situo, but you’ll have to power cycle your Somy rollershutter. For 5 to 10 minutes after regaining power, your rollershutter will be in pairing mode and you can repair your rollershutter with a remote. Possibly, due to the lost pairing, you’ll have to physically press a reset button somewehere on your rollershutter to create a new pairing key. But one step at a time, possibly the fix is relatively “easy”.
I mean, that the situo is not paired with the rollershutter anymore.
I in fact followed the instruction of veluxs’ local portal and made the device receive the rollershutter from the the situo. It was visible then in the portal, but I did not realise, that this stage is sufficient to integrate to openhab.
Thus I went on with manual A which obviously messed up everything: No item listed in the portal anymore and the situo not paired anymore with the shutter.
Reading your last paragraph it appears to me, that re-pairing the"erased" situo must be the next step, right? It will be needed to pair the shutter with the klf. I do not dare to test with other items unless the 1st 1 is not successfully integrated to openhab.
Again, don’t know if you can repair with the device after a lost pairing, in which case you probably need a factory reset of your Rollershutter. But first try repairing your rollershutter with your situo and/or klf200 the normal way (power cycle the roller shutter and try pairing). If unsuccesful, you need to check how to reset your device to generate a new pairing key. I believe that is in the main Velux topic here in the forum somewhere as well.
