Things are working really well with my Lillygo T-Echo until I enable MQTT on the default primary channel, using mqtt.meshtastic.org, and enable uplink and downlink on that channel. Then, the T-Echo basically becomes unresponsive. I cannot even use the serial port to get logs. I imagine the poor thing is just getting overwhelmed with messages, but I am wondering if this SHOULD work, or should I just change to Long - Slow and live with that?
I have the same issue on my T-Beam. When MQTT is enabled it becomes largely unresponsive. Have to press the reset each time to be able to log in and disable MQTT.
Has something changed in the past week?
Yeah, the traffic on LongFast has increased considerably recently. There’s now a warning in the documentation that your device may get overloaded. Indeed changing to another channel is the best option.
Thanks! That makes perfect sense. Since there are not a lot of Meshtastic nodes around where I live (yet), I wanted to test this out. Is there a good secondary channel or MQTT server to use for testing?
How did you connect your T-echo to internet?
as i know it does not have wifi.
You can use the proxy option in the MQTT tab.
Any suggestions as to what channel to use? I don’t want to overload the device, but I’d still like some contact 
ok, i see, using the phone :
Last time I tried there was some activity on LongSlow and it could handle that. But this might change in the future though.
You can see all the traffic using MQTT Explorer. I just opened it and these channels popped up:
If I leave it open for longer, more will appear.
1 Like
Thank you very much for your help! MQTT Explorer is very helpful. If I understand correctly, if I want to use one of those topics, I set my Lora Preset Config to the names in explorer? i.e., if I wanted NJ, I would set my preset name to NJ?
You can leave the LoRa preset config the same, but change the channel name. But indeed for the default LongFast preset, the channel name will also be LongFast.
Note that some of these channels may use a different encryption key than the default.
Ah, that makes sense. So “PRIMARY” uses the name LongFast by default? Also, yikes, the LongFast is SUPER busy. No wonder it overloaded my poor T-Echo.
I had the default channel,msg. My device didn’t appear to handle the influx messages. Looking at the Debug Panel I was getting 40+ messages/packets per second. Is this a lot ?
2 examples
That will crash quickly
Yup . Sometimes in minutes, sometimes I’ll get 30 minutes. It’s a petty we can’t offload this to a local server that had meshtastic running on it.