Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zwave entities disappeared after HAOS update #137286

Open
plaidbear opened this issue Feb 4, 2025 · 4 comments
Open

Zwave entities disappeared after HAOS update #137286

plaidbear opened this issue Feb 4, 2025 · 4 comments

Comments

@plaidbear
Copy link

The problem

After updating to 2025.1.4 the entities for my GoControl thermostats are missing and show the following error: “This entity is no longer being provided by the zwave_js integration. If the entity is no longer in use, delete it in settings.” In the Zwave_JS integration the devices show, are connected, ping, etc, just the entities are missing.

What version of Home Assistant Core has the issue?

2025.1.4

What was the last working version of Home Assistant Core?

2025.1.3

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

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

I have one Honeywell Zwave thermostat also connected to the Zwave network via Zwave_JS and it’s entities are all intact. I thought I’d seek advice before proceeding.

@home-assistant
Copy link

home-assistant bot commented Feb 4, 2025

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)

@kpine
Copy link
Contributor

kpine commented Feb 4, 2025

Please attach the device diagnostic file (attach file to comment, not copy and paste). You can download the diagnostic file by going to Settings -> Devices & services -> Z-Wave "Devices" -> The Device -> Device info -> ... -> Download diagnostics.

@plaidbear
Copy link
Author

File attached. I re-interviewed the devices and the entities are now associated. For me, the issue is solved but it's still suspicious that all of the same model of thermostat lost their association on upgrade.

zwave_js-01JES1Q4V4KFTW09GXENDWJEW0-Z-Wave Plus Thermostat-7e958c720116418391b6dcbf4a02bb29.json

@kpine
Copy link
Contributor

kpine commented Feb 4, 2025

Are you sure you also didn't upgrade some other components at the same time, like the OS or add-on?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants