@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.
Discussion for Feature Request and Future Additions to Pybytes
yes, new chips are really interesting. Reading draft version of docs are promising.
As they send some testing parts already i suppose full delivery and final version of docs will be really soon.
I am really interested if ADC will be better in new chips ;-)
Is someone able to answer the question above? I'm not sure if I have this problem, also. When I click on one of my active 1NCE SIM in pybytes I get an error message: "GraphQL error: Cannot return null for non-nullable field SimCardNCEDetail.iccid". What is the problem? Please help.
I had the same issue few days back. I found that sometime it works and sometime it doesn't. Also nowadays i started using Pybytes ios app based method. It working perfectly fine for me. Also I was getting 401 error some time back. I have no clue what it was.
@Stuart-Gall Hi Stuart. There is an issue with how filenames/folders are handled. This will be addressed in the next release, but for the moment please make sure filenames have a dot like main.py or config.json and foldernames do not have a dot, like lib or whatever. Unfortunately things can go wrong with files like README, or folders like .git
Thank you for the offline support. To give an update for the community to benefit from, the reason for the failure was due to a special character in the python file not covered by the ASCII format. The advice was to use only ASCII format in all the text/python files.
I am sorry, forgot to post the solution.
I even had a quick skype call with one of the pycom developers.
Yes the solition was the same for me also. I renamed the file mqtt.py to something else like mqttclient.py, and it solved the issue. Somewhere deep there is a mqtt.py file in the pybytes firmware. That caused the issue.