0

deserlize,Json error
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.

deserlize,Json error

by chuck.untulis on Mon Dec 06, 2021 5:20 am

Wippersnapper tells me that I have v1.0.0-beta.8 installed on my Funhouse.

I tried to drag wippersnapper.funhouse_tinyusb.1.0.0-beta.16 onto my CIRCUITPY device but I received a message that there was not enough space. The four lights keep flashing green 4 times. It does not tell me what I need to do to fix the space problem.

There is a wipper_boot_out file on the device that contains the following:

1.0.0-beta.16
ERROR: deserializeJson() failed with code
InvalidInput

what does this mean and how do I fix it?

secrets.JSON and secrets.py seem to have the correct information.

chuck.untulis
 
Posts: 104
Joined: Mon Jun 20, 2011 11:54 pm

Re: deserlize,Json error

by brubell on Mon Dec 06, 2021 11:52 am

Let's fix one thing at a time, first the space issue...

Wippersnapper tells me that I have v1.0.0-beta.8 installed on my Funhouse.

I tried to drag wippersnapper.funhouse_tinyusb.1.0.0-beta.16 onto my CIRCUITPY device but I received a message that there was not enough space.


The reason it's running out of space is that it is currently running the CircuitPython application, instead of the bootloader.

You will need to drag the beta.16 UF2 onto the HOUSEBOOT volume (NOT the CIRCUITPY volume) which can be accessed by putting your FunHouse into its bootloader mode. There are instructions on how to do this here: https://learn.adafruit.com/adafruit-fun ... ep-3089490

Let me know if you still experience an error.

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

Re: deserlize,Json error

by chuck.untulis on Mon Dec 06, 2021 12:20 pm

I will try that.

I did not realize that there are two or more volumes on the device. How can I see this volume information. Is there a diagram someplace that shows the layout on the device.

This should be mentioned in the documentation.

chuck.untulis
 
Posts: 104
Joined: Mon Jun 20, 2011 11:54 pm

Re: deserlize,Json error

by chuck.untulis on Tue Dec 07, 2021 12:55 am

That did not work and I ended up with the Funhouse sitting here flashing its lights green four times followed by a pause and then more flashing in groups of four. How do I get out of this blinking state? Reset just pauses it for a second, exits the File Browser and then restarts the browser, blinks blue and starts blinking green. Turning the board off and then back on just continues the blinking.

It is shown as CIRCUITPY. 
Along the way, I had to add the lib directory and the code.py file trying to get it to work with no luck. I think I am following the directions but occasionally I get to a point where the documentation says to do something but it does not match what I see.

I registered my board a long time ago - how would I delete it?
The secret files were working at one time and have not been changed - should I rebuild them from scratch?

The wipper_boot_out should be mentioned in https://learn.adafruit.com/quickstart-a ... esp32-s2-2.

I looked in the wipper_boot_out file and it shows 1.0.0-beta.16 so it looks like Wippersnapper is loaded on the board but it just keeps flashing across resets and power cycles. How do I get out of this state and connected to Adafruit IO.

CIRCUITPY has 809,984 bytes of free space

chuck.untulis
 
Posts: 104
Joined: Mon Jun 20, 2011 11:54 pm

Re: deserlize,Json error

by chuck.untulis on Tue Dec 07, 2021 1:52 am

Now all of a sudden I noticed that the File explorer shows the device as WIPPER?

I noticed that there were only a few files shown. I added lib files and some code files including code.py file. I power cycled it but the screen was blank but the led above the on/off switch flashed a number of times. I reached to cycle the on/off switch but before I cycled it the two leds at the top left of the device flashed a couple of times (I think blue), the led above the on/off switch is now a constant green and the lights at the top are now flashing 4 times yellow, pause and then flash again.

I hit reset and it rebooted and is back into flashing mode and showing all the files on the WIPPER drive. Adafruit IO still shows it as offline running v1.0.0-beta.8 with an X. Recycling the power ends up the same behavior

Double clicking reset turns off WIPPER and reboots as HOUSEBOOT.

Still stuck.

In the past as my fingers neared the lower right corner of the card it would do a reset or flash various lights and then reboot.

chuck.untulis
 
Posts: 104
Joined: Mon Jun 20, 2011 11:54 pm

Re: deserlize,Json error

by brubell on Wed Dec 08, 2021 12:52 pm

I registered my board a long time ago - how would I delete it?


