Missing triggers when creating an automation

Hi guys, I’m trying to make a trigger for when a light switch is pressed to switch on something else. In my automation setup, under trigger type, I can choose the switch but for the Trigger itself I’m getting the message ‘Unknown trigger;’ image

This is appearing for all devices, ie Hue bulbs etc…

Any ideas appreciated!

Try to use a ‘State’ trigger type.

1 Like

Thank you for the idea!

I have successfully fixed my issue with physical zigbee button triggers missing.

For Xiaomi Zigbee Switches:
TRIGGER > STATE
When bathroom-switch-1 Action changes to single
When bathroom-switch-1 Action changes to double
When bathroom-switch-1 Action changes to triple
When bathroom-switch-1 Action changes to quadruple
When bathroom-switch-1 Action changes to hold
Note: I had to use “Action” as “Click” did not work this way.

Some devices are refusing to pair with specific coordinators, a good example is all Xiaomi and Aqara devices (which are still Xiaomi in reality); they might pair with TuYa routers but they will be quicky disconnecting from them, same goes with Sonoff Zigbee Dongle-E as coordinator (not talking about Dongle-P). These Xiaomi or Aqara devices will need to be paired with their own brand (I think I have read somewhere that they don’t follow Zigbee protocol standards comletely).
The point is, you need to pair the device to be able to obtain their triggers (you might be also be able to use Mqtt Explorer I guess), then those triggers are just simple text in your state definition.

This issue we have here also related to this one: Home Assistant lost all my devices triggers

Hi! I have the same issue with a Aqara/Xiaomi physical button. I could not follow your instructions how you fixed it - can you describe it in another way how you did it? Thanks.

If you’re using Zigbee2Mqtt you’ll need to enable Legacy Triggers for this method:

Then you select your “State”, then define your entity and “Action”.

Few more examples of such state actions:

To identify the proper actions shown above, you might need to re-pair your device in case your actions are missing, once re-paired you can use regular device triggers to check the available actions to be used for “State” triggers. Below is the device trigger for action reference.

To summarize: the point is not to use “Device” type actions as they tend to dissappear on Aqara/Xiaomi/Lumi devices, instead you will use the legacy State trigger shown in the beginning (toilet-switch Action)

Hope this helps, and sorry for the delay ed response.