Tuya TS0044_1 action entity gone after update

[koying (Chris B)]

Did you have a look at

Zigbee2MQTT 2.0.0 breaking changes · Koenkk/zigbee2mqtt · Discussion #24198

[msknight (Michelle Knight)]

The HA installation was built early December so I would hope I was already past that… but possibly not. I’m going to try and restore to the last backup and see what happens.

[koying (Chris B)]

Z2M 2.0 came out yesterday

[msknight (Michelle Knight)]

That’ll probably be it then.

I won’t bother reverting to backup, there’s little point. I’m going to have to work out a way forward. Any ideas please?

[koying (Chris B)]

I guess

Only breaking when legacy is enabled:

• All click sensors have been removed (homeassistant.legacy_triggers setting). This means all sensor.*_click entities are removed. Use the MQTT device trigger instead.

[KennethLavrsen]

Read this help topic Using the new action events in Zigbee2MQTT 2.0

[msknight (Michelle Knight)]

It’s the _action that is reported as being no longer provided by MQTT… so I’m not sure how to discover what I should be using instead.

[KennethLavrsen]

The new thing in 2.0 is that button presses are now reported as events in event entities. Look for new entities in HA that starts with with event like event.bedroom_switch_action

And look at the topic I just linked to how to use them

[msknight (Michelle Knight)]

That’s the interesting thing. I only have one “event” in my entities list and that’s for a callendar. I think I must be looking in the wrong place. I’m going to have a break and return to this after a cup of tea.

[msknight (Michelle Knight)]

OK - they’re showing up in automations… but only what it has seen being pressed. It will mean saying goodbye to the blueprint, which was great because one automation covered all the button possibilities… but hey ho.

[KennethLavrsen]

That is device triggers. That is not new. It works. But the yaml will use some cryptic device ids that many of us avoid. If you have no event entities then

Did you update zigbee2mqtt to 2.0? And I refer to the Zigbee2MQTT version, not the addon versioning.

Is this the only switch/remote you have?

If yes to both questions then maybe the switch has not been implemented to the new world. You can still enable the legacy sensors in Zigbee2MQTT config and the old will work again. Until it gets phased out

[msknight (Michelle Knight)]

No, I have five remotes. It’s easier for my Mother as she doesn’t get on with tablets or mobile phones. Remotes… she can handle.
My Zigbee is reporting as - Zigbee2MQTT
Current version: 2.0.0-1
… and my configuration.yaml for the zigbee is…

homeassistant:
  enabled: true
advanced:
  network_key:
    - 144
    - 201
    - 204
    - 30
    - 166
    - 12
    - 248
    - 238
    - 159
    - 31
    - 234
    - 210
    - 96
    - 162
    - 169
    - 185
  pan_id: 60125
  ext_pan_id:
    - 112
    - 15
    - 116
    - 67
    - 14
    - 111
    - 19
    - 6
  channel: 25
  homeassistant_legacy_entity_attributes: false
  homeassistant_legacy_triggers: false
  legacy_api: false
  legacy_availability_payload: false
mqtt:
  server: mqtt://core-mosquitto:1883
  user: mqtt-user
  password: (redacted)
frontend:
  enabled: true
  port: 8099
serial:
  port: >-
    /dev/serial/by-id/usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_7c0265df5ed9ee118f8fb84c37b89984-if00-port0
  adapter: ember
device_options:
  legacy: false
devices:
 (list of devices)
availability:
  enabled: true
  active:
    timeout: 10
  passive:
    timeout: 60
version: 4

[KennethLavrsen]

See this reply to similar question

Using the new action events in Zigbee2MQTT 2.0

First lets see if it is supposed to be there If you go to Integrations → MQTT and find your device. Click on it. You should see something like this for a 4-button Hue switch [image] Note that there is an Events window in center column at the top. You should see an Action device there. Unfortunately there is no UI in this view that can show attributes. You have to go to developer tools → States (NOT Actions!) In the top of Filter Entities you can type event. and you should see your remote…

[msknight (Michelle Knight)]

Unfortunately, not for me. If I interpret what you’re saying, then given my current configuration, the Tuya remotes I’m using aren’t integrated into 2.0 yet and how I’m currently addressing the buttons will eventually be depreciated and removed. Am I understanding correctly please?

