@jmarcelino Is there any example code that incorporates deepsleep and LoraWAN with these new functionalities to test it? thanks

@bucknall i have the same problem of @moenad OTTA with nanogateway, (but not with Conduit for example). Could you find any solution to this?

I would rather recommend you to have a look at Anker 21W solar charger. In cloud (single port) : 0.45 amps @ 4.75 V In sun (single port) : 1.81 amps @ 5.09 V It recharged the phone even faster than using normal which is using plugging it into a computer USB port. The Anker unit provides 5VDC through 2 USB connections, which keeps the kit compact and light. I can easily carry this in my go bag along with a couple of 10,000mAH battery boxes. Sounds nice, right?

@jmarcelino said in Socket documentation: @bmarkus 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.

OP Here I also uninstalled atom and pymakr a couple of times. I also uninstalled pymakr a third time and installed using apm install and that did not work.

@aktivalux said in Kernel Panic when using SSL connections (MQTT or HTTPS): -35123 You mean it raises OSError: -35123? Actually -35123 beeing -0x8933 is out of the error range defined by mbedtls. Is there a typo in this numer? https://tls.mbed.org/api/error_8h.html

@rolandvs said in Is the time in the RTC preserved after hard reset w/o power down?: If true it makes the use of the RTC sort of worthless in situations where you want to keep time with an attached battery without the possibility to use Wi-Fi to NTP your time like with LoPy or SiPy... It doesn't solve the original issue, but you can update time without network connection using GPS receiver, e.g. on the pytrack extension board.

@rolandvs look at watchdog https://docs.pycom.io/chapter/firmwareapi/pycom/machine/WDT.html

@jmarcelino As you suspected, I was implicitly using: s.setsockopt(socket.SOL_LORA, socket.SO_CONFIRMED, False) So I explicitly added s.setsockopt(socket.SOL_LORA, socket.SO_CONFIRMED, False) to my script, and now the network server returns a downlink, and I am able to access the [LoRa instance].stats(). Thank you very much for taking the time to help me out. A+ :) Frank

@jmarcelino Great, then work is being done :) Thanks for the reply!

The same USB cable works fine with all other LoPys so I don't think it is a problem related to the cables nor the USB ports...

Question 1: that is correct, the payload is still encrypted. Question 2: this has been discussed before here. I would like to refer you to Pierre's blog here.

@berni I would like to add my name to the list of people having the same problem with join issues. Incidentally I have another Node using an Arduino LoRaWan shield on the same nano gateway that joins successfully every time so I would tend to exclude noise issues with the Pycom OTAA / Nano Gateway example. It looks like software or firmware issues in the node to me. Hope this helps.

@neilh93 Great. Yes I use a similar thing for my commercial product. But remember that nodes may miss (due to RF issues, power) the "key change" message and still use the old one. What I did was to clone the existing device on the server backend but with the new keys. Then when a transmission arrives on the new device (which means the node has updated the keys) the old device is deleted. If the next transmission still arrives on the old device it means the node has not picked it up so a new key change message is scheduled for retransmission - this is repeated until it's finally picked up.

@sjp770 SPI is a bus system. In a star configuration you can connect several slave devices to one master, as long as the (capacitive) load is not exceeded. But you need a CS for each device. If D/C is needed, you may be able to share it. If devices have active feedback pins like an Alarm pin, that has to be connected too to a separate I/O.

@lollisoft Thanks for this information! I'll try this!

@jalperin This works to restore RTC after pysense go-to-sleep. py.setup_sleep(sleepsec) pycom.nvs_set('gtsSec',sleepsec) pycom.nvs_set('ttSec',time.time()) py.go_to_sleep() rtc = RTC() ttSec = pycom.nvs_get('ttSec') # time.time() previous value if ttSec: gtsSec = pycom.nvs_get('gtsSec') # go to sleep seconds # reset clock to prior saved time plus length of sleep (both in seconds) rtc.init(time.gmtime( ttSec + gtsSec )) else: # Initialize your wifi, then rtc.ntp_sync("pool.ntp.org") # rtc.ntp_sync("23.239.26.89") while not rtc.synced(): time.sleep(1) Since I can't distinguish awakening from reset, I am currently setting ttSec manually before running code. pycom.nvs_set('ttSec',0)

For the record, there is now a socket.recvfrom(bufsize) method that will return a (data, port) tuple.