@mcmxii Depends what you mean by "at the same time" but I'm pretty sure you can queue one message for transmission via LTE and the same via LoRa. (of course LoRa will be the limitation due to limited packet size and airtime regulatory restrictions) I'm also pretty sure - unless the team pulled off some miracle - that you cannot queue a message over LoRa and Sigfox at the same time because those two share the same chip.

@jamjam In the last Kickstarter update they said end of Sept, but let's say 2 months.

@ClementN The PR is here: https://github.com/pycom/pycom-micropython-sigfox/pull/65 It shows also the minor change to the file pybdac.c and what you can expect from the change (which is just four different levels).

@danielm Not that I know of. Personally - but I'm no RF expert - I'd just stick the known values into an online calculator such as https://www.eeweb.com/toolbox/pi-match

For WiPy 3.0 my wish is it can be smaller. Go for 1.27mm pin pitch and use a breadboard adapter if you have to. In my dreams the OEM module would be a SOIC-28 or similar package and the the Development Kit would simply be a board with a socket for it.

@bigboy20769 I see at least two options: call the respective init methods in a try block call os.uname and check the type of module

Hi @RobTuDelft Thanks! Jiemde

@rskoniec Thanks, it helped debugging. If I unplug the power completely it shows the POWER_ON_WAKE, but if I do a manual reset (button pressed) it says TIMER_WAKE. I reckon it's a bit confusing. I couldn't see the values after connecting the USB and reconnecting to the console, so I assumed a manual reset would be treated as a POWER_ON_WAKE.

@iotmaker You can tell both I2C and onewire which Pin to use. For I2c, you do it by i2c.init(), for the onewire driver, it is given in the constructor of the class.

@eron93br The SX1272 and SX1276 have no problems communicating, as long as you set the same modulation it's OK. But your request for node code is difficult, the SX1276 is just a radio transceiver it doesn't run any code, to use it you need to connect it to a host processor (can be a microcontroller, a SoC like the Raspberry Pi or even a computer via USB). All of these will have different code. For example if you host is an Arduino and since you mentioned LoRaWAN something like Arduino-LMIC would be suitable for a node. You can even use the ttn ABP example just remove the LMIC_setupChannel() lines to match your LoPy nano gateway setup (so have only ONE LMIC_setupChannel line with the same frequency you set on the LoPy)

@jmarcelino SOLVED Thanks for the help. Was able to adapt the example to connect to my Lopy and get a specific service with no issues. Some tips for anybody else trying to do access a GATT service. If you use the Pycom example it will print out a services.uuid like this b'\xdet-\xf0p\x13\x12\xb5DK\xb1\xc5 \xff\x95\xa4' . But if you are trying to access the service using the UUID as it appears it will not work. So what I did (as suggested by jmarcelino) was use binascii.hexlify to get a hex value. Which in this case was -----de742df0701312b5444bb1c520ff95a4' ,then use that as the value with binascci.unhexlify as the uuid input like this service.uuid()==binascii.unhexlify(b'de742df0701312b5444bb1c520ff95a4'): Another way to get the uuid is to use the Android Nordic Semiconductor nRF Connect app (or similar) to get the hex value for the UUID and then use unhexlify as above.

@jmarcelino if that is built in to the low level esp.read and esp.write to flash, then it may be transparent, covering anything in flash, like binary code, frozen bytecode and file system. It would then protect against raw readout of flash bypassing the esp.

If you want to customise how the current process works have a look at the https://github.com/pycom/pycom-micropython-sigfox/tree/master/esp32/ftp folder, especially updater.c.

Hi @scott, Many thanks for that work ! Thinking this morning that I will do it too this week-end, but you do it so I can do an other thing. The Sipy seem to be the same as the Lopy so it can be easy to duplicate them. BR

@scott Thank you for you reply. I tested the server side notifications yesterday and my first tests worked so it looks good so far.