Green Trap Old Canal Way · Facility 3322

Mesh backbone:Red troncal: 34 devices are online and communicating, so the gateway can push WP5 to them at the scheduled update. The gateway updates to WP5 and pushes it to every device online at that moment; devices that are offline simply stay on WP4 (unchanged — not harmed). This facility has 2 gateways on record, both already on WP5 (ggVer=2): H2100002537 “gateway office” is online and is the active push path; H2100002120 has been silent since 2026-07-11 — confirm in the AROYA app whether it is still needed before the push. The push is run remotely by AROYA; a site visit is the exception, not the default.

Your fleet lists 12 radios as “repeaters”; the serial prefix splits them into 8 range-extender/IO radios (H1100…) and 4 climate stations (H1110…) — a repeater-class radio with an Atmos-14 attached. Across the 45 substrate nodes (each carrying a TEROS-12), 25 have a reporting attached sensor, 3 are alive but the attached sensor isn’t reporting (reseat the probe / check the connector), and 17 are dark along with their node. The fleet also carries 4 Atmos-14 climate sensors and 4 ES-2 EC/temp sensors on the repeater radios — attached sensors ride on their host radio for the WP5 push. The two gateways are the updaters and are not counted as push recipients.

Cross-referenced against the retired-device register (portal_api · retired=true): sensors whose host puck/radio is flagged retired qualify for a free 1:1 TEROS One Single replacement. This facility has 0 qualifying units — the register lists no retired hosts here, so there is nothing free to claim this cycle. Paid TEROS One / Climate One upgrades are still available 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. Esta instalación tiene 0.

No devices currently qualify for the free trade-in.Ningún dispositivo califica actualmente para el canje gratuito.

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, ES-2) 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 (H1110 = climate station, H1100 = range-extender/IO repeater, H21xx = gateway, H32xx/H33xx/H34xx = substrate node). Readiness reflects the WP5 go/no-go — a device receives WP5 only if it is online at the scheduled push; otherwise it stays on WP4 (unharmed) and can be recovered later via a WP4 gateway revert. These are live-snapshot values pulled from the SPA /devices/?facility=3322 on 2026-07-14 — per-device online state, battery %, RSSI and last-communication as reported at pull time. This is a point-in-time snapshot, not a 24 h telemetry percentile: 24 h battery/signal/link percentiles, radio travel time and gap counts were not available, so those columns are left blank (n/a) rather than estimated. ggVersion, room names and trade-in counts are taken directly from the live records; nothing on this page is inferred where the field was empty. Priorities: P0 = act before the push, P1 = shore up, P2 = plan/trade-in, P3 = verify only. This is a device-readiness report — cultivation metrics are covered in the facility’s cultivation audits, not here.