forum

Hello, I had to run a re-interview for my window sensor (Devolo Door/Window Contact) because I changed its location. Unfortunately, it now always stops at 94% and shows that the interview for the security command class was not performed. Despite trying several times and manually waking up the device, it remains at 94%. I am currently running software version v3.2.2.

In the forum I found different solutions, that one should execute the following URLs, but that didn't help either.

http://IP:8083/JS/Run/zway.devices[numb ... ityLevel=0
http://IP:8083/JS/Run/zway.devices[numb ... ntroller=0

Does anyone have any ideas what else I can do to get the sensor working again?

Unfortunately, there are many users who experience device interview failures using Z-Way software. My experience is that the Zwavejs2Mqtt Z-Wave controller software (https://zwave-js.github.io/zwavejs2mqtt) is much better at completing the interview process successfully. Until the Z-Way team updates their software to work as well as Zwavejs2Mqtt, the only option is to manually tell Z-Way the interview was successful. Note that the workaround generally does not apply to devices that require a secure inclusion. I suggest trying the following:

1. Exclude the device.
2. Include the device without security.
3. Let the interview process finish, to whatever extent it does (e.g., 94%).
4. If the interview for the Security command class fails for device ID XX fails, run the following (replace USER, PASSWORD and XX):
curl -u USER:PASSWORD --globoff 'http: //127.0.0.1:8083/JS/Run/zway.devices[XX].instances[0].Security.data.interviewDone=true'
5. If the interview fails for a different command class (e.g., Version), replace "Security" with the name of the command class.

To help the Z-Way team improve their software, I suggest sending @PoltoS the z-way-server log file where the interview failed (nominally on linux, /var/log/z-way-server.log) and the Zwavejs2Mqtt Z-Wave message log file (nominally if installed via the snap method, /var/snap/zwavejs2mqtt/current/zwavejs_current.log). From what I can tell in comparing log files, there are significant differences in message transmission timing and sequence. Ideally, the Z-Way team has some Z-Wave devices where the Z-Way interview process fails and they install Zwavejs2Mqtt so that they can directly observe/develop/test what changes are needed to the Z-Way interview process.

Hello Seattleneil,

thank you very much for your help. This worked. Now I was able to get my two contact sensors fully connected to the network again.

Thanks again!