That’s for the old method, you will see in your app that a new token is generated by the Overkiz app.
We are migrating to the new way in the upcoming Home Assistant update.
Hi @imick,
Yes indeed, the Overkiz integration setup triggered a token creation that is visible in my app.
In what aspects will the new method be different? I’m curious.
PS: AWESOME work on the integration! It’s working very well so far.
The new method will only ask for a valid API token from your Somfy app. No need to provide any credentials.
Ah great! One last question: I just noticed that with Overkiz local API, the blinds are inverted (ie: position 0-100 is 100-0, up is down and down is up). Anything I can do, except for setting up a template cover on top of that?
Best to create a new issue for this. Good to test if a service call (cover open, cover close) does work, often people are confused with how awnings work in HA.
Thanks @imick . No no the service calls are working, I just had to define a “wrapper” template cover to invert the controls and position.
FYI the case looks quite similar to that one: Open/close status of (vertical?) `HorizontalAwningIOComponent` is inverted · Issue #123810 · home-assistant/core · GitHub
The root of the issue might well be the TaHoma exposing a “PositionableHorizontalAwning” => io:HorizontalAwningIOComponent through Overkiz.
Again not serious as I inverted the controls 
I meant, are the service calls also reverted. I am working on a major rewrite of the cover implementation ( Migrate cover platform to entity descriptions in Overkiz by iMicknl · Pull Request #141330 · home-assistant/core), which will make it easier to make exceptions for certain models.
Would be good to further debug your issue, and see if we can fix it in the upcoming rewrite.
Ah, sorry I misunderstood.
So I just tried it: the “Cover: Open” and “Cover: Close” actions are inverted: they close and open the shade respectively.
If I may help further, feel free to ask. Thanks!
Hi @MatrixRewriter,
I’m relatively new to the Somfy/TaHoma world. I have a TaHoma Switch, and I also enabled developer mode via the app, just like you did. I am facing the same issue with the local API setup. Which web portal did you use to enable or manage the developer mode settings?
I am able to log in to https://accounts.somfy.com/, where I can see that I have the TaHoma application listed. However, once I click on it, I am redirected to https://classic.tahomalink.com/, and I am unable to log in there, no matter what I try. I have tried several password resets, etc., but nothing has worked.
@xsida the first beta release containing the fix will be available tomorrow and the release will be May 7nd. From tomorrow you could try the beta :-).
1 Like
Hi @xsida ,
Indeed enabling Developer mode from the app did not have any effects for me. I also had to enable it on “Somfy Dashboard”). It worked immediately after I did that. Maybe the setting would have synced after a while, I don’t know.
Anyway, Somfy Dashboard is accessible from there. Example for Switzerland/French:
∘ https://www.somfy.ch/fr-ch/se-connecter
‣ Voir mon TaHoma
• Activer le mode développeur
Let us know how it goes…
Hello,
I have successfully integrated a Somfy slatted roof with the overkiz integration. I can open and close the roof without any problems, but when I close it, it stays in the status (closing) for longer and then jumps to the status open, although it is closed. Does anyone else have the problem or a solution?
Best regards
Stefan