What it does

Schedule this as a dish that runs early each morning. It reads today's planned and weather_hold visits, looks up the forecast at each distinct weather-sensitive site, and writes a verdict onto every visit.

⛔ It plans TODAY and only today. Open-Meteo returns the daily forecast as parallel columns (daily.time, daily.precipitation_sum, …) and the recipe language cannot index an array by a value computed at run time — {{step.x.daily.weather_code.{{step.offset}}}} is a nested template, which is an error, not a lookup. So the recipe reads index 0, which is today. Planning tomorrow the night before would silently read today's weather; refusing to offer it is the honest option. Tomorrow's plan is tomorrow's run.

⛔ It never geocodes. Coordinates come off the site row, written once by Add a service site. The Nominatim pack is explicit that it is not for periodic geocoding, and a daily planner is exactly the periodic caller it warns about.

⚠ A hold the customer was told about is NOT lifted automatically. If the forecast improves and notified_at is set on the visit, the visit stays held and the card lists it under "held, customer already notified". Reinstating it is a deliberate act — the alternative is a machine quietly contradicting a message you already sent. Holds that were never notified are released normally.

⚠ Indoor sites are never held. A site with Weather sensitive off gets the verdict indoor and is left alone whatever the sky is doing.

⚠ Forecast failures are visible, not silent. A site whose forecast call fails keeps its previous verdict and is counted under "forecast unavailable" on the card. It is not treated as clear.

⚠ Site-local vs server-local midnight. The pack sends timezone=auto, so index 0 of the forecast is the day it is at the site, verified live (a London coordinate returned timezone: Europe/London, daily.time[0] = today). But the visit list is filtered on the server's local date. Those agree for anyone whose sites share their server's timezone — which is every ordinary field-service operator — and diverge by a day only if you dispatch across timezones. If you do, run the plan mid-morning rather than just after midnight.

⚠ The visit cap bounds the weather calls. At most Max visits visits are read per run (default 40). If your day is longer than that, the card says so — it does not quietly plan half a day.