First I would say expect that you will have some devices that just want to be problematic. Personally I had about 9 of 54 devices that didn't fully connect properly. All of them were battery powered devices. Most of those were able to be connected simply by waking them up. For this reason, it is good to know the process to wake your specific devices.
It should also be noted that S2 data gets wiped when changing to ZwaveJS. For that reason you would want to use @jtp10181 SmartStart App to backup and then restore the SmartStart data during this process.
The process I followed was
- Upgrade Hub to 2.4.1.x
- Once that was done I pretty much immediately change to Zwave JS.
- I waited a little while for the hub to settle down and then updated the firmware Zwave firmware. This is good because the firmware that is already loaded on the zwave radio is not the recommended version.
- You will need to wait for probably atleast 24 hours for all of the devices to be interviewed and show as connected to the hub. During this time the devices will be interviewed by the radio and should reconnect. Some battery powered devices seem to have issues.
If a device somehow changes it's security settings then use the below endpoint to re-interview the device. Remember to change the # at the end to the number value shown on the zwave page.
/hub/zwave2/reinterview?node=15
Lastly if you can't get a device to connect I ended up unpairing and repairing the device.
My problem devices were Zen34 Remote Switch devices. I couldn't get them to complete the interview process. I ended up just excluding and including them again. I only have 4 of those so not to big of a deal.
The good news is that you can always go back to Z/IP if things start going really wrong.
