Getting started with PyGos and Pylife

[Alberto Fassio]

I received my Pygo two days ago. It does not charge nor configure. Impossible to load new firmware even from cradle. Unusable

[robert-hh]

@Alberto-Fassio When placed into the cradle, it may take an hour or more until it starts charging the fist time. The devices seem to arrive with a completely empty battery.
You could check in the cradle & device, if the contacts are clean and correctly aligned.

[Timothy spann]

My screen never says hello. It seems to be charging with the bars going up and blue light on the charger

[thinginnovations]

I'm getting the same battery charging bars after charging the devices in my makeshift holder. They both show 100% via the app, I try to set the LoRa band but this cannot be set for some reason, even though the PyGo are showing as connected.

I try to wake the Pygo with a double tap but they either show nothing or just the battery charging indicator. I can get the REPL to show when USB uart adaptor is connected.
I was able to issue reset() and see the device restart and that's about it. No change to display. Is the current firmware still not working?

Regards

Andrew

[robert-hh]

@thinginnovations If you have a USB terminal window open while trying someting in the APP, you'll see error messages about faults in RPC.
I never got the app to show the battery level.
So no, the devices are not useful for anything at the actual state. But maybe Pycom is working at bringing some functionality to the device. Maybe not.

[thinginnovations]

@robert-hh Good call, thanks.

I do get this now when trying to set LoRa frequency:

>>> Client connected
{}
Traceback (most recent call last):
  File "_ble_rpc.py", line 236, in feed
  File "_ble_rpc.py", line 236, in <listcomp>
  File "_ble_rpc.py", line 253, in resolve
AttributeError: 'RPCHandler' object has no attribute 'set_lora_freq'

Going to try a few more things.

Cheers

Andrew

[thinginnovations]

Also, while viewing the output I see the same error repeated :

>>> Traceback (most recent call last):
  File "_ble_rpc.py", line 236, in feed
  File "_ble_rpc.py", line 236, in <listcomp>
  File "_ble_rpc.py", line 245, in resolve
TypeError: 'int' object isn't iterable

Guessing there are some incompatibilities between the app and the firmware.

Cheers

Andrew

[Whatamiseeing]

@thinginnovations Fuck it, why are you doing Pycom's job fixing this mess?

[Alberto Fassio]

@robert-hh I have charged the Pygo all the night. It does not work!!!

[robert-hh]

@Alberto-Fassio That's not good. So something is broken:

• the PyGo
• the cradle
• the cable to the cradle.

Do you see a com device for it when the the cradle is connected to the computer? The com device is created by the cradle itself.

[robert-hh]

@thinginnovations Every few days I have another short look at the PyGo & PyGo App. Yesterday I noticed that there is a new version of the App. SO I loaded it.
The only change I could notice was the change in the version number. No additional feature, not better interaction with the PyGo. The PyGo are still discovered, when being fully charged and close to the phone, unless they were set to "eco" mode. No setting of LoRa mode, no display of the charge state.
The only function that works reliably is: "Forget the PyGo"

[Keptenkurk]

The only function that works reliably is: "Forget the PyGo" 🤣 LMAO you really made my day!

[exa]

@andreas58 I'm interested, what did you use to connect to the pins?

[exa]

I've realised that there's a Specsheet that contains quite a bit of information in the Getting Started page

It shows the location of a sim car slot, but I can't see it on my device I'm wondering now if I got sent a PyGo1 in a PyGo2 box
@Gustav-Hilding

[robert-hh]

@Gaetan-Gueraud There is no SIM card slot at the final design. The SIM is built-in, it's said. I faintly recall, that was mentioned in one of the posts aiming at IP67 certification.
Which SIM and which service level is unknown, but only matters when the device are working eventually.

[exa]

@robert-hh Ok so then the app is also missing the Esim configuration then..

Does it actually charge with the cradle? Can you do something with it?
I didn't get a cradle because I assumed it came with some sort of charger and now I can only charge with QI which as I've read and found out doesn't actually charge.
The location doesn't seems to update on the app.
Overall the product doesn't seem to work and I'm considering asking a refund under the EU consumer rights.

[robert-hh]

@Gaetan-Gueraud The device charges in the cradle. Using the cradle, you can connect via USB and get a REPL prompt abd use it like a generic esp32 device. You can as well update the firmware.
When trying the APP, you will see at the serial console error messages, which demonstrate that App and PyGo firmware do not match.
I could not tell whether the PyGo2 connects to LTE or LoRa or gets a GPS fix.
At the moment, The PyGo seems pretty useless, and there is no communication from Pycom about fixing the firmware and making the devices work as promised.

[thinginnovations]

@Whatamiseeing Not fixing anything, just showing there is a problem.

[thinginnovations]

@robert-hh I saw there was a an app update, so tried it. No change.

Thanks

Andrew

[robert-hh]

@thinginnovations Looks like I managed to kind-of-brick my PyGo2 by calling ntp_on_boot(). Now it reboots every minute, and shows an error message:

>>> Traceback (most recent call last):
  File "_main_pybytes.py", line 78, in <module>
TypeError: can't convert 'NoneType' object to str implicitly

Maybe it tries to get a time, does not get one, there is no error handling, and boom! Firmware update does not help, since it does not erase flash to get in a new clean state.