Zigbee2MQTT - Tuya 4-button Scene Switch (TS0044)

Chaoscontrol · January 27, 2024, 6:03pm

Yes, it worked wonderfully! Thanks!

Milinator · February 2, 2024, 8:00pm

I updated Zigbee2Mqtt and Home Assistant Core and now only one click works. Is it just me?

RTJR · February 4, 2024, 2:32am

Does not work when using Input Select: Next to cycle through scenes. Normal operations on the a regular light bulb work for me. I’m able to cycle through the scene entities using a separate automation as shown below:

alias: test
description: ""
trigger:
  - platform: device
    domain: mqtt
    device_id: some_device_ID
    type: action
    subtype: 3_single
    discovery_id: some_device_ID action_3_single
condition: []
action:
  - service: input_select.select_next
    target:
      entity_id: input_select.scene_entities
    data:
      cycle: true
  - service: scene.turn_on
    target:
      entity_id: "{{ states('input_select.scene_entities')}}"
mode: single

Edit: It doesn’t look like you can have more than a single action per press (i.e. you can’t call Light Bulb 1: Toggle and Light Bulb 2: Toggle. Only Light Bulb 1: Toggle will work)

speynaud · February 9, 2024, 9:50am

Hi Guy,
I’m new in Home Assistant and I try to use a TS0044 button, my mqtt setup and Zigbee2MQTT setup seems to be ok because I successfully pairing my button and my roller.
Regarding my roller all is OK, but I have an issue with my button x4 TS0044
I can see in equipement event “button 1 single” “button 2 single” “button 1 double” but nothing is working in blueprint script.
When I excute manualy automation I was an error with
command: ‘{{ trigger.to_state.state }}’
I changed it as I saw in forum by :
command: “{{ trigger.payload_json }}”
Now I don’t get error with manual execution but when I push a button nothing
Can you help me?
I give you screenshots
Thank you so much for your help

speynaud · February 9, 2024, 9:51am

speynaud · February 9, 2024, 9:51am

simpat1zq · February 11, 2024, 2:42pm

I can only get single click to work as well.

phier · May 3, 2024, 2:01pm

hello,
what is that blueprint good for? as its natively supported by haas?

thanks!

yossi33 · May 25, 2024, 7:11pm

Same problem here. Stopped working for some reason (not even sure when). I get the Z2M evens correctly (I checked the log file of the sensor entity and I see the events) but for some reason the automation itself does not execute.
Can anyone help ?

yossi33 · May 25, 2024, 8:01pm

Solved.
The Entity ID includes the attribute. In my case the entity ID looked like that:
sensor.0x847127fffe27cc14_action
In the blue print the trigger was based on the entity ID and the attribute (“Action”).

I removed the attribute from the trigger (put a # in front of it) and it started to work:
trigger:

platform: state
entity_id: !input switch

attribute: action

DuongHC88 · May 28, 2024, 3:33pm

Thank you so much. Worked.

yfrans · June 16, 2024, 8:32pm

Since these buttons report an empty state immediately after reporting the button state, I recommend adding a condition to the template so when the state is empty, the automation will not restart.

Add this right after the trigger:

condition:
  condition: template
  value_template: '{{ trigger.to_state.state in ( ''1_single'', ''2_single'',
    ''3_single'', ''4_single'', ''1_double'', ''2_double'',
    ''3_double'', ''4_double'', ''1_hold'', ''2_hold'',
    ''3_hold'', ''4_hold''
    ) }}'

(This code is from the Aqara Opple template: Aqara Opple 6 Button Remote 3 bands (WXCJKG13LM) via Zigbee2MQTT [Z2M] · GitHub)

Lux4rd0 · June 21, 2024, 6:10pm

Thanks to everybody for their continuing updates to this blueprint over the years. I was still running into troubles with all the variations, plugging away at what worked in some parts of the script but stopping working along the way in others with different platform updates. I think I got bit by the spaces in my friendly names, but I didn’t want to have to configure my MQTT server every time. So, combining all the different blueprints and some help from ChatGPT - I finangled another version. I’m publishing here if it helps anybody! Thanks to the community!

