I get some new warnings during startup since the upgrade to build #1232 (maybe #1231). These warnings didn’t exist on previous builds (was on #1222 or #1224 before).
[ommunicator.parser.GetParamsetParser] - Can't set value for datapoint 'OEQ0299850:M_0#P3_TEMPERATURE_WEDNESDAY_6
These messages repeat for each master parameter, so it’s quite a mass, hundreds of log messages. That’s why i am sure these warnings didn’t exist before.
I’m running Homegear Nightly 0.8.0-2108.
Please post the relevant items / rules / things / etc.
The only relevant thing is the Thing, this is a Wall thermostat hm-tc-it-wm-eu. No rules or items involved.
The master parameters are usually not accessible from openHAB. And they also weren’t logged as warnings before.
Maybe @gerrieg is working on including them into openHAB?
I have the same problem / issue …
No rules involved; Using homegear as ccu replacement and the latest openhab version 2.3
Thomas
Are you also using some quite new homegear nightly?
I Think so. just updates oh to the latest nightlies on a more or less regular basis
This error occurs, when the gateway sends wrong metadata (getParamset / getParamsetDescription), so it’s a Homegear issue. It has no effect on the functionality of the binding itself, it can only not read the values from the MASTER datapoints at startup.
The master parameters are usually not accessible from openHAB.
They are only available via PaperUI (Configuration Parameters)
Thanks i created a thread in the homegear forum:
https://forum.homegear.eu/t/homegear-openhab2-kommunikation/1989
I’m facing with the same problem, but in my case with the official ccu2 box.
log message
[WARN ] [ommunicator.parser.GetParamsetParser] - Can’t set value for datapoint ‘NEQXXXXXXXX:1#NEXT_TRANSMISSION’
homematic.things
Thing HM-Sec-MDIR-2 NEQXXXXXXXX “LR Motion Sensor Hallway” @ “Hallway”
I’m facing the same problem (on Docker / Raspberry), but with HmIP-SWDM (Window and Door Contact with magnet)
22:20:06.184 [WARN ] [communicator.parser.GetParamsetParser] - Can't set value for datapoint '00155D89919AB1:0#UPDATE_PENDING'
What I tried already to get rid of the error, but so far without success:
Both did not work / still getting the same error message.
Anyone by any chance have an idea? Since I’ll be getting more of these sensors it’d be great to not have the log flooded with these error messages.
The binding retrieves all information about the available datapoints and their configuration from the CCU (or Homgear). If the metadata contains wrong information, e.g. that UPDATE_PENDING is writeable then problems like this can occur.
Therefore it would be interesting to see what the CCU returns. Can you execute the following steps:
As a bypass you can set the minimum log level for the class issueing the warning messages to ERROR, e.g. with log:set ERROR org.openhab.binding.homematic.internal.communicator.parser.GetParamsetParser.
I think I have an similar issue here. It’s since the update to 3.2.0, I think.
If I press my button for a long time, now, this information is logged:
2021-12-23 10:04:51.156 [INFO ] [openhab.event.ChannelTriggeredEvent ] - homematic:HmIPW-DRI16:CCU3:0016D8A9A4B6FA:2#BUTTON triggered LONG_PRESSED
2021-12-23 10:04:51.470 [INFO ] [openhab.event.ChannelTriggeredEvent ] - homematic:HmIPW-DRI16:CCU3:0016D8A9A4B6FA:2#BUTTON triggered LONG_PRESSED
2021-12-23 10:04:53.176 [INFO ] [openhab.event.ChannelTriggeredEvent ] - homematic:HmIPW-DRI16:CCU3:0016D8A9A4B6FA:2#BUTTON triggered LONG_RELEASED
2021-12-23 10:04:53.230 [INFO ] [openhab.event.ChannelTriggeredEvent ] - homematic:HmIPW-DRI16:CCU3:0016D8A9A4B6FA:2#BUTTON triggered LONG_PRESSED
OpenHab.Log:
2021-12-23 10:04:51.167 [WARN ] [ternal.handler.HomematicThingHandler] - Channel not found for datapoint '0016D8A9A4B6FA:2#PRESS_LONG_START'
2021-12-23 10:04:51.169 [WARN ] [irtual.ButtonVirtualDatapointHandler] - Unexpected vaule 'LONG_START' for PRESS virtual datapoint
2021-12-23 10:04:53.173 [WARN ] [ternal.handler.HomematicThingHandler] - Channel not found for datapoint '0016D8A9A4B6FA:2#PRESS_LONG_START'
2021-12-23 10:04:57.676 [WARN ] [ternal.handler.HomematicThingHandler] - Channel not found for datapoint '0016D8A9A4B6FA:2#PRESS_LONG_RELEASE'
2021-12-23 10:04:59.682 [WARN ] [ternal.handler.HomematicThingHandler] - Channel not found for datapoint '0016D8A9A4B6FA:2#PRESS_LONG_RELEASE'
Now the event “LONG_PRESSED” fires 3 times in a rule… The button is pressed only one long time…
I allready cleared the cache and reinstalled the addon.
I sent you the log file via PM due to its size, hoping it’s what you had in mind. The log starts shortly before starting the scan and stops after scan (which re-revealed the respective HmIP-SWDM).
@elle4u Maybe this problem is more related to this PR: [homematic] Remove double press events and improve long press events for button trigger by maniac103 · Pull Request #11186 · openhab/openhab-addons · GitHub
@maniac103 Can you have look at this problem? You have more experience with the button devices.
Unfortunately the interesting part is missing in the log file. It seems that the discovery process was finished but not the creation of the devices when you copied the log file. The creation is an asynchronous process and can issue message even if the discovery has finished.
The CCU returns an information about the SWDM but I can see no further action.
Can you search in the log file for a line like this:
2021-12-24 14:38:33.849 [TRACE] [ommunicator.AbstractHomematicGateway] - HmDevice[hmInterface=HMIP,address=xxxxxx,type=HmIP-SWDM,name=rmware=2.6.2,gatewayId=CCU]
Important is the value of attribute “type”.
If you find this line, please scroll up until “Client XmlResponse” (I need the following XML data) and down until you see an entry
HmDatapoint[name=UPDATE_PENDING
This one will be interesting, especially the value of readOnly.
I would also help if you can get the part of the log file where the warning is issued. Especially the lines before the message. About 50 lines should be sufficient.
@MHerbst Sure.
@Elle4u I’d need a trace log of the long press process - enable trace, long press the button, disable trace, post log … thanks 
I sent you the entire logs again via PM due to their size, since I suspected that, in case I just send you an extract of what I believe you requested, I might have missed something important. The first log is from “adding the thing” again, the second log is from “scanning and adding the thing again”.
Let me know if I can assist any further.
Thanks. The gist of it is this:
2021-12-28 13:29:13.291 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'true' for '00171BE99324D8:1#PRESS_LONG' from gateway with id 'CCU3'
2021-12-28 13:29:13.293 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG, value true, button state null -> LONG_PRESSED
2021-12-28 13:29:13.309 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'true' for '00171BE99324D8:1#PRESS_LONG_START' from gateway with id 'CCU3'
2021-12-28 13:29:13.311 [WARN ] [irtual.ButtonVirtualDatapointHandler] - Unexpected vaule 'LONG_START' for PRESS virtual datapoint
2021-12-28 13:29:13.312 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG_START, value true, button state LONG_PRESSED -> null
2021-12-28 13:29:13.534 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'true' for '00171BE99324D8:1#PRESS_LONG' from gateway with id 'CCU3'
2021-12-28 13:29:13.537 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG, value true, button state null -> LONG_PRESSED
2021-12-28 13:29:13.794 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'true' for '00171BE99324D8:1#PRESS_LONG' from gateway with id 'CCU3'
2021-12-28 13:29:13.797 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG, value true, button state LONG_PRESSED -> LONG_PRESSED
2021-12-28 13:29:14.043 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'true' for '00171BE99324D8:1#PRESS_LONG' from gateway with id 'CCU3'
2021-12-28 13:29:14.045 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG, value true, button state LONG_PRESSED -> LONG_PRESSED
2021-12-28 13:29:14.294 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'true' for '00171BE99324D8:1#PRESS_LONG' from gateway with id 'CCU3'
2021-12-28 13:29:14.297 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG, value true, button state LONG_PRESSED -> LONG_PRESSED
2021-12-28 13:29:14.523 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'true' for '00171BE99324D8:1#PRESS_LONG' from gateway with id 'CCU3'
2021-12-28 13:29:14.524 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG, value true, button state LONG_PRESSED -> LONG_PRESSED
2021-12-28 13:29:14.778 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'true' for '00171BE99324D8:1#PRESS_LONG' from gateway with id 'CCU3'
2021-12-28 13:29:14.781 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG, value true, button state LONG_PRESSED -> LONG_PRESSED
2021-12-28 13:29:15.037 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'true' for '00171BE99324D8:1#PRESS_LONG' from gateway with id 'CCU3'
2021-12-28 13:29:15.040 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG, value true, button state LONG_PRESSED -> LONG_PRESSED
2021-12-28 13:29:15.262 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'true' for '00171BE99324D8:1#PRESS_LONG' from gateway with id 'CCU3'
2021-12-28 13:29:15.264 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG, value true, button state LONG_PRESSED -> LONG_PRESSED
2021-12-28 13:29:15.317 [DEBUG] [ematic.internal.misc.DelayedExecuter] - Executing delayed event for '00171BE99324D8:1#PRESS_LONG_START'
2021-12-28 13:29:15.320 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG_START, value false, button state LONG_PRESSED -> LONG_RELEASED
2021-12-28 13:29:15.537 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'true' for '00171BE99324D8:1#PRESS_LONG' from gateway with id 'CCU3'
2021-12-28 13:29:15.539 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG, value true, button state LONG_RELEASED -> LONG_PRESSED
2021-12-28 13:29:15.785 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'true' for '00171BE99324D8:1#PRESS_LONG' from gateway with id 'CCU3'
2021-12-28 13:29:15.787 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG, value true, button state LONG_PRESSED -> LONG_PRESSED
2021-12-28 13:29:16.050 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'true' for '00171BE99324D8:1#PRESS_LONG' from gateway with id 'CCU3'
2021-12-28 13:29:16.052 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG, value true, button state LONG_PRESSED -> LONG_PRESSED
2021-12-28 13:29:16.292 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'true' for '00171BE99324D8:1#PRESS_LONG' from gateway with id 'CCU3'
2021-12-28 13:29:16.294 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG, value true, button state LONG_PRESSED -> LONG_PRESSED
2021-12-28 13:29:16.537 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'true' for '00171BE99324D8:1#PRESS_LONG' from gateway with id 'CCU3'
2021-12-28 13:29:16.539 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG, value true, button state LONG_PRESSED -> LONG_PRESSED
2021-12-28 13:29:16.790 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'true' for '00171BE99324D8:1#PRESS_LONG' from gateway with id 'CCU3'
2021-12-28 13:29:16.792 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG, value true, button state LONG_PRESSED -> LONG_PRESSED
2021-12-28 13:29:17.034 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'true' for '00171BE99324D8:1#PRESS_LONG' from gateway with id 'CCU3'
2021-12-28 13:29:17.036 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG, value true, button state LONG_PRESSED -> LONG_PRESSED
2021-12-28 13:29:17.583 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'true' for '00171BE99324D8:1#PRESS_LONG_RELEASE' from gateway with id 'CCU3'
2021-12-28 13:29:17.585 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG_RELEASE, value true, button state LONG_PRESSED -> LONG_RELEASED
2021-12-28 13:29:19.045 [DEBUG] [ematic.internal.misc.DelayedExecuter] - Executing delayed event for '00171BE99324D8:1#PRESS_LONG'
2021-12-28 13:29:19.047 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG, value false, button state LONG_RELEASED -> null
2021-12-28 13:29:19.590 [DEBUG] [ematic.internal.misc.DelayedExecuter] - Executing delayed event for '00171BE99324D8:1#PRESS_LONG_RELEASE'
2021-12-28 13:29:19.594 [DEBUG] [irtual.ButtonVirtualDatapointHandler] - Handled virtual button event on 00171BE99324D8:1: press type LONG_RELEASE, value false, button state null -> null
So HMIP works differently than HM in this regard: HM sends LONG - CONT for repetition - LONG_RELEASE, HMIP sends LONG_START - LONG for repetition - LONG_RELEASE.
I guess previously you got more than one LONG_PRESSED event for each long press as well, right? (I think that’s the case because the binding didn’t handle LONG_START before either).
Either way, I’ll think about a solution for this that is compatible with both HM and HMIP.