It should be on the device interface page,
IO_-_WipperSnapper_.png
IO_-_WipperSnapper_.png (251.91 KiB) Viewed 234 times


), the led above the on/off switch is now a constant green and the lights at the top are now flashing 4 times yellow, pause and then flash again.


On the WIPPER drive, please edit the secrets.py with your network and Adafruit IO credentials, they may have been overwritten by flashing/re-flashing

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

Re: deserlize,Json error

by chuck.untulis on Wed Dec 08, 2021 2:55 pm

Replaced network ssid, network password, aio_username and aio_key with fresh typed values. Still in the flashing state after reset then power cycle.

chuck.untulis
 
Posts: 104
Joined: Mon Jun 20, 2011 11:54 pm

Re: deserlize,Json error

by chuck.untulis on Wed Dec 08, 2021 5:39 pm

Renaming secrets.py and code.py out of the way did not affect the flashing behavior.

Deleting all the files at the top level and power cycling did not change the flashing behavior. A secrets.JSON template file was created and wipper_boot_out says to edit it and reset the board.

I edited the secrets.JSON file (which is in a different format than previously) , hit reset as suggested in the wipper_boot_out file and now the board flashed a different light pattern (white, pink, blue. yellow, green, green - colors supplied by my wife since I am color limited) and the blank display is sitting here (no flashing lights), led under the display is red and no error messages on the display.

