@barrybaksteen I have the same bulbs in GU10 form. Did you manage to figure out the issue?
Im also seeing just 1 to 2 changes and then it gets stuck on a single color. Using the christmas lights setting and it goes from green to red, then back to green and just stays green.
I tried to install/save this blueprint multiple times and always got this error âNew automation setup timed outâ thought at first it was because I wanted to add around 20 lights but then tried just 2 and unfortunately got the same error. Any idea how to solve or troubleshoot? Thanks!
Sounds like it could be related to the issue as described here: New automation or script has saved, but waiting for it to setup has timed out. ¡ Issue #134967 ¡ home-assistant/core ¡ GitHub
Have you checked the automation traces?
In the âAutomationsâ menu, click on the 2 dots and select âTracesâ, then check the step details. It will give you an overview of what happened. You can click on the different parts of the automation schema to see the different steps.
Hello I like de blueprint but I have 4 lights in one room. And they al change in the same color. Is there something to do that they al change in different colors?
Hi Martin,
turn off the âsynchronize lightsâ slider.
Had the same issue. Got errors in the automation because one light in a group has lost the network connection. Added âcontinue_on_errorâ as a fix but seems not to work.
@AntonH how hard would it be to integrate Spotify or Sonos? So that the lights react to base (loudness) in a track? That would be the ultimate party trick!
Happy New Year;)
Probably very hard.
Youâd need analyze the bpm via either an external microphone (probably the easiest) or decrypt the stream from Spotify (most likely considered piracy, so illegal?) and then trigger a change on every beat. That would come with a delay, which would be specific to your setup so there would need to be a buffer to account for that as well.
Hi there! I am having a hmmm.. moment. For whatever reason, that I have not been able to put my finger on, the sequence stops after 5000 loops, then posts a Home Assistant Core error message.
I apologize if this has been addressed in the past, I did not see it mentioned. Traces reveal nothing out of the ordinary.
Other than this, thank you so much for a very interesting and useful blueprint.
I am running version 3.2
Error: Until condition [{âconditionâ: âstateâ, âentity_idâ: [âswitch.shelly_relay_2_dryer_disable_notify_switch_0â], âstateâ: âoffâ, âmatchâ: âallâ}] terminated because it looped 5000 times
Some one suggested to me, add a âWatchdogâ automation that ârestartsâ the Party before the 5000 loop expires.
Iâm going to try that and will post results.