@neoniousTR Good vacation !

Several things have changed with the newest lowsync version (1.4.7, yesterday) and the newest firmware. Can you update both and try again?

Please check v1.4.0, this includes the changes: https://www.neonious.com/documentation/changelog

My first step this lowsync 1.4.2 : I sync the mcu files !!!!!!

Quick update: the last version of low.js is now working on my ESP32 Wrover board: LOLIN D32 Pro based on ESP32-WROVER Rev 1 (chip is ESP32-D0WD). This is really great news as I failed soldering the ESP32-WROVER module by hand. I need more practice and the use of soldering flux for next time. So I will continue working on that LOLIN D32 board for now.

Got it! Since it was connected to the internet already by cable, I didn't understand why configuring the wifi also to the same LAN would be any good. So I concluded access via USB is needed. Got it now, quick steps: lowsync init lowsync settings set wifi.ssid="YOUR_SSID" wifi.password="YOUR_PASS" wifi.mode=station wifi.dhcp=client that failed at first, however, once I chose comminication via port 8000 on HTTP things magically resolved themselves Installing NPN modules works now just fine. Thanks!

The new version is online! Do you want to try it out?

lowsync now shows the correct 507 no space error in this case. I tried out express myself. It runs out of memory, correct? Have this in the list for some time in the future. Till then, I would recommend not to use express. It is, after all, a large framework, and even when it works, it will be slowing down the microcontroller much.

Interesting. I guess I will have to try to reproduce this. Thank you, and have a nice day!

@ygageot I just worry a little about the range of BLE for my application, having some additional range that wifi gives would be real nice.

Ah, ok, interesting.. Could have to do with what happens during transpiling. Will look at this soon, but currently on vacation till 26th, and as you can continue developing, it is not urgent :-)!

Right, it is connected to a breadboard, and twiddling the components a bit do help, so it is probably a poor connection. Thank you for your help.

Thanks, fstats with 'rc' flag works My global object stringified to json had a size of 1445 bytes seen as uncompressed in fact it is 598 bytes in memory, compressed.

@neoniousTR Ok For the moment it is not important for me, I have the useful packages installed

Thanks, this solved the same issue also here.

I think that is what is supposed to be.

So I tried today to access the wrover soldered to the breakout board via USB-UART. I was hoping to get here at least some success, since my NEONIOUS ONE is currently also not working. I sort of achieved some kind of communication once I figured out how to connect my USB-UART to the break-out-board. I followed this configuration in "upload-mode" (IO0 to GND): https://www.ranta.ch/tutorials/ESP-32-Initial/ I enered step 1/3. lowsync was checking whether this is a wrover and then aborted. Why I don't know. Might be bad solder-job. Might be some missing components on the board. Might be bad connectivity via Dupont-connectors, ... I will put that aside, until all the missing parts arrive.

In my last source with Strings, the string content is always zeros. If the storage is UTF-8, it is is pure Ascii string, very simple. But if all the previous temporary strings are kept in a cache and not freed ....

Here you go: https://github.com/neonious/lowjs/commit/1028ffb4bc97030df91cfaa6674f8933ec572ec2 Will be in PC binaries tomorrow, in ESP32 binaries with the next update.

For flashing with other tools (esptool directly for example), you need to license the unlocked version from us, contact info@neonious.com if you are interested. But, with the free version you can already build your own firmware with lowsync build (see docs) and flash every board with a lowsync flash call, so as I wrote, for normal use cases the free version is all you need. Thomas