0

beta.6 on Funhouse - offline
Moderators: adafruit_support_bill, adafruit

Forum rules
If you're posting code, please make sure your code does not include your Adafruit IO Active Key or WiFi network credentials.
Please be positive and constructive with your questions and comments.

Re: beta.6 on Funhouse - offline

by brubell on Mon Aug 30, 2021 4:09 pm

SandPig wrote:I'm a little embarrassed that I didn't think to try that...
Good news, it connects after updating the secrets /heavy sigh
Bad news, it never goes "online"
(1.0.0-beta.8)

Registering Board...
22:35:47.960 -> registerBoard()
22:35:47.960 -> Encoding registration message...Encoded!
22:35:49.148 -> Publishing registration message...Published!
22:35:49.148 -> Publishing registration message...Published!
22:35:51.530 -> Publishing registration message...Published!
22:35:51.530 -> Publishing registration message...Published!
22:35:53.921 -> Publishing registration message...Published!
22:35:53.921 -> Publishing registration message...Published!
22:35:56.290 -> Publishing registration message...Published!
22:35:56.290 -> Publishing registration message...Published!


Could you run a speed test on the network you're using by visiting https://speed.measurementlab.net/? Copy and paste the results here.

brubell
 
Posts: 1520
Joined: Fri Jul 17, 2015 10:33 pm

Re: beta.6 on Funhouse - offline

by SandPig on Tue Aug 31, 2021 1:38 am

Test Server Los Angeles, US
Download 233.86 Mb/s
Upload 10.25 Mb/s
Latency 20 ms
Retransmission 10.54%

My traffic originates from Phoenix, AZ over COX

SandPig
 
Posts: 44
Joined: Sun Sep 10, 2017 8:25 am

Re: beta.6 on Funhouse - offline

by jerryn on Fri Sep 03, 2021 6:13 am

Just to share my experience -- your mileage may vary ;-)
I tried putting beta.8 on a Funhouse and it would not boot - no drive mounted.

I erased the flash with esptool then reloaded CircuitPython via the non-UF2 bootloader -- that worked OK
I then used the WEB USB tool to reinstall the UF2 bootloader and reloaded CircuitPython -- still working OK
I then reinstalled wippersnapper beta,8 and it mounted CIRCUIPY with a new - secrets.json
I updated the secrets.json and it is now working fine on wippersnapper.


All of the above steps are likely not necessary, but erasing the flash and reinstalling the UF2 bootloader may be helpful
see https://learn.adafruit.com/adafruit-funhouse/install-uf2-bootloader
Note: you can erase the flash via the WEBUSB Tool -- as noted in the guide.

WARNING: Do no use the WIPPERSNAPPER WEBUSB ESP32 Tool to load wippersanpper to an ESP32S2!! That did not go well ;-)


I have run into similar issues with esp32-s2 boards when loading CircuitPython and erasing the flash with esptool (command line or WEBUSB Tool) has restored them. If you erase the flash, you will have to re-install the UF2 bootloader in order to install wippersnapper.

jerryn
 
Posts: 1546
Joined: Sat Sep 14, 2013 9:05 am

Re: beta.6 on Funhouse - offline

by brubell on Fri Sep 10, 2021 9:26 am

SandPig wrote:Test Server Los Angeles, US
Download 233.86 Mb/s
Upload 10.25 Mb/s
Latency 20 ms
Retransmission 10.54%

My traffic originates from Phoenix, AZ over COX

Could you try beta.9? We've done a refactor over the registration method to increase the reliability.

brubell
 
Posts: 1520
Joined: Fri Jul 17, 2015 10:33 pm

Re: beta.6 on Funhouse - offline

by SandPig on Sun Sep 12, 2021 5:24 pm

beta.9 still isn't working (shows offline, but updates software version on the boards page), but it does produce a new symptom

13:41:40.924 -> Registering hardware with WipperSnapper...
13:41:40.924 -> Registering hardware with IO...
13:41:41.025 -> Encoding registration request...Encoding registration msg...Published!
13:41:41.025 -> Polling for registration message response...2
13:41:41.025 -> Polling for registration message response...2
13:41:41.101 -> Polling for registration message response...2
13:41:41.101 -> Polling for registration message response...2
13:41:41.135 -> Polling for registration message response...2
13:41:41.135 -> Polling for registration message response...2
13:41:41.173 -> Polling for registration message response...2
13:41:41.173 -> Polling for registration message response...2
13:41:41.211 -> Polling for registration message response...2
13:41:41.211 -> Polling for registration message response...2
13:41:41.245 -> Polling for registration message response...2
13:41:41.245 -> Polling for registration message response...2
13:41:41.282 -> Polling for registration message response...2
13:41:41.282 -> Polling for registration message response...2
13:41:41.316 -> Polling for registration message response...2
13:41:41.316 -> Polling for registration message response...2
13:41:41.352 -> Polling for registration message response...2
13:41:41.352 -> Polling for registration message response...2
13:41:41.390 -> Polling for registration message response...2
13:41:41.390 -> Polling for registration message response...2
13:41:41.427 -> Polling for registration message response...2
13:41:41.427 -> Polling for registration message response...2
13:41:41.497 -> Polling for registration message response...2

it continues the rapid-fire polling for exactly one minute and then reloads on its own.
I hope this helps.

SandPig
 
Posts: 44
Joined: Sun Sep 10, 2017 8:25 am

Re: beta.6 on Funhouse - offline

by brubell on Mon Sep 13, 2021 11:05 am

Could you try this again? We've deployed a fix to the WipperSnapper web application. You don't need to update your firmware to a new beta version.

brubell
 
Posts: 1520
Joined: Fri Jul 17, 2015 10:33 pm

Re: beta.6 on Funhouse - offline

by SandPig on Tue Sep 14, 2021 1:40 pm

brubell wrote:Could you try this again? We've deployed a fix to the WipperSnapper web application. You don't need to update your firmware to a new beta version.


10:32:25.195 -> Registering hardware with WipperSnapper...
10:32:25.195 -> Registering hardware with IO...
10:32:25.261 -> Encoding registration request...Encoding registration msg...Published!
10:32:25.297 -> Polling for registration message response...2
10:32:25.297 -> Polling for registration message response...2
10:32:25.331 -> Polling for registration message response...2
10:32:25.331 -> Polling for registration message response...2
10:32:25.365 -> Polling for registration message response...2
10:32:25.365 -> Polling for registration message response...2
10:32:25.403 -> Polling for registration message response...2
10:32:25.403 -> Polling for registration message response...2
10:32:25.471 -> Polling for registration message response...2


no change

SandPig
 
Posts: 44
Joined: Sun Sep 10, 2017 8:25 am

Re: beta.6 on Funhouse - offline

by brubell on Fri Sep 17, 2021 12:52 pm

We just released beta.10, could you try that? Thanks!

brubell
 
Posts: 1520
Joined: Fri Jul 17, 2015 10:33 pm

Re: beta.6 on Funhouse - offline

by SandPig on Sat Sep 18, 2021 8:27 am

unfortunately, beta.10 produces the same results.
The serial output appears to be a bit more verbose during connection, I assume the is an artifact of testing.

