Skip to content

fix: Compatibility with ESPHome 2026.4.0#50

Merged
hostcc merged 3 commits intomainfrom
fix/cront-trigger-setup
Apr 19, 2026
Merged

fix: Compatibility with ESPHome 2026.4.0#50
hostcc merged 3 commits intomainfrom
fix/cront-trigger-setup

Conversation

@hostcc
Copy link
Copy Markdown
Owner

@hostcc hostcc commented Apr 19, 2026

This fixes the compatibility issue with ESPHome 2026.4.0, where the CronTrigger was moved to setup()-registered interval callbacks (see ESPHome PR #15433 "[time] Use set_interval for CronTrigger instead of loop()").
The fix is to call the base setup method so the CronTrigger properly registers the interval callbacks.
Without this fix, the CronTrigger would not start and the on_time automations would not fire.

This fixes the compatibility issue with ESPHome 2026.4.0, where the CronTrigger
was moved to setup()-registered interval callbacks (see ESPHome PR [#15433
"[time] Use set_interval for CronTrigger instead of loop()"](esphome/esphome#15433)).
The fix is to call the base setup method so the CronTrigger properly registers
the interval callbacks.
Without this fix, the CronTrigger would not start and the on_time automations
would not fire.
@hostcc hostcc self-assigned this Apr 19, 2026
@hostcc hostcc added the bug Something isn't working label Apr 19, 2026
@sonarqubecloud
Copy link
Copy Markdown

@hostcc hostcc merged commit 6a91a1d into main Apr 19, 2026
8 checks passed
@hostcc hostcc deleted the fix/cront-trigger-setup branch April 19, 2026 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant