I just did a test migration to Z-Wave 1.0.1 following these instructions, which I realize might not be the final version.
I don’t know if this is helpful, but I took some notes about a few things I found confusing.
Overall, it was pretty smooth. Personally, I prefer configuring z-wave in ZUI and I’m not quite clear if that’s possible with the core app now. Will the old ZUI app still be available?
Migration Notes:
I installed HAOS on a spare Rpi4 and then I installed the (old) community ZUI and configured a controller and a device.
Should it just be a link to the raw script? The Advanced SSH app has wget. Would it be easier in the step where you ssh into /tmp to then to have an wget command to copy-and-paste to download the script?
I feel like this could be challenging w/o some examples. How many people migrating have ever ssh’d into HA?
Should this explain don’t check if using the GPIO module, or maybe just remove this and link to the next step in the instructions?
[migrate] You can now reconfigure the Z-Wave integration as follows:
[migrate] If using a USB or TCP based controller:
[migrate] - CHECK 'Use the Z-Wave Supervisor app'
[migrate] Otherwise:
[migrate] - DO NOT check 'Use the Supervisor app'
[migrate] - URL: ws://core-zwave-js:3000
By the way, on a more general note, not related to the migration.
I always find this dialog confusing. If you click on “Recommended installation” HA will immediately start downloading the core app if not already done.
Might be a little helpful, but you also need to get the store backup zip file into /tmp as well. In my case, I have the /share folder samba mounted to my PC, so I downloaded both the store backup files and the shell script and put them in the /share folder, and from there in the Adv SSH & Web Terminal has access to the /share folder so I next “cp”'d these two files into /tmp dir of the Adv SSH &Web Terminal.
BTW I did just now try out your idea of wget. The following worked for me in Adv SSH & Web Terminal wget "https://gist.githubusercontent.com/AlCalzone/eb0947a39a3ff91c053f259f0ac4efc3/raw/69494c1671a04ba81b5ffb6060037ccf02a57fb2/migrate_to_zwave_js_app.sh"
For what its worth, I didn’t get that dialog. Is that dialog from the ZWA-2 Integration? If it is, then it would explain why I didn’t get it as I don’t have a ZWA-2.
It’s what you get the first time you add the integration or if you “Add hub” later.
It just confused me (which isn’t hard) a few times early on. Of course you want the Recommended way!
I haven’t thought about it but seems like a if you do not have the app installed is could say “Click continue to install the Z-wave app and configure it.” but also have an “Advanced” or “Manual” option. And if the core app is installed then only offer the Advanced option. Or something like that.
Hmm… in this situation, the integration is already there, and according to the instructions one is not Adding a Hub (meaning adding a second instance), but instead “Reconfiguring” the existing instance.
You are right. Sorry. It was more of a side note. Just to test, I first clicked on the z-wave integration and saw that dialog and pasted it in my post. I clicked Recommended and away it went installing the core app. Unrelated to migration but something I find a bit confusing.
I’ll also add, that there is a slight usage difference I stumbled across between the UI for the original ZWaveJS-UI AddOn/app and the UI for the new ZWaveJS AddOn/app.
The Keys and port were configured in the UI in the former, but in the latter, they are not in the UI but instead are in the AddOn/App’s config tab.
