Before you start make sure you have updated your Pycom device to latest firmware.
Otherwise these new features won't work!
Over the air update of /flash directory
Now it is possible to update content of your device's /flash directory over the air using WiFi connection
Read content of /flash directory
Push file changes to device
Delete files from device
Now it is possible to connect your device using Sigfox to Pybytes
Use sigfox backend API to register new devices on Sigfox Backend
Send uplink messages from Pycom device to Pybytes using Sigfox
Integration works best with custom Sigfox contract
devKit support and full documentation is comming soon
TLS connection for Pybytes library
This feature works at this moment only for devices flashed with stable firmware and pybytes library manually added to /flash folder. We will add this feature to soon to pybytes firmware too.
Pybytes library now supports secure TLS connection over MQTT protocol on WiFi.
This feature is enabled by default for newly added devices to Pybytes which run latest stable firmware with pybytes library in /flash folder.
In pybytes_config.json you should have these keys:
So be it. But, why provide a schematic for the 2.0 expansion board, but not the 3.0 board? I don't want to build my own board. I just want to know what is wired to what. I'm an EE. I care about these things.
@hetifi said in Lora -> TTN-console working. Howto open Pybytes payload ?:
If look device data: payload: 9E050233335341
Line in Main.py:
pybytes.send_virtual_pin_value(False, id_payload , (ruuvitag.temperature))
But maybe is more wise code tree temperatures in one transmission my own and not use pybytes.send_virtual_pin_value.
After one night sleep... 9E050233335341 is simply 13.2 (32-bit float)