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

Error message "The NVM file ID must be set before serializing" when trying to restore NVM on new controller #7219

Closed
4 of 7 tasks
AlCalzone opened this issue Oct 7, 2024 Discussed in #7199 · 0 comments · Fixed by #7220
Closed
4 of 7 tasks

Comments

@AlCalzone
Copy link
Member

Discussed in #7199

Originally posted by @Aegis940 September 27, 2024

Checklist

  • I have read and followed the above instructions

  • I have checked the troubleshooting section and my problem is not described there.

  • I have read the changelog and my problem was not mentioned there or the fix did not work.

Describe the issue

Hello, I have an error when trying to restore the NVM on new zwave controller

Steps to reproduce the behavior:

  1. Backup NVM on current controller
  2. Shutdown Zwave API
  3. Switch to new controller
  4. Restart Zwave API
  5. Restore NVM

Error is display at the end of "Convert NVM progress" process

Software versions

ui: 9.20.0.bf3bdc3
driver: 13.4.0
server: 1.38.0

Managed by the Jeedom solution

Z-Wave Controller (Stick/Dongle/...)

source controller:
Z-Stick Aeotec Gen5 ZW090 (firmware Gen5+)
FW: v1.2
SDK: v6.81.6

Target controller:
Zooz 800 ZST39 LR
FW: v1.50
SDK: v7.22.1

Checklist

  • I made sure to provide a driver log on level debug.

  • The log includes a re-interview of the problematic device (if applicable).

  • The log includes the problematic interaction with the device (if applicable).

  • I provided the node ID of the problematic device (if applicable).

Upload Logfile

z-ui_current.log

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

Successfully merging a pull request may close this issue.

1 participant