core: Zwave-JS Migration Wizard Doesn't Appear to Work
The problem
Attempting to use the the Zwave-JS Migration Wizard doesn’t appear to migrate any of the devices or entities names and doesn’t appear to include all the nodes.
Per this discussion it seems like it happening to others as well.
System specs: Core version: core-2021.11.0 Operating System: Home Assistant OS 6.6 supervisor-2021.10.8 running on Home Assistant Blue Adapter: AEON Labs ZW090 Z-Stick Gen5 US
On this step I get no info on the nodes, the only node that has any info is the zwave adapter’s info, all others are blank:
And when completed there are missing node:
When process gets finalized all names are reverted to a default name. Have tried multiple times with the same results over all versions released since code-2021-10-0.
What version of Home Assistant Core has the issue?
core-2021.11.0
What was the last working version of Home Assistant Core?
introduced and also not working in core-2021.10.0
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Zwave-JS Migration Wizard
Link to integration documentation on our website
https://github.com/home-assistant/core/blob/dev/homeassistant/components/zwave_js/migrate.py
Example YAML snippet
No response
Anything in the logs that might be useful for us?
There doesn't seem to be anything in the logs related to the migration at all.
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 6
- Comments: 30 (18 by maintainers)
We finally yesterday managed to find the two bugs that was causing the migration wizard to not give feedback about non ready devices in Z-Wave JS. The fixes will be part of release core-2022.3.0.
A workaround is to just make sure that all devices are ready and have completed their interview in Z-Wave JS before finishing the migration wizard. Usually devices that stay non ready for a longer time are sleeping and can be woken up manually to faster complete the interview.
I have been able to reproduce the issue and we’re investigating how to solve it.
debug logs and zwave network dump here:
zwave_js.log
zwave_js_dump.json.txt
Thank you.
Sounds good, thank you.
Person note: I really enjoyed your presentation last weekend on the State of the Open House (pretty sure that was you), so thank you for that also!
Here is the debug log. Note that the error that occurred on line 11 of the log never happened in previous attempts. I tried the migration twice today and it happened both times and came with the UI error from the attached screenshot. After I clicked close on the UI error there was an option to continue in the main window. After doing that it proceeded to not succeed in the same manner as previous attempts.
home-assistant.log
Attaching the legacy_zwave_migration files that appear to get generated in the .storage directory during the migration, in case they are helpful.
zwave_js.legacy_zwave_migration.txt zwave.legacy_zwave_migration.txt
Thanks so much. I migrated to 0.1.47 of zwave-js and its working fine now, talk about good timing 😃