Govee light automation trouble

I have an automation to turn on a few Govee bulbs at sundown. I see in the log that the automation ran at sundown, but the lights aren’t turned on. When I manually run the automation, it correctly turns on the bulbs. Any ideas on next diagnostic steps?

@jruben4 attach the automation yaml to this post so you can receive help.

alias: Deck Path Sunset On
description: ""
trigger:
  - platform: sun
    event: sunset
    offset: 0
condition: []
action:
  - service: light.turn_on
    metadata: {}
    data:
      brightness_pct: 100
    target:
      entity_id:
        - light.path_light_driveway
        - light.rgbic_path_lights
        - light.deck_string_lights_3
mode: single

Here is the logbook indicating the automation ran at sundown:

Can you post the trace timeline to see if there are any errors, the automation is correct.

I don’t think you yaml is format correctly try just one with ‘entity_id: light.path_light_driveway’

When I try to do an automation with multiple lights, I have to create a separate action for each light.

Unless you put the lights in a group or area.

I tried separating it into three automations (one light in each) - still no luck.

The crazy part is when I manually run the automation, the lights turn on fine. And I can see it’s triggering at sunset.

What happens if you create a new automation with a certain time as trigger and, for starters, 1 of the lights.
If that works, you can add the others 1 by 1, just as a test.

Also, to check if you action - and if used conditions - work, it can help to create a script which you can trigger manually.
That way you can distinguish whether you problem is the trigger or the action (or something else)

Problem solved - I think the Govee API was overloaded with too many calls when they all fired at sunset.

Anyway, I switched to Govee2Mqtt and works fine now.