Pybytes not seeing my WiPy 2.0

Phil shared this problem 2 years ago

I'm running linux Mint and I upgraded to the most recent firmware updater, flashed the new 1.17.5.b2 firmware onto my WiPy 2.0, removed the wire and reset it. It appeared to have connected to my home network, but I saw no connectin to pybytes. I then downloaded my custom firmware package from pybytes, unzipped it into a directory and synced that into my device using Atom/Pymakr. Doing that gives this dialog:

Syncing project (main folder)...

Reading file status

Failed to read project status, synchronizing all files

Creating dir lib

[1/10] Writing file

[2/10] Writing file

[3/10] Writing file lib/

[4/10] Writing file lib/

[5/10] Writing file lib/

[6/10] Writing file lib/

[7/10] Writing file lib/

[8/10] Writing file lib/

[9/10] Writing file lib/

[10/10] Writing file

Synchronizing done, resetting board...

ets Jun 8 2016 00:22:57

rst:0x7 (TG0WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)

configsip: 0, SPIWP:0xee


mode:DIO, clock div:1





entry 0x400a059c

Using configuration file from /flash folder

WMAC: 240ac4006d3c

Firmware: 1.17.5.b2

WiFi connection established

Using 8192 bytes as stack size

memory allocation failed, allocating 8192 bytes was executed properly (using a firmware that does not include frozen libraries)

Traceback (most recent call last):

File "", line 184, in <module>

File "/flash/lib/", line 60, in send_virtual_pin_value

File "/flash/lib/", line 526, in send_pybytes_custom_method_values

TypeError: unsupported types for : 'str', 'int'

MicroPython v1.8.6-849-b9d53b40 on 2018-05-03; WiPy with ESP32

Any ideas for getting this fixed would be appreciated!


Comments (5)


Hi Phil,

Can you send me the 3 files mentioned at the end of the logs (,, at ?

When you added your device to pybytes, did you used the quick add device process or the former firmware updater tool?

Because the quick add device process flashes a firmware version that includes frozen code, which contains a default version of the files that you normally had to flash manually to the device, like

So, in theory, using this firmware, you can simply transfer a project that contains only a and your

Here I feel like that ran by your device is out dated or corrupted.




Thanks for the help, Alex:

Suspecting that the upgrade process could be an issue, I asked for help in The response there seemed to suggest that I should just update my linux firmware updater, and then update my WiPy. Did I get that wrong? To answer your question, here's the process that I believe that I went through:

1) Download and apply the .deb package to my linux box

2) Created a pybytes account and added a new device (WiPy w/a WiFi shield (this seemed odd--WiFi isn't really a shield on a WiPy device). From this I got the pybytes identifier for my device.

3) connect the WiPy to my linux box and ran the updater (note: there were various error messages that popped up on the terminal screen, but the device did ultimately update). I was asked for and included the pybytes identifier

4) Rebooted the device

5) The device started, connected to my home network and then gave the error messages displayed.

I can't get to my files until later today, but I went to the line in question (File "/flash/lib/", line 526, in send_pybytes_custom_method_values) and it's a perfectly good looking python .append command.



Hello Phil,

I just went through the same steps as you and downloaded the pybytes libraries from here:


(after adding a new device)

And the files from that download link are indeed outdated.

I'll let my colleagues know about that so you can download the proper libraries.

Btw, even if you used the quick add device (the recommended option because the device should be able to connect right away after the process) you would need at least the from the libraries to be able to customize it and override the included in the frozen code of the firmware, and actually be able to modify the behavior of your device.

I am just mentioning that here to let other people with the same issue know about it.

I will let you know here again when the download link will be ready.





Now that I see that link, it reminds me that I've only got WiPy 2.0 devices. Presumably they don't have enough memory. When I originally tried the quick add method, I never saw my device on the PyBytes console.

What's my path forward?

Also, specifically, which check boxes should I check when doing the firmware upgrade?




From what I read in the logs you sent in the first place, the device started correctly and executed the code, otherwise it wouldn’t have been able to execute the

With the libraries you have in your device right now, it’s perfectly logical that pybytes doesn’t show anything even if the device is connected to your wifi.

Let’s just see what happens with the updated libraries. :)


Alexis writes:>I will let you know here again when the download link will be ready.

Any progress on this?


Hello Phil, Sorry for the late reply!

Yes you can now download the latest libraries from the settings tab of your device, or by creating a new one.

From the downloaded files, you can simply flash the and the config file to your device and it should work (using pymakr).

Beware that from now on the is deprecated, the file pybytes_config.json will be used instead. The content of the two files is basically the same. The firmware is set up to create the .json file (if it doesn't exist) from the file content (if it exists). If you have issues with this please let me know.

Otherwise, we have been encountering a strange issue when trying to login to pybytes lately: if you see the error message "Internal server error" when trying to sign in, please clear your browser's cache and try again, that should fix the problem.

Cheers, Alexis


Indeed, when attempting to log into pybytes, (from chrome) I get

Internal errorUh Oh! Something wrong happened, please try again later, thanks.

Back to login page

So far, neither trying again later nor clearing the cache, etc., has not helped.


Hello Phil,

Have you tried to refresh the page after clearing the cache?


Seriously? Of course I tried refreshing the page. I also restarted the browser.


Yeah, sorry... ^^

It appears to work for me, maybe the server (or some parts of it) was being updated at the time you tried. You can also try with another browser but if the cache isn't causing the issue it's unlikely that it can solve the problem.

If it still doesn't work, can you try to open the browser's console and send me what you have there after trying to login?

Thanks, Alex