All of a sudden homematic IP eTRV2 warnings in openhab.log

I recently updated to OH 5.1.0 w/o issues. Yesterday my CCU3 (version 3.79.x) started to behave strangely (tried to change Temp settings on a legacy HM-CC-RT-DN via web interface which were simply ignored). So I updated it to 3.85.7 (current version). This did not solve the problem so I restarted the CCU3 using the web interface again. The CCU3 did not come up again so I had to powercycle it. It then came up as expected. I restarted OH afterwards. Now openhab.log is flooded with messages like this:

2026-01-09 10:39:48.325 [WARN ] [ternal.handler.HomematicThingHandler] - Channel 
not found for datapoint ‘000xxxxxxxxxxx:1#VALVE_STATE_TOO_TIGHT’
2026-01-09 10:39:48.326 [WARN ] [ternal.handler.HomematicThingHandler] - Channel 
not found for datapoint ‘000xxxxxxxxxxx:1#VALVE_STATE_ADJUSTMENT_TOO_BIG’
2026-01-09 10:39:48.326 [WARN ] [ternal.handler.HomematicThingHandler] - Channel 
not found for datapoint ‘000xxxxxxxxxxx:1#VALVE_STATE_ERROR_POSITION’
2026-01-09 10:39:48.327 [WARN ] [ternal.handler.HomematicThingHandler] - Channel 
not found for datapoint ‘000xxxxxxxxxxx:1#VALVE_STATE_ADJUSTMENT_TOO_SMALL’

I rebooted the CCU3 and openhab again this morning but that did not help.

I have about 50 Thermocontrollers attached so I would like to avoid removing and adding them …

Any suggestions ?

Just removed one HmIP eTRV-2 and registered it again at the CCU3: no difference. Neither helped deleting the cache (while OpenHAB was stopped) nor rebooting the eTRV-2 alone.

The error seems to be complaining that the device is reporting a new value from Homeatic, but there is no Channel on the Thing to represent that data. I would try to remove the Thing and then rediscover/recreate the Thing and see if these new Channels are added to the Thing.

Thx - that was it.