search

pycom / pycom-documentation

Pycom Official Documentation for WiPy 2.0, Wipy 3.0 LoPy, Lopy4, SiPy, FiPy, GPy, etc.
https://docs.pycom.io
36 stars 81 forks source link

Pylife #494

Closed Xykon closed 2 years ago

CLAassistant commented 2 years ago

CLA assistant check
All committers have signed the CLA.

aws-amplify-eu-central-1[bot] commented 2 years ago

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-494.d1rmdw1xyxqk1e.amplifyapp.com

idea--list commented 2 years ago

I was trying to follow the description, but in reality today nothing works as advertised on this page. For example this page states, one should fully charge the device before doing anything. Well maybe am just not brave enough to do so, as my PyGo gets extremely hot and also on the forum we get the advice not to fully charge the device before upgrading the firmware.

Another thing that is not on par with this page: Using the latest PyLife app for android downloaded today from google play to my Samsung Galaxy S7 i can create a pylife account, can also log into that... i can BEGIN adding a device by clicking "Add device" and then tapping "Start scanning" button. My phone also finds a PyGo device and suggests a name, but all the goodness stops here as i simply can not type anything that would be accepted by the app. All i get is a NOT_VALID_DEVICE message when i tap the "Add PyGo" button. Now i wonder what i might be doing wrong or how this all has been tested? Or has it ever been tested on an Android device?

Another discrepancy in the FAQ part:

Your PyGo is an always on device. You can wake it up by charging it, or by double tapping the screen.

Well, my PyGo2 does not turn on/activate when i double tap it. Maybe i just can not do it right. What about a youtube video about what you mean by double tapping? The only way it wakes up on my side is to place it on the wireless charger. However even that does not work for my PyGo1... so there are a bunch of things to sort out in the doc.

I am getting torn by this project as was waiting for so long. Can also understand HW related delays, but i get the impression you are simply not fit to come up with a documentation that is on par with how the delivered devices work. You might pretty much have an intention how these should work, but in reality i can not even start using both my devices. My PyGo1 is completely unreactive to anything, the PyGo2 does at least charge on the pad, but am not able to provision that device because the Pylife app seems to be buggy. Have no idea how i will succeed with FW upgrade. The only thing that seems to be positive that also Nordic nRF connect app can find my PyGo2 when doing a scan, so there is some hope you can fix your app.