TRU Infusion · Facility 3015

Mesh backbone:Red troncal: 292 of 324 non-gateway devices are online and communicating on the live snapshot, so the gateways 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 10 gateways on record but only 5 are currently online (4 on WP4 firmware, 1 on WP5) — the remaining 5 report WP5 (ggVer 2) but have been dark since 2022–2024 and appear decommissioned; confirm in the AROYA app before the push. The push is run remotely by AROYA; a site visit is the exception, not the default.

Your fleet lists 71 radios as “repeaters”; the serial prefix splits them into 12 range-extender / IO radios (H1100…) and 59 climate stations (H1110…) — a repeater-class radio with an Atmos-14 attached. Behind the gateways sit 253 substrate nodes (H3210…), of which 251 carry a paired TEROS-12 probe and 2 have no sensor attached. Attached sensors (TEROS-12 on the nodes, Atmos-14 on the climate stations) ride on their host radio for the WP5 push — there is nothing to update on the sensor itself. TEROS-12 hosts are the free 1:1 TEROS One Single replacement candidates once retired.

A retired TEROS-12 host qualifies for a free 1:1 TEROS One Single replacement when its radio is off-air > 30 days and the sensor has been physically removed / de-paired. This facility has 1 qualifying unit.Un anfitrión TEROS-12 retirado califica para un reemplazo TEROS One Single gratis 1:1 cuando lleva > 30 días sin conexión y el sensor fue retirado. Esta instalación tiene 1.

Host radio	Sensor	Room	Entitlement
H3210008342	de-paired / removed	F-35	FREE 1:1 TEROS One Single

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 (H-prefix radio serial); an attached sensor (TEROS-12 on nodes, Atmos-14 on climate stations) is folded into the radio it plugs into and its head serial is masked — locate hardware on the floor by the H-prefix radio serial only. Class by serial prefix: H2100 = gateway, H3210 = substrate node, H1110 = climate station, H1100 = range-extender / IO radio. Gateway ggVersion and every device value here come from the live SPA /devices/?facility=3015 snapshot pulled 2026-07-14 (admin-tier; portal_api returns null for ggVersion). Readiness reflects the WP5 go/no-go from that snapshot — online status, battery %, RSSI, link quality and last-communication — not 24-hour telemetry percentiles. Battery % is shown for battery-powered nodes only; climate stations and range-extenders are line-powered, so battery, travel-time and gap-count read “—” (n/a) rather than a fabricated value. A device receives WP5 only if it is online at the scheduled push; otherwise it stays on WP4 (unharmed) and can be recovered later. This is a device-readiness snapshot — devices recover and reconnect over time; re-pull to refresh.