You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the last update of the Tahoma Box to version 1.21 my old RTS windows coverings cannot be operated anymore in HomeKit. All window coverings using IO protocol still work fine, but five old ones using RTS do not work anymore (performed without any issue before).
The RTS devices can still be operated in the new TaHome app, but in Homebride the following error occurs:
Polling error - socket hang up
setClosure Error 400 No such command : setClosure on device rts://1228-9252-9165/16721931 (rts:ExteriorVenetianBlindRTSComponent) (UNSUPPORTED_OPERATION)
It seems linke the plugin / Tahoma Box can not handle the RTS position properly anymore. Interestingly in the TaHome app the RTS devices do not show a status (open / close), while IO devices certainly do.
Any idea what's the issue here and is there any fix for it?
Thanks & kind regards
Ingo
The text was updated successfully, but these errors were encountered:
Gateway: 9165
Device: WindowCovering > Eltern
States
close
Since the last update of the Tahoma Box to version 1.21 my old RTS windows coverings cannot be operated anymore in HomeKit. All window coverings using IO protocol still work fine, but five old ones using RTS do not work anymore (performed without any issue before).
The RTS devices can still be operated in the new TaHome app, but in Homebride the following error occurs:
Polling error - socket hang up
setClosure Error 400 No such command : setClosure on device rts://1228-9252-9165/16721931 (rts:ExteriorVenetianBlindRTSComponent) (UNSUPPORTED_OPERATION)
It seems linke the plugin / Tahoma Box can not handle the RTS position properly anymore. Interestingly in the TaHome app the RTS devices do not show a status (open / close), while IO devices certainly do.
Any idea what's the issue here and is there any fix for it?
Thanks & kind regards
Ingo
The text was updated successfully, but these errors were encountered: