Advanced Zigbee CT driver can't setLevel to 0

🛎️ Get Help
1

I tried migrating all of my Osram Lightify CT can lights to the Advanced Zigbee CT Bulb driver. Everything looked good after hitting configure for each bulb. The issue I have is when my automation sends a setLevel to 0 to a group of the bulbs.

Scenario: I have my lights turned off by setting level to 0 so that when they turn on again, they can dim up to the level I have a global variable set to. When my automation runs, they dim to off, then come back on to 5%. Also, there is no log entry for any events which occur from my automations or groups with these bulbs now.

I suspect this may have something to do with the new preference parameter of minimum level, which defaults to 5, and can't be set lower. Is it possibly forcing the light to dim no lower than 5%?

I'd love to use these new drivers for the new features they provide, but this definitely won't work. Any ideas are appreciated

Thanks,
Jon

2

0 is not a ledgimate level for a bulb, some in fact will honor that level but remain on...
When 0 is used in setLevel with these drivers, it's used as a proxy for off, but with an optional fade rate.
I can add some lower minimum options, but they will work the same way, 0 cant be a minimum.

1 Like
3

Thanks, @mike.maxwell. I appreciate what you are saying about some bulbs not working with setLevel of 0. With the old Generic driver, this worked fine for all of my bulbs. I don't know if I ever noticed whether they ever show as off when setLevel to 0 is used.

I like that I can use setLevel 0 as a proxy for off with the added benefit of the fade rate because I want to do exactly that.

What do you suggest I do to achieve this without using setLevel to 0?

Thanks Again,
Jon

4

I would just stick with the drivers you were using before.

5

OK. Thanks. That's unfortunate.

6

Could you add a 1%? That would be great.

7

@mike.maxwell, another vote for 1% minimum level option in the Advanced Zigbee drivers.

Thanks
Jim

1 Like
8

My hub logs are 100% clean - no errors with a single exception and I'd like to ID the problem.
I've a Sylvania Smart A19 Tunable White bulb which operates normally and doesn't give me any trouble - but generates this:

image
image960×128 3.39 KB

Has anyone seen / resolved this?
ava.lang.ArithmeticException: Division by zero on line 643 (method setColorTemperature)

(my driver is customized - I freely admit. I changed the CT color range tables to match Amazon but thats nearly brain-dead changes)

9

what version of the driver are you using?, the most recent one was released in platform 2.2.8 and the source in our public repo updated shortly after.

It's likely you're using an older version of the driver prior to implementing the three parameter setColorTemperature.
if that's not the case then you'll have to post the driver code you're using.

10

Whoa, there's a public repo?? Man I must have completely overlooked this.

11

:man_facepalming:t3:

1 Like
12

Ah, I've seen this one. Thought maybe they published their full library and not just the generics.

1 Like
13

Nope, just limited go-by / examples (for the most part).

14

Yea, there are a lot of little things I'd like to tweak for my own personal use but I don't want to do it all from scratch. Maybe when my ocd kicks in sometime in the future I'll get around to it.

2 Likes
15

Hi - darn - For a second I thought you'd solved it easily but I'm using a mod'd version of the latest. My only changes are in the name array from lines 63 - 76 originally.
a link to the code I use (i have 5 of these bulbs):

16

what command and parameters exactly are you using, and from where are you trying to execute it (driver, app ect)?