05:19:33.765 -> Connecting to: io.adafruit.com
05:19:33.765 -> Connect result: 1
05:19:33.765 -> MQTT connect packet:
05:19:33.765 -> [0x10], a [0x61], [0x00], [0x04], M [0x4D], Q [0x51], T [0x54], T [0x54],
05:19:33.765 -> [0x04], [0xC2], [0x00], [0x04], [0x00], * [0x2A], i [0x69], o [0x6F],
05:19:33.765 -> - [0x2D], w [0x77], i [0x69], p [0x70], p [0x70], e [0x65], r [0x72], - [0x2D],
05:19:33.765 -> a [0x61], d [0x64], a [0x61], f [0x66], r [0x72], u [0x75], i [0x69], t [0x74],
05:19:33.765 -> - [0x2D], f [0x66], u [0x75], n [0x6E], h [0x68], o [0x6F], u [0x75], s [0x73],
05:19:33.765 -> e [0x65], - [0x2D], e [0x65], s [0x73], p [0x70], 3 [0x33], 2 [0x32], s [0x73],
05:19:33.765 -> 2 [0x32], 0 [0x30], 6 [0x36], 1 [0x31], 9 [0x39], 6 [0x36], 0 [0x30], 9 [0x39],
05:19:33.765 -> [0x00], [0x07], S [0x53], a [0x61], n [0x6E], d [0x64], P [0x50], i [0x69],
05:19:33.765 -> g [0x67], [0x00], [0x20], c [0x63], 4 [0x34], 4 [0x34], 3 [0x33], b [0x62],
05:19:33.765 -> 1 [0x31], c [0x63], 7 [0x37], 8 [0x38], c [0x63], 9 [0x39], 3 [0x33], 4 [0x34],
05:19:33.765 -> 4 [0x34], 5 [0x35], 6 [0x36], a [0x61], f [0x66], a [0x61], 3 [0x33], 3 [0x33],
05:19:33.765 -> 6 [0x36], 0 [0x30], b [0x62], 3 [0x33], f [0x66], c [0x63], d [0x64], 6 [0x36],
05:19:33.765 -> e [0x65], e [0x65], d [0x64],
05:19:33.834 -> Client sendPacket returned: 99
05:19:33.834 -> Read data: [0x20],
05:19:33.834 -> Packet Type: [0x20],
05:19:33.834 -> Read data: [0x02],
05:19:33.834 -> Packet Length: 2
05:19:33.834 -> Read data: [0x00], [0x00],
05:19:33.834 -> MQTT subscription packet:
05:19:33.834 -> [0x82], N [0x4E], [0x00], [0x00], [0x00], I [0x49], S [0x53], a [0x61],
05:19:33.834 -> n [0x6E], d [0x64], P [0x50], i [0x69], g [0x67], / [0x2F], w [0x77], p [0x70],
05:19:33.834 -> r [0x72], s [0x73], n [0x6E], p [0x70], r [0x72], / [0x2F], i [0x69], o [0x6F],
05:19:33.834 -> - [0x2D], w [0x77], i [0x69], p [0x70], p [0x70], e [0x65], r [0x72], - [0x2D],
05:19:33.834 -> a [0x61], d [0x64], a [0x61], f [0x66], r [0x72], u [0x75], i [0x69], t [0x74],
05:19:33.834 -> - [0x2D], f [0x66], u [0x75], n [0x6E], h [0x68], o [0x6F], u [0x75], s [0x73],
05:19:33.834 -> e [0x65], - [0x2D], e [0x65], s [0x73], p [0x70], 3 [0x33], 2 [0x32], s [0x73],
05:19:33.834 -> 2 [0x32], 0 [0x30], 6 [0x36], 1 [0x31], 9 [0x39], 6 [0x36], 0 [0x30], 9 [0x39],
05:19:33.834 -> / [0x2F], s [0x73], i [0x69], g [0x67], n [0x6E], a [0x61], l [0x6C], s [0x73],
05:19:33.834 -> / [0x2F], b [0x62], r [0x72], o [0x6F], k [0x6B], e [0x65], r [0x72], [0x01],
05:19:33.834 ->
05:19:34.365 -> Client sendPacket returned: 80
05:19:34.365 -> MQTT subscription packet:
05:19:34.365 -> [0x82], N [0x4E], [0x00], [0x01], [0x00], I [0x49], S [0x53], a [0x61],
05:19:34.365 -> n [0x6E], d [0x64], P [0x50], i [0x69], g [0x67], / [0x2F], w [0x77], p [0x70],
05:19:34.365 -> r [0x72], s [0x73], n [0x6E], p [0x70], r [0x72], / [0x2F], i [0x69], o [0x6F],
05:19:34.365 -> - [0x2D], w [0x77], i [0x69], p [0x70], p [0x70], e [0x65], r [0x72], - [0x2D],
05:19:34.365 -> a [0x61], d [0x64], a [0x61], f [0x66], r [0x72], u [0x75], i [0x69], t [0x74],
05:19:34.365 -> - [0x2D], f [0x66], u [0x75], n [0x6E], h [0x68], o [0x6F], u [0x75], s [0x73],
05:19:34.365 -> e [0x65], - [0x2D], e [0x65], s [0x73], p [0x70], 3 [0x33], 2 [0x32], s [0x73],
05:19:34.365 -> 2 [0x32], 0 [0x30], 6 [0x36], 1 [0x31], 9 [0x39], 6 [0x36], 0 [0x30], 9 [0x39],
05:19:34.365 -> / [0x2F], s [0x73], i [0x69], g [0x67], n [0x6E], a [0x61], l [0x6C], s [0x73],
05:19:34.365 -> / [0x2F], b [0x62], r [0x72], o [0x6F], k [0x6B], e [0x65], r [0x72], [0x01],
05:19:34.365 ->
05:19:34.439 -> Client sendPacket returned: 80
05:19:34.439 -> Read data: [0x90],
05:19:34.439 -> Packet Type: [0x90],
05:19:34.439 -> Read data: [0x03],
05:19:34.439 -> Packet Length: 3
05:19:34.439 -> Read data: [0x00], [0x01], [0x01],
05:19:34.439 -> MQTT subscription packet:
05:19:34.439 -> [0x82], R [0x52], [0x00], [0x02], [0x00], M [0x4D], S [0x53], a [0x61],
05:19:34.439 -> n [0x6E], d [0x64], P [0x50], i [0x69], g [0x67], / [0x2F], w [0x77], p [0x70],
05:19:34.439 -> r [0x72], s [0x73], n [0x6E], p [0x70], r [0x72], / [0x2F], i [0x69], o [0x6F],
05:19:34.439 -> - [0x2D], w [0x77], i [0x69], p [0x70], p [0x70], e [0x65], r [0x72], - [0x2D],
05:19:34.439 -> a [0x61], d [0x64], a [0x61], f [0x66], r [0x72], u [0x75], i [0x69], t [0x74],
05:19:34.439 -> - [0x2D], f [0x66], u [0x75], n [0x6E], h [0x68], o [0x6F], u [0x75], s [0x73],
05:19:34.439 -> e [0x65], - [0x2D], e [0x65], s [0x73], p [0x70], 3 [0x33], 2 [0x32], s [0x73],
05:19:34.439 -> 2 [0x32], 0 [0x30], 6 [0x36], 1 [0x31], 9 [0x39], 6 [0x36], 0 [0x30], 9 [0x39],
05:19:34.439 -> / [0x2F], i [0x69], n [0x6E], f [0x66], o [0x6F], / [0x2F], s [0x73], t [0x74],
05:19:34.439 -> a [0x61], t [0x74], u [0x75], s [0x73], / [0x2F], b [0x62], r [0x72], o [0x6F],
05:19:34.439 -> k [0x6B], e [0x65], r [0x72], [0x01],
05:19:34.513 -> Client sendPacket returned: 84
05:19:34.513 -> Read data: [0x90],
05:19:34.513 -> Packet Type: [0x90],
05:19:34.513 -> Read data: [0x03],
05:19:34.513 -> Packet Length: 3
05:19:34.513 -> Read data: [0x00], [0x02], [0x01],
05:19:34.513 -> MQTT subscription packet:
05:19:34.513 -> [0x82], [0x13], [0x00], [0x03], [0x00], [0x0E], S [0x53], a [0x61],
05:19:34.513 -> n [0x6E], d [0x64], P [0x50], i [0x69], g [0x67], / [0x2F], e [0x65], r [0x72],
05:19:34.513 -> r [0x72], o [0x6F], r [0x72], s [0x73], [0x00],
05:19:34.621 -> Client sendPacket returned: 21
05:19:34.621 -> Read data: [0x90],
05:19:34.621 -> Packet Type: [0x90],
05:19:34.621 -> Read data: [0x03],
05:19:34.621 -> Packet Length: 3
05:19:34.621 -> Read data: [0x00], [0x03], [0x00],
05:19:34.621 -> MQTT subscription packet:
05:19:34.621 -> [0x82], [0x15], [0x00], [0x04], [0x00], [0x10], S [0x53], a [0x61],
05:19:34.621 -> n [0x6E], d [0x64], P [0x50], i [0x69], g [0x67], / [0x2F], t [0x74], h [0x68],
05:19:34.621 -> r [0x72], o [0x6F], t [0x74], t [0x74], l [0x6C], e [0x65], [0x00],
05:19:34.694 -> Client sendPacket returned: 23
05:19:34.694 -> Read data: [0x90],
05:19:34.694 -> Packet Type: [0x90],
05:19:34.694 -> Read data: [0x03],
05:19:34.694 -> Packet Length: 3
05:19:34.694 -> Read data: [0x00], [0x04], [0x00],
05:19:34.694 -> Registering hardware with WipperSnapper...
05:19:34.694 -> Registering hardware with IO...
05:19:34.694 -> Encoding registration request...Encoding registration msg...MQTT publish packet:
05:19:34.694 -> 2 [0x32], M [0x4D], [0x00], [0x1B], S [0x53], a [0x61], n [0x6E], d [0x64],
05:19:34.694 -> P [0x50], i [0x69], g [0x67], / [0x2F], w [0x77], p [0x70], r [0x72], s [0x73],
05:19:34.694 -> n [0x6E], p [0x70], r [0x72], / [0x2F], i [0x69], n [0x6E], f [0x66], o [0x6F],
05:19:34.694 -> / [0x2F], s [0x73], t [0x74], a [0x61], t [0x74], u [0x75], s [0x73], [0x00],
05:19:34.694 -> [0x05], [0x0A], [0x19], a [0x61], d [0x64], a [0x61], f [0x66], r [0x72],
05:19:34.694 -> u [0x75], i [0x69], t [0x74], - [0x2D], f [0x66], u [0x75], n [0x6E], h [0x68],
05:19:34.694 -> o [0x6F], u [0x75], s [0x73], e [0x65], - [0x2D], e [0x65], s [0x73], p [0x70],
05:19:34.694 -> 3 [0x33], 2 [0x32], s [0x73], 2 [0x32], [0x10], [0xD9], [0xE8], % [0x25],
05:19:34.694 -> z [0x7A], [0x0D], 1 [0x31], . [0x2E], 0 [0x30], . [0x2E], 0 [0x30], - [0x2D],
05:19:34.694 -> b [0x62], e [0x65], t [0x74], a [0x61], . [0x2E], 1 [0x31], 0 [0x30],
05:19:34.763 -> Client sendPacket returned: 79
05:19:34.763 -> Read data: @ [0x40],
05:19:34.763 -> Packet Type: @ [0x40],
05:19:34.763 -> Read data: [0x02],
05:19:34.763 -> Packet Length: 2
05:19:34.763 -> Read data: [0x00], [0x05],
05:19:34.763 -> Publish QOS1+ reply: @ [0x40], [0x02], [0x00], [0x05],
05:19:34.763 -> Published!
05:19:34.801 -> Polling for registration message response...2
05:19:34.801 -> Polling for registration message response...2
05:19:34.839 -> Polling for registration message response...2
05:19:34.839 -> Polling for registration message response...2
05:19:34.877 -> Polling for registration message response...2
05:19:34.877 -> Polling for registration message response...2
05:19:34.915 -> Polling for registration message response...2
05:19:34.915 -> Polling for registration message response...2
05:19:34.953 -> Polling for registration message response...2
05:19:34.953 -> Polling for registration message response...2
05:19:34.987 -> Polling for registration message response...2
05:19:34.987 -> Polling for registration message response...2
05:19:35.022 -> Polling for registration message response...2
05:19:35.022 -> Polling for registration message response...2
05:19:35.092 -> Polling for registration message response...2
05:19:35.092 -> Polling for registration message response...2
05:19:35.129 -> Polling for registration message response...2
cont for 60 sec
reboot

