Works. It was the group driver in this case. It’s late, but I’ll check it out more in the morning. Thanks.
Edit: the problem seems to be fixed and I’m not seeing any new issues so far. Thanks again @bertabcd1234
Works. It was the group driver in this case. It’s late, but I’ll check it out more in the morning. Thanks.
Edit: the problem seems to be fixed and I’m not seeing any new issues so far. Thanks again @bertabcd1234
So is this an issue in the latest build from HPM? My entire 1st floor is built on hue groups and room lighting instances
I am not aware of any issues other than the one mentioned above, and that is the only similar report I've seen (and it involves a different app than you mentioned). If it still ends up being an issue for you, that workaround may help, otherwise I will make it part of the next release if it doesn't cause any unforeseen problems in my testing.
Mine have been working perfectly since your suggested fix.
I updated from HPM, working great!
I posted how to control Dynamic Scenes with webcore.
At least in my setup, CoCoHue "sees" Hue dynamic scenes and Rule Machine can trigger them with no problem and without using Webcore. The strip light behind my TV uses dynamic scenes, and I trigger them via RM.
Room Lighting, unfortunately, can't do a transition between two dynamic scenes. But I get around that by turning on a static Hue scene that resembles the first dynamic scene, transitioning between that and a static Hue scene that resembles the second dynamic scene, and the turning the second dynamic scene on. Hokey, but not too jarring.
Interesting, I recently used cocohue to present the scene 'Moonlight' for a room to hubitat, and set up a button to toggle the Scene in hubitat on or off. It works, as far as turning the lights to the color scheme for moonlight, but they seem to be static colors and never change. Is there something specific I need to do to get the dynamic effect?
I didn't do anything special, and mine do change. Have you checked the Hue app for the dynamic speed on your scheme? The default seems to be so slow the change is almost imperceptible. But you can change the speed to make it change much faster.
I haven't, but they definitely don't change at all. However, I think I just found something. It seems that Hue added a new setting for dynamic scenes in the app last fall. If you edit a dynamic scene, there's now an 'Auto-Play' option, to start the dynamic scene automatically when switching to the scene, rather than starting it as static until you hit the play button. I wonder if that's the difference? I'll have to play with it and see!
Edit: Yup, that seems to do the trick. Now when I toggle on the scene from hubitat it is animated as expected.
Totally forgot about that! Good catch. Yup... that would do it!
Hi
This setting - "Mark all GroupScenes for this group as off", does not work for me.
Whenever I turn off a group, the last activated scene remains as on.
Any suggestions how to fix this?
Thanks in advance
I'm seeing this too and don't know off the top of my head what could be causing it. My suggestion would be to treat scenes as button devices, not switches (something I wish I never implemented...). I will look at this again when I get around to using the v2 API for activating scenes. or possibly before then if I can see some easy fix.
I'm guessing it's related to eventstream changes, so reverting to only the "classic" polling API should work if you don't mind that and really want this behavior (assuming that guess is correct at all).
Thanks for the reply.
Do you mean turning this setting off?
If so, that didn't seem to make a difference.
Thanks
They was the one.
Id like to thank for this brilliant integration. Would it be possible to add support for the hue dial scene button dial please?
Thank you
I think it should already work. Are there any problems?
Hi All. I am new to Hubitat, hub arriving in next couple of days.
I currently use Hue movement sensors and Alexa to trigger scenes and lights and want to move everything over to Hubitat so I can duplicate what I have now but do so locally and not have to rely on external cloud based systems.
Reading through the forums and docs I see that the Hubitat hue integration doesnt allow for scenes so it would appear that Cocohue will be required, which does.
I am a complete novice to all this (think of me as an idiot at this stage) so excuse me whilst I find my feet and ask what may appear to be blindingly obvious to the rest of you. But at 57 years old, this stuff doesnt come easy although I usually manage to get things going and once I get them working I am pretty good at keeping them up and running..
So at the moment I have several scenes that I use in a particular room and this is the most complex room in my smart home. The scenes are:-
Normal: This is my first scene, all 15 Hue bulbs lit at various levels of intensity. Most are Ambience, a few are RGB. This scene is activated via Alexa voice and via movement sensor.
Cinema Mode: This scene is just two play lights and one ceiling mounted GU10 ambience light. Activated by voice via Alexa.
Bedtime: This is a bedside light, two play lights in red and a bloom light in red gradually fading to off over 30 mins. Activated by voice via Alexa.
My Normal mode if activated by movement sensor via the Hue sensor if its dark enough and uses the "Do Not Disturb My Scene" from Hue labs so that if I switch to Cinema mode, the sensor doesnt switch back to Normal mode if I leave the room.
So to questions:-
Question 1: Will Cocohue add Hubitut allow me to duplicate the above functions, still using the Hue Movement sensor and Alexa?
Question 2. What Do I require on the Hub in terms of apps and drivers to make this all work?
Question 3. If I download the full zip file for Cocohue from GitHub, will the Hubitat app installer just allow me to point at each unzipped file and install one by one, is it that easy?
Yes, please!
Webcore keeps getting tripped up when I try to activate a scene, but the lights in a room or a zone have been turned off from some other source without CoCoHue catching that. The result is always that webcore is unable to the scene on, since it's already shown as on, so nothing happens.
Scenes as button devices would be perfect!
They already are. (The regret is making them also switches...)
Do a push(1)
on the device or "push button 1" or however the UI phrases these, and it will activate the scene.