[Device]: Ubiquiti AmpliFi HD Mesh Point UK Version AFi-P-HD #282
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#282
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Vendor
Ubiquiti
Exact model name
Ubiquiti AmpliFi HD Mesh Point UK Version AFi-P-HD
Category
Wireless AP
Ports and interfaces
PoE budget (watts)
None
Datasheet or product page URL
https://www.4gon.co.uk/ubiquiti-amplifi-hd-mesh-point-p-7173.html
What do you want to model with it?
A Wi-Fi access point in a wireless lab.
Capabilities
wireless, l2-forward
Before submitting
The MeshPoint cannot be specified from the source yet. Ubiquiti's AmpliFi datasheet states the port row once for the family and it belongs to the AFi-R router, now catalogued at
devices/ubiquiti/afi-r.json. The MeshPoint's own port count is not in the document, so it gets no entry rather than a guessed one.Not closing this one yet, but the blocker is now sharper than "the page 422s" - the sources contradict each other, which is a different problem.
What the public pages say about AFi-P-HD (Amplifi HD MeshPoint):
Networking Interface: Wi-Fi/Gigabit Ethernet (1) WAN, (1) LANforAFi-P-HD-UK;So the three candidate answers are zero, one and two Ethernet ports. The device is a wall-plug mesh node, so zero is the plausible reading and the "(1) WAN, (1) LAN" line looks copied from a different Amplifi product - but "looks copied" is not a source, and this is exactly the case where a guessed port list becomes a lab that refuses to cable.
What would close it: Ubiquiti's own AFi-P-HD datasheet (dl.ui.com) or a photo of the unit's connector end. I would rather leave this open than model a wall-plug node with Ethernet ports it may not have.
Closing: already fixed on main — this issue's fix landed in
a9034db1(PR #1655, 2026-11-16 11:33 UTC) but that PR's body did not carryFixes #282, so Forgejo never auto-closed it. Nothing to add; the spec isdevices/ubiquiti/afi-p-hd.json.What it records: AFi-P-HD (EU) / AFi-P-HD-UK — zero Ethernet ports, zero PoE, no console, two radios only:
radio-2g450 Mbps — datasheet Supported Data Rates: 802.11n 6.5 Mbps to 450 Mbps (MCS0–MCS23, HT 20/40)radio-5g1300 Mbps — 802.11ac 13 Mbps to 1300 Mbps (MCS0–MCS9, VHT 20/40/80); "Speed 1750 Mbps" is the sum of the two bandswireless,l2-forward(multi-hop mesh node); max power consumption 9 WRe-verified today against the vendor's own material (text layer, not reseller tables):
https://amplifi.com/docs/AmpliFi_Datasheet.pdf— the labelled hardware diagrams on p.2 name four callouts for the MeshPoint (Adjustable Antenna, Signal LEDs, Magnetic Connector, MeshPoint Base) while the Router diagram names "Gigabit LAN Ports", "WAN Port", "Power Port"; the MeshPoint Specifications table (p.9) has no Networking Interface row at all, whereas the Router table on the facing page gives "Wi-Fi/Gigabit Ethernet (1) WAN, (4) LAN".https://amplifi.com/docs/AFi-P-HD_QSG.pdf(MODEL: AFi-P-HD) — "MeshPoint Overview" lists only the same four items; install step 1 is "Plug the MeshPoint into a power outlet" and pairing is by Bluetooth + Wi-Fi.The three-way contradiction in the 2026-11-10 comment (zero / one / two ports) was between reseller tables that copy the AFi-R row; the datasheet's own MeshPoint table and diagram, plus the QSG, agree on none. The vendor wins, so nothing is modelled.
Gates on the checkout that carries the spec (
origin/main@0074b73d, which containsa9034db1):node scripts/syntax-check.js→ 348 files, all OK;node scripts/audit-port-types.js→ "No port contradicts its declared type."