Can't connect to my LAN mosquitto MQTT broker following update to pilot 1.2.25

[Simon Walters]

Hi John

thanks for fixing previous issue :)

Unfortunately, the script I was previously running on my PicoW doesn’t seem to want to connect to my LAN mosquito MQTT broker anymore

I’m trying a few things out but no success so far :(

‌

Simon

[Simon Walters]

I substituted an ESP8266 board and that worked fine

[John Maloney]

Thanks for trying the ESP8266. So the issue is definitely with the PicoW.

There were no explicit WiFi or MQTT changes in the past several pilot releases, but some other change could have had an unwanted side effect. Do you remember the last release that worked?

Actually, there is one recent change -- the WuKong2040 VM no longer supports WiFi. (A WuKong2040 hardware design flaw prevents detecting the difference between a Pico-W and a plain Pico when running the WuKong2040 on battery power. It was hanging on startup if a plain Pico was installed. Disabling WiFi was the lesser of evils.) Are you using WuKong2040?

The PicoW WiFI cannot connect to open networks (ones without passwords). That's a low-level WiFI driver issue that I've reported. I think you know about the restriction since I believe you were the one who reported it!

I'm leaving shortly for two weeks of traveling so my debugging time will be limited but let me know if you find any further clues. (e.g. do all WiFi operations fail on your PicoW or just MQTT? Does decreasing the distance to the WiFI router help?)

Did MQTT work on the Pico-W in the previous stable release? If so, you can revert to that release:

https://microblocks.fun/downloads/v1.2.5/

[John Maloney]

I did a quick test with the test.mosquitto.org broker, and that worked.

I used Firmware v191 on a Pico-W using the stable release in the Chrome browser.

[Simon Walters]

Unfortunately, I don’t know what what previous version I was running

(Has been running 24/7 for past week driving a Neopixel)

I’ll try reverting to previous versions and see if I get anywhere

It's a vanilla Pi PicoW

It’s not a major issue as the ESP8266 can replace it in the sort term

Have a nice trip away :)

I’ll post any updates :)

Simon

[Simon Walters]

PEBKAC :)

I was loading in the wrong script :) (it was one using my open SSID which explains why it didn’t work but worked on the ESP8266)

What a fool :)

I didn’t even check the WiFi connection block as I knew it was working as I have a say block saying connected - obviously, in retrospect, the connect block must be timing out without raising an error

I’ve amended my “connected “ message to add in the IP address which should be more robust visual indicator :)

Simon

[John Maloney]

I'm glad you found the problem, and thanks for letting me know. Now I won't need to worry about it on my trip.

[John Maloney]

Marking this resolved. There is already an issue about the Pico-W failing to connect to public networks. Hoping that will get fixed in drivers soon. MicroPython also ran into this issue and I believe they found a workaround.