TS0603 going to sleep/ignoring first message

[andystewart999]

Hi all - I've got a Zigbee Tuya TS0603 that's mains powered, controlling my garage door.

Although the garage door switch is momentary it presents to Home Assistant as a traditional switch. Not a problem, I just call switch_toggle to operate the garage door. Interestingly it's a different behaviour to this article, in that the act of toggling the switch will effectively momentarily press the button, so I don't really care if the switch is showing on or off, I'm happy that toggling will trigger the door.

It all works fine until it hasn't been used for a while (I haven't worked out how long a while is yet), after which point I have to call switch.toggle twice - once to apparently wake up the TS0603 and then once again to have the switch actually operate.

I've set QoS to 2 but that hasn't made any difference. Has anyone else found this and is there a fix?

Cheers,
Andy

[slippery-carrot]

This has been bugging me since changing out my controller for this one!!! I've just moved my coordinator thinking it may have been a LQi thing but it didn't help. How frustrating!
This sounds like a firmware related issue of the device itself. Why would it need to go to sleep if its powered by mains. Interesting implementation

[ChoffaH]

Did you ever solve this? Or can you recommend another controller that works better?

I have the same problem but mine won't respond at all after a while. It still updates the open/closed sensor but I can't trigger it other than with the manual button in the garage.

[slippery-carrot]

Whats been working for me is to have an automation that forces the switch to "off", its sending two commands that way.

Back Story

My old controller used to force itself to off and this one doesn't It just responds to the change of state and I preferred that behaviour from a frond-end pov. I have a helper input boolean that you turn on, and an automation turns it back to off after 2 seconds. This mimics the old one.
I have made an automation toggles the garage controller switch when this helper boolean is pressed.

Potential solution

I mentioned the back story because it sort of aligns with what I have that could be working. By could I mean that its been working so far, which is a few days.
I have set an automation that triggers when the garage controller switch turns "on", after 500ms it will set this back to "off".
What this is doing is basically sending two comands to the controller. If its asleep, it will respond to the second state change.
Most garage systems have a debounce on the switch that prevents double taps. I've taken advance of this. There is a chance the relay will switch twice if its not alseep, which would then send this to the garage. The idea being is that 400ms is too quick between presses for the garage to respond to as its excluded due to the debounce.

This is by no means a great solution, its a band-aid fix. To properly fix it, new code will need to be written, but I have never written firmware for zigbee nor do I fully understand how it even works. This is most definitely on my todo list of home projects, but not very high on the list due to the fix mentioned above.

The automation yaml is below

alias: Force Garage Controller State to Off
description: When the garage door switch is set to on, force it back to off after 400ms
triggers:
  - trigger: state
    entity_id:
      - switch.garage_door_controller_state
    from: "off"
    to: "on"
    for:
      hours: 0
      minutes: 0
      seconds: 0
      milliseconds: 400
conditions: []
actions:
  - action: switch.turn_off
    metadata: {}
    data: {}
    target:
      entity_id: switch.garage_door_controller_state
mode: single

[ChoffaH]

Okey, it feels like we don't have the exact same problem as mine doesn't respond even after 2 state changes. I have to unplugg mine for it to work again.

[slippery-carrot]

Oh, you replied to a thread to do with something else entirely, my bad