Meshtastic - Revision history

Jschrempp: /* Overview */

2026-05-15T18:23:57Z

Overview

← Older revision		Revision as of 14:23, 15 May 2026
Line 1:		Line 1:
	== Overview ==		== Overview ==

			(We have info on [[Mesh_Networks\|other mesh networks]])

	Meshtastic is an open source, low bandwidth mesh network that runs on 933MHz in the U.S. It runs on LoRa radio technology which is very low power, line of sight. Nodes can broadcast for miles if you are high on a hill. In an urban, flat area you might get 0.25 miles. But the power of the mesh is that if just one node can hear your message, then it can be relayed on to others.		Meshtastic is an open source, low bandwidth mesh network that runs on 933MHz in the U.S. It runs on LoRa radio technology which is very low power, line of sight. Nodes can broadcast for miles if you are high on a hill. In an urban, flat area you might get 0.25 miles. But the power of the mesh is that if just one node can hear your message, then it can be relayed on to others.

Jschrempp: /* Low Level Details */

2026-05-15T18:23:06Z

Low Level Details

← Older revision		Revision as of 14:23, 15 May 2026
Line 26:		Line 26:

	Low level, but still crucial to get right.		Low level, but still crucial to get right.

			=== Radio Things ===

			Read our [[Mesh_Networks\|Tips on Radio hardware]]

	=== Protocol Details ===		=== Protocol Details ===

Jschrempp: /* Radio Things */

2026-05-15T18:19:38Z

Radio Things

