T-Lora / T-Beam / can not connect or set anything

Support
1

Dear Meshtastic Community

I’m out of ideas. Since days I’m trying to use my new hardware T-Lora and T-Beam with Meshtastic. But I can’t manage to get it going. I’ve searched the on the Meshtastic Page, here in discourse, GitHub…no luck. So here is my problem:

I’ve successfully flashed meshtastic 1.3.41 via windows / cmd / meshtastic-flasher on to my T-Beam V 1.1 while setting it to boot-mode by connecting GND to Pin0. (cmd as Administrator, Flasher can find the Port) I can see in the cmd-line that the flashing is successfull. After the flashing I restart the T-Beam and I can read the firmware version 1.3.41 on the display. The display is telling me to connect via App, CLI…to set the region. From there the problems start:

  1. I’m not able to do the configuration via meshtastic-flasher. when Device Settings is clicked I get the message “Timed out waiting for connection completion” in comand line tool. For me this is strange, because over the same COM Port I can flash the device. Same thing happens if I try to get information in cmd with CLI meshtastic.exe with meshtastic --info. Also any other thing than flashing does not work.

  2. If I try to connect my T-Beam with flashed 1.3.41 Firmware to my Samsung Note 20 Ultra (Android 12, Meshtastic App 1.3.16 Sideload APK with permission for Location set to allways and devices near) I can pair my phone via meshtastic app with the T-Beam. The T-Beam is showing me the code to connect. From then on strange things happen: The App ist showing me, that I’m connected with my T-Beam. I can set the name for the node and the region. But nothing happens. The T-Beam is allways telling me on the display to connect and set the region. I’ve tryied with reseting / restarting the T-Beam, restarting App, deleting cache, reinstalling App, Installing newes App version via APK…no luck. After a while, I can’t even connect anymore via Bluetooth when I choose the right node in the App. The cloud sign never show connection anymore…

I’v done the above with two different T-Beam, both new. And with a T-Lora V 1.1. Allways the same result. I’ve also tryied with a different android phone (with app from playstore)…Sometimes the devices connect to the phones and a can give node names and set the region, but the devices don’t accept these settings…

Pls beleve me, I’ve spent many hours reading and trying to find the solution by my self. But I’m out of ideas by now.

Maybe someone here can help me. I’d realy aperciate that!

2

You need to use the matching android app, there were breaking changes in 1.3.41 so previous app versions are not compatible Release Meshtastic Android 1.3.41 alpha preview · meshtastic/Meshtastic-Android · GitHub

3

Thanks a lot! This now worked with my phone! I’m so stubid, sorry.

But I still have the problem with settings in the flasher. I can flash, but not connect via COM Port and change any settings.

Maybe you have a solution for that too?

Thanks garth!

4

The only setting in the flasher now is region, you can use the CLI, iOS or the web UI to do more comprehensive settings updates. Android lets you set region and channel settings.

5

Hi garth

Thanks for your answer. But in the flasher I can not even set the region. In CMD I can see that the flasher is trying to open the correct port but it ends with a timeout. Same when I try CLI. When I enter
with GND and 0 connected in Bootmode

meshtastic --port COM6 --info

I get: Exeption: Timed out waiting for connection completion.

Flashing is working, any other commands don’t work. I’m sure I entered the correct port because I double checked in windows device manager.

Maybe you have an other good hint? I have red this entry:

Could that be the problem? Until now I’m not skilled enough to change this setting…

Thanks in Advace

Ps: here my CLI meshtastic --support output

System: Windows
Platform: Windows-10-10.0.22000-SP0
Release: 10
Machine: AMD64
Encoding (stdin): utf-8
Encoding (stdout): utf-8
meshtastic: v1.3.29
Executable: meshtastic
Python: 3.9.13 CPython MSC v.1929 64 bit (AMD64)

6

Hi garth

Never mind, I got it working with the newest Meshtastic Python 1.3.36

and the device not being in boot mode…

Thanks a lot for your help dough!