-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
T-Echo nonreactive with red LED pulsing #47
Comments
Rescued the device with the following steps (only this exact order of steps seems to work):
But then 3 days later, the same thing happens again and the T-Echo becomes nonreactive. Do I have a defective device or are these known issues? |
Same with the latest stable Meshtastic firmware v2.4.0. |
Same situation with the two T-Echo devices I bought straight from Lilygo a couple weeks ago. Erased, reflashed. They work fine for maybe a few days, then corrupt themselves again. They're pretty much $50 paperweights, currently. One was intended to be a mobile solution, but I can't even rely on it enough to take it with me. |
I've had mine a few weeks and havent had this issue. |
I have the same - bought 2 pc, one works just fine, the other froze just the way you describe. It seems to me from the description it's just the firmware though? |
My T-Echo with Meshtastic 2.3.15 was running fine but in the middle of the night it just froze. No more Bluetooth connection and the device doesn't react to any button presses. The display just shows whatever it showed when it froze.
The left of the two red LEDs makes two pulses every 5 seconds and that's it. I tried the following without success:
.uf2
file, disconnects, and nothing happens.Any idea how I can rescue the device?
The text was updated successfully, but these errors were encountered: