Received 2 T-Echo today after a good wait. Both appear to be running meshtastic 2.01. I attempted to use the drag and drop method to update one of them. connected with no problem, dropped the correct file , device states “hutting down” on the screen , red led on the left is lit, just stuck here. Wont reboot and will not connect to bluetooth. Closely followed instructions to flash with Arduino , T-Echo/firmware at main · Xinyuan-LilyGO/T-Echo · GitHub.
Instructions say open the sketch, where is this sketch? And how do I proceed?
here is the boot loader listed in the info file UF2 Bootloader 0.6.1-2-g1224915
after dragging and dropping the latest uf2 file when I bring up the device it still shows current UF2 date to be from 2021
Pulling the battery for 30 minutes seems to do nothing
I have tried the factory erase uf2 file and the 2.01 factory firmware, files appear to be transfering but the t-echo disconnects from computer around 80%, reboots screen still says “hutting down”
this is far as I seem to able to make it following the guide on setting up t-echo, have python and pip 3 installed meshtastic —noproto yields the following
Microsoft Windows [Version 10.0…
C:\Users\Overlord>meshtastic --noproto
WARNING file:mesh_interface.py _sendToRadio line:737 Not sending packet because protocol use is disabled by noProto
Connected to radio
WARNING file:mesh_interface.py _sendPacket line:579 Not sending packet because protocol use is disabled by noProto
Well I have successfully flashed with latest meshtastic update, app on ios sees the radio but will not connect, followed the full erase and installed 2.01 no ability to connect either
Just to be clear, this time I don’t mean using the webflasher to erase. There’s a serial monitor button on the website, which will open a window showing diagnostic output from the device in real time (hopefully)
yes it attaches to the device thru the serial monitor, has no error messages, just one line with power status followed by a screen refresh line, both seem to update every 10-15 seconds.
My current issue since complete wipe and reinstall of the firmware it shipped with, 2.01 is that it will not connect to the app. The app sees the avail radio, when I click connect it goes thru the attempt to connect, 1…2…thru 10 , and then restarts the countdown without ever connecting.
after being monitored by serial monitor for about 10 minutes its receiving pings from other nodes with no problem and then the following warning has popped up
not comfortable enough with python to change that way, and cant connect to app to set region. I do remember a bug report recently about either t-echo or t-deck having bluetooth connection issues but I assumed after a full erase and reinstall of 2.01 this would not be a problem, had no problem connecting to app before 2.3.6.7
meshtastic --set lora.region US
or whatever region you’re in should be all there is to it. No risk involved, even if you set it to something completely wrong, you can just set it again.
On a hunch, is there any chance another bluetooth device has auto-connected to the radio? I spent a good hour pulling my hair out trying to figure out why one of my radios wouldn’t connect to my phone…it was working, but wouldn’t allow a BT connection.
Turned out my wife’s phone, which I’d been using as a tester, had automatically latched on to the radio in-question.
Sometimes it’s the simple things…which are, all in all, better to be up against than the difficult things!
Thanks, that worked well, no other bluetooth devices on that I can find, I have powered down the other 2 nodes close enough to be a problem.
Whats weird is I no longer see the radio in the list on meshtastic app, but the apps enters an endless loop of trying to connect as soon as the radio is turned on ,currently going on 20 minutes of counting 1-10, quick red flash of unable to connect , then attempts again, seems to never end, even when I turn on other meshtastic devices, Only way to break the endless cycle is to power the t_Echo down
The device will recieve message from other devices, just cant connect to send]
After going thru the motions a few times I determined I was left click highlighting then copy and pasting important bits that have buttons on the right to copy, as a result I was botching the convert rak step. Self induced problem LOL.
On the plus side I have learned a bit about commands from control line . Thanks for all the help, great community and I look forward to learning more.
