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

[andyzlen]

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

[fibu-freak]

Is there a solution in the mean time ?

[andyzlen]

Unfortunately not - as you can see this issue is still open. My only workaround for now is to ignore the warnings and to wait for a solution before I activate my other 3 HmIP-SWDs.

[fibu-freak]

It's very curious, as this error/warning comes up when I added my second Thing (HmIP-SWDO-I). Have you tried a third one to install and looked what happened ?

[andyzlen]

First - we have to distinguish between the two Homematic products which have different datapoints:

• HmIP-SWD => Water sensor
• HmIP-SWDO / HmIP-SWDO-I => Window / door contact

Second - I had a similar effect like you described with another device type (HmIP-PS): after installation of a second HmIP-PS a datapoint error occured - due to different firmware versions of both devices => my advice: check firmware of your devices, for each device type update to the same version (possibly you have to unteach/teach device).
Third - since the HmIP-SWD datapoint error appeared I installed other devices (e.g. 3 HmIP-BROLL): no installation issues with them, HmIP-SWD datapoint error still remains.

[fibu-freak]

Thank's for reply.
You are right. I have different Firmware-Versions (SWDO=1.12.1 and SWDO-I=1.16.10). But both Versions are the actual ones for the single products. For additional tests I will buy another SWDO within the next days.
But I don't think that this is the problem at all, as I get the same warning as you, although I have neither SWD nor PS installed:
2019-05-10 [WARN ]- Can't set value for datapoint '00109A498AE754:M_1#ALARM_MODE_ZONE_6' 2019-05-10 [WARN ]- Can't set value for datapoint '00109A498AE754:M_1#ALARM_MODE_ZONE_5' 2019-05-10 [WARN ]- Can't set value for datapoint '00109A498AE754:M_1#ALARM_MODE_ZONE_7' 2019-05-10 [WARN ]- Can't set value for datapoint '00109A498AE754:M_1#ALARM_MODE_ZONE_2' 2019-05-10 [WARN ]- Can't set value for datapoint '00109A498AE754:M_1#ALARM_MODE_ZONE_1' 2019-05-10 [WARN ]- Can't set value for datapoint '00109A498AE754:M_1#ALARM_MODE_TYPE' 2019-05-10 [WARN ]- Can't set value for datapoint '00109A498AE754:M_1#ALARM_MODE_ZONE_4' 2019-05-10 [WARN ]- Can't set value for datapoint '00109A498AE754:M_1#ALARM_MODE_ZONE_3'

[andyzlen]

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.

[fibu-freak]

I can confirm it's a SWDO-I.
As I didn't find what latest version of my SWDO-I is, I called the Support of Homematic today and they approved me Version1.16.10 to be the newest one.
I'll keep you informed when installing the next SWDO

[Taxi99fe]

Hello everybody
I have to report a similar problem:
I work with several HmIP-SMO and HmIP-SMO-A (Motion-Sensor, Firmware 1.2.8).
After each call "Reload_All_From_HM_Gateway" the error appears per sensor:
…: M_1#ALARM_MODE_TYPE'
…: M_1#ALARM_MODE_ZONE_1 … M_1#ALARM_MODE_ZONE_7
(work with OpenHAB 2.4 on Synology).
At the same time a second error is reported:
HM-Sen-RD-O (Rain-Sensor, Firmware 1.4)
"Can not load values for device: OEQ0xxxxx, channel: 2, paramset: MASTER, maybe there are no values available".
Nevertheless: Thank you for the very good software!

[fibu-freak]

As the Warning message comes up after installing a SWDO-I with Firmware-Version .1.16.10 it also was produced after I upgrated my SWDO from 1.12.1 to 1.16.8. As this is the latest Version according to Homematic-Support.
Installing two new SWDO's (V.1.16.8) the the Warning-Message appears for those devices too.
As in the Homematic IP Devices Technical Documentation no such Channels are listed for those devices.
Maybe @gerrieg or @davidgraeff have any ideas what the reasons for those warnings could be.

[FaHuSchmidt]

Same problem here.
I have 13 HmIP-SWDO-I devices, all at firmware version 1.16.10.
Running Openhab 2.4.0 over Docker on Synology nas.

[fibu-freak]

It seems that no one knows something about this fault or is willing to help.
What a pity

[MHerbst]

Let me try to ping the code owners: @FStolte @gerrieg @mdicke2s

[fibu-freak]

Meanwhile there is a new Documentation from Homematic here. Where the Parameters are described on Side 8571, but I don't know how to handle within openHAB ore elsewhere.

[NStiens]

This bug still exists. Can someone please help? Or is there any workaround?

[fibu-freak]

Problem still exists, but nobody seems to be inetrrested in. As a workaround you can change the log of the homematic-binding to "Error" in the console.
log:set error org.openhab.binding.homematic

[MHerbst]

Unfortunately none of the code owners has reacted yet. I am working my way into the binding and will see if I can solve the problem. It may take a few more days and I may need more information.

[fibu-freak]

Martin, thx for your help. What additional information do you need ? Can I help in any way ?

[lobocobra]

same issue here but the sensors seem to work. So is it only an issue in the log, or does something actually not work?
Log says in addition...
[WARN ] [ematic.handler.HomematicThingHandler] - Could not reinitialize the device '0000D7099A2DAF': Total timeout 15000 ms elapsed

Device is....
HMIP-SWDO |   | 0000D7099A2DAF | 1.16.8

It seems to be a problem with homematic IP contacts ? The older homematic door-contacts do not show the issue?
=> I moved recently from ccu2 original to ccu3 on raspberry 3b

I would bet, that following error is related...
[ERROR] [ommunicator.AbstractHomematicGateway] - Total timeout 15000 ms elapsed
=> I tried this... maybe it works?????

[fibu-freak]

@lobocobra , can't say if it's the same problem, as I'm using an original CCU3. I will keep an eye on the log, if I can find a similar Warning/Error.
What do you mean with this ? => I tried this... maybe it works?????

[Sschhsd]

Same issue here. Any fixes planed?

[chrostek]

Same issue here with HmIPW-FIO6 and HmIPW-DRI32
everything works, but as i have many of this devices it spams the logfiles

[chrostek]

Maybe this Log-Snippet with TRACE enabled helps:

<?xml version="1.0" encoding="ISO-8859-1"?><methodResponse><params><param><value><struct><member><name>REPEATED_LONG_PRESS_TIMEOUT_UNIT</name><value><i4>2</i4></value></member><member><name>CHANNEL_OPERATION_MODE</name><value><i4>3</i4></value></member><member><name>EVENT_DELAY_UNIT</name><value><i4>0</i4></value></member><member><name>EVENT_DELAY_VALUE</name><value><i4>0</i4></value></member><member><name>CONTACT_BOOST</name><value><boolean>0</boolean></value></member><member><name>MSG_FOR_POS_B</name><value><i4>2</i4></value></member><member><name>ALARM_MODE_ZONE_6</name><value><boolean>0</boolean></value></member><member><name>MSG_FOR_POS_A</name><value><i4>1</i4></value></member><member><name>ALARM_MODE_ZONE_5</name><value><boolean>0</boolean></value></member><member><name>ALARM_MODE_ZONE_7</name><value><boolean>0</boolean></value></member><member><name>LONG_PRESS_TIME</name><value><double>0.4</double></value></member><member><name>ALARM_MODE_ZONE_2</name><value><boolean>0</boolean></value></member><member><name>ALARM_MODE_ZONE_1</name><value><boolean>0</boolean></value></member><member><name>ALARM_MODE_TYPE</name><value><i4>0</i4></value></member><member><name>ALARM_MODE_ZONE_4</name><value><boolean>0</boolean></value></member><member><name>ALARM_MODE_ZONE_3</name><value><boolean>0</boolean></value></member><member><name>REPEATED_LONG_PRESS_TIMEOUT_VALUE</name><value><i4>2</i4></value></member><member><name>DBL_PRESS_TIME</name><value><double>0.0</double></value></member></struct></value></param></params></methodResponse>
2020-06-10 15:31:17.989 [WARN ] [ommunicator.parser.GetParamsetParser] - Can't set value for datapoint '00171A49949ABC:M_2#ALARM_MODE_ZONE_6'
2020-06-10 15:31:17.989 [WARN ] [ommunicator.parser.GetParamsetParser] - Can't set value for datapoint '00171A49949ABC:M_2#ALARM_MODE_ZONE_5'
2020-06-10 15:31:17.989 [WARN ] [ommunicator.parser.GetParamsetParser] - Can't set value for datapoint '00171A49949ABC:M_2#ALARM_MODE_ZONE_7'
2020-06-10 15:31:17.990 [WARN ] [ommunicator.parser.GetParamsetParser] - Can't set value for datapoint '00171A49949ABC:M_2#ALARM_MODE_ZONE_2'
2020-06-10 15:31:17.990 [WARN ] [ommunicator.parser.GetParamsetParser] - Can't set value for datapoint '00171A49949ABC:M_2#ALARM_MODE_ZONE_1'
2020-06-10 15:31:17.990 [WARN ] [ommunicator.parser.GetParamsetParser] - Can't set value for datapoint '00171A49949ABC:M_2#ALARM_MODE_TYPE'
2020-06-10 15:31:17.990 [WARN ] [ommunicator.parser.GetParamsetParser] - Can't set value for datapoint '00171A49949ABC:M_2#ALARM_MODE_ZONE_4'
2020-06-10 15:31:17.991 [WARN ] [ommunicator.parser.GetParamsetParser] - Can't set value for datapoint '00171A49949ABC:M_2#ALARM_MODE_ZONE_3'

[MHerbst]

@chrostek Can you try it with enabled DEBUG mode and attach the log information before the warning is displayed. These messages are only issued if the CCU sends more information then expected and this is a bit weird.

[chrostek]

@MHerbst i made a re-init with debug loglevel. from line 684 on is what you search:

openhab.log

[MHerbst]

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:

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

[fibu-freak]

@MHerbst
I sent you a trace-log directly via mail as a zip-file.

