Google Home automation doesn't change color or temperature

Hello, I have Govee lights connected to my HE device using Govee Integration v2 by @mavrrick58; then send those devices to the Google Home HE app. But I have some problems changing color and temperature in Google Automations. I can change the colors via voice command or in the app (or on the nest hub) but when I want to change it in a google automation, it doesn't change the color (brightness and on/off works fine). I'm able to change colors with automations if I add the govee lights directly to the Google Home app. So far no lights (govee or zigbee) sent using the HE Google Home allow ColorControl in Google Automation.

Has anyone come across this issue? There is a workaround in routines - implementing a custom voice command in the routine and change the color but I dont like that.

Thanks for any help.

This is almost identical to the issue mentioned on reddit.

Is this only a Govee device problem and others work or are they the only devices you have. The drivers use standard device capabilities everywhere possible so i don't see how this would be limited to Govee. I dont think you actually said it is just Govee, but just wanting to make sure that is not the case.

I will need to do some testing to validate.

So far it's both govee and zigbee but it seems like it has more to do with the Google Home HE app. Most of my RGB lights are govee so it's more noticeable for me. I tested "Works with Google" option with my govee lights and a smartlife device and I can change color with automation in the native Google Home App. Definitely needs more testing. I'm curious if this happens with any zwave RGB light?

Is there a way to view the source code for built-in apps on HE? I ask because I was looking through the source for the Google Home community edition HE app and it looks like they might be using deprecated Google traits for ColorSpectrum and ColorTemperature based on what I see here and here.
I'm not sure what the delta is between the built-in Google Home HE app vs the community edition but I've tried both and community edition seems more complicated to get setup.

1 Like

That is some good investigating. At this point i would suggest it would be a good time to get the @support_team engaged to get the right folks to look at it.

We don't get to see source code for built-in apps as far as i am aware. Sometimes they will share source for drivers as exampmes to be built on to.

2 Likes

however deprecated isn't retired or removed, but maybe thats the issue as we are also using these older traits

1 Like