-
Notifications
You must be signed in to change notification settings - Fork 173
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
restore configuration issue (on dig octa) #750
Comments
Been a while since I was in this area. I will take a look. |
Confirmed |
fixed in #749 |
Also made an attempt to merge the new and old config to create fields for features that may have been added since the backup was made. |
Hi I was testing the save restore feature from scratch with the latest CI and found some issues. |
I just did a save and the device config is certainly there. Keep in mind that the data in the config file does NOT strictly follow the layout you find on the UI. Fields are located to make the code work better, not make it easy on humans. |
on Dig-Octa this is whay I see: this is the file I have edited this post: So It might be still a restore problem |
I tried again (latest release win dns) and can see errors in the restore log after reboot [FileMgr] Configuration File: '/config.json' saved 748 bytes. rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) [ ESP] ESPixelStick v4.0-ci8317436315 (Mar 17 2024 - 18:25:30) |
That happened once in my testing and then I could not get it to reproduce. |
this very simple config file of a dig-octa can produce the issue on a rest device |
For the dig octa, the problems starts way earlier. On a first boot after a new FS is installed we already see this error: |
Fix has been uploaded and is part of the current PR. Octa has a huge output config and the json doc was not big enough to hold it under all configuration combinations and definitely not big enough to merge two configs together. |
While I see no error, I still don't see the output configuration restored |
after loading the file the output 1 is enabled correctly as by config but after reboot and merge is not [ [FileMgr] Configuration File: '/config.json' saved 703 bytes. rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) [ ESP] ESPixelStick v4.0-ci8327847865 (Mar 18 2024 - 13:59:28) |
Config merge has been disabled. It is a future looking feature and not needed at this |
Yes! working on my Dig-Octa. It looks we are ready for a new beta release. Do you have other improvements/fixes in mind? |
I am still working on a config merge mechanism that will work on significant upgrades. The current merge only works on the same version of SW that you started with. It will result on config fields not getting set when changed in the UI. |
ESPixelStick Firmware Version
4.0-ci8237205806
Hardware Version
dig octa
Binary release or compiled yourself?
ci release
Describe the bug
restoring the configuration produces an error and parameters are not applied
I saved this file
bubbleid-4C7F5A1B5AE0-network.json
applied a factory reset
loading the file produces this log:
19:34:51.164 -> [FileMgr] Configuration File: '/config.json' saved 1436 bytes.
19:34:51.209 -> [FileMgr] Configuration File: '/config.json' saved 1436 bytes.
19:34:51.307 -> [FileMgr] Configuration File: '/config.json' saved 1436 bytes.
19:34:51.383 -> [FileMgr] Configuration File: '/output_config.json' saved 1436 bytes.
19:34:51.489 -> [FileMgr] Configuration File: '/output_config.json' saved 1436 bytes.
19:34:51.526 -> [FileMgr] Configuration File: '/config.json' saved 1436 bytes.
19:34:51.636 -> [FileMgr] Configuration File: '/config.json' saved 1436 bytes.
19:34:51.781 -> [FileMgr] Configuration File: '/config.json' saved 1436 bytes.
19:34:51.890 -> [FileMgr] Configuration File: '/config.json' saved 1436 bytes.
19:34:51.997 -> [FileMgr] Configuration File: '/input_config.json' saved 979 bytes.
19:34:52.182 -> [FileMgr] Configuration File: '/output_config.json' saved 1436 bytes.
19:34:52.691 -> [FileMgr] Configuration File: '/output_config.json' saved 1436 bytes.
19:34:52.764 -> [FileMgr] Configuration File: '/output_config.json' saved 1436 bytes.
19:34:52.876 -> [FileMgr] Configuration File: '/output_config.json' saved 1436 bytes.
19:34:52.947 -> [FileMgr] Configuration File: '/config.json' saved 1436 bytes.
19:34:52.981 -> [FileMgr] Configuration File: '/input_config.json' saved 1010 bytes.
19:34:53.095 -> [FileMgr] Configuration File: '/config.json' saved 1436 bytes.
19:34:53.164 -> [FileMgr] Configuration File: '/config.json' saved 1343 bytes.
19:34:53.273 -> [FileMgr] Configuration File: '/output_config.json' saved 1436 bytes.
19:34:53.349 -> [FileMgr] Configuration File: '/output_config.json' saved 1436 bytes.
19:34:53.562 -> [FileMgr] Configuration File: '/output_config.json' saved 143 bytes.
19:34:57.327 -> [FileMgr] Configuration File: '/input_config.json' loaded.
19:34:57.690 -> [FileMgr] Configuration File: '/config.json' loaded.
19:34:57.690 -> [ ESP] Missing Config Version ID
19:34:57.690 -> [ ESP] No device settings found.
19:34:57.728 -> [FileMgr] No File Manager settings found.
19:34:57.728 -> [NetworkMgr] No network config found. Use default settings
19:34:57.799 -> [FileMgr] Configuration File: '/config.json' saved 634 bytes.
19:34:58.503 -> [FileMgr] Configuration File: '/output_config.json' loaded.
The text was updated successfully, but these errors were encountered: