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.
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?
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).
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
Hello, I have the same problem, I try to reconfigure Overkiz but it asks me to activate developer mode and I canât find the option in the Somfy menu. This has happened after an update of the Somfy Tahoma. I have tried restarting HA but it still doesnât work
Update:
problem solved, selecting cloud api (before I tried local api), it asks for username/password and it works
How to enable Developer Mode in Somfyâs Tahoma Web UI
If anyone wants to set up Local API (so your blinds etc keep working even when your internet or Somfy cloud is offline), the option to âEnable Developer Modeâ is in web interface specific to your country (I was not able to find it in phone app, hopefully this saves others time):
Once the Developer Mode is enabled, you can set up Local API in HA.
How to fix if gateway-xxxx-xxxx-xxxx.local:8443 is not working
I think that may be PIN? It did not work for me because I have custom DNS setup that breaks / disables .local names.
In networks where *.local:8443 name does not work, Local API can be set up by using the IP of your Somfy box instead (e.g. 192.168.X.Y:8443) + disable TLS verification.
NOTE: If you set Host to a raw IP you need to remember to do two things:
Assign static IP to your Somfy box (configure DHCP at your Router to always give the box the same IP, and use the static IP instead of dynamic one as Host). If you donât do this, things may break in a few days, weeks, months because eventually the IP will change.
Skip TLS verification (i am guessing it only works with .local common names and may cause connectivity error with raw IP, likely why it did not work for you).
After a issue with the connexion, I have tested the local api connection. Unfortunately I have encountered disconnection which avoid to get a normal and stable usage.
It seems that there is not real solution for this point (actually I did not read a clear solution).
How to switch back to the cloud api without losing with current entity names.
Is there a way to delete the token in order to display the âconfigurationâ button?