You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Home Assistant Android app version(s): 2023.1.1-full
Android version(s): 13 (TQ1A.230105.002)
Device model(s): Pixel 7 Pro
Home Assistant version: 2023.2.5
Last working Home Assistant release (if known): 2023.2.5
Description of problem, include YAML if issue is related to notifications:
An SSID of only whitespace is actually a valid SSID. I currently have my network name set to (two space characters).
When configuring the "Home Network WiFi SSID" in the Home Assistant Companion for Android app, it rejects a whitespace-only SSID. After tapping "Add", the "New WiFi SSID" text input is outlined red and an "!" icon is shown. There is no error message shown.
(I won't ask you to support newlines (which... kind of actually work in SSIDs too... but break absolutely everything) but I've generally not actually had compatibility issues with spaces, so I thought I'd file a bug.)
Screenshot or video of problem:
Additional information:
The text was updated successfully, but these errors were encountered:
Home Assistant Android app version(s): 2023.1.1-full
Android version(s): 13 (TQ1A.230105.002)
Device model(s): Pixel 7 Pro
Home Assistant version: 2023.2.5
Last working Home Assistant release (if known): 2023.2.5
Description of problem, include YAML if issue is related to notifications:
An SSID of only whitespace is actually a valid SSID. I currently have my network name set to
(two space characters).
When configuring the "Home Network WiFi SSID" in the Home Assistant Companion for Android app, it rejects a whitespace-only SSID. After tapping "Add", the "New WiFi SSID" text input is outlined red and an "!" icon is shown. There is no error message shown.
(I won't ask you to support newlines (which... kind of actually work in SSIDs too... but break absolutely everything) but I've generally not actually had compatibility issues with spaces, so I thought I'd file a bug.)
Screenshot or video of problem:
Additional information:
The text was updated successfully, but these errors were encountered: