Set dimmer in rule not functioning

📐 Rule Machine®
1

i have a rule that turns on 3 bulbs at 10% brightness. its been working find for months. a few days ago it stopped functioning.
now the lights come on at full bright and dont dim.
The light is homekit enabled. i can set the brightness of these lights manually.

has anyone seen this or know what might be wrong?

2

Came here to say the same thing. It seems to have broke with the last firmware update.

I completely deleted one button controller and recreated it and it started working, but on another one it still doesn't work.

I'm using groups to control multiple lights in both instances. On the dashboard for the broken one, when I press the button the state of the group toggles between on/off, but the individual lights still won't toggle when I press the button. If I hit the icon on the dashboard, the on/off seems to be properly passed on down to the individual lights in the group.

So, it kinda smells like the button controller has gone flakey ...?

3

i also deleted all the rules and re created it. i also tried a basic rule. same result

4

What device is this, and what driver is it using? Also, what platform version are you running (Settings > Hub Details)?

5

I have an update of what I think is happening.

I noticed that all my switches that still work are controlling plain white bulbs.

All the broken switches are on RGBW bulbs. I was essentially using the "Dim:" function to turn colored bulbs on and off while retaining the last color that was set. Now it appears that setLevel is not working for the RGB part of the RGBW bulbs.

If I set my button handler to use "Set color:" instead, it works. But this has the drawback of having to specify a single color for the button. Previously, using 'setLevel' essentially triggered an on/off without regards to what color the bulb was currently set to.

All of the lights that are affected for me are using the "Generic Matter RGBW Light" driver, but have various form factors (Nanoleaf A16 bulb, Nanoleaf Holiday Lights, Nanoleaf light strip.)

Platform version is 2.3.9.196. I believe that this started happening after the last update a day or two ago. This is on a C-8 Pro.

6

One last thing before I'm off work. Ha ha.

If I go to the settings of one of these devices and set the level using setColor or setColorTemperature, then the level is correctly set. However, using setLevel alone never works. That appears to be broken altogether, even when I've set the bulb using temperature (the W in RGBW.)

If I were a software engineer (and I am) and I was writing a bug, I might suggest that setLevel has stopped working for this driver.

7

This is why I asked this question. There is a known bug with this driver and the "Set Level" command in 2.3.9.196, which will likely be fixed with the next build in a couple days. Rolling back or using another command, like Set Color Temperature, are workarounds for the problem in the meantime.

EDIT: fixed in build 197.

2 Likes
8

i have the same results. set level does nothing.

10
  • endpointId: 01
  • hardwareVersion: 3.0
  • inClusters: ####,####,####,####,####,####,####
  • manufacturer: Tapo
  • model: Smart Multicolor Bulb
  • outClusters:
  • serialNumber: ########
  • softwareVersion: 1.0.0
  • uniqueId: ########
11

If this is using the Generic Matter RGBW driver (the only question above about the driver and an answer that isn't apparent from the information above; the question about versions was to verify the hub platform version), the explanation is the same as above, and there should be a fix in the next release.

2 Likes
12

The issue noted in the original post is fixed as of 2.3.9.197. If you are having other problems, please create a new topic and send share relevant details, including brand/model of device, the driver being used, and the app, rule, or other feature you experiencing problems with.