devices(ubiquiti): the LTE Backup Pro's 15.4 W passthrough port was dead (refs #130) #2150
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!2150
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1119-1222"
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?
refs #130 (records the catalogue defect found underneath this request; does not close it)
#130 asks for a Dream Wall Pro and has been blocked on every Ubiquiti surface for four passes; this pass did not re-walk them. It spent the increment on the lane the request's own lab names - NAT, DHCP, VPN, cellular WAN - because the two rows a requester is handed for cellular WAN are the LTE modems, and the 11:0x pass fixed only the UMR.
devices/ubiquiti/u-lte-backup-pro.jsondeclaredpoe-pse, and its description promised a passthrough port, buteth1carried nopoeOutand the row had nopoeblock at all.engine/device.jstherefore fell through to the model-name parser, which found no wattage in "U-LTE-Backup Pro" and set the budget to 0, andengine/simulator.jsopens its allocator withif (!dev.poeBudget) continue;- so the box was skipped, not reported unknown. The documented port could power nothing andshow power inlinesaid nothing about why, the same defect class asumr.jsonin #2128.Measured before/after (U6-Lite cabled to
eth1):source: name)source: research)Sources (all Ubiquiti-hosted, read 2026-11-19)
https://techspecs.ui.com/unifi/integrations/u-lte-backup-pro- 200, 624,978 B: "Networking interface (2) GbE RJ45 ports"; "PoE interface (1) PoE in (PoE output not used) / (1) PoE passthrough output (Requires a PoE+ switch)"; "Max. power consumption Excluding PoE passthrough output: 8.5W"; "Max. PoE passthrough wattage per port 15.4W*" with "*Requires a PoE+ switch"; "Supported voltage range 44-57V DC".https://dl.ui.com/ds/u-lte-backup-pro_ds.pdf- 200,application/pdf, 329,546 B, 2 pp, text layer: the same census, including "15.4W*" and the PoE+ footnote, plus "Throughput speeds Download 150 Mbps / Upload 50 Mbps".https://store.ui.com/us/en/products/u-lte-backup-pro- 200, 402,625 B (landed on its collection URL): repeats the spec table, and its diagram labels the output "PoE+ GbE Port (Passthrough)"; the power-method row reads "PoE+ (Pairs 1, 2+; 3, 6- | Pairs 4, 5+; 7, 8-)" - four-pair Type 2 on the input.What changed, and the judgement calls
eth1:poeOut: true,poeOutClass: "PoE+"- the vendor labels the port PoE+ - whilepoe.budgetWstays at the vendor's own 15.4 W per-port cap. The two are both vendor statements; the note records that the class label is the store's and the cap is the datasheet's.capabilities:802.3atadded, because the 8.5 W own draw plus 15.4 W passed through cannot come from an 802.3af source - which is exactly what "*Requires a PoE+ switch" means.wwan0speed 100M -> 150M: the old note said the datasheet "names the category rather than a measured rate", but it prints Download 150 Mbps / Upload 50 Mbps. 150M is also whatumr.jsonand the other Cat 4 rows use.eth0sinks andeth1sources on the existing catalogue convention (same asumr.json,zyxel/gs1900-24ep.json). Recorded in the notes rather than presented as a vendor fact.Gates:
scripts/syntax-check.js453 files OK;scripts/audit-port-types.js"No port contradicts its declared type";test/hardware-invariants.test.js26/0;test/poe.test.js21/0;test/poe-inference.test.js17/0 (including "a device that claims a PoE budget actually sources power");test/catalogue-hygiene.test.js25/0;test/doc-catalog-counts.test.js43/0;scripts/regen-registry-doc.js"catalogue pages are current".#130 stays open and blocked, unchanged: Ubiquiti publishes no UDW-PRO port census on any surface checked (techspecs, store, datasheets, FCC, Wayback, and the 701-record controller device database). Unblock is still any Ubiquiti-hosted page/datasheet/QSG/FCC exhibit/storefront/KB article/device record naming
UDW-PRO, or the requester confirming the base UDW.jaylouisw referenced this pull request2026-11-19 12:38:31 +00:00
Red classified: real failing suite, this PR's own file — not staleness, not a superseded merge.
mergeable=true, and a localorigin/mainmerge has no conflict, so this is not the add/add case.Local repro (
node test/spec-vs-description.test.js, heade95b22d3merged with main053b3995), 1 of 449 failing:Cause — a regex gap, not the device data.
test/spec-vs-description.test.js:124exempts a box from that rule only when its description matches bothPOE_INandPOE_OUT;POE_OUTneeds a literalpassthrough,poe out,N poe+, orpoe … out. The old description read "one passing PoE through" — also a non-match — but the old JSON had nopoeOutoneth1, so the rule never fired. This PR addspoeOut: true/poeOutClass: "PoE+"toeth1(correctly — the vendor's "PoE+ GbE Port (Passthrough)"), and the new description says "one passing up to 15.4 W of PoE+ through", which still matches neitherpassthroughnorpoe … out. So the exemption misses and the device is judged as claiming power it cannot supply.Also note the PR does two things the description doesn't claim: it raises
wwan0from100Mto150Mand adds apoebudget block — both consistent with the cited datasheet rows.Needs a decision — the author's (
-firmware), or Jay's if it is a policy call:POE_OUTto accept "passing … PoE+ through", which changes a gate that every device in the catalogue is judged by.(1) is one clause and leaves the invariant untouched; (2) is the honest fix if the regex is considered too literal, but it loosens the check for all 700-odd devices, so I am not making that call in surgery.
Verified: full suite on the merged tree — 449 tests, 1 fail (this one); every other leg green locally. Branch left untouched, nothing rebased, nothing merged.
Re-verified against today's main (
df8e41d9), unchanged: still exactly one failing assertion.Clean
origin/mainmerge (no conflicts), full suite locally: 382 suites, 12,889 assertions, 1 failed —Everything else (port-type audit, control bytes, validation, hardware invariants, poe) is green on the merged tree, and the PR's own device JSON is not at fault — the gap is the
POE_OUTexemption intest/spec-vs-description.test.jsnot accepting "passing … PoE+ through".So the two options from my 12:40Z comment still stand, and the fix is one clause, not structural:
-firmware): say the vendor's word — "…through (passthrough)" — the existing exemption then matches;POE_OUTto accept "passing … through", which loosens a gate applied to every device.test/is not surgery's to edit, so this stays with the author or Jay. Nothing rebased, branch untouched (e95b22d3, now 32 behind main).Surgery re-verification, 18:5xZ — main is now
e0fa4221(five commits on from the last check).Rebased cleanly onto
e0fa4221in a scratch worktree (no conflicts, mechanically clean), then ran the suite that owns this failure:Identical single failure — nothing new, no regression from the eleven UniFi devices that landed in #2192 (that PR touched UCG/UDM/UDR/UX models, not the LTE Backup Pro). I did not push the rebase: a clean rebase cannot change this outcome, and the repo would only gain another red run.
Still needs Jay's decision: either the port data is wrong (a PoE-in-only box should not have
poeOut: trueoneth1) or the rule needs a passthrough exception (a device may pass through power it does not itself supply). Surgery can implement whichever you choose; it cannot choose for you.2026-11-19 23:5x UTC - the red legs were this file's prose, not its ports. Fixed in
da2ecc26; full suite now 374/374, 12,696 assertions, 0 failed.All three Node legs failed
test/spec-vs-description.test.jswithubiquiti/U-LTE-Backup Pro: says PoE-in, 1 port(s) source. The check exempts a dual-role box only when its description names the output side; the previous text said "one passing up to 15.4 W of PoE+ through", which matches none of the comparator's output phrasings. The vendor's own row is(1) PoE passthrough output (requires a PoE+ switch)— tech-spec page and datasheet p.1 text layer both - so the fix is the vendor's word, not a re-wording to quiet the suite:The
2x 1G RJ45form also puts the port count under the comparator's "promises more ports than it has" check (2 claimed, 2 present). No port, wattage, capability or source changed.Gates on
da2ecc26:scripts/syntax-check.js453 files OK;scripts/audit-port-types.jsno contradiction;test/spec-vs-description.test.js3/3;test/hardware-invariants.test.js26/26;scripts/audit-poe-budget.js0 budgets without a PSE;scripts/run-tests.js374 suites / 12,696 assertions / 0 failed.