This is the ticket we opened to keep track of this. We went through the rollback and saw that it was able to restore functionality by updating the OS and Controller after it was charged. Can you send us the serial number for the device as well as what version you are on and what version you were updating to. If you can try upgrading back to the latest version and see if the issue reoccurs as we talked about on the call?
The issue is caused by letting the controller charge drop below 5% on the latest os - 1.1.0-dev1.
Reverted the os to the previous version and the controller worked again.
updated the os to latest, updated the controller - was charged ~100% - seeems to solve the problem
I just wanted to follow up on this and see if you still required assistance from us. No response is required if your issue is resolved. We will close the ticket if we do not hear back from you after some time.