GTI Rock Island IL · Facility 2753

Mesh backbone:Red troncal: 303 of 307 devices are online and communicating, so the gateways can push WP5 to every device that is online at the scheduled update. All seven gateways already report ggVersion 2 (WP5); six are online now and one (H2100002346) has been silent since 2026-06-02 — it already reads WP5, so confirm/restore its uplink in the AROYA app before the push. Devices that are offline at the moment of the push simply stay on WP4 (unchanged — not harmed). The push is run remotely by AROYA; a site visit is the exception, not the default.

Your fleet is 307 physical radios. The 43 repeater-class radios split by serial prefix into 23 range-extender/IO radios (H1100…) and 20 climate stations (H1110… — a repeater-class radio with an Atmos-14 attached). The 257 substrate nodes split into 243 TEROS-12 hosts (H3110… / H3210…) and 14 next-generation TEROS One hosts (H3430…, TEROS-15). Across the fleet, 277 radios carry a reporting attached sensor (TEROS-12, Atmos-14, and already-upgraded TEROS One probes). Seven Gateway Hybrid units (H2100… / H2110…) form the backbone — all on ggVersion 2 (WP5). Attached sensors ride on their host radio for the WP5 push.

The FREE 1:1 TEROS One Single replacement applies to retired TEROS-12 hosts (serial H3210…) that are off-air > 30 days with the sensor already removed or de-paired. Cross-referenced against this facility's live inventory, 0 units qualify — every TEROS-12 host on record is still in service with its sensor attached.El reemplazo TEROS One Single gratis 1:1 aplica a anfitriones TEROS-12 retirados (serie H3210…) fuera de línea > 30 días con el sensor ya retirado. En esta instalación, 0 unidades califican.

No retired hosts qualify at this facility right now. This section stays on the report — if a TEROS-12 host is retired and its sensor removed, it becomes eligible for a free 1:1 replacement.No hay anfitriones retirados elegibles en esta instalación en este momento.

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 offline gateway H2100002346, silent since 2026-06-02) 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 only); an attached sensor (TEROS-12, Atmos-14, 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 (H11 = repeater / climate station, H21 = gateway, H31/H32/H34 = substrate node). Readiness reflects the WP5 go/no-go — a device receives WP5 only if it is online with battery ≥ 30% and link ≥ 50% at the scheduled push; otherwise it stays on WP4 (unharmed) and can be recovered later via a WP4 gateway revert. Source: a live device snapshot pulled from the SPA /devices/?facility=2753 on 2026-07-14 — verdicts use the live snapshot fields (online, battery %, signal, link quality, last-comm) and live per-gateway ggVersion. This is not a 24 h telemetry-percentile audit: battery/signal/link are the current live values, not p05 percentiles, and travel-time and 60-min gap counts are not computed from a single snapshot (shown blank). ggVersion is admin-tier gated on the SPA; portal_api returns null for it. This is a snapshot in time — devices recover and reconnect over time.