FWIW, to get to the “Unable to get time” error, the WiFi connection has been successfully made - the problem has never actually been at the WiFi level, it’s either something upstream or the ntptime library is …. locally broken?
OK I tried that. But no change I still get the “Unable to set time” error but I notice it is a longer time before it says that. However, that is only to be expected.
I ran it and got :-
MPY: soft reboot
Scanning for WiFi networks.
Scanning…
Found WiFi networks:
SSID BSSID CH dB Auth
TP-Link_1102 “my mac address redacted for safety” 3 -93 WEP/WPA2
Connecting to “my router name” redacted for safety.
Status: CONNECTING
Status: NO_AP_FOUND
Status: NO_AP_FOUND
Status: NO_AP_FOUND
Status: NO_AP_FOUND
Status: NO_AP_FOUND
Status: NO_AP_FOUND
Timed out after 5 seconds…
Yes I know this, in fact if you try and run things with the secrets file blank, you will get a message saying “Secrets file empty”.
Ok, so it is in fact not connecting to your WIFI. Not that I doubted you, I’m not so swift some times decoding error messages.
Might be time to e-mail tech support directly and get them involved.
I’d put a link to this Thread in the e-mail. ;)
As I said before I need to examine what is going on inside my modem before calling for the cavalry.
The hardware to allow me to make that connection will take another one to two weeks to arrive.
This figure (-93 for dB) is extremely low. And given the fact that you are next to your router even more. So either the RM2 has a problem, or the TX-power of the RM2 is not configured correctly. But no idea how MicroPython does that. And why it would suddenly be different.
Interestingly I’ve got similarly low dB for one of my APs here, although it is in another room from the Presto.
Also interestingly, I get exactly the same fail to connect messages if I have a typo in my secrets.py SSID…
No I did this test upstairs as moving it next to the router made no difference
I have checked this value many times. It is quite complex for a few reasons but I have checked this many times. I just got an email saying my Ethernet adaptor would be delivered on the 19th August.
Can you repeat this test next to your router? It would be interesting to see the signal strength there. BTW: the fact that your router is detected by the wifi-scan does show that the wifi-chip RM2 is working.
I mean from the looks of that log, it’s just “TP-Link_1102”, but I’m clearly not helping now so I’ll butt out :-)
I was just tinkering with my just arrived Pico Lipo 2 and RM2. At one point, for what ever reason, it stopped connecting to my network / router. Connection timed out error. And hardware miss match messages in Thonny? In the end I had to power cycle my Router to get it to connect? Just a FYI post.
This is interesting. I have just repeated the test both from upstairs and next to the router and have got exactly the same dB readings.
This has got to tell me something, but I can’t figure out what yet.
Yes that indeed was the problem.
I am dyslexic and was spelling the name of my router as FRITS and not FRITZ. Couldn’t see it until I checked my system report under the Wi-Fi section.
Many thanks to everyone who contributed to this thread. You are all stars.
glad, you found the root cause to the problem.
But how could this lead you to assume it came with the firmware update, as there is no connection between updating the firmware and changing the credentials of secret.py on the PICO itself?
You usually just flash the ROM image and leave everything untouched (as long as the firmware update does not rewrite the filesystem and thus erases all content).
This might be just an unhappy coincidence…
Anyways, this just shows that we always should expect the unexpected while tinkering around with electronics… ;)
@m1cr0py7h0n If you use a with file system uf2 it will wipe everything.
The presto-v1.0.0-micropython-with-filesystem.uf2 gets you the factory setup with all the examples etc. It also resets your secrets file to a blank one. ;)