Thank you for your words 
So once the official app will be released, you will have to delete the files related to the custom component and restart HA. That’s all. You have to keep the configuration.
Hi!
I’m trying the pre release version 0.95.0b3 with your Somfy component that looks so good. Unfortunately I can’t pass the authorization process… I added an app at developer.somfy.com with as callback url:
https://xxxxx.ddns.net:8123/auth/somfy/callback, and I have the following in my configuration.yaml:
http:
base_url: https://xxxxx.ddns.net:8123
somfy:
client_id: "xxxxxxxxxx"
client_secret: "xxxxxxxxxx"
The id and secret have been checked multiple times. But trying to activate the somfy integration leads to an error when attempting to authorize it. The URI of the error shows that somfy is using my private local ip as redirect uri… redirect_uri=http%3A%2F%2F192.168.0.11%3A8123%2Fauth%2Fsomfy%2Fcallback
My server is hidden behind a router that redirects port 8123 to it, and I use no-ip ddns to access the assistant from outside the network.
Any idea what I’m doing wrong?
thanks a lot!
Hi, welcome on board For your issue, I suggest you to update the callback URL you provided to somfy in your application to 192.168.0.11:8123/auth/somfy/callback. Even if your local network is not accessible from the outside, it does not care. This call will be done once by your browser. So you have to be on the same network of course. It should solve your issue.
wow, thanks for the quick reply! you’re amazing! First thing first, I had a space before my http which explains why it was not take into account. Now in the error URI I do find the redirect_uri=https%3A%2F% xxxxx.ddns.net%3A8123%2Fauth%2Fsomfy%2Fcallback. But it’s not working any better… I tried with both http and https, and also as you suggested with the local ip address from inside my local network, again with http and https. But it was unsuccessful…
Can you explain the error you got? Did you receive also the error message from Somfy: «An error has occured.»?
Nothing shows up in hass’s log. I get the following message in the popup:
And in the Home Assistant, I’m stuck with the " This step requires you to visit an external website to be completed. OPEN WEBSITE" message.
So you are stuck like other :S Here there is nothing I can do about this. I suggest you to contact the Somfy Support from the dev website and to give the maximum of information you have (url, datetime, ip, country…). It’s really sad to see such issue on their side.
Damn… It sure is. Thanks anyway for the support! appreciated it.
I dropped an email to Somfy’s support. I guess it won’t do much, but one never knows…
Cheers
I have the same issue of vlebourl.
My Home Assistant instance is on my domain (https://www.mydomain.com) in a Python venv running on my debian server.
In “My App” configuration on developer site of Somfy i have specified my url “https://www.mydomain.com//auth/somfy/callback” but it didn’t work.
I’ve tried all (local ip, remove https and use http, use the same network, use a browser from the same HA machine).
If you have news about this issue, please, update this post. Meanwhile fortunately we can use old integration method for Tahoma
Still the same issue. HA ver. 0.95 and I make a new application at somfy webpage.
That’s really sad that for the official release of my component the Somfy server go crazy.
I have the same problem that all of you. I’ve contacted again the support, hope they can do something quickly. Normalize, they answer me quickly.
1 Like
I got a response 2 days ago from SOMFY API - Support: “We’ll take a look.” Nothing since then… I hope they solve this quickly. Maybe if we regularly send emails to ask wether they found and solve the problem, they will finally see it as an important one?
Polish branch of the Somfy has only ONE (sic!) person who is responsible and has a knowledge, but he is on vacations now. No help at all.
I think the same. As you said perhaps they have to see we are a lot to use their API.
Meanwhile, I don’t know if it’s in their priority.
I also send them a message from dev site.
Interesting thing is that their api doesn’t work at the moment from Google Home. It could be the same bug. Wait and see
Same here.
@koomik Perhaps Google home use the Somfy API 
On my side, I was finally able to login. I haven’t touch the configuration on the dev website. After that, everything works as expected.
But I’m still expecting an answer from their support.
First of all, thank you for all the work put in to this component!
Unfortunatly im running into the same problems. At first i did get the ‘do you wish to authenticate’ screen with a Yes/No option. After that i would get an error of an invalid redirect URL. To make sure the Somfy app wasnt the problem i deleted it and created a new one. Now when trying to authenticate i immediatly get an error on the website. (accounts.somfy.com).
I just contacted Somfy by phone, and their answer was that they are moving things in the head office and that i should keep an eye on it for the next few days…
If any of you have any ideas to solve my problems that would be greatly appreciated.
Do you know what they mean by Head Office? It’s interesting.
About your error, it can be due also to a bad configuration, double check your redirect URL. Compare the one you see URL encoded in your address bar and the one you have in the application. It can be a typo, https instead of http, etc.
You have the documentation here.
My URL is correct (https://mydomain.com//auth/somfy/callback). I have tested it also from url string with a urlencrypt/decript function in PHP.
If i go to this url from a browser i have this response:
500 Internal Server Error
Server got itself in trouble
is this response correct for a direct access from browser?