Device & Network Health Audit

Cannapproach — CCMS

Wirepas mesh connectivity audit · facility 4549 · live snapshot of every device's online state, signal, link quality, and battery
FacilityCannapproach — CCMS (4549) Rooms monitored20 (8 with devices) Devices46 (parents + sensors) Generated2026-06-24 03:42 UTC WindowLive snapshot (per-device last seen shown inline) Prepared byCian Sullivan
Verdict Summary KPIs Mesh topology Rooms Devices Actions Method

Verdict

Mesh backbone
2 sink(s) down
3/5 gateways anchoring online devices
Rooms down
3
Joe's Demo, Fiacre FR2, Fiacre FR3
Rooms degraded
5
Fiacre FR1, Fiacre FR4, Fiacre FR5, Fiacre FR6, Fiacre FR7
Rooms healthy
0
none
FINDINGSome rooms have devices in a silent or partial-online state.
Down: Joe's Demo, Fiacre FR2, Fiacre FR3
Partial online:
Marginal:
Sensors flagged as silent have not communicated in the last 4+ hours and need to re-attach to a sink (no firmware change involved). See the Devices table for serials, last-seen ages, and the anchored gateway each one is hopping toward.

Gateway changeover (2026-06-22) · 24h follow-up

The Fiacre flower cluster's two old gateways were swapped out on 2026-06-22 for two new units. Yesterday's audit captured a partially-converged mesh with FR6 down and FR7 marginal. Today's snapshot shows that FR6 and FR7 have both recovered cleanly — but the situation in FR2 and FR3 has reversed: those two rooms now show silent radios anchored to a new gateway (numeric id 222789) that wasn't in yesterday's set, and Joe's Demo went silent late on 06-23.

Gateways yesterday vs. today

