[Bug]: T-Echo Plus braked menu

[Renboo]

Category

Hardware Compatibility

Hardware

T-Echo

Is this bug report about any UI (https://meshtastic.org/docs/configuration/device-uis/) component firmware?

• Meshtastic UI aka MUI
• InkHUD
• BaseUI

Firmware Version

2.7.26.54e0d8d

Description

Hello!

I have updated my T-echo Plus to 2.7.26.54e0d8d Beta. It started correct and i have used menu. But sometimes late it was rebooted by themself and after that i have non working menu: no button combinatios could help.
Reflashing do not help.

Other problem is battery charge level display. It shows random, then selfreboot and then random. Finally it was discharged ~ after 48 hours and did not start.

Please help me to correctly collect a log if you need it.

Relevant log output

[github-actions[bot]]

@Renboo, Welcome to Meshtastic! 👋

Thanks for opening your first issue. If it's helpful, an easy way
to get logs is the "Open Serial Monitor" button on the Web Flasher.

If you have ideas for features, note that we often debate big ideas
in the discussions tab
first. This tracker tends to be for ideas that have community
consensus and a clear implementation.

We're very active on discord,
especially the #firmware and #alphanauts-testing channels. If you'll
be around for a while, we'd love to see you there!

Welcome to the community! ❤️

[Renboo]

Found ERROR that happens sometime:

�[0m�[34mDEBUG �[0m| ??:??:?? 256 [Router] �[34mUse AES128 key!
�[0m�[31mERROR �[0m| ??:??:?? 256 [Router] �[31mCan't decode protobuf reason='wrong wire type', pb_msgdesc 0xc5bbc
�[0m�[31mERROR �[0m| ??:??:?? 256 [Router] �[31mInvalid protobufs in received mesh packet id=0xcc9ea6ae (bad psk?)!
�[0m�[33mWARN  �[0m| ??:??:?? 256 [Router] �[33mNo suitable channel found for decoding, hash was 0x1f!

Need other kind of logs to show that menu does not work anymore.
And there is no chance to collect logs of battery problem with connected type-c.

meshtastic-log-2026-07-18T07-48-37.945Z.log

[caveman99]

That is not an error, you are receiving incompatible packets or packets you don't have a decryption key for. We need a log from the actual moment your device resets and reboots.

[Renboo]

1. I think the firmware is having a problem with the battery. How can I collect logs without powering the battery? Any ideas?
2. What logs can I collect to show the broken UI menu?