Hello @bertabcd1234. I just switched to this app, from a previous one for my outside landscape Hue's. Thank you for creating this.
I want to mainly use the setEffect : colorLoop for my backyard landscaping lighting. Is there a way to control the transition timing for this color loop effect, as it transitions from one color to another? I tried to adjust all the timing preferences on the group driver for the backyard HUE group and then setEffect:1 on it. However, I noticed the timing does not have any effect.
Not that I know of. This just comes directly from the v1 Hue API, not anything CoCoHue per se is doing.
In fact, it's probably going away in the new/v2 Hue API, so if they ever get rid of v1 as planned, you might not be able to do it this way at all anymore at some point. A "dynamic scene" would be a good replacement; one could be set up to create a similar effect with whatever customizations you want. Better support for these in CoCoHue will be coming soon, but for now, I think they can be imported like regular scenes and should retain the "dynamic" thing as long as they are never stopped.
It's been a while so I may be missing something obvious but I can't seem to add a new bulb.
The "Select Hue Lights to add:" is empty (well it bumps down a wee bit but nothing there) and the rediscover button doesnt help. Restarted/refreshed everything I could. Any ideas?
It's probably already added. It should show you a list. I'd start by looking there, and be sure to make note of any bulbs you may have renamed in the Hue app but not Hubitat (CoCoHue will show both; there are matched by Hue ID, not name).
Thanks - you were spot on. I realized my blunder this morning and came back to follow-up my post. The "new" bulb had been added before I just didn't recognize it in the list because I was looking for the Hue name and didn't notice it in the brackets. I really need to get in the habit of wearing my readers.
@bertabcd1234 Does your App and Drivers control the Hue Smart Plug? Model 552349. I will be putting it in the Hue App so it can get firmware updates. Thanks
Looks like I have run into a small issue. In the Hue App there is no accessory selection for their smart plug. How would it get into CoCoHue if it isn't in the app?
You do, as you suspect, need to have the plugs added to your Bridge network to be visible in CoCoHue. From what I recall, adding it is more similar to adding a bulb than it is an "accessory," but it's been a while...
You are right. It threw me for a bit until I noticed the first one I plugged in got added to the app as a light. Weird. I remember that now as well. Thanks
Big fan of the integration. I'm pretty sure the answer is related to the hybrid approach of using both version 1 and 2 of the API with scene recall being on 1, but I'm asking just to make sure. Is it possible to add a transition time attribute to calling a scene? I found a third party app that modifies current scenes on the bridge and allows for setting a transition time. When I modify a scene with it and call via your integration, it works and allows for my scenes to fade up to 90 minutes. I'd greatly prefer keeping everything in Hubitat and having it an option in preferences if possible.
There is no way to do that right now. Scene recall is indeed on v1, but I don't know if v2 allows that, either (I'll look some day...). Scene editing is a different beast that is not supported on CoCoHue at all at the moment, and I'm not sure it makes sense to add it, though I can see some cases where it would be neat.
That’s what I figured. Version 2 does have a scene recall function and allows for custom transition time. I’m pretty sure version 1 does as well, though it is more limited. If I could get back into the developers site (I’ve been getting a 502 error for the last few days), I’d help where I can though I am not a programmer.
The only reason I ask is that it would allow us to set up rules in Hubitat that simulate a custom automation in the Hue app with the fade setting for on. It allows for the smooth transition between the current light setting to the scene rather than the hardcoded 0.4 seconds right now. For instance, i use the modified scene to transition from our circadian rhythm to tropical twilight over the course of an hour. Hubitat pushes the button at 6:45 and by 7:45 the scene is fully active.
Either way, I greatly appreciate your app and am perfectly fine with my current methods. I was more just curious than anything else.
2023-08-14 21:08:52.017 [error] No Bridge device found; could not refresh/poll.
The message is being repeated every minute, but all my bulbs connected to HE through the Hue hub are working normally. Is there some way to get rid of the message? It's not overloading, but gererating a lot of traffic to the Hubitat.
There should be more information than that. What device or app is the log entry coming from?
Also, to be clear, this is not "generating traffic" in the sense of network traffic as the term "traffic" is often used; it is just a log entry, albeit one that may represent a problem.
The app generating the message is the Hue Bridge Integration, @bertabcd1234!
Checking the app I saw that you implemented an option to set the interval to pool the bridge. Once everything is working fine, I just disabled it, but I'm curious about what is generating the error...
In the interest of clarity, I wrote CoCoHue, or "CoCoHue - Hue Bridge Integration" as it might display in Hubitat. I did not write "Hue Bridge Integration," which is the built-in option. I asked where the error came from because CoCoHue itself is a combination of app(s) and drivers, and I'd need to know exactly where it came from to look into the error.
The first thing I would do is make sure all of your app and driver code is up-to-date. If you aren't using Hubitat Package Manager, I would highly suggest that over manual installation. Do a "Repair" on CoCoHue in HPM to get the latest on everything (you could also try a regular "Update" if it says one is available, but I would still try the repair if that doesn't help). If you want to install manually, then I would suggest the "Bundle" (ZIP file) installation over manually installation of every app and driver code file. If you don't want to do that for some reason, then I suggest copying every app and driver file from the repo into your hub to make sure they are all up-to-date.
After one of those, open the CoCoHue integration app and hit Done.
If that still doesn't help:
Enable debug logging in the app and provide full logging context (screenshots display better than copy/paste, IMHO, if you're able to do that)
If the app ID of the CoCoHue app is not apparent from the log entry in #1, provide that as well
Also provide the device network ID (DNI) of the CoCoHue Bridge device corresponding to this CoCoHue instance (this is how the app locates it, and I want to make sure that logic works)
Anyone else notice that 'flash' doesn't work in WebCore? It's weird because it shows a 'custom' flash option, but no device 'flash' option. Not sure if there's something about the driver, or if webcore itself is missing something. Just finally bothered me enough to mention it. I've wanted to use flashing lights for alarms, but cannot at this point.
Probably discussed before but reporting anyway.
I'm seeing errors like this few times per week. I do not know what it means and I luckily do not know what is not working.
