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

Logbook on the device page attributes entries to wrong device after replacing or resetting #8

Open
marcelveldt opened this issue Jul 13, 2023 · 2 comments
Labels
backend This bug or request (primary) involves the Home Assistant backend/integration (and its dependencies)

Comments

@marcelveldt
Copy link
Collaborator

marcelveldt commented Jul 13, 2023

From core created by AlCalzone: home-assistant/core#94530

During certification tests where I end up factory resetting the controller a lot, I noticed that after just including a device, the logbook on the device page was showing old entries from the device that previously used to have the same node ID.

It does not seem to matter if the device is the same or not, because this also reproduces after including an entirely different device.
All these entries are from a different controller I used for certification tests:
grafik

After factory resetting the controller (new home ID) and including a multisensor, HA now attributes all the state changes to the multisensor, although it wasn't part of the network at that time. The only thing that is the same is the node ID 2.

Diagnostics information

This is after replacing:

zwave_js-50da63f28934190600d0d68b43b2d834-Node 2-e308902a081a661262ba2565c42bdde0.json.txt

@marcelveldt marcelveldt changed the title Z-Wave JS: Logbook on the device page attributes entries to wrong device after replacing or resetting Logbook on the device page attributes entries to wrong device after replacing or resetting Jul 13, 2023
@MartinHjelmare MartinHjelmare added the backend This bug or request (primary) involves the Home Assistant backend/integration (and its dependencies) label Sep 2, 2024
@MartinHjelmare
Copy link
Collaborator

TODO

  • Find a test to reproduce the behavior.
  • Fix it.

Possible leads:

  • Devices entries not being cleared on hard reset?
  • Logbook data not refreshed (cache)?

@AlCalzone
Copy link
Member

Find a test to reproduce the behavior.

  • Hard reset controller
  • Include device A (node ID 2)
  • Make sure A shows up on the logbook
  • Hard reset controller
  • Include device B (now node ID 2)
  • See entries from A in B's logbook

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend This bug or request (primary) involves the Home Assistant backend/integration (and its dependencies)
Projects
Development

No branches or pull requests

3 participants