Pleasantrees 1 · Facility 1228

Mesh backbone:Red troncal: 175 of 207 devices are online and communicating, so the gateways can push WP5 to them at the scheduled update. This facility runs two gateways of different generations, both online: H2100002009 is already on WP5 (ggVer 2) with 76 devices paired to it, and H2100002010 is still on WP4 (ggVer 1) with 127 devices paired — that WP4 gateway is the one that receives the push. A gateway updates to WP5 and pushes it to every device online at that moment; devices offline at push time simply stay on WP4 (unchanged — not harmed). The push is run remotely by AROYA; a site visit is the exception, not the default.175 de 207 dispositivos están en línea. Dos gateways de distinta generación, ambos en línea: H2100002009 ya en WP5 (ggVer 2, 76 dispositivos) y H2100002010 en WP4 (ggVer 1, 127 dispositivos). Los dispositivos fuera de línea quedan en WP4 (sin daño). La actualización la realiza AROYA de forma remota.

Cross-referenced against the retired-device register (retired=true): a host qualifies for a free 1:1 TEROS One Single replacement only when its radio is flagged retired and its sensor has been removed. No devices are flagged retired at this facility in this pull, so nothing qualifies for the free program right now. Working TEROS-12 and Atmos-14 stations can still be upgraded at the trade-in price below — a customer choice, not required.Ningún dispositivo está marcado como retirado en esta consulta, por lo que nada califica para el reemplazo gratuito 1:1 en este momento. Las estaciones en servicio pueden mejorarse al precio de canje (opcional).

No retired hosts qualify at this facility.No hay anfitriones retirados elegibles en esta instalación.

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, so the goal is to have as many devices as possible online at the push. The update is run remotely by AROYA; keeping the fleet online is the site's responsibility.

1. P0Bring as many devices online as possible before the scheduled push. Work the "Offline" and "Likely to miss" lists — replace batteries and shore up signal so each meets online + battery ≥ 30% + signal ≥ 50%. Every device up at push time receives WP5; every device down stays on WP4.
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. P3Confirm the gateways/sinks are online in the AROYA app. The gateway carries the push; verify the backbone (especially the silent Gateway I) before the scheduled update.
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, 30-day window (2026-05-11 → 2026-06-10) sampled at four 2-day windows. 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.