Error message on HTTP calls, from ESP32 (In Pilot version)

[Geek]

No description provided.

[John Maloney]

What is the error message? Which pilot version were you using (the about... menu command gives the version)?

I did a quick test with a Wemos d1 mini. After connected to my WiFi, I was able to retrieve the version file from microblocks.fun:

The Wemos d1 mini is an ESP8266 board. I'll test this on an ESP32 board when I get home (don't have one with me now).

[John Maloney]

It is mostly working for me on the ESP32, but I've seen a few failures. If you are getting "Could not connect" errors you may be hitting the connection timeout. The time it takes to connect to a server depends on things outside of your control, such as the speed of your local router and which DNS server your router is using. The current timeout, 800 msecs, is probably too short. I will increase it in the next Pilot release.

[Geek]

The messages appeared in version 1.1.56 pilot, I have also tried it with 1.1.59 pilot - firmware v154 and it gives the same result

‌

[John Maloney]

Thanks. I'm hoping this will be fixed by increasing the connection timeout. That will be in the next pilot, probably out by early next week.

[John Maloney]

I've done a new Pilot (1.1.61) that increases the connection timeout.

To get it that version, run MicroBlocks in the browser and reload the page if it isn't 1.1.61 or click the "Pilot" button on the Download page to download the stand-alone pilot app for your platform. You will also need to update the firmware on your board ("update firmware on board" command in the gear menu) The "about" box should show firmware v155 or later.

Let me know if that fixes your HTTP connection failures.

[Geek]

It works fine!

Thank you!