Hello: I have an advanced flow that starts “90 minutes before sunset”, and then goes through several steps that ultimately result in two Govee lightbulbs increasing in brightness by 1% to 100% over 75 minutes.
Recently, this flow stopped working. I added some logging and ‘error catching’ steps, but the logging shows that the ‘start’ action works properly, and none of the ‘error catching’ steps catch any errors.
However, if I manually slick the ‘start’ action, or any action after the ‘start’ action, the flow works just fine.
I was hoping someone could assist/advise me. Thanks!!
I see in your screenshot that you turn on the lights first before dimming them. In most cases, using only the dim cards also turns the lights on. If it doesn’t, you should add a short delay between the “Turn on” and Dim cards.
I’ll add a 3-second delay, and see if that helps, but when I simply press button to start the flow manually (or use a ‘test from here’ action), the whole flow runs without any issues.
No - the flow is triggered (I am already logging that part, in the Google Sheets screenshot in my original post). I had switched it to the built-in card from an external-webhook trigger (above the 90-min card in the pic above), thinking it was the external trigger that wasn’t working, however the Google Sheet logging also captures that it is working.
When I look in the Govee app, it only shows the bulbs at 1%, so they don’t increase in brightness over time, even though if I run the flow manually, they do increase over time.
In order for this card to work and not error out by itself, all four Error parameters need to be present. Not sure where these Error messages originate from. I assume the source of these are four different flow cards. All those flowcards need to result in an error in order for the ‘Create…as Text-tag’ card to work. If not, then one or more parameters are not available and (as far as I know), this card will error out and the flow will not continue.
It hasn’t triggered so far, but my thought was that the ‘create ___ as text-tag’ would just concatenate any messages from the individual cards before and use the | character as a separator not as an actual boolean (although, I suppose if it were operating as an OR it would work as well).
When the garage light is turned off by the switch, you allow 10s for the bulbs to reconnect. During the test there is more time to reconnect because of the slower animation.
I strongly recommend another way to turn off the light and keep the lights allways connected.
(You needed 4 screenprints to show the flow. Consider zooming out so you can see the whole canvas)
This is because in that case you act as “sun sets in 90 minutes” trigger card.
Which implicates the sun trigger card doesn’t work (well) anymore.
The trigger, like it is now, doesn’t work, probably the offset is out of range due to firmware changes;
It’s very well possible it’s limited to 60 minutes max.
If that’s not the case:
I always had the idea the onboard sun cards are just not 100% reliable.
I can therefore recommend to switch to the Sun Events app by 100%
