[RELEASE] CoCoHue: Hue Bridge Integration (including scenes!)

Custom Apps and Drivers Custom Apps
1267

I appreciate all the feedback on this! I've released an update with a breaking change, so please read if you use scenes and haven't been following:

CoCoHue 5.1

  • Removed switch capability (and related on/off commands) from CoCoHue Scene driver. *To activate a scene, use the "Push" command with button number 1, e.g., push(1).
  • Removed preferences and related code to the above from scene and group drivers and app code.
  • As before, if anyone depends on "legacy" behavior, CoCoHue 4.2 remains available (see first post)
  • Existing users, if you use scene devices from CoCoHue on Hubitat and depend on the switch state or commands, please:
    • change any uses of the on() command on the scene device to push(1) ("push button 1") to activate the scene
    • change any uses of the off() command on the scene device to do whatever it is you actually want to do, likely an off() command on the associated group (room/zone) or lights; and look at group or light states instead of the scene states if you previously relied on the status of the scene activator device

See first post for how to obtain.

Hue, unfortunately, does not -- so I think it's time to finally rip the bandage off in this integration. :smiley: In the process, this removes considerable complexity in some parts of the scene and group code as well as quite a bit in general for both of these drivers and the app. (The Hue V2 API does have an attribute that looks promising for reporting state, but that's not what anything I can find says it's supposed to mean, and there's still no command to "deactivate" a scene, so it doesn't fully solve the switch capability problem in the driver, either...)

2 Likes