Why do my Philips Hue bulbs turn on by themselves after a power outage, even when I set them to “PowerOn Behavior: Last State”?

Sunset-based automations are among the most popular routines in Home Assistant and other smart-home platforms. They rely on accurate local time to turn on lights, activate outdoor scenes, and adjust energy settings at the right moment. However, many users notice that these automations sometimes trigger too early, too late, or not at all—especially when using Zigbee devices. The root cause is often Zigbee time synchronization drift.

In this article, we explain why this drift occurs, how it affects sunset automations, and what you can do to eliminate the issue.

1. Why Sunset Automations Depend on Accurate Time

Sunset routines are calculated using:

• Your geographic location
• Daily sunset calculations
• The system clock of the hub
• The time-sync behavior of connected radios (Zigbee, Thread, Wi-Fi)

If any layer drifts out of sync, the automation fires at the wrong time.

2. What Causes Zigbee Time Synchronization Drift?

a. Battery-Powered Zigbee Devices Enter Deep Sleep

Most Zigbee sensors sleep aggressively to save battery. When they wake up, they may use cached timestamps that are several minutes old. This causes them to report outdated triggers that disrupt time-based logic.

b. Weak or Noisy RF Signals

Interference from:

• Wi-Fi 2.4 GHz
• Bluetooth
• Microwave ovens
• Dense Zigbee networks

can delay synchronization packets between the Zigbee coordinator and its child devices.

c. Coordinators with Unstable System Clocks

Some inexpensive or older USB coordinators have:

• Drift-prone internal clocks
• CPU spikes that delay time updates
• Firmware lacking periodic resync routines

This slowly offsets the network clock.

d. Cloud-Linked Zigbee Hubs Re-Sync at Long Intervals

Hubs like SmartThings or Philips Hue may synchronize time only every few hours, which allows small inaccuracies to accumulate.

3. How Drift Causes Sunset Automations to Misfire

When Zigbee time is off by even 2–5 minutes, automations can behave unpredictably:

• Lights turn on before sunset because sensors report outdated time.
• Automations fail because the trigger arrives in the wrong time window.
• Scripts fire twice when Zigbee packets arrive late and get re-evaluated.
• Outdoor automations activate after dark due to slow resync cycles.

Because Zigbee events are timestamped locally, any drift affects how the automation engine interprets them relative to sunset time.

4. How to Fix Zigbee Time Drift for Reliable Sunset Automations

1. Update Zigbee Coordinator Firmware

Modern firmware improves:

• Clock correction
• Sync packet frequency
• Handling of sleeping devices

2. Minimize 2.4 GHz Interference

Change:

• Router Wi-Fi to channel 1 or 6
• Zigbee channel to 15, 20, or 25
  for cleaner radio space.

3. Add Powered Zigbee Routers

Devices like smart plugs stabilize the mesh, ensuring:

• Faster sync propagation
• Reliable timestamp updates
• Fewer packet delays

4. Use Home Assistant’s Time Synchronization Add-Ons

These ensure the system clock is always accurate, especially on Raspberry Pi setups.

5. Avoid Overloading the Zigbee Network

Too many devices on a weak coordinator cause timestamp queue delays.

5. When to Suspect a Zigbee Time Sync Problem

You are likely experiencing drift if:

• Sunset automations trigger inconsistently
• Timed routines behave differently day to day
• Zigbee sensors report events with incorrect timestamps
• Automations work fine with Wi-Fi devices but fail with Zigbee

Conclusion

Sunset automations depend entirely on precise timekeeping. When Zigbee introduces time synchronization drift—whether from interference, outdated firmware, sleeping devices, or mesh instability—your automations may misfire. By improving network stability, updating firmware, and reducing interference, you can restore accurate and reliable sunset-based triggers.