Cannamsterdam: East Palm Canyon · Facility 1294

Mesh backbone:Red troncal: This is a single-gateway facility — and the gateway fleet is already on WP5. Sheet gateway H2100002017 was listed as WP4 at the sheet snapshot (2026-06-08); the live audit (2026-06-11) shows ggVersion = 2, confirming it has since been upgraded to WP5. It is online and carrying the mesh today, so the gateway side of the migration is done. 115 units are online and communicating through it; devices that were offline when the gateway moved to WP5 simply stay on WP4 (unchanged — not harmed) and can be brought current later via a short WP4 gateway revert + re-run, coordinated with AROYA — there is no time limit. The remaining upgrade landscape here is therefore the TEROS-12 + Atmos-14 trade-in pool below. Any re-run is done remotely by AROYA; a site visit is the exception, not the default.

Your fleet lists 39 radios as “repeaters”; the serial prefix splits them into 4 range-extender/IO radios and 35 climate stations (H111…) — a repeater-class radio with an Atmos-14 attached. Across the 135 substrate nodes, 78 have a reporting attached sensor, 4 are alive but the sensor isn’t reporting (reseat the probe / check the connector), 48 are dark with the node, and 5 have no sensor paired. Beyond TEROS-12s (137), this fleet also carries Atmos-14 climate sensors, SQ-521 PAR sensors, ES-2 EC/temp sensors and 0 already-upgraded TEROS One probes — attached sensors ride on their host radio for the WP5 push.

Cross-referenced against the retired-device register (portal_api · retired=true, pulled 2026-06-11): sensors whose host puck/radio is flagged retired qualify for a free 1:1 TEROS One Single replacement. This facility's register holds one retired node — H3210008273 (Mom Veg 2, silent since 2022-10) — with no sensor paired to it, so there are 0 free entitlements; every TEROS One / Climate One upgrade here is at the trade-in pricing below.Comparado con el registro de dispositivos retirados: los sensores cuyo anfitrión está retirado califican para un reemplazo TEROS One Single gratis 1:1. El registro de esta instalación tiene un nodo retirado (H3210008273, sin sensor emparejado), así que hay 0 canjes gratis — todas las mejoras usan el precio de canje de abajo.

The gateway updates to WP5 and pushes it to every device that is online and communicating at the scheduled time (the go/no-go is: online, battery ≥ 30%, signal ≥ 50%). Devices that are offline at that moment simply stay on WP4 — they are not harmed, they just don't get the new firmware. The catch is compatibility, not damage: a WP4 device needs a WP4-matched gateway to keep communicating. At this facility the gateway (H2100002017) is already on WP5, so the list below is about recovering WP4 stragglers and planning sensor upgrades, not preparing for a first push. Updates and re-runs are done remotely by AROYA; keeping the fleet online is the site's responsibility.

1. P0Work the "Offline" list — those devices are still on WP4. The gateway here is already on WP5, so anything that was offline at the push stayed on WP4 (unharmed) and won't rejoin the mesh until it's brought current. Replace batteries and shore up signal so each meets online + battery ≥ 30% + signal ≥ 50%, then coordinate a short WP4 gateway revert + re-run with AROYA to catch them up.
2. P1Shore up the "At risk" list. Marginal battery/signal devices may drop out around the push window — plan battery swaps and repeater coverage now.
3. P2Decide what to retire or trade in instead of recovering. For dead/legacy sensors you won't bring back, mark them for a TEROS One / Climate One upgrade in the planner above rather than spending effort reviving them — and claim the free trade-in above first.
4. P3Gateway: nothing to do. The single gateway H2100002017 is online and already on WP5 (confirmed live, ggVersion = 2) — the gateway side of the migration is complete.
5. After the push, recover any stragglers. Devices that were offline can still be brought current later by reverting a gateway to WP4, bringing them online, re-running, then returning the gateway to WP5 — there's no time limit. Keep the mixed WP4/WP5 window short, though: mixed firmware on one network long-term can cause connectivity issues.
6. Note: existing WP4 gear keeps working as-is; new AROYA equipment requires WP5, which is the reason to update.

Method & scope. One row per physical device; an attached sensor (TEROS-12, Atmos-14, SQ-521 PAR, ES-2, TEROS One) is folded into the radio it plugs into, and sensor-head serials are masked — locate hardware on the floor by the H-prefix radio serial only. Class by serial prefix (H111 = climate station, H21x = gateway, H31x/H32x/H33x/H34x = node). Readiness reflects the WP5 go/no-go — a device receives WP5 only if it's online with battery ≥ 30% and signal ≥ 50% at the scheduled push; otherwise it stays on WP4 (unharmed) and can be recovered later via a WP4 gateway revert. Telemetry: AROYA public API, continuous 24 h window (2026-06-10 → 2026-06-11). Flags: battery crit<3.0/warn<3.2 V; RSSI crit<-95/warn<-85 dBm; link crit<40/warn<60; travel crit>60/warn>30 s; last-seen >48 h = offline. Priorities: P0 = act before the push, P1 = shore up, P2 = plan/trade-in, P3 = verify only. This is a device-readiness report — cultivation metrics (dryback in absolute pp, irrigation P0–P3 day-phases) are covered in the facility's cultivation audits, not here.