·Re-Provisioning Evaluation

Grow United Farms · Seminole, OK

Acquired hardware audit — assets purchased from a closed grow (originally tagged TERPZ on Salesforce; portal verification shows current ownership in active orgs — see Provenance Verification below), to be installed at a new consulting site · Prepared 2026-06-11 · For Khoa Nguyen
Customer / contact
Khoa (Trang Nguyen)
trangn1102@yahoo.com · Case 00039767 (KOAH)
Destination facility
Grow United Farms
35720 EW 1140 · Seminole, OK 74868 · NEW (not yet in AROYA)
Source account(s)
Multi-org (verification pending)
Mad Industries: Kaniboss + Diamond Dust Farms — see Provenance Verification
Asset count
18 sensor devices + 1 gateway
Per Khoa's handwritten list (IMG_8883.jpeg)
Report date
2026-06-11
Generated by Cian Sullivan
Recommended scenario
B — new AROYA facility
Different business entity from TERPZ; clean slate
Firmware family
New-gen (WP5-native)
H411 / H342 / H180 prefixes; no WP4→WP5 push needed
Provisioning effort
~2–3 hours remote
After Khoa confirms gateway + access
Loading shared state…

Summary

Headline: the hardware Khoa purchased is current-generation AROYA gear (H411 repeaters, H342 substrate nodes, plus 2 H180-prefix repeaters and an included gateway). Per AROYA's firmware ground rules, devices in these prefix ranges are already on WP5 firmware — there is no WP4→WP5 OTAP push to schedule before they can be used. The work is purely provisioning: moving them from the source AROYA org(s) into a new Grow United Farms facility, then re-deploying them at the Seminole site. De-provisioning is currently blocked pending provenance reconciliation — see the Provenance Verification section below.

Recommended path: Scenario B — create a fresh Grow United Farms organisation + facility in AROYA, re-provision each device into it, and bring the mesh up at Seminole. We do not transfer Khoa into any of the source orgs (different businesses; no historical-data continuity worth preserving). Action gate first: reconcile which closed grow Khoa actually purchased from (the Salesforce 'TERPZ' label appears to have been mis-tagged) and get AROYA Support sign-off on multi-org de-provisioning rights.

Open question: the 2 H180-prefix repeaters are not in any facility currently visible in our scope, so I cannot confirm their current firmware state from telemetry. The handwritten serial list also has 4 substrate-node digits where Khoa's handwriting is borderline — Cian to spot-check both before kicking off.

16
High confidence — WP5-native, ready to re-provision
2
Verify in app — H180 firmware state unknown
1
Gateway — included with bundle (serial TBD)
4
Substrate-node serials with handwriting uncertainty

⚠️ Provenance Verification

Three of Khoa's serials sampled against the AROYA portal show current ownership in active orgs, not the closed-grow TERPZ account originally referenced on Salesforce case 00039767.

SerialCurrent AROYA org (portal-verified 2026-06-11)
H4110006178Kanniboss / Mad Industries
H4110006144Kanniboss / Mad Industries
H3420001786Diamond Dust Farms

Context. TERPZ does exist in AROYA (92 devices) but holds older hardware (H210 / SINKH2100 / H1100 serial prefixes) — a different hardware generation entirely from the H411 / H342 / H180 family Khoa listed. The "TERPZ" label attached to Salesforce case 00039767 appears to have been mis-tagged; the real source orgs look to be Mad Industries (Kaniboss) and Diamond Dust Farms, both currently outside Cian's SPA scope-1272.

Three reconciliation possibilities to clear with Khoa BEFORE de-provisioning:

  1. The source orgs (Mad Industries, Diamond Dust Farms) are aware they sold the hardware and have simply not de-provisioned on their side yet.
  2. The "closed grow" Khoa referenced is a sub-tenant / leased operation under one of those parent orgs.
  3. Khoa is operating from incomplete information about device provenance (i.e. she bought through a broker and the seller orgs may not know).

Action gate — de-provisioning is BLOCKED pending: (a) Khoa-side provenance clarification, (b) AROYA Support sign-off on multi-org de-provisioning rights, (c) full per-serial portal verification of all 19 devices (3 of 19 verified so far — sampled provenance).

Device inventory — per-device classification

Serial (AROYA H-prefix)FamilyFirmware familySource org (sampled / inferred)Transferability tierActionPre-flight OK?Notes

