node-zwave-js: Unknown manufacturer, 0xXXXX, Unknown product

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?

NO, my problem is NOT within Home Assistant or the ZWave JS integration

Is your problem within ZWaveJS2MQTT?

YES, BUT a ZWaveJS2MQTT developer has told me to come here

Checklist

• I have checked the troubleshooting section and my problem is not described there.

• I have read the changelog and my problem was not mentioned there.

Describe the bug

What causes the bug? Not sure what is causing it

What do you observe? Devices keep going to “Unknown manufacturer, 0xXXXX, Unknown product 0xXXXX” ? This is the third time it’s happened, very annoying. Everything in HA fails when this happens. I end up having to remove them and add them again to get them to work. zWave stick info HUSBZB-1 (Silicon Labs Z-Wave 500 Series Controller ACC-UZB3)

What did you expect to happen? Once added I expect them to stay remembered and not go to unknown

Steps to reproduce the behavior:

1. Add zWave devices
2. Wait for them to turn up as unknown (not specific time)
3. I do reboot my HA device (NUC) daily
4. Maybe rebooting will make it repro

Device information

Manufacturer: Model name: Node ID in your network:

How are you using node-zwave-js?

• zwavejs2mqtt Docker image (latest)
• zwavejs2mqtt Docker image (dev)
• zwavejs2mqtt Docker manually built (please specify branches)
• ioBroker.zwave2 adapter (please specify version)
• HomeAssistant zwave_js integration (please specify version)
• pkg
• node-red-contrib-zwave-js (please specify version, double click node to find out)
• Manually built from GitHub (please specify branch)
• Other (please describe)

Which branches or versions?

snap install

store-url: https://snapcraft.io/zwavejs2mqtt installed: v6.2.0 (315) 137MB

snap-id: k26XpW9UYHL1HNh20isi5MHoazqHZ8br tracking: latest/edge refresh-date: yesterday at 05:25 PST

zwavejs2mqtt: 6.2.0.fa6b2ab zwave-js: 8.9.3-0-pr-4011-940427a home id: 4276191763 home hex: 0xfee18213

Did you change anything?

no

If yes, what did you change?

No response

Did this work before?

Yes (please describe)

If yes, where did it work?

Yes, it works for a while before this issue appears

Attach Driver Logfile

zwavejs_2022-01-03.log