Homematic Binding: "Channel not found for datapoint" errors for definitely existing channels

Interesting… Do your thing-types have channels? Are there any channels for your things or are all of them missing?

There are channels - and they are working.

//Homematic Schalter1
Switch HMSchalter11kurz "HMSchalter1-1 kurz"  {channel="homematic:HmIP-WRCC2:3014F711A0001F5A4993EAD1:002C1BE999698A:1#PRESS_SHORT", expire="2s,command=OFF"} //, expire="2s,command=OFF"
Switch HMSchalter11lang "HMSchalter1-1 lang" {channel="homematic:HmIP-WRCC2:3014F711A0001F5A4993EAD1:002C1BE999698A:1#PRESS_LONG", expire="2s,command=OFF"}
Switch HMSchalter12kurz "HMSchalter1-2 kurz" {channel="homematic:HmIP-WRCC2:3014F711A0001F5A4993EAD1:002C1BE999698A:2#PRESS_SHORT", expire="2s,command=OFF"}
Switch HMSchalter12lang "HMSchalter1-2 lang" {channel="homematic:HmIP-WRCC2:3014F711A0001F5A4993EAD1:002C1BE999698A:2#PRESS_LONG", expire="2s,command=OFF"}

Hi,
unfortunaly I have the error with 3.2 too.
The devices that are affected seems to be randomly selected. Every startup a couple of another device lost their datapoints.

When I deactivate my manuel written *.things files & add the homematic bridge via this clicke-di-click JSON Config UI-Tool it seems to be stable.

Feels a bit like the beginning of the end of the config files. :frowning:

Kind regards,
Fabu

That was not the question. The question is, if your thing-types have channels and if the actual things have channels. It doesn’t matter if you define them or not, if the thing doesn’t have them for some reason that’s worth nothing.

If there are channels and just those are missing then the fix probably won’t help you…

Same question for @Fabu.

At least for me my fix solved the issues, I know it’s not perfect but the entire stuff is so messed up that this is the only fix I could think about. It might be necessary to completely throw out the channel generation for thing-types and only do it at the thing level if there are now only some channels missing and the thing itself has some channels (although I’m wondering how that could happen with this race condition, I expected it to be “all or nothing” and my fix catches the “nothing”). I’m not sure what happens if there is no connection during thing creation and when the connection is established later on. That’s all something that someone who still has the issue now needs to investigate.

@flole,
not sure i get your question - does the attached screenshot answer it?

Not really, check using the REST-API to see if the thing and the thing-types have any channels or not. I’m not really sure but I think the channels were being shown on my device aswell but I am not sure (it’s been a while since I fixed this issue).

Thing-Type information from REST-API:

  {
    "UID": "homematic:HmIP-WRCC2",
    "label": "Homematic IP Wandtaster - flach",
    "description": "Homematic IP Wandtaster - flach (HmIP-WRCC2)",
    "listed": true,
    "supportedBridgeTypeUIDs": [
      "homematic:bridge"
    ],
    "bridge": false
  },

And thing information:

{
  "channels": [
    {
      "linkedItems": [
        "HomematicSchalter10CONFIGPENDING"
      ],
      "uid": "homematic:HmIP-WRCC2:3014F711A0001F5A4993EAD1:002C1BE999698A:0#CONFIG_PENDING",
      "id": "0#CONFIG_PENDING",
      "channelTypeUID": "homematic:HmIP-WRCC2_0_CONFIG_PENDING",
      "itemType": "Switch",
      "kind": "STATE",
      "label": "Config Pending",
      "description": "Zeigt eine ausstehende Konfigurations Aktualisierung an",
      "defaultTags": [],
      "properties": {},
      "configuration": {
        "receiveDelay": 0,
        "delay": 0
      }
    }
  ],
  "statusInfo": {
    "status": "ONLINE",
    "statusDetail": "NONE"
  },
  "editable": true,
  "label": "Homematic-Schalter1",
  "bridgeUID": "homematic:bridge:3014F711A0001F5A4993EAD1",
  "configuration": {
    "HMP_0_CYCLIC_INFO_MSG_DIS_UNCHANGED": 0,
    "HMP_2_DBL_PRESS_TIME": 0,
    "HMP_0_DISABLE_MSG_TO_AC": false,
    "HMP_0_CYCLIC_INFO_MSG_DIS": 20,
    "HMP_2_LONG_PRESS_TIME": 0.4,
    "HMP_0_CYCLIC_BIDI_INFO_MSG_DISCARD_VALUE": 57,
    "HMP_0_ENABLE_ROUTING": true,
    "HMP_2_ABORT_EVENT_SENDING_CHANNELS": 2,
    "HMP_0_LOCAL_RESET_DISABLED": false,
    "HMP_0_ARR_TIMEOUT": 10,
    "HMP_1_ABORT_EVENT_SENDING_CHANNELS": 1,
    "HMP_0_LOW_BAT_LIMIT": 2.2,
    "HMP_0_DUTYCYCLE_LIMIT": 180,
    "HMP_0_SUPPORTING_WIRED_OPERATION_MODE": true,
    "HMP_1_REPEATED_LONG_PRESS_TIMEOUT_UNIT": "M",
    "HMP_1_REPEATED_LONG_PRESS_TIMEOUT_VALUE": 2,
    "HMP_2_REPEATED_LONG_PRESS_TIMEOUT_UNIT": "M",
    "HMP_0_CYCLIC_BIDI_INFO_MSG_DISCARD_FACTOR": 1,
    "HMP_0_CYCLIC_INFO_MSG": 1,
    "HMP_1_LONG_PRESS_TIME": 0.4,
    "HMP_1_DBL_PRESS_TIME": 0,
    "HMP_2_REPEATED_LONG_PRESS_TIMEOUT_VALUE": 2,
    "HMP_0_CYCLIC_INFO_MSG_OVERDUE_THRESHOLD": 2
  },
  "properties": {
    "serialNumber": "002C1BE999698A",
    "firmwareVersion": "2.2.8",
    "modelId": "HmIP-WRCC2",
    "vendor": "eQ-3 AG"
  },
  "UID": "homematic:HmIP-WRCC2:3014F711A0001F5A4993EAD1:002C1BE999698A",
  "thingTypeUID": "homematic:HmIP-WRCC2",
  "location": "IT"
}

Well looks like you have a channel so my fix doesn’t recreate the channels as there is already one. I am not sure why your thing only has that single channel and if that is the same issue that was fixed or if that’s something completely different.

I just thought about this and maybe it’s a good idea to check the size of the channel set and re-do it if there’s a mismatch instead of just fixing it if it’s empty. Of course what you can also do is don’t give the ThingType channels at all, then the different firmware issue would also no longer be an issue I guess.

Hi,

had following in the log:

2022-04-15 16:51:18.311 [WARN ] [ternal.handler.HomematicThingHandler] - Channel not found for datapoint 'SEQ1034420:2#STATE'
2022-04-15 16:51:18.323 [WARN ] [ternal.handler.HomematicThingHandler] - Channel not found for datapoint 'SEQ1034420:2#WORKING'

and found this solution:

https://community.openhab.org/t/solved-wireless-switch-actuator-2-channel-flush-mount-hm-lc-sw2-fm-only-reports-one-channel/135001/2?u=peterk

BR
PeterK

Hi all,

since update HmIP-BROLL to Version 1.10.8 i got some Errors:

2023-04-23 08:16:50.376 [WARN ] [ternal.handler.HomematicThingHandler] - Channel not found for datapoint '00111BE99286E5:0#ERROR_OVERLOAD'

2023-04-23 08:16:59.474 [WARN ] [ternal.handler.HomematicThingHandler] - Channel not found for datapoint '00111BE99286DD:0#ERROR_OVERLOAD'

Regards
Simon

Anything else beside the warnings (which are not errors from my perspective)? Strange behavior or anything?
I was just about to update but saw your post. There are some more firmware updates for me:

  1. HMIP-SWDO 1.16.8 → 1.18.10
  2. HmIP-HAP 2.4.24 → 2.4.28 (for a while but faulty afair)
  3. HmIP-SRD 1.0.18 → 1.0.20
  4. HmIP-SRH 1.2.10 → 1.2.12
  5. HmIP-BROLL 1.8.20 → 1.10.8 as stated by Simon_B

At least for 1. & 4. the firmware is currently transferred to my devices. If there are changes I can notice, I will inform you.

Today i got these messages:

2023-04-24 11:40:35.350 [WARN ] [ternal.handler.HomematicThingHandler] - Channel not found for datapoint '00111BE99286E5:0#ERROR_OVERLOAD'

2023-04-24 11:40:35.703 [ERROR] [ternal.handler.HomematicThingHandler] - Can't convert INTEGER value '' with DecimalTypeConverter for '00111BE99286E5:3#SECTION'

org.openhab.binding.homematic.internal.converter.ConverterTypeException: Can't convert INTEGER value '' with DecimalTypeConverter for '00111BE99286E5:3#SECTION'

	at org.openhab.binding.homematic.internal.converter.type.AbstractTypeConverter.convertFromBinding(AbstractTypeConverter.java:120) ~[?:?]

	at org.openhab.binding.homematic.internal.handler.HomematicThingHandler.updateChannelState(HomematicThingHandler.java:468) ~[?:?]

	at org.openhab.binding.homematic.internal.handler.HomematicThingHandler.updateDatapointState(HomematicThingHandler.java:411) ~[?:?]

	at org.openhab.binding.homematic.internal.handler.HomematicBridgeHandler.onStateUpdated(HomematicBridgeHandler.java:281) ~[?:?]

	at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.lambda$1(AbstractHomematicGateway.java:744) ~[?:?]

	at org.openhab.binding.homematic.internal.misc.DelayedExecuter.start(DelayedExecuter.java:65) ~[?:?]

	at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.eventReceived(AbstractHomematicGateway.java:741) ~[?:?]

	at org.openhab.binding.homematic.internal.communicator.server.RpcResponseHandler.handleEvent(RpcResponseHandler.java:98) ~[?:?]

	at org.openhab.binding.homematic.internal.communicator.server.RpcResponseHandler.handleMethodCall(RpcResponseHandler.java:51) ~[?:?]

	at org.openhab.binding.homematic.internal.communicator.server.RpcResponseHandler.handleMethodCall(RpcResponseHandler.java:68) ~[?:?]

	at org.openhab.binding.homematic.internal.communicator.server.XmlRpcServer$ResponseHandler.handle(XmlRpcServer.java:125) ~[?:?]

	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) ~[bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.server.Server.handle(Server.java:516) ~[bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:487) ~[bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:732) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:479) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:409) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034) [bundleFile:9.4.46.v20220331]

	at java.lang.Thread.run(Thread.java:829) [?:?]

2023-04-24 11:41:56.923 [WARN ] [ternal.handler.HomematicThingHandler] - Channel not found for datapoint '00111BE99286DD:0#ERROR_OVERLOAD'

2023-04-24 11:41:57.279 [ERROR] [ternal.handler.HomematicThingHandler] - Can't convert INTEGER value '' with DecimalTypeConverter for '00111BE99286DD:3#SECTION'

org.openhab.binding.homematic.internal.converter.ConverterTypeException: Can't convert INTEGER value '' with DecimalTypeConverter for '00111BE99286DD:3#SECTION'

	at org.openhab.binding.homematic.internal.converter.type.AbstractTypeConverter.convertFromBinding(AbstractTypeConverter.java:120) ~[?:?]

	at org.openhab.binding.homematic.internal.handler.HomematicThingHandler.updateChannelState(HomematicThingHandler.java:468) ~[?:?]

	at org.openhab.binding.homematic.internal.handler.HomematicThingHandler.updateDatapointState(HomematicThingHandler.java:411) ~[?:?]

	at org.openhab.binding.homematic.internal.handler.HomematicBridgeHandler.onStateUpdated(HomematicBridgeHandler.java:281) ~[?:?]

	at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.lambda$1(AbstractHomematicGateway.java:744) ~[?:?]

	at org.openhab.binding.homematic.internal.misc.DelayedExecuter.start(DelayedExecuter.java:65) ~[?:?]

	at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.eventReceived(AbstractHomematicGateway.java:741) ~[?:?]

	at org.openhab.binding.homematic.internal.communicator.server.RpcResponseHandler.handleEvent(RpcResponseHandler.java:98) ~[?:?]

	at org.openhab.binding.homematic.internal.communicator.server.RpcResponseHandler.handleMethodCall(RpcResponseHandler.java:51) ~[?:?]

	at org.openhab.binding.homematic.internal.communicator.server.RpcResponseHandler.handleMethodCall(RpcResponseHandler.java:68) ~[?:?]

	at org.openhab.binding.homematic.internal.communicator.server.XmlRpcServer$ResponseHandler.handle(XmlRpcServer.java:125) ~[?:?]

	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) ~[bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.server.Server.handle(Server.java:516) ~[bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:487) ~[bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:732) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:479) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:409) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034) [bundleFile:9.4.46.v20220331]

	at java.lang.Thread.run(Thread.java:829) [?:?]

Hey, did you get any updates?

Same for me since updating HmIP-BROLL to Version 1.10.8.

I have the same error since the update of the firmware. Any idea how to fix?

Anyone could help with this errror:

