@p4co86 yes I do, but I wish I would have more time for stuff like did 
However, I managed to wrap it up and fixed all of the noticed bugs, so you give it a try
-
Plugin for WIFI controlled LED light (IWY-Light)
-
Nice. Thank you very much, how can i install a pull?
Thanks. -
Yeah u can. Just clone it into node_modules, checkout alternative_ui and run npm install
-
If i set it on white, its to white lol. Shouldn’t white be ‘warm white’ aka 2700k? My hue’s are to white in white mode.
-
@sweebee said:
If i set it on white, its to white lol. Shouldn’t white be ‘warm white’ aka 2700k? My hue’s are to white in white mode.
Looks like hue doesn’t have a dedicated white mode, so white is just a predefined RGB value on the plugin level. What I try to say with this its hardcoded at this line: https://github.com/philip1986/pimatic-led-light/blob/hue/devices/hue.coffee#L78
Yeah probably you are right and this should be changed to something warmer. -
Yes that is easy. But somehow the rgb conversion is wrong for hue. I can’t get it to warm white (2700k) is always to yellow or pink.
I think this has to do with the saturation? In the hue api you can set the saturation so its not a hard yellow color.
-
the white on milight is warm white 2700k.
things i have noticed:
(lights are off) when i click white, the lights goes on, but the switch in the gui is still off. when i click color the lights are still off. this works.
when i change color on zone 0 the lights from zone 1,2 change to the setted color. but in the gui the color from zone1,2 has the old color, i thing they schould also changed in realtime like the color in zone 0 and the switches should also go on when i switch zone 0 on and off when i switch zone zero off.when i click white, the colorpoint change to yellow. maybe it is better to change in white. and the satuation for white should have a gradient from dark(black) to white. now it is from dark(yellow) to white.
Thanks for your effort.
-
@philip1986 as you said setWhite() sets the color to #FFFFFF which obviously is not warm white. I think it would be better to use the white() call of node-hue-api instead of tweaking the RGB value. For example:
# hueState(colorTemp, briPercent) where colorTemp is a value between 154 (cool) and 500 (warm) and briPercent is 0 to 100 hueState = hue.lightState.create().on().white(500, 100)I’ll change the code accordingly for testing
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@mwittig tested it myself and its works great
But the hue lights turn on after a restart of pimatic?
Edit: they were turned of in the hue app itself, but the led light plugin doesn’t poll the hue states. Is this hard to add? Polling the hue lights?
Hm, and when I go back to color the saturation is lower, so setting a high saturated color is not possible. For full hue control there are 3 sliders needed? 1 for brightness, 1 color and 1 saturation.
-
milight light is also turned on after resart.
-
@sweebee said:
but the led light plugin doesn’t poll the hue states. Is this hard to add? Polling the hue lights
I’ll take care of this soon. The base library used now supports to query the RGB color value
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
When playing with several MQTT dimmer, I got this result.
{ "id": 'object-with-lights' "name": 'Object with lights' "class": 'Dimmer' "lights": [ { "id or channel": 1, "name": "30W WW LED", "color-picker": false, "saturation": true, "OnOff": "true", "resolution": 256 }, { "id": 2, "name": "CW LED Strip", "color-picker": false, "saturation": true, "OnOff": "true", "resolution": 4096, "correction": "cie1931" }, { "id": 3, "name": "RGB LED", "color-picker": true, "saturation": true, "OnOff": "false", "correction": "gamma" }, { "id": 4, "name": "RGB", "color-picker": true, "saturation": false, "correction": "cie1931" } ] }Pimatic = Smart Home
-
@p4co86 said:
when i change color on zone 0 the lights from zone 1,2 change to the setted color. but in the gui the color from zone1,2 has the old color, i thing they schould also changed in realtime like the color in zone 0 and the switches should also go on when i switch zone 0 on and off when i switch zone zero off.
I don’t think its a good idea to support zone 0, in that way. I would mean to have direct interaction between devices. In my opinion thats the job of rules! So you would never add a device with zone 0 to pimatic, instead you add 1,2,3,4 and a dummy device. Than add rules to apply the commands to the dummy device to all zone devices.
-
ok, but the think with clicking the withe button should be fixed.
actually when i click withe the led goes on, but they should be off till i turn them on. -
@sweebee said:
Hm, and when I go back to color the saturation is lower, so setting a high saturated color is not possible. For full hue control there are 3 sliders needed? 1 for brightness, 1 color and 1 saturation.
Yes thats true, the saturation is hardcoded to 80%. I took this decision to keep the complexity low (for UI/UX and code). Maybe I could add a wider variety of colors (including saturation variation) in the already existing slider.
-
-
What i also noticed, dimming in white mode ddoes not work.
-
After restart the lights are in. but the GUI shows off. After trying to turn them in the GUI on so i can after that turn the lights off, the GUI switch is directly switching to off after turning in. But the lights are still in. There is no Chance to turn them off.
-
i’m trying to take control one of these milight-modules with pimatic
i upload the milight-sketch on the arduino, connect the NRF and know howto add it in pimatic
now I have arrived at the point where I didn’t how to get an “addr”
the serial output shows me
# OpenMiLight Receiver/Transmitter startingbut i have no remote to receive an “addr” and no idea how to get to it.
is it possible to synchronize the NRF-nano with the milight-module or does I need necessarily a remote??
