Is it possible to connect a Meshtastick node to Chirpstack?
I have a RAK4631 device that works in this mesh network. I’m interested in integrating this device with CS.
Hello Marekpow , from what I understood but which is 99% sure, it is not possible because mehastic is a P2P “point to point” network where your nodes belong to you but you can share the data with others and also discuss with other nodes of the MESHASTIC network so it remains LORA while shirpstack is designed around the LORAWAN NETWORK but you can flash your node from MEHASTIC to LORAWAN on condition that you want to do it and that you find how to do it. Lorawan is on WAN network like TTN and co which run under chirpstack server surely and MESHASTIC use all the nodes to bounce the data on the principle to other nodes. From what I understood or thought I understood.
chat gpt
- LoRaWAN:
A standardized protocol built on LoRa modulation, LoRaWAN is designed specifically for Internet of Things (IoT) applications. It provides long-range, low-power communications using a star-of-stars topology, where end devices talk directly to gateways, which then relay data to a centralized network server. - Meshastic:
Meshastic is an open-source project that leverages LoRa radios to create decentralized, ad-hoc mesh networks. Instead of relying on fixed gateways and centralized servers, nodes in a Meshastic network forward messages to each other, forming a self-healing, peer-to-peer network.
Network Architecture
- Topology:
- LoRaWAN: Uses a star topology. Devices (sensors, actuators) communicate directly with gateways, which cover large areas by relaying data to a central server.
- Meshastic: Employs a mesh topology. Every node can act as a relay, which helps extend coverage in environments without fixed infrastructure.
- Centralization:
- LoRaWAN: Centrally managed, with network servers coordinating device activity, security, and data routing.
- Meshastic: Decentralized and ad hoc, which can be advantageous in scenarios where traditional infrastructure is unavailable (e.g., emergency or off-grid communications).
Applications & Use Cases
- LoRaWAN:
- Best suited for IoT applications such as smart cities, agriculture, asset tracking, and industrial monitoring.
- Ideal for devices that need to send small, infrequent bursts of data over long distances while preserving battery life.
- Meshastic:
- Often used for off-grid communication, emergency networks, and personal messaging where infrastructure is limited.
- Useful in situations where a decentralized network is more resilient, such as in disaster recovery scenarios or remote areas.
Pros & Cons
- LoRaWAN Pros:
- Scalability: Well-established ecosystem with extensive deployments and vendor support.
- Power Efficiency: Optimized for low-power devices.
- Range: Capable of long-range communication through centralized gateways.
- LoRaWAN Cons:
- Dependency on Infrastructure: Requires gateways and a centralized server, which might not be available in every environment.
- Limited Flexibility: Less suited for dynamic, ad-hoc networking scenarios.
- Meshastic Pros:
- Decentralization: No need for pre-installed gateways or central servers, allowing for flexible deployment.
- Resilience: Mesh topology provides self-healing capabilities if some nodes fail or move.
- Ad-hoc Networking: Ideal for temporary networks in events, disaster zones, or remote regions.
- Meshastic Cons:
- Scalability Limits: Mesh networks can become complex to manage as the number of nodes increases.
- Range Dependency: The effective communication range depends on the density and placement of nodes, as messages may need to hop multiple times.
Summary
While both technologies utilize LoRa radio frequencies, their approaches differ significantly:
- LoRaWAN is best for structured IoT deployments that benefit from a centralized, low-power, long-range system.
- Meshastic offers a decentralized, flexible alternative suited for environments where traditional network infrastructure is lacking or when dynamic, peer-to-peer communication is needed.
No, Meshtastic is not LoRaWAN. Cool product though.
Thanks for all the responses.
Hi, this is an interesting idea and I wanted to make a universal interface to work with different types of packets. At the moment I am extending the original packet forwarder to implement this feature. As soon as I make the first release, I will inform about ChirpStack Community Forum who is interested
I’m interested in this topic. I am considering another way to get data from the Meshtastic node. I have a node with RAK4631; it has only BT by air (it doesn’t have Wi-Fi). Then, attach a BT antenna to any computer with the MQTT server and transfer the data to CS via this protocol. Then, process this data on the CS side. I don’t know how at the moment.
Yes, this is a good approach for m2m integration and does not require efforts to make changes to the Lora Wan protocol software to decode the Meshtastic packet. In my case, I have different devices that work simultaneously with Lora Wan and Meshtastic P2P protocol.