Gateway2026-06-23 03:39 UTC state2026-06-24 03:42 UTC stateNotes
H2110001266 (Joe's Demo)ONLINEONLINE but anchoring 0 online devicesJoe's Demo went silent ~14:11 on 06-23; the gateway is still up but its nodes need a reset.
H2110001287 (FR4/FR5)ONLINEONLINEFR4/FR5 still anchored here, healthy. The split-route condition on FR6 has resolved.
H2200001038 (FR6/FR7 NEW)ONLINE (FR7 + 1 FR6 radio)ONLINEFR6 and FR7 now both fully anchored here. The split-route problem resolved on its own — no on-site reset was needed.
H2200001039 (FR1 NEW)ONLINE (FR1–FR4)ONLINE (FR1 + FR4 only)FR2 and FR3 have migrated to a new anchor id (222789) and are now silent there.
gw#222789 (FR2/FR3 NEW anchor)not present in prior auditNO ONLINE DEVICESThis gateway id appeared today as the anchor for FR2/FR3, but its nodes haven't reported since 06-23 13:42 (FR2) / 00:28 (FR3). The gateway is the suspect.
H2100005595 (old)OFFLINEOFFLINEOLD — went offline 06-22 14:43 during changeover. Should be marked retired in AROYA if intended.
H2110001269 (old)OFFLINEOFFLINEOLD — went offline 06-22 14:40 during changeover. Same as above.

What changed since yesterday

FR6 / FR7 healedThe split-route problem on FR6 self-resolved.
FR6 today shows 3/3 devices online, all anchored cleanly to H2200001038 via repeater H4210005930. FR7 is also healthy (RSSI ≥6, link 100%). The "two-rooms-closest-to-the-new-gateway-have-the-worst-signal" symptom from yesterday has gone away — the mesh re-converged on its own as predicted, no on-site reset required.
FR2 / FR3 DOWNNew silent-rooms condition: FR2 went silent 06-23 13:42, FR3 silent 06-24 00:28.
FR2 (2 nodes) and FR3 (2 nodes) are both anchored to a gateway id (222789) that wasn't in the previous audit. Their last data packet was hours ago — FR2 ~14 h, FR3 ~3 h — well past the 4 h P0 threshold for FR2.
FR3 was also showing a degraded signal-quality reading (rssi 1/8, link 15%) before it stopped reporting, which is a different pattern from the clean drop FR6 had during the original changeover.
This is the room cluster that needs eyes on it today: confirm gateway 222789 is the gateway you intended to use, that it has power and an internet path, and that the FR2/FR3 nodes can be reset / power-cycled to re-attach.
Joe's Demo silentJoe's Demo went silent at 14:11 on 06-23 — all 4 devices offline.
The Joe's Demo gateway (H2110001266) is still ONLINE in AROYA's gateway table but it is anchoring zero online devices. Most likely the gateway needs to be checked at-site, or one of the room nodes was unplugged. The fix is the same as FR2/FR3: confirm the gateway path, then power-cycle the room nodes.

Carrying forward from the prior post-mortem

The original three hypotheses from yesterday — stale Wirepas routes, child-slot contention near the new gateway, and antenna geometry — still apply to mesh churn during gateway swaps. FR6/FR7 played out exactly as the route-reconvergence story predicted (they resolved without intervention as Wirepas re-costed paths over the day). The same fix-list applies to today's silent rooms: reset the affected nodes first, verify the anchor gateway is healthy, and only escalate to slot contention or antenna geometry if a clean reset doesn't hold.

Summary KPIs

Total devices
46
15 OK · 0 P1 · 15 P0 · 16 offline
P0 critical
15
device-level critical flags
P1 marginal
0
battery/signal/link/stale warnings
OK
15
no flags
Offline
16
last-seen > 4h or online=false
Gateways online
3/5
anchoring at least one online device
Avg link quality
83%
across all reporting nodes
Median battery
100%
battery-bearing devices only

Mesh topology

Devices are anchored to a gateway via their gateway field. The numeric IDs map to physical gateway serials below.

H2200001039 ANCHORING

NEW — FR1 sink (serves FR1) · numeric id 192178 · 3/3 devices online
  • Fiacre FR1 3/3 online
    • 🟢 OK H3440013462 · node · rssi 7/8 · link 100%
    • 🟢 OK H3440013462-2 · node · rssi 7/8 · link 100%
    • 🔴 P0 H4210006646 · h421 · rssi 1/8 · link 59%

H2110001266 NO ONLINE DEVICES

Existing — Joe's Demo sink · numeric id 202015 · 0/4 devices online
  • Joe's Demo 0/4 online
    • ⚫ OFFLINE H3310009922 · node · rssi 6/8 · link 100%
    • ⚫ OFFLINE H5200001002 · h520 · rssi 6/8 · link 100%
    • ⚫ OFFLINE H8200001003 · node · rssi 6/8 · link 100%
    • ⚫ OFFLINE H8200001003-2 · node · rssi 6/8 · link 100%

H2110001287 ANCHORING

Existing — FR4/FR5 sink · numeric id 202052 · 6/6 devices online
  • Fiacre FR4 3/3 online
    • 🟢 OK H3440014929 · node · rssi 7/8 · link 100%
    • 🟢 OK H3440014929-2 · node · rssi 7/8 · link 100%
    • 🔴 P0 H4210004507 · h421 · rssi 1/8 · link 52%
  • Fiacre FR5 3/3 online
    • 🟢 OK H3440014928 · node · rssi 5/8 · link 100%
    • 🟢 OK H3440014928-2 · node · rssi 5/8 · link 100%
    • 🔴 P0 H4210005146 · h421 · rssi 1/8 · link 84%

gw#222789 NO ONLINE DEVICES

FR2/FR3 anchor — gateway state unverified (rooms offline) · numeric id 222789 · 0/4 devices online
  • Fiacre FR2 0/2 online
    • ⚫ OFFLINE H3440015299 · node · rssi 5/8 · link 100%
    • ⚫ OFFLINE H3440015299-2 · node · rssi 5/8 · link 100%
  • Fiacre FR3 0/2 online
    • ⚫ OFFLINE H3440015383 · node · rssi 1/8 · link 15%
    • ⚫ OFFLINE H3440015383-2 · node · rssi 1/8 · link 15%

H2200001038 ANCHORING

NEW — FR6/FR7 sink · numeric id 222833 · 6/6 devices online
  • Fiacre FR6 3/3 online
    • 🟢 OK H3440014948 · node · rssi 5/8 · link 100%
    • 🟢 OK H3440014948-2 · node · rssi 5/8 · link 100%
    • 🔴 P0 H4210005930 · h421 · rssi 1/8 · link 49%
  • Fiacre FR7 3/3 online
    • 🟢 OK H3440014947 · node · rssi 6/8 · link 100%
    • 🟢 OK H3440014947-2 · node · rssi 6/8 · link 100%
    • 🔴 P0 H4210005159 · h421 · rssi 1/8 · link 68%

Rooms

Fiacre cluster (FR1–FR7 + Veg)

RoomStateOnlineAvg RSSIAvg linkAnchored gateway(s)
Fiacre FR1CRITICAL3/35.0/886%H2200001039
Fiacre FR2DOWN0/25.0/8100%gw#222789
Fiacre FR3DOWN0/21.0/815%gw#222789
Fiacre FR4CRITICAL3/35.0/884%H2110001287
Fiacre FR5CRITICAL3/33.7/895%H2110001287
Fiacre FR6CRITICAL3/33.7/883%H2200001038
Fiacre FR7CRITICAL3/34.3/889%H2200001038
Fiacre Vegempty

Joe's Demo + R&D + Powrhouse

RoomStateOnlineAvg RSSIAvg linkAnchored gateway(s)
R&Dempty
Powrhouseempty
Joe's DemoDOWN0/46.0/8100%H2110001266

Room 1–5 + CCMS + qa + Michael 3 Light

RoomStateOnlineAvg RSSIAvg linkAnchored gateway(s)
Room 1empty
Room 2empty
Room 3empty
Room 5empty
CCMSempty
qa 1empty
qa 2empty
qa 3empty
Michael 3 Lightempty

Devices

Every device including paired sensors. Sensors that share a puck show their parent's nextHop. RSSI=0 with linkQuality=— is an AROYA-side artifact for paired ter15 sensors, not a real signal issue (the parent puck carries the radio).

RoomSerialModelStatusBatteryRSSILinkHopAnchored gatewayLast seen
Joe's DemoH3310009922node⚫ OFFLINE93%6/8100%1H211000126613.5 h ago
↳ sensorB015824sq-521⚫ OFFLINE93%6/8100%via parent13.5 h ago
Joe's DemoH5200001002h520⚫ OFFLINE100%6/8100%1H211000126613.5 h ago
↳ sensorH5200001002Sflow_ph⚫ OFFLINE100%6/8100%via parent13.5 h ago
Joe's DemoH8200001003node⚫ OFFLINE100%6/8100%1H211000126613.5 h ago
↳ sensorH8200001003-ter15ter15⚫ OFFLINE100%6/8100%via parent13.5 h ago
Joe's DemoH8200001003-2node⚫ OFFLINE100%6/8100%1H211000126613.5 h ago
↳ sensorH8200001003-2-ter15ter15⚫ OFFLINE100%0/8via parent13.5 h ago
Fiacre FR1H3440013462node🟢 OK100%7/8100%2H220000103916 min ago
↳ sensorH3440013462-ter15ter15🟢 OK100%7/8100%via parent16 min ago
Fiacre FR1H3440013462-2node🟢 OK100%7/8100%2H220000103916 min ago
↳ sensorH3440013462-2-ter15ter15🔴 P0100%0/8via parent16 min ago
Fiacre FR1H4210006646h421🔴 P01/859%1H220000103915 min ago
↳ sensorH4210006646See894🔴 P01/859%via parent15 min ago
Fiacre FR2H3440015299node⚫ OFFLINE100%5/8100%2gw#22278914.0 h ago
↳ sensorH3440015299-ter15ter15⚫ OFFLINE100%5/8100%via parent14.0 h ago
Fiacre FR2H3440015299-2node⚫ OFFLINE100%5/8100%2gw#22278914.0 h ago
↳ sensorH3440015299-2-ter15ter15⚫ OFFLINE100%0/8via parent14.0 h ago
Fiacre FR3H3440015383node⚫ OFFLINE100%1/815%1gw#2227893.2 h ago
↳ sensorH3440015383-ter15ter15⚫ OFFLINE100%1/815%via parent3.2 h ago
Fiacre FR3H3440015383-2node⚫ OFFLINE100%1/815%1gw#2227893.2 h ago
↳ sensorH3440015383-2-ter15ter15⚫ OFFLINE100%0/8via parent3.2 h ago
Fiacre FR4H3440014929node🟢 OK100%7/8100%2H211000128713 min ago
↳ sensorH3440014929-ter15ter15🟢 OK100%7/8100%via parent13 min ago
Fiacre FR4H3440014929-2node🟢 OK100%7/8100%2H211000128713 min ago
↳ sensorH3440014929-2-ter15ter15🔴 P0100%0/8via parent13 min ago
Fiacre FR4H4210004507h421🔴 P01/852%1H211000128713 min ago
↳ sensorH4210004507See894🔴 P01/852%via parent13 min ago
Fiacre FR5H3440014928node🟢 OK100%5/8100%2H211000128712 min ago
↳ sensorH3440014928-ter15ter15🟢 OK100%5/8100%via parent15 min ago
Fiacre FR5H3440014928-2node🟢 OK100%5/8100%2H211000128715 min ago
↳ sensorH3440014928-2-ter15ter15🔴 P0100%0/8via parent15 min ago
Fiacre FR5H4210005146h421🔴 P01/884%1H211000128713 min ago
↳ sensorH4210005146See894🔴 P01/884%via parent12 min ago
Fiacre FR6H3440014948node🟢 OK100%5/8100%2H220000103812 min ago
↳ sensorH3440014948-ter15ter15🟢 OK100%5/8100%via parent12 min ago
Fiacre FR6H3440014948-2node🟢 OK100%5/8100%2H220000103812 min ago
↳ sensorH3440014948-2-ter15ter15🔴 P0100%0/8via parent12 min ago
Fiacre FR6H4210005930h421🔴 P01/849%1H220000103812 min ago
↳ sensorH4210005930See894🔴 P01/849%via parent13 min ago
Fiacre FR7H3440014947node🟢 OK100%6/8100%2H220000103814 min ago
↳ sensorH3440014947-ter15ter15🟢 OK100%6/8100%via parent14 min ago
Fiacre FR7H3440014947-2node🟢 OK100%6/8100%2H220000103814 min ago
↳ sensorH3440014947-2-ter15ter15🔴 P0100%0/8via parent14 min ago
Fiacre FR7H4210005159h421🔴 P01/868%1H220000103811 min ago
↳ sensorH4210005159See894🔴 P01/868%via parent11 min ago

Actions — prioritized

PriorityActionWhy / expected resultAffected devices
P0Power-cycle / re-seat the Joe's Demo nodesForces the nodes to drop stale routes and re-attach to the strongest current sink. Expect them back online within a few minutes.H3310009922, H5200001002, H8200001003, H8200001003-2
P0Power-cycle / re-seat the Fiacre FR2 nodesForces the nodes to drop stale routes and re-attach to the strongest current sink. Expect them back online within a few minutes.H3440015299, H3440015299-2
P0Power-cycle / re-seat the Fiacre FR3 nodesForces the nodes to drop stale routes and re-attach to the strongest current sink. Expect them back online within a few minutes.H3440015383, H3440015383-2
P3Re-audit in 24–48h after any resetsConfirm offline devices return and signal stays strong; check whether the partial-online rooms self-heal.

Method & data quality

ItemDetail
Live device snapshotAROYA SPA /rooms/<id>/v2/ per room — pulled strictly sequentially on 2026-06-24 03:27–03:42 UTC. 20 rooms; 46 devices total (parents + paired sensors).
Thresholds appliedbattery <15%=P0, <30%=P1; rssi ≤1=P0, ≤3=P1 (on 0–8 bar scale); linkQuality <40%=P0, <60%=P1; lastCommunication >4h=P0, >1h=P1. Paired ter15 sensors that report rssi=0 with linkQuality=null are AROYA-side artifacts (parent puck carries the radio) and not flagged.
Gateway serial mappingNumeric gateway IDs map to physical serials as listed in the Mesh topology section. Some IDs (e.g. gw# rendered as plain numeric) remain unresolved where the SPA tab returned no gateway record this session.
Hop countInferred by chasing each device's nextHop until a sink/gateway id is reached or 6 hops elapsed. "?" = chain didn't resolve.
Prior audit referenceYesterday's post-mortem (2026-06-23 03:39 UTC) is mirrored under "Gateway changeover" above. The two new gateway ids that surfaced today (222789, 222833) were correlated to the existing fleet via the gateway field on each device — the prior audit's gateway table lists their physical serials (H2200001038 / H2200001039) for the ids whose serials we could resolve.
Unresolved IDsgw#222789 / gw#222788 — these surfaced today as the new anchor for FR2/FR3 but the SPA tab returned no gateway record for them this session, so we mark them as gw#-prefixed numeric IDs rather than guessing a physical serial.
Rooms with no devicesThe legacy Room 1/2/3/5, R&D, and Powrhouse rooms are archived shells with no AROYA hardware (legacy IDs preserved for historical chart links). CCMS / qa 1–3 / Michael 3 Light / Fiacre Veg are active rooms in the AROYA app but have no devices currently deployed in them.

Connectivity terms used as AROYA does: a device that has not communicated in >4h has gone silent and needs to re-attach to a sink. It is not damaged and rejoins on reset. No firmware change is involved in any of the issues flagged here.