Liebe Somfy-Kunden, leider besteht aktuell ein Problem mit unserem Smart-Home-Server für die TaHoma- und Connexoon-Boxen. Eine manuelle Steuerung Ihrer eingebundenen Anwendungen ist daher gerade nicht möglich. Alle bereits aktivierten Zeit-Programmierungen und Wenn-Dann-Bedingungen laufen weiterhin ohne Einschränkungen. Unser Entwicklerteam arbeitet mit Hochdruck daran, dies so schnell wie möglich zu lösen. Bitte entschuldigen Sie vielmals die Unannehmlichkeiten.
which translates to:
Dear Somfy customers,
Unfortunately there is currently a problem with our smart home server for the TaHoma and Connexoon boxes. Manual control of your integrated applications is therefore not possible. All already programmed time programming and if-then conditions continue to run without restrictions. Our development team is working flat out to solve this as quickly as possible. We apologize for the inconvenience.
So once again they haven’t got their hardware under control.
They pinned a message at the top of their French forum too:
Chère Cliente, Cher Client,
Nous rencontrons actuellement un ralentissement de serveur TaHoma/Connexoon empêchant le pilotage de vos équipements à travers vos applications.
Nos services de développement qualité mettent tout en œuvre pour solutionner ce problème le plus rapidement possible.
Nous vous prions d'accepter nos excuses pour la gêne occasionnée.
L’équipe des Yellow’s SOMFY
I want to give a heads up to Tetienne! Although the Somfy API product is in a miserable state he keeps trying to make the best out of it and is giving support on problems that are most of the time out of his control. And we are very happy when the api is up and the integration is working great, because of his time and effort.
So thank you!
I moved from Tahoma box to Velux KLF200 in order to get rid of somfy servers. I could transfer all my devices (9 shutters and 4 exterior venetian blinds) quickly and control them (open and close). The KLF200 provides a local API ant the API specification allows to control nearly everthing the io-homecontrol protocol supports. However the current implementation via pyvlx packages provides not all functions.
One lovely feature I’m missing is the control of the tilt of the blinds. So I would much appreciate if someone could support to modify the velux integration in that way that it would be able to control also functional parameters of io-homecontrol devices and not only the main parameter (which is the position in most devices). Also it would be great if the complete velux integration would be part of home-assistant and not just a bridge to pyvlx package.
Well, in order to explain exactly I would need to repeat, but mostly the following Video explains it very good, just instead of sharing devices from a remote, I shared my key from Tahoma settings and started the product search. All configured devices on Tahoma was found on KLF200, just the naming was not shared, so I had to identify each shutter and blind and give them a proper naming. https://youtu.be/47dUdAHTCBA
I’m also pretty sure both Tahoma and Velux boxes can be used in parallel. I have not tried it yet, due to lack of Ethernet ports on my switch. Once I configured KLF 200 via WiFi (KLF200 creates its own wifi access point for configuration only, WiFi cannot be used for API access) I exchanged Tahoma by KLF200 in order to link with hassio. Once configured VELUX Integration I had all my shutters and blinds in hassio with the naming I defined on KLF200. By the way, the shutters react much faster than via Tahoma.
I connected now my Tahoma also in order to test it and was able to control my devices via both, Tahoma and Velux. However I had all my covers doubled in Home Assistant. But the change on one cover has caused a change on the other. I also created a custom component based on pyvlx in order to control the tilt settings via KLF200. So now I have all the functions from Tahoma also on my custom velux component.
Hey there, I have a problem authenticating for quite a long time (but having an rfxCom for the blinds I do not use the integration that much when the weather is cold, however my sun awning is used these times.
I have the following issue :
my redirect uri is correct https://<MA_HA_URL>/auth/external/callback, I can see it in the URL that is presented on the permission grant screen, but when I validate I get a “redirect uri mismatch” (this uri is the proper one on somfy developer’s side)
I’ve recreated the app on somfy developer side but it bails out with an error even before showing me the permission grant screen.
Hi! About the redirection issue, it happened to me also some times. As you said, if the URL you set and the url you see are the same, the issue come from the Somfy server sadly. For your 2nd issue, apparently, you have to wait for the sync between all the Somfy server afterwhile it will be ok.
I suggest you to switch to the cloud choice with this integration. There is no privacy concern, and it will work out of the box.
It’s really nice to have both solution working at the same time. Once a KLF200 found at a good price, I will still be able to maintain my component! Thx for this information.
How can we get Somfy working for us? The Tahoma integration is EOS/EOL and this API should be the way but still doesn’t support all Somfy devices. How can we get the development in action so that all possible Somfy devices can be controlled by the official API. I really hate those half solutions when I still need to use to old Somfy app to control my awning as example.
Is it in any way possible to utilize the “My Position” command using the official Somfy API?
It works with the Tahoma integration, because the Tahoma cover.stop_cover command translates into a My position RTS in the somfy platform, when the blind is initially at standstil.
With the new Somfy API, the cover.stop_cover only translates into a stop/abort command, and therefore doesn’t trigger the My Positon RTS function.
I can of course keep both integrations, but the official API would probably be the right way to go.
Did you get this working with adding a 2nd account? I tried creating a second account attached to my Somfy Connexoon (Australia) and it wouldn’t allow me. “This PIN code is correct and CONNEXOON has alreayd bene activated.”
This project seems really great. But there is two bad points: it’s only for RTS devices, no IO, and it requires some knowledge in electronics. That’s not for everyone.
The title can be translated to “TaHoma and HomeKit compatibility: What’s taking so long?”
To sum up, they thought their products with the cloud in mind, but Homekit required a local connection to the device. So they have a lot of improvement to do to receive the Homekit certification. So perhaps thank to Apple, in few months, we will see the deployment of a local API.
I am a new Home Assistant user and am learning a lot from reading on this forum and using your knowledge to slowly migrate my systems (Somfy, Velux, Zigbee and Z-wave) to H.A.
I am a bit stuck with my Connexoon box. I have 3 Velux io motorised windows with 3 blinds mounted in them. My Connexoon is connected to these, and I can control all 6 devices via the “Connexoon WINDOW” App on my android phone.
I used the simply activation methode of the opening post and managed to include the Somfy integrations in H.A. but it only shows the 3 blinds, not the 3 Velux windows:
If I log in to my Somfy account, I see my Connexoon box is registered and linked to the WINDOWS App.
Question: how can I get my Velux windows into H.A.?
Thanks!
PS
With my Homey, I integrated the Somfy devices the same way as with H.A.: I had to save my credentials. After that, the 6 devices are available in Homey. So, it is possible
Hi, the Somfy official API returns only the Somfy devices. And even for this last one, it’s only a subset.
I suggest you to try the Tahoma component which use the unofficial API (the one used by the website).
Hi @C_Holm, thanks for asking. I’m also looking for this.
BTW thank you so much @tetienne for the job. I can finally get rid of IFTTT to connect TaHoma to Domoticz.
Cheers.
