Opened/closed state FIX [blueprint] -> TS130F loratap (zigbee) roller shutter / blinds

Blueprints Exchange
, , ,
1

:house: fix for loratap TS130F (zigbee cover controller)

Almost perfect zigbee switch for my covers, except the open/closed position is not set correctly when operated from the physical button…
This very simple blueprint fixes the thing (I didn’t found anything about this correction so I had to do it… and that’s my very first blueprint, so tell me if anything is wrong :see_no_evil:)

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

loratap
loratap400×403 30.5 KB
wrongState
wrongState236×757 16.3 KB

2

Spook i tegrations inverse helper might be able to do it.

3

thanks for the suggestion, but I think this is not relevant here.

Certainly the presentation of the FIX is too short, so here is the full explanation of the issue that need a fix:

  • the cover is closed → HA states are cover state closed and current_position 0 → OK :ballot_box_with_check:
  • OPTION1: opening via the HA interface
    • the cover is open → HA states are cover state open and current_position 100 → OK :ballot_box_with_check:
  • OPTION2: opening via the physical controller
    • the cover is open → HA states are cover state closed and current_position 100 → WTF!! :beetle:
    • clic on :pause_button: in HA → HA states realizes its error and cover state open and current_position 100 → :flushed: ok… but I don’t want to clic on HA after using the physical button…
      Same for closing the cover…

Is it better than the short version “except the open/closed position is not set correctly when operated from the physical button…” ? (I won’t explain with a comic, nor a video :see_no_evil: )

4

Understood. :smiley:
The blueprint is to fix a “bug/missing feature”.

And yes the Spook integration would maybe not solve this issue or if it did then it would be a coincident of its actions.

1 Like