[Device]: ASUS RT-AX89U - the actual router model, catalogue only has RT-AX89X #8

Closed
opened 2026-11-08 06:05:43 +00:00 by jaylouisw · 1 comment
Owner

Ported from GitHub Jaylouisw/packetforge#96, filed before Forgejo became the source of truth.

Summary

Home Assistant's Asus integration reports the live hardware as Asus / RT-AX89U, firmware 3.0.0.4.388.33, on both 10.0.0.1 and 10.0.0.2 — two units, main router and AiMesh node.

The catalogue has asus/rt-ax89x but no rt-ax89u. They are different SKUs (the U is the operator/multi-pack variant), so a rebuilt topology labelled "RT-AX89X" is subtly wrong about the hardware that is actually sitting in the house.

Requested

Add devices/asus/rt-ax89u.json, mirroring the AX89X port set if the port map is genuinely identical — or alias the two models so a search for either resolves.

Notes

Found by reading the real device registry rather than by guessing a model from the vendor list, which is how the wrong SKU got onto the canvas in the first place.

> Ported from GitHub `Jaylouisw/packetforge#96`, filed before Forgejo became the source of truth. ## Summary Home Assistant's Asus integration reports the live hardware as **`Asus / RT-AX89U`**, firmware `3.0.0.4.388.33`, on both `10.0.0.1` and `10.0.0.2` — two units, main router and AiMesh node. The catalogue has `asus/rt-ax89x` but no `rt-ax89u`. They are different SKUs (the U is the operator/multi-pack variant), so a rebuilt topology labelled "RT-AX89X" is subtly wrong about the hardware that is actually sitting in the house. ## Requested Add `devices/asus/rt-ax89u.json`, mirroring the AX89X port set if the port map is genuinely identical — or alias the two models so a search for either resolves. ## Notes Found by reading the real device registry rather than by guessing a model from the vendor list, which is how the wrong SKU got onto the canvas in the first place.
Author
Owner

Modelled — devices/asus/rt-ax89u.json, commit ca10781 on fix/sfp-plus-connectors.

You were right that the two string are one board, and it is now measured rather than assumed:

  • ASUS ships the AX89X firmware as FW_RT_AX89U_<build> — an owner's flash log on an RT-AX89X runs FW_RT_AX89U_300438647027 and then FW_RT_AX89X_300438647468 on the same unit;
  • Asuswrt-Merlin's model.c maps the hardware model string RT-AX89U to MODEL_RTAX89U;
  • the GPL/SWRT source for the AX89X builds as target rt-ax89u.

So RT-AX89U is in the catalogue with the AX89X's own port map (1x 1G WAN, 8x 1G LAN, 10GBASE-T RJ45, one 10G SFP+ cage, two radios), sourceUrl pointing at the AX89X technical-specification page, and a notes field that says which board it is so the next reader does not have to re-derive it.

test/intake-batch.test.js pins the one claim that could rot: the two specs must describe exactly the same sockets, so an edit to one without the other fails the suite instead of quietly inventing a second product. Docs counts updated (catalogue 1,584 → 1,586; README.md, docs/DEVICE_REGISTRY.md, docs/ROADMAP.md and the generated wiki).

Modelled — `devices/asus/rt-ax89u.json`, commit `ca10781` on `fix/sfp-plus-connectors`. You were right that the two string are one board, and it is now measured rather than assumed: * ASUS ships the AX89X firmware as **`FW_RT_AX89U_<build>`** — an owner's flash log on an RT-AX89X runs `FW_RT_AX89U_300438647027` and then `FW_RT_AX89X_300438647468` on the same unit; * Asuswrt-Merlin's `model.c` maps the hardware model string `RT-AX89U` to `MODEL_RTAX89U`; * the GPL/SWRT source for the AX89X builds as target `rt-ax89u`. So `RT-AX89U` is in the catalogue with the AX89X's own port map (1x 1G WAN, 8x 1G LAN, 10GBASE-T RJ45, one 10G SFP+ cage, two radios), `sourceUrl` pointing at the AX89X technical-specification page, and a `notes` field that says which board it is so the next reader does not have to re-derive it. `test/intake-batch.test.js` pins the one claim that could rot: **the two specs must describe exactly the same sockets**, so an edit to one without the other fails the suite instead of quietly inventing a second product. Docs counts updated (catalogue 1,584 → 1,586; `README.md`, `docs/DEVICE_REGISTRY.md`, `docs/ROADMAP.md` and the generated wiki).
Sign in to join this conversation.
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#8
No description provided.