Generated 2026-06-05 01:57 UTC · Org: Gem Star · Gateway: H2100002306 · Operator state syncs across every device that opens this link.
Partial pull — Data Quality: Pulled active page 1 of 4 (25 of 89 active devices) before the opencli Browser Bridge dropped under parallel swarm load. Pages 2-4 of active and the full retired upgrade pool were NOT fetched in this run. Counts in the KPI strip reflect ONLY the 25-device sample plus the 1 known WP4 gateway. Real totals will be larger; the per-device table is complete for the rows shown but does not enumerate the remaining 64 active devices. Re-run once the SPA browser tab in app.aroya.io is refreshed to get the full inventory.
24
GREEN-READY online + batt ≥ 30% + signal OK
0
YELLOW-RECOVERABLE bring up before push
1
RED-OFFLINE won't receive WP5 — stays on WP4 (not harmed)
1
GATEWAY-WP4 pushes update; revert path for stragglers
How the WP4 → WP5 update works at Bloomfield Building 2
The gateway updates to WP5 and pushes it to every device online at the scheduled time. Go/no-go is: online, battery ≥ 30%, signal ≥ 50%. Devices that are offline at that moment simply stay on WP4 (unharmed — not bricked); the constraint is WP4 ↔ WP5 compatibility, not damage. Stragglers can be recovered later by reverting the gateway to WP4, bringing the device online, re-running the push, then returning the gateway to WP5. Remote is the default — no site visit needed unless the on-floor team needs hands-on to revive specific nodes.
Bring as many devices online as possible before the scheduled push. Work the YELLOW and RED rows below — replace batteries, walk weak-signal nodes closer to a repeater or reseat the radio.
Confirm the gateway is online. H2100002306 carries the push for the whole site — verify in the AROYA app first.
Decide what to retire instead of recovering. For dead/legacy sensors you won't bring back, mark them for a TEROS One / Climate One upgrade rather than spending effort.
After the push, recover any stragglers. Revert the gateway to WP4, bring the offline node up, re-run, return the gateway to WP5. No time limit. Keep the mixed WP4/WP5 window short — long-term mixed firmware can cause connectivity issues.
Existing WP4 gear keeps working as-is. The reason to update: new AROYA equipment requires WP5.
Sibling site coordination
Bloomfield Building 1 & 2 are a paired update. Bloomfield Building 1 (facility 2872) is a sister site under the same Gem Star org and is being audited in parallel. Coordinate the WP5 push across both buildings with the same on-site POC; gateway serials differ (this site = H2100002306, Building 1 = H2100002390).
TEROS One & Climate One upgrade planner
Tick the Upgrade? box on any sensor — including working ones. TEROS-12 → TEROS One (Dual or Single per sensor); ATMOS-14 → Climate One. The quote totals exactly from your picks; pricing fixed below.
TEROS One Dual$458$608 MSRP · save $150 ·
TEROS One Single$319$419 MSRP · save $100 ·
Climate One $479$629 MSRP · save $150
0
Ticked for upgrade quote
$0
Total trade-in quote
$0
TEROS One: 0 single + 0 dual
$0
Climate One: 0 × $479
By room (observed sample)
Room
Devices
Readiness mix
(unassigned)
3
20100
Dry Room
2
20000
Flower 10
2
20000
Flower 11
2
20000
Flower 12
2
20000
Flower 13
2
20000
Flower 14
2
20000
Flower 15
2
20000
Flower 16
2
20000
Flower 17
2
20000
Flower 18
2
20000
Veg 2
2
20000
nGREEN-READYnYELLOWnREDnGATEWAYnRETIRED
Every device — readiness, sensor, action & your status
0
ticked for upgrade
TEROS One $0
Climate One $0
Total quote $0
Save $0 vs MSRP
Resolved 0
Serial
Model
FW
Online
Batt
Signal
Last comm
Room
Readiness
Upgrade?
Dual / Single
Your status
Recommendation panel
Gateway: H2100002306 is online and serves all 89 active devices at this site. Verify in app.aroya.io before the scheduled WP5 push.
Mesh backbone (observed sample): 14 of 14 H110/H111-class repeaters in the sample are online on firmware 1.2.1.0 (one on 1.1.14.0 — H1110003478). All are above the signal/battery thresholds for the WP5 push.
Climate & substrate sensors (observed sample): 11 of 11 ATMOS-14 sensor heads in the sample report battery 100% and recent communication. One node (17066-01-822 in Flower 18) shows online=true but battery=100% and last comm 2026-06-05 — clean.
Bloomfield Buildings 1 & 2 should be scheduled in the same push window. Same Gem Star org, same Bloomfield campus — coordinate the on-site POC and confirm both gateways (this site = H2100002306, Building 1 = H2100002390) before the push.
Re-pull the remaining inventory before publishing externally. 64 active devices (pages 2-4) and the full retired upgrade pool are not in this sample — actual GREEN/YELLOW/RED counts will scale with the full fleet.
One row per physical device. Class by serial prefix: H21x = gateway, H110/H111 = mesh repeater (range extender / climate-station radio), 17xxx-xx-xxx = TEROS-12 / ATMOS-14 sensor head. TEROS One upgrade applies to TEROS-12 substrate sensors; Climate One replaces ATMOS-14. Your status edits and upgrade picks sync across every device that opens this link (shared cross-device store) with a local cache when offline; Export gives a JSON snapshot the next data pull reconciles against. Readiness reflects the WP5 go/no-go — a device receives WP5 only if it is online with battery ≥ 30% and signal ≥ 50% at the scheduled push; otherwise it stays on WP4 (unharmed). Offline devices aren't bricked — the constraint is WP4↔WP5 compatibility, not damage; stragglers can be recovered later via a WP4 gateway revert. Telemetry: AROYA portal_api/devices, pulled 2026-06-05 01:57 UTC. Sample = first 25 of 89 active devices.