05-25-2024, 01:20 AM
(05-24-2024, 02:14 PM)Tim Curtis Wrote:(05-24-2024, 01:07 PM)TheOldPresbyope Wrote:(05-24-2024, 11:56 AM)Tim Curtis Wrote: I am able to repro "SCAN only displaying the first word in a " 2-words-with-a-space" SSID. This looks like a parsing issue. I'll add to the TODO list.
You beat me to it again.
but I had gone a step further this morning.
1. Temporarily configured my Pi400 (full-on RaspiOS) as a hot spot with the imaginative SSID "Hot Spot".
2. Scanned for SSIDs with a moOde 9..0.0 player, which returned only the first word "Hot".
3. Set the correct WiFi SSID and pw manually in the player, saved, and rebooted.
4. Using AngryIP on the Pi400, I don't see the moOde player in the subnet address space managed by the hotspot. OTOH I can associate with the hotspot using my Linux laptop and it does show up in the subnet.
5. Running a WiFi analyzer I see that the moOde player has reverted to its own HotSpot mode.
Regards,
Kent
Can you clarify, is this a conflict with name "Hot Spot"?
In any case grab the latest www/net-config.php from the repo and let me know if the scan list bug is fixed.
I amended my post this morning before we went out. Fat fingers had led to a mis-typed pw when I created the entry. Naturally, moOde went to AP mode when it failed to associate with "Hot Spot".
This evening I overwrote net-config.php directly. It successfully finds "Hot Spot" and I can select it and enter a pw. After saving and rebooting, the player is associated with the "Hot Spot" access point. The 'Hot Spot.nmconnection' file looks correct.
Regards,
Kent
PS - for anyone tempted similarly to overwrite net-config.php directly don't forget to change the last line to read "include('footer.min.php')", e.g., point to the minified version of footer.php.