While setting up the VacuGlide 2 for the first time, I noticed that no available Wi-Fi networks were displayed in the network selection list.
While investigating the issue using the browser’s developer tools, I noticed an error related to invalid JSON syntax in an entry that appeared to contain the list of discovered networks (discovered-networks or similar).
The issue could be reproduced in an environment where a Wi-Fi network with the SSID (for example) /\utoblow was available. After temporarily disabling this network, the other detected Wi-Fi networks were displayed correctly in the selection list and i could finally connect.
Once connected to the correct SSID, reconnects to the saved one work properly, even if the /\utoblow-SSID was turned back on.
This could be particularly problematic in environments with many neighboring Wi-Fi networks. If the affected SSID belongs to a neighboring network, the device may have to be moved to a location where that network is no longer detected before the user’s own network appears in the list (or in this case any network at all), provided that the user’s network is still within range. Since the neighboring network cannot simply be switched off temporarily, this can make the issue particularly difficult to work around.
This suggests that the backslash in the SSID may not be handled correctly during JSON serialization or parsing. It might be worth checking whether SSIDs containing characters that require escaping in JSON are detected and handled appropriately during First-Time Setup.
Your finding is correct and we know about this issue. We have shipped a fix in the latest Ultra firmware that had a similar issue(1.06-prod).
We have the fix ready to deploy for Vacuglide 2 as well and it will be deployed most likely this month or the next month.
To clarify why this was not an emergency for us is because we rarely got complaints from the customers in the real world from this bug and even if we ship an update the bug does not really disappear because they still need to connect to update. I think we only got 2 issues like this since we started selling VG2.
Usually we wait a bit longer to deploy new firmware as the update process is annoying for the users and this would come with no extra features.
Super thanks for reporting this even that we knew about it, it helps knowing that you guys are involved and wanting to help us solve bugs like that
I was already worried that my network setup might be a bit unusual
It’s great to hear that the bug is known and successfully addressed in the Ultra firmware.
Thank you very much for the feedback and update. For me, it wouldn’t be an urgent update either, since I figured it would affect very few people. However, I suppose new products or newly manufactured devices will eventually be shipped with the appropriate fix included in the firmware.
I was more than happy to share that, even though it was already known to you. You guys are doing an absolutely outstanding job, and the device, the communication, and the technology immediately captivated me.
