OH5 - Persistence Error message

Add-ons Persistence Services
1

I just upgrade to 5.1.3 and just now recognized the changes made to persistence.
Anyhow, I renamed the persistence definition file to “influxdb.persist.old” for my influxDB and defined all strategies in the UI, except the default one of course.

To ensure that all is fine, I restarted my openHAB installation (Docker based).

I still have the following error message in my openhab.log during startip:

DSL model 'influxdb.persist' has errors, therefore ignoring it: [10,5]: no viable alternative at input 'default'

I’m a bit puzzled, since I checked all possible locations, but can not find any other definition of my influxdb persistent config file, which I already renamed, so that openHAB will not read it.
Any idea, where else to look and may remove this definition?

2

Move the file outside of that folder just in case.

Restart OH just to ensure there that file is absolutely not being loaded. When OH starts up you should not see a line similar to Loading model influxdb.persist. If you do see that log statement, this file still exists somewhere.

Navigate to Settings → Persistence → InfluxDB → Code and paste the YAML you find there into a reply. Use code fences.

```
code goes here
```
3

I moved the file outside the directory, but that did not change the error message.

2026-02-26 10:15:45.718 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading DSL model ‘influxdb.persist’
2026-02-26 10:15:45.989 [WARN ] [el.core.internal.ModelRepositoryImpl] - DSL model ‘influxdb.persist’ has errors, therefore ignoring it: \[10,5\]: no viable alternative at input ‘default’
2026-02-26 10:15:45.991 [INFO ] [el.core.internal.ModelRepositoryImpl] - Unloading DSL model ‘influxdb.persist’

Here the YAML code from the UI persistence configuration. That is actually working, just the error message is strange.

configurations:

* items:
  * Daily_Values\*
    strategies:
  * restoreOnStartup
  * everyDay
    filters: [ ]
* items:
  * Raumtemperaturen\*
    strategies:
  * restoreOnStartup
  * everyTenMinutes
    filters: [ ]
* items:
  * Thermo_Garten_Temperatur
    strategies:
  * restoreOnStartup
  * everyTenMinutes
    filters: [ ]
* items:
  * Temperature
    strategies:
  * restoreOnStartup
  * everyTenMinutes
    filters: [ ]
* items:
  * Pressure
    strategies:
  * restoreOnStartup
  * everyMinute
    filters: [ ]
* items:
  * Pegel
    strategies:
  * everyUpdate
  * restoreOnStartup
    filters: [ ]
* items:
  * Historic_Data\*
    strategies:
  * restoreOnStartup
  * everyHour
    filters: [ ]
* items:
  * TVAV_Wohnzimmer_Verbrauch
    strategies:
  * restoreOnStartup
  * everyHour
    filters: [ ]
* items:
  * VacationMode
    strategies:
  * everyUpdate
  * restoreOnStartup
    filters: [ ]
    aliases: {}
    cronStrategies:
* name: everyTenMinutes
  cronExpression: 0 0/10 \* \* \* ?
* name: everyMinute
  cronExpression: 0 \* \* ? \* \*
* name: everyHour
  cronExpression: 0 0 \* \* \* ?
* name: everyDay
  cronExpression: 0 5 0 \* \* ?
* name: everyQuarterly
  cronExpression: 0 0/15 \* \* \* ?
  thresholdFilters: [ ]
  timeFilters: [ ]
  equalsFilters: [ ]
  includeFilters: [ ]
4

Ok found the issue finally.
This happens if you don’t link directories in proper manner … :roll_eyes:

The correct location of the persistence configuration file was not where I assumed it was.
Checking all relevant directories revealed that it was located in the docker linked directories.
And I though I did linked them to a different location.

Anyhow, thanks for helping!