I have a Tahoma switch SW version 1.21 from 28th of november 2023. so up to date ! could be great if another user is on the same version he confirms this is working for him
Hearing what you say i would try verifying certificate and if it does not work i would automatically continue installation without (informing user)… this would be more user friendly
This should always be a conscious choice and should be visible to the user, since it is a security feature.
Let’s see if we get more similar issues reported, and otherwise we can see where to improve the error message or documentation.
Not sure why yours didn’t work, but it could be that some hubs didn’t receive the new certificate yet.
It looks like very similar as my reported issue Overkiz integration - Local API [Development / Testers topic] - #204 by brozikcz
Thank you for creating the issue.
After I have renewed my complete network I had no issues anymore with the availablity of my covers with the Tahoma Switch.
Unfortunately I had some issues tonight. My network gives no issues with my Home Assistant hardware and with the Somfy Tahoma Switch.
This are the first issues of a the covers that they are not available anymore:
Gesloten
03:57:18 - 3 uur geleden
Is niet meer beschikbaar
03:54:32 - 3 uur geleden
After this the message is repeated EVERY second:
Gesloten
03:59:23 - 3 uur geleden
Is niet meer beschikbaar
03:59:22 - 3 uur geleden
Gesloten
03:59:21 - 3 uur geleden
Is niet meer beschikbaar
03:59:19 - 3 uur geleden
…
…
…
Is niet meer beschikbaar
03:57:53 - 3 uur geleden
Gesloten
03:57:52 - 3 uur geleden
Is niet meer beschikbaar
03:57:51 - 3 uur geleden
Gesloten
03:57:51 - 3 uur geleden
Is niet meer beschikbaar
03:57:50 - 3 uur geleden
Gesloten
03:57:49 - 3 uur geleden
So very strange because the mechanism is that it polls every 30 seconds?
What could this be?
I don’t think it is any network related.
UPDATE:
This in the log file
2023-12-12 03:54:29.614 INFO (MainThread) [backoff] Backing off fetch_events(...) for 0.5s (aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host 192.168.1.32:8443 ssl:default [Connect call failed ('192.168.1.32', 8443)])
2023-12-12 03:55:02.276 INFO (MainThread) [backoff] Backing off fetch_events(...) for 0.0s (aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host 192.168.1.32:8443 ssl:default [Connect call failed ('192.168.1.32', 8443)])
2023-12-12 03:55:32.889 INFO (MainThread) [backoff] Backing off fetch_events(...) for 0.8s (pyoverkiz.exceptions.NotAuthenticatedException: Not authenticated)
2023-12-12 03:56:02.453 INFO (MainThread) [backoff] Backing off fetch_events(...) for 0.5s (pyoverkiz.exceptions.NotAuthenticatedException: Not authenticated)
2023-12-12 03:56:47.590 INFO (MainThread) [backoff] Backing off fetch_events(...) for 0.7s (aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host 192.168.1.32:8443 ssl:default [Connect call failed ('192.168.1.32', 8443)])
2023-12-12 03:57:17.875 INFO (MainThread) [backoff] Backing off fetch_events(...) for 0.4s (pyoverkiz.exceptions.NoRegisteredEventListenerException: No registered event listener)
@martinst I don’t know how to debug this to be honest. It is an error thrown by our underlying HTTP library, and this happens when it cannot connect to your host. This can be a connection issue (network) or an issue with the hub, where it isn’t available for a bit…
Not sure where to start debugging this.
Okay…hopefully it will not execute many times 
After 1 week, the official local integration is working perfectly for me with a TaHoma Rail Din v1, a bunch of IO cover by Somfy, an IO Velux and a Somfy Smart Elixio motorized gate.
The only issue I have is that my gate (an on rail sliding gate) is seen as 50% opened when fully opened. At the same time, it’s seen fully opened in Homebridge with TaHoma plugin.
Maybe something that could be easily fixed, tell me @imick if you want some more information and debug ?
Do you use HomeBridge via Local API or Cloud API? Please create an issue on GitHub with your diagnostics log for the motorized gate.
Both configuration are local, either HomeBridge and Overkiz integration. I will do so this week-end when at home.
Same here. Tahoma Switch on latest firmware. Local API works, but only when deselecting SSL during setup.
Tonight I had the same issue as before. The Tahoma switch was not available:
2023-12-20 03:45:46.604 INFO (MainThread) [backoff] Backing off fetch_events(...) for 1.0s (aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host 192.168.1.32:8443 ssl:default [Connect call failed ('192.168.1.32', 8443)])
2023-12-20 03:46:17.234 INFO (MainThread) [backoff] Backing off fetch_events(...) for 0.6s (pyoverkiz.exceptions.NoRegisteredEventListenerException: No registered event listener)
My network gives no errors in the logging.
In HA I see at the history for 2 minutes EVERY second the covers are unavailable and closed…unavailable…closed…etc
Does anybody have those same issues?
Switched my cloud integration over to Local and it went flawlessly, everything came back with old names.
Thanks for all the effort. Whilst turning off polling fixed me getting banned every couple of months, glad I completely don’t have to worry about that any more.
Hi, is it possible to somehow simply switch from cloud api to local api (overkiz) in installation, which is now running cloud api? I dont want to reconfigure all the things and automations.
Thx
If you haven’t change the entity id and you reconfigure from cloud to local your entities should appear with exactly the same name. Therefore no reconfiguration of your automations etc. are required.
Can you please share how you got the status working? I’ve tried using a Cover Template as suggested but those entites still shows as Unknown.
sure thing
template:
- trigger:
- platform: state
entity_id: cover.media_room_somfy_window_shade
id: opening
to: opening
- platform: state
entity_id: cover.media_room_somfy_window_shade
id: open
from: opening
to: unknown
- platform: state
entity_id: cover.media_room_somfy_window_shade
id: closing
to: closing
- platform: state
entity_id: cover.media_room_somfy_window_shade
id: closed
from: closing
to: unknown
sensor:
- name: Media Room Shade Helper
unique_id: a5c19860-c74d-4b25-8893-982e8b135bcd
state: "{{ trigger.id }}"
cover:
- platform: template
covers:
media_room_window_shade:
unique_id: b717049e-f5d0-43ba-a6b5-c2f64041b9c4
device_class: shade
friendly_name: "Media Room Window Shade"
value_template: "{{states('sensor.media_room_shade_helper')}}"
open_cover:
- condition: state
entity_id: sensor.media_room_shade_helper
state: "closed"
- service: cover.open_cover
target:
entity_id: cover.media_room_somfy_window_shade
close_cover:
- condition: state
entity_id: sensor.media_room_shade_helper
state: "open"
- service: cover.close_cover
target:
entity_id: cover.media_room_somfy_window_shade
stop_cover:
service: cover.stop_cover
target:
entity_id: cover.media_room_somfy_window_shade
icon_template: >-
{% if this.state == 'opening' %}
mdi:arrow-up-box
{% elif this.state == 'closing' %}
mdi:arrow-down-box
{% elif this.state == 'closed' %}
phu:shutter-100
{% else %}
phu:shutter-20
{% endif %}
Great thanks. I have 6 shades so I’m assuming this will be rather large?
just duplicate the code foe each shade (don’t forget to change the unique_id)
Is anybody here who has a Unifi network? I am longer able to use the local integration and i think it changed since one of the latest Unifi updates. Unfortunately i dont know currently how i can fix that issue.
For instance i do no longer get a response when i try to open the local URL: https://gateway-xxxx-xxxx-xxxx.local:8443