@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 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.
@Nils-Erlands this might be browser related... What browser are you using and what version? I'm using current Microsoft Edge (Version 95.0.1020.44) withouth any issues.
@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
@Ryan-Keeffe Please turn on debug like this:
import pycom; pycom.nvs_set('pybytes_debug', 99)
then reset and try again and paste the output. Please check and remove passwords before posting
An update:
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.
You can look at this page: https://docs.pycom.io/pybytes/api/ to start pybytes manually. Set pycom.pybytes_on_boot(False). You can first setup the connection and for example check different SSID's, and when connected, call the code in the top codeblock to actually start Pybytes
@BetterAuto said in Pybytes with custom firmware?:
or am I required to use the pycom.ota_start() method?
Concerning the pycom.ota_start it is not required to be used.
If you want to implement this yourself please take a look at the below reference.
Reference: https://github.com/pycom/pycom-libraries/tree/master/examples/OTA
Ah, here is the reason. "WiPy2, SiPy, and LoPy1 and are not supported anymore since they only have 4MB flash." That was unexpected because the latest non-beta firmware works fine, but I knew this was coming some day.
Also, "No OTA support from Pybytes yet"
I tried with the updater and it says, "Your hardware is not supported by this firmware package"
https://forum.pycom.io/topic/7016/new-beta-release-v1-20-3-b3
