Closed jdmc closed 6 months ago
Blueforcer
commented
6 months ago Sounds like an hardware issue to me. After thousands of installations, I have not yet received a similar problem. Which would certainly happen a lot if it was a bug.
(unless unifi access points were used)
I would suggest that you try a different firmware, or a WiFi demo for the ESP32.
jdmc
commented
6 months ago I'm pleased to inform you that I've resolved the issue.
Here's what I did differently from the previous installation:
Firstly, I ensured the battery was charged to at least 50%. Then, I reinstalled firmware version 0.94. This time, after installation, I disconnected the device from my laptop. To connect to the access point, I used an older tablet, which had fewer issues establishing and maintaining a connection. The device stayed connected to this access point reliably. Thank you for your attention to this matter.
summarized:
Issue resolved
Bug report
Describe the bug
After updating my TC001 device to Version 0.94, it experiences significant delays when connecting to an access point named "awtrix_XXXXX" with the password "12345678". The connection process involves multiple attempts to obtain the connection checking for an IP address during the connection intent, causing extended waiting times. Despite eventually establishing a connection to the access point, the device fails to scan or connect to any Wi-Fi networks. Even manual entry of my home Wi-Fi network's SSID doesn't work. I conducted tests using a laptop running Windows 11, an older Xiaomi Android phone, and a Pixel 8 Pro phone, all using the Chrome browser for debugging, but the issue persisted across all devices.
PS Did not initially configure the clock with the factory/original stock, directly flashed it with Awtrix Light.
Additional information
To Reproduce
Flashed Version 0.94: I successfully updated my TC001 device to Version 0.94. (Flashed it 2 times to be sure there was no error)
Connected to Access Point: After updating, I connected to an access point named "awtrix_XXXXX" using the password "12345678". Everything went "smoothly" here.
Encountered Wi-Fi Login Screen: Once connected to the access point, I was prompted with a Wi-Fi login screen, which is typical when setting up a new Wi-Fi connection.
Unable to Scan Wi-Fi Networks: Here's where the problem started. When I tried to scan for available Wi-Fi networks, the device couldn't find any. It was like it couldn't see any networks around, which was odd because there should have been several.
Manually Entered Home Wi-Fi SSID: Thinking it might be a scanning issue, I tried manually entering the name of my home Wi-Fi network (SSID). But even after doing that, the device still couldn't connect.
Used Chrome DevTools for Debugging: Frustrated, I decided to dive into some troubleshooting. I used Chrome DevTools to inspect the network and see if I could pinpoint where the problem was occurring.
Expected behavior
Wi-Fi Scanning: Upon reaching the Wi-Fi login screen, the device should promptly scan for available Wi-Fi networks in the vicinity. It should then display a list of detected SSIDs, allowing the user to select their desired network for connection.
Manual SSID Entry: In case automatic scanning fails to detect nearby networks, the device should allow users to manually enter the SSID of their home Wi-Fi network. Upon entry, it should promptly attempt to connect to the specified network using the provided credentials.
Overall, the expected behavior is for the TC001 device to successfully connect to Wi-Fi networks, either automatically through scanning or via manual entry, providing users with reliable connectivity options.
Screenshots
Logs
it says something like "device lost" after the connection with Wifi failed, because it says that it connects to the Wifi
Additional context
I've encountered issues with SSID detection on my printer previously, where it wouldn't display my SSID due to the specific Wi-Fi channel I was using. However, it would show other SSIDs in the vicinity. This situation differs from the current scenario.