S2 Boards Going Offline Since Beta.19 Moderators: adafruit_support_bill, adafruit

[adafruitguy]

Since upgrading from Beta.16 to Beta.19 my S2 boards are going offline, and require a reboot to reconnect.

They are available via ping on the local networks, but no longer connected to IO. This includes: FunHouse, MagTag, Metro S2, Adafruit Feather S2, and QT Py S2.

My Ultimate Maker Feather S2 is still running Beta.16 and hasn't experienced a problem. Metro M4 w/ AirLift & PyPortal do not have the disconnect problem and are running Beta.19.

Huzzah 32's are covered in a separate issue.

1 of 2

Screen Shot 2021-12-28 at 12.12.30 PM.png (988.71 KiB) Viewed 137 times

2 of 2

Screen Shot 2021-12-28 at 12.12.38 PM.png (317.79 KiB) Viewed 137 times

[adafruitguy]

Serial output from Adafruit Feather S2...

Code: Select all | TOGGLE FULL SIZE

MQTT ping packet:
          [0xC0],   [0x00],
Client sendPacket returned: 2
Read data:                [0xD0],
Packet Type:              [0xD0],
Read data:                [0x00],
Packet Length:  0
PING!
MQTT ping packet:
          [0xC0],   [0x00],
Client sendPacket returned: 2
Read data:                [0xD0],
Packet Type:              [0xD0],
Read data:                [0x00],
Packet Length:  0
PING!
MQTT ping packet:
          [0xC0],   [0x00],
Client sendPacket returned: 2
Read data:                [0xD0],
Packet Type:              [0xD0],
Read data:                [0x00],
Packet Length:  0
PING!
MQTT ping packet:
          [0xC0],   [0x00],
Client sendPacket returned: 2
Connecting to: io.adafruit.com
Connect result: 0
Connecting to: io.adafruit.com
Connect result: 0
Connecting to: io.adafruit.com
Connect result: 0
Connecting to: io.adafruit.com
Connect result: 0
Connecting to: io.adafruit.com
Connect result: 0
Connecting to: io.adafruit.com
Connect result: 0
Connecting to: io.adafruit.com
Connect result: 0
Connecting to: io.adafruit.com
Connect result: 0
Connecting to: io.adafruit.com
Connect result: 0
Connecting to: io.adafruit.com
Connect result: 0
Connecting to: io.adafruit.com
Connect result: 0
ERROR: Unable to connect to Adafruit.IO


[adafruitguy]

Reverting the S2 boards to beta.16 fixes the problem.

[brubell]

Do you have the full serial output after a reboot/reset? It should include information prior to the output you submitted?

Issue filed here for tracking: https://github.com/adafruit/Adafruit_Wi ... issues/199

[adafruitguy]

Except for the initial stuff @ boot it's many minutes to a few hours of the MQTT ping packets.

Code: Select all | TOGGLE FULL SIZE

MQTT ping packet:
          [0xC0],   [0x00],
Client sendPacket returned: 2
Read data:                [0xD0],
Packet Type:              [0xD0],
Read data:                [0x00],
Packet Length:  0
PING!


Are you looking for stuff near the board starting or something else?

[brubell]

Are you looking for stuff near the board starting or something else?

Near the board starting.

To confirm - the boards are initially connected, then disconnect at some point, then fail to reconnect? Or are they not connecting at all

[adafruitguy]

I can happily send the board bring-up stuff. It includes my IO Key - so let me know where to send it, or if you want that redacted out.

The ESP32-S2 boards all connect on Beta.19 and stay connected for a little while. Which I would define as a random # of minutes or hours, then they all eventually get to the "ERROR: Unable to connect to Adafruit.IO" state - while remaining locally responsive to pings (IP ICMP).

The SAMD51 + AirLift boards keep chugging without a problem on Beta.19, as do my ESP32-S2 boards on Beta.16. Both have been connected since board boot (for week+ / weeks).

We are tracking the HUZZAH ESP32 on Beta 19 in a separate thread. That never connected to Adafruit.IO with Beta.19. And, in yet another thread, I have one HUZZAH ESP32 unit that never once connected to Adafruit IO.

[brubell]

Submit those logs to io.adafruit.com/support and the logs will be emailed to us, privately.

Thanks for the explanation regarding the behavior of the boards, looking into both issues this week.

[adafruitguy]

Sent.

[Jdfry]

Has there been any resolution on this yet? I have a PyPortal that is behaving the same way, in that from a few minutes to several hours (~18+) the board will disconnect from Adafruit.IO. I'm running CircuitPython and have modified the code with additional timeout time of 5 seconds via io.loop(5) in the try statement, with an except statement of wifi.reset(), wifi.connect(), and another indented try with io.reconnect() and except statement of io.connect(). I thought I had solved the issue by including wifi.connect() after the example code's wifi.reset(), but then still crashed after about 18 hours.

[brubell]

Has there been any resolution on this yet? I have a PyPortal that is behaving the same way, in that from a few minutes to several hours (~18+) the board will disconnect from Adafruit.IO. I'm running CircuitPython and have modified the code with additional timeout time of 5 seconds via io.loop(5) in the try statement, with an except statement of wifi.reset(), wifi.connect(), and another indented try with io.reconnect() and except statement of io.connect(). I thought I had solved the issue by including wifi.connect() after the example code's wifi.reset(), but then still crashed after about 18 hours.

This thread is for Adafruit WipperSnapper, please post a CircuitPython issue in the Adafruit IO Forum (viewforum.php?f=56) along with your full code so we can take a look at it.