Differences

This shows you the differences between two versions of the page.

--- mosh:transports [2025/06/25 15:59] – [MOSH Transports] mosh
+++ mosh:transports [2026/06/10 13:55] (current) – mosh
@@ Line 1: / Line 1: @@
+<WRAP important>
+This page is retained for historical reference and may not reflect the current MOSH/IMC/MTRP architecture.
+See [[guide:architecture_map]] for the current model.
+</WRAP>
 ====== MOSH Transports ======
@@ Line 30: / Line 34: @@
   * Wi-Fi
   * Serial
+  * Bluetooth (future)
+  * nRF24L01 (future)
+  * nRF52840 (future)
+  * LoRa (future)
+MOSH is designed to abstract the transport layer so that core functionality (messaging, routing, automation) remains consistent regardless of whether messages are transmitted via ESP-NOW, Wi-Fi, Serial, or future transports.
 ==== ESP-Now (v1 and v2) ====
@@ Line 44: / Line 54: @@
 TTL Serial (UART) is commonly used by MCUs for programming or debugging, but it can also be used for MOSH communication between nodes. This is especially useful for bridging different transport -- for example, a MOSH Controller can connect a UART node to an ESP-NOW or Wi-Fi network, acting as a gateway.
+===== Transport Bridging =====
+MOSH provides a built-in method of bridging transports together. These bridges, called MOSH Controllers, act as relays or protocol translators. This allows multiple MOSH networks to communicate with one another, and allows a MOSH transports to be chosen based on specific use-cases.