Are yuo unable to install? Read this

[ktomy]

THere are some cases where people are unable to install the firmware. If you experience an issue installing the firmware, just try doing it using a different computer. See an example here: #55

[ktomy]

Another instance: #58

[ktomy]

Actually, I think this is not about a different computer, but about bad hardware design. I did not disassemble the clock, but I suppose that what happens is tht one of the pins is not connected properly (not grounded) and ths makes programming the device unstable. Initially I thought that the problem is with my particular device, but the amount of people saying they have intermittent issues is too high so that I can think of only my device to be affected.
How I solve the issue for myself, is through simple retry. Well, I have automated the retry logic, but for people flashing the device from the installation web page, a manual retry should work. Just retry for 5-10 times, maybe it will work. If not, use different usb port, usb cable or a different computer.

[pressdarling]

Glad I found this discussion - I hadn't updated since 0.14, when the USB cable I'd been using to power it (quite long, USB A-C) kept running into issues that I couldn't figure out from either browser console logs or code in the repo.

@ktomy I might create a PR with some basic docs that can be linked to from the installer page + readme - let me know if you have anything you've wanted to document specifically, otherwise I'll sweep the codebase, issues, PRs, and discussions for anything worth covering.

[ktomy]

Hi,

I would be very happy for any help with the documentation.
As of now, the biggest challenges people experienced were around installation and connecting the clock to various (non-classical) data sources (gluroo/juggluco).
So feel free to create any amount of documentation, setup and connection guides are especially welcomed.
There are already a few videos with this, but written documentation is always helpful.

Thanks a lot for your intention

[ktomy]

and if i dont have access to another computer ? also tried all ports and different cables

As I said earlier, I think this is actually a hardware issue of the clock, there is one ESP32 pin which shoud be pulled up (or grounded?) but it is not. As a result, flashing is unstable.
I also experience the same effect. In order to overcome this I wrote a script which retries flashing if it fails, sometimes it works out from the first try, sometimes it retries for 5-10 times.
So, my advice in this case would be to just retry for 10-20 times, it should work after some retries.

Thank you.

[ktomy]

There was another thread on this, its conclusion is "Use USB 2.0 ports" (meaning not to use USB 3.x or 4.x)

[mstry9]

Just mentioning I always had trouble on my new HP laptop but I ended up getting a cheap 2.0 USB hub and plugged the clock into it. No problems since then. Flashing and development installs work every time now.