My Connexoon has MAC F8:81:1A:53:xx:xx. I bought it this year.
Regarding MAC addresses, mine starts with F8:81:1A:52:XX:XX
Out of interest the issues people are having with authorisation where you having that issue while using your Tahoma or is this problem only present when directly using the Somfy API?
My Conexoon box starts with F8:81:1A:53
Hey,
I tried to set up also the slider underneath each cover, but I got the error message: Custom element doesn't exist: slider-entity-row. What did I miss?
My connexxoon mac starts with:
F8:81:1A:54
The error is probably related to the custom component:
The slider-entity-row isn’t a standard Lovelace component, so you’ll need to add as module as described in the repository. Did you do that? If you did so it is probably a little bit harder to debug and a bit out of scope for this topic, but a guess you can start your own topic on the forum to find out what is going wrong 
Thanks! No I didn’t know that. I tried but still get the same error message. But anyway I will change to hass.io shortly (I still use the “normal” homeassistant container) and give it another try then …
Is the Connexoon RTS working with this API?
I think it should… I’m trying to get it to work
Could it be that this integration is currently broken? If I tried to set it up (right key and secret) and when I try to add the integration. I get:
{"error":"redirect_uri_mismatch","error_description":"The redirect URI provided does not match registered URI(s)."}
If I look at (redirect) the uri that’s in the browser it says something like:
&redirect_uri=https://my-sites-url-thats-ok/auth/external/callback&state=some_hash
See that “external” instead of “somfy” there? I did not put it in there So either the documentation is not right, or I am missing something…
n.b.
If I change the redirect URL in somfy config to bla “external” instead of bla “somfy” I still get the same error.
Hi, the callback has indeed changed, probably with the latest release. Purpose is to use the same callback url for all the components using oauth2 protocol like here Somfy.
There was a PR to update the documentation: https://github.com/home-assistant/home-assistant.io/pull/10840
But this last has not been merged. I’ve added a comment.
About your issue, it’s maybe due to a sync issue or delay on the Somfy servers. Wait until tomorrow to be sure.
1 Like
You can check on the Somfy developers website if your devices are returned by the API.
After deleting app in dev-somfy and adding again with right call-back url and some yin and much needed yang it all worked after 20+ tries… :-/
Somfy replied to me, regarding devices not being listed.
Hello,
Awnings and Lights are not supported by the API. This is why you cannot see them in the response payload.
Best regards
I have sent 2 e-mails since then regarding the fact that Connexoon is being listed as supported but no reply yet.
Hello Tetienne,
My TaHoma box‘ MAC address starts with f8:81:1A:51. It is a TaHoma Premium V2.
Hi all,
i’ve setup the integration, first I had generic error, but after some time of wait, as someone suggested, maybe Somfy’s servers syncronyzed and then I was able to do a little bit step forward, now i’m stuck at
- ```{“error”:“redirect_uri_mismatch”,“error_description”:“The redirect URI provided does not match registered URI(s).”}`
my callback url is: https://192.168.0.251:8123/auth/somfy/callback
Can anyone help me?
Try https://192.168.0.251:8123/auth/external/callback instead, the callback url has changed. Documentation will be updated soon. You will have perhaps to wait also (for the sync reason)
I’ve currently the same error.
@tetienne I’ve try also to change for external instead of Somfy. Do we need to wait some times ?
Is it possible to use the external URL to access to HA : https://xxxx.mydomain.com/auth/external/callback or I need to use IP address ?
Thanks.
I think you have to wait yes. You have to use your external URL if you have setup one. But to be sure, you can look at the callback url in the adress bar when you see the Somfy login portal.