This time I stared at the board sternly while I powered it on... the results above attest to its effectiveness.

SandPig
 
Posts: 44
Joined: Sun Sep 10, 2017 8:25 am

Re: beta.6 on Funhouse - offline

by brubell on Mon Sep 20, 2021 12:56 pm

Yeah, we're increasing the verbosity of the logs so we can do some protocol-level debugging. Getting closer...

1) Could you take a screenshot of the device page, including the components attached to the device, and upload it here?
2) Could you keep the io.adafruit.com/monitor page open? Does the device stay connected after it publishes the registration message?

brubell
 
Posts: 1520
Joined: Fri Jul 17, 2015 10:33 pm

Re: beta.6 on Funhouse - offline

by SandPig on Mon Sep 20, 2021 7:42 pm

brubell wrote:Yeah, we're increasing the verbosity of the logs so we can do some protocol-level debugging. Getting closer...

1) Could you take a screenshot of the device page, including the components attached to the device, and upload it here?
2) Could you keep the io.adafruit.com/monitor page open? Does the device stay connected after it publishes the registration message?


ScreenShot2021-09-20_43028PM.png
ScreenShot2021-09-20_43028PM.png (681.7 KiB) Viewed 29 times


I have never seen the monitor page show "online" on the funhouse

SandPig
 
