Overkiz API and Somfy API

Hi Tetienne, probem with the URL was that I needed to use httpS://192.168.178.99:8123/… I managed to successfully complete the authorization process but when I look at the configured Somfy integration, I get:

This integration has no devices.

Even though I have several screens with Somfy I/O controller via a Connexoon. In the error log the only reference I can find of Somfy is:

2019-06-15 21:15:36 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for somfy which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.

That’s great you found a solution!

For your new issue, can you go on the Somfy developers website (the one where you create the application)? On this one, there is a section where you can play with the API. Use it to see if your devices are detected.

Are you referring to the test platforn? More specifically where you can get the site ID (via GET /site) and subsequently the devices (via GET /site/{siteid}/device). I did run the first one, but I do not seem to get site ID in the response. Anything specific I should do or should be looking for?

Yes I was talking about the test platform. Hum, you don’t get any site id? What’s your country? Apparently the API is not available world wide. For instance in Australia it does not work. You can contact their support from the website to directly ask them.

I live in The Netherlands, API is available here. What I do not understand is via which mechanism the screens should be visible. As I did not want to mess up what I already have (control screens via the Somfy Windows app), I have set up a new Somfy account for the using the official Somfy API but how can it be aware a connexoon box resides in my network? Or should I be using the Somfy account I have been using in the Somfy Window app instead? The latter one is linked to the Connexoon box.

You have to use your main Somfy account to create the application otherwise as you said you wont be able to see your device. You are close to make it work :wink:

ONLY i again or anyone else? :-
An error has occurred
Please try again. If the problem persists, please contact our technical support team.

Hi,
As above - Bojkas has the same problem.
I can’t Authenticate Somfy for the last few days. Receive an error after login.
Any ideas?
Regards

I wrote to Somfy, but apparently they don’t have a good work ethic and so far a month without a response. :frowning:

Apparently they are aware of this issue and have to work on a fix. @robertpe wait for the next HA release where my component will become official and create a new application on Somfy site.

It’s great that the app will be official, really hard work, congratulations! :slight_smile: I suppose already in 0.95, which could come out every day.
So in the new official version we will drop the application on somfy.com and will your application create a new one by itself? Or will we have to create a new one? You have no instructions to prepare. :wink:

Thank you for your words :slight_smile:
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 :slight_smile: 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