@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!

Thank you! I will take a look and merge when creating the next lowsync version. This can take a while however. Thomas

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.

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 :-)!

@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.

What I did: installed "mqtt" and "mqtt-connection" built one file which contains all your server + client code. Here is the link to the file: https://drive.google.com/file/d/1jx6i8g7VR3OJHeOLd-Z4NlWd3nUdxUDy ran it => working Also it is working if I only do the client on the device and set the URL to the IP of my PC where I have the server running. Some ideas: Can you update low.js? Maybe I fixed something in the meantime which is why it runs If it does not run, does it run directly after a reboot? Then I wonder what you are doing before running the script what breaks things... Thomas

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.

I am using udp at the moment in the first layer of my control and data aq system which I am porting from Nodes hosted on linux embedded or windowsPC. At the moment it seems. UDPserver.address() only provides the host IP adress on connected sockets. Until a connection is made it seems that the host adrress in the tcp/ip layers is not initialised. UDP.connect is also not supported at the moment (dont need it anyway) but a UDP connection will cause the local hostip to become correctly populated and server.address() will work ON my PC. Soon I will be implementing my tcp socket connections so I will come back to this problem then . As I assume tcpserver.connect is impemented and therefore this method will work. As I also have a dedicated (application) server in my system infrastructure it will be no problem in the future to obtain the IP address this way. However, for other applications using DHCP (most serious iot apps I think) it would be nice to know the IP at start up time, particularly if the module is roaming. Instead of implementing the interfaces part of the OS module I would suggest you just provide a private function call to pull this up from the underlying DHCP client. I'll be back.

Thanks. Shouldn't be a problem at all. I'll keep lowJs bokmarked. I'll for sure find a project in the future where it will fit