United Medical Alliance LLC · Facility 2795

Mesh backbone:Red troncal: 41 of 88 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 16 gateways on record: 6 are online and already on WP5 (ggVersion 2) and carry the push — H2110001276, H2110001277, H2110001278, H2110001279, H2110001300 and H2110001301. The other 10 gateways are offline; one of them (H2100002302) is the only unit still on WP4 (ggVersion 1). The recovery job is the 47 offline devices: 22 were active within the last ~6 months and are realistic to bring back before the push, and 25 have been dormant longer. The push is run remotely by AROYA; a site visit is the exception, not the default.

This fleet is 88 physical radios: 16 gateways, 12 repeater-class radios and 60 substrate nodes. The 12 repeater-class radios split by serial prefix into 11 climate stations (H1110…, Atmos-14 attached) and 1 range-extender/IO radio (H1100…, no sensor). Across the 60 substrate nodes, 29 have a reporting attached sensor, 0 are alive but the sensor is not reporting (reseat the probe / check the connector), and 31 are dark with the node. Sensors present: 58 TEROS-12, 11 Atmos-14 climate sensors, 1 SQ-521 PAR and 1 ES-2 EC/temp — each attached sensor rides on its host radio for the WP5 push. TEROS-12 hosts are the free 1:1 TEROS One Single replacement candidates once retired.

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. No devices at this facility are currently flagged retired, so none qualify for the free replacement today — this pool populates automatically once a TEROS-12 host is retired and its sensor removed.Comparado con el registro de dispositivos retirados: los anfitriones retirados califican para un reemplazo TEROS One Single gratis 1:1. Ningún dispositivo está marcado como retirado en esta instalación, así que por ahora nada califica.

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 any gateway shown offline in the list above) 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) 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 (H111x = climate station, H21xx = gateway, H31xx = substrate node). Verdict is sourced from the live SPA /devices/?facility=2795 ggVersion + device snapshot pulled 2026-07-14. Device health uses the live snapshot only — online state, last-reported battery %, and last-communication time — not 24 h telemetry percentiles. This snapshot does not carry RSSI (dBm), link-quality, travel-time or gap-count percentiles, so those columns are shown as “—” rather than estimated. Readiness reflects the WP5 go/no-go: an online, healthy device receives WP5 at the push; an offline device stays on WP4 (unharmed) and can be recovered later via a WP4 gateway revert. Buckets: online → will receive; offline ≤ 30 d → at risk (bring up first); offline 30–180 d → likely to miss; offline > 180 d → offline/stays on WP4; last-seen defines 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 are covered in the facility's cultivation audits, not here.