@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.
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
@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.
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.
@jcaron I am sure that the callback works, I have gotten into the callback when using the nRF connect app as a server and sending notifications with that server. However after further tracing, it seems that I cannot properly subscribe to the NOTIFY characteristic. To subscribe for notifications it seems that you have to send a value to the descriptor, not the characteristic as I have been trying. The same problem got mentioned here: https://github.com/pycom/pycom-micropython-sigfox/issues/37, although it is still not clear how to write to the descriptor. Is there any way to write to the descriptor?
@plsecker Can someone just post the Callback url they have for a Sigfox device?
Mine (above) has been provisioned as:
(its listed under Devicetypes|Callbacks).
Bit bemused as to the lack of help on this. No response from Pycom either.