High Season Building 3 · Facility 2773

Mesh backbone:Red troncal: 88 of 200 devices are online and communicating right now, 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 4 gateways on record, all already on ggVersion 2 (WP5); 3 are online. Gateway H2100002348 has been silent since 2025-04-16 — confirm in the AROYA app whether it is decommissioned before the push. The push is run remotely by AROYA; a site visit is the exception, not the default.

Your fleet is 200 physical devices: 169 substrate nodes (radio + TEROS-12), 16 climate stations (H111… radio + Atmos-14), 11 range-extender repeaters (H110…) and 4 gateways (H210…, all on WP5). Across the 169 substrate nodes, 68 have a reporting attached sensor, 0 are alive but the sensor isn’t reporting (reseat the probe / check the connector), 98 are offline with the node, and 3 have no sensor paired. Attached sensors (166 TEROS-12, 15 Atmos-14) ride on their host radio for the WP5 push.

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 in the current snapshot — no hosts are flagged retired. Retire a TEROS-12 host and de-pair its sensor to make it eligible, then re-run this report.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 en la instantánea actual.

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 are online in the AROYA app. The gateway carries the push; all 4 gateways are on WP5 (ggVersion 2). Verify the silent gateway H2100002348 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) 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, H210 = gateway, H311/H321 = substrate node, H110 = repeater). Verdict is sourced from the live SPA /devices/?facility=2773 ggVersion + device snapshot pulled 2026-07-14. Device health uses the live snapshot — online status, battery %, RSSI indicator (0–8 bars), link quality and last-communication timestamp — not 24-hour telemetry percentiles. Fields the live snapshot does not carry (24 h battery / signal / link percentiles, sensor travel time, gap-over-60-min counts) are shown as “—”, not estimated. Readiness reflects the WP5 go/no-go — a device receives WP5 only if it is online and healthy at the scheduled push; otherwise it stays on WP4 (unharmed) and can be recovered later via a WP4 gateway revert. 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.