Double persistence entries for items

running OH5.0.3 on docker.

My persistence (JDBC with mariaDB) does insert double on everyChange:

the jdbc-persistence looks like this:

configurations:
  - items:
      - "*"
      - "!PL12Images*"
    strategies:
      - everyChange
      - restoreOnStartup
    filters: []
  - items:
      - PL12Forecast*
    strategies:
      - forecast
    filters: []
  - items:
      - "*"
      - "!PL12Images*"
    strategies:
      - everyChange
      - restoreOnStartup
    filters: []
aliases: {}
cronStrategies: []
defaultStrategies:
  - everyChange
thresholdFilters: []
timeFilters: []
equalsFilters: []
includeFilters: []

the items are only linked to one thing:

and the thing listens to a mqtt-topic, which definetely only gets updated once every 2seconds:

There’s only one openHAB instance running, and I triple checked as I just restarted the container, there was a gap in the persistence during the restart-process:

What do i miss here?
It affects as far as I can see all items, regardless the binding?

the trace spits out only one store-command?

...
2025-11-24 17:42:54.271 [DEBUG] [jdbc.internal.JdbcPersistenceService] - JDBC: Stored item 'KOS_HomeConsumption' as '962 W' in SQL database at Mon Nov 24 17:42:54 CET 2025 in 10 ms.
2025-11-24 17:42:54.360 [DEBUG] [persistence.jdbc.internal.JdbcMapper] - JDBC::storeItemValue: item=KOS_TotalActivePower (Type=NumberItem, State=967.5 W, Label=Netzbezug (Gesamtwirkleistung Netz), Category=, Tags=[Point], Groups=[PL12Kostal10]) state=967.5 W date=null
2025-11-24 17:42:54.361 [DEBUG] [persistence.jdbc.internal.dto.ItemVO] - JDBC:ItemVO tableName=item0902; newTableName=null; 
==> /logs/events.log <==
2025-11-24 17:42:54.363 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'KOS_TotalActivePower' changed from 963.9000244140625 W to 967.5 W
==> /logs/openhab.log <==
2025-11-24 17:42:54.364 [DEBUG] [istence.jdbc.internal.db.JdbcBaseDAO] - JDBC::storeItemValueProvider: item 'KOS_TotalActivePower' as Type 'NUMBERITEM' in 'item0902' with state '967.5 W'
2025-11-24 17:42:54.368 [DEBUG] [istence.jdbc.internal.db.JdbcBaseDAO] - JDBC::storeItemValueProvider: itemState: '967.5 W'
2025-11-24 17:42:54.369 [DEBUG] [persistence.jdbc.internal.dto.ItemVO] - JDBC:ItemVO setValueTypes dbType=DOUBLE; javaType=class java.lang.Double;
2025-11-24 17:42:54.372 [DEBUG] [istence.jdbc.internal.db.JdbcBaseDAO] - JDBC::storeItemValueProvider: newVal.doubleValue: '967.5'
2025-11-24 17:42:54.373 [DEBUG] [istence.jdbc.internal.db.JdbcBaseDAO] - JDBC::doStoreItemValue sql=INSERT INTO item0902 (time, value) VALUES( NOW(3), ? ) ON DUPLICATE KEY UPDATE VALUE= ? value='967.5'
2025-11-24 17:42:54.382 [DEBUG] [jdbc.internal.JdbcPersistenceService] - JDBC: Stored item 'KOS_TotalActivePower' as '967.5 W' in SQL database at Mon Nov 24 17:42:54 CET 2025 in 22 ms.
2025-11-24 17:42:54.384 [DEBUG] [persistence.jdbc.internal.JdbcMapper] - JDBC::storeItemValue: item=KOS_TotalActivePower (Type=NumberItem, State=967.5 W, Label=Netzbezug (Gesamtwirkleistung Netz), Category=, Tags=[Point], Groups=[PL12Kostal10]) state=967.5 W date=null
2025-11-24 17:42:54.387 [DEBUG] [persistence.jdbc.internal.dto.ItemVO] - JDBC:ItemVO tableName=item0902; newTableName=null; 
2025-11-24 17:42:54.390 [DEBUG] [istence.jdbc.internal.db.JdbcBaseDAO] - JDBC::storeItemValueProvider: item 'KOS_TotalActivePower' as Type 'NUMBERITEM' in 'item0902' with state '967.5 W'
2025-11-24 17:42:54.390 [DEBUG] [istence.jdbc.internal.db.JdbcBaseDAO] - JDBC::storeItemValueProvider: itemState: '967.5 W'
2025-11-24 17:42:54.391 [DEBUG] [persistence.jdbc.internal.dto.ItemVO] - JDBC:ItemVO setValueTypes dbType=DOUBLE; javaType=class java.lang.Double;
2025-11-24 17:42:54.391 [DEBUG] [istence.jdbc.internal.db.JdbcBaseDAO] - JDBC::storeItemValueProvider: newVal.doubleValue: '967.5'
2025-11-24 17:42:54.392 [DEBUG] [istence.jdbc.internal.db.JdbcBaseDAO] - JDBC::doStoreItemValue sql=INSERT INTO item0902 (time, value) VALUES( NOW(3), ? ) ON DUPLICATE KEY UPDATE VALUE= ? value='967.5'
2025-11-24 17:42:54.405 [DEBUG] [jdbc.internal.JdbcPersistenceService] - JDBC: Stored item 'KOS_TotalActivePower' as '967.5 W' in SQL database at Mon Nov 24 17:42:54 CET 2025 in 22 ms.
2025-11-24 17:42:54.406 [DEBUG] [persistence.jdbc.internal.JdbcMapper] - JDBC::storeItemValue: item=EMS_Ueberschuss (Type=NumberItem, State=-962 W, Label=Überschuss, Category=, Tags=[Point], Groups=[PL12EMS]) state=-962 W date=null
...