Posts: 44
Joined: Sun Sep 10, 2017 8:25 am

Re: beta.6 on Funhouse - offline

by SandPig on Thu Sep 30, 2021 10:09 am

same with beta.11

07:04:44.438 -> Connecting to: io.adafruit.com
07:04:44.438 -> Connect result: 1
07:04:44.438 -> MQTT connect packet:
07:04:44.438 -> [0x10], a [0x61], [0x00], [0x04], M [0x4D], Q [0x51], T [0x54], T [0x54],
07:04:44.438 -> [0x04], [0xC2], [0x00], [0x04], [0x00], * [0x2A], i [0x69], o [0x6F],
07:04:44.438 -> - [0x2D], w [0x77], i [0x69], p [0x70], p [0x70], e [0x65], r [0x72], - [0x2D],
07:04:44.438 -> a [0x61], d [0x64], a [0x61], f [0x66], r [0x72], u [0x75], i [0x69], t [0x74],
07:04:44.438 -> - [0x2D], f [0x66], u [0x75], n [0x6E], h [0x68], o [0x6F], u [0x75], s [0x73],
07:04:44.438 -> e [0x65], - [0x2D], e [0x65], s [0x73], p [0x70], 3 [0x33], 2 [0x32], s [0x73],
07:04:44.438 -> 2 [0x32], 0 [0x30], 6 [0x36], 1 [0x31], 9 [0x39], 6 [0x36], 0 [0x30], 9 [0x39],
07:04:44.438 -> [0x00], [0x07], S [0x53], a [0x61], n [0x6E], d [0x64], P [0x50], i [0x69],
07:04:44.438 -> g [0x67], [0x00], [0x20], c [0x63], 4 [0x34], 4 [0x34], 3 [0x33], b [0x62],
07:04:44.438 -> 1 [0x31], c [0x63], 7 [0x37], 8 [0x38], c [0x63], 9 [0x39], 3 [0x33], 4 [0x34],
07:04:44.438 -> 4 [0x34], 5 [0x35], 6 [0x36], a [0x61], f [0x66], a [0x61], 3 [0x33], 3 [0x33],
07:04:44.438 -> 6 [0x36], 0 [0x30], b [0x62], 3 [0x33], f [0x66], c [0x63], d [0x64], 6 [0x36],
07:04:44.438 -> e [0x65], e [0x65], d [0x64],
07:04:44.438 -> Client sendPacket returned: 99
07:04:44.544 -> Read data: [0x20],
07:04:44.544 -> Packet Type: [0x20],
07:04:44.544 -> Read data: [0x02],
07:04:44.544 -> Packet Length: 2
07:04:44.544 -> Read data: [0x00], [0x00],
07:04:44.544 -> MQTT subscription packet:
07:04:44.544 -> [0x82], N [0x4E], [0x00], [0x00], [0x00], I [0x49], S [0x53], a [0x61],
07:04:44.544 -> n [0x6E], d [0x64], P [0x50], i [0x69], g [0x67], / [0x2F], w [0x77], p [0x70],
07:04:44.544 -> r [0x72], s [0x73], n [0x6E], p [0x70], r [0x72], / [0x2F], i [0x69], o [0x6F],
07:04:44.544 -> - [0x2D], w [0x77], i [0x69], p [0x70], p [0x70], e [0x65], r [0x72], - [0x2D],
07:04:44.544 -> a [0x61], d [0x64], a [0x61], f [0x66], r [0x72], u [0x75], i [0x69], t [0x74],
07:04:44.544 -> - [0x2D], f [0x66], u [0x75], n [0x6E], h [0x68], o [0x6F], u [0x75], s [0x73],
07:04:44.544 -> e [0x65], - [0x2D], e [0x65], s [0x73], p [0x70], 3 [0x33], 2 [0x32], s [0x73],
07:04:44.544 -> 2 [0x32], 0 [0x30], 6 [0x36], 1 [0x31], 9 [0x39], 6 [0x36], 0 [0x30], 9 [0x39],
07:04:44.544 -> / [0x2F], s [0x73], i [0x69], g [0x67], n [0x6E], a [0x61], l [0x6C], s [0x73],
07:04:44.544 -> / [0x2F], b [0x62], r [0x72], o [0x6F], k [0x6B], e [0x65], r [0x72], [0x01],
07:04:45.055 ->
07:04:45.055 -> Client sendPacket returned: 80
07:04:45.055 -> MQTT subscription packet:
07:04:45.055 -> [0x82], N [0x4E], [0x00], [0x01], [0x00], I [0x49], S [0x53], a [0x61],
07:04:45.055 -> n [0x6E], d [0x64], P [0x50], i [0x69], g [0x67], / [0x2F], w [0x77], p [0x70],
07:04:45.055 -> r [0x72], s [0x73], n [0x6E], p [0x70], r [0x72], / [0x2F], i [0x69], o [0x6F],
07:04:45.055 -> - [0x2D], w [0x77], i [0x69], p [0x70], p [0x70], e [0x65], r [0x72], - [0x2D],
07:04:45.055 -> a [0x61], d [0x64], a [0x61], f [0x66], r [0x72], u [0x75], i [0x69], t [0x74],
07:04:45.055 -> - [0x2D], f [0x66], u [0x75], n [0x6E], h [0x68], o [0x6F], u [0x75], s [0x73],
07:04:45.055 -> e [0x65], - [0x2D], e [0x65], s [0x73], p [0x70], 3 [0x33], 2 [0x32], s [0x73],
07:04:45.055 -> 2 [0x32], 0 [0x30], 6 [0x36], 1 [0x31], 9 [0x39], 6 [0x36], 0 [0x30], 9 [0x39],
07:04:45.055 -> / [0x2F], s [0x73], i [0x69], g [0x67], n [0x6E], a [0x61], l [0x6C], s [0x73],
07:04:45.055 -> / [0x2F], b [0x62], r [0x72], o [0x6F], k [0x6B], e [0x65], r [0x72], [0x01],
07:04:45.055 ->
07:04:45.055 -> Client sendPacket returned: 80
07:04:45.117 -> Read data: [0x90],
07:04:45.117 -> Packet Type: [0x90],
07:04:45.117 -> Read data: [0x03],
07:04:45.117 -> Packet Length: 3
07:04:45.117 -> Read data: [0x00], [0x01], [0x01],
07:04:45.117 -> MQTT subscription packet:
07:04:45.117 -> [0x82], R [0x52], [0x00], [0x02], [0x00], M [0x4D], S [0x53], a [0x61],
07:04:45.117 -> n [0x6E], d [0x64], P [0x50], i [0x69], g [0x67], / [0x2F], w [0x77], p [0x70],
07:04:45.117 -> r [0x72], s [0x73], n [0x6E], p [0x70], r [0x72], / [0x2F], i [0x69], o [0x6F],
07:04:45.117 -> - [0x2D], w [0x77], i [0x69], p [0x70], p [0x70], e [0x65], r [0x72], - [0x2D],
07:04:45.117 -> a [0x61], d [0x64], a [0x61], f [0x66], r [0x72], u [0x75], i [0x69], t [0x74],
07:04:45.117 -> - [0x2D], f [0x66], u [0x75], n [0x6E], h [0x68], o [0x6F], u [0x75], s [0x73],
07:04:45.117 -> e [0x65], - [0x2D], e [0x65], s [0x73], p [0x70], 3 [0x33], 2 [0x32], s [0x73],
07:04:45.117 -> 2 [0x32], 0 [0x30], 6 [0x36], 1 [0x31], 9 [0x39], 6 [0x36], 0 [0x30], 9 [0x39],
07:04:45.117 -> / [0x2F], i [0x69], n [0x6E], f [0x66], o [0x6F], / [0x2F], s [0x73], t [0x74],
07:04:45.117 -> a [0x61], t [0x74], u [0x75], s [0x73], / [0x2F], b [0x62], r [0x72], o [0x6F],
07:04:45.117 -> k [0x6B], e [0x65], r [0x72], [0x01],
07:04:45.205 -> Client sendPacket returned: 84
07:04:45.205 -> Read data: [0x90],
07:04:45.205 -> Packet Type: [0x90],
07:04:45.205 -> Read data: [0x03],
07:04:45.205 -> Packet Length: 3
07:04:45.205 -> Read data: [0x00], [0x02], [0x01],
07:04:45.205 -> MQTT subscription packet:
07:04:45.205 -> [0x82], [0x13], [0x00], [0x03], [0x00], [0x0E], S [0x53], a [0x61],
07:04:45.205 -> n [0x6E], d [0x64], P [0x50], i [0x69], g [0x67], / [0x2F], e [0x65], r [0x72],
07:04:45.205 -> r [0x72], o [0x6F], r [0x72], s [0x73], [0x00],
07:04:45.318 -> Client sendPacket returned: 21
07:04:45.318 -> Read data: [0x90],
07:04:45.318 -> Packet Type: [0x90],
07:04:45.318 -> Read data: [0x03],
07:04:45.318 -> Packet Length: 3
07:04:45.318 -> Read data: [0x00], [0x03], [0x00],
07:04:45.318 -> MQTT subscription packet:
07:04:45.318 -> [0x82], [0x15], [0x00], [0x04], [0x00], [0x10], S [0x53], a [0x61],
07:04:45.318 -> n [0x6E], d [0x64], P [0x50], i [0x69], g [0x67], / [0x2F], t [0x74], h [0x68],
07:04:45.318 -> r [0x72], o [0x6F], t [0x74], t [0x74], l [0x6C], e [0x65], [0x00],
07:04:45.318 -> Client sendPacket returned: 23
07:04:45.394 -> Read data: [0x90],
07:04:45.394 -> Packet Type: [0x90],
07:04:45.394 -> Read data: [0x03],
07:04:45.394 -> Packet Length: 3
07:04:45.394 -> Read data: [0x00], [0x04], [0x00],
07:04:45.394 -> Registering hardware with WipperSnapper...
07:04:45.394 -> Registering hardware with IO...
07:04:45.394 -> Encoding registration request...Encoding registration msg...MQTT publish packet:
07:04:45.394 -> 2 [0x32], M [0x4D], [0x00], [0x1B], S [0x53], a [0x61], n [0x6E], d [0x64],
07:04:45.394 -> P [0x50], i [0x69], g [0x67], / [0x2F], w [0x77], p [0x70], r [0x72], s [0x73],
07:04:45.394 -> n [0x6E], p [0x70], r [0x72], / [0x2F], i [0x69], n [0x6E], f [0x66], o [0x6F],
07:04:45.394 -> / [0x2F], s [0x73], t [0x74], a [0x61], t [0x74], u [0x75], s [0x73], [0x00],
07:04:45.394 -> [0x05], [0x0A], [0x19], a [0x61], d [0x64], a [0x61], f [0x66], r [0x72],
07:04:45.394 -> u [0x75], i [0x69], t [0x74], - [0x2D], f [0x66], u [0x75], n [0x6E], h [0x68],
07:04:45.394 -> o [0x6F], u [0x75], s [0x73], e [0x65], - [0x2D], e [0x65], s [0x73], p [0x70],
07:04:45.394 -> 3 [0x33], 2 [0x32], s [0x73], 2 [0x32], [0x10], [0xD9], [0xE8], % [0x25],
07:04:45.394 -> z [0x7A], [0x0D], 1 [0x31], . [0x2E], 0 [0x30], . [0x2E], 0 [0x30], - [0x2D],
07:04:45.394 -> b [0x62], e [0x65], t [0x74], a [0x61], . [0x2E], 1 [0x31], 1 [0x31],
07:04:45.394 -> Client sendPacket returned: 79
07:04:45.467 -> Publishing across: SandPig/wprsnpr/info/status
07:04:45.467 -> Read data: @ [0x40],
07:04:45.467 -> Packet Type: @ [0x40],
07:04:45.467 -> Read data: [0x02],
07:04:45.467 -> Packet Length: 2
07:04:45.467 -> Read data: [0x00], [0x05],
07:04:45.467 -> Publish QOS1+ reply: @ [0x40], [0x02], [0x00], [0x05],
07:04:45.467 -> Published!
07:04:45.467 -> Polling for registration message response...2
07:04:45.541 -> Polling for registration message response...2
07:04:45.541 -> Polling for registration message response...2
07:04:45.575 -> Polling for registration message response...2
07:04:45.575 -> Polling for registration message response...2
07:04:45.651 -> Polling for registration message response...2
07:04:45.651 -> Polling for registration message response...2
07:04:45.727 -> Polling for registration message response...2
rinse/repeat

Am I the only one experiencing this trouble?
I have another funhouse that i can test with if you think that would be of any value.

SandPig
 
Posts: 44
Joined: Sun Sep 10, 2017 8:25 am

Re: beta.6 on Funhouse - offline

by ksprayberry on Thu Sep 30, 2021 11:15 am

Sandpig
You're not the only one. I have a Funhouse too on Beta 11 and It never shows to be online. When I pull up the serial output, I see the rapid fire polling request, but i'm not seeing the other information you're showing , the MQTT information and the packets and what not. I keep wondering if I'm just doing something wrong. I've checked and rechecked my IO key and everything. I have some other M5stack products posting to the Adafruit IO on a regular basis with the same IO key and username, so I'm fairly certain it's not that. I have put my device right at the wifi router to check, it goes through all the sequence on the pixels from Cyan to Blue to Amber, but never shows online. I keep wondering if this is isolated to my board and others are working fine. I see that they've opened it up more and have begun to promote it, so I can't help but now wonder if my results are isolated. Looking forward to playing around with this. I like the idea behind it all.

ksprayberry
 
Posts: 18
Joined: Tue Feb 05, 2019 8:52 pm

Re: beta.6 on Funhouse - offline

by brubell on Fri Oct 01, 2021 9:45 am

ksprayberry wrote:Sandpig
You're not the only one. I have a Funhouse too on Beta 11 and It never shows to be online. When I pull up the serial output, I see the rapid fire polling request, but i'm not seeing the other information you're showing , the MQTT information and the packets and what not. I keep wondering if I'm just doing something wrong. I've checked and rechecked my IO key and everything. I have some other M5stack products posting to the Adafruit IO on a regular basis with the same IO key and username, so I'm fairly certain it's not that. I have put my device right at the wifi router to check, it goes through all the sequence on the pixels from Cyan to Blue to Amber, but never shows online. I keep wondering if this is isolated to my board and others are working fine. I see that they've opened it up more and have begun to promote it, so I can't help but now wonder if my results are isolated. Looking forward to playing around with this. I like the idea behind it all.


I'm merging the latest version of ESP32 Arduino 2.0.0 (https://github.com/espressif/arduino-es ... /tag/2.0.0), based on the latest development version of ESP-IDF, into Beta.12. WipperSnapper on ESP32-S2 was previously built with the 2.0.0 alpha 1 so we could retain TinyUSB support. We recently (https://github.com/adafruit/Adafruit_Ti ... o/pull/126) added support in TinyUSB compatibility for the latest 2.0.0 release of ESP32 and can now track Espressif's latest releases.

My hope is that it'll fix some of these intermittent WiFi/connection issues as there have been a few releases between alpha1 and the latest stable release. We've opened it up more (still in Beta) so we're able to gather more data to fix these issues.

brubell
 
Posts: 1520
Joined: Fri Jul 17, 2015 10:33 pm

Re: beta.6 on Funhouse - offline

by SandPig on Fri Oct 01, 2021 1:43 pm

Thank you for the sanity check, K. I'm glad/sorry to hear that you're running into the same issue and I'm not an isolated case.
Very odd that you're not getting the increased logging, though. What are you using to capture the serial output?

Brent, I hooked up the funhouse to my Verizon hotspot just to rule out any possible issue with router/modem/provider and got the exact same results.
if I can't be directly helpful, I can at least try to eliminate some variables!
This evening, I will test again while having a beer. I'm pretty sure that not having a refreshing beverage while testing could be causing the issue...

SandPig
 
Posts: 44
Joined: Sun Sep 10, 2017 8:25 am

Please be positive and constructive with your questions and comments.