45
Self-host Meshtastic Metrics in Grafana (roguesecurity.dev)
submitted 1 year ago by to c/selfhosted@lemmy.world
8 comments fedilink hide all child comments
 

cross-posted from: https://infosec.pub/post/32151664

This is a generic metrics post to leverage a spare ESP32 meshtastic node to ingest metrics into Grafana! We've had some congestion issues due to poor config in my area, and this has helped me pinpoint which nodes are causing the biggest problems, and block them at my repeater.

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 1 year ago (4 children)

Yeah its pretty spotty. A walky talkie would probably be better in an actual emergency. Im hoping meshcore or related projects will make it less spotty.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] [S] 2 points 1 year ago (3 children)

    Meshcore does address some of the biggest shortfalls of Meshtastic, but I absolutely HATE that they're positioned to either rugpull, or setup a perpetual "freemium" model. It's also not interoperable, so if Meshcore is to work, it needs the numbers like Meshtastic has.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 1 year ago (2 children)

    Agreed! I wish they could have worked with meshtastic instead of trying to get everyone off and using their project. Which is totally open source but not really.

    I think the next year or so will be interesting in the space. Im just sitting here with my little nodes making an impromtu weather station.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago (1 child)

    What’s the difference between the two? Reading the GitHub for meshcore, it sounds exactly like meshtastic. What makes it better?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 1 point 1 year ago

    The primary thing is rather than "dumb" flood routing, you can choose the path your message takes to its destination; as a repeater operator you can also choose the path it takes to repeat out. Its a slight compensation to people carelessly placing infrastructure nodes with poor configurations in poor places. Not perfect, but better. Adoption is much, much lower though, and the licensing is not copyleft.

  • permalink
  • fedilink
  • source
  • parent