Alexa no longer able to trigger Scripts

Yesterday I started on my disaster recovery plan by building a duplicate Raspberry Pi 5 with HA and restored my most recent backup. The original HA was also running. Both complained that they were using the same instance ID so I changed the instance ID on the standby instance and then powered it down. Everything seemed to be running ok until I tried to trigger a script or control a device (connected through HA & Nabu Casa) using Alexa. She said that the device was not responding, so I disabled Alexa and re-enabled it under Settings/Voice assistants. At this point Alexa recognised the devices but they then showed up as duplicates, with the originals no longer functioning, so I deleted those and was able to control devices.

What I cannot get to work is routines that run scripts. The scripts exposed to Alexa are recognised in Alexa and I can re-add them to a routine, but they just do not work. I don’t get an error from Alexa, just nothing happens. I again disabled and enabled the Alexa voice assistant integration and the scenes (Alexa terminology for scenes exposed by HA) were discovered again, but did not show up as duplicates. I also tried discovering scenes and discovering devices, but nothing works. When I try ‘Alexa, turn on [script name]’ it says that [script name] is not responding. I also tried not exposing it and then re-exposing it. Each time I did that, it triggers a notification from Alexa that the scene has been added.

I don’t understand why all this is happening (admittedly, I just updated the HA 2025.12, so it may related to that).

I suppose I could disable and re-enable the HA skill in Alexa, but since it is able to see the scripts I doubt that would help.

Ok, I just did a full reboot of HA and its now working. I’d still welcome any ideas why this happened.*

I had to fire up my standby instance again today and the exact same thing happened, so its defiantly caused by this. Rebooting my main instance after I shut down the standby instance fixed the issue.

My guess is that when HA starts it grabs the alexa hooks, so when I started my standby it hijacked the alexa devices and when I shut down that instance these were orphaned. Restarting my main instance grabbed those ‘hooks’ back again.

I hope this may be helpful to someone someday (maybe even me!)