2023-06-02 16:13:01.087 [ERROR] [ternal.handler.HomematicThingHandler] - Can't convert INTEGER value '' with DecimalTypeConverter for '00111BE99286DD:3#SECTION'

org.openhab.binding.homematic.internal.converter.ConverterTypeException: Can't convert INTEGER value '' with DecimalTypeConverter for '00111BE99286DD:3#SECTION'

	at org.openhab.binding.homematic.internal.converter.type.AbstractTypeConverter.convertFromBinding(AbstractTypeConverter.java:120) ~[?:?]

	at org.openhab.binding.homematic.internal.handler.HomematicThingHandler.updateChannelState(HomematicThingHandler.java:468) ~[?:?]

	at org.openhab.binding.homematic.internal.handler.HomematicThingHandler.updateDatapointState(HomematicThingHandler.java:411) ~[?:?]

	at org.openhab.binding.homematic.internal.handler.HomematicBridgeHandler.onStateUpdated(HomematicBridgeHandler.java:281) ~[?:?]

	at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.lambda$1(AbstractHomematicGateway.java:744) ~[?:?]

	at org.openhab.binding.homematic.internal.misc.DelayedExecuter.start(DelayedExecuter.java:65) ~[?:?]

	at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.eventReceived(AbstractHomematicGateway.java:741) ~[?:?]

	at org.openhab.binding.homematic.internal.communicator.server.RpcResponseHandler.handleEvent(RpcResponseHandler.java:98) ~[?:?]

	at org.openhab.binding.homematic.internal.communicator.server.RpcResponseHandler.handleMethodCall(RpcResponseHandler.java:51) ~[?:?]

	at org.openhab.binding.homematic.internal.communicator.server.RpcResponseHandler.handleMethodCall(RpcResponseHandler.java:68) ~[?:?]

	at org.openhab.binding.homematic.internal.communicator.server.XmlRpcServer$ResponseHandler.handle(XmlRpcServer.java:125) ~[?:?]

	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) ~[bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.server.Server.handle(Server.java:516) ~[bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:487) ~[bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:732) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:479) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:409) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883) [bundleFile:9.4.46.v20220331]

	at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034) [bundleFile:9.4.46.v20220331]

	at java.lang.Thread.run(Thread.java:829) [?:?]

I have enabled TRACE log, but cant find the reason.
I dont even use the datapoint ‘00111BE99286DD:3#SECTION’

2023-06-16 20:03:01.085 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'false' for '00111BE99286DD:0#UNREACH' from gateway with id '3014F711A0001F58A9A71BCE'

			00111BE99286DD:3

			00111BE99286DD:3

			00111BE99286DD:3

			00111BE99286DD:3

			00111BE99286DD:3

			00111BE99286DD:3

2023-06-16 20:03:01.088 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value '1' for '00111BE99286DD:3#SECTION_STATUS' from gateway with id '3014F711A0001F58A9A71BCE'

2023-06-16 20:03:01.089 [TRACE] [converter.type.AbstractTypeConverter] - Converting datapoint '00111BE99286DD:3#SECTION_STATUS' (dpType='ENUM', dpUnit='null', dpValue='1') with StringTypeConverter

2023-06-16 20:03:01.089 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Double) value '0.955' for '00111BE99286DD:3#LEVEL' from gateway with id '3014F711A0001F58A9A71BCE'

2023-06-16 20:03:01.089 [TRACE] [converter.type.AbstractTypeConverter] - Converting datapoint '00111BE99286DD:3#LEVEL' (dpType='FLOAT', dpUnit='100%', dpValue='0.955') with PercentTypeConverter

2023-06-16 20:03:01.089 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value '0' for '00111BE99286DD:3#LEVEL_STATUS' from gateway with id '3014F711A0001F58A9A71BCE'

2023-06-16 20:03:01.090 [TRACE] [converter.type.AbstractTypeConverter] - Converting datapoint '00111BE99286DD:3#LEVEL_STATUS' (dpType='ENUM', dpUnit='null', dpValue='0') with StringTypeConverter

2023-06-16 20:03:01.090 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (String) value '' for '00111BE99286DD:3#SECTION' from gateway with id '3014F711A0001F58A9A71BCE'

2023-06-16 20:03:01.090 [TRACE] [converter.type.AbstractTypeConverter] - Converting datapoint '00111BE99286DD:3#SECTION' (dpType='INTEGER', dpUnit='null', dpValue='') with DecimalTypeConverter

