@patrickl That's indeed what I would do: just "interconnect" the UART connected to the Pi with the LTE's UART, sending data receiving from one end to the other and vice versa. Then the modem will look like it's directly connected to the Pi. Just don't call LTE and make sure you have the same speed settings everywhere. An alternative would probably to do it over BLE, but that seems like quite some more work to me.

Dear @shanefowler25, @shanefowler25 said in Bluetooth GATTSCharacteristic GPy: I just wasn't able to do a GET request for my application. May I humbly ask whether you wanted to connect using SSL here? I'm just asking because we didn't test these details thoroughly with our custom builds yet. @shanefowler25 said in Bluetooth GATTSCharacteristic GPy: Hopefully sometime in the future, there will be another update to the firmware that allows users to use Wifi/Bluetooth or Cellular/Bluetooth, without the program crashing and resetting the board. Issues around this "coexist" thing have even bitten Espressif Systems for quite a while, as outlined above. In this manner, the Pycom firmware is pretty much innocent here as it depends very much on the details coming from the ESP-IDF in this regard. @shanefowler25 said in Bluetooth GATTSCharacteristic GPy: My program would still crash when I used to Bluetooth to break the while loop of my program. While we are avid WiFi users, some people from our community are also approaching BLE these days. @poesel reported his observations on [1] and [2] already, but unfortunately he is currently traveling without being able to confirm our latest build would work better for him. He is using a GPy as well. @shanefowler25 said in Bluetooth GATTSCharacteristic GPy: I figured out a workaround that works for the application that I'm trying to do. Good that you found something that works for you. As we are currently trying to collect experiences from people affected by this issue on [3], we still ask anyone who could test the latest dragonfly builds. So, if you might find some time for that beyond working on your program, we would be more than happy to hear about the outcome. Thanks already and happy hacking. With kind regards, Andreas. [1] https://forum.pycom.io/topic/5358/1-20-0rc13-guru-meditation [2] https://community.hiveeyes.org/t/investigating-core-panics-with-ble-on-pycom-devices/2715 [3] https://community.hiveeyes.org/t/testing-the-custom-dragonfly-builds-on-pycom-devices/2746

hi @westmaxx, Let's first connect the 2 Lopy4 in the same Mesh network. What firmware are you using? what micropy scripts are you using? Could you run this tutorial: https://docs.pycom.io/tutorials/lora/lora-mesh/ ? The LoRa 868 Mhz antenna is on the right side of the LED, as shown here: https://docs.pycom.io/gitbook/assets/lopy4-pinout.pdf Also, please make sure you're using the same LoRa parameters on both boards? Band, frequency, bandwidth and spreading factor?

I think I might have a flash memory problem, something that has haunted me with GPYs from the getgo. If I upload then remove then upload boot.py & main.py several times I seem to get a more stable system. It's like the first write of new software is not enough.

@robert-hh Thanks for the info. Always rescued it via software. Will test it with machine Deepsleep

@paul-thornton Thanks for your input, the probmlem was that we had connected some sensors on the pins that was shared with LTE.

Hi @james-matthews, Maybe a LoRa mesh network? (Note: it's still in development) What type of devices do you have?

Hello, If you want, I propose a new powerful embedded Web Server for MicroPython (and CPython) that supports route handlers, modules like WebSockets or PyhtmlTemplate and a lot of simultaneous requests. Mostly used on ESP32, Pycom WiPy, STM32 on Pyboard, ... Robust and efficient (thousands requests on CPython!) GitHub - Open Source - MIT. --> https://github.com/jczic/MicroWebSrv2 <--

@robert-hh Hello, I updated the firmware and it seems to work, thank you ! Can't belive I didn't do this step ...

I have the same problem after upgrading to release='1.16.0.b1', version='v1.8.6-849-055728a on 2018-02-13' now I have to do a wlan init (and wlan deinit) to get the mac address firmware bug? tnx André

@seb https://docs.pycom.io/tutorials/introduction should be the link (without final / ) causing Newbie panic :)

I have tried this before with LoRa and it didn't work. I expect the same result with Wi-Fi as the clock and other network delays are the biggest problems. To get accurate results you would need a very reliable clock, which isn't available. Also ntp servers will only let you sync up to a certain accuracy which is not good enough by far. Fingerprinting, multilateration etc. are maybe alternatives you could check out.

@livius Node should talk about each hour (or maybe less, but I don't think I'll go lower than 10 minutes) do to a keep alive and update informations or "right away" if there's a trigger trigged (alarm). I'm pretty sure the hardware can do it, I was less sure about the MicroPython (I saw there was some limitation if we compare to the Python3). I'll order some for testing I guess ! :)

@jmarcelino Thanks. I think I tried that this morning, but w/o success. I'll retry this evening.

@shariq I have the code below in main.py, which sets up the device for connecting to my router with a fixed IP, which you then can use to access the device. WIFI_IP = "aa.bb.cc.ss" ROUTER_IP = "aa.bb.cc.rr") WIFI_SSID = "your AP SSID" WIFI_PASS = "your AP Password" def do_connect(): import network import time wlan = network.WLAN(mode=network.WLAN.STA) # create station interface if not wlan.isconnected(): # check if the station is connected to an AP wlan.ifconfig(config=(WIFI_IP, "255.255.255.0", ROUTER_IP, ROUTER_IP)) wlan.connect(ssid=WIFI_SSID, auth=(network.WLAN.WPA2, WIFI_PASSWD)) for _ in range(100): if wlan.isconnected(): # check if the station is connected to an AP break print('.', end='') time.sleep_ms(200) else: print("Connect attempt timed out\n") return print('\nnetwork config:', wlan.ifconfig()) do_connect()

similar problem. this: sigfox = Sigfox(mode=Sigfox.SIGFOX, rcz=Sigfox.RCZ1) s = socket.socket(socket.AF_SIGFOX, socket.SOCK_RAW) s.setblocking(True) s.setsockopt(socket.SOL_SIGFOX, socket.SO_RX, True) s.send(bytes([0x00, scale(lux.light()[0]), 3, 4, 5, 6, 7, 8, 9, 10, 0xAA, 0xFF])) retval = s.recv(32) print ("received " + retval) gives me: Traceback (most recent call last): File "<stdin>", line 164, in <module> OSError: [Errno 100] ENETDOWN whilst the backend shows me: Status : [ACKED] Data (Hexa) : cafecafecafecafe any idea what i'm missing here? It's definitively not the link - sender and receiver have free LOS. avgSnr=20.74 rssi=-52.00 Used HW: FiPy on '1.17.5.b6'

@timeb look here - there is topic - but not solution.. https://forum.pycom.io/topic/829/mesh-network-on-wipy-2-0

@misterlisty yep. Go ahead ! :)