Ubiquiti AmpliFi HD MeshPoint (AFi-P-HD): zero Ethernet ports, per the vendor’s own tables (#282) #1655

Merged
jaylouisw merged 1 commit from catalogue/1116-1125 into main 2026-11-16 11:33:59 +00:00
Owner

Fixes #282

What

devices/ubiquiti/afi-p-hd.json — the AmpliFi HD MeshPoint (AFi-P-HD, EU and UK), two radios and zero Ethernet ports, plus the matching research/incoming/ record and the regenerated registry doc (2,202 → 2,203 models; Ubiquiti 367 → 368; wireless 219 → 220).

The issue declared wireless, l2-forward; both are carried over, so no declared capability is dropped.

Why zero ports, not the one or two the resellers quote

#282 was left open because three pages disagreed — zero, one and two RJ45. Three Ubiquiti documents settle it, and they agree:

  1. AmpliFi datasheet (https://amplifi.com/docs/AmpliFi_Datasheet.pdf) — the labelled hardware diagram names Gigabit LAN Ports, WAN Port and Power Port on the Router and only Signal LEDs, Magnetic Connector, MeshPoint Base, Adjustable Antenna on the MeshPoint. The MeshPoint Specifications table has no Networking Interface row at all (Dimensions, Weight, TX power, Radios 2, MIMO 6, Speed 1750 Mbps, buttons, antenna, 802.11ac, power save, security, temperature, humidity, certifications, Max. Power Consumption 9W) while the Router table beside it does.
  2. Quick Start Guide, MODEL: AFi-P-HD (https://amplifi.com/docs/AFi-P-HD_QSG.pdf) — the MeshPoint Overview shows no jack, and installation is "Plug the MeshPoint into a power outlet", pairing over Bluetooth/Wi-Fi.
  3. Ubiquiti store page (https://eu.store.ui.com/eu/en/category/all-amplifi-mesh/products/amplifi-hd-meshpoint) — EU and UK variants of one SKU page, identical Hardware table, again no Networking Interface row.

The reseller "(1) WAN, (1) LAN" line for AFi-P-HD-UK is the AFi-R router row verbatim, which is how the family-sibling error got into the request in the first place. Per the evidence rule the vendor wins over the reseller.

Correction carried with it

devices/ubiquiti/afi-r.json notes used to say the MeshPoint's port count was simply "not stated" and that it therefore had no entry. That sentence is now false in a way that would invite the same guessing again, so it points at the new entry and names the zero-port reading.

Radio figures

802.11ac 13 Mbps-1300 Mbps (MCS0-MCS9, VHT 20/40/80) at 5 GHz and 802.11n 6.5 Mbps-450 Mbps (MCS0-MCS23, HT 20/40) at 2.4 GHz, from the datasheet's Supported Data Rates table; "Speed 1750 Mbps" is the two bands summed. 9 W max power consumption.

Gates

  • node scripts/syntax-check.js → 348 files, all OK
  • node scripts/audit-port-types.js → "No port contradicts its declared type."
  • node scripts/audit-devices.js → "No hard defects."
  • node test/hardware-invariants.test.js → 26 passed, 0 failed
  • node test/spec-vs-description.test.js → 3 passed, 0 failed
  • node test/request-queue.test.js → 23 passed; node test/topology-roundtrip.test.js → 35 passed
  • node scripts/check-control-bytes.js → clean
  • importer round trip via PF_INCOMING fixture dir: 1 spec seen, 1 added, 0 rejected, 0 collisions
Fixes #282 ## What `devices/ubiquiti/afi-p-hd.json` — the AmpliFi HD MeshPoint (AFi-P-HD, EU and UK), **two radios and zero Ethernet ports**, plus the matching `research/incoming/` record and the regenerated registry doc (2,202 → 2,203 models; Ubiquiti 367 → 368; wireless 219 → 220). The issue declared `wireless, l2-forward`; both are carried over, so no declared capability is dropped. ## Why zero ports, not the one or two the resellers quote #282 was left open because three pages disagreed — zero, one and two RJ45. Three Ubiquiti documents settle it, and they agree: 1. **AmpliFi datasheet** (https://amplifi.com/docs/AmpliFi_Datasheet.pdf) — the labelled hardware diagram names `Gigabit LAN Ports`, `WAN Port` and `Power Port` on the Router and only `Signal LEDs`, `Magnetic Connector`, `MeshPoint Base`, `Adjustable Antenna` on the MeshPoint. The MeshPoint Specifications table has **no Networking Interface row at all** (Dimensions, Weight, TX power, Radios 2, MIMO 6, Speed 1750 Mbps, buttons, antenna, 802.11ac, power save, security, temperature, humidity, certifications, Max. Power Consumption 9W) while the Router table beside it does. 2. **Quick Start Guide**, MODEL: AFi-P-HD (https://amplifi.com/docs/AFi-P-HD_QSG.pdf) — the MeshPoint Overview shows no jack, and installation is "Plug the MeshPoint into a power outlet", pairing over Bluetooth/Wi-Fi. 3. **Ubiquiti store page** (https://eu.store.ui.com/eu/en/category/all-amplifi-mesh/products/amplifi-hd-meshpoint) — EU and UK variants of one SKU page, identical Hardware table, again no Networking Interface row. The reseller "(1) WAN, (1) LAN" line for AFi-P-HD-UK is the **AFi-R router row verbatim**, which is how the family-sibling error got into the request in the first place. Per the evidence rule the vendor wins over the reseller. ## Correction carried with it `devices/ubiquiti/afi-r.json` notes used to say the MeshPoint's port count was simply "not stated" and that it therefore had no entry. That sentence is now false in a way that would invite the same guessing again, so it points at the new entry and names the zero-port reading. ## Radio figures 802.11ac 13 Mbps-1300 Mbps (MCS0-MCS9, VHT 20/40/80) at 5 GHz and 802.11n 6.5 Mbps-450 Mbps (MCS0-MCS23, HT 20/40) at 2.4 GHz, from the datasheet's Supported Data Rates table; "Speed 1750 Mbps" is the two bands summed. 9 W max power consumption. ## Gates - `node scripts/syntax-check.js` → 348 files, all OK - `node scripts/audit-port-types.js` → "No port contradicts its declared type." - `node scripts/audit-devices.js` → "No hard defects." - `node test/hardware-invariants.test.js` → 26 passed, 0 failed - `node test/spec-vs-description.test.js` → 3 passed, 0 failed - `node test/request-queue.test.js` → 23 passed; `node test/topology-roundtrip.test.js` → 35 passed - `node scripts/check-control-bytes.js` → clean - importer round trip via `PF_INCOMING` fixture dir: 1 spec seen, 1 added, 0 rejected, 0 collisions
Ubiquiti AmpliFi HD MeshPoint (AFi-P-HD): zero Ethernet ports, per the vendor's own tables (#282)
All checks were successful
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 17s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 18) (pull_request) Successful in 1m33s
CI / Test (Node 20) (pull_request) Successful in 1m33s
CI / Test (Node 22) (pull_request) Successful in 1m42s
f469bcd75f
jaylouisw scheduled this pull request to auto merge when all checks succeed 2026-11-16 11:33:50 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!1655
No description provided.