groston
(Gerry Roston)
November 12, 2023, 4:28am
1
Automations in my system where running without issue. I made a small tweak and am now seeing:
Automation is unavailable
Message malformed: Unable to determine action @ data['action'][0]
on one of the automations. So, I dumped the entirety of my automations.yaml file into https://www.yamllint.com/ and it reported “Valid YAML!”.
What should I try doing to fix this issue?
123
(Taras)
November 12, 2023, 4:38am
2
groston:
I made a small tweak
I would start by undoing it.
1 Like
groston
(Gerry Roston)
November 12, 2023, 5:36am
3
I did. In fact, when I tried to use the screen interface to modify the automation (previously, I had edited the .yaml directly), that failed with a similar error message:
Message malformed: Unable to determine action @ data['action'][0]
groston
(Gerry Roston)
November 12, 2023, 5:42am
4
Figured it out: Someone had suggested that device_id not be used under action. I had removed this line and that is what caused the problem.
tom_l
November 12, 2023, 5:52am
5
You need to replace it with service calls and entity ids instead of device actions. See:
Don’t forget that the first post in a community guide is a wiki - feel free to add to it or correct it.
This guide was written with reference to:
Home Assistant 2023.8.3
Supervisor 2023.08.1
Operating System 10.5
Frontend 20230802.1 - latest
Background
When you start writing automations, a device trigger seems the obvious choice. Everybody knows what a device is and it comes at the top of the UI dropdown list.
[image]
It works… but it is certainly not a “great way to start” because it …