bgoncal
commented
16 hours ago My initial guess is that for some reason your server ID is changing when you update core, if the server ID changes the configuration items don't know what to display because they are looking for the old ID, weirdly that never happened to me, can you please export and send your logs? https://forms.gle/Uoqz127Phx4mMTpS6
iOS device model, version and app version
Model Name: iPhone 14 Pro Software Version: 18.0.1 App version: 2024.9.4 Apple Watch Ultra 2; Software Version 11.0.1
Home Assistant Core Version 2024.10.4
Describe the bug Background: I recently upgraded to an Apple Watch Ultra 2. When I upgraded, I decided to adopt "scripts" for my Watch Configurations; I retired the use of Actions. This was about a month ago. All was good for a while, until I upgraded HA Core (not sure of the upgrade rev at the time). After upgrading, none of my Watch "Configurations" would work. They were there but when you tapped them, they gave an X instead of a Check Mark (Check Mark means its working). Additionally, after refreshing the configurations in the Apple Watch app, the script names changed from Friendly Name to script.XXX name. This aligned as well to what they showed in the iOS companion app watch configuration, too.
Fast forward to last night, I upgraded to 2024.10.4 and again my watch configurations stopped working. Having seen this before, I knew I needed to remove them and re-add them. The act of readding them isn't the end of the world but as noted under expected behavior, I expect them to persist an update. So, effectively, it seems that upgrading core breaks Watch Configurations each time you upgrade. You must remove and re-add them. You don't have to delete the script, just remove the item from configuration and Tap Add Item and reselect the script(s).
Mitigation: Delete the items in Companion App/Watch/Configuration section and re-add them. Once you re-add them they seem to work fine until the next Core update.
To Reproduce Upgrade Core to any new version
Expected behavior Upgrade Core and not have to delete and re-add the "script" items in the Watch Configuration section of the companion app.
Screenshots
Additional context NOTE: The items in the screenshots are out of order. The point I'm trying to make is that the core update breaks something. The order is irrelevant since you must re-add them after the core update to restore functionality.