Overview - Mesh Network Communication
Meshtastic
Nodes
| Long Name | Short Name | Standort | Hardware | Role |
| AN1 | Arnsberg HQ | mesh.attyc.de | AN1 | Alt-Arnsberg | MeshAdv Mini @ RPi Zero 2 | CLIENT |
| AN2 | Bruchhausen | mesh.attyc.de | 🦆 | Arnsberg Bruchhausen | Heltec Wireless Paper V1.2 | CLIENT |
| ices Heltec v3 | mesh.attyc.de |
💬 | mobil | Heltec WiFi LoRa 32 (V3) | CLIENT_MUTE |
| ices SenseCap | mesh.attyc.de | ices | mobil | Seeed SenseCAP T1000-E | CLIENT_MUTE |
Channel Arnsberg
Ich habe einen Channel mit MQTT Anbindung für den Raum Arnsberg erstellt. Jeder ist eingeladen dort mitzuchatten! 😊
 |
|
| Channel-Name | Arnsberg |
| Keysize | 256 bit |
| Key |
|
| Channel Role | secondary |
MeshCore
Why MeshCore? When you do something, you should do it right. Mesh communication is exciting, and in my opinion, it is important to have a decentralized off-grid messaging system. I am convinced that the young MeshCore protocol is the better choice for this than Meshtastic. In the future, I will do my best to contribute to the network with new repeaters and hope to inspire others to join in.
Every repeater improves the mesh network!
MeshCode Deutschland @ Telegram
MeshCore @ Discord
Nodes
| Long Name | Standort | Hardware | Role |
| ices Heltec v2 | mesh.attyc.de | mobil | Heltec WiFi LoRa 32 (V2) | |
| AN2 | mesh.attyc.de | Alt-Arnsberg | LilyGo Lora v2.1-1.6 | Repeater |