Hmm ok I've flagged this internally and will investigate! Thanks for your patience!

@tainanfish You might be surprised what LoRa can do (and remember in LoRa you CAN set the TX power) but if the question is just cost, then the GPS will be about the same ($8 for a GPS module, same as a LoRa module) To me the problem with GPS is it's even higher power consumption than WiFi.

@iber LoPy currently only supports Bluetooth LE GATT protocol which in simple terms is a key/value read+write protocol (like a simple database) and ill suited for streaming serialized data like JSON. You should however be able to make your mobile app write to Bluetooth LE characteristics on the LoPy which then set the WiFi and password. The GATTS example should give you the right idea: https://docs.pycom.io/pycom_esp32/library/network.Bluetooth.html#network.characteristic.events

@nagarjuna-reddy same here

Thanks for the reply. I'm afraid that is not the problem though. I do this: Use Pycom Firmware updater to update to latest. (1.6 something) Power Cycle Connect USB. REPL is ready import os os.mkfs("/flash") Sync Files works fine Then I do this I do this: Use command lie tool to downgrade firmware to 1.4 something Power Cycle Connect USB. REPL is ready import os os.mkfs("/flash") Sync Files fails Based on this, I feel sure there is no code running on the board. Also, the REPL prompt is active and ready when I click sync files so I know there is a good usb connection Really, if possible I would rather address the Bluetooth Issue. Atom file sync works just fine with the latest firmware. It is Bluetooth that should be fixed. Any chance a blue tooth fix is coming soon?

My lopy4 arrived and i tested with it, too, although i was pretty sure it wouldn't make a difference. It didn't, it does the same thing. I left my lopy running since yesterday noon and from 270 readings, 223 were correct. So that's around 17-18% loss.

@Jurassic-Pork @jmarcelino I tried it, and as far as I can see the result is the same.

@redimo Good luck. Thanks for the update. We scan BLE for 10 seconds then delete/restart the ble object. I'm noting there are maybe 3 updates we've not tried yet for BLE reliability. Maybe they are better? Very interested in how it works for you.

@tenspot No problem! :) It was likely that you had a very old version of the firmware tool installed!

@pwest We've found out how. On iBeacon, when you read the data you get an Array. You need to do int(lastHexValue, 16) and then -256. This results in the set TxPower the BLE Beacon has Edit: this site explains very well how the iBeacon protocoll is built, aswell as to where to find the TxPower: http://www.warski.org/blog/2014/01/how-ibeacons-work/

@berni I don't know if the bug was solved in new firmware releases, You should try the same code on the 1.4.0.b1 version, maybe it'll solve your problem.

Have you solved this problem?

High, Can I have some news about my issue? I don't know how to solve it !

Yes it did work, Thank you very much for your help.

@mkharibalaji Thanks for the explanation. Currently the Bluetooth stack only supports Bluetooth LE. You'd have to change your mobile app to use this instead. Bluetooth Classic is planned but I'm not sure when, it's not even on the low-level toolchain yet.

@jmarcelino Is this problem fixed?

Hello, Thanks for pointing out this bug. It has been fixed on the latest release 1.7.1.b1. Cheers, Daniel