I am attempting to use the "Tasmota - Generic RGB/RGBW Controller/Bulb/Dimmer" from @markus with Google Home. The driver works fine with Google home if I have either "ColorTemperature" or "ColorControl" commented out in the driver code. However, if both capabilities are active, the corresponding device gets excluded from the Google Home App in Hubitat after a few minutes.
Does anybody know if this is an issue with the driver, Hubitat, or Google Home itself?
I would post this on the thread where the driver was released so @markus is sure to see it. I have no problem getting devices with both of those attributes to sycn to google home without a problem. Does your device display the current Color Mode as well? That is required in order to get the device to work.
That is good to know, then it is probably the driver, I don’t use Google Home. I’ll check the driver. Any examples of a driver (with available source code) with these capabilities which is known to work?
The ones for CoCo Hue work correctly. But basically, colorMode has to be set to RGB or CT depending on what mode the bulb is in. This is required for all RGBW lights. It's a required attribute for many different implementations, not just google.
Not only that, but you have to make sure it is displayed with a default also. Many drivers are guilty of not setting this by default on install so the device has to be "flipped around" a bit before it can pair to GH.
Well, first of all, that example is 100% local. It does not use any thing in the cloud.
Second of all, what difference does it make? If the bulb is in CT mode, you have to set it to CT. If it's in RGB mode you have to set it to RGB. It makes absolutely no difference how you talk to the light.
Ok, maybe I need to rephrase that, if it communicates with something that is connected in with the cloud, like Google Home, then no, it is not what I would call a 100% local. Maybe other people would, but that is not my definition. It's ok, I'll find a way to check my compliance.
It just helps in detecting non-compliance, so does bug reports however.
Thank you for your feedback, it helped pinpoint this rapidly.
Your driver doesn't talk to Google Home. It talks to the bulb. Google home has absolutely nothing to do with it. But if you want another app that requires colorMode besides the Google Home integration check RM or Groups or Scenes. All rely on coloMode.
If they didn't display colorMode, then no, they didn't. They might have looked like they did but I guarantee they didn't. For example, in a scene, the scene app uses color mode to compare the values of the device against the values in the scene to determine if the scene switch should be on or off. Without colormode, it won't know how to do that.
Also, at a platform level, devices that are RGBW are required to have colorMode. So, I guarantee there were errors being thrown in other places.