Overkiz integration - Local API [Development / Testers topic]

Is here an easy way to move an existing cloud API config/integration to the local API? Or do I have to remove it completely and create a new integration?

1 Like

Exactly the same question here! :raising_hand_man:

I just deleted the cloud one and re-added the local one. I didnt have to do much more, all the new entities took up their old name, so I didn’t need to modify any of my automations.

1 Like

Hope this is still on topic, but does this also work with the IO verrsion?
I’m looking to buy 4 rollershades and looking to control these via automations locally?

Yes this works all locally. I have RS100 io cover motors and they work perfectly local with the tahoma switch.

Hey guys,

I have the following problem with the local API to control my Tahoma Switch.

I used the cloud API for a while and wanted to switch to the (now a core feature) local API.
I got the PIN-Code, Tahome Switch is in Dev Mode, credentials are correct (tested on somfy webpage). But is neither working for the .local nor the IP (with SSL off) way?!
For each scenario a get a “Connection failed” message without any further information.

What am I missing? I really appreciate your work and help here!!!

1 Like

Update:

This is now resolved for unknown reason. Altough, I had issues with my garage door as well when using a Somfy KeyGo IO. Opening the door would change the state correctly to open(ing) but after it was open and I used my KeyGo again, the door is closing but the state kept for ~1 hour on open, which as of cource incorrect. I fixed this by using an Ikea Parasoll. When the state of the parasoll changed from open to closed, I’m calling my local Somfy API to close the door so it changes the state to closed.

I’m using The Overkiz integration for my garage door and Awning cover. I’m also using the Homekit bridge function so I see these devices in my Apple Home. For some reason, the Awning cover is seen as ‘open’ , but it’s closed. My garage door has the correct status , closed if it’s closed.

Does anyone know if this is a issue with the overkiz implementation, or the homekit bridge integration?

seeing that on a regular base with my garage door, (open while being closed) and only happening after it actually has been open.

closing it (even though closed in real life already) fixed the state in that case immediately

btw this is with the core integration, not any experimental.

The same issue here

Hi, how can I change the address of the used hub? I would like to change it from name to IP.

Did you get a fix for this? I have the exact same issue and it happens almost daily.

Hi, is it possible to switch from Cloud API to Local API ? Thank you.

No it happens only a few times by me.

I have changed nothing (yes my network was completely changed by tp-link
Omada but it have even with this new hardware one time the problem)

Hi, I switched to local access and it works but is there a way to completely disable or remove Somfy cloud access?
When I use the official app (TaHoma) and when I’m not connected with my wifi network it’s still functioning like before. Yes I could remove the app, but the somfy box/hub still doing something with the cloud I guess (updates?)

To use ‘local’ you still need an access token that is being checked with Somfy servers first. So, basically the Tahoma will always first communicate with Somfy services. And yes, it needs the (firmware) updates as well.

In the cloud API we have the battery level of the sun


but the battery level isn’t available in the local API

Should it be possible to have this data for the diagnostic of the batteries?

Thank you for your work on the integration!
I recently bought the Tahoma switch, installed the app and managed to get my sunscreen and two rolling shutters connected.
I followed the steps in the link provided when switching on the developer mode and made the connection in HA with the Overkiz integration on local API.
I had to change the IP and restart the Tahoma switch (replaced my router), but it never came up again.
When I try to make the connection again, I get a message “Failed to connect”.

The switch is working and pingable, DNS records are correct, I can connect it via cloud api so the switch is working and connected. Alse my Somfy login is working, so the credentials are ok.
I can’t find any attempt to connect in de HA logging.

Does anyone have any idea where to look? It’s all working with the cloud api, so I can rule out most of the components.
Does anyone know why I have to go through the steps with REST api to generate a token when I don’t seem to need any when connecting with the Overkiz integration?

Thanks in advance!

Can you still access port 8443? You should be able to access https://[ip adress]:8443/enduser-mobile-web/1/enduserAPI/apiVersion if the port is still open. In my situation, this one is often closed and the local API is not responding (where cloud API does work).

See:
Port 8443 closed after reboot · Issue #139 · Somfy-Developer/Somfy-TaHoma-Developer-Mode (github.com)
Local access stops randomly working · Issue #131 · Somfy-Developer/Somfy-TaHoma-Developer-Mode (github.com)

You can actually disable network access and the local API will still work. For the first time you will need to create a token via the Somfy API, but afterwards it won’t communicate with the Somfy server anymore.

I have been using the Overkiz integration for a long time.
This morning it asks me to reconfigure. It says I have to enable developer mode.
I enable developer mode on the somfy web page, but I can’t configure the integration because I have errors.
The host was set to gateway-xxxxxxxxx.local:8443, is that correct?
Do I have to put something in place of the x’s? I tried to put the gateway IP but it doesn’t work
I know the username and password, but when I try to connect it gives me a connection error.
What parameters do I have to put to configure the integration? I couldn’t figure it out by reading here and there.

UPDATE: After I did a reboot everything started working again, sorry