Skip to content

Ghost controller node after restoring NVM where controller is NOT node 1 #4361

@AlCalzone

Description

@AlCalzone

Checklist

  • I am not using Home Assistant. Or: a developer has told me to come here.
  • I have checked the troubleshooting section and my problem is not described there.
  • I have read the changelog and my problem is not mentioned there.

Deploy method

Manually built (git clone - npm run build - npm install

Z-Wave JS UI version

master (as of 2025-09-08)

ZwaveJS version

15.12.0

Describe the bug

When restoring the NVM from a controller where the controller itself was not node 1 onto one where it is, the device list keeps the old entry for node 1, even though it no longer exists.

Restarting Z-Wave JS UI and force-reloading the browser causes the ghost device to disappear.

To Reproduce

  1. Use factory reset controller with own node ID 1
  2. Use NVM backup from controller that was not node ID 1
  3. Restore the backup onto the factory reset controller
  4. See Node 1 in the list of devices after NVM restore

Expected behavior

There should be no node 1 in the list of devices after NVM restore

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions