@jirkakrepl said in New Pybytes firmware 1.18.1.r9 (Experimental LTE support):
If your LTE configuration is correct, your device with a Simcard should connect to Pybytes using LTE.
Then Terminal and Flash OTA update should work too.
Awesome, I'll try it out soon, thanks! LTE OTA was only thing holding us back from a production release.
In the meantime, it has been documented ;) http://docs.pycom.io/firmwareapi/pycom/pycom/#pycompybytes_on_boot
Soon, it will be in the Pybytes section as well
Gijs
Hi,
If the device is connected to pybytes, using the update location button will update the location in the map.
You can find the map in the dashboard of the device.
To send a custom location, you should be able to use the following function:
pybytes.send_custom_location(), but it appears to not work (yet)
@Gijs I found the issue! The GPy was connected to my guest wifi which apparently has a firewall that blocks all non-websurfing and -email traffic (probably by only allowing ports 80 and 443). Connecting it to my main wifi or disabling this firewall let the GPy start up.
It would be nice if Pybytes still continues booting up even if it can not connect to the MQTT server.
@VST-Admin Funny, reading back after another posting I just made and realized suddenly I was talking to myself. Either Pycom never reads their forums or they are not seriously interested in business.
I have gone throught the tutorial of pygate with chirpstack setup (https://docs.pycom.io/pybytes/networks/lora/chirpstack/) and have done the process of addign gateway a few times now. Under the network server setting of adding a gateway, I get pycom as the only option. Gateway ID is the same ID I am using which I used to get my pygate connected to TTN. But my pygate never connects to pycom chirpstack NS. The last activity says Never. There are no errors on my pygate as well
Hi @bruyn,
Kindly note that this has been solved. if you face any other issue I am happy to help.
Thank you for reporting that.
Best Regards,
Ahmad El Masri
@ahmadelmasri Thanks for your support on this.
Yes everything is working now, I just got a duplication of the "Signal 1" in my dashboard.
But messages are coming via LoRaWAN and device is online, Thank you again !
@VST-Admin Im not sure if this is the final answer or not, but I have discovered that the integration does not like a \r in the data. my data extractions were adding a Carriage Return by mistake. I could send any data I wanted to through the integration EXCEPT the variable containing the string I needed. I then had it echo that string as an array of bytes and then I could see there was an additional \r at the end. I removed it and the line started working through the integration immediately.
I really wish something like this was documented, so I wouldn't literally lose days of work.
Hi @troy-salt
I tried the OTA firmware update on WiPy from 1.20.1.r2 to 1.20.2.r7 using OTA firmware update example and the update worked fine. Please refer to this example (https://docs.pycom.io/tutorials/all/ota/) for the exact steps to perform an OTA update.
The image file that you have in the flash seems to be corrupt. Make sure that the file is written correctly.
@brugues isn’t this using Classic Bluetooth rather than Bluetooth Low Energy (BLE)?
Even though the ESP32 supports both, I believe Pycom firmware only supports BLE.
@plsecker Can someone just post the Callback url they have for a Sigfox device?
Mine (above) has been provisioned as:
https://sigfoxbridge.pybytes.pycom.io/sigfox/callback
(its listed under Devicetypes|Callbacks).
Bit bemused as to the lack of help on this. No response from Pycom either.
