Another argument to Somfy: I want to set the covers depending on their current position (e. g. set the shutter to a position between 10% and 50%. If the shutter is at 40% then leave it there, is it at 60% then move it to 50%, is it at 0% then move it to 10%). In other words, I need to poll the current cover position, before I can make a decision what to do. The Somfy App does not allow that.
If Somfy wants to pursue that road I am fine with it. After more than a year of dealing with their terrible support and actively trying to hinder the usefulness of their product I am done with them.
If it wasn’t so expensive I would throw out all Somfy stuff and replace it with cheap chinese motors and Shelly 2.5 to integrate them with HA. However that is bit expensive, so as soon as they decide to cripple the api experience I will move over to a KLF 200. On the short term they get what they want, less API usage, but on the long term the KLF 200 will remain a reminder, to never ever Somfy products again as their support of the product is terrible and they do not regard their end users. I hope a lot of people will do the same.
@tetienne thanks for trying to keep in contact with them, even if Somfy is unreasonable in its demands.
2 Likes
I would instantly change to the KLF 200 but this is only supporting 5 products or 5 product groups (whatever this means). So in my case I would need to buy 5 of those to be able to control all of my covers individually in my house. Even not knowing if this is then supported by HA …
So I really hope that Somfy will change their mind and support other implementations than the thamolink UI.
Hello,
Well that’s bad news I can read on this post, I hope SOMFY will change their mind.
This also concerns TAHOMA custom composent, I suppose?
It especially concerns the TaHoma component, more than the Somfy one. The Somfy one uses the official open API which was incorrectly targeted by Somfy’s email. Their real target are users of the unofficial API mimicking the tahomalink webapp, which is exactly what the TaHoma custom component does. Hopefully we’ll find some common ground to continue using it.
1 Like
After I have received Somfy’s mail last week, I ordered the Velux KLF 200 the very same day. It arrived today and I can confirm that I can control all 12 covers with it. The limitation of 5 covers is a hardware limit (there are only 5 connectors at the box). But since the Somfy io covers are controlled wirelessly, the Velux box can handle them.
I captured network traffic with wireshark to see how much packets is actually communicated. I have used this filter:
(ip.addr >= 34.241.162.0 && ip.addr <= 34.241.162.255) || ip.addr == 52.18.178.5 || ip.addr == 54.72.117.59 || ip.addr == 34.252.103.201
In summary, there is a regular communication every 30sec.
Somfy assumes that polling to their API shall only happen when there positive number of open ws connections from UI to HA. Is that is doable without loosing user experience. Any ideas where it hurts? Maybe in some automations?
Anyway, I am completely fed up with somfy, their API service and support. Hence I am glad that I learned about KLF-200 today and would be grateful if you guys can share some more experience on your migration journey.
You can change the polling interval in Home Assistant → Integrations → Somfy TaHoma → options, the default is 30 seconds.
The Somfy TaHoma integration periodically retrieves new events. Change the update interval to a lower value if you want more frequent updates, for example when you also control your devices outside Home Assistant.
If you control your devices outside Home Assistant (with the remote, tahomalink.com or other ways) a low polling interval is required. If Home Assistant doesn’t know the state (and thus position of your cover, or state of your sensor) it is hard to create automations and take actions based on intelligence.
In my situation, I have a lot of times that the device is ‘unavailable’ in tahomalink.com due to the limited range. It is important that this shows up, because otherwise it won’t know that it couldn’t execute an action…
Hopefully we are able to get an exception from Somfy to use their unofficial API for the time being. We have conversations with one of their developers, thus I hope we can update all of you soon.
That I didn’t know. Thank you for informing 
Ok, that’s good to know, but as @vlebourl wrote the Somfy component - which I am using - is not affacted. So I will wait and see how the things go on and how good the integration works for me.
I dont need to know the blinds position (they are RTS anyway) and only use HA and the Somfy integration to close and open them when the house alarm sets. So I could change the poll time to 1 hour? .
I have looked at the integration and I dont have any options like that within the system options tab, just the “enable newly added entities” Am I looking in the wrong place?
The email was about Tahoma integration only. Users using the Somfy API aren’t concerned.
1 Like
I had the email too?
Few posts above
1 Like
I dumped the TaHoma integration from my home assistant installation more than half a year ago. And I still got the mail. Does Somfy even know what they are doing?
Sorry for the negative attitude. I think @tetienne did and still does a marvelous job developing and maintaining the Somfy component. But the company doesn’t really support the open source community and treats you more like a step kid. That makes your efforts even more valuable and honorable.
You rock! 
I see there was a code update to change the scan_interval.
Given the ongoing issue with Somfy and polling, would it make sense to add the scan_interval as a config option?
In my system, I have no need to poll Somfy (afaik), as I get no state info back on my RTS covers.
Thus all I need is to send open/close events via automation.
So for me an scan_interval in days would be fine (unless I missunderstood what the scan does).
If agreed, I’ll make a pull request to add the option.
Hi, as said above, the email was sent by mistake to the users using the official api. There is no need to change the polling interval
Hello to everybody, I have io motors (7 pieces) and I still didnt buy controller for them. Somebody told that we are need to wait for the 31st of October, then guys from Somfy will definately come up with some “solution”/ information?
My concern is whether to buy Somfy Conexoon IO hub or Tahoma hub (I really need only for roller shutters, nothing more). Or to wait and see and maaybe to consider KLF200?
What do you guys think, should I wait or just buy conexoon IO just to try?
Thanks
I use a Conexoon and the offiicial Somfy API (Somfy integration in HA) and it works. But from time to time there are some timeouts and my covers won’t response.
If I got it right the advantage of the KLF is that it has a local running API which makes you independent from the Internet. The Conexoon box needs the internet to work. So I would suggest to go with the KLF.
Thanks @azrael783 .
Just a question - if the KLF200 is a wireless option? I dont need to manually do a wiring to each of my roller shutters? KLF200 can detect swimming signal for io communication protocol?
Thanks