Skip to content

fix: use base64 serial command for Wi-Fi provisioning - #1933

Open
qus20000 wants to merge 1 commit into
SlimeVR:mainfrom
qus20000:fix/set-bwifi-provisioning
Open

qus20000 wants to merge 1 commit into
SlimeVR:mainfrom
qus20000:fix/set-bwifi-provisioning

Conversation

@qus20000

Copy link
Copy Markdown

Summary

This changes serial Wi-Fi provisioning to send credentials with SET BWIFI instead of quoted SET WIFI.

The SSID and password entered in the UI are still handled as normal text in the app, but are encoded as UTF-8 base64 immediately before being written to the tracker serial port.

Why

The tracker firmware already supports SET BWIFI for base64-encoded Wi-Fi credentials. This avoids command parser ambiguity when SSIDs or passwords contain spaces, quotes, non-ASCII characters, or punctuation.

This is a real setup issue for users in Korea: ISP-provided routers from the three major carriers commonly ship with SSIDs and/or default passwords containing special characters, for example + or @. Sending those values through the quoted SET WIFI "<ssid>" "<password>" command can fail during provisioning even though the same credentials are valid.

Using SET BWIFI makes the serial payload command-safe while keeping the UI behavior unchanged.

Compatibility

SET BWIFI is supported by the stock SlimeVR Tracker ESP firmware and was added as part of the firmware's base64 Wi-Fi credential command support.

Testing

  • Ran git diff --check
  • Ran .\gradlew.bat :server:desktop:compileKotlin --no-daemon
  • Android compile was not run locally because Android SDK is not configured in this environment

- Send Wi-Fi provisioning credentials with SET BWIFI instead of quoted SET WIFI.
- Encode UI-provided SSID and password as UTF-8 base64 in desktop and Android serial handlers.
- Preserve empty-password provisioning by sending an explicit empty password argument.
- Avoid parser issues with special characters commonly found in ISP-provided router credentials.
@loucass003

loucass003 commented Sep 20, 2026 •

Copy link
Copy Markdown
Member

Please implement it to server rewrite. see #1880

@qus20000

Copy link
Copy Markdown
Author

Please implement it to server rewrite. see #1880

Hello, Thanks for the clarification. I wasn’t aware that the server rewrite was already in progress, and I’m sorry I missed that.

I’ll review the server-rewrite structure, rework the changes if needed, and then submit a PR against the rewrite branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants