Unknown Manufacturer/Product/Product Code after upgrade

[renatohtpc]

After upgrading from version 9.3.2 to 9.5 (and later 9.6) I noticed that several of my devices are now showing as "Unknow" as depicted from the attached. I was able to fix a few by removing them and re-adding them.

After. Trying to reinterview the affected devices did not help.

I am running the software inside a docker. Here is the script:

`root@IOT:~/docker_compose/zwavejs2mqtt# more docker-compose.yml
version: '3.7'
services:
zwavejs2mqtt:
container_name: zwavejs2mqtt
image: zwavejs/zwavejs2mqtt:latest
restart: always
tty: true
stop_signal: SIGINT
environment:
- SESSION_SECRET=XXXXXXXXXXXXXXXX
- ZWAVEJS_EXTERNAL_CONFIG=/usr/src/app/store/.config-db
# Uncomment if you want logs time and dates to match your timezone instead of UTC
# Available at https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
- TZ=America/New_York
networks:
- zwave
devices:
# Do not use /dev/ttyUSBX serial devices, as those mappings can change over time.
# Instead, use the /dev/serial/by-id/X serial device for your Z-Wave stick.
- '/dev/serial/by-id/usb-Zooz_800_Z-Wave_Stick_533D004242-if00:/dev/zwave'
volumes:
#- ./zwave-config:/usr/src/app/store
- $PWD/store:/usr/src/app/store
ports:
- '8091:8091' # port for web interface
- '3005:3000' # port for Z-Wave JS websocket server
networks:
zwave:
#volumes:

zwave-config:

name: zwave-config`

Also, here is the output of the 'ls' command for the USB stick:

root@IOT:~/docker_compose/zwavejs2mqtt# ls -al /dev/serial/by-id/usb-Zooz_800_Z-Wave_Stick_533D004242-if00 lrwxrwxrwx 1 root root 13 Dec 2 21:36 /dev/serial/by-id/usb-Zooz_800_Z-Wave_Stick_533D004242-if00 -> ../../ttyACM0

I am also attaching the log file (large)

zwavejs_2023-12-19.log

Is removing/adding the only solution?

Thank you for your help.

Renato

[robertsLando]

Fist I'm not sure volume is setup correctly: - $PWD/store:/usr/src/app/store

If you check your local folder directory (the one next to the docker-compose file) do you see something inside it?

Also did you tried to re-interview unknown devices? You can easily do that by pressing on Advanced button on an expanded node row

[renatohtpc]

Good morning. The docker-compose file exists within the /root/docker_compose/zwavejs2mqtt directory.

The /root/docker_compose/zwavejs2mqtt/store does exist and contains the following:

root@IOT:~/docker_compose/zwavejs2mqtt/store# ls -al /root/docker_compose/zwavejs2mqtt/store
total 492
drwxr-xr-x 14 root root   4096 Dec 20 08:54 .
drwxr-xr-x  3 root root   4096 Dec  2 21:54 ..
-rw-r--r--  1 root root    544 May 28  2023 c145e9a3.jsonl
drwxr-xr-x  2 root root   4096 May 29  2023 c145e9a3.jsonl.lock
-rw-r--r--  1 root root   1106 May 28  2023 c145e9a3.metadata.jsonl
drwxr-xr-x  2 root root   4096 May 29  2023 c145e9a3.metadata.jsonl.lock
-rw-r--r--  1 root root    829 May 28  2023 c145e9a3.values.jsonl
drwxr-xr-x  2 root root   4096 May 29  2023 c145e9a3.values.jsonl.lock
drwxr-xr-x  2 root root   4096 Nov 28  2022 config
drwxr-xr-x  3 root root   4096 Dec 19 15:06 .config-db
drwxr-xr-x  3 root root   4096 Dec 14 08:01 .config-db_old
-rw-r--r--  1 root root  29701 Dec 20 08:55 d133c078.jsonl
drwxr-xr-x  2 root root   4096 Dec 20 08:57 d133c078.jsonl.lock
-rw-r--r--  1 root root 302511 Dec 20 08:34 d133c078.metadata.jsonl
drwxr-xr-x  2 root root   4096 Dec 20 08:57 d133c078.metadata.jsonl.lock
-rw-r--r--  1 root root  75324 Dec 20 08:34 d133c078.values.jsonl
drwxr-xr-x  2 root root   4096 Dec 20 08:57 d133c078.values.jsonl.lock
drwxr-xr-x  2 root root  12288 Dec 20 00:06 logs
-rw-r--r--  1 root root    691 Dec  4 08:50 nodes.json
drwxr-xr-x  2 root root   4096 Nov 28  2022 sessions
-rw-r--r--  1 root root   1283 Dec 14 18:15 settings.json
drwxr-xr-x  2 root root   4096 Nov 28  2022 snippets
-rw-r--r--  1 root root    186 Nov 28  2022 users.json

Here is a screenshot before the re-interview:

and a screenshot after:

As you can see, nothing changes.

Thank you

Renato

[robertsLando]

Please make a driver log, loglevel debug and attach it here as a file (drag & drop into the text field).

[renatohtpc]

Here it is.
zwavejs_2023-12-20.log

Thank you

[robertsLando]

I see a ton of:

2023-12-20T05:05:59.664Z DRIVER « [Node 029] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -83 dBm
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: No security class granted

Did you changed your security keys for some reason or maybe them are not set?

[robertsLando]

@renatohtpc them are private, I suggest you to don't upload them

[renatohtpc]

Ops. Would it be possible for me to retrieve the keys from an older log or perhaps a device which a re-added manually after this problem started?

Thanks

[robertsLando]

Wait a moment, maybe @AlCalzone can help you. This problem should be debugged on driver side, I moved the issue to his repo but he is actually on parental leave so he may be slow to respond

[AlCalzone]

Sorry, this slipped through. Is it still an issue?

[zwave-js-assistant]

This issue has not seen any recent activity and was marked as "stale 💤".
Closing for housekeeping purposes... 🧹

Feel free to reopen if the issue persists.