So i just had a user hit me up about trying to use setcolor in RM to adjust the color of a device for their kids. It resulted in some strange behavior. I just wanted to check if this is intended behavior.
First they were trying to set the color to what was indicated as WARM White in the RM UI but at a bulb value of 1. When the rule executed it appears that the device didn't turn on. When I tested this myself i got a similar result, but was able to confirm that the device did actually turn on, but the color was a near black color also. So when on there was really nothing to show on the light device because it was such a black color. I was able to confirm this by looking at the command that was submitted through the driver. To work with the Hubitat the integration driver does have to change from HSB % scale to RGB scale. It does appear RM is passing the bulb level as the B value in the HSB % Scale, but that doesn't really relate to bulb dim level, but color brightness and when converted is causing strange results. That Bulb level value really needs to submit Set level command after the color is requested to ensure the color is first achieved and then the level is set as expected.
I don't know if this is diffrent for bulbs that work on the HSB scale but this is certainly causing a issue when converting between HSB % scale and RGB. It is also shown well when you look at the color picker in the Hubitat ui.