Meshtastic and Meshcore Bookmarks
https://github.com/filipsPL/meshtastic-network-visualization/tree/main A mesh visualization for Node "stw0" https://meshtastic.steyr-werke.at/
https://meshmonitor.lorameshaustria.at/#nodes
https://meshtastic.org/docs/configuration/module/neighbor-info/
Du brauchst Ein Antennenmessgerät wie den NanoVNA. https://döner-hawaii.de/meshtastic/antenne/
https://app.element.io/#/room/#longfast:freiburg.social
https://meshtastic.at/autarkes-node-errichten/
https://de.wikipedia.org/wiki/Meshtastic
https://meshtastic.org/docs/software/python/cli/usage/
https://www.youtube.com/watch?v=knyg6EEiGOo
Die Wahl des Funkprofils ist entscheidend. Profile für große Reichweiten belegen den Kanal länger und erhöhen die Chance auf Störungen. In belebten Netzen entsteht so ein regelrechter Funkstau. https://spacepc.de/meshtastic-aktuelle-probleme-und-warum-nachrichten-manchmal-unzuverlassig-sind/
https://meshtastic.org/blog/why-your-mesh-should-switch-from-longfast/
https://meshtastic.org/blog/a-major-solution-to-a-miner-problem/
https://kieranmurphy.net/gitfos-gat562-solar-mesh-relay-node/
https://www.bitsnbytes.dev/posts/2025-08/meshtastic-configuration-settings.html
https://www.gaskutsche.de/tipps_cbfunk_swrmeter.php
Frequenz: "EU/UK Narrow"-Preset https://www.himesh.de/bauvorschlag-repeater.html
Debug log to PC if something is wrong:
meshtastic --noproto
assert failed: static NimBLEClient* NimBLEDevice::getClientByID(uint16_t) NimBLEDevice.cpp:307 (0)
Sources:
Force flash device: Set the device into download mode.
Methode 1 (beim Einstecken):
Sources:
For better recognition on the node list, the country code as prefix is recommended.
Connect the device to mqtt. https://analyzer.letsmesh.net/observer/onboard
https://meshcore.co.uk/map.html
https://github.com/LitBomb/MeshCore-FAQ
https://github.com/ipnet-mesh/meshcore-mqtt/tree/main/meshcore_mqtt
https://dl-nordwest.com/index.php/2025/11/09/meshcore-wenn-dein-lora-netz-mitdenkt/
https://www.73mesh.com/2025/11/19/RoomServers.html
Room-Peater: A combination of Room Server and Repeater roles. Install the Room Server then enable repeater role via the "set repeat {on|off}" command. https://pugetmesh.org/meshcore/
heltec_v4 --> ok heltec_v3 --> not ok, Wire.cpp:499] requestFrom(): i2cWriteReadNonStop returned Error -1 https://pugetmesh.org/meshcore/repeater_setup/ https://github.com/meshcore-dev/MeshCore/blob/main/docs/faq.md#31-q-how-do-you-configure-a-repeater-or-a-room-server
On Meshtastic, new nodes automatically announce their presence to the rest of the network. This is not done automatically with MeshCore for a Companion firmware, only Repeaters automatically have their presence broadcasted at a regular interval every few hours. https://jeromegagnonvoyer.wordpress.com/2025/07/06/running-meshcore-in-canada/
MeshCore provides the ability to create wireless mesh networks, similar to Meshtastic and Reticulum but with a focus on lightweight multi-hop packet routing for embedded projects. Unlike Meshtastic, which is tailored for casual LoRa communication, or Reticulum, which offers advanced networking, MeshCore balances simplicity with scalability, making it ideal for custom embedded solutions., where devices (nodes) can communicate over long distances by relaying messages through intermediate nodes. This is especially useful in off-grid, emergency, or tactical situations where traditional communication infrastructure is unavailable. https://www.cnx-software.com/2025/07/19/meshcore-lightweight-alternative-to-meshtastic-for-lora-based-off-grid-messaging/
Meshtastic works well when people and links are moving (friends at an event, a hike, a bike ride). Regular nodes help by rebroadcasting, so coverage can shift and grow as people move. MeshCore works well when you can place fixed repeaters on rooftops or hills. Phones connect through companion radios; companions do not rebroadcast, so repeaters are what grow the mesh. https://www.austinmesh.org/learn/meshcore-vs-meshtastic/