Closed scstraus closed 2 years ago
zwave documentation zwave source (message by IssueLinks)
@MartinHjelmare Any chance I could get you to take a look?
You need to wait until the devices have been interviewed by Z-Wave JS and are ready before completing the migration wizard. Non ready devices won't be migrated.
Sleeping devices won't be ready until they have woken up and the interview can be completed. You can normally manually wake a device up by pressing a button on the device. How to wake a device up is device specific.
I tried pressing the buttons on the devices but it did nothing. Can I leave the migration tool running for like 24 hours and have it gather the details as devices are being interviewed?
Yes, you should be able to leave the page open.
See my comment here, there does seem to be a documentation issue and many others frustrated by "failing" migrations: https://community.home-assistant.io/t/migrating-to-z-wave-js-broke-my-whole-z-wave-network-and-db-discussion-and-suggestions/376388/18?u=bs87
I can confirm the same behavior for me as well migrating from Zwave 1.4 to Zwave JS. No nodes show as able to migrate. I had to restore backup and will try again and wait a while for nodes to be interviewed and report back. Though, this waiting step is not mentioned in the wizard nor the documentation so I agree there should probably be an update to one or both.
The wizard explicitly calls out each device that isn't ready. Eg from the top post above:
Device Node 4 is not ready yet! For the best result, wake the device up if it is battery powered and wait for this device to become ready.
Update on this, I left the migrate window open while waiting for all my nodes to be interviewed. It was updating live for a while but eventually stopped updating the status and timed out. However, I watched status in another window and once all nodes were alive (some I had to intervene and wake manually), I clicked Migrate and it seemed to work for about 90% of nodes and entities. Just had to clean up a few things.
Not sure if there is interest in fixing the page timing out, but otherwise the migration seemed to go pretty well.
Great information! How did you watch the status in another window?
Great information! How did you watch the status in another window?
I just opened the Z-Wave JS config page in another tab and periodically refreshed that until all device reported ready. Then went back to the migration wizard tab and clicked migrate.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
The problem
This was open in a previous issue #59119 , and though the thought was that it had been fixed, it still doesn't work at all for me. This is a major problem since this will be the last version which supports the old zwave integration and I was hoping there would at least be some hope for migration, because frankly I'm not sure I will ever be able to do this manually. I'm at the point where I just don't want to bother with this any more.
What version of Home Assistant Core has the issue?
2022.3.7
What was the last working version of Home Assistant Core?
Never worked.
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
Zwave (deprecated)
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zwave/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Here are the logs:
zwave_js.legacy_zwave_migration.txt zwave.legacy_zwave_migration.txt
This is the text I got after the migration wizard finished (page was too long to screenshot)- it apparently only migrated 1 device.
Additional information
Here's what I get when I try to do the migration. Initially it told me about 30-40% of my devices couldn't be woken. I went around trying to wake them but it didn't do anything so I continued. But after I continued, it ended up not migrating really any of the details of even the devices it could wake over:
.
I inserted the log I had from the integration above. and this is what I ended up with at the end.
Any chance to get this fixed?