Transition error in Generic Zigbee CT (dev)

🧰 Built-In Apps and Drivers
1

For the most part, I no longer touch or change my HE device.
for no obvious reason, I have 4 sengled CT bulbs in the hallway. I have been using the Advanced Zigbee CT Bulb driver for all 4 bulbs since I installed them more than 2 months ago.
I began seeing an error message for a divide by zero

image
image961×304 52.2 KB

I played around and could cause the error everytime by simple using the device panel to issue a colortemp change to something, such as 3000 or 4000. When I issue a colortemp change to 2000 (which is out of range for this bulb) the bulb goes to 2702. but a direct setting of the colortemp gives me an error.
I switched driver to Generic Zigbee CT bulb (dev). initially it was a bit flaky even after button mashing the 'configure'. I changed to 'Device' - cleared all - states, childs etc, then switched back to Generic and it cleared things eventually.
Once changed, the 'transition time' drop down was filled with 'Click to Set'. The choices are 500, 1, 1.5, 2 and 5. I set to 500MS. The resultant delay on the bulb was uncomfortable so I chose to turn it off.
When I returned to set 'Transition time' there is no '0' or off. If you select 'No Selection', it will jump to 1 second. There is no way to turn off this transition time.

image
image1102×673 28.8 KB

Secondarily - if HE would care to push the dev driver to the public examples pile - it would be a great template for me to write my own driver for this bulb, while being able to add features I've added to my other drivers and fix the colortemp table as I have done for my other 2 CT bulb brands.

2

The correct driver for these sengled bulbs is the Sengled Element Plus (legacy) or Sengled Element Plus driver.

3

thank you - I admit I'd forgotten about that driver - in my defense - a long while back when attempting to address load and performance, I 'standardized' all my CT devices to the Adv CT bulb driver which is what I use for my other 2 brands of CT bulbs. now that I've offloaded my HE in part to alexa it is not as critical that I attempt to be so efficient.

I'm grateful for the solve - however I'd like to kindly point out that this was a report of a transition bug in the driver, something someone may want to address for others who don't have the luck of the option to switch to a specific driver without the problem.

4

I understand, however I'm not able to replicate this issue when the driver is used with the devices that it's supposed to be used with.

1 Like
5

It also fails with older OSRam ct bulbs and EcoSmart ct bulbs. Is there a better driver?

6

Don't know as its not possible for us to test every bulb/firmware version out there.
I would start with the advanced, then the generics.

It's only the sengleds that have dedicated Zigbee drivers.

7

well the chance that others stumble onto/over this decreases each day as legacy devices reach obsolescence.
In my drupal world we'd call this 'Closed (Outdated)'.