After spending several hours trying to migrate from the legacy Z-Wave integration to the new Z-Wave JS to MQTT add-on, I finally got it working! Here’s my journey and some tips for anyone else going through this process.The Issue: When I first tried to start the Z-Wave JS to MQTT add-on, it wouldn’t launch. The logs showed that the add-on was stuck during initialization, and I couldn’t access the web UI. After checking the logs repeatedly, I noticed that the add-on was trying to start both NGinx and the Z-Wave JS service simultaneously, which seemed to be causing a conflict.What I Tried: 1. Disabling Legacy Integrations: I made sure the legacy Z-Wave integration was completely disabled in Home Assistant. 2. Clearing Old Data: I deleted the old Z-Wave configuration files to ensure there was no leftover data causing issues. 3. Checking Supervisor Logs: I reviewed the supervisor logs to ensure there were no underlying issues with Docker or the add-on itself. The Solution: After several failed attempts, I realized that the add-on might need a fresh start. I decided to restart my entire Home Assistant supervisor. This simple step finally allowed the add-on to initialize properly. Tips for Others: - Backup First: Always back up your configuration before making changes. - Check Logs Thoroughly: The logs are your best friend during troubleshooting. - Restart When Stuck: Sometimes, a full restart can resolve hidden issues. Final Thoughts: The migration process was a bit challenging, but it’s worth it for the improved functionality and stability of the Z-Wave JS to MQTT add-on. My devices are now communicating seamlessly, and I’m excited to explore all the new features this integration offers. If anyone else is struggling with this migration, feel free to reach out! I’m happy to share what I learned along the way.