In the past, I had no problems with mapdb.persist
Strategies {default = everyChange} Items {mCR* : strategy = everyChange, restoreOnStartup}
Now with Release 5.1.x, I get after starting
22:34:27.589\[WARN\] \[org.openhab.core.model.core.internal.ModelRepositoryImpl\] - DSL model ‘mapdb.persist’ has errors, therefore ignoring it: \[3,13\]: no viable alternative at input ‘default’
and due to the missing restoreOnStartup, various subsequent problems. Additionally, then occurs every minute
22:37:54.943\[INFO\] \[org.openhab.binding.enocean.internal.transceiver.EnOceanTransceiver\] - Transceiver shutdown
22:37:54.947\[INFO\] \[openhab.event.ThingStatusInfoChangedEvent\] - Thing ‘enocean:bridge:EnOceanGateway’ changed from OFFLINE (CONFIGURATION_PENDING): trying to get bridge base id… to OFFLINE (CONFIGURATION_PENDING): opening serial port…
22:37:54.985\[INFO\] \[org.openhab.binding.enocean.internal.transceiver.EnOceanTransceiver\] - EnOceanSerialTransceiver initialized
22:37:54.986\[INFO\] \[org.openhab.binding.enocean.internal.transceiver.EnOceanTransceiver\] - EnOceanSerialTransceiver RX thread started
22:37:54.986\[INFO\] \[openhab.event.ThingStatusInfoChangedEvent\] - Thing ‘enocean:bridge:EnOceanGateway’ changed from OFFLINE (CONFIGURATION_PENDING): opening serial port… to OFFLINE (CONFIGURATION_PENDING): starting rx thread…
22:37:54.986\[INFO\] \[org.openhab.binding.enocean.internal.handler.EnOceanBridgeHandler\] - EnOceanSerialTransceiver RX thread up and running
22:37:54.987\[INFO\] \[openhab.event.ThingStatusInfoChangedEvent\] - Thing ‘enocean:bridge:EnOceanGateway’ changed from OFFLINE (CONFIGURATION_PENDING): starting rx thread… to OFFLINE (CONFIGURATION_PENDING): trying to get bridge base id…
even if that doesn’t seem to have anything to do with persistence
please, where is the error