r

[KennethLavrsen]

See tuya 4-button switch ts0044 not show mqtt · Issue #25481 · Koenkk/zigbee2mqtt · GitHub

Also note the homeassistant_legacy_triggers: false If you enable this I would think the old stuff you had would work again. But you will be on borrowed time I would think

[msknight (Michelle Knight)]

Thanks. Reading that, I conclude that all I need to do is re-write the automations and ditch the old blue print, and everything should be fine going forward. Yes?

[KennethLavrsen]

I personally stay far away from Blueprints. I want to understand what automations are doing so I can maintain them and fix them when they break.

Blueprints always end up being too generic and try so do everything and the result is that noone excep the author understands what is going on.

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

You can enable action entities that you likely were using before that are missing now by default.

Follow the advice I gave my blueprint users in this post, enable the legacy action entities, and get your house back while you fix the rest.

Zigbee2MQTT - ZemiSmart ZM-RM02 Controller

Z2M version 2.x has dropped. This means if you install that, you will need to make a change to your configuration in order to use Zigbee2MQTT - ZemiSmart ZM-RM02 Controller. I have not yet made changes to accommodate for the update, and my changes are going to be likely using the Home Assistant experimental event entities. So to accommodate the change, I will be asking you to change 2 buttons in the Z2M set-up screen in the User Interface (UI) screen. [Z2M_Fix_2.0] …

[msknight (Michelle Knight)]

I opted to move forward. Enabling the legacy options would only work for a while.

I followed Kenneth’s advice and managed to get the buttons working by going to the device and triggering an automation from there. If you want to know precisely what I did, I altered my blog notes to cover what I hope is a method which will continue to work …
https://msknight.com/technilife/?p=2967

[SvenGeukens]

I had the same issue. So, I made a simple automatisation. Two examples from my home:

alias: Slpk Lena Drukknop
description: “”
triggers:

• trigger: mqtt
  topic: zigbee2mqtt/Slpk Lena Schakelaar Bed
• trigger: mqtt
  topic: zigbee2mqtt/Slpk Lena Schakelaar Bed
• trigger: mqtt
  topic: zigbee2mqtt/Slpk Lena Schakelaar Bed
  conditions:
  actions:
• choose:
  • conditions:
    • condition: template
      value_template: “{{ trigger.payload_json.action == ‘1_single’ }}”
      sequence:
    • action: light.toggle
      metadata: {}
      data: {}
      target:
      device_id: 4f47dc2423b6c55aee02b4772c59e414
  • conditions:
    • condition: template
      value_template: “{{ trigger.payload_json.action == ‘2_single’ }}”
      sequence:
    • action: light.turn_on
      metadata: {}
      data: {}
      target:
      entity_id: light.slpk_lena_hoofd
  • conditions:
    • condition: template
      value_template: “{{ trigger.payload_json.action == ‘2_double’ }}”
      sequence:
    • action: light.turn_off
      metadata: {}
      data: {}
      target:
      entity_id: light.slpk_lena_hoofd
      mode: single

and

alias: Tuya TS0042 - Linker- en Rechterknop Enkel Druk
description: >-
Schakelt het licht in de knutselhoek met de linkerknop en de Multiroom TL met
de rechterknop.
triggers:

• topic: zigbee2mqtt/Knutselhoek drukknop
  value_template: “{{ trigger.payload_json.action == ‘1_single’ }}”
  trigger: mqtt
• topic: zigbee2mqtt/Knutselhoek drukknop
  value_template: “{{ trigger.payload_json.action == ‘2_single’ }}”
  trigger: mqtt
  actions:
• choose:
  • conditions:
    • condition: template
      value_template: “{{ trigger.payload_json.action == ‘1_single’ }}”
      sequence:
    • target:
      entity_id: light.knutselhoek
      action: light.toggle
      data: {}
  • conditions:
    • condition: template
      value_template: “{{ trigger.payload_json.action == ‘2_single’ }}”
      sequence:
    • target:
      entity_id: light.multiroom_tl
      action: light.toggle
      data: {}
      mode: single

I hope this can help a bit.