I have been able to get the On/Off status, color temperature, but I am not able to read the RGB status.I don't understand that about xy and then being able to convert it to 3 bytes to use it on KNX screens.
Can anybody help me?
Thank you so much in advance,
I'm trying to use xy_to_rgb from user.hue v2.lua. But I can't be doing it right. I have copied the function into common functions. Then I have in the event script:
But I get the excact same rgb value wether I have red or blue light. (255,0,0) or (0,0,255) gives the same rgb value. But the lamp is red or blue correctly. For colours without blue the result makes sense I think, but it seems like blue and red is mixed up somehow.
Value of variable rgb is 16711680 for both (255,0,0) and (0,0,255)...
I can see that the x and y values differ (45913,19614) for red and (8880,2613) for blue - so the result shouldn't be equal...
Well, looking more into this I now understand that the xy coordinates should be less than 1 - and that's the main problem. Don't know where these numbers come from, or what I can do with them... Help!
(and my Gira devices...) the 6 byte DPT 251.600 should have 0-100 as value for the different colours. Unlike 232.600 which is 0-255... Yay for consistency from KNX...
Unless I'm mistaken (which I very much could be...) it would be awesome if this could be fixed in the next FW release
25.09.2024, 07:31 (This post was last modified: 25.09.2024, 07:41 by stianj.)
Might be... But Gira sends (and expects) 0-100. But that might be their bug, I don't have anything else to compare with.
(But why is the DPT 232.600 showing expected value to be 0-255, while DPT 251.600 shows 0-100 in the specifications?)
Seems atleast a MDT Dali controller does the same: https://community.openhab.org/t/rgbw-col...600/150055
I still think I'm right about the 6 bit DALI RGBW DPT...
But anyways, your xytorgb() works very good. I have not been comparing input and output, because that doesn't really matter, but I just noticed that for different green colours, I usually get the same feedback anyways...
rgb(0 149 48) gives me x=11049, y=44152
rgb(0 255 0) gives me x=11299, y=48940
But running both these coordinates through xytorgb() gives me 0,255,0 as feedback...
As I wrote, I understand that it's impossible to match input and feedback 100%, but I feel this should have been better..?
MDT is brand labeling this from IPAS and they have new firmware which is fixing this bug. Check if MDT already released latest version.
Same works correct on SE (also IPAS branded) version.