by Addium
Wirepas mesh & device health · HK Cassandra LLC · 2026-06-24

HK Cassandra LLC · Wirepas Mesh & Device Health

Live snapshot of every AROYA device at the facility — mesh parent linkages, child-slot saturation against the Wirepas 13-child rule, RSSI / link quality / battery health, and a prioritized remediation plan.

FacilityHK Cassandra LLC (4576) Pulled2026-06-24 14:33:29 SourceAROYA SPA /devices/?facility=4576

Executive summary

13-child slot rule why this is the load-bearing metric

Each parent node in the Wirepas mesh — gateway or relay — supports at most 13 DIRECT children. Grandchildren count against their immediate parent's slots, NOT against the grandparent's. Mid-layer relays can be saturated even when the gateway above them has plenty of headroom — so saturation has to be checked at every level of the topology, not just gateway-level. Once a parent crosses 13, additional devices either fail to join, get pushed to a worse parent at higher hop count, or thrash between slots — producing the long travel times, retries, and growing data gaps operators see.

Dash-2 dedup: two AROYA serials sharing the same base number where one has a -2 suffix (e.g. H4210005066 and H4210005066-2) are ONE radio with two sensor heads, not two mesh nodes. They fill one slot on their parent. This report deduplicates by base serial before counting — counts are per unique radio, not per raw serial.

Counts are per-immediate-parent: n_children(P) = unique base serials whose nextHop == P.

🟢 ≤10 children headroom · 🟠 11–12 near saturation · 🔴 13 at limit · 🔴🔴 >13 over-subscribed (orphaned devices & multi-hop spillover).

Mesh health KPIs

57
Unique radios
93 raw serials, −36 dash-2 pairs
55
Online
96.5% of radios
1/1
Gateways
online
0
Parents over 13
Wirepas 13-child limit
0
Parents 11–12
watch tier
0
Excess children
over 13-slot budget

Per-gateway summary

H2110001181
id 198079 · ggVersion 2 · online
🟢 7/13 · Headroom
7 hop-1 children
56 total routing
54/56 online
(no children resolved)

Mesh topology tree

Mesh topology — colored by parent's child-slot saturation🟢 ≤10🟠 11–12🔴 13🔴🔴 >13● GW · H2110001181sink: 7/13 hop-1 · 56 totalH3400003019 ·repeater·h?H3400003020 ·repeater·h?H3400003021 ·repeater·h?H3440014640 ·node·h?H3440014715 ·node·h?H3440014717 ·node·h?H3440014719 ·node·h?H3440014721 ·node·h?H3440014725 ·node·h?H3440014726 ·node·h?H3440014727 ·node·h?H4210004996 ·h421·h?H4210005100 ·h421·h?H4210005106 ·h421·h?H4210005141 ·h421·h?H4210005142 ·h421·h?H4210005143 ·h421·h?H4210005537 ·h421·h?H4210005539 ·h421·h?H8100001785 ·node·h?H8100001830 ·node·h?H3440014641 ·node·h?H3440014718 ·node·h?H3440014720 ·node·h?H3440014723 ·node·h?H3440014730 ·node·h?H4210004990 ·h421·h?H8100001821 ·node·h?H8100001832 ·node·h?H8100001837 ·node·h?H3440014728 ·node·h?H3440014729 ·node·h?H4210005001 ·h421·h?H4210005103 ·h421·h?H4210005140 ·h421·h?H8100001823 ·node·h?H3400002893 ·repeater·h?H3400003001 ·repeater·h?H4210005066 ·h421·h?H8100001831 ·node·h?H8100001833 ·node·h?H8100001838 ·node·h?H3440014716 ·node·h?H4210005097 ·h421·h?H4210005109 ·h421·h?H8100001834 ·node·h?H3440014722 ·node·h?H3440014724 ·node·h?H3440014731 ·node·h?H8100001788 ·node·h?… and 6 more
Each column is one gateway. Box color = sink's 13-child saturation. Edge color = child's RSSI tier. Devices listed in hop / signal order; capped at 50 per gateway for legibility.

Telemetry map logical layout — AROYA exposes no spatial coordinates for these devices

