Aeotec LED Strip RGBWW #300
Comments
|
The same thing, mqttthing =) |
|
Using the test RGBWW accessory in test/config.json: {
"accessory": "mqttthing",
"type": "lightbulb-RGBWW",
"name": "Test RGBWW Light",
"url": "http://192.168.10.35:1883",
"topics": {
"getRGBWW": "test/rgbwwlight/rgb",
"setRGBWW": "test/rgbwwlight/rgb/set"
},
"logMqtt": true
},... I'm definitely seeing values for all 5 channels as I drag around the colour wheel: ... so it seems to be working as intended. Ah, sorry, I've just read your description again. If I'm now understanding correctly, you're saying that the Aeotec LED strip can't cope with this: it wants EITHER warm white and cold white values (and zero R,G,B) OR red, green and blue values (and zero WW,CW). This can't be done at the moment, but it doesn't sound too hard to add in theory. |
|
Thanks David - yep you got it, if there are WW/CW values, RGB is ignored. RGB works in a pinch i.e. if i drag all the way out to the edges in Home.app UI where its pure colour it'll RGB because the WW/CW channels are 0. And I can use the colour temp UI to pick a white colour But yeah the big zone in the middle of the colour picker is useless because it splits off some values to white channels - even though it could in theory be expressed as RGB, right? So yeah, I think it's just a mismatch between Home.app/homekit expectations and this hardware. |
|
Thanks. I've just been playing with this. I've added a new {
"accessory": "mqttthing",
"type": "lightbulb-RGBWW",
"name": "Test RGBWW Light",
"url": "http://192.168.10.35:1883",
"topics": {
"getRGBWW": "test/rgbwwlight/rgb",
"setRGBWW": "test/rgbwwlight/rgb/set"
},
"whiteMix": false,
"logMqtt": true
} |
|
What a boss! Let me know whats the easiest way for me to pull and test this for you when you're ready. |
|
It's a pretty minor change, so I've just published it in a new release (1.1.18). Let me know how you get on! |
|
(P.S. I see you are also messing with muti-service stuff. For the record I tried to add a multi-service accessory for my Aeotec trisensor - light, motion etc. and ran into a homebridge error about "cannot create a service with the same uuid" even though the service names etc. are different. Let me know if you want me to write that up for you). |
Actually in this case it's a mismatch between mqttthing and the hardware. Mqttthing is trying to be clever by extracting the white components, which can work well when the hardware supports it! Sadly while Homekit helpfully provides the colour temperature for a white light, as soon as you create a coloured light it just provides hue, saturation and value. |
That's odd. Yes, if you post your config and some sample MQTT messages in another issue I'll take a look... |
Thanks, I assume homebridge will pick this up when it gets pushed to NPM? Or want me to test it first |
|
Should be there now - I made a silly error with the release, but hopefully all fixed now! |
|
Definite improvement, two small places where I get interesting behaviour Near the orange-y/warmwhite colours in the RGB wheel I can see it flipping back between the RGB and WW/CW channels. mqttthing must its close enough to white to send to white channels instead. And at lower intensities/brightness, it seems to be swap over to white a bit sooner from other colours (e.g. here, dragging inwards to center from purple): If i increase the brightness when I hit this point it will flip back to the RGB LEDs RE: the comment on the commit: Anyways, pretty minor stuff but a big improvement to what it was, if you have any other thoughts or changes I'm happy to test em. |
|
I've added threshold values for the next release, allowing configuration of the switching point between RGB and WW/CW lights. |
|
Thank you |
I'm using homebridge-mqttthing to speak to an Aeotec LED strip via ZWave2MQTT.
The communication works great, but I'm having an issue mapping its expectations into Homebridge.
Specifically, the device expects an RGBWW value for its configuration, and I'm configuring that as
However, the wrinkle is that on this system, either the RGB LEDs, OR the WW/CW LEDs get used - never both at the same time. If there is a value on the WW/CW channel, the RGB LEDs will never turn on.
This doesn't work so great with HomeKits UI (e.g. the colour wheel) etc. Unless the WW/CW values are absolute 0 in the RGBWW parameter, the RGB will not work. Perhaps there is some way to do this with
coldWhiteandwarmWhitevalues? Do I need to configure this as a multi-service accessory?I have some other issues but I can solve those after I get this one straightened out. Any advice appreciated.
The text was updated successfully, but these errors were encountered: