@ahelllycan I think we would need to see code, or general overview of your process. At the moment we are guessing. But @jcaron is right. You should have a call back on message receive and you choose when to send messages based on other criteria. The rest of the time you will be sleeping or waiting.
Did you find out about this? I where also able to connect and send a message to the AWS IoT platform. Then I got a similer error where it continiously report "Socket receive error: -80", but no "Socket send error [Errno 104] ECONNRESET" message.
@livius That was my first guess but I've dropped the power to the lowest possible level (15%) and it's as far away as I can make it. I have counted 90 Wi-Fi signals in the area though, which is staggering!
@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?
Do you know if Loriot supports confirmed uplinks in the free community tier? Just wondering what happens because according to the docs downlinks are not supported.
Yes it works as well as OTAA since the latest Network Server update. In the free community tier you can't send download messages to the device but sending and receiving MAC layer messages (commands and responses) works in both directions. You can use ADR also of course and Battery Level is also handled.