Fix the M-1 setup hotspot details in step 3 - #27
Conversation
Step 3 told users to join a WLED-AP network with password wled1234. That is stock WLED, not what our builds do. Both Apollo images broadcast an OPEN hotspot named after the product. Checked against the shipped firmware rather than WLED defaults: wled1234 does not appear in M-1_full_install.bin or in Apollo_M-1_Rev6_14.5.1.bin, while the sibling default wledota does appear in both, so apPass is empty. WLED-AP occurs once in each image, inside the unrelated "All Settings erased. Connect to WLED-AP to setup again" message, not as an SSID. The m1-b8 release notes say it outright: "STEP 1: join the open Apollo M-1 WiFi", plus "cleaner hotspot name: the setup WiFi is now just Apollo M-1 (no serial-number suffix)" as new in that build. 4.3.2.1 was correct and stays. Step 3 now names the open Apollo <device> hotspot, notes that builds before 16.0.1 carry a serial-number suffix, and mentions the on-panel setup card and QR code that 16.0.1 shows. Tests assert the WLED copy contains neither wled1234 nor WLED-AP, so the stock-default wording cannot come back unnoticed. The evidence is written down in docs/m1-wled-migration.md. Verified: scripts/validate_registry.py OK, 44 python tests, 28 playwright tests, 0 skipped. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
|
Warning Review limit reached
Next review available in: 18 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
1 participant
Step 3 told users to join a WLED-AP network with password wled1234. That is
stock WLED, not what our builds do. Both Apollo images broadcast an OPEN
hotspot named after the product.
Checked against the shipped firmware rather than WLED defaults: wled1234 does
not appear in M-1_full_install.bin or in Apollo_M-1_Rev6_14.5.1.bin, while the
sibling default wledota does appear in both, so apPass is empty. WLED-AP occurs
once in each image, inside the unrelated "All Settings erased. Connect to
WLED-AP to setup again" message, not as an SSID. The m1-b8 release notes say it
outright: "STEP 1: join the open Apollo M-1 WiFi", plus "cleaner hotspot name:
the setup WiFi is now just Apollo M-1 (no serial-number suffix)" as new in that
build. 4.3.2.1 was correct and stays.
Step 3 now names the open Apollo hotspot, notes that builds before
16.0.1 carry a serial-number suffix, and mentions the on-panel setup card and QR
code that 16.0.1 shows. Tests assert the WLED copy contains neither wled1234 nor
WLED-AP, so the stock-default wording cannot come back unnoticed. The evidence is
written down in docs/m1-wled-migration.md.
Verified: scripts/validate_registry.py OK, 44 python tests, 28 playwright tests,
0 skipped.
🤖 Generated with Claude Code