WAPIRZ-1 Motion Sensor no longer detects motion after Z-Wave JS 0.1.15 update

[olddawgpowers]

I have a WAPIRZ-1 Motion Sensor that no longer detects motion after I upgraded to Z-Wave JS 0.1.15. The temperature and battery sensors are still working but no motion detection. 0.1.16 does the same thing. I can go back to 0.1.14 and it works. Any ideas?

[rnormore (Ron)]

I have the same issue, I only moved my zwave devices over today from the old zwave.

[Hackashaq666]

Zwavejas2mqtt addon is working with this device. You can use it with or without mqtt as an alternative to the zwavejs addon.

[olddawgpowers]

From what I have read I think I have to delete Z-Wave JS add on then install Z-Wave JS to MQTT. Do you know if I will have to rename all my entities again?

[rnormore (Ron)]

I would also like to know if we will have to rename all entities?

Thanks!!!

[Hackashaq666]

I followed these instructions from @brandont to backup the device names to switch from zwavejs addon to zwavejs2mqtt addon. Please be sure to save a snapshot of your current configuration, you can always revert to that!
There are more details in the thread linked below.

[Resolved] Zombie official zwave-js addon

You don’t need to backup the whole directory. I just SSH’ed in, went to the homeassistant/.storage directory and did something to the effect of sudo cp core.entity_registry core.entity_registry1 sudo cp core.device_registry core.device_registry1 After uninstalling the integration, restarting, reinstalling the integration (and not checking that use add-on option), I just did the reverse of that cp command and restarted once more. Like I said, it was a mess to fix. Perhaps there might be anothe…

[olddawgpowers]

I can confirm the WAPIRZ-1 works with Z-Wave JS to MQTT. I stopped Z-Wave JS. Installed Z-Wave JS to MQTT. Copied Device Path and netowrk_key from Z-Wave JS to Z-Wave JS to MQTT. Edited .storage/core.config_entries to change “use_addon”: false. Restarted and let it Interview. I had to wakeup some of the battery devices.