As a long-time user of ZWave technology, I’ve recently undertaken a significant project to migrate my ZWave network from an older ZWave.me UZB1 stick to a more modern ZWA-2 controller. This process has been both enlightening and frustrating, but I’m happy to share my experiences and solutions to common pitfalls.
The Migration Journey
My setup is a bit unique—I’m running Home Assistant on a virtual machine hosted on a Synology NAS. This added an extra layer of complexity to the migration process. Initially, I struggled with firmware upgrades and NVM backups, which are critical steps for preserving network information. The ZWave.me firmware was outdated, and without proper NVM backup, the migration would have been impossible.
Firmware Upgrade
I used Z-Way software to update my UZB1 stick to a compatible firmware version. This tool simplified the process by automatically determining the necessary updates. Upgrading from SDK <6.61 to SDK 6.81 was a crucial step that enabled NVM backup functionality.
NVM Backup Challenges
Saving the NVM proved to be the most challenging part. Many tools either failed or produced incompatible backups. However, using Aeotec’s backup tool for their Gen5 sticks worked perfectly, even though my stick was a ZWave.me variant. This step was essential for ensuring that my network configuration and device associations were preserved.
Restoring on ZWA-2
Once the NVM was safely backed up, restoring it to the new ZWA-2 controller was straightforward. The official documentation from Nabu Casa was invaluable here. I recommend thoroughly reviewing their guides before starting the migration process.
Common Issues and Solutions
-
Time Zone Mismatch
If you’re experiencing time-related discrepancies in your UI, double-check your system and UI time zone settings. A quicktimedatectl statuscommand in the terminal can reveal if there’s a mismatch. Ensuring both your system and UI are set to the correct time zone (e.g., US/Eastern) can resolve seemingly strange timing issues. -
Automation Rule Not Saving
When creating new rules in the Basic Rules app, it’s easy to feel frustrated if the rules don’t appear as expected. The key step I often see overlooked is verifying the rule’s existence in the correct section of the UI. If you’re still having trouble, try restarting the Home Assistant core or checking the logs for any errors. -
Unexpected Device Behavior
Devices occasionally act unpredictably, especially after a major network change. If you notice devices behaving oddly, try resetting their associations or performing a soft reset by unplugging them momentarily.
Lessons Learned
- Documentation is Your Friend: Always refer to official documentation before making significant changes.
- Backup Early and Often: Whether it’s NVM backups or configuration files, having backups can save hours of troubleshooting.
- Community Support: Don’t hesitate to reach out to forums like this one if you’re stuck. The community is incredibly helpful and willing to share their expertise.
If anyone has specific questions about their ZWave migration or is facing similar issues, feel free to reach out! I’d be happy to provide more detailed guidance or troubleshoot specific scenarios.
Happy automating! ![]()