-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for UpDownHorizontalAwning (rts:HorizontalAwningRTSComponent) #42
Comments
@gieljnssns every Awning should already be supported, could you give it a try using the latest version? |
For me it's correct now, so green circled button closed (lift the screen "up" in my case) and red circled button brings the screen down out. |
@gieljnssns could you try the following branch https://github.com/iMicknl/ha-tahoma/tree/fix_44 and see if this fixes your issue? |
It takes about 15 a 20 sec in between a click and my awning to respond |
@gieljnssns don't you have this delay when using the Tahoma app? Because I am not sure what could cause the delay, we send the commands directly to the Tahoma API like the old component. Thanks for testing. |
I do not experience this delay with my (io protocol) awning. |
I do not have this delay when using https://www.tahomalink.com/enduser-mobile-web/steer-html5-client/tahoma/ deploy awning {
"startTime": 1592044728710,
"owner": "[email protected]",
"actionGroup": {
"label": "Zonnetent - Ontplooien - TaHoma PC",
"shortcut": false,
"notificationTypeMask": 0,
"notificationCondition": "NEVER",
"actions": [
{
"deviceURL": "rts://1211-2998-xxxxxxx/16728xxxx",
"commands": [
{
"type": 1,
"name": "deploy",
"parameters": []
}
]
}
]
},
"description": "Execution : Zonnetent - Ontplooien - TaHoma PC",
"id": "ad42b184-ac10-3401-3e31-xxxxxxxxxxxxxxx",
"state": "TRANSMITTED",
"executionType": "Immediate execution",
"executionSubType": "MANUAL_CONTROL"
} undeploy {
"startTime": 1592044875418,
"owner": "[email protected]",
"actionGroup": {
"label": "Zonnetent - Sluiten - TaHoma PC",
"shortcut": false,
"notificationTypeMask": 0,
"notificationCondition": "NEVER",
"actions": [
{
"deviceURL": "rts://1211-2998-xxxxxxxx/16728xxxx",
"commands": [
{
"type": 1,
"name": "undeploy",
"parameters": []
}
]
}
]
},
"description": "Execution : Zonnetent - Sluiten - TaHoma PC",
"id": "ad44ee99-ac10-3401-3e31-xxxxxxxxxxxxx",
"state": "TRANSMITTED",
"executionType": "Immediate execution",
"executionSubType": "MANUAL_CONTROL"
} my-position {
"startTime": 1592044984619,
"owner": "[email protected]",
"actionGroup": {
"label": "Zonnetent - My positie - TaHoma PC",
"shortcut": false,
"notificationTypeMask": 0,
"notificationCondition": "NEVER",
"actions": [
{
"deviceURL": "rts://1211-2998-xxxxxxxx/16728xxxx",
"commands": [
{
"type": 1,
"name": "my",
"parameters": []
}
]
}
]
},
"description": "Execution : Zonnetent - My positie - TaHoma PC",
"id": "ad44ee99-ac10-3401-3e31-xxxxxxxxxxxxx",
"state": "TRANSMITTED",
"executionType": "Immediate execution",
"executionSubType": "MANUAL_CONTROL"
} |
I am not sure why I will see if we can find some more people with different |
'There hasn't been any activity on this issue recently. Is this issue still present? |
Hi @iMicknl I see this issue is auto closed, sadly I have the same issue as @gieljnssns. When looking at the icons, I find these very confusing, I would have preferred the same icons as in your example: https://raw.githubusercontent.com/iMicknl/ha-tahoma/master/media/tahoma_device_page.png I've got an RTS awning connected to a TaHoma box in my setup, I'm more than happy to help you test, let me know! |
I think this is indeed more HA related, since you can change the icon type but not the direction of the arrows, my "Horizontal" IO awning also moves diagonally down when opening so diagonal arrows would be more fitting. |
Unfortunately, this is something in core that is confusing. We map this device to The screenshot on the main page of this repository is using |
I don't really mind which direction the arrows show, I just don't understand the current buttons :-) I'll have a look into changing the device class |
Copied from vlebourl/tahoma_extended#8 by @gieljnssns
Device details
The text was updated successfully, but these errors were encountered: