Not sure if this is a bug within the HomeKit app, or within the Room Lighting app, or with the Room Lights Activator Bulb.
I've got some Ikea Color Temp bulbs connected directly to Hubitat. They work fine. If I export them to HomeKit, they work fine. I can select "Export as Color Temperature Light", which is what I expect.
I've got them (and nothing else) in a Room Lighting app, with an activator device for them. The activator device has RGB settings available (which do nothing, and should probably be fixed, as 2 CT bulbs shouldn't even have RGB controls on their Activator), as well as Color Temperature settings. If I change color temp from the activator, that also works as expected.
When I try exporting the Room Lights Activator Bulb to HomeKit, the only options I get are "Button", "Switch", and "Dimmer". I don't have any option to export it as a color temperature light (so I can change color temp via HomeKit), and there are no options for RGB/RGBW either (which exist on the activator but really shouldn't, since there's only CT on the bulbs).
I know there's no support for any sort of dynamic capabilities, but maybe we could have multiple different Activator drivers, with varying capabilities depending on what they control? So one with switch, one with dimmer, CT, RGB, RGBW, Shade Level, etc? And have an option in the Room Lighting app next to the Activator name field where we could select what capabilities the Activator should have?
Ideally, if the devices controlled by the activator all have the same capabilities, then the activator should just automatically mimic that, rather than need to be selected manually. So default to "whatever the devices have" and default to "switch" or something sane if there's a mix of devices in the Room Lights app, in case someone has an activator for a mix of bulbs, switches, blinds, etc, all in one app.
It's not really a big deal exporting 2 bulbs instead of 1 activator, but other rooms have many more bulbs than 2, and they "popcorn" wildly when controlled via HomeKit, since I can't export the Hubitat activator (which uses ZigBee groups) to avoid the popcorn.
I think this should fall within what Hubitat apps/drivers can do. If the app has a drop down for "Activator Capability" or some sort of CheckBox selector, and the user changes what the Activator capabilities are, it should be possible to store the DNI of the present activator, remove said child device, create a new activator with the required driver to match the needed capabilities, and then restore the same DNI as before so anything referencing the old Activator continues working.