2023-06-16 20:03:01.090 [ERROR] [ternal.handler.HomematicThingHandler] - Can't convert INTEGER value '' with DecimalTypeConverter for '00111BE99286DD:3#SECTION'

org.openhab.binding.homematic.internal.converter.ConverterTypeException: Can't convert INTEGER value '' with DecimalTypeConverter for '00111BE99286DD:3#SECTION'

2023-06-16 20:03:01.092 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value '1' for '00111BE99286DD:3#PROCESS' from gateway with id '3014F711A0001F58A9A71BCE'

2023-06-16 20:03:01.092 [TRACE] [converter.type.AbstractTypeConverter] - Converting datapoint '00111BE99286DD:3#PROCESS' (dpType='ENUM', dpUnit='null', dpValue='1') with StringTypeConverter

2023-06-16 20:03:01.093 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value '1' for '00111BE99286DD:3#ACTIVITY_STATE' from gateway with id '3014F711A0001F58A9A71BCE'

2023-06-16 20:03:01.093 [TRACE] [converter.type.AbstractTypeConverter] - Converting datapoint '00111BE99286DD:3#ACTIVITY_STATE' (dpType='ENUM', dpUnit='null', dpValue='1') with StringTypeConverter

			00111BE99286DD:4

			00111BE99286DD:4

			00111BE99286DD:4

			00111BE99286DD:4

			00111BE99286DD:4

			00111BE99286DD:4

2023-06-16 20:03:01.096 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value '0' for '00111BE99286DD:4#SECTION_STATUS' from gateway with id '3014F711A0001F58A9A71BCE'

2023-06-16 20:03:01.097 [TRACE] [converter.type.AbstractTypeConverter] - Converting datapoint '00111BE99286DD:4#SECTION_STATUS' (dpType='ENUM', dpUnit='null', dpValue='0') with StringTypeConverter

2023-06-16 20:03:01.097 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Double) value '1.0' for '00111BE99286DD:4#LEVEL' from gateway with id '3014F711A0001F58A9A71BCE'

2023-06-16 20:03:01.098 [TRACE] [converter.type.AbstractTypeConverter] - Converting datapoint '00111BE99286DD:4#LEVEL' (dpType='FLOAT', dpUnit='100%', dpValue='1.0') with PercentTypeConverter

2023-06-16 20:03:01.098 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value '0' for '00111BE99286DD:4#LEVEL_STATUS' from gateway with id '3014F711A0001F58A9A71BCE'

2023-06-16 20:03:01.099 [TRACE] [converter.type.AbstractTypeConverter] - Converting datapoint '00111BE99286DD:4#LEVEL_STATUS' (dpType='ENUM', dpUnit='null', dpValue='0') with StringTypeConverter

2023-06-16 20:03:01.099 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value '3' for '00111BE99286DD:4#SECTION' from gateway with id '3014F711A0001F58A9A71BCE'

2023-06-16 20:03:01.099 [TRACE] [converter.type.AbstractTypeConverter] - Converting datapoint '00111BE99286DD:4#SECTION' (dpType='INTEGER', dpUnit='null', dpValue='3') with DecimalTypeConverter

2023-06-16 20:03:01.099 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value '1' for '00111BE99286DD:4#PROCESS' from gateway with id '3014F711A0001F58A9A71BCE'
2023-06-16 20:07:26.137 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (String) value '' for '00111BE99286DD:3#SECTION' from gateway with id '3014F711A0001F58A9A71BCE'

2023-06-16 20:07:26.137 [ERROR] [ternal.handler.HomematicThingHandler] - Can't convert INTEGER value '' with DecimalTypeConverter for '00111BE99286DD:3#SECTION'

org.openhab.binding.homematic.internal.converter.ConverterTypeException: Can't convert INTEGER value '' with DecimalTypeConverter for '00111BE99286DD:3#SECTION'

Any Help would be nice.
Regards
Simon

Got the same „problem“ with ‘ERROR_OVERLOAD’ being spammed into the logs.
This behavior started with the update 1.10.16 of my HmIP-BROLLs.
I came from an old version so it could‘ve come with the earlier version mentioned above.

1 Like

Was there any progress with this?
I also have repeated log messages
[WARN ] [ternal.handler.HomematicThingHandler] - Channel not found for datapoint ‘00111D89B79D02:0#ERROR_OVERLOAD’
with Version 1.10.16 on a HmIP-BROLL.
Other Rollershutters with Version 1.10.16 on a HmIP-BROLL-2 seem to be okay.
This seems to be the same as