It would be nice, if this just updates automatically with some HA update.
I’m actually a bit tired of changing things manually every time, when someone decide to change things, which worked fine…
669 lines of code to check only in scripts.yaml, I so have no time for this…
I believe you don’t have to change anything if you don’t want to. My understanding is that the legacy syntax will continue to work, and there are no plans to remove it.
This can only be done after updating to the October release.
So in short do not change service: to action: just yet. Wait until you can change action: to actions: after updating to the October release. Only then it is safe (easy) to update service:.
I’m personally not changing anything. Everything is backward compatible. If it ain’t broke, don’t fix it. New automations will get these changes, that’s it.
oh well, the vscode warnings are often wrong anyways. IIRC they only work well if you have a basic automation. Anything remotely advanced and it’s red squigglies everywhere.
As the originator of this thread, I absolutely get where @Sir_Goodenough is coming from, but am also mindful of what the moderators are saying.
I have some quite complex, “non-basic” automations and scripts etc and very seldom have red squigglies unless syntax or indentation is wrong. The “if it’s not broken don’t fix it” approach is generally the best but the OCDness of lots of “deprecation” messages will annoy quite a lot of people.
As a 2 year user of HA I bow to the greater knowledge and experience of long time users. After all, isn’t that one of the benefits of this community.
I looked yesterday, they edited the extension so that either syntax is accepted, and not listed as deprecated. I converted mine anyway, will have a YE video about it out Sunday morning my time.