rkoshak
commented
4 years ago I think I need more info.
The way I'm expecting it to work is that on the first boot the MapDB is empty. Once the Initialization Rule kicks off, it commands and updates the settings Items with appropriate defaults based on the initial settings (Temp Unit Type, System Type which get pulled from the files in scripts). At that point those values and any subsequent changes to them get saved to MapDB and restored the next time OH is booted.
If you watch openhab.log during a boot, you should see a bunch of log statements along the lines of "Blah is undefined initializing to blah". That indicates the Item was not restored from the database. The next time you boot those lines will disappear indicating that the Item's state was restored from MapDB. You can set the initialization logger to DEBUG and see what they are restored to in the logs if desired.
So my questions are:
- what are you seeing in the log on the first boot and the second boot?
- if it's not working right, is it failing for all Items or just some Items?
Assuming that it's working right, I think we want to delete the MapDB files which will give the users a nice clean environment with everything initialized to the hard coded defaults to start with (similar to how it came up before every time it rebooted before all these changes). Without deleting the MapDB files, any changes you make prior to cutting the SD card image will be preserved and restored when the users first boot.
/home/pi/scripts/packitupandgo.sh needs updating as
sudo rm -f /var/lib/openhab2/persistence/mapdb/*;is not getting reinitialised on first boot as mentioned here. @rkoshak should we keep this line in and work around initialisation or something else?