Have you any error on your log?
no, nothing in the log at all.
rebooted the Tahoma Switch and all working, must have had a bug up itâs arse. thanks anyway.
1 Like
No. If the status isnât reflected in the TaHoma classic app, after you use your mechanical switch, we canât fix it either.
As far as I know, these Izymo IO transmitters donât broadcast the state real-time.
does the entity show status opening / closing, my IO roman blinds do, but do not show Open / Closed, so I created my own helper / automation / cover, so now if i use the remote control it shows the correct state Open or Closed
if your entity does show Opening / Closing when you press the button you could do the same, give me a shout if you need help.
I am not sure if we are talking about a similar configuration or the same challenge.
I have an io shutter motor (tied into HA) with mechanical up/down rocker switch interrupted by an intermediate izymo io receiver #1822660 (NOT detectable and NO entity in HA), so the shutter can be controlled both manually (via up/down rocker switch with signaling of command (via izymo) and directly via Tahoma.
Here I wonder if and how I can integrate the izymo io receiver in HA so that I can also process its signals (up/down/status?) passed from the manual switching operation (rocker switch up/down) to the io shutter.
But maybe I still understand too little of a âhelperâ in HA 
ahh i see, then if it were me i would just replace the izymo with something like a shelly 2.5 Shelly Plus 2PM - All products - Products - Shelly it has full support in HA and replace the switch with push button type, that would give you full control over the motor.
considered in isolation, this might be a good solution - but here the izymo represents the connection from the manual wall switch and/or a SOMFY hand-held transmitter to the (dumb) roller shutter - at least the SOMFY integration would be omitted with the Shelly solution.
yeah, you also get a Shelly Blu Shelly BLU Button1 - All products - Products - Shelly if you really need a handheld remote.
Hi, newby here.
I have the Overkiz integration up and running on my sun-shades, and everything seems to work just fine.
However, the original sun- and windsensor of Somfy (i/o) is still active, and makes unwantend movements initiated by the sun-sensor. I can turn this sensor off by switching to the âmanualâ mode on my remote.
But when I do this, commands from HA are not followed up anymore. In the Tahoma Switch it gives a notification that the motor is in manual mode, and because of that, can not be controlled. There is a manual override button available in the Tahoma app, and after pressing this button I do get the chance to control it, one time.
My question is: Is there a way to control this override in HA? In a way that I can switch to manual mode to turn off the original sunsensor and still control through HA?
Thanks already for your advice!
1 Like
I did some more browsing ⌠and this one, BleBox ShutterBox v2.0, seems to solve my challenge, I guess, i.e. full HA integration, the shutter remains manually operable, it puts the handheld remote out of work 
1 Like
Hi Andy,
i am working on a challenge thatâs close to the one you are discussing here i guess.
my setup is looking like this HA >> OverKIZ >> Somfy Connection Kit >> many roman blinds with IO motors.
i want to use the opening/closing status as a condition within an automation, but i am struggling how i can check / read those ⌠you were talking about a âhelperâ.
Can you provide me some help if possible how i can achieve this in any way?
The goal of the automation idea is, i also want to be able to close / open the blinds with a zigbee based switch - which works in general - but i want to be able to press the same switch a second time to stop the current action/movement.
Thx !!!
Hi sure herâe an example from my configuration.yaml, I use it on my roman blinds.
template:
- trigger:
- platform: state
entity_id:
- cover.andys_bedroom_somfy_window_shade
id: "on"
from: opening
to: unknown
- platform: state
entity_id:
- cover.andys_bedroom_somfy_window_shade
id: "off"
from: closing
to: unknown
binary_sensor:
- name: Andys Shade Helper
unique_id: bef6f128-9493-49f1-a61c-d3db57d38af4
state: "{{ trigger.id }}"
cover:
- platform: template
covers:
andys_bedroom_window_shade:
unique_id: dcb9f6e3-f1f2-46d6-9d06-6f52a3222681
device_class: blind
friendly_name: "Andys Bedroom Window Shade"
value_template: >
{% if states('cover.andys_bedroom_somfy_window_shade') == 'opening' %}
opening
{% elif states('cover.andys_bedroom_somfy_window_shade') == 'closing' %}
closing
{% elif states('binary_sensor.andys_shade_helper') == 'off' %}
closed
{% elif states('binary_sensor.andys_shade_helper') == 'on' %}
open
{% else %}
none
{% endif %}
open_cover:
- condition: state
entity_id: binary_sensor.andys_shade_helper
state: "off"
- service: cover.open_cover
target:
entity_id: cover.andys_bedroom_somfy_window_shade
close_cover:
- condition: state
entity_id: binary_sensor.andys_shade_helper
state: "on"
- service: cover.close_cover
target:
entity_id: cover.andys_bedroom_somfy_window_shade
stop_cover:
service: cover.stop_cover
target:
entity_id: cover.andys_bedroom_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 %}
and to action it you can use cover.andys_bedroom_window_shade
you can still use your remotes, as it will update tthe new cover to the correct state,the only down side is, closing / opening half way, will show the incorrect state, I.E if open, and you close half way and stop it will show as closed, but just open slightly and stop, the Fav postion button works though, as it should closed completely the reopen to your saved position.
Hi Andy,
thank you so much for your help âŚ
i now understand this concept a bit more 
however - it looks like either my venetian blinds or the connection of the blinds through the somfy-connectivity-kit with the overkiz integration does not report the âopeningâ or âclosingâ state.
tried to check it with a simple {{ states(âcover.arbeitenâ)} line within the template tab of the developer tools - and moved the blinds around. This unfortunately resulted only in reporting back âopenâ or âclosedâ.
or am i on the wrong track here?
no, you are correct, mine are the reverse (only show âopening, closing, unknownâ)
First of all apologies for asking maybe an âoff Topicâ questionâŚ
I Have a Somfy opening sensor, that shows if a door is open, closed or even being tampered with.
In the Somfy ap, this sensor switches instantly, when open or closed.
However, in the Overkiz on HA, the sensor does not respond the actual open or close state, or just very late. (Minutes later, or not at all)
Is there a way to see the changing sate instantly, like in the Tahoma app?
Apologies once again, but I am an absolute Noob to HA and programming.
Thanks in Advance,
Erwin
Hi,
I canât get the local API working on my connexoon.
- HA version 2023.12.0 in a container
- On an up-to-date rpi
- I got the connexoon in developer mode (ergo my credentials are being accepted)
- the default host: gateway-xxxx-xxxx-xxxx.local:8443 completed with my own PIN wonât connect
- Filling the host with the IP of the connexoon completed with the port:8443 will result in a response: âCannot connect to host, certificate verify failed.â
- when trying to access with false credentials I get : âOngeldige authenticatieâ (invalid authentication) so it seems iâm able to reach somethingâŚ
I powercycled the connexoon several times and even left it unpowered for while.
Am I missing something? Somebody got a clue what to do?
Many thanks!
JJ
try with IP and disable SSL. a user in the beta had the same same as you
Overkiz integration - Local API [Development / Testers topic] - #240 by samvandenberge
Great! Works like a charm!
Thanks!!!