this post was submitted on 24 Aug 2024
87 points (98.9% liked)
Meshtastic
334 readers
1 users here now
A community to discuss Meshtastic (https://meshtastic.org/docs/introduction)
founded 11 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Check out mqtt until you get nodes around you, the main channel will bogg down a heltec v3 but you should be able to find one for your city/state/area.
But chatting through the internet kind of defeats the point imo.
Also I tried to connect to mqtt but it did nothing. Do you have instructions for dummies how to set it up? I used the meshtastic module config docs and it didn't work ^^
You have to make sure uplink and downlink are enabled in the settings on your long fast channel, then enable mqtt in the mqtt settings and turn on "proxy to client enabled".
The main root topic in the mqtt settings is msh/US/ you should get plenty of nodes if you connect but if there are to many it will reboot your heltec after a while. I connect to my city's root topic at msh/US /IN/Evansville and only have 4 to 6 other nodes. You may want to try the main channel or my local just to make sure it's working then try and find your local mqtt root topic.
You usually can check meshmap.net to see what root topic people are on around you but it seems to be down right now. You could just try msh/US/State/City if you're in the us.
I am in Germany. I would like to find a root topic for Berlin :)
Thanks I'll search around.
Looks like a few in Berlin are on msh/EU_868/2/map/ from
https://meshmap.app/?lat=52.530216577830124&lng=373.37997436523443&zoom=12
Thanks. Where did you get the channel from? "Show full details"?
Yup on the green ones.
Defeats the purpose a little bit, but MQTT can fill the gaps to ensure practical use until it’s unnecessary anymore. That’s the goal!
Hmm not sure I like that. Apparently the default channel has too much traffic to be handled well by the esp32 devices.