openhab-addons: [homematic] HmIP-SWD - Can't set value for datapoint ALARM_MODE_xxx

After creation of an Homematic Thing for the Homematic IP water sensor “HMIP-SWD” in my thing file I found folllowing warnings in openhab.log:

[ommunicator.parser.GetParamsetParser] - Can't set value for datapoint '001898A997FC9C:M_1#ALARM_MODE_TYPE'
[ommunicator.parser.GetParamsetParser] - Can't set value for datapoint '001898A997FC9C:M_1#ALARM_MODE_ZONE_1'
[ommunicator.parser.GetParamsetParser] - Can't set value for datapoint '001898A997FC9C:M_1#ALARM_MODE_ZONE_2'
[ommunicator.parser.GetParamsetParser] - Can't set value for datapoint '001898A997FC9C:M_1#ALARM_MODE_ZONE_3'
[ommunicator.parser.GetParamsetParser] - Can't set value for datapoint '001898A997FC9C:M_1#ALARM_MODE_ZONE_4'
[ommunicator.parser.GetParamsetParser] - Can't set value for datapoint '001898A997FC9C:M_1#ALARM_MODE_ZONE_5'
[ommunicator.parser.GetParamsetParser] - Can't set value for datapoint '001898A997FC9C:M_1#ALARM_MODE_ZONE_6'
[ommunicator.parser.GetParamsetParser] - Can't set value for datapoint '001898A997FC9C:M_1#ALARM_MODE_ZONE_7'

Remarkable: obviously for Homematic datapoint the channel number “M_1” was expected - which is not a digit seen in Homematic datapoints of other devices (channels of my other Homematic devices are working properly). Nevertheless PaperUI shows the corresponding thing is ONLINE, but the channels ALARM_MODE_x and ALARM_MODE_TYPE corresponding to the warnings were not detected for the Thing. Following channels were detected for the Thing:

homematic:HmIP-SWD:ccu:001898A997FC9C:
   0#
      ERROR_NON_FLAT_POSITIONING
      OPERATING_VOLTAGE
      RSSI_PEER
      DUTY_CYCLE
      DELETE_DEVICE_MODE
      CONFIG_PENDING
      DELETE_DEVICE
      RSSI_DEVICE
      BATTERY_TYPE
      OPERATING_VOLTAGE_STATUS
      UPDATE_PENDING
      ERROR_CODE
      RSSI
      FIRMWARE
      SIGNAL_STRENGTH
      INSTALL_TEST
      UNREACH
      LOW_BAT
   1#
      WATERLEVEL_DETECTED
      MOISTURE_DETECTED
      ALARMSTATE

Thing definition (omitted for things not related to this issue):

Bridge homematic:bridge:ccu "Homematic CCU2" [ gatewayAddress="Homematic-ccu2", bindAddress="0.0.0.0" ] {
	Thing GATEWAY-EXTRAS-CCU GWE00000000 "HomeMatic Gateway Extras"
	Thing HM-RCV-50 BidCoS-RF "HomeMatic CCU2"
	Thing HmIP-SWD 001898A997FC9C "HomeMatic Wassersensor 1"
}

My environment:

openHAB 2.4.0 (Release Build) on Raspberry PI3 with Raspbian Jessie
Homematic Binding version 0.10.0.201812191738 - snapshot from here

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 74 (26 by maintainers)

Commits related to this issue

[homematic] Checking of full datapoint name is necessary (#8331) * Test of address only was not sufficient. * Another exception for data point added. According to: https://github.com/openhab/openha... — committed to openhab/openhab-addons by MHerbst 4 years ago
[homematic] Better support for rollershutters + several smaller fixes (#8242) * Set bridge state to offline for duty cycle = -1 * Use correct type Contact for state channel of tilt sensor * Support... — committed to andrewfg/openhab-addons by MHerbst 4 years ago
[homematic] Checking of full datapoint name is necessary (#8331) * Test of address only was not sufficient. * Another exception for data point added. According to: https://github.com/openhab/openha... — committed to andrewfg/openhab-addons by MHerbst 4 years ago
[homematic] Better support for rollershutters + several smaller fixes (#8242) * Set bridge state to offline for duty cycle = -1 * Use correct type Contact for state channel of tilt sensor * Support... — committed to andrewfg/openhab-addons by MHerbst 4 years ago
[homematic] Checking of full datapoint name is necessary (#8331) * Test of address only was not sufficient. * Another exception for data point added. According to: https://github.com/openhab/openha... — committed to andrewfg/openhab-addons by MHerbst 4 years ago
[homematic] Better support for rollershutters + several smaller fixes (#8242) * Set bridge state to offline for duty cycle = -1 * Use correct type Contact for state channel of tilt sensor * Support... — committed to andrewfg/openhab-addons by MHerbst 4 years ago
[homematic] Checking of full datapoint name is necessary (#8331) * Test of address only was not sufficient. * Another exception for data point added. According to: https://github.com/openhab/openha... — committed to andrewfg/openhab-addons by MHerbst 4 years ago
[homematic] Better support for rollershutters + several smaller fixes (#8242) * Set bridge state to offline for duty cycle = -1 * Use correct type Contact for state channel of tilt sensor * Support... — committed to andrewfg/openhab-addons by MHerbst 4 years ago
[homematic] Checking of full datapoint name is necessary (#8331) * Test of address only was not sufficient. * Another exception for data point added. According to: https://github.com/openhab/openha... — committed to andrewfg/openhab-addons by MHerbst 4 years ago
[homematic] Better support for rollershutters + several smaller fixes (#8242) * Set bridge state to offline for duty cycle = -1 * Use correct type Contact for state channel of tilt sensor * Support... — committed to DaanMeijer/openhab-addons by MHerbst 4 years ago
[homematic] Checking of full datapoint name is necessary (#8331) * Test of address only was not sufficient. * Another exception for data point added. According to: https://github.com/openhab/openha... — committed to DaanMeijer/openhab-addons by MHerbst 4 years ago
[homematic] Better support for rollershutters + several smaller fixes (#8242) * Set bridge state to offline for duty cycle = -1 * Use correct type Contact for state channel of tilt sensor * Support... — committed to CSchlipp/openhab-addons by MHerbst 4 years ago
[homematic] Checking of full datapoint name is necessary (#8331) * Test of address only was not sufficient. * Another exception for data point added. According to: https://github.com/openhab/openha... — committed to CSchlipp/openhab-addons by MHerbst 4 years ago
[homematic] Better support for rollershutters + several smaller fixes (#8242) * Set bridge state to offline for duty cycle = -1 * Use correct type Contact for state channel of tilt sensor * Support... — committed to markus7017/openhab-addons by MHerbst 4 years ago
[homematic] Checking of full datapoint name is necessary (#8331) * Test of address only was not sufficient. * Another exception for data point added. According to: https://github.com/openhab/openha... — committed to markus7017/openhab-addons by MHerbst 4 years ago

Most upvoted comments

@fibu-freak Thanks, it’s exactly the same situation. I will try to find a way to get access to these data points. But it really seems that they are not directly accessible. In this case I will lower the log level for these messages to DEBUG to prevent the logs from getting cluttered.

MHerbst on Jul 20, 2020

@andyzle The PR has been merged two day ago. So I think it’s is included in the snapshot

MHerbst on Aug 31, 2020

@MHerbst Great! The “Can’t set value for datapoint 'xxxxxxxxxxxx:M_1#ALARM_MODE_ZONE_x” no longer exist in the log file! A thousand thanks for your dedicated work. Stay healthy!

henrydiesner on Aug 11, 2020

I am now quite sure that the problem is caused by the “M_” in the datapoints. Because I don’t have one of the devices that are causing the problem I would need a TRACE log from the device discovery. Please perform the following steps:

Remove one of the things that is causing this problem
Set log mode to TRACE
Run a a new discovery and add the thing
Post the log

MHerbst on Jul 11, 2020

OK, I see. But strange that you get this errors related to SWDO/-I devices. According to the newest Homematic IP Devices Technical Documentation those devices do not support any “ALARM_MODE_*” channel parameters, but SWDM devices. Can you confirm that HmIP device with ID 00109A498AE754 is an SWDO? By the way - newest SWDO firmware version you can find here (only on german FAQ page, see 1st FAQ, update at your own risk). Please let me know the result of your test with another SWDO.

andyzlen on May 10, 2019