[MHerbst]

@fibu-freak I am sorry, but I did not receive any mail. Please try it again

[Taxi99fe]

I only loaded the download from your link. Otherwise my addons were empty.
I work on a NUC with Ubuntu 20.04 and the stable version 2.5.8.
The warnings are caused by three HmIP-SMO-A.
The application runs on a CCU2 under 2.53.27.
Sorry, but I'm a total software layman.
Do you need more information?

[MHerbst]

@Taxi99fe Did you uninstall the binding in PaperUI and did you clean up the cache directory before copying the jar to the addons folder? You can check the loaded add on if you connect to the openHAB console and enter bundl:list | grep Homematic.

[Taxi99fe]

The HmIP-SMO-A has the SW 1.2.8

[Taxi99fe]

No, I didn't do it right.
I'm trying to uninstall and reinstall it again.
I'll be in touch ...
PS: how do I delete the cash? I just restarted the NUC. That is probably not enough

[MHerbst]

You can either use linux command to remove the content of the cache directory. Or you can use this command: openhab-cli clean-cache. After that you have to restart openHAB.

[Taxi99fe]

OK, I uninstall and reinstall it again, in between I emptied the cache.
after the restart from Openhab (all 10'):
No warning!
That was my fault! Sorry for the effort.
Thanks for the patience with beginners.
If anything should appear, I would contact you again.
Greetings, Urs

[Taxi99fe]

After a few hours I can confirm that the warnings for all IP components no longer appear.
Perfect and a big thank you!

Information and two warnings are still logged:

2020-08-31 10:40:18.411 [INFO ] [ommunicator.AbstractHomematicGateway] - Can not load values for device: OEQ0216411, channel: 2, paramset: MASTER, maybe there are no values available
2020-08-31 10:40:19.486 [WARN ] [ommunicator.parser.GetParamsetParser] - Can't set value for datapoint 'OEQ1530178:M_-1#CENTRAL_ADDRESS' interface WIRED
2020-08-31 10:40:32.426 [WARN ] [ommunicator.parser.GetParamsetParser] - Can't set value for datapoint 'OEQ0853316:M_-1#CENTRAL_ADDRESS' interface WIRED

Tings:
Thing HM-Sen-RD-O OEQ0216411 "HM-CCU2 Regensensor (OG1 Balkon)" @ "Garten"
Thing HMW-IO-12-Sw14-DR OEQ0853316 "HM-CCU2-WR IO 12-/14-ch (UG)" @ "UG"
Thing HMW-IO-12-Sw14-DR OEQ1530178 "HM-CCU2-WR IO 12-/14-ch (UG)" @ "UG"

Trigger of the message: (for me every 10 ')
Reload_All_From_HM_Gateway.sendCommand(ON)

However, this has no effect on the function of my system. Everything works fine.
A blemish remains in the log file.
Thank you and have a nice day; greetings, Urs

[andyzle]

@MHerbst Thank you for all the work to fix this issue. Thanks to all who supported him.
@MHerbst Is this fix already merged in 2.5.9 snapshot version?

Regards,
Andy

[MHerbst]

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

[Elle4u]

@Elle4u I can add HM-Sec-MDIR-2 and suppress the message.

@MHerbst That would be nice.

You have not updated the code, yet, did you?
Please let me know if some additional information is missing.

Markus

[MHerbst]

@Taxi99fe Good to hear that it working. For the additional messages please open a new issue (otherwise I probably forget to solve it). They are issued because the binding only suppresses these messages for HmIP components, but these are "WIRED" components where currently no exceptions have been added.

[MHerbst]

@Elle4u I have updated it and it has already been merged. Should be available in the latest snapshot build for 2.5.9.

[Boldfor]

I have updated it and it has already been merged. Should be available in the latest snapshot build for 2.5.9.

@MHerbst, sorry for bringing up this annoying topic again, but the bug which I read above got fixed appears in my log. (OH 3.2.0 Release Build on Raspi 3 / Docker). Not sure if it appeared in my log from when I bought the sensor or not, but now I have the following regular log entry for the Homematic HmIP-SWDM:

22:20:06.184 [WARN ] [communicator.parser.GetParamsetParser] - Can't set value for datapoint '00155D89919AB1:0#UPDATE_PENDING'

I read through the following two threads https://community.openhab.org/t/cant-set-value-for-datapoint-00109a498ae754-m-1-alarm-mode-type/74873 and https://community.openhab.org/t/homematic-binding-cant-set-value-for-datapoint-warning-for-master-parameter/42145, tried to a) remove / add the sensor/thing and b) removed the binding, cleaned the cache (/userdata/tmp and /userdata/cache) and installed the binding again. Nothing helped.

Does anyone have an idea?

[MHerbst]

@Boldfor Please don't add new comments to already closed issues, especiall when the issue is different.

I have added a comment with a bypass to the forum thread: https://community.openhab.org/t/homematic-binding-cant-set-value-for-datapoint-warning-for-master-parameter/42145/11?u=mherbst

[Boldfor]

@MHerbst , thanks for the advice. I assumed the root cause is identical.