Reinterrogate existing device in ZwaveJS?

Is there a way to Reinterrogate an existing device without excluding it and re-including it? I have a multisensor which used to report its motion on a motion-sensor on/off entity and a recent update seems to have moved it to a basic entity which has 0 or 255 as its values. Was thinking possibly an update changed how some of the multisensor values are viewed and I need to get it updated.

What is the device? Do you have any logs showing the basic values being received?

If you’re using the official addon, there’s currently no way to do a re-interview aside from manually deleting the cache files (need to access the container details) or completely uninstalling it. Those aren’t very convenient methods though. Re-including despite it’s annoyances is probably easier than those choices.

If you’re using zwavejs2mqtt instead, you can do it through the node control panel in the Advanced dialog.

You can also issue the re-interview command directly to the zwave-js-server websocket API (need to expose port 3000) or via the HA websocket API. Neither are easy to explain or perform, but it’s possible. It might be functionality added to the UI in the future.

It is a Zipato Z-Wave Multi-Sensor Dual - ZP3102 and I am using the latest ZwaveJS update. It has two entities (that are relevant to this conversation) “Motion Sensor: Motion Detected” and “Motion Sensor: Basic”. The “Motion Detected” entity worked until a couple of releases ago. The “Basic” entity was disabled; I enabled it and am seeing values of 0 when no motion and 255 when motion. It appears something is slightly off in the configuration.

Unfortunately, it sounds like the best option is to pry the motion sensor off the wall again to re-include it. (the inclusion button is on the back and it is mounted with adhesive tape to the wall)

This device was fixed in v7.2.4, 4 days ago. Are you sure you’re using that version? I don’t think the fix requires a re-interview.

Thanks, I usually keep up-to-date with the latest patch. I was on 2021.4.5 which was released on April 16th. After your comment, I went ahead and upgraded to 2021.4.6 which was released on April 19th but the release notes notes didn’t mention anything about ZwaveJS. I should have taken a look at which version the integration was on before I upgraded… but I am now running v7.2.4 and the motion detector works correctly now. I just was not patient enough; I thought it was a config issue on my side since it was several releases without it being fixed.

Thanks!!!

FYI, the version of HA does not determine the version of Z-Wave JS. If you are using any of the addons, those will determine the version.