ConfigParser: Conversion of value '0' with type 'class java.math.BigDecimal' to 'class java.lang.String' failed

I have several warnings in my openhab.log (3.4.0) where I have problems to find the cause:

2023-01-15 12:37:10.766 [WARN ] [penhab.core.config.core.ConfigParser] - Conversion of value '0' with type 'class java.math.BigDecimal' to 'class java.lang.String' failed. Returning null

From the context of the debug messages, I assume that it is related to the systeminfo binding.
Any ideas which config file is affected?

2023-01-15 12:37:10.619 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - bundle org.openhab.core.config.discovery:3.4.0 (162)[org.openhab.core.config.discovery.internal.DiscoveryServiceRegistryImpl(131)] : dm DiscoveryService tracking 9 MultipleDynamic added {org.openhab.core.config.discovery.DiscoveryService}={service.id=555, service.bundleid=287, service.scope=bundle, component.name=org.openhab.binding.systeminfo.internal.discovery.SysteminfoDiscoveryService, component.id=343} (enter)
2023-01-15 12:37:10.622 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - bundle org.openhab.core.config.discovery:3.4.0 (162)[org.openhab.core.config.discovery.internal.DiscoveryServiceRegistryImpl(131)] : dm DiscoveryService tracking 9 MultipleDynamic already active, binding {org.openhab.core.config.discovery.DiscoveryService}={service.id=555, service.bundleid=287, service.scope=bundle, component.name=org.openhab.binding.systeminfo.internal.discovery.SysteminfoDiscoveryService, component.id=343}
2023-01-15 12:37:10.699 [DEBUG] [g.discovery.AbstractDiscoveryService] - Background discovery for discovery service 'org.openhab.binding.systeminfo.internal.discovery.SysteminfoDiscoveryService' enabled.
2023-01-15 12:37:10.716 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - bundle org.openhab.core.config.discovery:3.4.0 (162)[org.openhab.core.config.discovery.internal.DiscoveryServiceRegistryImpl(131)] : invoking bind: addDiscoveryService: parameters [org.openhab.binding.systeminfo.internal.discovery.SysteminfoDiscoveryService]
2023-01-15 12:37:10.719 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - bundle org.openhab.core.config.discovery:3.4.0 (162)[org.openhab.core.config.discovery.internal.DiscoveryServiceRegistryImpl(131)] : invoked bind: addDiscoveryService
2023-01-15 12:37:10.732 [WARN ] [core.thing.internal.ThingManagerImpl] - Initializing handler for thing 'mqtt:broker:mosquitto' takes more than 5000ms.
2023-01-15 12:37:10.724 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - bundle org.openhab.core.config.discovery:3.4.0 (162)[org.openhab.core.config.discovery.internal.DiscoveryServiceRegistryImpl(131)] : dm DiscoveryService tracking 9 MultipleDynamic added {org.openhab.core.config.discovery.DiscoveryService}={service.id=555, service.bundleid=287, service.scope=bundle, component.name=org.openhab.binding.systeminfo.internal.discovery.SysteminfoDiscoveryService, component.id=343} (exit)
2023-01-15 12:37:10.723 [WARN ] [penhab.core.config.core.ConfigParser] - Conversion of value '0' with type 'class java.math.BigDecimal' to 'class java.lang.String' failed. Returning null
2023-01-15 12:37:10.738 [WARN ] [penhab.core.config.core.ConfigParser] - Conversion of value '0' with type 'class java.math.BigDecimal' to 'class java.lang.String' failed. Returning null
2023-01-15 12:37:10.766 [WARN ] [penhab.core.config.core.ConfigParser] - Conversion of value '0' with type 'class java.math.BigDecimal' to 'class java.lang.String' failed. Returning null
2023-01-15 12:37:10.767 [WARN ] [penhab.core.config.core.ConfigParser] - Conversion of value '0' with type 'class java.math.BigDecimal' to 'class java.lang.String' failed. Returning null
2023-01-15 12:37:10.781 [WARN ] [penhab.core.config.core.ConfigParser] - Conversion of value '0' with type 'class java.math.BigDecimal' to 'class java.lang.String' failed. Returning null
2023-01-15 12:37:10.788 [WARN ] [penhab.core.config.core.ConfigParser] - Conversion of value '0' with type 'class java.math.BigDecimal' to 'class java.lang.String' failed. Returning null
2023-01-15 12:37:10.790 [WARN ] [penhab.core.config.core.ConfigParser] - Conversion of value '0' with type 'class java.math.BigDecimal' to 'class java.lang.String' failed. Returning null
2023-01-15 12:37:10.793 [WARN ] [penhab.core.config.core.ConfigParser] - Conversion of value '0' with type 'class java.math.BigDecimal' to 'class java.lang.String' failed. Returning null
2023-01-15 12:37:10.795 [WARN ] [penhab.core.config.core.ConfigParser] - Conversion of value '0' with type 'class java.math.BigDecimal' to 'class java.lang.String' failed. Returning null
2023-01-15 12:37:10.838 [DEBUG] [g.discovery.internal.PersistentInbox] - bundle org.openhab.core.config.discovery:3.4.0 (162)[org.openhab.core.config.discovery.internal.PersistentInbox(132)] : dm ThingHandlerFactory tracking 26 MultipleDynamic added {org.openhab.core.thing.binding.ThingHandlerFactory}={service.id=558, service.bundleid=287, service.scope=bundle, component.name=org.openhab.binding.systeminfo.internal.SysteminfoHandlerFactory, component.id=341} (enter)
2023-01-15 12:37:10.839 [DEBUG] [g.discovery.internal.PersistentInbox] - bundle org.openhab.core.config.discovery:3.4.0 (162)[org.openhab.core.config.discovery.internal.PersistentInbox(132)] : dm ThingHandlerFactory tracking 26 MultipleDynamic already active, binding {org.openhab.core.thing.binding.ThingHandlerFactory}={service.id=558, service.bundleid=287, service.scope=bundle, component.name=org.openhab.binding.systeminfo.internal.SysteminfoHandlerFactory, component.id=341}

Base on the error message it looks like it is the same as in openHAB 3.4 Milestone discussion - #97 by usambara
Read that post and a few of the following ones.

These are for sure the same warnings, as I was also the poster of the other topic. Before I’ve posted this question, I’ve checked this forum.
But nevertheless in the milestone discussion it was more a side note and I haven’t got a solution for this.If I’ve overlooked it, please point me to it.

Do you have the systeminfo binding configured in the UI or in a things file? The original conversation was about that issue, and that should have been resolved.
I don’t know where the ConfigParser errors come from. Can you switch logging to TRACE mode for the binding? That should give a better hint if it the problem is in the binding, and where if so.

First of all I would like to confirm that the issues from the other post are solved.
Now I did some tests with TRACE and DEBUG messages and I got no clear picture. The surrounding messages of the warnings were always totally different. Finally I’ve uninstalled the systeminfo binding and these warnings remained. So It is is not the systeminfo binding!
But nevertheless it is hard to find a reason for the message when there is no further information in the message.