Currently running HA core: 2024.6.3, Zigbee2MQTT: 1.38.0 commit: fe048e6

github.com

lux4rd0/homeassistant/blob/4070c53c0597808250fbe435cedc51a8cec55409/blueprints/zigbee2mqtt_tuya_4_button_scene_switch_ts0044.yaml

blueprint:
  name: Zigbee2MQTT - Tuya 4-Button Scene Switch TS0044
  description: >
    Automate your Tuya 4-Button Scene Switch (TS0044) via Zigbee2MQTT.

    This blueprint allows you to configure actions for each button press type on
    the Tuya 4-Button Scene Switch (TS0044). The switch can be integrated with
    Home Assistant using Zigbee2MQTT. Each button supports single press, double
    press, and long press actions.

    **Instructions:**

    1. **Switch**: Select your Tuya 4-Button Scene Switch from the entity dropdown.

    2. **Base MQTT Topic**: By default, the base MQTT topic is set to `zigbee2mqtt`.
       You can change this if your Zigbee2MQTT setup uses a different base topic.

    3. **Actions**: For each button, configure the desired actions for a single press,
       double press, and hold.

This file has been truncated. show original

stncttr908 · June 28, 2024, 3:12pm

Literally just took delivery of a couple of these yesterday and this is just what I needed. Thank you!

jplivingston08 · July 7, 2024, 1:12am

You are the best !! Worked perfectly !
Thanks!

Hound · July 23, 2024, 1:09pm

Does this also work for the ts004f that many of us have?

Lux4rd0 · July 28, 2024, 6:32am

I think so. I was confused about which one I had until I double-checked what showed up in MQTT. I’ll see if i can find some examples of any differences…

Wheemer · August 5, 2024, 11:40pm

Hello;

I have three of the TM-YKQ004 remotes that recently stopped working with the original blueprint. I cannot get them working at all now, even with the latest version of the blueprint offered by Lux4rd0.

Am I the only one that this remote no longer works for? Any suggestions or updates? I should mention I am running the latest beta of home assistant.

Thanks

Wheemer · August 6, 2024, 2:24pm

Turns out a complicated blueprint is not the answer. A simple automation is working just perfectly.

alias: Remote
description: ""
trigger:
  - platform: state
    entity_id:
      - sensor.remote_action
    to: 1_single
    id: 1s
  - platform: state
    entity_id:
      - sensor.remote_action
    to: 2_single
    id: 2s
  - platform: state
    entity_id:
      - sensor.remote_action
    to: 3_single
    id: 3s
  - platform: state
    entity_id:
      - sensor.remote_action
    to: 4_single
    id: 4s
condition: []
action:
  - choose:
      - conditions:
          - condition: trigger
            id:
              - 1s
        sequence:
          - action: light.toggle
            target:
              entity_id: light.room_light
            data: {}
      - conditions:
          - condition: trigger
            id:
              - 2s
        sequence:
          - action: light.toggle
            data: {}
            target:
              entity_id: light.bird_light
      - conditions:
          - condition: trigger
            id:
              - 3s
        sequence:
          - action: light.toggle
            data: {}
            target:
              entity_id: light.fish_light
      - conditions:
          - condition: trigger
            id:
              - 4s
        sequence:
          - action: fan.toggle
            data: {}
            target:
              entity_id: fan.roomfan
mode: single

LoftGolf · August 13, 2024, 5:42pm

I will start by saying that I am fairly new to HA but coming along. I purchased a 4 button scene switch and have it connected and appears operational as per the logbook entries. My confusion is in triggering the automations as none of the blueprints or @Wheemer script is working for me. I am fairly certain that it is related to a simple missing link but I am not sure what I should be looking for. I appreciate any help.