WTH for usablity can't the services in automations include check boxes for the bulk of options without digging into Yaml

Don’t get me wrong i am sure that the volume of work involved in doing this would not be small, but would it not be possible to have the most common “Data” entries available with a clue to what it is so you can just select and drop in the setting?

I am no programmer, and I don’t really have time to learn the structure in depth or do it enough to remember what i had done previously. So It is a shame as all the really interesting, useful and cool stuff needs you to select a service and then jump between browser tabs trying to copy and paste in the Yaml in the right format, layout and spacing.

It would probably need some groundwork and expectations to be set but would be a great benefit for usability

Can you give an example to make this less general/vague?

No matter what the devs come up with you are going to have to learn to use it.

Apologies, i have dug into the examples which i had struggled with in the past and they seem to have improved (I had not gone back to them due to the challenge).
The only residual item is the notifications to the Companion App under Data, however there are so many variables in there its unlikley to have those listed out, regardless of how many users use (or want to use) it.

I agree (and know) there is always going to have to be things to understand on whatever the software.

Best to close this one off or delete if possible as it had fixed itself in previous releases (Must try to read the release notes more)

Thanks