AROYA
by Addium

Verano — FL (Palatka) · Device Health & Facility Status Audit

Facility 4462 · Org 3501 (Verano Holdings) · Window analyzed: 2026-05-21 → 2026-06-11 (21 days) · Generated 2026-06-11
⛔ FACILITY DARK — the entire mesh stopped reporting on 2026-05-25 at 22:12 UTC (17 days ago).
Every sensor series at Palatka ends within the same 3-minute interval. The gateway, all 12 nodes and the Climate One went silent simultaneously — a single upstream failure (gateway power or site uplink), not a radio or battery problem. No inbound report of this outage was found in support email. Palatka is the only live AROYA site in the $427K Verano enterprise rollout.
0 / 15
Mesh devices online
17 d
Since last data (May 25)
100%
Node battery (all 12, at last comm)
0
Active harvest groups
174 d
Flower 5 repeater offline (Dec 19)
29
Devices inventoried

Outage signature — one failure, not many

Every series from every reporting device at the facility ends between 22:09 and 22:12 UTC on 2026-05-25. Before that moment, the substrate sensors were reporting on a clean 3-minute cadence with zero gaps over 30 minutes for 4.3 straight days. Batteries on all 12 nodes read 100% at last communication. This pattern rules out node radios, batteries, and individual sensors: the failure is upstream — the gateway ("veg 5 nova core", H2110001107) lost power or the site lost its internet uplink. The gateway, sink and Climate One are PoE-powered, so the first physical check is the PoE switch / power circuit feeding the head-end, then the uplink.

May 21–25 · clean 3-min data
May 25 22:12 UTC → today · NO DATA (17 days)
ReportingDark
No support thread or case about this outage was found in the last 30 days of correspondence with Verano — the site appears to have gone dark unnoticed. Recommend raising it directly in today's 10:15 AM rollout call with Richard Callahan, Mitch Tipton and Dustin Shroyer.

Device status by room (SPA status, authoritative)

Room "F9 novacore vs bio" — 14 mesh devices, all offline since 2026-05-25

DeviceSerialModelZoneBatteryStatusLast comm (UTC)
veg 5 nova coreH2110001107Gateway (PoE)zone 1 novaOFFLINE2026-05-25 22:10
veg5 novaH4210004197Climate One (PoE)zone 1 novaOFFLINE2026-05-25 22:09
nova core e85 tbl3 botH3440012461Node ×2zone 1 nova100%OFFLINE2026-05-25 22:11
nova core gc tbl2 botH3440012462Node ×2zone 1 nova100%OFFLINE2026-05-25 22:10
nova gc tbl 2 bot b3H3440012489Node ×2zone 1 nova100%OFFLINE2026-05-25 22:10
bioH3440012466Node ×2bio100%OFFLINE2026-05-25 22:10
bio e85 tbl7 botH3440012470Node ×2bio100%OFFLINE2026-05-25 22:09
bioH3440012474Node ×2bio100%OFFLINE2026-05-25 22:10

"Node ×2" = paired radio units sharing a position (-2 suffixed serials), each hosting a TEROS One substrate sensor. 12 node radios + 12 TEROS One total.

Room "Flower 5" — 1 device, offline since 2025-12-19

DeviceSerialModelBatteryStatusLast comm (UTC)
RepeaterH3400002704Mesh Repeater (H340 = battery; legacy H11x = PoE)100%OFFLINE 174 d2025-12-19 14:58
The Flower 5 repeater predates the May outage by five months — separate issue. It is PoE-powered: check its power feed / port. Rooms F22, F32 and F16 have no AROYA devices assigned at all.

Last-known-good snapshot — 4.3 days before the blackout (May 21 → May 25)

The trial in F9 ("novacore vs bio", zones "zone 1 nova" vs "bio") was producing clean data right up to the outage. These are observed ranges from the final 4.3 days — shown for context only; this is NOT a 14-day audit window.

SignalZone 1 nova (6 TEROS One)Bio zone (6 TEROS One)
Substrate VWC (median per sensor)30.2 – 50.0 %22.9 – 63.0 %
Pore EC (typical, mS/cm)p50 ≈ 3.6
Substrate temp≈ 78.4 °F≈ 78 °F
Climate (Climate One, zone 1 nova)Observed May 21–25
Air temperature74.6 – 82.1 °F (p50 78.9)
Relative humidity46.8 – 72.6 % (mean ≈ 56)
CO₂850 – 1397 ppm (p50 1335)

Per-sensor VWC medians spread 23–63% across the bio zone — wide position-to-position variation worth reviewing once data is restored. Sensor H3440012461 (TEROS One) also logged one 2-day internal gap before the outage and is worth watching after recovery. No dryback or irrigation-phase metrics are quoted here: with no series after May 25 and no configured harvest group, computing them would require fabricating data.

2-week cultivation audit — not produced (and why)

The scheduled 14-day audit window (2026-05-28 → 2026-06-11) contains zero sensor data: the facility went dark three days before the window opened. Coverage is 0% of the required ≥90%. Per audit rules, missing days are never synthesized or modeled, so no cultivation audit is published for this window.

Additionally, the facility has no active harvest groups — the last two HGs ended in September 2025 (F22 and Flower 5 runs). The F9 trial has been running without a configured harvest group, which means no phase context (P0–P3 irrigation day structure, steering targets) can be attached to its data even when the mesh returns.

Sensor-fleet context for today's rollout call

Palatka runs the new-generation fleet: 12× TEROS One substrate sensors + Climate One. On 2026-06-09 Richard Callahan flagged TEROS One reading 5–15% higher VWC than TEROS 12 on replacement units. As already communicated to Richard: the two sensor families measure VWC and EC differently and are expected to read differently — TEROS 12 is being phased out in favor of TEROS One. Recommend the training session include a short "reading the TEROS One" segment so site teams stop comparing it 1:1 against TEROS 12 history.

Recommendations

P0
Restore the Palatka head-end. Physical check of the PoE switch / power circuit feeding gateway H2110001107 ("veg 5 nova core") and the site uplink. The simultaneous all-device drop means one fix likely brings all 14 F9 devices back. Batteries are full; no field hardware replacement expected.
P0
Raise the outage in today's 10:15 AM rollout meeting. 17 days of unnoticed downtime at the rollout's only live site is also a process gap: agree an alerting/escalation owner on both sides as part of the rollout plan (AROYA alert recipients + Verano site contact).
P1
Recover the Flower 5 repeater (H3400002704, offline since 2025-12-19): check PoE power/port; replace if it does not rejoin once powered.
P1
Create a harvest group for the F9 trial once data flows, so phases, targets and crop-steering context attach to the novacore-vs-bio comparison. Currently the facility has had no HG since Sept 2025.
P2
Add TEROS One expectations to team training (reads differently than TEROS 12 by design; 5–15% VWC offset is expected, not a defect) and review the wide per-position VWC spread in the bio zone after recovery.

Data quality & method