ZWave devices changed from switch / light to window cover

[spikenheimer]

The problem

concurrent to either an upgrade from 2024.4.4 to 2024.5.2 all 57 of my leviton z-wave dimmer switches, various Aeotec and Minostan (not all) switched plugs and my 3 Fibaro RGBW controllers all got switched from light devices to window / covers in HA. zwaveJS still shows them correctly, and the resolution (at least temporarily bc it seems to have reset itself in the last 8 hours) was to in HA go into the wave device and ask for a ZWave Re-Interview. once that completed i could delete the cover entity and the light entity returned.

What version of Home Assistant Core has the issue?

core-2024.5.2

What was the last working version of Home Assistant Core?

core-2024.4.4

What type of installation are you running?

Home Assistant Core

Integration causing the issue

Z-Wave JS

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zwave_js/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zwave_js can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zwave_js Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

zwave_js documentation
zwave_js source
_{^{(message by IssueLinks)}}

[markfrancisonly]

Major loss of functionality in my home assistant with 20+ devices reporting configuration file changed under repair. All lights changed to covers. Zwavejs device database appears to have bad interview data? Reinterviewing all nodes results in covers, individually interviewing a device corrects the problem ....

zwave-js-ui: 9.10.2.68fdf4d
zwave-js: 12.5.2

[raman325]

please provide a diagnostics dump of a device that has the correct entities and a dump of one that does not so that we can try to find the difference

[dawiinci]

Same happened here after update from 2024.5.1 to 2024.5.2. Going back bo 2024.5.0 doesn't resolve this issue.

Reinterviewing in zwavejs2mqtt fixes the issue - so my guess is that this is not an HA issue.

For me it might be coincidental with a Z2M update.

[spikenheimer]

zwave_js-b995ecd3f664ce2a03a3e5682581d9b6-Bar Display Cases-0b77ec3a843e082d838ea0eadcd63f48-2.json
zwave_js-b995ecd3f664ce2a03a3e5682581d9b6-Bar Display Cases-0b77ec3a843e082d838ea0eadcd63f48.json

here are both - the -2 file is the dump as a light device as should be.

[kpine]

@spikenheimer Thanks for the diagnostics. The existence of the cover entity in HA is explained now. There are at least two bugs here, one is in HA with regards to how the entities are discovered, the second is potentially in the Z-Wave JS driver. The latter needs more investigation.

The source of the problem is the value device class property that HA receives.

Good:

      "deviceClass": {
        "basic": {
          "key": 4,
          "label": "Routing Slave"
        },
        "generic": {
          "key": 17,
          "label": "Multilevel Switch"
        },
        "specific": {
          "key": 1,
          "label": "Multilevel Power Switch"
        },

Bad:

"deviceClass": null,

The bad case has never occurred before, so it wasn't being checked.

[AlCalzone]

This is a bug in the driver, where the device class gets unintentionally deleted. Fix is up at zwave-js/node-zwave-js#6840, and I'll push a hotfix ASAP.

Edit: 12.7.0 is building now.

[AlCalzone]

@raman325 @MartinHjelmare do we need a repair to re-interview the device in this case? Device class shouldn't be undefined unless the node is new and waiting to be interviewed.