Node deviceClass is returning as null

[raman325]

Checklist

• I have read and followed the above instructions

• 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 or the fix did not work.

Describe the issue

A bug in the zwave integration code exposed the fact that in our JSON state dumps from zwave-js-server, many devices are returning deviceClass = null that previously had a valid deviceClass. Is this expected? If not then there may be a bug. It appears this happened in the transition between 12.4.x and 12.5.x but I can't say with certainty. It appears a reinterview may fix it?

Data points:

• ZWave devices changed from switch / light to window cover home-assistant/core#117121
• https://community.home-assistant.io/t/rgbw-show-up-as-covers/727607

PR to fix the HA bug: home-assistant/core#117232

Software versions

Driver (node-zwave-js): 12.5.x

Z-Wave JS UI: N/A

Home Assistant Z-Wave Integration: N/A

Home Assistant Z-Wave JS Addon: N/A

ioBroker.zwave2 Adapter: N/A

If you are using something non-standard, tell us here: ...

Device information

Doesn't appear to be isolated to a singular device

Checklist

• I made sure to provide a driver log on level debug.

• The log includes a re-interview of the problematic device (if applicable).

• The log includes the problematic interaction with the device (if applicable).

• I provided the node ID of the problematic device (if applicable).

Upload Logfile

State dumps from before and after the upgrade:
before.json
after.json

[zwave-js-bot]

👋 Hey @raman325!

It looks like you attached a logfile, but its filename doesn't look like it a driver log that came from Z-Wave JS.

Please double-check that you uploaded the correct logfile. If you did, disregard this comment.

As a reminder, here's how to create one:

• Z-Wave JS UI
• Home Assistant Z-Wave Integration
• ioBroker.zwave2 Adapter