openHAB 4.1.0 with current KM200 binding, KM200, /gateway/versionHardware “iCom_Low_NSC_v1”
With my Buderus GB 162-15 I found several lines like this during startup (no upgrade procedure taken place).
2024-01-06 15:31:03.233 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'km200:sensor:Heizung:temperatures' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2024-01-06 15:30:33.165 [INFO ] [ler.KM200SwitchProgramServiceHandler] - !!! Wrong configuration on device. 'on' instead of 'high' in switch program. It seems that's a firmware problem-> ignoring it !!!
2024-01-06 15:31:03.234 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'km200:sensor:Heizung:temperatures': {thing/channel=Type description km200:sensor:Heizung:temperatures:outdoor_t1 for km200:sensor:Heizung:temperatures:outdoor_t1 not found, although we checked the presence before.}
These messages are quite similar for every KM200 thing.
Does anybody have an idea, if this can be ignored or how to correct this?
2024-01-28 22:38:01.752 [WARN ] [ort.loader.AbstractScriptFileWatcher] - Script loading error, ignoring file '/etc/openhab/automation/js/test.js'
2024-01-28 22:39:23.484 [INFO ] [ler.KM200SwitchProgramServiceHandler] - !!! Wrong configuration on device. 'on' instead of 'high' in switch program. It seems that's a firmware problem-> ignoring it !!!
2024-01-28 22:39:23.484 [INFO ] [ler.KM200SwitchProgramServiceHandler] - !!! Wrong configuration on device. 'on' instead of 'high' in switch program. It seems that's a firmware problem-> ignoring it !!!
2024-01-28 22:39:23.485 [INFO ] [ler.KM200SwitchProgramServiceHandler] - !!! Wrong configuration on device. 'on' instead of 'high' in switch program. It seems that's a firmware problem-> ignoring it !!!
2024-01-28 22:39:23.485 [INFO ] [ler.KM200SwitchProgramServiceHandler] - !!! Wrong configuration on device. 'on' instead of 'high' in switch program. It seems that's a firmware problem-> ignoring it !!!
2024-01-28 22:39:23.485 [INFO ] [ler.KM200SwitchProgramServiceHandler] - !!! Wrong configuration on device. 'on' instead of 'high' in switch program. It seems that's a firmware problem-> ignoring it !!!
2024-01-28 22:39:23.485 [INFO ] [ler.KM200SwitchProgramServiceHandler] - !!! Wrong configuration on device. 'on' instead of 'high' in switch program. It seems that's a firmware problem-> ignoring it !!!
2024-01-28 22:39:23.486 [INFO ] [ler.KM200SwitchProgramServiceHandler] - !!! Wrong configuration on device. 'on' instead of 'high' in switch program. It seems that's a firmware problem-> ignoring it !!!
2024-01-28 22:39:23.486 [INFO ] [ler.KM200SwitchProgramServiceHandler] - !!! Wrong configuration on device. 'on' instead of 'high' in switch program. It seems that's a firmware problem-> ignoring it !!!
2024-01-28 22:39:23.486 [INFO ] [ler.KM200SwitchProgramServiceHandler] - !!! Wrong configuration on device. 'on' instead of 'high' in switch program. It seems that's a firmware problem-> ignoring it !!!
2024-01-28 22:39:23.487 [INFO ] [ler.KM200SwitchProgramServiceHandler] - !!! Wrong configuration on device. 'on' instead of 'high' in switch program. It seems that's a firmware problem-> ignoring it !!!
2024-01-28 22:39:23.487 [INFO ] [ler.KM200SwitchProgramServiceHandler] - !!! Wrong configuration on device. 'on' instead of 'high' in switch program. It seems that's a firmware problem-> ignoring it !!!
2024-01-28 22:39:23.487 [INFO ] [ler.KM200SwitchProgramServiceHandler] - !!! Wrong configuration on device. 'on' instead of 'high' in switch program. It seems that's a firmware problem-> ignoring it !!!
2024-01-28 22:39:23.487 [INFO ] [ler.KM200SwitchProgramServiceHandler] - !!! Wrong configuration on device. 'on' instead of 'high' in switch program. It seems that's a firmware problem-> ignoring it !!!
2024-01-28 22:39:23.487 [INFO ] [ler.KM200SwitchProgramServiceHandler] - !!! Wrong configuration on device. 'on' instead of 'high' in switch program. It seems that's a firmware problem-> ignoring it !!!
2024-01-28 22:39:53.292 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'km200:sensor:Heizung:temperatures' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2024-01-28 22:39:53.294 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'km200:sensor:Heizung:temperatures': {thing/channel=Type description km200:sensor:Heizung:temperatures:outdoor_t1 for km200:sensor:Heizung:temperatures:outdoor_t1 not found, although we checked the presence before.}
2024-01-28 22:39:53.300 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'km200:dhwCircuit:Heizung:dhw1' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2024-01-28 22:39:53.301 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'km200:dhwCircuit:Heizung:dhw1': {thing/channel=Type description km200:dhwCircuit:Heizung:dhw1:charge for km200:dhwCircuit:Heizung:dhw1:charge not found, although we checked the presence before.}
2024-01-28 22:39:53.307 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'km200:appliance:Heizung:appliance' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2024-01-28 22:39:53.308 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'km200:appliance:Heizung:appliance': {thing/channel=Type description km200:appliance:Heizung:appliance:actualSupplyTemperature for km200:appliance:Heizung:appliance:actualSupplyTemperature not found, although we checked the presence before.}
2024-01-28 22:39:53.314 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'km200:heatingCircuit:Heizung:hc1' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2024-01-28 22:39:53.314 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'km200:heatingCircuit:Heizung:hc1': {thing/channel=Type description km200:heatingCircuit:Heizung:hc1:supplyTemperatureSetpoint for km200:heatingCircuit:Heizung:hc1:supplyTemperatureSetpoint not found, although we checked the presence before.}
2024-01-28 22:39:53.321 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'km200:notification:Heizung:notifications' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2024-01-28 22:39:53.322 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'km200:notification:Heizung:notifications': {thing/channel=Type description km200:notification:Heizung:notifications:nbrErrors for km200:notification:Heizung:notifications:nbrErrors not found, although we checked the presence before.}
2024-01-28 22:39:53.328 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'km200:heatingCircuit:Heizung:hc1-switchprogram' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2024-01-28 22:39:53.329 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'km200:heatingCircuit:Heizung:hc1-switchprogram': {thing/channel=Type description km200:heatingCircuit:Heizung:hc1-switchprogram:weekday for km200:heatingCircuit:Heizung:hc1-switchprogram:weekday not found, although we checked the presence before.}
2024-01-28 22:39:53.335 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'km200:system:Heizung:system' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2024-01-28 22:39:53.335 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'km200:system:Heizung:system': {thing/channel=Type description km200:system:Heizung:system:healthStatus for km200:system:Heizung:system:healthStatus not found, although we checked the presence before.}
2024-01-28 22:39:53.347 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'km200:gateway:Heizung:gateway' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2024-01-28 22:39:53.348 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'km200:gateway:Heizung:gateway': {thing/channel=Type description km200:gateway:Heizung:gateway:update_status for km200:gateway:Heizung:gateway:update_status not found, although we checked the presence before.}
2024-01-28 22:39:53.360 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'km200:heatSource:Heizung:heatSources' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2024-01-28 22:39:53.361 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'km200:heatSource:Heizung:heatSources': {thing/channel=Type description km200:heatSource:Heizung:heatSources:nominalCHPower for km200:heatSource:Heizung:heatSources:nominalCHPower not found, although we checked the presence before.}
Were you able to find and rectify the root cause of these messages? For a few weeks now - without any deliberate changes to the configuration - I have been getting the same messages that I didn’t have before. I am with openHAB 4.3.3.
