Ambient Awareness kills my Chroma, Hue, and my Studio

I’m trying to figure out why my Chroma is not working and it seems I have narrowed it down somewhat to Ambient Awareness. Ambient Awareness was working fine for a long time and I really don’t think I changed anything that should have killed it so I believe it was an update. To test this and because I was ready to do it anyway I did a fresh install of Win 11 moving from Win 10. The profiles were recreated from the cloud however, but I did delete all my profiles and redo them. Now I am working with only two profiles, a static and and ambient awareness. When I remove the ambient awareness profile and restart Synapse everything all seems to work, and that was also the case when I had all kinds of other profiles as well, just not that one ambient awareness.  I should add that I am using Philips Hue and at some point an update added those devices into the Studio and that seems to be where the problem lies. I say this because when I remove the ambient awareness profile from Studio and everything works, the Hue devices show up in the the Studio Profiles, When I add a profile in Studio for Ambient Awareness, Studio lags really really bad, like 30 seconds to accept a mouse click bad, AND those HUE devices go away. I also tried the info in the Razer support article that asked to Choose "Auto-select" or "Integrated graphics" from the dropdown list under "Preferred graphics processor” in the NVIDIA Control Panel", but that selection wasn’t there. I did find that I could change the OpenGL rendering GPU option so I tried that, but that made no difference. I have web searched and found some problems with ambient awareness, even some that are really close to what I am describing, just no posts with solutions or responses in some cases, so if anyone knows what's going on, I would love to hear some feedback. Thanks.