Legacy actions, and how to proceed?

[golles]

In 2024.12 Actions was renamed to (Legacy) iOS Actions (as in #3251)

I did hear/read something about this before, but what's next? What are we supposed to do now? I can't seem to find anything about that.
Eg. https://companion.home-assistant.io/docs/core/actions and the release notes don't mention anything about it.

I've got a few actions defined in Yaml that are used on a daily base, so I'd like to know what I should be doing to stop using legacy features.

Thanks!

[bgoncal]

For widgets you now have scripts widget as replacement and also “widget builder” (which will bring more flexibility) is under development.

For Apple Watch you can also use scripts and scenes as replacement.

Same for CarPlay

[bgoncal]

And just to be clear, no plans to remove iOS Actions for now, the change was just to make clear that this is not the recommended way anymore.

[golles]

Is the plan that widgets will completely replace actions?

[bgoncal]

iOS actions can be triggered in many ways as described above. Widgets is one of the ways.

You can trigger a script widget instead now.

[kristian]

@bgoncal I now switched to using a script & the script widget instead, as you suggested. Worked just fine, thanks for the tip!

Quick question: is it still possible to customize the icon & background color of the iOS widget, when using scripts instead of the legacy actions? Thanks!

[bgoncal]

@kristian not possible yet, keep an eye on the app updates, a "widget builder" is coming

[kristian]

Thanks for the quick reply @bgoncal! Have a good one 👍

[kristian]

To be honest, I was also very confused seing the „Legacy“ (or in German „Veraltet“) in the app. It took me quite some minutes & two Git blames to get here. I have no issues with switching to Widgets or whatever, but I think it would make sense to add a note to the app / menu item, as well as to the actions documentation, in order to clarify that widgets may be used as a (non-legacy) replacement & to make it clear to end-users that there is no immediate need of migrating, as there are, as you said, no plans of deprecating the „legacy“ actions.

In my oppinion „legacy“, as well as the German translstion „veraltet“, insist a form of urgency. Maybe choosing a word like „classic“ would have been the better choice, if there is no intend of deprecating them in near future anyways. „Classic“ would make it clearer from a terminology point of view, that the feature is still perfectly fine to use. Also the term indicates that there is a newer feature that is more powerful.

[bgoncal]

Thanks for the feedback!

[kristian]

Made an edit to my comment, to bring my point with „classic“ better across (sorry it overlapped with your answer).