Mine works fine and I think it could be because you have 2 restore on startup. That also cause me problems.
My mapdb.persist looks like this:
Strategies {
default = everyChange, restoreOnStartup
}
Items {
// persist all items on every change and restore them from the db at startup
* : strategy = everyChange, restoreOnStartup ,everyUpdate
}
My rdd4j.persist looks like this:
Strategies {
default = everyChange
}
Items {
// persist all items on every change and restore them from the db at startup from mapdb
* : strategy = everyChange, everyUpdate
}
if i am not mistaken, you don’t need a persist config file in the first place for your default service if you anyway want to persist everything. I have also both persist services running and the rrd4j my default with no config file, with the MapDB if have persisted some items only configured in the file for other purposes. You can try delete your rrd4j config file and see if this works with you
Comparing our files it seems that the files should be ok on my side. So I finally dared to “restoreonstartup” openhab (usually I hesitate doing that on my production device) like in the old saying “didyouturnitonandoffagain?” which I should have done before.
now it works…
The hint on having two restoreonstartups though is a good one when I think about it because it would mean that any of the two “wins” which could be an issue. So I removed that option from the rrd4j.
For those who are reading along who wonder why I use two persistence implementations:
RestoreOnStartup is recommended to do with mapdb as it only uses ONE entry for an item but even more important: other persistence implementations like rrd4j for example do not support “string” to be persisted.