Closed waynethomas69 closed 1 year ago
Thanks for the report. Will debug your example in my test setup.
The first thing I already spotted is the incorrect use of useKelvin
that is now called colorUnit
As of #337:
useKelvin=true is replaced by colorUnit="kelvin"
When did that setting change? Either way, changed the text-based config and still not detected. The GUI-based config did not have that option selected (so was previously blank); added it manually in the code tab for the ga metadata and still not detected either.
It changed with https://github.com/openhab/openhab-google-assistant/releases/tag/v3.5.0
So 10 days ago.
It also explains the second error. Complex lights are now called "specialcolorlight".
I also need to say that the options presented in the UI are not up to date with the latest changes here. This is a known issue we currently try to solve.
https://community.openhab.org/t/documentation-in-openhab-vs-current-google-assistant-features/140735
specialcolorlight fixed it. I didn't think to look for breaking changes since I hadn't changed anything myself and didn't realise the cloud connector was updates completely independently. But now I know for the future! Thanks for your help!
As a follow up to #383, the two light groups I had previously created (one in GUI, one in config files) are no longer detected by google home at all. I even tried setting the colorTemperatureRange again, but this did not influence it this time (it was probably a red-herring). Here is the config file that isn't detected:
and here are some screenshots of the gui configured group that also isn't configured: