[adev_]

> Meshtastic routing is also completely broken.

I am curious about that.

What is in particular broken ?

Any reason why Meshtastic is not using a well specified / tested a mesh aware routing protocol like BATMAN [1] ?

[1]: https://en.wikipedia.org/wiki/B.A.T.M.A.N.

[wtallis]

I suspect protocols like B.A.T.M.A.N. would consume all available LoRa airtime just with neighbor discovery. On Meshtastic, nodes announcing their presence more than once per hour is seen as unnecessarily talkative.

I also don't think it's possible to make Meshtastic into the kind of reliable and high-performance mesh network some users want without effectively dropping support for most battery-powered devices by requiring much more frequent transmissions to maintain connectivity and participation in the mesh.

[adev_]

> I also don't think it's possible to make Meshtastic into the kind of reliable and high-performance mesh network some users want without effectively dropping support for most battery-powered devices

Interesting.

Zigbee has this distinction between router node and non-router node.

Routers are active members of the mesh (relay). Non-routers are just clients.

Most battery devices in Zigbee acts generally as non-router.

It is surprising that Meshtastic did not follow this pattern. Zigbee is not a young protocol.

[sandos]

Meshtastic did, in a way. There are roles and settings to disable rebroadcasts, then you are effectively a client. And it is used to preserve battery.