Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot Set WIFI SSID that Contains Emoji #1201

Open
erichowey opened this issue Oct 15, 2024 · 6 comments
Open

Cannot Set WIFI SSID that Contains Emoji #1201

erichowey opened this issue Oct 15, 2024 · 6 comments
Labels
Area: GUI Related to the GUI Area: Hardware Protocol Related to communication with hardware/software trackers Area: Server Related to the server Priority: Normal The default priority Type: Bug Something isn't working

Comments

@erichowey
Copy link

Using SlimeVR server, I'm unable to set the wifi when the network's SSID contains emoji. The SSID that is sent is ? rather than the emoji. This works fine using the Butterscotch firmware tool so it appears to be a SlimeVR Server specific issue.

@TheDevMinerTV
Copy link
Member

I... what.

  1. To use emojis, you need proper UTF-8 support which the tracker firmware doesn't have (and will ever have, it's just too big for the small micro controllers)
  2. The ? is very likely because somewhere the emoji's UTF-8 encoding gets broken
  3. Why do you have an emoji in your WiFi password... I'm surprised your router is even letting you do that. WPA2 explicitly states that only printable ASCII characters are allowed. (WPA3 isn't supported by the tracker hardware.)

@erichowey
Copy link
Author

To use emojis, you need proper UTF-8 support which the tracker firmware doesn't have (and will ever have, it's just too big for the small micro controllers)

You might want to double check if you're correct or not. My wifi configuration with the SSID containing emojis works perfectly fine using the butterscotch site or using PlatformIO directly. It only doesn't work with SlimeVR server.

Why do you have an emoji in your WiFi password...

I'm not. I said i'm using emoji in the wifi SSID - not password

@erichowey
Copy link
Author

See? Works perfectly fine.
image

@TheDevMinerTV
Copy link
Member

I'm not. I said i'm using emoji in the wifi SSID - not password

Oops, missed that. Yeah, the SSID can be whatever, as long as it's 32 bytes with a NUL byte at the end.

Still definitely a weird issue lol

@ButterscotchV ButterscotchV added Type: Bug Something isn't working Area: Hardware Protocol Related to communication with hardware/software trackers Priority: Normal The default priority Area: GUI Related to the GUI Area: Server Related to the server labels Dec 8, 2024
@ButterscotchV
Copy link
Member

Marked as GUI, server, and hardware protocol, as I do not know which step this issue originates from. Please update labels when known.

@unlogisch04
Copy link
Contributor

Trackers from version 0.4.0 supports bwifi (base64) encoding for the transfer the ssid and of the password. So trackers with version < 0.4.0 do not support that feature.
Transfering utf8 over terminal directly might work, as long there are no null or termination (lf). but did not test that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: GUI Related to the GUI Area: Hardware Protocol Related to communication with hardware/software trackers Area: Server Related to the server Priority: Normal The default priority Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants