Advanced Zigbee RGBW Bulb with Ledvance Mini Garden Pole

Hi,
I have an issue with "this" driver. Actually also the Generic Zigbee RGB, hence my guess is: it's the device. The Ledvance Mini Garden Pole connects just fine. But I cannot chose colors or at least they don't match the chosen one at all. Furthermore, and for me most important: I cannot chose Color Temp. For example the color is blue (which it is after connecting the device), and I but in 2700K, the device driver page goes from "color: blue" to "color: CT", but the device just shows blue.
I also have an older Osram Mini Garden Pole and this actually works fine wiht the Advanced Zigbee RGBW driver. I have another Ledvance Set, which has the same issues. I think and would expect that this could be fixed with some minor changes to this integrated driver to build a custom one? Or what do you think is the problem here?

Really, nobody can help with this?

Perhaps the newer models don't support fully adjustable color temperature?
Some product data I found mentions two specific color temperatures.
We don't have any drivers that support two specific static value color temperatures, all of them are for fully adjustable color temperature devices.

Thanks for your reply! You mean this part from the product page "Control of the color temperature from warm white 2000 K to daylight white 6500 K, dimming and RGB color change"?
I don't think that this means fixed 2000K or 65000K but fully variable from 2k to 6500K.

no, it was another one, anyway, if that product description is the exact device/model/firmware you have then its a faulty device...
There is only one set of Zigbee color temperature commands in both the ZHA/ZLL and Zigbee 3.0, so I have no idea what's up with the specific device you have.

If you loan it to me I can try to figure it out...

I have two of them and both do/behave exactly the same. I don't think that both are faulty?!

Thanks for your offer, but the shipping costs to the US are a bit high for that one (I might get back to you about the aqara window sensors though!).

EDIT:

State Variables

  • tt : {level=0A00, RGB=0A00, off=0A00, colorTemperature=0A00, on=0A00}
  • ct : {current=9900, requested=0, min=1901, max=6535}
  • hexColor : {requestedHue=00, requestedSaturation=00, currentHue=A9, currentSaturation=FE}
  • checkPhase : 0
  • lastSaturation : FE
  • lastHue : A9
  • groups : []
  • xyOnly : false
  • hexLevel : {current=33, requested=33}
  • lastAddress : 9E9C
  • lastCT : 0099

EDIT2:
dev:4922022-02-02 19:38:25.481 infoMini Pole 1 colorMode is RGB

dev:4922022-02-02 19:38:25.478 debugevt- rawValue:0, value: RGB, descT: Mini Pole 1 colorMode is RGB

dev:4922022-02-02 19:38:25.474 infoMini Pole 1 color is Blue

dev:4922022-02-02 19:38:25.463 debugparse description: read attr - raw: 9E9C0103000A08003000, dni: 9E9C, endpoint: 01, cluster: 0300, size: 0A, attrId: 0008, encoding: 30, command: 01, value: 00

dev:4922022-02-02 19:38:25.266 infoMini Pole 1 colorTemperature is 6535°K

dev:4922022-02-02 19:38:25.262 debugevt- rawValue:153, value: 6535, descT: Mini Pole 1 colorTemperature is 6535°K

dev:4922022-02-02 19:38:25.258 debugparse description: read attr - raw: 9E9C0103000C0700219900, dni: 9E9C, endpoint: 01, cluster: 0300, size: 0C, attrId: 0007, encoding: 21, command: 01, value: 9900

dev:4922022-02-02 19:38:25.068 infoMini Pole 1 saturation is 100%

dev:4922022-02-02 19:38:25.062 debugevt- rawValue:254, value: 100, descT: Mini Pole 1 saturation is 100%

dev:4922022-02-02 19:38:25.058 debugparse description: read attr - raw: 9E9C0103000A010020FE, dni: 9E9C, endpoint: 01, cluster: 0300, size: 0A, attrId: 0001, encoding: 20, command: 01, value: FE

dev:4922022-02-02 19:38:24.864 infoMini Pole 1 hue is 67%

dev:4922022-02-02 19:38:24.860 debugevt- rawValue:170, value: 67, descT: Mini Pole 1 hue is 67%

dev:4922022-02-02 19:38:24.857 debugparse description: read attr - raw: 9E9C0103000A000020AA, dni: 9E9C, endpoint: 01, cluster: 0300, size: 0A, attrId: 0000, encoding: 20, command: 01, value: AA

dev:4922022-02-02 19:38:24.664 infoMini Pole 1 is 100%

dev:4922022-02-02 19:38:24.658 debugevt- rawValue:254, value: 100, descT: Mini Pole 1 is 100%

dev:4922022-02-02 19:38:24.654 debugparse description: read attr - raw: 9E9C0100080A000020FE, dni: 9E9C, endpoint: 01, cluster: 0008, size: 0A, attrId: 0000, encoding: 20, command: 01, value: FE

dev:4922022-02-02 19:38:24.473 infoMini Pole 1 is on

dev:4922022-02-02 19:38:24.470 debugevt- rawValue:1, value: on, descT: Mini Pole 1 is on

