-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[homematic] Error CUXD Virtuelle Devices homematic:VIR-LG-xxx #9137
Comments
Hi Thorsten, I would assume that this error is returned from the CCU resp. CuxD. Can you please enable the DEBUG log mode and send an excerpt from openhab.log where I can see what happens before and after this error message. I don't have that much experience with Cuxd but maybe the log can help to find the reason. |
Hello MHerbst, I hope this help to find the reason..... the last messages repeats some more often.... `==> /openhab/userdata/logs/openhab.log <== 2020-11-27 18:07:04.303 [ERROR] [ternal.handler.HomematicThingHandler] - Can't find datapoint for thing property CUX2801008:M_3#EXEC_ON_CHANGE 2020-11-27 18:07:04.309 [ERROR] [ternal.handler.HomematicThingHandler] - Can't find datapoint for thing property CUX2801008:M_4#MAX_VAL 2020-11-27 18:07:04.312 [ERROR] [ternal.handler.HomematicThingHandler] - Can't find datapoint for thing property CUX2801008:M_5#MAX_VAL 2020-11-27 18:07:04.317 [ERROR] [ternal.handler.HomematicThingHandler] - Can't find datapoint for thing property CUX2801008:M_3#MAX_VAL 2020-11-27 18:07:04.328 [ERROR] [ternal.handler.HomematicThingHandler] - Can't find datapoint for thing property CUX2801008:M_2#EXEC_ON_CHANGE 2020-11-27 18:07:04.332 [ERROR] [ternal.handler.HomematicThingHandler] - Can't find datapoint for thing property CUX2801008:M_5#EXEC_ON_CHANGE 2020-11-27 18:07:04.337 [ERROR] [ternal.handler.HomematicThingHandler] - Can't find datapoint for thing property CUX2801008:M_4#EXEC_ON_CHANGE 2020-11-27 18:07:04.343 [ERROR] [ternal.handler.HomematicThingHandler] - Can't find datapoint for thing property CUX2801008:M_2#MAX_VAL ==> /openhab/userdata/logs/events.log <== 2020-11-27 18:07:04.366 [hingStatusInfoChangedEvent] - 'homematic:VIR-LG-RGBW-DIM:3014F711A0001F58A9A7127D:CUX2801008' changed from OFFLINE (COMMUNICATION_ERROR): -4 Unknown parameter (sending getValue() CUX2801008:1 CMD_RETS ) to ONLINE 2020-11-27 18:07:04.404 [hingStatusInfoChangedEvent] - 'homematic:VIR-LG-RGBW-DIM:3014F711A0001F58A9A7127D:CUX2801008' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): -4 Unknown parameter (sending getValue() CUX2801008:1 CMD_RETS ) 2020-11-27 18:07:04.408 [hingStatusInfoChangedEvent] - 'homematic:VIR-LG-RGBW-DIM:3014F711A0001F58A9A7127D:CUX2801008' changed from OFFLINE (COMMUNICATION_ERROR): -4 Unknown parameter (sending getValue() CUX2801008:1 CMD_RETS ) to ONLINE 2020-11-27 18:07:04.443 [hingStatusInfoChangedEvent] - 'homematic:VIR-LG-RGBW-DIM:3014F711A0001F58A9A7127D:CUX2801008' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): -4 Unknown parameter (sending getValue() CUX2801008:1 CMD_RETS ) 2020-11-27 18:07:04.447 [hingStatusInfoChangedEvent] - 'homematic:VIR-LG-RGBW-DIM:3014F711A0001F58A9A7127D:CUX2801008' changed from OFFLINE (COMMUNICATION_ERROR): -4 Unknown parameter (sending getValue() CUX2801008:1 CMD_RETS ) to ONLINE 2020-11-27 18:07:04.463 [hingStatusInfoChangedEvent] - 'homematic:VIR-LG-RGBW-DIM:3014F711A0001F58A9A7127D:CUX2801008' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): -4 Unknown parameter (sending getValue() CUX2801008:1 CMD_RETS ) 2020-11-27 18:07:04.470 [hingStatusInfoChangedEvent] - 'homematic:VIR-LG-RGBW-DIM:3014F711A0001F58A9A7127D:CUX2801008' changed from OFFLINE (COMMUNICATION_ERROR): -4 Unknown parameter (sending getValue() CUX2801008:1 CMD_RETS ) to ONLINE 2020-11-27 18:07:04.488 [hingStatusInfoChangedEvent] - 'homematic:VIR-LG-RGBW-DIM:3014F711A0001F58A9A7127D:CUX2801008' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): -4 Unknown parameter (sending getValue() CUX2801008:1 CMD_RETS )` |
Hello, ok, in CUXD it is possible a "VIR-LG-RGBW-DIM", but in the background you can use different base devices with other parameters. It is possible to clear that for a special device type and reimport it ? |
The binding asks the CCU for a list of the devices and their data points. It then creates things + channels based on this information.
You can delete the thing in openHAB and run a new discovery. Then the thing is created completely new. The unknown data points seem to be similar to a problem with HmIP devices (#5048). There were also data points that could not be used as channels (they had a "M_" in their name, too). They seem to be thing configuration data points. I think I could enhance to binding to ignore these data points. Currently, I only a development environment for OH 3. Will have to see whether I can set up an environment for OH 2.5. |
Hallo, no problem, I have the same problem in my OH 3 M2 Test instance (docker). But I think it could be an other problem: At the CUxD Documnetation I found the following:
Here an similar Problem with device type (28) https://openhabforum.de/viewtopic.php?t=3295 Cloud be this the problem ? Thank you Regards |
Hello, I made a test.... setting the datapoint with Homematic script dom.GetObject ("CUxD.CUX2801005:1.CMD_QUERY_RET").State (1); |
I am quite sure that this is the problem. As far as I know there is no special treatment for special CUxD devices like this. I think I will have to install CUxD and have a closer look into it. |
Hello, i have CCU3 with raspberrymatic and installed OpenHab with Homematic Binding I'm using Cuxd with many Devices Type "(28) System" and i'm surprised thas Things has still problems with them (also tried newes snapshot, but no success) COMMUNICATION_ERROR Is there a workaround or will this problem be fixed soon? thank you! |
I did not find enough time for this problem. It will probably a bit complicated to solve this problem. The binding is not prepared to send a special value for a data point before it can retrieve it. |
Thaink you for your fast reply. I hope you find the time in the near future, i‘m certainly not the only one who would be excited when the bug fixed. I wait patiently 😉 |
As this is a rather old issue, it might have been fixed. Can you confirm this is still an issue with most recent stable (openHAB 4.2.0) |
Hello, sorry I could not confirm this, because I removed CUxD (and VIRT- Devices) from my Homematic. Should I also close this issue ? |
LEt's close it for now, if someone else encounters this, we can always re-open. Thanks for your quick response! |
Hello,
I use OH 2.5.10 on docker and homematic (Raspberrymatic Version 3.53.34.20201121 = latest release on RPI3)
I have some virtual CUxD Devices Type (28) System --> Exec for controlling hue lights (or light groups) via an Hue Addon (j-a-n).
Virtual Devices like...
VIR-LG-RGBW-DIM
VIR-LG-WHITE-DIM
....
This virtual device type are the only ones to have a homematic control for color and color temperature...
After the initial adding as thing, the thing directly get a communication error
"-4 Unknown parameter (sending getValue() CUX2801008:1 CMD_RETS )"
Any idea how to solve this ?
Thank you
Regards
Thorsten
The text was updated successfully, but these errors were encountered: