Overkiz API and Somfy API

Feature Requests
266

Hi tetienne, I have been trying and re-trying for days, I delete and create your component, I delete and create the app from somfy api but when I ask for authorization OAuth 2 the error always comes out: "An error has occurred
Please try again. If the problem persists, please contact our technical support team. "I have already contacted the technical support twice but I have not received a reply.

267

That’s really annoying. Sadly I can’t do anything on my side, I don’t work for them. I’ve sent a new email to their support. Usually, they answer me.

268

Hi, always answers, if I write from the site “thank you, we will deal with it”, the next answer will not come. I’ve been dealing with it for almost two weeks. Perhaps one man does somfy support. :frowning:

269

I have also written in support of my country, which has backed support in France and the answer was “We have your problem when you changed your consumer_key. We will keep looking and try to come back to you soon.” I’m not sure what he means. Did I spoil it when I changed consumer_key? Or should I create a new app? Or wait?

270

They answered me too. So indeed all these errors 500 are linked to an issue on their side. Apparently, they have a synchronisation issue with some applications created through their portal. Not everyone is impacted. It’s explain why we cannot see all the problem.

272

MyslĂ­te si, ĆŸe problĂ©m bude vyƙeĆĄen v blĂ­zkĂ© budoucnosti?

273

I’ve no idea. They didn’t give me any deadline.

274

Hi guys,
Great work here . I have been following this topic and set up my Somfy blinds last weekend. Everything was working fine until Wednesday. I did not had much time to troubleshoot it yet, but am I reading it correctly that there is some kind of problem with the Somfy API?

Thanks!

275

Thank you. The best to know where the issue come from is to look into the logs. But yes, Somfy has some trouble with their server.

276

Finally shift, but some mistake again. After clicking on the authorization it will write an error. :frowning:
{“error”:“redirect_uri_mismatch”,“error_description”:“The redirect URI provided does not match registered URI(s).”}

base_url: http://192.168.0.60:8123
Call back URL: http://192.168.0.60:8123/auth/somfy/callback
URL from HA: https://accounts.somfy.com/oauth/oauth/v2/auth?response_type=code&client_id=xxxxxxxxxxxxxxxxxx&redirect_uri=http%3A%2F%2F192.168.0.60%3A8123%2Fauth%2Fsomfy%2Fcallback&state=xxxxxxxx

277

Indeed, i wanted to have a closer look to my problem today, however it’s working again since the update:

Update image homeassistant/qemux86-64-homeassistant:0.92.2 to homeassistant/qemux86-64-homeassistant:0.93.1

Not sure whether it’s related or just a co-incident.

278

Stupid question, but what’s the difference between the somfy custom_components discussed here (with the installation procedure described by @koomik here) and the tahoma component documented here ?

I found this thread while looking how to use the tahoma components which does not work for me


279

That’s not a stupid question. The custom component we discuss here use the official Somfy API. Whereas the existing Tahoma component use an unofficial and undocumented one. Meaning it can break at any time, like it was the case for the Logitech Harmony.

1 Like
280

Another thing is that the tetienne component can do more. For example, tilt the blinds, the other can only do up, down and stop.

281

So another problem can be at https://accounts.somfy.com/oauth_client, which does not match this https://developer.somfy.com/user/me/apps. Unfortunately, in my case, I can’t change it. I’m waiting for Somfy to solve it.

1 Like
282

Hi

I just install and test your plugin and it’s works fine !

But the garage door does not appear in the list, unlike the Tahoma basic plugin provided by Home Assistant. Is this normal?

Thanks

283

Hi,
yes, unfortunately, as described here https://developer.somfy.com/products-services-informations , garage doors are not yet available. Hopefully, we think that Somfy will extend their API soon or later.
This i why we can use both this component and the Tahoma one (where you can add exclusion for equipment managed by the first)
Stay tuned ! :wink:

1 Like
284

Ok thanks :slight_smile:

Little question, what is the difference between this plugin that uses the official API and that proposed by Home Assistant?

Thanks :slight_smile:

285

Answer from the big boss just 5 messages above :wink:

1 Like
286

So I solved the detour. The application partially corrected me, but there was still a “https://accounts.somfy.com/oauth_client” problem with an old IP address that I couldn’t change. I put an old address in the application as well as in configuration.yalm and I started the authorization. As soon as it redirected me back to a broken address, I replaced it with a local one and now it works.
What is the IP address for when it can be bypassed?
I’ll wait for it to resolve and change the address.