Closed fistcrunch closed 4 years ago
I am not related to Inovelli, but I had a similar issue with a hue hub integration and it had to do with color mode. I don’t see color mode being changed, and HomeKit needs this to know, as well as other integrations like sharptools. I would recommend looking to see if, when you change to a color temp, that color mode is being set to CT and when changing to a color, that color mode is being set to RGB in Hubitat. This may be a clue into the cause of the issue. Hubitat is very forgiving with this type of stuff. But, other systems need to know it.
This might be fixed.. You should re-test with the updated driver
Going to close this. Let me know if the changes haven't fixed it and we can look into it further.
I'm having some issues getting the LZW42 to work correctly with combination of Hubitat <> Maker API <> Homebridge.
In Hubitat, all the functions work correctly sans the hue and saturation "buttons".
When using HomeKit/Homebridge the color temperature, dimming, and on/off work. However, when I try change the RGB settings the color does not change and the screen snaps back to the color temperature selection screen. If I try to adjust color temperature, it does change temperature but HomeKit UI doesn't retain the value.
I tried having a look at the driver code but I'm not too familiar with the ZWave specification or Groovy. I see a parse error for command 3304 when setting color in Hubitat but it does succeed. It looks like HomeKit is setting hue and saturation which in turn call setColor. While Hubitat is calling setColor directly with both hue and saturation. Not sure if that's the issue but it's only connection I could see.
Here's the debug log when trying to change RGB via HomeKit -> Homebridge -> Maker API -> Hubitat
Here is the logs when using the set color button in Hubitat:
Any help with the driver would be greatly appreciated!