Where are the various light color significances documented? For we color vision deficency or CVD people (1/12 men and 1/200 women, changing the light pattern as well as the color would be very helpful - for instance blue and a single light on the left, pink and the second light on the left, blue and the single light at the apex...

The wipper_boot_out file shows it is is running beta.16.

Adding a code.py containing print("hello") and resetting shows same light sequence and no output on display.

Adding a code.py containing the Internet example code, populating the lib folder https://www.screencast.com/t/xz0Lgrr2yDS and resetting shows same light sequence and no output on display.

Neither save in Mu or Visual Studio triggers a reset of the device.

After checking the app on the Android https://io.adafruit.com/chuck.untulis/w ... funhouse... shows the device Online and running beta.16. I can turn the LED off and on from my Android phone. Pushing the buttons is reflected on the Android as well as the state of the PIR.

My working hypothesis is that all my problems are related to the change of format of the secrets.JSON file. After changing the format most things now work. Was the change in format documented and if so where? While changing things and requiring users to keep checking for the changes, sending out specific messages to detail these changes would be much appreciated. Did I miss signing up for such a list?

My new problem is that nothing shows up on the Funhouse display either from simple print statements, the internet test code or the full code that shows touch sensor status, button status , PIR status... on the Funhouse display? Am I missing a library or has the library changed underneath me - see library list above? I will go back and make sure my libraries are up to date.

It was specified above to change secrets.py. My running device does not have a secrets.py file only a secrets.JSON file. I changed the format and it seems to be mostly running now.

chuck.untulis
 
Posts: 104
Joined: Mon Jun 20, 2011 11:54 pm

Re: deserlize,Json error

by chuck.untulis on Fri Dec 10, 2021 3:24 am

I found LED color WipperSnapper RGB Status Light.

I still can't get the display to show any information. I think I have put the latest libraries in the lib directory on the WIPPER drive.

chuck.untulis
 
Posts: 104
Joined: Mon Jun 20, 2011 11:54 pm

Re: deserlize,Json error

by chuck.untulis on Fri Dec 10, 2021 10:13 pm

I still have a blank display on the Funhouse. After updating the libraries, I tried changing the code in the code.py file and restarting the device. No matter what I do including renaming code.py to something else the display remains blank and the the buttons on the device change the state of https://io.adafruit.com/chuck.untulis/wippersnapper - turning the LED on and off, showing a button is pressed when I do so. I have tested it on two Windows 10 systems and https://io.adafruit.com/chuck.untulis/wippersnapper shows it running v1.0.0-beta.16 followed by a checkmark.

How can this be??? Is there another copy of the code running on the device some place??? How do I get rid of it?

I2C scan finds two internal and one external device (sparkfun MUX) but still nothing visible on the Funhouse display.

Button 1 on the device is flakey - if I touch it without pressing, on the https://io.adafruit.com/chuck.untulis/wippersnapper it quickly toggles between Pressed and Unpressed. Pressing it shows Pressed and sometimes it says Pressed until I Reset the device.

chuck.untulis
 
Posts: 104
Joined: Mon Jun 20, 2011 11:54 pm

Re: deserlize,Json error

by chuck.untulis on Sat Dec 11, 2021 4:09 am

I am running v1.0,0-beta.16.

Since I made multiple changes to code.py (using Mu, Notepad or VScode) and still nothing appears on the display - neither an error message nor any output - I postulated that the code I was seeing at the top level of WIPPER was not being executed but another set of code was running.

I did some more probing and changed the secrets.py file and the io.adafruit wippersnapper interface continued to change when I pressed buttons on the Funhouse and the LED on the Funhouse changed when I depressed the button on the wippersnapper interface on my Android phone.

However when I renamed the secrets.JSON file to secrets1.JSON and did a reset, the Funhouse hung and went into the periodic blinking of the dotstar leds. It also created a secrets.JSON template file with no data filled in. I then renamed the file back to secrets.JSON populated it with io information and the network information, saved it, pressed reset and the system came up.

My conclusion is that secrets.py does not serve a purpose and the documentation stating that it is necessary is wrong or hasn't been updated saying the secrets.JSON should be used instead.

My next postulation was that the change to version 16 broke my device and I will try going back to a previous version to see if it will work again - can't find version 15 so I can't try to go back

I still have not been able to get Arduino setup on either machine to give me the option of pointing to the funhouse board.

chuck.untulis
 
Posts: 104
Joined: Mon Jun 20, 2011 11:54 pm

Re: deserlize,Json error

by chuck.untulis on Sat Dec 11, 2021 4:45 am

Finally have Arduino configured so I can see Funhouse.

chuck.untulis
 
Posts: 104
Joined: Mon Jun 20, 2011 11:54 pm

Re: deserlize,Json error

by chuck.untulis on Sat Dec 11, 2021 5:13 am

A lot of data is streaming on the Serial Monitor and I do not see any error messages.

chuck.untulis
 
Posts: 104
Joined: Mon Jun 20, 2011 11:54 pm

Re: deserlize,Json error

by brubell on Mon Dec 13, 2021 11:23 am

chuck.untulis wrote:A lot of data is streaming on the Serial Monitor and I do not see any error messages.

Could you please copy and paste the data from the serial monitor, here?

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

Re: deserlize,Json error

by chuck.untulis on Mon Dec 13, 2021 2:19 pm

Here is just some of the traffic. The Wippersnapper app is working. The screen is blank. I understand that is what is to be expected. The code.py file is not looked at while in snap(Wippersnapper) mode. Are there any plans to allow a user to quickly switch between snap and non-snap mode so that I could put programs into code.py and have them executed without dragging uf2 files onto the BOOT drive.

Executing state-based event on D16
Encoding pinEvent...Encoded!
Publishing pinEvent...MQTT publish packet:
2 [0x32], ^ [0x5E], [0x00], P [0x50], c [0x63], h [0x68], u [0x75], c [0x63],
k [0x6B], . [0x2E], u [0x75], n [0x6E], t [0x74], u [0x75], l [0x6C], i [0x69],
s [0x73], / [0x2F], w [0x77], p [0x70], r [0x72], s [0x73], n [0x6E], p [0x70],
r [0x72], / [0x2F], i [0x69], o [0x6F], - [0x2D], w [0x77], i [0x69], p [0x70],
p [0x70], e [0x65], r [0x72], - [0x2D], a [0x61], d [0x64], a [0x61], f [0x66],
r [0x72], u [0x75], i [0x69], t [0x74], - [0x2D], f [0x66], u [0x75], n [0x6E],
h [0x68], o [0x6F], u [0x75], s [0x73], e [0x65], - [0x2D], e [0x65], s [0x73],
p [0x70], 3 [0x33], 2 [0x32], s [0x73], 2 [0x32], 1 [0x31], 9 [0x39], 0 [0x30],
2 [0x32], 1 [0x31], 8 [0x38], 0 [0x30], 5 [0x35], / [0x2F], s [0x73], i [0x69],
g [0x67], n [0x6E], a [0x61], l [0x6C], s [0x73], / [0x2F], d [0x64], e [0x65],
v [0x76], i [0x69], c [0x63], e [0x65], [0x00], [0x13], z [0x7A], [0x08],
[0x0A], [0x03], D [0x44], 1 [0x31], 6 [0x36], [0x12], [0x01], 1 [0x31],

Client sendPacket returned: 96
Publishing across: chuck.untulis/wprsnpr/io-wipper-adafruit-funhouse-esp32s219021805/signals/device
Read data: @ [0x40],
Packet Type: @ [0x40],
Read data: [0x02],
Packet Length: 2
Read data: [0x00], [0x13],
Publish QOS1+ reply: @ [0x40], [0x02], [0x00], [0x13],
Published!
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
Executing state-based event on D5
Encoding pinEvent...Encoded!
Publishing pinEvent...MQTT publish packet:
2 [0x32], ] [0x5D], [0x00], P [0x50], c [0x63], h [0x68], u [0x75], c [0x63],
k [0x6B], . [0x2E], u [0x75], n [0x6E], t [0x74], u [0x75], l [0x6C], i [0x69],
s [0x73], / [0x2F], w [0x77], p [0x70], r [0x72], s [0x73], n [0x6E], p [0x70],
r [0x72], / [0x2F], i [0x69], o [0x6F], - [0x2D], w [0x77], i [0x69], p [0x70],
p [0x70], e [0x65], r [0x72], - [0x2D], a [0x61], d [0x64], a [0x61], f [0x66],
r [0x72], u [0x75], i [0x69], t [0x74], - [0x2D], f [0x66], u [0x75], n [0x6E],
h [0x68], o [0x6F], u [0x75], s [0x73], e [0x65], - [0x2D], e [0x65], s [0x73],
p [0x70], 3 [0x33], 2 [0x32], s [0x73], 2 [0x32], 1 [0x31], 9 [0x39], 0 [0x30],
2 [0x32], 1 [0x31], 8 [0x38], 0 [0x30], 5 [0x35], / [0x2F], s [0x73], i [0x69],
g [0x67], n [0x6E], a [0x61], l [0x6C], s [0x73], / [0x2F], d [0x64], e [0x65],
v [0x76], i [0x69], c [0x63], e [0x65], [0x00], [0x14], z [0x7A], [0x07],
[0x0A], [0x02], D [0x44], 5 [0x35], [0x12], [0x01], 1 [0x31],
Client sendPacket returned: 95
Publishing across: chuck.untulis/wprsnpr/io-wipper-adafruit-funhouse-esp32s219021805/signals/device
Read data: @ [0x40],
Packet Type: @ [0x40],
Read data: [0x02],
Packet Length: 2
Read data: [0x00], [0x14],
Publish QOS1+ reply: @ [0x40], [0x02], [0x00], [0x14],
Published!
Executing state-based event on D5
Encoding pinEvent...Encoded!
Publishing pinEvent...MQTT publish packet:
2 [0x32], ] [0x5D], [0x00], P [0x50], c [0x63], h [0x68], u [0x75], c [0x63],
k [0x6B], . [0x2E], u [0x75], n [0x6E], t [0x74], u [0x75], l [0x6C], i [0x69],
s [0x73], / [0x2F], w [0x77], p [0x70], r [0x72], s [0x73], n [0x6E], p [0x70],
r [0x72], / [0x2F], i [0x69], o [0x6F], - [0x2D], w [0x77], i [0x69], p [0x70],
p [0x70], e [0x65], r [0x72], - [0x2D], a [0x61], d [0x64], a [0x61], f [0x66],
r [0x72], u [0x75], i [0x69], t [0x74], - [0x2D], f [0x66], u [0x75], n [0x6E],
h [0x68], o [0x6F], u [0x75], s [0x73], e [0x65], - [0x2D], e [0x65], s [0x73],
p [0x70], 3 [0x33], 2 [0x32], s [0x73], 2 [0x32], 1 [0x31], 9 [0x39], 0 [0x30],
2 [0x32], 1 [0x31], 8 [0x38], 0 [0x30], 5 [0x35], / [0x2F], s [0x73], i [0x69],
g [0x67], n [0x6E], a [0x61], l [0x6C], s [0x73], / [0x2F], d [0x64], e [0x65],
v [0x76], i [0x69], c [0x63], e [0x65], [0x00], [0x15], z [0x7A], [0x07],
[0x0A], [0x02], D [0x44], 5 [0x35], [0x12], [0x01], 0 [0x30],
Client sendPacket returned: 95
Publishing across: chuck.untulis/wprsnpr/io-wipper-adafruit-funhouse-esp32s219021805/signals/device
Read data: @ [0x40],
Packet Type: @ [0x40],
Read data: [0x02],
Packet Length: 2
Read data: [0x00], [0x15],
Publish QOS1+ reply: @ [0x40], [0x02], [0x00], [0x15],
Published!
Executing state-based event on D5
Encoding pinEvent...Encoded!
Publishing pinEvent...MQTT publish packet:
2 [0x32], ] [0x5D], [0x00], P [0x50], c [0x63], h [0x68], u [0x75], c [0x63],
k [0x6B], . [0x2E], u [0x75], n [0x6E], t [0x74], u [0x75], l [0x6C], i [0x69],
s [0x73], / [0x2F], w [0x77], p [0x70], r [0x72], s [0x73], n [0x6E], p [0x70],
r [0x72], / [0x2F], i [0x69], o [0x6F], - [0x2D], w [0x77], i [0x69], p [0x70],
p [0x70], e [0x65], r [0x72], - [0x2D], a [0x61], d [0x64], a [0x61], f [0x66],
r [0x72], u [0x75], i [0x69], t [0x74], - [0x2D], f [0x66], u [0x75], n [0x6E],
h [0x68], o [0x6F], u [0x75], s [0x73], e [0x65], - [0x2D], e [0x65], s [0x73],
p [0x70], 3 [0x33], 2 [0x32], s [0x73], 2 [0x32], 1 [0x31], 9 [0x39], 0 [0x30],
2 [0x32], 1 [0x31], 8 [0x38], 0 [0x30], 5 [0x35], / [0x2F], s [0x73], i [0x69],
g [0x67], n [0x6E], a [0x61], l [0x6C], s [0x73], / [0x2F], d [0x64], e [0x65],
v [0x76], i [0x69], c [0x63], e [0x65], [0x00], [0x16], z [0x7A], [0x07],
[0x0A], [0x02], D [0x44], 5 [0x35], [0x12], [0x01], 1 [0x31],
Client sendPacket returned: 95
Publishing across: chuck.untulis/wprsnpr/io-wipper-adafruit-funhouse-esp32s219021805/signals/device
Read data: @ [0x40],
Packet Type: @ [0x40],
Read data: [0x02],
Packet Length: 2
Read data: [0x00], [0x16],
Publish QOS1+ reply: @ [0x40], [0x02], [0x00], [0x16],
Published!
Executing state-based event on D5
Encoding pinEvent...Encoded!
Publishing pinEvent...MQTT publish packet:
2 [0x32], ] [0x5D], [0x00], P [0x50], c [0x63], h [0x68], u [0x75], c [0x63],
k [0x6B], . [0x2E], u [0x75], n [0x6E], t [0x74], u [0x75], l [0x6C], i [0x69],
s [0x73], / [0x2F], w [0x77], p [0x70], r [0x72], s [0x73], n [0x6E], p [0x70],
r [0x72], / [0x2F], i [0x69], o [0x6F], - [0x2D], w [0x77], i [0x69], p [0x70],
p [0x70], e [0x65], r [0x72], - [0x2D], a [0x61], d [0x64], a [0x61], f [0x66],
r [0x72], u [0x75], i [0x69], t [0x74], - [0x2D], f [0x66], u [0x75], n [0x6E],
h [0x68], o [0x6F], u [0x75], s [0x73], e [0x65], - [0x2D], e [0x65], s [0x73],
p [0x70], 3 [0x33], 2 [0x32], s [0x73], 2 [0x32], 1 [0x31], 9 [0x39], 0 [0x30],
2 [0x32], 1 [0x31], 8 [0x38], 0 [0x30], 5 [0x35], / [0x2F], s [0x73], i [0x69],
g [0x67], n [0x6E], a [0x61], l [0x6C], s [0x73], / [0x2F], d [0x64], e [0x65],
v [0x76], i [0x69], c [0x63], e [0x65], [0x00], [0x17], z [0x7A], [0x07],
[0x0A], [0x02], D [0x44], 5 [0x35], [0x12], [0x01], 0 [0x30],
Client sendPacket returned: 95
Publishing across: chuck.untulis/wprsnpr/io-wipper-adafruit-funhouse-esp32s219021805/signals/device
Read data: @ [0x40],
Packet Type: @ [0x40],
Read data: [0x02],
Packet Length: 2
Read data: [0x00], [0x17],
Publish QOS1+ reply: @ [0x40], [0x02], [0x00], [0x17],
Published!
Executing state-based event on D5
Encoding pinEvent...Encoded!
Publishing pinEvent...MQTT publish packet:
2 [0x32], ] [0x5D], [0x00], P [0x50], c [0x63], h [0x68], u [0x75], c [0x63],
k [0x6B], . [0x2E], u [0x75], n [0x6E], t [0x74], u [0x75], l [0x6C], i [0x69],
s [0x73], / [0x2F], w [0x77], p [0x70], r [0x72], s [0x73], n [0x6E], p [0x70],
r [0x72], / [0x2F], i [0x69], o [0x6F], - [0x2D], w [0x77], i [0x69], p [0x70],
p [0x70], e [0x65], r [0x72], - [0x2D], a [0x61], d [0x64], a [0x61], f [0x66],
r [0x72], u [0x75], i [0x69], t [0x74], - [0x2D], f [0x66], u [0x75], n [0x6E],
h [0x68], o [0x6F], u [0x75], s [0x73], e [0x65], - [0x2D], e [0x65], s [0x73],
p [0x70], 3 [0x33], 2 [0x32], s [0x73], 2 [0x32], 1 [0x31], 9 [0x39], 0 [0x30],
2 [0x32], 1 [0x31], 8 [0x38], 0 [0x30], 5 [0x35], / [0x2F], s [0x73], i [0x69],
g [0x67], n [0x6E], a [0x61], l [0x6C], s [0x73], / [0x2F], d [0x64], e [0x65],
v [0x76], i [0x69], c [0x63], e [0x65], [0x00], [0x18], z [0x7A], [0x07],
[0x0A], [0x02], D [0x44], 5 [0x35], [0x12], [0x01], 1 [0x31],
Client sendPacket returned: 95
Publishing across: chuck.untulis/wprsnpr/io-wipper-adafruit-funhouse-esp32s219021805/signals/device
Read data: @ [0x40],
Packet Type: @ [0x40],
Read data: [0x02],
Packet Length: 2
Read data: [0x00], [0x18],
Publish QOS1+ reply: @ [0x40], [0x02], [0x00], [0x18],
Published!
Executing state-based event on D5
Encoding pinEvent...Encoded!
Publishing pinEvent...MQTT publish packet:
2 [0x32], ] [0x5D], [0x00], P [0x50], c [0x63], h [0x68], u [0x75], c [0x63],
k [0x6B], . [0x2E], u [0x75], n [0x6E], t [0x74], u [0x75], l [0x6C], i [0x69],
s [0x73], / [0x2F], w [0x77], p [0x70], r [0x72], s [0x73], n [0x6E], p [0x70],
r [0x72], / [0x2F], i [0x69], o [0x6F], - [0x2D], w [0x77], i [0x69], p [0x70],
p [0x70], e [0x65], r [0x72], - [0x2D], a [0x61], d [0x64], a [0x61], f [0x66],
r [0x72], u [0x75], i [0x69], t [0x74], - [0x2D], f [0x66], u [0x75], n [0x6E],
h [0x68], o [0x6F], u [0x75], s [0x73], e [0x65], - [0x2D], e [0x65], s [0x73],
p [0x70], 3 [0x33], 2 [0x32], s [0x73], 2 [0x32], 1 [0x31], 9 [0x39], 0 [0x30],
2 [0x32], 1 [0x31], 8 [0x38], 0 [0x30], 5 [0x35], / [0x2F], s [0x73], i [0x69],
g [0x67], n [0x6E], a [0x61], l [0x6C], s [0x73], / [0x2F], d [0x64], e [0x65],
v [0x76], i [0x69], c [0x63], e [0x65], [0x00], [0x19], z [0x7A], [0x07],
[0x0A], [0x02], D [0x44], 5 [0x35], [0x12], [0x01], 0 [0x30],
Client sendPacket returned: 95
Publishing across: chuck.untulis/wprsnpr/io-wipper-adafruit-funhouse-esp32s219021805/signals/device
Read data: @ [0x40],
Packet Type: @ [0x40],
Read data: [0x02],
Packet Length: 2
Read data: [0x00], [0x19],
Publish QOS1+ reply: @ [0x40], [0x02], [0x00], [0x19],
Published!
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

chuck.untulis
 
Posts: 104
Joined: Mon Jun 20, 2011 11:54 pm

Please be positive and constructive with your questions and comments.