updating feedparser sensor took longer than the scheduled update interval #133

Activity

1. iantrich commented on Nov 14, 2026

   

   iantrich

   on Nov 14, 2026

   Member

   More actions

   A new beta, v1.0.0-beta2, should help with this. Requests now have a timeout (10s to connect, 30s to read), so a slow or stalled server can no longer block updates. If a fetch fails, the sensor becomes unavailable until the feed responds again. Polling now uses Home Assistant's update coordinator instead of the old platform polling, which is where "took longer than the scheduled update interval" came from.

   If a server is slow only for unknown clients, you can now set a User-Agent per feed.

   How to try it

   1. In HACS, open Feedparser → ⋮ → Redownload, and under Need a different version? pick v1.0.0-beta2. Then restart Home Assistant.
   2. Your existing YAML sensors are imported into Settings → Devices & services → Feedparser automatically and keep their entity IDs. A Repairs notice then asks you to remove the YAML.
   3. To go back: delete the Feedparser entries under Devices & services, redownload 0.1.12 and restart. Your YAML isn't changed.

   Release notes: https://github.com/custom-components/feedparser/releases/tag/v1.0.0-beta2

   Please reply here with whether it works for you. If it doesn't, include the feed URL and your sensor options. Thanks!
2. iantrich

   closed this as completedon Nov 14, 2026