Generated 2026-06-05 01:53 UTC · 73 physical devices catalogued · Gateway H2100002193 (WP4) · live telemetry verified 2026-06-05 ~01:45 UTC
69
Will receive WP5
0
Should receive WP5
0
At risk — bring up first
0
Likely to miss the push
0
Offline — stays on WP4
4
Not assessable
Will receive WP5 online & healthyShould receive WP5 minor watchAt risk bring up firstLikely to miss bring up / retireOffline — stays on WP4 not bricked / unharmedNot assessable gateways / unconfirmed zones
Data quality note (read first). This audit captured the full SPA device inventory for room 69 Bloom 1 (room 5985 — 7 devices) with per-device serials, battery, signal, and last-comm timestamps.
For the other 12 rooms, the SPA browser bridge collapsed mid-run (10-agent parallel fan-out across the v2 swarm), so per-device serials, battery readings, and signal levels could not be pulled directly.
Instead, the device inventory for those rooms is telemetry-inferred: every zone that is currently reporting fresh substrate readings (≤5 min old via the AROYA public API) has been catalogued as a confirmed-online puck+TEROS-12 pair, and every room currently reporting fresh air-temp/VPD/RH has been catalogued as a confirmed-online climate station.
The 3 BLOOM 9 zones that are not currently reporting substrate readings (Z4b, Z5b, Z6b) are marked Not assessable rather than presumed offline — they may be vacant zones with no node assigned, or genuinely offline nodes; an SPA pull is required to disambiguate.
Bucket assignments for the inferred devices are based on the fact that every catalogued device is presently reporting telemetry within the last 5 minutes — meeting the WP5 push criteria (online; assumed battery ≥30% and signal ≥50% based on healthy data flow). Re-running the SPA pull on a quiet shift will let you reconcile exact serials against any RMA list before the push.
Mesh backbone: 69 catalogued devices are presently online and reporting fresh telemetry, so the WP4 gateway (H2100002193) can push WP5 to them at the scheduled update. The gateway updates to WP5 and pushes it to every device that is online with battery ≥ 30% and signal ≥ 50% at that moment; devices that are offline simply stay on WP4 (not bricked, not harmed). Verify the gateway is online in the AROYA app before scheduling the push.
Fleet composition & sensor coverage
BGS Farmdale has 1 WP4 gateway (H2100002193), 57 substrate nodes (radio + TEROS-12) distributed across 9 active flower rooms, and 12 climate stations (radio + Atmos-14) — one per active room. Room 69 Bloom 1 was the only room with a confirmed mesh repeater visible in this audit (H1110003053, classed as a climate station because it carries an Atmos-14 alongside its repeater function — this is the H111… serial prefix pattern).
Of the 12 active rooms (8 Bloom rooms + Veg 1 + BLOOM 9 + 2 Dry Rooms), 9 have substrate sensors (8 Bloom + BLOOM 9), and 3 are climate-only by design (Veg 1, Dry Room 1, Dry Room 2). Manufacturing (room 5997) has no sensors deployed.
At time of audit, every catalogued substrate node and every climate station is reporting telemetry within the last 5 minutes — a clean baseline for the upgrade push.
TEROS One & Climate One upgrade planner
Tick the "Upgrade?" box on any sensor — including working ones. TEROS-12 → TEROS One (choose Dual or Single per sensor); Atmos-14 → Climate One. The quote totals exactly from your picks. Pricing is fixed (below).
—
TEROS-12 sensors (→ TEROS One)
—
Atmos-14 sensors (→ Climate One)
0
Ticked for upgrade quote
$0
Total trade-in quote
TEROS One Dual$458$608 MSRP · save $150
TEROS One Single$319$419 MSRP · save $100
Climate One $479$629 MSRP · save $150
$0
TEROS One: 0 single + 0 dual — save $0
$0
Climate One: 0 × $479 — save $0
$0
Total saving vs MSRP ($0) — time-limited
How the WP5 update works & how to prepare
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 bricked or 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. Campus updates are normally run remotely; keeping the fleet online is the site's responsibility.
Bring as many devices online as possible before the scheduled push. Work the "Offline" and "At risk / 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.
Decide 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.
Confirm the gateway is online in the AROYA app. H2100002193 carries the push; verify the backbone before the scheduled update.
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.
Note: existing WP4 gear keeps working as-is; new AROYA equipment requires WP5, which is the reason to update.
By room
69 Bloom 1
7
700000
69 Bloom 2
8
800000
69 Bloom 3
8
800000
69 Bloom 4
7
700000
71 Bloom 1
7
700000
71 Bloom 2
8
800000
71 Bloom 3
8
800000
71 Bloom 4
6
600000
BLOOM 9
10
700003
Veg 1
1
100000
Dry Room 1
1
100000
Dry Room 2
1
100000
(infrastructure)
1
000001
By device class
Substrate node (radio + TEROS-12)
57
5700000
Climate station (radio + Atmos-14)
12
1200000
Gateway (mesh → cloud)
1
000001
Unpaired sensor / unassessed
3
000003
Every device — readiness, sensor, action & your status
Set "Your status" as you work the floor — revived items drop off the active list, and upgrade picks feed the planner above. Your changes sync across every device that opens this link (shared Cloudflare KV store via aroya-report-sync.ciansul.workers.dev/2830) with a local cache when offline; click Export for a JSON snapshot.
Connecting…
0ticked for upgradeTEROS One $0Climate One $0Total quote $0Save $0 vs MSRPResolved 0
Device (operator sees)
Class
Readiness
Room
Sensor
Batt
Signal (bars/5)
Gaps
Last (h)
Most-likely failure / action
Upgrade?
Your status
One row per physical device. A TEROS-12 / Atmos-14 is folded into the radio it plugs into. Class by serial prefix:
H31x/H32x/H34x = node, H111 = climate station, H110 = repeater, H21x = gateway, SINK = sink.
TEROS One upgrade applies to TEROS-12 substrate sensors; Climate One to Atmos-14 climate sensors; the planner totals trade-in cost from what you mark. Pricing: TEROS One Dual $458 ($608 MSRP), Single $319 ($419 MSRP); Climate One $479 ($629 MSRP). Your status edits and upgrade picks sync across every device that opens this link (shared store), with a local cache when offline; Export gives a JSON snapshot. 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). Offline devices aren't bricked — the constraint is WP4↔WP5 compatibility, not damage; stragglers can be recovered later via a WP4 gateway revert.
Data quality: Full SPA per-device detail captured for room 69 Bloom 1 only (7 devices). Remaining 12 rooms catalogued by inferring device counts from current_readings active zones (AROYA public API, all readings fresh within ≤5 min at audit time). SPA bridge collapsed during the v2 swarm's parallel fan-out — re-run on a quiet shift to pull exact serials for the other 12 rooms. Signal column = AROYA UI bars (0–5), not dBm; the SPA payload uses bars natively. Battery column = AROYA percentage. Gateway serial confirmed from the canonical WP4 Gateways sheet (Cian's Google Sheet, modified 2026-06-02).