HmIP-RGBW MISSING_NON_OPTIONAL_PARAMETER

[derDennis99]

Describe the bug
I am trying to set the saturation for the HmIP-RGBW device via IoBroker VIS. It is entered as a percentage (whole numbers). However, I get the error in the image.

To Reproduce
Steps to reproduce the behavior:

1. Go to the HmIP-RGBW device, in the object tree and I change the % value there manually.
2. Then I go to the log and see the error as in the picture

Expected behavior
I would have expected the new value to be transferred to the HmIP device.

Screenshots & Logfiles

Versions:

• hm-rpc version: 1.15.19
• hm-rega version: 4.0.0
• JS-Controller version:
• Node version: v16.20.2
• Operating system: Raspbian GNU/Linux 11 (bullseye)
• CCU model: raspberrymatic
• CCU firmware: 3.69.7.108

Additional context
I have also tried to enter a 5000. However, it doesn't seem to be able to cope with the value that is defined as "FLOAT".

[derDennis99]

Six months later... No answer and the problem is still there. Why can't you simply adapt the data types?

[Apollon77]

You are sure it is about data types? Why?

An alternative reading of the error could be that it is not enough to just set auturation and more parameters needs to be provided in order to set it, so Ithink it could be informative to see the exact definition of that device. So maybe a debug log of a full "resync" of the devcies with the CCU might be an interstsing log to add here to provide more information and insight.

And PS: "six month later" ... yes ... and interestingly you still seem to be the only user affected by the issue ... So please take a breath, think about what the developer could do with the information above and without owning such a device. And yes also developers are just people that try to do all this in their free time and so a github issue in the flood of issues we normally work on can easiely be missed.

[derDennis99]

I understand your perspective and thank you for the explanation. It's certainly not easy to deal with all the different requests and issues that developers face. My intention was not to blame, but simply to express my frustration that the issue has not been resolved after so long. (Especially when I think of the price of Homematic devices).

Regarding your question about why I think there might be a problem with the data types: Since the input is an integer, while the error message indicates an inability to handle the value defined as "FLOAT", this seemed like a possible cause to me.

However, if there are other possible explanations, I am of course open to learning more about them. For example, it would be interesting to see what other parameters are required to set the saturation. Therefore, I agree with you that a more precise definition of the device could be helpful.

The Homematic devices were bought with certain expectations and it is frustrating not to be able to use them as expected. I am willing to provide more information or help with testing to arrive at a solution.

PS: The problem seems to have occurred over a year ago with someone else. (https://forum.iobroker.net/topic/64779/fehler-im-adapter-homematic-rpc-mit-hmip-rgbw)

[jwlzlawl]

I bought the RGBW Controller a few weeks ago and also met the problem described.

If I can support the developers in any way, just let me know. Because I would really appreciate a solution, soon. :)

[Manuel1607]

I also have the same problem

[tehmilcho]

hey,

i got the same when i try to change the SATURATION to 100% or 99%.

hm-rpc.0
2024-06-24 15:30:03.944 error Cannot call setValue: XML-RPC fault: Generic error (MISSING_NON_OPTIONAL_PARAMETER)

hm-rpc.0
2024-06-24 15:30:03.943 error xmlrpc -> setValue ["XXXXXXXXXXX:1","SATURATION",0.99] FLOAT

{
"type": "state",
"common": {
"name": "XXXXXXXXXXXX:1.SATURATION",
"role": "",
"def": 0,
"type": "number",
"read": true,
"write": true,
"min": 0,
"max": 100,
"unit": "%"
},
"native": {
"MIN": 0,
"UNIT": "100%",
"OPERATIONS": 7,
"MAX": 1.01,
"FLAGS": 1,
"ID": "SATURATION",
"TYPE": "FLOAT",
"DEFAULT": 0,
"CONTROL": "UNIVERSAL_LIGHT_RECEIVER.SATURATION"
},
"from": "system.adapter.hm-rega.0",
"user": "system.user.admin",
"ts": 1719090269719,
"_id": "hm-rpc.0.XXXXXXXXXXXXXX.1.SATURATION",
"acl": {
"object": 1636,
"state": 1636,
"owner": "system.user.admin",
"ownerGroup": "system.group.administrator"
}
}

i also tried a other Value "RAMP_TIME_TO_OFF_VALUE" and changed it from 0 to 1 but its the same

hm-rpc.0
2024-06-24 15:40:31.274 error Cannot call setValue: XML-RPC fault: Generic error (MISSING_NON_OPTIONAL_PARAMETER)

hm-rpc.0
2024-06-24 15:40:31.274 error xmlrpc -> setValue ["0033E0C9923FAF:1","RAMP_TIME_TO_OFF_VALUE",1] INTEGER

[Nunmalfix]

I also have the same issue.

[Armin2229]

Ich habe auch das gleiche Problem. Ich hoffe es gibt bald eine Lösung hierfür.