We definitely have plans for more videos like these, although we haven't decided on the specific topics yet. You're not the first person to ask for MQTT though, so keep tuned it could be coming!
Hey, I only discovered Meshtastic a few days ago, but I’m already spinning this stuff up as a group project for my local community. I’m not sure you really appreciate what you have started. I cannot see where this ends, perhaps replacing the internet for example, but the sky is the limit, and the application is pretty much everything. A framework for an internet of everything. I will be pushing my software friends in Seattle to look at this. Otherwise, you need to be careful of government big tech and media. They may see what I see.
@@cheekybastard99 Don’t be so sure. Most people prefer text over voice for general communication. AI doesn’t require high bandwidth. People are sick of search, sick of bills, sick of big brother.
This is nice and simple but also quirky as shown at 3:15. As a test I ran traceroute requests in a loop for hours from the CLI with 5s sleep between every call. Sometimes it'll succeed many times in a row but it's more common for it to fail 2 to 10 times in a row with each failure taking about 30s to time out. All my nodes are in the same room, I have 4 nodes with low 5% utilization, no mqtt, in a very rural area with near zero external traffic or interference. Is this normal? I'm looking for something akin to a ping where I can tell if a node is alive from the CLI or python, any recommendations?
Would trace routing be a good way of testing the db returns on antenna or radio outputs at 2 locations with gps on. Or is "range testing" a better option? Which i havent gotten to work yet.
Indeed there is! You can select "Client Proxy" to connect via your client's internet connection rather than using the device. This enables you to essentially use any device for MQTT.
Just wondering why traceroute does not indicate MQTT itself as a hop? That would be useful to know there is no direct RF link. MQTT itself is after all also a hop.
The "hop" is specific to our version of BATMAN protocol we implement for the mesh layer, but your intuition is correct that this information could be important. Please open a feature request: github.com/meshtastic/firmware/issues
Are you able to communicate with the device you are trying to trace route? You might be in a position where your device can receive from that node but your messages to them are having trouble getting there.
Traceroute module has been very helpful in understanding how our local mesh works in a dense city environment. Thank you!
Great video! Could you please share a MQTT config video? Thank you for thr great work! I have 6 devices and I'm spreading Meshtastic across my town.
We definitely have plans for more videos like these, although we haven't decided on the specific topics yet. You're not the first person to ask for MQTT though, so keep tuned it could be coming!
Echo mqtt pls
MQTT 👍
Hey, I only discovered Meshtastic a few days ago, but I’m already spinning this stuff up as a group project for my local community. I’m not sure you really appreciate what you have started. I cannot see where this ends, perhaps replacing the internet for example, but the sky is the limit, and the application is pretty much everything. A framework for an internet of everything. I will be pushing my software friends in Seattle to look at this. Otherwise, you need to be careful of government big tech and media. They may see what I see.
This isn't going to replace a carrier.
@@cheekybastard99 Don’t be so sure. Most people prefer text over voice for general communication. AI doesn’t require high bandwidth. People are sick of search, sick of bills, sick of big brother.
@@memyselfandi8544 I say this due to the limited node size.
Great video again, Ben! Very informative.
Great video, thanks!!
It would be cool if you could see the traceroute on the map (gps must be on)
MQTT Tutorial would be greatly appreciated.
While there's no current plans for a MQTT specific video, we're definitely making plans to create more videos like these so keep tuned!
@@Meshtastic ok thanks really like the videos you've made so far. Keep up the good work.
This is nice and simple but also quirky as shown at 3:15. As a test I ran traceroute requests in a loop for hours from the CLI with 5s sleep between every call. Sometimes it'll succeed many times in a row but it's more common for it to fail 2 to 10 times in a row with each failure taking about 30s to time out. All my nodes are in the same room, I have 4 nodes with low 5% utilization, no mqtt, in a very rural area with near zero external traffic or interference. Is this normal? I'm looking for something akin to a ping where I can tell if a node is alive from the CLI or python, any recommendations?
Yes, the parameters you describe would lead to a lot of issues and is not how this is meant to be used.
I would love to see a video about mqtt!
It's on the list of future videos!
Would trace routing be a good way of testing the db returns on antenna or radio outputs at 2 locations with gps on. Or is "range testing" a better option? Which i havent gotten to work yet.
That is very cool. Is there any way to connect a phone directly to a Meshtastic MQTT server?
Indeed there is! You can select "Client Proxy" to connect via your client's internet connection rather than using the device. This enables you to essentially use any device for MQTT.
Just wondering why traceroute does not indicate MQTT itself as a hop? That would be useful to know there is no direct RF link. MQTT itself is after all also a hop.
The "hop" is specific to our version of BATMAN protocol we implement for the mesh layer, but your intuition is correct that this information could be important. Please open a feature request: github.com/meshtastic/firmware/issues
@@Meshtastic thank you. OK I did log but under the Android app on the project. Should I rather close that and log under firmware?
@@GadgeteerZA No worries, I found your report and moved it. Thank you!
So this is the outbound route that is traced then ? Each hop responds and the originator compiles the trace ?
What if every time I try traceroute I get nothing back? What am I doing wrong?
Are you able to communicate with the device you are trying to trace route? You might be in a position where your device can receive from that node but your messages to them are having trouble getting there.
single quotes for linux/mac '!bff18ce4', no quotes for Windows !bff18ce4
Yup! This is accurate!
Thanks!