Generated 2026-06-04 16:47 UTC · 264 physical devices (462 raw rows incl. folded sensors) · 30-day window, sampled at 4 points
Last device connection on record: none (no telemetry served; facility locked).
0
Will receive WP5
0
Should receive WP5
0
At risk — bring up first
0
Likely to miss the push
0
Offline — stays on WP4
264
Not assessable
Will receive WP5 online & healthyShould receive WP5 minor watchAt risk bring up firstLikely to miss bring up / retireOffline — stays on WP4 not brickedNot assessable gateways
Inactive customer — not in the active-facilities list. This facility is locked in AROYA and does not appear in the active-customer dropdown. The device registry is intact (462 records / 264 physical units), but the API serves no telemetry for it: every device chart is empty across the 30-day window and on historical probes back ~2 years, so no device has a connection on record and WP5 readiness cannot be assessed. Practical read for the firmware push: (1) they are not an active customer, and (2) they are likely a low priority for the WP5 update until/unless the account is reactivated and the fleet is brought back online. To reassess, reactivate the facility, bring the 2 gateways + 2 sinks online in the AROYA app, and re-run this report.
Fleet composition & sensor coverage
This fleet is 196 substrate nodes (H32x), 22 climate stations (H111x), 21 repeaters (H110x), 2 gateways, 2 sinks, and 21 unpaired Apogee SQ-521 PAR sensors — all currently dark / not reporting (no telemetry is served for this locked facility). Of the 196 nodes, 175 carry a paired TEROS-12 and 21 have no probe; the 22 climate stations each carry an Atmos-14. Because no device has a connection on record, every unit is shown as Not assessable rather than online/offline.
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).
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 gateways/sinks are online in the AROYA app. The gateway 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
Flower 1
10
0000010
Flower 2
10
0000010
Flower 3
9
000009
Flower 4
10
0000010
Flower 5
9
000009
Flower 6
10
0000010
Flower 7
9
000009
Flower 8
10
0000010
Flower 9
10
0000010
Flower 10
9
000009
Flower 11
10
0000010
Flower 12
11
0000011
Flower 13
10
0000010
Flower 14
7
000007
Flower 15
8
000008
Flower 16
9
000009
Flower 17
10
0000010
Veg 1
3
000003
Veg 2
4
000004
Veg 3
1
000001
Clone Room
19
0000019
Unassigned
76
0000076
By device class
Substrate node (radio + TEROS-12)
196
00000196
Climate station (radio + Atmos-14)
22
0000022
Repeater (range extender)
21
0000021
Gateway (mesh → cloud)
2
000002
Sink (mesh root)
2
000002
Unpaired sensor
21
0000021
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 save in this browser; click Export to send the snapshot back for the next pull.
Connecting…
0ticked for upgradeTEROS One $0Climate One $0Total quote $0Save $0 vs MSRPResolved 0
Device (operator sees)
Class
Readiness
Room
Sensor
Batt
RSSI
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
(sensor.puck). Class by serial prefix (the API hides a climate station as a
“repeater” when its Atmos-14 is offline): H31x/H32x/H34x = node, H111 = climate station, H110 = repeater,
H21x = gateway, SINK = sink. TEROS One upgrade applies to TEROS-12 substrate sensors; the planner totals
trade-in cost from what you mark. 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 the next data pull reconciles
against. 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.
Telemetry: AROYA public API, 30-day window sampled at four 2-day windows; silent devices re-pulled on a clean
recent window. Flags (telemetry proxy for the go/no-go): 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.