I just updated the startLevelChange methods with the suggestions above.
I'll look into the colorMode issues. I have a really hard time getting colorMode: CT to stay for me at all because as of recent Bridge or bulb firmware versions, Hue really seems to like to use xy mode for everything--even for a lot of the "default" scenes like Read and Concentrate that were formerly CT--which neither Hubitat's nor my integration really supports (I pretend xy is RGB mode; no idea what Hubitat does, and I plan to figure out a better solution for this in the future if I can). This happens as reported by the Bridge itself. However, I'll see if I might be doing something odd to cause it to incorrectly report RGB instead of CT myself--I don't doubt that I might just not be noticing something here that is my problem (since the Bridge does it so much on its own when I don't want it to, I've almost tuned this out).
Not sure about the flashing-on thing, either, but I can look into that as well. I wonder if at least one of these might be related to me trying to report colorMode: EFFECTS when the bulb/group is put into "colorloop" mode, which is consistent with what it looks like Hubitat does for Z-Wave bulbs that support effects. I might just give up on trying to track this with that attribute (not even sure "EFFECTS" is a valid value, despite the fact that they do it: Color bulb capabilities and attributes) in favor of a custom attribute or something. I was never really happy with how I made that work (and Hue doesn't treat it as a special color mode, so it would be easier on me as well).
