fix(hass): tides via resilient REST sensor (not noaa_tides integration) #69

Merged

kblack0610 merged 1 commit from feat/hass-surf-tide-cams into master

2026-06-30 23:23:55 +00:00

kblack0610 commented

2026-06-30 23:23:54 +00:00

Owner

Follow-up to #68. noaa_tides validates the station at setup and fails permanently (until restart) when NOAAs CO-OPS API is down — and NOAA is currently returning 504s (verified from inside the pod). Swapped to a REST sensor: goes unavailable on outage, self-heals next poll, same sensor.san_diego_tides entity so the existing tiles bind. Next-tide value_template verified via HAs template engine against a synthetic payload (High 5.6 ft @ 11:30 PM); degrades to unknown when empty. Will confirm live values once NOAAs API recovers.

Follow-up to #68. `noaa_tides` validates the station at setup and fails **permanently** (until restart) when NOAAs CO-OPS API is down — and NOAA is currently returning 504s (verified from inside the pod). Swapped to a REST sensor: goes `unavailable` on outage, self-heals next poll, same `sensor.san_diego_tides` entity so the existing tiles bind. Next-tide `value_template` **verified via HAs template engine** against a synthetic payload (`High 5.6 ft @ 11:30 PM`); degrades to `unknown` when empty. Will confirm live values once NOAAs API recovers.

kblack0610 added 1 commit

2026-06-30 23:23:54 +00:00

fix(hass): tides via resilient REST sensor, not noaa_tides integration 9ed247bc98

The noaa_tides integration validates the station at setup and fails
PERMANENTLY ('station does not exist') when NOAA's CO-OPS API is down at boot
— and NOAA was returning 504s. Replaced with a REST sensor against the NOAA
predictions API: it goes 'unavailable' on an outage and self-heals on the next
poll (no restart), same sensor.san_diego_tides entity so the tiles still bind.
Next-tide value_template verified via HA's template engine against a synthetic
payload (renders 'High 5.6 ft @ 11:30 PM'); degrades to 'unknown' when empty.