I am facing a challenge when attempting to decompress data compressed using the miniz library on the ESP32 platform. My objective is to compress data using miniz library in flasher_stub compoment of esp-idf and then decompress the data on the cloud side using some python script that can be compatible with miniz decompression style like zlib. As per the documentation and information available, the miniz library is described as a "lossless, high-performance data compression library" that implements the zlib (RFC 1950) and Deflate (RFC 1951) compressed data format specification standards. However, I am encountering difficulties when attempting to decompress the compressed data using Python. Specifically, when using the Python zlib module, which should be compatible with the zlib and Deflate formats, I am receiving an "unknown compression method" error. I have verified that the file and data are correct, and they were compressed using the miniz library on the ESP32. Despite this, I am unable to successfully decompress the data. I would greatly appreciate any help or any insights that you can provide regarding how to properly decompress data that has been compressed with the miniz library using Python.

@ErickM said in Connect to wifi: VS say missing imports VS do not know pycom libraries at all, so do not worry.

@Andres-Ortega You can set up the lopy4 as WiFi AP and connect it with the Arduino. Then you can do socket level data exchange. That's easy with the LoPy4, and some more work with the Arduino. But there should be many examples to go for. You could as well set up a MQTT server in your network (any PC, RPi, etc will do) and use it by both the LoPy4 and Arduino for data exchange.

It says OSError: connection refused after trying to connect with connect(adv.mac)

@Alessandro-Cortese There is no way implemented to stop machine.sleep().

@Pedro-Almeida I can replicate this behavior. But there is little that canbe done in the uftpd code, since it does not get noticed. For uftpd, the session continues to exist.

@Alessandro-Cortese That's how it is implemented. It is not the init call, it is the constructor. if you call: uart2 = UART(2, 115200) # init with given baudrate the default pins for UART 2 are used. These are P3 and P4, which are then deassigned from UART 1. Putting all settings into the constructor call avoids that pitfall, and it is shorter code.

@Jorge-Romero So that's the configuration for COM4, which seems to be used with the LoPy4. If you say "without expansion board", you must have used another USB/UART converter.

@jmarcelino Just checking if this is resolved. I am still not able to connect to BLE device when using Bluetooth.RANDOM_ADDR.

@balefire I agree - the PyCom user experience is terrible. So many gaps in the documentation, the main effort is reverse engineering what to do from everyone's failures - no clear "how to" guidance that is actually accurate / complete. Its a shame - gut feel; pycom could have been a game changer, but will die a slow death due to too closely guarded "secrets" which only serve to hinder the developers and product users.

@robert-hh Okay thanks, I will try this firmware, and test lora.remove_channel(i), then add channel AS923-2 freqs (921.4MHz & 921.6MHz ).

@Steven-Boonstoppel said in Nice method to check if SD-card is removed: Expansion Board v3 I do not use Expansion Board so cannot help

@robert-hh thanks! I had read that somewhere momentarily and disconnected pin 23, but it was still pulled from software as a deepsleep wakeup pin. So removing the jumper was not enough. Moved the pin and it works now, thanks!