Just updated, looks like the Hold Config option doesn’t work anymore.
Actually, it looks like that option is gone entirely.
Create a new automation and see if you can find the “config_hold” action in the dropdown. If you find it, let me know. Otherwise, I’ll need to remove that
Interesting I am seeing “config_held” as an option. But I also don’t see anything past double on any of my actions.
What firmware are you on? I have 2.18
2.18 as well. As a standard automation it triggers just fine.
triggers:
- domain: mqtt
device_id: 83570d3dc15ce985ca18fadc49d99ada
type: action
subtype: config_held
trigger: device
conditions:
actions: - action: light.turn_on
metadata: {}
data:
transition: 0
rgb_color:
- 255
- 0
- 0
target:
entity_id: light.bulb_kitchen_table
mode: single
Also I see the held action in MQTT Explorer and inside Home Assistant in the device pages MQTT Info.
1 Like
Well, I just figured it out. There wasn’t a trigger set for config_held in the Blueprint when you updated originally this morning. I have added it to my local blueprint and it works as expected.
FWIW I am using EMQX as Mosquito would often give me missing actions on restarts with my Aqara buttons. Also I now have some more actions, looks like I have never triggered the triple and quintuple actions on that switch, and you have to trigger once them for them to show in Home Assistant now.
1 Like
Thank you for testing that! The blueprint at the top is updated to reflect config_held and config_release now.