@Gijs Hello, I found the "transfer" button on the original owner "Device" interface. But as he deleted it, the device is viewable in "Deleted Device" not in "Device" and there is no such a transfer button for Deleted Device. I tried with the Deleted Device PAC and get : "CRA rejected the modem ownership transfer: The device with id 00000000 can't be registered for the moment, please contact your device vendor.". (note the strange 00000000 instead of the PAC i gave) Another strange thing : the Deleted Device PAC is "E9--------------" (with - not to write the real one :-)) while the ubinascii.hexlify(Sigfox().pac()) gives "82--------------" maybe the issue is there? Any idea?

Are you able to upload files in safeboot mode? Please check the Pymakr settings (always enable safeboot before upload) or check here: https://docs.pycom.io/gettingstarted/programming/safeboot/ on how to activate safeboot manually Let me know!

I think the last link they attached: https://github.com/rafi021/Pycom-module-Example also includes the library with example

Perhaps you could use another type of magnetometer with a digital interrupt (or use an analog output and comparator circuit) that you could use to trigger a wakeup on the Lopy's deepsleep shield. My experience with the thing is limited, but according to this page: https://docs.pycom.io/datasheets/expansionboards/deepsleep/ you should be able to use P17 and P18 to trigger a wakeup. Once the wakup is triggered, all you need to do is send a lora packet and go back to sleep.

Hi, Working correctly with a new usb cable. Thank you regards

@Calvin-Foo advertising every minute is quite uncommon for a BLE device. It usually ranges from about every 10 ms to a few seconds. Most BLE devices are not constantly scanning, they scan only during the scan window, every scan interval. Also, they scan on the 3 advertising bands in a cycle. Coupled with the risk of collision or interference, this means it’s unlikely any BLE device will ever hear all advertisements from another one. For this reason, its probably better if you reduce the advertising interval if you want to get advertisements relatively quickly. As for filtering I don’t think there’s any support for low level filtering in the Pycom firmware, it’s up to you to filter the list of advertisements received using any criteria you want.

I try to do it over WiFi, more info here: https://forum.pycom.io/topic/7069/oserror-no-network-card-available-after-newest-firmware-update

@Little-Freak https://docs.pycom.io/firmwareapi/pycom/network/bluetooth/gattscharacteristic/#characteristiccallbacktriggernone-handlernone-argnone

@jcaron No it isn't. The only printout i have no control over is the boot printout. Nothing else is using it.

try: if(message_info > 0): # CONNEXION LORA ICI # message_info = 0 # Date = str(utime.mktime(utime.localtime())) # global_message[Date] = current_message # print("Current : " + str(global_message)) except Exception as e: print("Update current message exception : " + str(e)) time.sleep(1) I can't complete this part

@jcaron Wow! I was totally confused with the concept! Thank you very much :)

@Little-Freak Hello! I'm not sure if you still need it, but if you use the atom 1.52.0 the pymark package is working yet. The problem is with the new atom's version (it updates automatically if you don't cancel it). :)

@M-m No it is not echoed back from tx to rx, you must connect something to the line between. Think about, you have 2 devices conected by uart and you send something to second device and in the same thime you have same data as incoming ;-) How you can then know which data was send by second device to your first device? It not work in this way. You can try to connect rx to tx by the wire and then in should work in this way.

@jcaron Hello I'm here again, I was trying solving it without disturbing you but I can't understand how it works. I downloaded a few apps to advertise, but nothing solves my problem. To understand it more, I thought start using another lopy4 as an advertiser. I used this code: from network import Bluetooth bluetooth = Bluetooth() bluetooth.set_advertisement(name='LoPyNA', manufacturer_data="lopy_v1", service_uuid=b'1234567890123456') def conn_cb (bt_o): events = bt_o.events() # this method returns the flags and clears the internal registry if events & Bluetooth.CLIENT_CONNECTED: print("Client connected") elif events & Bluetooth.CLIENT_DISCONNECTED: print("Client disconnected") bluetooth.callback(trigger=Bluetooth.CLIENT_CONNECTED | Bluetooth.CLIENT_DISCONNECTED, handler=conn_cb) bluetooth.advertise(True) Now I come back to my first lopy with the BLE scanner and this is what I obtain: Mac: b'30aea474bc8e'. Data: b'02010607094c6f50794e41020aeb05122000400002010608ff6c6f70795f7631110731323334353637383930313233343536000000000000000000000000'. Adv name: LoPyNA. Thus, my code is working fine because I can find BLE devices. But not good enough because it can't find my two cell phones or my computer (or if it does, I'm unable to recognize them). Some suggestion or idea? Thank you very much!

@Assem-Hasna said in Handle temporary loss of WiFi: a device that wishes to send data over LoRa will send a request to the server using a pre configured static IP. It seems you have found your answer. But if connection robustness is what you need, the pre-configured static IP concerns me. If you convert it to a floating IP or DNS name with a low TTL, you will better handle a failure in that server. Alternately, configure multiple IPs in your device for multiple servers, and have it try each one until success. Only one of them needs to be alive at any one time.

Thank you for your help. I will come back after trying this.

Hi, It might take a couple of seconds / minutes before the device is synced to the ntp time, depending on the availability and how often you already tried (I think they have some sort of fair use policy). You might want to use a loop like this: while not rtc.synced(): time.sleep(1) Which will continue after syncing

@jcaron Thank you very much, I will comment on my progress soon. Regards!

I can confirm that this is now working. I had to update first to 1.20.2.rc6 and then to 1.20.2.r4