Telemetry map · logical mesh layoutAROYA does not expose physical device coordinates (lat/lng/what3words = null on all devices); positions inferred from mesh parent→child graph + hop depth.hop-1hop-2hop-3+H21100011817
Hub-and-spoke layout per gateway, hop depth shown as concentric contours, node color = RSSI tier (green ≥ −75 dBm · amber −75 to −85 · red < −85). Halo opacity shows weak-coverage envelope. AROYA SPA returns latitude / longitude / what3words as null on every device at this facility — open question for the customer is whether to instrument physical positions in the portal so the map can become true-to-floor.

Prescriptive remediation

P1 DEVICE Impact: Medium · Effort: Low

Restore 2 offline devices on gateway H2110001181

Finding
2 devices route through gateway H2110001181 but are currently offline / stale (>24h since last comm).
Action
Physical check: verify gateway is online and antenna seated; swap battery on Node devices; for non-Node PoE devices verify power + Ethernet. List: H4210005066 (h421), H4210005537 (h421)
Expected outcome
After swap / power-restore: 2 devices return to online state within 5–15 min of physical fix; fleet online-rate climbs by 4 pp.
Affected devices (2)
  • H4210005066 · h421 · room 18758
  • H4210005537 · h421 · room 18758
P2 ARCHITECTURE Impact: High · Effort: High

Add a second gateway for redundancy

Finding
Facility has only 1 gateway serving 56 devices. Single point of failure: a gateway outage cascades to fleet-wide blackout.
Action
Procure and deploy a second AROYA gateway in the geometric centroid of the device population, ideally serving a different VLAN / uplink for true diversity. Provision and wait for natural rebalance.
Expected outcome
Mesh self-rebalances within 12-24h — each gateway settles to ~28 devices, hop depth drops by 1, single-gateway outage no longer fleet-fatal.
P3 PROCESS Impact: Low · Effort: Low

Document as-built mesh topology in customer wiki

Finding
Topology is not currently captured in the customer wiki — future device adds are blind to the existing parent loading.
Action
Add a 'Mesh topology' section to the facility's wiki with the parent → child table from this report and the per-gateway loading. Update on every device add.
Expected outcome
New-device decisions become topology-aware; saturation regressions become rare and easily diagnosed.

Prioritized action plan

  1. 01 P1 Restore 2 offline devices on gateway H2110001181 Impact: Medium · Effort: Low
  2. 02 P2 Add a second gateway for redundancy Impact: High · Effort: High
  3. 03 P3 Document as-built mesh topology in customer wiki Impact: Low · Effort: Low

Per-room device tables

Room 1 (21 LED) · 4 devices · 4 online · 0 crit · 0 warn
SerialModelOnBat%RSSILinkQHopParentStateFlags
H3400002893 repeater ● 100 4 98 — 198078 OK healthy
H3440014716 (2-head) node ● 88 5 100 — 199651 OK healthy
H4210005103 h421 ● — 3 100 — 198078 OK healthy
H8100001785 (2-head) node ● 100 1 98 — 198078 OK healthy
Room 10(27 lights) · 4 devices · 4 online · 0 crit · 0 warn
SerialModelOnBat%RSSILinkQHopParentStateFlags
H3440014720 (2-head) node ● 100 2 100 — 199657 OK healthy
H3440014727 (2-head) node ● 100 1 76 — 199649 OK healthy
H4210005109 h421 ● — 5 100 — 199655 OK healthy
H8100001821 (2-head) node ● 100 2 100 — 205704 OK healthy
Room 11(31 lights) · 4 devices · 4 online · 0 crit · 0 warn
SerialModelOnBat%RSSILinkQHopParentStateFlags
H3440014717 (2-head) node ● 100 1 100 — 201009 OK healthy
H3440014722 (2-head) node ● 100 8 100 — 199737 OK healthy
H4210005140 h421 ● — 3 100 — 199657 OK healthy
H8100001837 (2-head) node ● 100 2 100 — 201005 OK healthy
Room 2 (99 LED) · 7 devices · 7 online · 0 crit · 0 warn
SerialModelOnBat%RSSILinkQHopParentStateFlags
H3400003021 repeater ● 100 1 96 — 199649 OK healthy
H3440014721 (2-head) node ● 100 1 95 — 198078 OK healthy
H3440014724 (2-head) node ● 100 8 100 — 200999 OK healthy
H4210004990 h421 ● — 2 100 — 201007 OK healthy
H4210004996 h421 ● — 1 71 — 198078 OK healthy
H4210005141 h421 ● — 1 100 — 201005 OK healthy
H8100001831 (2-head) node ● 100 4 100 — 201007 OK healthy
Room 3 (42 LED) · 5 devices · 5 online · 0 crit · 0 warn
SerialModelOnBat%RSSILinkQHopParentStateFlags
H3400003001 repeater ● 100 4 100 — 196774 OK healthy
H3440014726 (2-head) node ● 100 1 100 — 205704 OK healthy
H3440014729 (2-head) node ● 100 3 100 — 196774 OK healthy
H4210005539 h421 ● — 1 100 — 201007 OK healthy
H8100001823 (2-head) node ● 100 3 100 — 201005 OK healthy
Room 4(16 lights) · 3 devices · 3 online · 0 crit · 0 warn
SerialModelOnBat%RSSILinkQHopParentStateFlags
H3440014719 (2-head) node ● 100 1 83 — 198078 OK healthy
H4210005001 h421 ● — 3 100 — 200999 OK healthy
H8100001788 (2-head) node ● 100 8 100 — 201009 OK healthy
Room 5(24 lights) · 3 devices · 3 online · 0 crit · 0 warn
SerialModelOnBat%RSSILinkQHopParentStateFlags
H3440014640 (2-head) node ● 100 1 100 — 201009 OK healthy
H4210005143 h421 ● — 1 100 — 201009 OK healthy
H8100001834 (2-head) node ● 100 6 100 — 201001 OK healthy
Room 6(75 lights) · 6 devices · 4 online · 2 crit · 0 warn
SerialModelOnBat%RSSILinkQHopParentStateFlags
H4210005066 h421 ○ — 4 99 — 205708 CRITICAL offline
H4210005537 h421 ○ — 1 99 — 201001 CRITICAL offline
H3400003020 repeater ● 100 1 94 — 199649 OK healthy
H3440014715 (2-head) node ● 100 1 100 — 191514 OK healthy
H3440014731 (2-head) node ● 100 8 100 — 196774 OK healthy
H8100001832 (2-head) node ● 100 2 100 — 199534 OK healthy
Room 8(49 lights) · 6 devices · 6 online · 0 crit · 0 warn
SerialModelOnBat%RSSILinkQHopParentStateFlags
H3400003019 repeater ● 100 1 100 — 205704 OK healthy
H3440014725 (2-head) node ● 100 1 100 — 201007 OK healthy
H3440014728 (2-head) node ● 100 3 100 — 191514 OK healthy
H4210005097 h421 ● — 5 100 — 201003 OK healthy
H4210005142 h421 ● — 1 69 — 199649 INFO link-marginal
H8100001833 (2-head) node ● 100 4 100 — 201003 OK healthy
Room 9(27 lights) · 4 devices · 4 online · 0 crit · 0 warn
SerialModelOnBat%RSSILinkQHopParentStateFlags
H3440014723 (2-head) node ● 100 2 100 — 199657 OK healthy
H3440014730 (2-head) node ● 100 2 100 — 199655 OK healthy
H4210005106 h421 ● — 1 84 — 201007 OK healthy
H8100001838 (2-head) node ● 100 4 100 — 199649 OK healthy
veg room · 3 devices · 3 online · 0 crit · 0 warn
SerialModelOnBat%RSSILinkQHopParentStateFlags
H3440014641 (2-head) node ● 100 2 100 — 199649 OK healthy
H3440014718 (2-head) node ● 100 2 100 — 199655 OK healthy
H4210005100 h421 ● — 1 100 — 205704 OK healthy
Unassigned / infrastructure (8 devices) · 8 devices · 8 online · 0 crit · 0 warn
SerialModelOnBat%RSSILinkQHopParentStateFlags
H2110001181 gateway ● — — — — — OK healthy
H8100001814 (2-head) node ● 100 8 100 — 200285 OK healthy
H8100001819 (2-head) node ● 100 8 100 — 200285 OK healthy
H8100001827 (2-head) node ● 100 8 100 — 200285 OK healthy
H8100001830 (2-head) node ● 100 1 84 — 198078 OK healthy
H8100001835 (2-head) node ● 100 8 100 — 200285 OK healthy
H8100001836 (2-head) node ● 100 8 100 — 200285 OK healthy
H8100001839 (2-head) node ● 100 8 100 — 200285 OK healthy