AROYA · Pre-WP5 Firmware Update Readiness

AYR: Oasis · Facility 2804 · Nevada (AYR Wellness · NASDAQ:AYR)

Generated 2026-06-05 01:43 UTC · Gateway H2100002313 (single WP4 gateway) · Page-1 sample (25 of 113 devices, 22.1%) — see Data Quality below

Partial inventory — page-1 sample only. The portal_api fleet endpoint returned 25 of 113 active devices before the AROYA browser bridge dropped (CLAUDE.md memory: feedback_spa-config-not-parallel-safe — recovery requires a manual refresh of app.aroya.io). All counts in the KPI strip below are page-1 only. The retired-pool pull (retired=true) was also blocked, so the TEROS One / Climate One free-upgrade pool is not yet sized. A complete re-run is needed to ship the operator-facing planner with full numbers.

Will receive WP5

Should receive WP5

At risk — bring up first

Likely to miss the push

Offline — stays on WP4

Not assessable (gateway)

KPIs above reflect the 25-device page-1 sample. Full fleet = 113 active devices.

Will receive WP5 online & healthyShould receive WP5 minor watch At risk bring up firstLikely to miss bring up / retire Offline — stays on WP4 not bricked, not harmedNot assessable gateway

Mesh backbone (page-1 sample): The single gateway H2100002313 is up and reporting; 3 range-extender repeaters in the Storage room (H1100003182, H1100003188, H1100003737) are online (PoE). Every other page-1 device — substrate pucks, ATMOS 14 climate sensors, additional repeaters — is offline with lastCommunication ranging from July 2021 to August 2024. Pattern matches the dormant-facility shape Cian shipped for Antrinity LA (1920, 0/46 online): a single WP4 gateway in a site whose deployment was either decommissioned or has had hardware shelved into "Storage" while still attached to the facility record. The WP5 push will go to the gateway and to whatever devices are online at the scheduled time — for AYR Oasis, that may be just the gateway + the live repeaters unless the floor team brings nodes/sensors back up first.

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 don't meet the criteria simply stay on WP4 — they are not bricked, not harmed. The constraint is WP4↔WP5 compatibility, not damage. You can recover stragglers later by reverting a gateway to WP4, bringing them online, re-running, then promoting to WP5 — no time limit. Remote is the default; a site visit is the exception.

Bring as many devices online as possible before the scheduled push. Work the "Offline" / "At risk / Likely to miss" lists below — replace batteries and shore up signal so each device hits the go/no-go thresholds before the gateway pushes WP5.
Decide what to retire or trade in instead of recovering. Dormant TEROS-12 substrate sensors and ATMOS 14 climate sensors qualify for the TEROS One / Climate One upgrade pricing (see planner section once the retired-pool pull completes).
Confirm gateway is online in the AROYA app. Gateway H2100002313 carries the push for AYR: Oasis. It is currently up.
After the push, recover stragglers. Devices that were offline can still be brought current later — revert a gateway to WP4, bring them online, re-run.
Existing WP4 gear keeps working as-is; the reason to update is that new AROYA equipment requires WP5.

By room (page-1 sample)

(unassigned)	1	0 0 0 0 0 1
Flower Room 5	2	0 0 0 0 2 0
Flower Room 5 Z10	1	0 0 0 0 1 0
Storage	17	3 0 0 0 14 0
VEG- Zone 19	2	0 0 0 0 2 0
VEG- Zone 21	2	0 0 0 0 2 0

By device class (page-1 sample)

Substrate node (radio + TEROS-12)	9	0 0 0 0 9 0
Climate station (radio + Atmos-14)	5	0 0 0 0 5 0
Repeater (range extender)	5	3 0 0 0 2 0
Gateway (mesh → cloud)	1	0 0 0 0 0 1
Unpaired sensor	5	0 0 0 0 5 0

Page-1 device roster — readiness, sensor, action & your status

Set "Your status" as you work the floor — revived items drop off the active list. Upgrade picks feed the trade-in planner. State syncs cross-device via the AROYA report-sync Worker.

Hide resolved Connecting…

0ticked for upgrade TEROS One $0Climate One $0 Total quote $0 Save $0 vs MSRP Resolved 0

Device	Class	Readiness	Room	Sensor	Batt %	RSSI (raw)	Last comm (h)	Last (date)	Failure / action	Upgrade?	Your status

Account context

Customer: AYR Wellness (NASDAQ: AYR) — vertically integrated multi-state operator headquartered in Boston, MA, with cultivation in NV, AZ, FL, IL, MA, NJ, OH, PA. "Oasis" is the Nevada site.

Email-context cache (Addium inbox): No firmware-related emails found for AYR Oasis. Treat as a cold contact for the WP5 push — the AROYA account team should identify the right corporate POC at AYR before scheduling the rollout for this gateway.

Recommended next step (Cian / Brad): Surface this dormant-gateway status to AYR corporate ops. Two paths — (1) revive the deployment (battery swap + reseat campaign, then schedule WP5), or (2) confirm the site has been decommissioned and retire the gateway record. Either way the single WP4 gateway needs an explicit go/no-go from the customer before the next OTAP window.

Data quality

Page 1 of 5 only (25 of 113 active devices, 22.1%). The portal_api fleet pull successfully returned page 1 via opencli aroya raw --path '/portal_api/devices/?facility_id=2804&retired=false'. Page-2 pagination triggered a Browser Bridge disconnect; the sub-agent cannot recover the bridge (per memory feedback_spa-config-not-parallel-safe, recovery requires a manual refresh of app.aroya.io in the user's logged-in browser).

Retired-pool pull also blocked. The TEROS One / Climate One free-upgrade planner (sized from retired=true per CLAUDE.md memory reference_aroya-retired-devices-from-api) cannot be populated without that pull. The planner UI is stubbed but the eligible-sensor counts default to zero.

Re-run needed: when the AROYA app browser tab is refreshed, re-run opencli aroya raw --path '/portal_api/devices/?facility_id=2804&retired=false&page=N' for pages 2–5, plus the retired-pool pull, then re-generate this report. The page-1 pattern (1/24 substrate devices online, gateway + 3 PoE repeaters live, 17 of 25 devices in Storage with last-comm 2021–2024) is consistent with a dormant facility — but full-fleet confirmation is mandatory before any customer-facing commitment.

One row per physical device. Class derived from serial-number prefix (H21x = gateway, H110 = repeater range-extender, H111 = climate station, H31x/H32x/H34x = substrate puck, A14*/T12* = orphan sensor). 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, not bricked, recoverable). Your status edits and upgrade picks sync across every device that opens this link via the AROYA report-sync Worker (https://aroya-report-sync.ciansul.workers.dev/2804) with a local cache when offline. Source: AROYA portal_api /portal_api/devices/?facility_id=2804&retired=false&page=1 at 2026-06-05 01:43 UTC. WP4→WP5 firmware language: per Cian's customer framing (NorCal Feb 2026, Case 00019910) — offline devices stay on WP4 unharmed; recovery is reversible; remote is the default.