setLevel unreliable on Sengled Multicolor E11-N1EA

Developer Programs Support
1

Tried searching but have not found an answer yet to an issue I’m having with my Sengled Multicolor E11-N1EA bulbs. In a nutshell: when I use setLevel in a smartapp it almost never sets the correct level. Now this same app/command works great with my Sengled Light E11-G13 bulbs. When I subscribe to the “level” handler with “subscribe (light, “level”, switch1Handler)” I get some interesting output. On my “regular” bulbs I get 2 lines in the log for every event (changing the level) most of the time, sometimes just a single line. So my app starts, I subscribe to the event, have a runIn set for 5 seconds, and then the app issues a “setLevel(15)”. The log shows:
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:38:14 PM: info switch1Handler Event: 15
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:38:14 PM: info switch1Handler Event: 15
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:38:08 PM: debug Updated with settings: [light:Desk, llevel:15]
and the bulb is at the specified level of 15%.
When doing this for a multicolor bulb I see this:
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 30
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 29
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 27
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 26
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 24
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 23
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 22
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 17
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 17
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 22
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 20
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 19
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 19
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 17
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 14
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 15
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 10
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 10
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 13
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:31:35 PM: info switch1Handler Event: 11
b8a3794c-6d74-4ab3-b290-952e1ca6ec79 3:39:20 PM: debug Updated with settings: [light:Mudroom, llevel:35]
and the bulb is still not at the correct level. Subsequent setLevel’s don’t do anything. From the SmartThings App itself I can try to adjust the level and while working most of the time, it will freeze on me and I need to go back to the overview, tap the bulb again and try again.

Has anyone run into this and found a solution?

2

We’re actively working on adjusting the DTH for “Zigbee RBGW Bulb.” The changes should resolve this behavior.

2 Likes
3

Thanks, that’s good news!

2 Likes
4

We released a change to the “Zigbee RGBW Bulb” DTH earlier today. Could you let me know if you’re still experiencing any of the above issues? Thanks in advance for your time.

2 Likes
6

Hi Garrett,

I was able to do 2 quick tests, going from 35 to 100 and the bulb ended up at 99, so close enough. The level handler I had going was still showing an up-down-up trend but as stated: it did get (close to) the desired value. Going from 99 to 10 also went well, it ended up at 11. Again one point difference, and a down-up-down stream of levels. But it did get there. So I’m cautiously optimistic that this will work. I’ll be able to give it a more thorough test next week but so far so good.

Thanks!