dev:4922022-02-02 19:38:24.466 debugparse description: read attr - raw: 9E9C0100060A00001001, dni: 9E9C, endpoint: 01, cluster: 0006, size: 0A, attrId: 0000, encoding: 10, command: 01, value: 01

dev:4922022-02-02 19:38:24.255 debugparse description: catchall: 0104 0300 01 01 0040 00 9E9C 00 00 0000 07 01 8D000000

dev:4922022-02-02 19:38:24.101 debugparse description: catchall: 0104 0300 01 01 0040 00 9E9C 00 00 0000 07 01 8D000000

dev:4922022-02-02 19:38:23.851 debugparse description: catchall: 0104 0300 01 01 0040 00 9E9C 00 00 0000 07 01 8D000000

dev:4922022-02-02 19:38:23.650 debugparse description: catchall: 0104 0300 01 01 0040 00 9E9C 00 00 0000 07 01 8D000000

dev:4922022-02-02 19:38:23.448 debugparse description: catchall: 0104 0008 01 01 0040 00 9E9C 00 00 0000 07 01 00

dev:4922022-02-02 19:38:23.244 debugparse description: catchall: 0104 0006 01 01 0040 00 9E9C 00 00 0000 07 01 00

dev:4922022-02-02 19:38:23.030 debugparse description: catchall: 0000 8021 00 00 0040 00 9E9C 00 00 0000 00 00 C400

dev:4922022-02-02 19:38:22.834 debugparse description: catchall: 0000 8021 00 00 0040 00 9E9C 00 00 0000 00 00 C300

dev:4922022-02-02 19:38:22.651 debugparse description: catchall: 0000 8021 00 00 0040 00 9E9C 00 00 0000 00 00 C200

dev:4922022-02-02 19:38:22.543 debugrefresh()

dev:4922022-02-02 19:38:22.516 warnconfigure...

My LEDvance garden lights (sorry, I don't have the model in front of me) behave similarly, in that they ignore color temperature.

Well, but you are using them? Because I cannot use mine at all.

The device is reporting all values correctly. There doesn't appear to be any reason they wouldn't accept ct commands, unless they aren't actually making it to the device some how.

Hi,
for example with this:

colorName Red Mini Pole 1 color is Red DEVICE 2022-02-03 07:58:25.216 CET
level 93 % Mini Pole 1 was set to 93% DEVICE 2022-02-03 07:58:25.004 CET
saturation 97 % Mini Pole 1 saturation was set to 97% DEVICE 2022-02-03 07:58:24.804 CET
hue 1 % Mini Pole 1 hue was set to 1% DEVICE 2022-02-03 07:58:24.594 CET
switch on Mini Pole 1 was turned on DEVICE 2022-02-03 07:58:12.081 CET

I do not get red, but lime green. With another color I chose before (some kind of yellow), the poles did not put out any light at all:

colorName Yellow Mini Pole 1 color is Yellow DEVICE 2022-02-03 07:55:03.661 CET
level 83 % Mini Pole 1 was set to 83% DEVICE 2022-02-03 07:55:03.459 CET
saturation 86 % Mini Pole 1 saturation was set to 86% DEVICE 2022-02-03 07:55:03.257 CET
hue 19 % Mini Pole 1 hue was set to 19% DEVICE 2022-02-03 07:55:03.050 CET

The only difference I can find between the working poles and this one is in the state variables:

  • tt : {level=0A00, RGB=0A00, off=0A00, colorTemperature=0A00, on=0A00}
  • ct : {current=7201, requested=7201, min=2702, max=6535}
  • hexColor : {requestedHue=17, requestedSaturation=D0, currentHue=17, currentSaturation=D0}

vs

  • tt : {level=0A00, RGB=0A00, off=0A00, colorTemperature=0A00, on=0A00}
  • ct : {current=9900, requested=0, min=1901, max=6535}
  • hexColor : {requestedHue=00, requestedSaturation=00, currentHue=A9, currentSaturation=FE}

shouldn't the requested and current values be the same in both?

if the device was working yes.
in the case of the devices not producing the requested RGB color, this is most certainly an issue with the physical device.

Thanks a lot Mike! Then I will order another one and see what that does.

@mike.maxwell What did you do!?! It works. Seriously, I have no idea how and why. Yesterday morning, when I postet the example, it did not. Then yesterday evening I wanted to show this problem to my dad and couldn't because it just worked. The only thing I did was connecting the lights to the Zigbee controller part of the old unit. I wanted to know if it's a problem from the lights or the controller. The lights worked with the old controller, hence I figured: the controller. First I thougt maybe this was the trick. But when I tried the second new set, which did not work when I tried them some weeks ago and have not been connected to the old controller: they worked too! I have NO clue why. Since I posted this I tried the lights out after each FW update, because I hoped that they could work now. So it was not "tried once" situation. I reconnected them serveral times, tried different device handlers etc.

sometimes when ■■■■ knows I'm coming after it, it just starts working...

2 Likes

Is it possible to connect this backwards? I’m just thinking maybe it’s connection issues.

2 Likes

No, there is only one way to connect it.

Download the Hubitat app