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

Device (e.g. z-wave) name/zone gets reset (& hence kicked off from scenes/groups) #80447

Closed
Chef-de-IT opened this issue Oct 16, 2022 · 1 comment

Comments

@Chef-de-IT
Copy link

The problem

In a HA install covering a large-ish area, on occasion several Z-Wave devices have gone out of range and then back in, which somehow resulted in their name being reset to device's default and Area to unassigned. Hence this kicks them out of scenes, dimmer groups, etc.

This is surprising as I would expect HA to keep track of devices' hardware IDs and if they disappear and then reappear, to put them back the way they were - not as newly added.

What version of Home Assistant Core has the issue?

2022.10.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Z-Wave JS (suspect, the same with any disappearing & reappearing devices)

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
Copy link

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)

@github-actions github-actions bot added the stale label Nov 15, 2022
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 22, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Dec 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant