While it appears to be true that previous things will continue to work following the significant changes in 2024.8[.1], the same is not true for editing things in the UI. If you have, say, an automation (or perhaps a 100 or so automations…) that make service calls or send notifications, or… then as soon as you change anything in one of those and click save, all of the service related UI entities change to say ‘Unknown’ and from that point onward can only be edited via YAML rather than the more friendly true UI based editor.
Is this really intended? It seems kind of severe. I would have hoped that these entries would get automatically migrated/modifed but to seems they do not. Kind of disappointed/upset as now I have hundreds of things to potentially ‘fix’ so that I can continue to edit them using the full power of the UI.
EDIT: It is even worse than I feared. Although you can re-create the affected items using the UI and they appear then to be fine, even after you Save, if you then navigate away and come back into the automation again the newly created entities also now show as ‘Unknown’. This is very poor; this change should not have been released in this state. What am I supposed to do now?
EDIT2: So, after some while everything now looks and behaves normally. I can only suppose there is some kind of migration process that occurs after the upgrade from 2024.7.x to 2024.8.x and that it takes a while to complete. At least I hope that is the case. In any event it was kind of scary initially. It would have been nice to have a heads up about it…
I will remember this for the future…