Do you own it? Have you noticed any log message?
Is there an option to change the UI class or Widget?
I got three older (2 years old) Somfy IO screens and these are working great with the correct widget. Now I get a few new IO screens and there are displaying the wrong widget to control them in Home assistant.
My older screens
current_position: 100
ui_class: ExteriorScreen
widget: PositionableScreen
controllable_name: 'io:VerticalExteriorAwningIOComponent'
rssi_level: 76
'core:NameState': SUNILUS io
'core:PriorityLockTimerState': 0
'core:StatusState': available
'core:DiscreteRSSILevelState': normal
'core:RSSILevelState': 76
'core:ClosureState': 0
'core:OpenClosedState': open
'core:Memorized1PositionState': 105
'core:TargetClosureState': 0
friendly_name: Erker links
supported_features: 527
device_class: blind
The new screens got these properties:
current_position: 0
ui_class: Awning
widget: AwningValance
controllable_name: 'io:AwningValanceIOComponent'
rssi_level: 82
'core:NameState': SUNEA SCR 40 io
'core:PriorityLockTimerState': 0
'core:StatusState': available
'core:DiscreteRSSILevelState': good
'core:RSSILevelState': 82
'core:ClosureState': 0
'core:OpenClosedState': open
'core:Memorized1PositionState': 105
friendly_name: Overloop
icon: 'hass:window-open'
supported_features: 527
device_class: awning
Hi, widgets and ui classes are derived from Tahoma itself, so it’s not intended to be changed. But you can customize the icon and device class for those entities if the one taken from Tahoma doesn’t suit you. Have a look here https://www.home-assistant.io/docs/configuration/customizing-devices/
Great; I fixed the Icon and Ui Widget. So we are almost there.
The only problem is that the state in inversed. Is there a simple way to switch that?
Currently the screens are closed (in the bin, not blocking sun). But the widget displays the wrong icons, to close the screen instead of open it.
This might be a real issue with our component. Somfy is not consistent with its states, sometimes it’s 0=closed, 100=open, sometimes the oposit… So we mostly have to guess for each device. Can you post a bug report on github with your device controllable name, and values for open and close (I guess here, 0 is open and 100 close ?).
You are right. Both types of Somfy screens are in state open. But the screens with the right icons are on position 100 and the wrong icons on position 0. I will try to open an github bug tonight.
I have the exact same problem, any news on this yet?
current_position: 100
ui_class: Awning
widget: PositionableHorizontalAwning
controllable_name: ‘io:HorizontalAwningIOComponent’
rssi_level: 14
‘core:NameState’: SUNILUS io
‘core:PriorityLockTimerState’: 0
‘core:StatusState’: available
‘core:DiscreteRSSILevelState’: low
‘core:RSSILevelState’: 14
‘core:DeploymentState’: 100
‘core:OpenClosedState’: open
‘core:Memorized1PositionState’: 105
‘core:TargetClosureState’: 100
friendly_name: Kapschuur
supported_features: 527
device_class: awning
We need to rollback a fix. I will try to do it latest by this weekend, would be good to have this fix tested before rolling it out :).
By the way, some news after the new update! (unfortunately not for my Pergola again…)
1 Like
I am kind of lost here. Also for me, after a HA reboot today, my Tahoma integration is no longer working.
Also for me tahomalink.com is not accepting my credentials. somfy-connect.com does accept my credentials, and redirects me to tahomalink.com which then immediately complains about wrong username/password (unlike with @rabesocke).
I don’t exactly understand your solution:
"Before, I installed the Somfy integration. Then I downgraded to 2.3.2 instead of 2.3.4 it works again. "
What exactly did you downgrade? The Tahoma box itself?
I am not using the Somfy integration, as it only shows one of the two (different types) of screens i have, i am using tahoma:
Then I downgraded to 2.3.2 instead of 2.3.4 it works again. " HACS plugins Somfy Tahoma
Allright. Yesterday i found iMicknl plug-in for Tahoma (i have a Connexoon). It works great for me.
1 Like
Sorry for the late answer. I don’t have yet the device but I could try to buy one to test.
Currently we support almost all devices, there are just a few climate devices that are not fully implemented yet. My guess would be that it works, but otherwise we can work with you to get it integrated.
What kind of device is it?
Currently the update time for TaHoma is 30 seconds, which means that it can take up to 30 seconds until your open/close status will be received by Home Assistant. This unfortunately is a limitation by Somfy and limits the possibilities of the window sensor.
In other news, we just released 2.4.0 (Release v2.4.0 · iMicknl/ha-tahoma · GitHub) with some nice bugfixes. This updates also introduces support for the CozyTouch, Rexel and Connexoon RTS hubs!
1 Like
Hi, do you know if there allready a fix available for this?
Hi, I have a problem. I have two shutters with an opposite state. I have a box Tahoma
This shutter is closed but it tells me in home assistant that it is open
I have 5 shutters and I have the problem with two
Please open an issue at GitHub - iMicknl/ha-tahoma: Custom component for Home Assistant to interact with smart devices via Somfy TaHoma or other OverKiz based API's. with your information. We need to gather more information about your devices. This is a problem that is easy to fix, but the main issue is understanding which device types need to have their position reversed… Somfy made quite a mess of this.
Hello,
I have a somfy one camera decared as follow :
MyFoxAlarmController, par Somfy, Firmware: myfox:SomfyProtectAlarmController
I have some problems using it, could you help me with these problems please ?:
1- The arm-home does not work. The arm-absent and the disarm work properly. What could be the problem ?
2- I have create some automations triggered by the alarm state but they do not work
For example the following automation test does not work :
alias: Alarme Away ON
description: ‘’
trigger:
- platform: device
device_id: 0874d314802ed9f218b813a8acf8ebea
domain: alarm_control_panel
entity_id: alarm_control_panel.somfy_one_salon
type: armed_away
condition: []
action: - device_id: 01e8270cf2cc3d50aa26b59f6e20c6c5
domain: cover
entity_id: cover.vr_bureau_2
type: set_position
position: 65
mode: single
Please open an issue at https://github.com/imicknl/ha-tahoma with your information. There is an issue template that you have to fill in, which provides us with the required information.