Broxtowe data stale / not being refeshed

[bobbinz]

Not sure if related but since the latest update my bins have only ever got new data union a home assistant reboot or full refresh of the integration.

My sync schedule is set to 12 hours but for some reason this seems not to get the latest data.

A device reload gets the correct up to date information.

Originally posted by @bobbinz in #2188 (comment)

Not sure what the difference is between a full reload and the 12 hourly refresh is. There no error logs or anything related sadly!

[bobbinz]

Actually upon further digging the next collection date is actually correct in the activity log, it's just the "in two days" or whatever text that is incorrect.

[robbrad]

Investigated — this is the same root cause as #2193, and your clarification (date correct, but the "in two days" text wrong) is actually a precise fingerprint of it.

Why data only updates on restart/reload: the manual_refresh_only option's runtime logic was flipped in commit 4c2a9924 (released in 0.171.0) without migrating existing config or updating the checkbox default/label. The net effect is that the coordinator is created with update_interval=None, so the 12-hour schedule never fires — data is only fetched by the one-shot refresh that runs on HA restart or an integration reload. It's not Broxtowe-specific; every council on 0.171.x is affected.

Why the date looks correct but "in N days" is wrong: the main bin sensor caches its state string ("In 2 days") and days value and only recomputes them when the coordinator pushes an update. The "Next Collection Date" attribute, on the other hand, is read live from the stored date — which is a valid future date, so it still shows correctly. With automatic polling dead, the stored date stays right while the "In N days" countdown is frozen at whatever it was during the last reload. That's exactly what you're seeing.

Fix: #2203 restores automatic refresh (via a config migration plus the corrected default/label from #2198), so the 12-hour schedule works again and the countdown advances.

I'm also adding a small follow-up so the "In N days" countdown recomputes at local midnight independent of data fetches — that way it stays exact even between refreshes.

Closing this as a duplicate of #2193 — please follow that issue / #2203 for the fix. Thanks for the detailed debugging, the "date vs countdown" detail was genuinely useful.

[robbrad]

Follow-up filed: #2205 makes the "In N days" countdown recompute at local midnight so it stays correct between data fetches. Combined with #2203 (which restores the automatic 12-hour refresh), that covers both halves of what you saw here.