-
-
Notifications
You must be signed in to change notification settings - Fork 633
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
Provisioning Entries Smart Start disappeared after upgrade to 9.10.2 #6755
Comments
I had the same experience, I swapped back to 9.9.1 and restored a backup. |
Do you happen to know which file to restore to get the provisioning entries back? |
I used the back up that was created using a previous doctor image and I just extracted the files into the base directory and overwrote everything. I think the provision details are stored in a file that looks like a mix of Alpha numeric Characters. |
I had the same issue. I restored from backup. |
cc @AlCalzone |
Everyone: Which versions did you upgrade from? @rohankapoorcom the file should be |
@AlCalzone - I upgraded from zwave-js-ui: 9.9.1.f6dff21 Unfortunately it seems my backup saving script failed, so I do not have a backup file to restore. Is it helpful if I send you that file (privately)? |
I'll try to reproduce myself first. Will let you know if I need anything else. |
Ok I can't reproduce. Can you send me the file via E-mail? |
I'm coming here from ticket #3658, but I had the same issue as well. In looking at the version: '3' |
@drowl87 can you send me your jsonl file aswell? I wonder if this is just the UI choking on some missing fields. |
Just sent it via email! |
Could someone check the chrome console when you open the provisioning entries table? That may be an UI error in that case as something changed when we added the long range support |
@drowl87 Yeah that seems to show no errors on UI side, at least those errors seems to be related to some of your chrome extensions |
Sent to the email on your Github profile. I'm also not seeing any errors in the chrome console. |
Confirmed this to be a bug in the driver. The data is still there, but it's not being exposed. |
@AlCalzone - thanks for pushing out a fix. I just updated to the latest version of Z-Wave JS UI and am still seeing the same issue. zwave-js-ui: 9.10.3.f2b51e2 |
I think your file actually didn't have any provisioning entries |
Sounds like something in the update must have clobbered them then. Pity my backup script broke. Any way to regenerate them from an existing network without scanning all of the QR codes again? |
It should be mostly possible with a bit of fiddling. |
I found this thread today when I found out all my Smart Start entries had disappeared. I saw there was an update, and applied it. I'm now running version: But all my smart start devices are still missing 😭 |
Anyone still having this issue since the release of Release 9.11.1? Rolled back to 9.9.1 to resolve the issue temporarily, but based upon the reports, not sure I want to update yet. Thanks! |
@alvinchen1 Yes I rolled back to 9.9.1, restored a backup, then successfully upgraded to 9.11.1 and my Smart Start entries remained. |
@drowl87 , Thanks! Appreciate you taking the plunge for me. |
@alvinchen1 i'm on 9.11.1 Provisioning Entries are still missing. is the revert, restore, upgrade required to get them back? |
You need the old jsonl file back when they are missing. |
this might be a good opportunity to make backup enabled by default for everyone ... I would have appreciated it now ... |
Checklist
Deploy method
Docker
Z-Wave JS UI version
9.10.2.68fdf4d
ZwaveJS version
12.5.2
Describe the bug
After upgrading Z-Wave JS UI to 9.10.2.68fdf4d, the "Provisioning Entries" page has no entries when previously there were ~40 or so.
To Reproduce
Expected behavior
The Provisioning Entries page should show the entries that were present before the upgrade.
Additional context
Rolling back to the previously running version (and several versions behind) did not restore the entries.
zwave-js-ui: 9.9.1.f6dff21
zwave-js: 12.4.4
The text was updated successfully, but these errors were encountered: