Meshtastic Device 1.3.30 alpha - Public Preview

We’re getting close! Can you feel it?

Reminder: This is not for the faint of heart. You will likely have problems. More information on how to use this:

4 Likes

I was able to get it connected to MQTT, now lets test… :smiling_imp:

2 Likes

Presently, this seems to have bricked all of my T-Beams…

Since installing this FW I can’t get any of them to turn on. External power doesn’t bring them to life, nor pressing any of the buttons.

hmm

What is the version of TBeams you have as the newer ones are based on AXP19x and this one will turn power on regardless of ESP32 FW. AFAIR, it has its own LED

Really hard to brick an esp32, are you sure the 1.1 firmware installed?

1.1 firmware?

I installed firmware-tbeam-1.3.30.9fe2ddb.bin

All four of my T-Beams are now dead.

I’ll try again.

There are two tbeam hardware variant firmware files 1.1 and .7

Ah yes - thanks.

I have now reflashed two of mine with 1.3.37 and they work.

I get one way messaging, as before.

From iOS the messages are sent, show up on the opposite T-Beam’s screen and show in the Android app.

There is no ACK in the iOS app.

Messages in the other direction, Android to iOS, don’t send (get a cloud with a line through it), don’t show up on the opposite tbeam and don’t show in the iOS app.

With two Android devices I get the following behaviour:

Sending messages from either device shows on the opposite T-Beam’s screen - but never shows in the Android app.

There is no ACK transmitted back - so messages never get a tick icon.

What could cause this?

1.3.38 solves my issue. I get two way comms and ACKs.

Range tested to 2.2km from my dining table on the first floor - with me walking down the seafront/ promenade. I’m pretty happy with that.

Now I will order some different antennas and see if I can push things further.

Does anyone know what power output the latest firmware uses when in 868 MHz mode? I know a couple of us found that it was permissible to use 500 mW but I wonder if that change was actually made? (Assuming a T-Beam can even output 500 mW?)

(It’s a shame 1.3.38 came out the day after Boomtown Festival. Meshtaastic would have been ideal for that! The cell networks were completely maxed out, SMS/ WhatsApp message were taking hours to get through. If I had had working Meshtastic there it would have been awesome! Ah well, there’s always next year!)

Now that device is working so well, can we make the screens more readable?

  • important stuff gets rendered at the unreadable edges of the screen
  • the font is very small
  • most of the screen is unused. Even the most busy screens don’t use half

I find with the t-echo I often have to turn it to get the edges out of the shadows and can’t read it unless I’m holding it. It would look so much better if it used that whole screen (but not the edges) so it could be read across a table. I very often want to put one at just a little distance and still see what it’s doing.