← Older revision		Revision as of 14:19, 15 May 2026
Line 26:		Line 26:

	Low level, but still crucial to get right.		Low level, but still crucial to get right.

	~~=== Radio Things ===~~

	~~[https://bayme.sh/docs/getting-started/recommended-hardware/ Bay Mesh] has some good hardware recommendations.~~

	Height above ground will dramatically improve your experience. The higher the better. If you drive to the top of a hill your signal will propagate much further. Like A LOT further. In one experiment we got good reception 1/4 mile down the block in an urban setting; the same devices with one on a hill worked at 3 miles! Nothing beats a high placement with clear line of sight.

	~~Line of sight planning tools~~

	* The official [https://site.meshtastic.org/ Site Planner] shows how far your radio will reach
	* [https://www.scadacore.com/tools/rf-path/rf-line-of-sight/ Move two pins and see what's between them]
	* Pick a location [https://heywhatsthat.com/ and see the horizon view]
	* Give it your location [https://www.peakfinder.com/ and see the peaks]

	The cable between your node and the antenna makes a difference. Sometimes you might want the antenna a ways away from your node. Then cable loss can be a big factor and depend on the type of cable. KMR 240 would be fine under 5-10 feet. KMR400 or KRM600 is better and also allows you to go 10-30 feet. It’s usually easier to just put the radio on the pole close to the antenna with a long power or network cable.

	~~Adapters also introduce signal loss. Try to avoid them.~~

	Some antennas have a built in right-angle joint. It seems convenient but in testing several of these we found that while straight they had a SWR of almost 1:1, when in right-angle position the SWR was 3:1 - yikes!

	If you have a node that can run high power, like the Station G2, then you can up the RF output to compensate for antenna configuration. What if you have a small unit like a Heltec V3? You might wonder which is better:
	* a well tuned 2.5dBi whip antenna with a short cable
	* a nice 6dBi antenna with two short cables and an adapter to connect them
	~~If you figure this out, let us know!~~

	~~If you are in a noisy area, then a well tuned RF filter can boost your signal reception dramatically. They are pricey.~~

	=== Protocol Details ===		=== Protocol Details ===

Jschrempp: /* Long Fast? Medium Slow? Something Else? */

2026-02-11T01:12:48Z

Long Fast? Medium Slow? Something Else?

← Older revision		Revision as of 21:12, 10 February 2026
Line 81:		Line 81:
	The Presets were created to offer a balance of distance and speed but to be more biased towards distance rather than speed. Long Fast is actually pretty slow, but gives long distance.		The Presets were created to offer a balance of distance and speed but to be more biased towards distance rather than speed. Long Fast is actually pretty slow, but gives long distance.

	In areas where the mesh is more dense we can tip the balance towards speed rather than distance. Even though it is called "Medium Slow", this Preset is still faster than Long Fast at the expense of a little bit of distance.		In areas where the mesh is more dense we can tip the balance towards speed rather than distance. Even though it is called "Medium Slow", this Preset is still faster than Long Fast at the expense of a little bit of distance.

			([https://k2xap.radio/mesh/lora-shapes LoRa shapes] is an interesting dive into this.)

	Speed is important in a busy mesh. The slower the transmission, the longer each message takes. And if two nodes transmit at the same time then no nodes will be able to understand the message. Faster speed means less air time for each message and lower overall utilization of the mesh air waves - less congestion.		Speed is important in a busy mesh. The slower the transmission, the longer each message takes. And if two nodes transmit at the same time then no nodes will be able to understand the message. Faster speed means less air time for each message and lower overall utilization of the mesh air waves - less congestion.

Jschrempp: /* Outdoor Nodes */

2025-12-04T01:44:01Z

Outdoor Nodes

← Older revision		Revision as of 21:44, 3 December 2025
Line 574:		Line 574:

	Or [https://www.seeedstudio.com/Wio-SX1262-with-XIAO-ESP32S3-p-5982.html cheapest node] we've seen.		Or [https://www.seeedstudio.com/Wio-SX1262-with-XIAO-ESP32S3-p-5982.html cheapest node] we've seen.

			A node [https://youtu.be/P2R9ad5PctY?si=xrEUC4DBMo35xGlb with a larger solar panel].

	=== Heltec V3 ===		=== Heltec V3 ===

Jschrempp: /* Radio Things */

2025-11-18T15:35:34Z

Radio Things

← Older revision		Revision as of 11:35, 18 November 2025
Line 38:		Line 38:
	* [https://www.scadacore.com/tools/rf-path/rf-line-of-sight/ Move two pins and see what's between them]		* [https://www.scadacore.com/tools/rf-path/rf-line-of-sight/ Move two pins and see what's between them]
	* Pick a location [https://heywhatsthat.com/ and see the horizon view]		* Pick a location [https://heywhatsthat.com/ and see the horizon view]
			* Give it your location [https://www.peakfinder.com/ and see the peaks]

	The cable between your node and the antenna makes a difference. Sometimes you might want the antenna a ways away from your node. Then cable loss can be a big factor and depend on the type of cable. KMR 240 would be fine under 5-10 feet. KMR400 or KRM600 is better and also allows you to go 10-30 feet. It’s usually easier to just put the radio on the pole close to the antenna with a long power or network cable.		The cable between your node and the antenna makes a difference. Sometimes you might want the antenna a ways away from your node. Then cable loss can be a big factor and depend on the type of cable. KMR 240 would be fine under 5-10 feet. KMR400 or KRM600 is better and also allows you to go 10-30 feet. It’s usually easier to just put the radio on the pole close to the antenna with a long power or network cable.

Jschrempp: /* Visualize the Mesh */

2025-11-17T21:24:56Z

Visualize the Mesh

← Older revision		Revision as of 17:24, 17 November 2025
Line 497:		Line 497:
	== Visualize the Mesh ==		== Visualize the Mesh ==

	Your node has a view of the mesh based on the nodes it has heard from. To get a bigger view of the mesh in your area, look for a local group that logs and plots nodes. For example, the Bay Area group has an [https://meshview.bayme.sh/map online map view] of the nodes. Note that you can filter this to show nodes on the ~~two~~ meshes in the Bay Area~~; the~~ long-fast ~~and the~~ medium-slow ~~meshes~~.		Your node has a view of the mesh based on the nodes it has heard from. To get a bigger view of the mesh in your area, look for a local group that logs and plots nodes. For example, the Bay Area group has an [https://meshview.bayme.sh/map online map view] of the nodes. Note that you can filter this to show nodes on just one of the meshes in the Bay Area: long-fast, medium-slow, medium-fast.

	[https://meshy.smerty.org/ Smerty] ~~another~~ view of the BayMe.sh data		=== Other options to view MQTT logged data ===

			These are implementations of open source software. If you like what you see, then you could go to GitHub and get what you need to start one in your area.

			*[https://meshview.bayme.sh/ Meshview Bay Area] BayMe.sh logger
			*[https://meshview2.bayme.sh/ Meshview Bay Area Development branch]
			*[https://meshyview.bayme.sh/ Meshyview, an alternative to Meshview]
			*[https://mesh.stonekitty.net:8080/ BayMalla, a Malla implementation]
			*[https://meshy.smerty.org/ Smerty] a different view of the BayMe.sh data
			*[https://www.svme.sh/ Sacramento Valley]
			*[https://mesh.stonekitty.net/ Meshview of all of California run by Nathan]

	=== Meshview ===		=== Meshview ===

Jschrempp: /* Visualize the Mesh */

2025-11-08T00:19:10Z

Visualize the Mesh

← Older revision		Revision as of 20:19, 7 November 2025
Line 498:		Line 498:

	Your node has a view of the mesh based on the nodes it has heard from. To get a bigger view of the mesh in your area, look for a local group that logs and plots nodes. For example, the Bay Area group has an [https://meshview.bayme.sh/map online map view] of the nodes. Note that you can filter this to show nodes on the two meshes in the Bay Area; the long-fast and the medium-slow meshes.		Your node has a view of the mesh based on the nodes it has heard from. To get a bigger view of the mesh in your area, look for a local group that logs and plots nodes. For example, the Bay Area group has an [https://meshview.bayme.sh/map online map view] of the nodes. Note that you can filter this to show nodes on the two meshes in the Bay Area; the long-fast and the medium-slow meshes.

			[https://meshy.smerty.org/ Smerty] another view of the BayMe.sh data

	=== Meshview ===		=== Meshview ===

Jschrempp: /* Browser Based Control */

2025-11-03T15:05:47Z

Browser Based Control

← Older revision		Revision as of 11:05, 3 November 2025
Line 479:		Line 479:
	# Verify that the updated container is running as expected.		# Verify that the updated container is running as expected.
	# If you no longer need the old image, you can remove it using '''docker rmi <image_name>'''		# If you no longer need the old image, you can remove it using '''docker rmi <image_name>'''

			[https://meshmonitor.org/ Meshmonitor] is a new development to manage several nodes from one UI.

	=== MeshSense App ===		=== MeshSense App ===

Jschrempp: /* Traceroute */

2025-10-18T02:06:58Z

Traceroute

← Older revision		Revision as of 22:06, 17 October 2025
Line 307:		Line 307:
	< Route Back: Herkimer-1!433d26b8 —-> Herkimer-O (8.25dB) --> jbs1 base San Carlos makernexus.org(-4.75dB) --> jschrempp makernexus.org (8.25dB)		< Route Back: Herkimer-1!433d26b8 —-> Herkimer-O (8.25dB) --> jbs1 base San Carlos makernexus.org(-4.75dB) --> jschrempp makernexus.org (8.25dB)
	</pre>		</pre>

			Traceroute messages are sent with the configured Message Hop Count Limit. This is also true of the response. For example, say the node sending the TR has a hop limit of 6 and it takes 5 hops to reach the destination. If the destination is configured with a hop limit of 3, the reply might not make it back.

	If you don't get a traceroute reply, you can still get a lot of information about your situation by looking at the outbound flood on Meshview.		If you don't get a traceroute reply, you can still get a lot of information about your situation by looking at the outbound flood on Meshview.