@scottgu3 makes sense, looks like you have to move Hue Motion Sensors to Hubitat to detect Motion/Temp/Luminance.
Will keep lights that work with hue in Hue.
Will play around to work out where Hue Switches sit best.
The main downside of moving Hue Motion Detectors Hubitat is I am introducing complexity to lighting, at the moment lighting is extremely robust and extraordinarily rare fo you to walk into a room and the lights do not turn on.
Now means I have to maintain two hubs to keep lighting working.
I'll migrate Hue Motion for my office and see how reliable it is.
The current system I am using provides full, timely integration with the Hue Hub so I can leave everything the Hue Hub AND have access to the Motion/Temp and Luminance Sensors for other triggers.
The Primary function of the Hubitat will be to control the Central Heating and Hot water systems.
But testing, the whole Hubitat capability right now.
Good things to consider. I can tell you however, that, in my experience the Hubitat->Hue integration is rock solid. Similarly the Philips Hue Hub simply never crashes nor does it require any real user intervention.
I use a Hue->Hubitat solution for all my pull string closet fixtures. I put a hue bulb in, and then a contact or motion sensor, and write a rule in RM4 for the light. Works great.
I also have an array of BR30 hues in pot light fixtures that are wired inconveniently. My biggest use is table lamps and torchierres, and they are all hue bulbs using a rule tied to outdoor Hue Illumance (motion) sensors. Works incredibly reliably.
Given the low burden of maintaining the Hue Hub (almost none), I find it to be worth it, and it keeps Bulbs and lightstrips off my Hubitat, which lightens the load.
Many of us use multiple hubs for our automations. In my small house, I have two Hubitat hubs, a Lutron Caseta Pro bridge, a Mijia smart gateway (soon to be 2), a Harmony hub, and an Odroid running various node servers, including node-red.