some ZWave devices have reset back to their generic names and entity ids.

COCottonwood commented 2 years ago

The problem

Has anyone reported issues with ZWave JS since the latest update?

I updated last night (10Jan2022) and at 3:55am Eastern on 11Jan all of my ZWave devices became unavailable. They reconnected 30 seconds later. Now when I got home after work today, I noticed all of my "ge_quick_fit_smart_in_wall_paddle_switch" switches that I have listed are no longer in my Dashboard. I saw another post on reddit/homeassistant from PDXSCARGuy that said he had the same problem today, losing all of his "ge_quick_fit_smart_in_wall_paddle_switch" devices listed in his dashboard.

All of their automations are still there, but these devices have reset back to their generic names and entity ids. I can still find them as a device, but under their generic name. I had to re-enable the entity so I could control it, and rename them back to the "friendly" name so that the automations & scripts could see them.

These are GE/JASCO 46201 / ZW4008 devices.

What version of Home Assistant Core has the issue?

core-2021.12.9

What was the last working version of Home Assistant Core?

core-2021.12.8

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZWave JS

Link to integration documentation on our website

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

Example YAML snippet

N/A

Anything in the logs that might be useful for us?

"XXXXX" became unavailable entry

Additional information

No response

probot-home-assistant[bot] commented 2 years ago

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! _{^{(message by CodeOwnersMention)}}

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

COCottonwood commented 2 years ago

Here is the time when all devices became unavailable... (not sure if this helps as this occurs anytime the zwave listing in HA gets updated) ZWave Unavailable

candrea77 commented 2 years ago

Don't exactly know if it is related. Yesterday I've update to 2021.12.9

I'm running zwavejs2mqtt on docker in a dedicated container and I'm using zwavejs integration configured to use the WebSocket connection to the container.

Today some zwave devices are not available anymore when I want to use automation .... here you are an example.

This is the yaml code of an automation action created before core-2021.12.9

type: turn_off
device_id: 1085c7efa9bc9b869c546cefeff1d6fc
entity_id: switch.luce_bagno_camera
domain: switch

This is the Editor view : LuceCamera

This is a different zwave device working correctly ... yaml code :

type: turn_off
device_id: 4f1301f6a867f351bc9e718271b08d22
entity_id: switch.cucina_luce_ventola
domain: switch

And visual editor : LuceCucina

BTW : I'm unable to create new action on switch.luce_bagno_camera using the visual editor, but the old already created are working and if I create new one with YAML they work correctly.

raman325 commented 2 years ago

Don't exactly know if it is related. Yesterday I've update to 2021.12.9

I'm running zwavejs2mqtt on docker in a dedicated container and I'm using zwavejs integration configured to use the WebSocket connection to the container.

Today some zwave devices are not available anymore when I want to use automation .... here you are an example.

This is the yaml code of an automation action created before core-2021.12.9
type: turn_off
device_id: 1085c7efa9bc9b869c546cefeff1d6fc
entity_id: switch.luce_bagno_camera
domain: switch
This is the Editor view :

This is a different zwave device working correctly ... yaml code :
type: turn_off
device_id: 4f1301f6a867f351bc9e718271b08d22
entity_id: switch.cucina_luce_ventola
domain: switch
And visual editor :

BTW : I'm unable to create new action on switch.luce_bagno_camera using the visual editor, but the old already created are working and if I create new one with YAML they work correctly.

Your issue is separate, probably the same as #63331

raman325 commented 2 years ago

Here is the time when all devices became unavailable... (not sure if this helps as this occurs anytime the zwave listing in HA gets updated)

Best guess is that the cache got wiped because of the update, and because of a bug (fixed in https://github.com/home-assistant/core/pull/59964), all of your original devices and entities were removed. This fix is coming in 2022.2 but unless you have a backup of the old addon (which would contain the old cache file), there's no fix that will restore your devices and entities unfortunately

raman325 commented 2 years ago

I've requested a patch release to add this fix, let's see what happens

decompil3d commented 2 years ago

This exact thing happened to one of my three Z-Wave GE switches yesterday. Renamed it back, and all worked again.

COCottonwood commented 2 years ago

I am tending to agree with the "wiped cache" theory but why only one specific model of ZWave device? Of the 10 or so different model numbers of ZWave devices I have installed, only the GE/JASCO 46201 / ZW4008 device got wiped.

kpine commented 2 years ago

I am tending to agree with the "wiped cache" theory but why only one specific model of ZWave device?

The problem is already fixed, there's nothing to theorize about. 😅 This comment explains why this occurred for your GE switches, it was due to a change in the model label.

home-assistant / core