@tttadam I think I find the issue. If I shut the pycom down by pluging it out (like the 99,9% of the cases) the sensor wont work. But if I reboot it after I pluged-in then it does work. So my "solution"/workaround is that I check in the boot.py if the checksum is false, if it is, then I do a machine.reset() . Any more elegant solution is welcomed :D

Hi @robert-hh , Both Lopy and Fipy have firmware release='1.18.2.r1'

@misterlisty Pycom bluetooth stack is currently BLE (Bluetooth Low Energy) . And, in BLE there is no SPP equivalent (Simple Port Protocol) as in Standard Bluetooth stack. The BLE normalization is as is, only nordic semi (a ble chip manufacturer) provide a non-standard SPP-like library for it's chip. BUT you can exchange data in BLE, you just have to do it by your self with specific software you write, take a look at how service/characteristics work in ble.

@robert-hh thanks. ill try and sort out some VM's and give that ago.

@testos Yes, you need to connect to the external IO header below the fipy. And you have to specify these Pins, when you open the UART, most likely UART1. On a Fipy, two of the three UARTs are already used by the firmware UART0 and maybe UART2. You have to try.

@robert-hh I managed to get it to work! Thanks for the help! I tried some code i found on the forum so i think it had something to do with my code in the end. I'll try to update this thread with the working code once i finished working on it

@andrejpekarcik UART0 is used for the REPL over USB. The regular speed is 115200. SO if you want to use that, you have to deinit REPL on UART, using uos.dupterm(None), and use Telnet for the REPL.

@robert-hh Thank you, much appreciated.

Big Thanks for the hint! I compiled the firmware with a buffer_len of 4096 instead of 512 and it seems to be working now. At least it says it reads the correct number of bytes. I still have to verify the data ;)

@eric73 This seems to have solved my problem! Thanks!

@robert-hh Hooray! I've got it! Signal wire was broken between pin and GPS. Thanks.

@robert-hh So a remote raw lora receiver with a lot of nodes sending it is just inevitable that collisions happen? My current "solution" is to send and wait for it to send back an acknowledge, if not just wait a random period of time.

@tschili Imho, if you trigger the wake-up just when the transmission starts, you'll have the issue that the GPY needs to little bit of time to wake-up and initialise, and you will most certainly lose and data received during that time. So you would need the SIM800L to wait until the GPY is ready to receive before it start sending the data, and some other way to wake up the GPY.

@jmpratt I cannot believe that you have the same code on both WiPy's. Please reload the code to both devices, reset them and try.