Cannamatics · Facility 2719

Mesh backbone & gateway firmware:Red troncal y firmware de gateways: Facility gateway fleet: all 12 active gateways are ALREADY ON WP5 (ggVersion 2, live SPA audit 2026-06-11) — 6 of 12 are online and carrying the mesh today. The gateway on the WP4 Gateways sheet, H2100002341, is confirmed WP5 and online — it has already been upgraded since the 2026-06-08 list snapshot, so there is no gateway firmware work left at this facility. The remaining story is on the device side: each online WP5 gateway serves WP5 to every device that is online and communicating at the scheduled push; devices that are offline simply stay on WP4 (unchanged — not harmed) and can be recovered later. 95 units are online and communicating today. The 6 offline gateways (silent since 2023–2025) are already on WP5 too — they are dormant capacity, not a firmware risk; decide whether to redeploy or retire them. A further 5 gateways are formally retired in the register. The push is run remotely by AROYA; a site visit is the exception, not the default.

6 of 12 active gateways online — all 12 already on WP5. Sheet gateway H2100002341 confirmed WP5 (already upgraded since the 2026-06-08 list snapshot). Source: live SPA device register (ggVersion 2 = WP5). The 6 offline units are also on WP5 — dormant, not a firmware risk.6 de 12 gateways activos en línea — los 12 ya están en WP5. El gateway de la lista, H2100002341, está confirmado en WP5. Fuente: registro de dispositivos SPA en vivo (ggVersion 2 = WP5).

Gateway	FirmwareFirmware	StatusEstado	Last commÚltima com.
H2100002341 WP4 sheet	WP5 ✓ (ggVersion 2)	online	2026-06-11
H2100002585	WP5 ✓ (ggVersion 2)	offline	2025-04-22
H2100004162	WP5 ✓ (ggVersion 2)	offline	2024-09-17
H2100004254	WP5 ✓ (ggVersion 2)	online	2026-06-11
H2100004310	WP5 ✓ (ggVersion 2)	online	2026-06-11
H2100004357	WP5 ✓ (ggVersion 2)	offline	2024-09-17
H2100004410	WP5 ✓ (ggVersion 2)	offline	2023-08-16
H2100004411	WP5 ✓ (ggVersion 2)	online	2026-06-11
H2100004412	WP5 ✓ (ggVersion 2)	offline	2025-09-09
H2100004603	WP5 ✓ (ggVersion 2)	online	2026-06-11
H2100004718	WP5 ✓ (ggVersion 2)	online	2026-06-11
H2100004720	WP5 ✓ (ggVersion 2)	offline	2024-03-05

Your fleet lists 32 radios as “repeaters”; the serial prefix splits them into 8 range-extender/IO radios and 24 climate stations (H111…) — a repeater-class radio with an Atmos-14 attached. Across the 109 substrate nodes, 71 have a reporting attached sensor, 0 are alive but the sensor isn’t reporting (reseat the probe / check the connector), 36 are dark with the node, and 2 have no sensor paired. Beyond TEROS-12s (108), this fleet also carries 24 Atmos-14 climate sensors and 2 SQ-521 PAR sensors — attached sensors ride on their host radio for the WP5 push.

Cross-referenced against the retired-device register (portal_api · retired=true, pulled 2026-06-10): this facility has 21 formally retired devices (5 gateways, 7 sinks, 5 repeaters, 2 nodes, 1 TEROS-12, 1 Atmos-14). Sensors whose host puck/radio is flagged retired qualify for a free 1:1 TEROS One Single replacement — here that's 2 free entitlements (below). Every other TEROS-12 / Atmos-14 upgrades at the trade-in pricing in the planner.Comparado con el registro de dispositivos retirados: esta instalación tiene 21 dispositivos retirados. Los sensores cuyo anfitrión está retirado califican para un reemplazo TEROS One Single gratis 1:1 — aquí son 2 canjes gratis (abajo). El resto usa el precio de canje del planificador.

Host radio	Sensor	Room	Entitlement
H1110003164	Atmos-14 (head ····-829)	RB-1	FREE 1:1 TEROS One Single
H3110010611	TEROS-12 (head ····3773)	SB1	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. P3Gateways: nothing to upgrade — keep the 6 online ones up. All 12 active gateways are already on WP5 (sheet gateway H2100002341 included), so the gateway side is done. Verify in the AROYA app that the 6 online gateways stay up through the push window, and decide whether the 6 dormant WP5 gateways (silent since 2023–2025) should be redeployed or retired.
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, 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 (H111 = climate station, H21x = gateway, H31x/H32x/H33x/H34x = node). Readiness reflects the WP5 go/no-go — a device receives WP5 only if it's online with battery ≥ 30% and signal ≥ 50% at the scheduled push; otherwise it stays on WP4 (unharmed) and can be recovered later via a WP4 gateway revert. Telemetry: AROYA public API, continuous 24 h window (2026-06-10 → 2026-06-11). Flags: battery crit<3.0/warn<3.2 V; RSSI crit<-95/warn<-85 dBm; link crit<40/warn<60; travel crit>60/warn>30 s; last-seen >48 h = 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 (dryback in absolute pp, irrigation P0–P3 day-phases) are covered in the facility's cultivation audits, not here.