@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 now completely re-activated and flashed the GPy again, but this time did not load any program and after resetting the GPy, it still hangs on the initial watchdog with no program and whatever pybytes_config.json file it initialize with.
I am only setting up an LTE connection in the provisioning to hologram with band 4, carrier standard, and CID 3. These are the same settings that I have been using for months.
No Pybytes will not transmit location unless you request that under Pybytes.
basically, we use this to identify some actions on Pybytes section for example sending a location command. the pin is used to know which pin is used under this command (also can be used as an identifier a random number)
The part that holds the message details is the payload.
Ahmad EL Masri
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)
It indeed seems to be related to the DNS server not being set correctly by the Vodafone service. You can manually set the DNS server by using:
socket.dnsserver() #this should return empty
My colleague @Xykon can tell you more about the DNS server IP address. It has to be specific to the pycom servers (so setting 22.214.171.124 as the dns server should not work)
I would like to add a constructive criticism. I really like the Pycom's products, but several times I have also felt like something is missing in the documentation. Sometimes it is the way it's organized, not so easy to browse it, other times some details are missing to quickly understand how things are working/designed or how should be configured, and sometimes it's not updated. In some way, I agree with this comment: "It sounds like you should do an audit of all your documentation". I know that I'm not the only one, I have read other people saying this kind of things.
Pycom products are great, but you have to make your documentation easier to read, add all necessary details, do not assume that your users know all the internal details that you know. You have to create documentation as great as your products.
@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.