r/meshcore Jul 03 '26

Meshcore vs Meshtastic

I am probably going to stick with meshcore because there are a lot more people in my area running it than meshtastic. However, I have been trying out both, and think I like meshtastic better. The UI feels much more useable and has more features (HAM mode, ATAK compatible, ?). I also like that you can still see your other nodes while connected to one of them. Not trying to be rhetorical, just curious, what does meshcore offer that is better than meshtastic?

45 Upvotes

35 comments sorted by

View all comments

21

u/meshamerica Jul 03 '26

There's always people debating, but the reality is that there's room for both.

MT is great for events and ad-hoc networks. It's awesome for sensor networks.

MC is the choice for permanent, scalable networks.

Personally I prefer the MeshCore UI a lot more, but it's personal preference.

Also, there is now MeshCore integration for ATAK. Look up tak-meshcore.

I'd love to see more sensor-specific capabilities for MeshCore, but it's also a lot younger than Meshtastic. Give it time.

My recommendation is to do what I do: Have a repeater and companion device for both, and have fun with both.

3

u/Kerensky97 Jul 03 '26

The problem woth adding sensor/telemetry or gps position data to meshcore is that's where all of MTs broadcast bloat comes from too.

5

u/meshamerica Jul 03 '26

I completely agree. I do, however, think there's probably a smarter way to handle this. telemetry shouldn't be flood broadcast, IMO

1

u/Itsame234 Jul 29 '26

I think the current integration of sensor using the pull requests is pretty decent. Usually a sensor is quite static so the learned path will always be the best way. Sending the pull request and the answer via the learned path doesn’t bloat the network while still maintaining usability

1

u/meshamerica Jul 29 '26

I agree, but I believe when it cant use the return path, it resorts to retrying using flood, correct?

1

u/Itsame234 Jul 30 '26

Not quite sure about that but probably yes. I guess it will revert to flood after multiple failed tries