- This topic has 4 replies, 3 voices, and was last updated 8 years, 1 month ago by .
Viewing 5 posts - 1 through 5 (of 5 total)
Viewing 5 posts - 1 through 5 (of 5 total)
- You must be logged in to reply to this topic.
OpenSprinkler › Forums › OpenSprinkler Unified Firmware › unattended install?
Hi there, was wondering if there was anyway to run ./build.sh unattended? trying to automate installation 🙂
thanks!
hi, and one last question on this topic, is there a master configuration file i can overwrite the default config? (i.e. set my default password, valve names, location, wunderground api key, etc)
i wanted to check if i backup my old config via the web UI, can i use that backup file to overwrite a static text file in the opensprinker directory? or do i need to reimport it through the webui because the file is parsed?
thanks!!
All configurations are in the file name nvm.dat
how do we read the sts.dat and NVM.dat?
recently had an RPI die on me and wanted to copy the opensprinkler settings. copy/pasting and resetting permissions didn’t help. any suggestions? thanks
NVM.dat is completely a binary file so it’s not really human readable. Its format is documented here:
https://github.com/OpenSprinkler/OpenSprinkler-Firmware/blob/master/defines.h#L158
assuming your newly installed OSPi firmware matches the firmware version in your nvm.dat, I would think copy and pasting it should work. The problem is that if the firmware is a different version than what the nvm.dat stores, it will trigger a factory reset and recover nvm.dat to default settings.
Because of the difficulty of directly dealing with this file, the better way is to use the app or web UI to export configurations to a (JSON) file and import those after re-installation. The exported configuration files are human readable.
OpenSprinkler › Forums › OpenSprinkler Unified Firmware › unattended install?