Iāve amended this in version 2.4. this is a BETA version of the blueprint.
Could you check if this fixes the issue on your end?
For information: Iāve tested it with a random Zigbee light in my home and it works without issues. However, I donāt have any Hue or other large name brand light installed at the moment.
Thanks for the feedback!
Iām going to wait a couple more days so that others can give feedback as well and will then push the change to the production version.
The 2.4 beta made it work with my tuya light strips as well, although they dont transition, but thats fine.
My only request for this would be to add add a āRandom Deep Hue Colorsā mode, the RGB is good but Iād prefer a mode that doesnāt have whites/light colors
Edit: I made a gist that adds a deep color mode: Party Mode Test.yaml Ā· GitHub
The only thing I cant figure out, is some of the transitions seem to cycle through white even when going between two deep hues, not sure why that is, might just be the way hue bulbs are.
Edit 2: From a RGB color wheel perspective it makes sense they would go through white depending on what color it is transition from/to. If its from blue to yellow for example it would go right through the middle of the wheel.
The yaml files I made shouldnt overwrite any other ones, you import them like any other. Click on the links in my messages, copy the url, go to your blueprints page in settings and click import bottom right.
But the SATURATED COLOR MODE doesnāt run smoothly for me. When I select RANDOM COLOR MODE, all lamps are addressed as expected. But nobody wants the white light, so I was looking forward to the new mode.
My lighting system runs via Hue.
What other data can I give you?
HA is up to date and I just downloaded the blueprint.
Is the Saturated Colour mode only supposed to work for Hue lights? When I change to that mode my Tuya based lights do nothing at all. However, the new Christmas mode does work.
Addendum: Although the Blueprint is only supposed to control an original Hue lamp via the Hue Bridge, this does not work reliably. Sometimes it works, sometimes not.
It would be nice if the script ran more reliably, because itās basically exactly what Iāve been looking for for a long time.
If I can contribute information for bugfixing, please let me know.
I made some new discoveries yesterday when I was setting up the party lights for my wifeās birthday.
About the setup: I operate all the lights via two Hue Bridges. However, the lamps mentioned in the script are all on the main Hue AP.
I operate 95% original Philipps HUe components, but also a few cheap controllers for LED Stripes.
All my components (whether original or cheap from China) have been working wonderfully for years with the āMagicHueā app (a kind of modern light organ, all selected lamps change by sound).
Thatās the initial situation.
What I discovered yesterday:
Saturation mode doesnāt work for me at all.
Colored mode only works for me if I have selected original Hue components. If I include one of the China Controller, nothing works either.
Summary for me at the moment: Saturation mode does not work for me if I have selected more than one device (I deliberately do NOT use the sync function).
Only original Hue lamps work in Colored mode.
Setup party light a few weeks ago, and the saturation mode did not really work. Did not have time before today. Updated to blueprint version 3.0 and it works perfectly.
I actually got a little disappointed at first as my cheap tuya bulbs connected using ZM, 18 of them in the bathroom, did not really change brightness. Figured out it is because the difference between 1% and 20% is not visible by looking at them. Had to change, using 15% to 35% to get visible good effect.
Itās Christmas time and my front yard lights have automatically kicked into coloured light mode at sunset using this Blueprint. Using the new Christmas Colours setting is perfect as it gets rid of all the washed out colours. Thanks for that update!
Yesterday, I migrated all my lights from the Tuya Cloud to Tuya Local. This has improved the response time considerably. Previously I had to have the lights change colour only every 2 seconds. Now I can have it at 500ms and it is perfect. However, at that rate of change, the loop runs very quickly and there is a 10,000 iteration limit on loops. Apparently there is no way to change that limit so it will have to be the Blueprint that changes. With the lights changing every 500ms it only runs for just over 1.5 hours before it crashes which is not long enough. It needs to be at least 4 hours or even longer which is many times the current iteration limit.
Can the Blueprint be changed in some way to alter the way it loops to somehow reduce the number of iterations?