Followed the steps outlined in the guides. The spokens list shows up under my new device, and the old 994 has been removed. Since it was z-wave and all the nodes changed names in the migration, I knew I was going to have to remap them.

I wanted to confirm others have this same issue, I cannot simply remap the "My Device" for each spoken, it is grayed out and will not allow to change...

So, I have to recreate every entry from scratch?

Different node names usually means needing to redo things. Alexa or Google home can't know what old name = the new name.

Edited 12 hours ago12 hr by Guy Lavoie

Guy, maybe I stated my question poorly.

If you look at the screenshot, the spoken is there, with the room, type, etc. The only thing wrong is "My Device". Why can't I just update the "My Device" field to point to the correct device. It is not editable.

It seems like I should be able to update "My Device" to the new name.

I have to delete the spoken completely, set the room, type in the spokens/alternatives, and select my device.

There is ZERO point in migrating if you have to delete everything and redo it... I guess its a z-wave problem only, as Insteon nodes don't seem to change.

Lastly, the post was to ask others if they had the same issue migrating Z-wave or if I missed as step that might help others.

Thing is, when you create a new spoken, the first thing you select is the node. It's the root pointer that everything else is related to. That's probably why it can't be changed.

Great, that information helped!

I created a brand new spoken entry, and pushed it to Google. Confirmed it worked. Went back to the new spoken entry to see if updating the "My Device" was possible and it is NOT. Which means I did not screw up the spokens migration process, and this problem will happen to anyone migrating Z-wave devices.

So, my suggestion to anyone migrating Z-wave to Google Home, would be to download your spoken list, and skip the "Migrate to" step. It fails and you will need to delete all spokens and re-enter them.