While the system is performing the initial updates, you should tell users to use the power cord. I think mine quit charging while updating and got stuck in a boot loop due to battery low. once I connected to the hard line it completed updates.
I’d much rather they just let you check for updates manually and initiate them on your own rather than waiting for the magic script to kick off. It also shouldn’t update if the battery is below a certain percentage.
5 Likes
Hi there, thank you for the suggestion. I’ll share this with our team for consideration.
2 Likes
My yarbo was fully charged and sitting on the pad.
It’s normal for it to do a few rounds of updates. Has a lot of stuff internally to update and a few firmware versions to update through initially. Can take 30-60 mins for it to complete the full process once it’s connected to the internet. Did it take longer than this? It also does stop charging during the update process. Some updates it won’t immediately start charging again and eventually will around 90% battery.
1 Like
I left it on the base over night, have no Idea when the update started or applied. My wife heard it and saw the lights on around 5 am it was still doing reboots every 5 minutes at 8 am. I checked it then and received the board disconnected error, battery showed zero but I did not know if that was a symptom of the board problem. I did look to see if charging was active the base showed blue. I started a ticket, and about an hour later disconnected the battery while waiting for a response. The next day engineering told me to use the line charger, within 2 hours it seemed to be working fine and I switched back to the pad. No problems since.
2 Likes
Interesting. Sounds like they fixed it remotely somehow then.
1 Like
I’m sure the battery level was part of the issue, remote intervention is possible but not likely while it was in the boot loop.
1 Like