Family map (how we classify by H-prefix)

Scenario A vs Scenario B — recommended path

Scenario A — re-use the existing TERPZ AROYA account

NOT recommended

Grow United Farms is a different business entity from any of the source orgs (Mad Industries: Kaniboss, Diamond Dust Farms — provenance verification pending). Khoa is consulting for a new operator, not buying any of the source businesses. There is no historical-data continuity worth preserving (different cultivars, different operators, different room layout in Seminole). And the credentials/admin on the source AROYA orgs sit with those businesses, not with Khoa or Grow United Farms.

Operationally there is no advantage to inheriting the closed-grow's account, room IDs, alert thresholds, or run history.

Scenario B — new Grow United Farms facility in AROYA

RECOMMENDED

Create a new organisation + facility owned by Grow United Farms (or by Khoa's existing "Khoa Nguyen" org as a 2nd facility, if Khoa wants to keep both Planet 405 and Grow United Farms under one login — Khoa's call).

Each device is de-provisioned from its source org by AROYA Support (Cian to drive — multi-org coordination required), then re-provisioned into Grow United Farms. Rooms get set up fresh against the actual Seminole layout. The included gateway boots into the new facility's network on first power-up.

→ Going with Scenario B. Confirmation needed from Khoa: separate Grow United Farms org, or 2nd facility under her existing Khoa Nguyen org.

Scenario B workflow — step by step

  1. Pre-flight confirmations with Khoa (the checklist below) — separate org vs 2nd facility under Khoa Nguyen; gateway serial; physical access window; spot-check of 4 ambiguous substrate serials.
  2. Multi-org de-provisioning coordination. Devices live in at least 2 active AROYA orgs (Mad Industries: Kaniboss, Diamond Dust Farms — full per-serial audit pending). For each source org: (a) AROYA Support sign-off that the org's admin has authorized release; (b) Cian / AROYA Support de-provisions; (c) chain-of-custody note attached to each device for Khoa's records. Blocked until Provenance Verification section closes.
  3. Create Grow United Farms in the AROYA portal. Org → facility (Seminole, OK address). Either Khoa creates it under a new owner login, or Cian creates it under Khoa's existing login depending on (1).
  4. Re-provision the 19 assets into Grow United Farms. Bulk re-assign by serial. Devices appear in the new facility's inventory; rooms are still empty at this point.
  5. Khoa powers up the gateway at Seminole. The bundled gateway claims the LAN, talks to AROYA, the H411 repeaters and H342 nodes onboard onto the new mesh as they're physically deployed.
  6. Set up rooms + assign devices. Rooms get created in the new facility per Khoa's Seminole layout; each H342 substrate node is dragged to its room/zone; H411 repeaters get placed where the mesh-map RSSI says.
  7. Smoke-test for 48 h. Watch the device list — every device online, battery + signal in spec, telemetry flowing into rooms. If anything's silent past 48 h, that's the time to act (replace battery, reseat, RMA — not at install time).

Per-device action notes

Pre-flight checklist (interactive — syncs across devices)

Confirmation neededNotes (live)

AROYA-side access requirements

Open items + caveats

Transcription confidence on 4 substrate serials. Khoa's handwritten list (IMG_8883.jpeg) has four H342 substrate-node serials where the last 1–2 digits are borderline — could read as e.g. H3420001288 or H3420001281. These don't block the re-provisioning workflow (the boxes have the serials printed) but they're worth a sanity-check before the AROYA Support ticket goes in. Cian to verify against the physical units or a clearer photo.
H180 firmware state cannot be telemetry-verified. The 2 H180-prefix repeaters aren't currently in any AROYA facility in Cian's scope. The expected behaviour is they're already on WP5 (consistent with their physical generation), but the only way to confirm is to bring them online on the bundled gateway and observe. Build the test into step 5 of the workflow above.
No WP4→WP5 push to schedule. Unlike the legacy fleets (H110/H111/H311 prefixes at e.g. Zugatti 14th Street, Granite Leaf), this hardware is already shipping with WP5. The gateway updates to WP5 and the mesh follows the gateway — no separate firmware rollout, no online/battery/signal gates to coordinate before go-live.

Sources

AROYA · Re-Provisioning evaluation for Grow United Farms · 2026-06-11 · Generated by Cian Sullivan · Status edits, pre-flight checks, and notes sync across every device that opens this link (shared store), with a local cache when offline.