Hello guys!
I was just wanted to check, I have IO roller shutters motors, so Im thinking to buy Somfy Tahoma.
Is it working? what if I loose the internet connection, if the API will still work locally? thanks!
Also, I found this thread…Tahoma Integration Refactored
Looks promising 
Hi, the Tahoma API is not local. So if you lose your internet connection HA won’t be able to control your cover. Look instead for the Velux KLF 200. It can control locally the IO devices and their is an HA connection.
Thanks for the info.
And can use Somfy Connexoon? I only need control for roller shutters and curtains.
You think that Velux KLF200 can integrate with SOmfy IO roller shutters?
So I have for now 3 options:
Somfy is currently showing bad signs regarding the open source community. They gave a deadline to october 31st. I would wait a bit before buying into Somfy if your goal is to include it in your HA installation. Follow this thread and that one to be up to date with that issue.
I got an answer from the Somfy support:
I am preparing a more complete answer with the team to clarify as soon as possible.
So wait and see.
any idea why since few days i got an error on stop command ?
echec d'appel du service "cover/stop_cover". 'dict_items' object is not reversible
latest version on tahoma integration(hacs) and HA (0.116)
This is a bug indeed, could you create an issue on GitHub? Otherwise I will do that later today.
Hi all,
So I got an answer from the Somfy support. And the update is not really nice… To sum up the content of the email:
They expect from the 3rd party plugins to behave as the tahomalink UI. Meaning that we should use the API when the end-user truly needs it. The device states can be updated when the user is manually connected to the dashboards.
in our opinion (@iMicknl, @vlebourl and myself), the solution to limit the use to UI interactions just means the end of this integration in Home Assistant.
Hopefully, there is one positive sentence in this email:
If you don’t agree, please let me know what we could miss.
Well that’s not really good news…
But to be fair I rather have a limited working connection so that I can control and automate my covers through home assistant than when having this interface removed completely.
With the information we have so far, complying to their request would mean sensors would be rendered useless as their state would only be retrieved when opening a Lovelace ui. Other devices could still be used though but only through human interaction via the UI as well. We really don’t want to fall that low, so we’re trying to negotiate a better solution. But there’s no guarantee…
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.
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.
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
