Folks, the API just started to work for me again (after HA restart). Hope it’s fixed permanently 
1 Like
After restart of HA the integration is working for me and the covers are responding much more faster than before.
Somfy service seem to be working again. I removed the integration and added it again to get it to work.
Indeed! Every night I have a scenario closing all my covers. Usually, I saw them closing one by one. Right now, they closed simultaneously.
Hi Tetienne! First of all thank you for your great work!
Could you please enable support for the izymo microdevice? The error I am getting is the following:
‘’’ WARNING (SyncWorker_5) [homeassistant.components.tahoma] Unsupported type io:MicroModuleRollerShutterSomfyIOComponent for Tahoma device Guest Blackout’’’
I have 32 rollers with this controller, so if you could do it I would be obliged! Happy to help if I can (with testing etc)
Many thanks! 
Can anyone confirm that new registrations cant be made? Tried it with the nodered node and in home assistant, both are returning an error on the somfy site.
I have a Somfy gate I can only open using a scene created on my Tahoma platform through the Tahoma integration. I’d like to use the status change of the gate as a trigger to turn on lights - but since the gate is not available on the Somfy API (which would have been accessible through the Somfy integration just like shutters etc) I need to use the Tahoma integration which only gives access to the scene “open gate” rather than the gate as an entity itself. Has anyone encountered this or does anyone know a solution?
Did you try with your own app on the Somfy developper website? If yes, you have to wait some delay. They have a synchronization to perform between their servers. 2 hours before your message, it was ok for me.
It seems an improvement is required on the Tahoma integration. Is your gate RTS or IO?
Hi, I’m working on improving the Tahoma integration, along with other people. Can you please post on this thread with your issue: https://community.home-assistant.io/t/additional-supported-device-types-tahoma-plafform?
1 Like
Hi Tetienne, I re-created my app on the site. Tried it yesterday and today and same message. After the login prompt on the developer site normally the authorize message appears but instead an error is shown. It does not matter if I use the node-red node or the home assistant integration “wizard”. The error is in dutch:
Er is een fout opgetreden.
Probeer het opnieuw. Als het probleem zich blijft voordoen, neem dan contact op met onze dienst technische ondersteuning.
Hi ceriel, I have exactly the same issue (except for the language of error message). I double checked several times client id and client secret. In my configuration file I have the following lines:
somfy:
client_id: XXX
client_secret: XXX
@ceriel @lindi I highly recommend you to use built-in application already configured for HA. Just remove the somfy node within your configuration.yaml. Their is no privacy issue with this.
1 Like
My gate is an IO gate (with Control box 3S)
@Marijn which Connexion do you have IO or RTS? I have Glydea curtains and Velux window. I know TaHoma can do them both but to expensive. Can you perhaps help in what direction I should go?
Hi all, I have the Glydea curtains, RTS protocol and also the Velux window IO protocol.
I don’t want to invest money in the TaHoma since HASS should do it all. Can someone explain me, help me what I should get to get both protocols working? I do see the Zwave protocol is supported too, so it should also connect to that protocol?
Again perhaps silly, but confuse what to choose?
Hi all,
We are working on refactoring the Tahoma Integration to make it better while Somfy work on their official api. Feel free to have a look here:
Cheers
2 Likes
That’s a nice initiative. I will have a look and see if I can help.
2 Likes
Hi Tetienne, how do you mean?
I am not using the custom component and followed the implementation on the HA docs website.
As said in the documentation, you don’t need to create your app. Just remove the Somfy entry from your configuration.yaml and try again.