I have the same issue with Somfy API… I have a connexoon also, and i’m unsure if you actually could add it to tahoma? I haven’t managed to add it to that system. I have been in contact with somfy support about adding my connexoon to the tahoma servers, and got the response it was not possible to add my device to tahoma, and if I was about to use any API i would have to use the Somfy API. I tried to use the API using postman late spring and manged it to work. But since this integration was released their API have always returned a 404 in the authentication process…
Honestly, I do also the same when somfy server is down. The good point is that my automation still work as the entity id generated by my component and the tahoma are the same.
I will also try to contact them again. According to the number of people here, and the number of view for sure their API interest people.
I tried to login on TahomaLink and it doesn’t seem to work. Not sure that I can access this service with my current and Connexoon. Extremely frustrating 
For now, I will stick to IFTTT and basics scenarios but it’s such a pity.
Connexoon component worked for ~ 2 weeks… not the entity is not available after a reboot. So i’m in the same boat again. 
@msmits2011 Do not change your configuration, it’s a problem with Somfy API. I noticed that it might take some reboots, but they will reappear if the API is up and working.
1 Like
I do not know if my problem, or Somfys, but when trying to set up the component and after authorising the app y get this message. BTW I own a conexoon
{“error”:“redirect_uri_mismatch”,“error_description”:“The redirect URI provided does not match registered URI(s).”}
Yes thanks for the tip! Normally it come back after a couple of reboots, but not in this case unfortunately.
It’s back now, but keep getting update errors.
Same here…
Question for the Tahoma people who are using the Tahoma component instead of the API, can you set your shutters to certain position or is it just open/close?
Depends on the shutters for me. I have an RTS switch connected to a bubbendorf micro module. No return state so no positional setting. I 1lso have velux shutters, with which positional setting works
I have IO shutters and I can set the position with the Tahoma component.
For those who are interested, I’m extending the tahoma component for my own usage. I stick with a custom component because it’s a bit messy and I don’t have the time nor the energy to apply all of HA’s rules for committing changes. Feel free to have a look and use it if you want: https://github.com/vlebourl/home-assistant-config.
Any help with this would also be appreciated.
So I can better move to the tahoma compontent and remove this somfy component?
Oh you added the Atlantic, that’s nice! That’s something I missed.
So your point is to add new supported device to the Tahoma component? I agree it took a lot of energy to submit a new component, but when you enhance an existing one (like your velux fix) it’s really quick.
While Somfy does not have a stable API server yes. On my side, I will keep using this official API component to follow the evolution, and see if things get better.
indeed, i committed the velux fix to HA!
The Atlantic io component integration is quite crude though… any enhancement idea is welcomed. I’m sorry it kinda sounds like i’m trying to take people away from your component… It’s not the case, it’s just that somfy’s support is so lame, I got tired of waiting for their API to work.
Don’t worry, I totally get it. Somfy component is for me a toy project and help me to learn Python. That’s more interesting than another Hello World!
If Somfy don’t play the game, that’s normal we find other way to control our devices.
By the way, on the Somfy French forum, some question about API pop: https://forum.somfy.fr/questions/2040037-probleme-connexoon-api
Added my comment to try to finally get an answer.
The “funny” thing to notice is that the native integration with Google Assistant seems to be broken too, it worked fine the day I set it up but it is not working anymore… Their system does not seem reliable at all…
1 Like
Highly annoying.