I would try to monitor the length of the output queue. See _io_thread_func in MQTTMsgHandler.py - in there there's the transmit loop and you could add some signaling there to indicate the TX queue is empty. You'll probably need to modify the code and rename the function so you are not using the builtin frozen ones.

@eric-waai These settings should be fine then.

@belal-chaudhary Can you confirm is your wireless network the standard wep/wpa-2 setup or does it use fancy certificate based authentication? Nothing strange going on Re Network proxy's like Eduroam/mobile providers are likely to have?

@vflorio94 this error can happen frequently, it happens when the url is available, but the board doesn't accept connections. Or when the board is starting, it might take a few seconds to be able to connect to it. You don't have another connection to the board, right? (And I assume you have tried hard resetting, disconnecting power then trying again)

@panda try lte.send_at_cmd('AT!="setDbgPerm full"') before using the command lte.send_at_cmd('AT!="RRC:showDetectedCell"')

@manuelc1318 as I wrote, you can transmit data in both directions: write to a characteristic to send data from client to server, and either read from a characteristic or use notifications for data from server to client.

@Ralph, thanks very much. It now works again.

Thank you @jcaron, for the data consumption topic, you're right, I will check the requirements again. For the gateway, can you recommend us some low price, fair range LoraWAN gateways? Doesn't matter if they aren't battery powered. We can start from there.

Yes! Thank you!!

Have you tried using something other than pymakr? maybe screen or minicom. Also its worth checking if your user has permissions for the serial port. The procedure to do this varies by linux distro but on most you can add your user to the dialout group and when you reboot that user will have permissions to use serial ports sudo usermod -a -G dialout $USER

@robert-hh Thank you, that worked perfectly.

@pmb_nl i have the same problem, do You have some solution about it? Thanks

@ahelllycan Using a serial terminal emulator program like picocom, minicom or screen, you can connect as many devices as you have available USB ports. Just open for each device a terminal window and start the serial terminal using the repective interface. The interfaces are called /dev/ttyUSB0, /dev/ttyUSB1, .... Example: picocom -b 115200 /dev/ttyUSB0 picocom -b 115200 /dev/ttyUSB1 .... To close picocom, enter Ctrl-A Ctrl-X of close the window with picocom.

@soren said in Socket having to close and reopen: You close socket on server side then you must close it also on client side(it is closed already but..) Question is what problem do you have with the code? Is it working, if yes, do you ask if there is some better way?

@ccarducci you could enable a for loop running every second, this way you can interrupt your program every second.

@panos29 It's more about the ADC range, which is about 0.07 - 1.1V for the reading between 0 and 4096. I assume you would always need some kind of pre-amplifier/buffer, at least to protect the esp32 against damage,, and if you do not need to take values at hight speed, you can always use averaging to reduce the noise. The esp32 chip is told to have a built-in preamplifier, but that is not supported by Micropython, and I do not know whether it works.

USB issues SOLVED The problem was the baud rate being used by Putty. The default baud rate in Putty is 9600 but the rate that should be used is 115200. This is mentioned in the documentation section for using Linux . After I changed the baud rate to 115200 did that Serial USB was working.