SlimeVR-Server icon indicating copy to clipboard operation
SlimeVR-Server copied to clipboard

Cannot Set WIFI SSID that Contains Emoji

Open erichowey opened this issue 1 year ago • 6 comments

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.

erichowey avatar Oct 15 '24 21:10 erichowey

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.)

TheDevMinerTV avatar Oct 15 '24 22:10 TheDevMinerTV

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 avatar Oct 15 '24 22:10 erichowey

See? Works perfectly fine. image

erichowey avatar Oct 15 '24 22:10 erichowey

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

TheDevMinerTV avatar Oct 15 '24 22:10 TheDevMinerTV

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

ButterscotchV avatar Dec 08 '24 07:12 ButterscotchV

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.

unlogisch04 avatar Dec 08 '24 14:12 unlogisch04