Wrong state for Velux Shutters with Tahoma Switch & home assistant #544
Comments
|
All the attributes prefixed by xx: are returned by Somfy. We will remove them as they can be confusing. Can you confirm when you open your cover HA is well returning a closed status? |
|
Hi, I'm not sure what is called cover HA. In the 'Aperçu' page, I can see that when the shutter is closed: The buttons are in the right state. However, in the history, or when I click on the shutter icon, I get this panel, which states the shutter as open:
When the shutter is closing or opening, I have a correct 'closing' or 'openning' state. In any other case, a state 'open' is reported. Thanks. |
|
OK so you confirmed my previous message. You are confused by the raw data we output as attribute. core:xxxx and io:xxxx are data returned by Somfy. We use them to compute what you see in HA. Just ignore them.
|
|
Tetienne, I clearly understood that xx:... attributes are not directly used. What confuses me is that as you said :
Also when clicking on the cover in the main panel, I get The buttons are in the correct state to open and not close, but the history in the other tab shows the cover as "open".
This is why I think something is wrong ... In a previous install (Under Synology, I think it was ha_tahoma 2.4.10 , I don't know ha version), done in early august, things where working ok and were synchonized. Best Regards and thanks a lot for your help. |
|
That's pretty clear now. Thx for the explanation. I didn't know this kind of bug was possible. I will try to understand how it's possible. As a remark it's indeed weird Somfy always returns open state. |
|
Thanks for having a look into it. If I can help by checking things or providing logs, don't hesitate. |
|
Thx ! Can you show me the attributes for your cover in the following states: closed, almost closed, almost opened and opened? In the Tahoma application, everything is OK? On our side to know if a cover is closed we check if |
|
Here are the attributes in the asked positions: Open Almost open: Almost closed: Closed: In the Tahoma application on iphone, everything works well: The cover appears as closed when closed. Yes, I think the reason is that I just checked with my previous install ( ha core-2021.7.4, ha_tahoma 2.4.10) and the behavior is now the same as with the current install... The |
|
In order to test, I tried to slightly modify tahoma_cover.py In the is_closed method, I just commented the test on the state variable, to rely only on the position to tell if the shutter is closed. Then, the value of core:OpenClosedState is not used anymore. This indeed seems to solve my problem, but I don't know if there are side effects. I'll check tomorrow. Thanks |
|
I will contact their support to know what’s the best way to know if a cover is closed or not. Removing the code you comment will break other devices, like the gate with pedestrian position which behave in HA like a cover but without position. |
{
"commands": [
{
"commandName": "advancedRefresh",
"nparams": 1
},
{
"commandName": "close",
"nparams": 0
},
{
"commandName": "delayedStopIdentify",
"nparams": 1
},
{
"commandName": "down",
"nparams": 0
},
{
"commandName": "getName",
"nparams": 0
},
{
"commandName": "identify",
"nparams": 0
},
{
"commandName": "my",
"nparams": 0
},
{
"commandName": "open",
"nparams": 0
},
{
"commandName": "refreshMemorized1Position",
"nparams": 0
},
{
"commandName": "setClosure",
"nparams": 1
},
{
"commandName": "setDeployment",
"nparams": 1
},
{
"commandName": "setMemorized1Position",
"nparams": 1
},
{
"commandName": "setName",
"nparams": 1
},
{
"commandName": "setPosition",
"nparams": 1
},
{
"commandName": "setSecuredPosition",
"nparams": 1
},
{
"commandName": "startIdentify",
"nparams": 0
},
{
"commandName": "stop",
"nparams": 0
},
{
"commandName": "stopIdentify",
"nparams": 0
},
{
"commandName": "up",
"nparams": 0
},
{
"commandName": "wink",
"nparams": 1
},
{
"commandName": "pairOneWayController",
"nparams": 2
},
{
"commandName": "setConfigState",
"nparams": 1
},
{
"commandName": "unpairAllOneWayControllers",
"nparams": 0
},
{
"commandName": "unpairOneWayController",
"nparams": 2
}
],
"states": [
{
"type": "ContinuousState",
"qualifiedName": "core:ClosureState"
},
{
"type": "DiscreteState",
"values": [
"good",
"low",
"normal",
"verylow"
],
"qualifiedName": "core:DiscreteRSSILevelState"
},
{
"type": "ContinuousState",
"qualifiedName": "core:Memorized1PositionState"
},
{
"type": "DataState",
"qualifiedName": "core:NameState"
},
{
"type": "DiscreteState",
"values": [
"closed",
"open"
],
"qualifiedName": "core:OpenClosedState"
},
{
"type": "ContinuousState",
"qualifiedName": "core:PriorityLockTimerState"
},
{
"type": "ContinuousState",
"qualifiedName": "core:RSSILevelState"
},
{
"type": "ContinuousState",
"qualifiedName": "core:SecuredPositionState"
},
{
"type": "DiscreteState",
"values": [
"available",
"unavailable"
],
"qualifiedName": "core:StatusState"
},
{
"type": "DiscreteState",
"values": [
"comfortLevel1",
"comfortLevel2",
"comfortLevel3",
"comfortLevel4",
"environmentProtection",
"humanProtection",
"userLevel1",
"userLevel2"
],
"qualifiedName": "io:PriorityLockLevelState"
},
{
"type": "DiscreteState",
"values": [
"LSC",
"SAAC",
"SFC",
"UPS",
"externalGateway",
"localUser",
"myself",
"rain",
"security",
"temperature",
"timer",
"user",
"wind"
],
"qualifiedName": "io:PriorityLockOriginatorState"
}
],
"dataProperties": [
{
"value": "500",
"qualifiedName": "core:identifyInterval"
}
],
"widgetName": "PositionableTiltedRollerShutter",
"uiProfiles": [
"StatefulCloseableShutter",
"StatefulCloseable",
"Closeable",
"StatefulOpenClose",
"OpenClose"
],
"uiClass": "RollerShutter",
"qualifiedName": "io:RollerShutterVeluxIOComponent",
"type": "ACTUATOR"
} |
|
Thanks tetienne, please keep me informed if you get some information from the support. I noticed that things are ok with Somfy shutters, but Velux shutters through Tahoma seem to have this pb. |
|
Somfy support was nice, and tested in their lab. They reported me the So we have to continue the investigation. Can you please close your cover, and restart HA. Do you still have the Can you also enable the debug mode (don’t forget to restart)? See https://github.com/iMicknl/ha-tahoma#enable-debug-logging Open your cover, then close it. Wait at least 30s, and go to the logs page. Click on the Load full HA logs button. Paste here all the logs you will see related to our component. |
|
Hello tetienne, sorry for being long to answer, but I didn't have access to the shutter during this time. I dit the requested manoeuvers: 1/ Close the shutter, restart HA. The state is as follow after the restart
2/ Enable debug, then open then close cover. Here is the full log Thanks for your help |
|
Can you please update the component with this version please https://github.com/iMicknl/ha-tahoma/archive/refs/heads/enhancement/better-logs.zip |
|
@dbrep can you retry the previous scenario with the latest version? You will see more debug log. |
|
Hello tetienne, Sorry for the answering delay : I couldn't find the time to have a look. I checked this morning after having updated to the last version on your github. It seems that the state is now perfect for the cover : When closed I get this : I'll try to find th etime today to send you the logs, but not sure I'll manage to do it. It can be next week. Thanks a lot anyway, things seem to be working fine. Best Regards |
|
@dbrep could you try how this works with 2.9.1? I will close this issue for now, since you mentioned last time that it works. Just reply here if you still have an issue, and we will reopen this issue. |
|
I have the exact same problem described here, only with a somfy gate, the state is always open and position 50, even if the gate is closed. Any suggestions would be very appreciated, planning to automate some tasks based on the gate and this is preventing that. Thanks and appreciate the great work, too bad somfy doesn't do at least 50% of what you are doing. |
|
@SeerKan that is another problem, see #487 (comment) where we track this issue. By the way, you could give the latest master version a try. This should add a select entitity that's correct. |
|
@iMicknl thank you for that, missed that ticket. |
|
'There hasn't been any activity on this issue recently. Is this issue still present? |
|
Hi.
|
|
@alexandreaudrain could you please create another issue, since your 'issue' is not the same? The number.my_position doesn't reflect your current position. It reflects the value where the my position (preset) is set to. Calling the button will set it to that position, when supported by your device. |
|
'There hasn't been any activity on this issue recently. Is this issue still present? |
Did you read the instructions?
The problem
I use Velux shutters as well as Somfy shutters connected to a Tahoma switch box. Home assistant is using the Tahoma switch through ha-tahoma integration.
Everything works well, except the state of two Velux shutters. Even if closed, they are reported as open in the history. Somfy shutters are well reported as closed.
The activated controls in the panel work well though : can only open if they the shutters are closed.
Home assistant runs on a raspberry pi 4. Home assistant in a docker container.
Thanks for all the very impressive work done so far !
What version of this integration (ha-tahoma) has the issue?
2.6.3
What version of Home Assistant Core has the issue?
core-2021.8.8
Which gateway / hub do you use?
Somfy Tahoma Switch
Device model
PositionableTiltedRollerShutter
Device type
io:RollerShutterVeluxIOComponent
Additional information
In the development tools interface, one can see that despite a current_position of 0, the reported state its open and core:OpenClosedState is open.
Relevant log output
The text was updated successfully, but these errors were encountered: