Overkiz API and Somfy API

Feature Requests
507

I think the somfy stuff is beyond help :rofl: Terrible API service

1 Like
508

When you got the error, look at the url in your browsers, you will see the callback URL. Use this site to decode it. Then compare it to the one you set in Somfy.
If they are the same, try to recreate your application. If still does not work, waitā€¦ It was the same for me at some time.

509

I seem to have trouble answering here, tried a few times now.

Anyhow, the callback URL is fine, it points to my external url which is accessible from outside. I tried interal as well, but same issue. Iā€™ve tried to recreate the app more than once, but the outcome never changes, just gives the security error. Still no response from support. I have emailed somfy support locally, but i doubt that will make any difference.

510

Just for testing, I added the tahoma component instead of somfy, and that works! (even with connexon hub!)

As I was testing this, i got reply from the api developer site, seems they are well aware of the problem, but have no idea why it happens.

511

Support also just answer me. The next Tahoma update will have a fix to avoid the issue some of you meet. I hope thatā€™s a final fix!
The Tahoma component a totally other system to control your device. It mimic the calls made by the Tahoma/Conexoon website. So it uses an undocumented and unofficial API.
On my own HA instance, I use my component to manipulate the covers, and the Tahoma one to access my light sensor, and scenarii.

1 Like
512

Yeah, i would prefer the open API, but for now, this will have to do. I notice that its a bit confused as well to states (one awning says position: 0 when open, other 100 when open). But as long as I can automate them, itā€™s good. :smiley: I will only be using covers as thats all i plan to have from somfy.

513

As many of us, I am struggling to get the official Somfy Open API working as well. But what I do wonder, is that when going through the same authorisation process to connect my Connexoon to IFTTT instead of Home Assistant, I have no issues at all.

As I expect IFTTT uses the same Somfy Open API as is being used by Home Assistant (not the Tahoma component of course!), I wonder what the difference is and why IFTTT is able to connect. Any ideas anyone? Perhaps understanding how IFTTT does this could help us getting this resolved in Home Assistant.

514

I think the main difference is that the ifttt app as well as Google Assistant one is that they are public API and not dev ones.

I think the problem weā€™re facing is that somehow the API does not recognize us as the dev (if we read the FAQ it is explained).

515

Indeed, on IFTTT you use the same kind of authentication process. But I donā€™t think behind the same API is used. On IFTTT, and Alexa only scenarios can be used, devices are not exposed. With the Somfy Open API, we have the reverse situation.

I really hope we can trust their support and so have a real fix coming soon.

516

Letā€™s hope so :slight_smile:

Interesting ā€œfeatureā€. I got two motors, both sunilus IO. Strange, but they have reverse directions on the arrows in the UI, and position is also reversed between the two.

517

Anyone using the Tahoma integreation have issues with entity idā€™s being swapped around on restarts? Suddenly my balcony awning, was my window screen. :stuck_out_tongue:

518

You mean when you click open on HA, your sunilus is closing? You use the Tahoma component or mine?

519

I guess im really posting in the wrong place, its the tahoma integration. It seems to have several issues. It also likes to change the entity_ids on restart, so its hard to automate anything (suddent motor 1 is 2, and vice versa). And yes, one motor closes on ā€œopenā€ and the other opposite (in hass).

520

Hey guys (maybe more @tetienne),
I succesfully added the official Somfy integration to HomeAssistant. But it is not showing any devices.
On the developer site of Somfy it is showing the Connexoon:

  {
    "id": "xxxxxxxx-yyyyyyyy-zzzzzzzz-xxxxxxxx",
    "type": "hub_connexoon",
    "categories": [
      "hub"
    ],
    "states": [],
    "capabilities": [],
    "site_id": "xxxxxxxx-yyyyyyyy-zzzzzzzz-xxxxxxxx",
    "available": true,
    "version": "2019.3.4-7"
  }```

What don't I understand or am I missing?
521

Hi,

What kind of devices do you own? Only few are supported for the moment by their API (thermostat, roller shutter, camera).
If you donā€™t see any devices it can mean they have a bug on their side (I faced this case sometimes) or perhaps your country is not supported (but so why can you see your connexoon?)

522

I own 1 roller shutter (Somfy Sunea 50 io). I live in the Netherlands. The Connexoon and roller shutter are IOā€™s.
Is this supported in the Tahoma (unofficial) integration?

523

Did you do anything special when adding the Somfy integration? Your Somfy setup seems quite similar to mine (Connexoon + IO motors, in NL) but Iā€™m running into the error that seems to plague everyone here (except you apparently :slight_smile:)

524

T.B.H. it was a search for me as well!
base_url has something to do with it. I donā€™t use it anymore after a fresh install of HassOS. I use the default_config: in configuration.yaml and run https through integration: NGINX. Quite easy to set up.
The callback url on the developer site of Somfy is my LOCAL Hass ip with portnumber: 8123
Like this: http://192.168.1.123:8123/auth/somfy/callback
Try to activate the integration when you are within your network.
My mistake with testing on the developer site was not push on the ā€œOAuth 2.0 setā€¦ā€ button before pressing ā€œTry it outā€ā€¦
Whoopsā€¦

1 Like
525

Where would you find that on the developers site? In the My apps section I cannot find a button like thatā€¦

526

Under Apiā€™s and Docs: https://developer.somfy.com/somfy-open-api/apis
But it is only for test purposes and only useful after successfully adding the Somfy integration.