-
-
Notifications
You must be signed in to change notification settings - Fork 190
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
Mueller Remote Control 404049D Color #2229
Comments
I am afraid I do not understand the question, nor can I read the linked data. Please rephrase the question with more details
A. |
Hi A. messages is {"colorx":39898,"colory":17393}
the old Remote control extracts directly the color as HEX value, for example #ff6600 in the object data
i need to know, how we can convert the color x and color y to RGB ? Mod Edit: Code Tags |
Please do the following:
|
result:
Mod Edit: Code Tags. Please post code and log entries in multiline code tags for readability |
Which adapter version are you using ? |
usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001CD4077E-if00, have on another raspberrypi a 2652P, same result.
how do you mean to tag the code entries? this is the downloaded log. mod edit: corrected code tags |
what I mean is this: first paste the data in, then mark the data (all of it) and use the code tag button (<>) to encapsulate it. Github will automatically select the correct code tag (single-line or multi-line) A |
|
I am afraid at this point I cannot do anything else to help. The device seems to work as advertised from zigbee2mqtt.io. Possible issues with the exposes may require attention, but that requires a device to fix, which I do not have Without being able to test, you can check here for a conversion method: A. |
result after press the rgb button in the messages i find colorx and colory. where can i find or figure out the new color, for example colorx with 39020 is no rgb color.
Result in the messages is {"colorx":39898,"colory":17393}
zigbee_message.txt
thank you for your support
The text was updated successfully, but these errors were encountered: