[Bunton33]

Adds all six HUB75 color orders to the M-1 firmware, so a panel with swapped color lines (the customer's green/blue panel needs RBG) can be fixed from Config > LED & Hardware. Same gap as wled#5723 (nothing is posted upstream).

What was wrong (b8 / upstream 16.0.1)

• Only RGB and BGR were applied; GRB, BRG, RBG and GBR were silent no-ops.
• The LED settings page hid the Color Order select for HUB75.
• BusHub75Matrix did not report its order, so any config save wrote RGB back.

What this does

• All six orders are applied by permuting the driver's r/g/b GPIO roles once, before the driver is created (the mechanism the old BGR case already used). No per-pixel cost; covers the buffered and the direct-draw paths. Meaning matches WLED's PolyBus orders and WLED-MM Effect Request: Random Pixel Strobe "Overlay" wled/WLED#349: "RBG" = the panel's G input lights blue and its B input lights green.
• Shipped units are unaffected. The factory cfg.json stores "order":0 and any saved config stores 1; both have always meant "no swap" on HUB75 and still do. Real GRB on HUB75 uses a new HUB75-only value 6. BGR (4) gives exactly the old pins.
• Persists: getColorOrder() override, so the choice survives save and reboot.
• Settings page (Config > LED & Hardware): Color Order shown for HUB75 with RGB, BRG, RBG, BGR, GBR, GRB. Switching a bus type to HUB75 and back keeps its order.

Order	Panel inputs R / G / B carry	M-1 pins r1,g1,b1 / r2,g2,b2
RGB (stored 0 or 1)	R / G / B	1,5,6 / 7,13,9 (unchanged)
BRG	B / R / G	5,6,1 / 13,9,7
RBG	R / B / G	1,6,5 / 7,9,13
BGR	B / G / R	6,5,1 / 9,13,7 (same as before)
GBR	G / B / R	6,1,5 / 9,7,13
GRB (6)	G / R / B	5,1,6 / 13,7,9

Verified (no hardware)

• apollo/hub75-color-order-test.js (runs in npm test): reads the table and the 0-is-RGB rule straight from the C++ and checks permutations, unchanged pins for stored 0/1/7-15, BGR = old swap, agreement with PolyBus and WLED-MM Effect Request: Random Pixel Strobe "Overlay" wled/WLED#349 on both panel halves. Five deliberate mutations of the C++ are all caught. npm test: 24/24.
• Settings page: 13 scenarios run on the real page script (load 0/1/3/6, both type round trips, manual choices, idempotence): all pass.
• Builds: apollo_m1 (+224 bytes vs b8), esp32s3dev_16MB_opi_hub75, esp32dev (non-HUB75, helpers compile out): all succeed, no new warnings.
• Independent review (shipped-unit safety, settings page, C++): no functional defects; its one UX finding (type round trip) is fixed in the second commit.

Bench check before merging (about 2 minutes per order)

1. Config > LED & Hardware > HUB75 output > Color Order = X, Save, reboot.
2. Solid red, green, blue (e.g. {"seg":[{"fx":0,"col":[[255,0,0]]}]}); top and bottom halves must match.
   On a standard panel: RGB = red/green/blue; RBG = red/blue/green; BGR = blue/green/red; GRB = green/red/blue; BRG = green/blue/red; GBR = blue/red/green.
3. Regression: OTA an untouched b8 unit (raw /cfg.json shows "order":0) without touching settings; colors must be unchanged and the page shows RGB.
4. On the customer's G/B-swapped panel, RBG must give correct colors.

Notes

• Applies to the whole HUB75 output (one set of color lines for a chain). On S3 the new order takes effect after the reboot WLED already asks for.
• Safari/iOS may show the disabled duplicate "GRB" entry greyed out; it cannot be selected.
• The b8 release does not have this; it ships with the next bundle (gates and apollo/RELEASE_CHECKLIST.md).
• Customer instruction once released: Config > LED & Hardware > Color Order: RBG > Save > reboot.
• With M-1: honour the launch preset without WiFi (setup card no longer forced at every boot) #9: saving LED & Hardware on a unit without WiFi also counts as choosing its launch preset, so the setup card stops appearing at power-on (it stays available as preset 5 "Setup").

Credits: troyhacks (MoonModules#349, order semantics and UI idea), softhack007 (pin-swap suggestion in that review), jsenecal (analysis in wled#5723). All EUPL-1.2; no code copied.

🤖 Generated with Claude Code

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

• Source mode: Auto
• Repository: ApolloAutomation/WLED-M1
• Branch: feat/hub75-color-order
• File: .coderabbit.yaml
• Commit: 439ddaa
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Advanced
• Run ID: 194154be-2277-42b4-a99d-0969de13dd61

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}