Differences

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

--- mosh:overview [2025/06/27 17:07] – [MOSH Nodes:] mosh
+++ mosh:overview [2026/06/10 13:54] (current) – mosh
@@ Line 1: / Line 1: @@
-====== MOSH Overview ======
+<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 is a decentralized, protocol-level framework for IoT devices. Unlike other protocols and their networks, MOSH requires **no internet** and **no fixed infrastructure**. MOSH is specifically developed for use-cases where internet connectivity isn't possible, is unreliable, or unwanted. This allows MOSH to be a fully-feature, modern protocol with many of the same features and functions of other protocols that rely heavily on an internet connection. Additionally, MOSH requires no additional hardware, or hub, to enable automations. Rather, MOSH uses a concept called a Virtual Wire™ to connect elements with one another.
+====== MOSH Project Overview ======
+MOSH is a decentralized, protocol-level framework for IoT devices. Unlike other protocols and their networks, MOSH requires **no internet** and **no fixed infrastructure**. MOSH is specifically developed for use-cases where internet connectivity isn't possible, is unreliable, or unwanted. This allows MOSH to be a fully-featured, modern protocol with many of the same features and functions of other protocols that rely heavily on an internet connection. Additionally, MOSH requires no additional hardware, or hub, to enable automations. Rather, MOSH uses a concept called a Virtual Wire™ to connect elements with one another.
 A MOSH network consists of nodes, with each node containing one or more elements (sensors, LEDs, etc). Elements then connect to other elements via one (or more) virtual wires. Virtual wires are, at their core, communication paths that allow an element to share information with other elements.
-Information is then processed by a MOSH Condition, which, simply put, is a conditionalized statement that tells the element what to do. MOSH Conditions are a rough equivalent to automations in other IoT networks.
+Information is then processed by a MOSH Condition, which, simply put, is a conditionalized statement that tells the element what to do. MOSH Conditions are a rough equivalent to automations in other smart home networks.
 It's also possible to have multiple MOSH networks, each with a different transport type. In order to "bridge" these networks MOSH implements a feature called a MOSH Coordinator. MOSH Coordinators, as their name implies, coordinate communication between elements on different networks, and can also hosts elements on their own.
-==== MOSH Nodes: ====
+====== MOSH Nodes: ======
@@ Line 18: / Line 23: @@
   * A node that relays messages between different transports.
-  * A bridge doesn't necessarily need to contain any elements. They can be stand alone nodes, although they are often paired with elements.
+  * A [[mosh:devices:bridge|bridge]] doesn't necessarily need to contain any elements. They can be stand alone nodes, although they are often paired with elements.
 === Coordinator: ===
@@ Line 34: / Line 39: @@
   * Usually built on a Pi or ESP32 with Wi-Fi
-===MOSH Peripheral:===
+===Peripherals and Nodes:===
-  * A node that performs a dedicated function (like sensing or controlling), but does not manage the network.
+  * A peripheral (or node) performs a dedicated function (like sensing or controlling), but does not manage the network.
   * Usually connects via ESP-NOW, Serial, or Wi-Fi.
   * Includes buttons, sensors, relays, etc.
-==== MOSH Protocol: ====
+====== MOSH Protocol: ======
 MOSH, strictly speaking, is a messaging protocol. MOSH nodes communicate with one another by exchanging MOSH messages. These messages handle things like:
@@ Line 73: / Line 78: @@
   * Write a MOSH elements properties (optional)
-==== MOSH Under the hood: ====
-MOSH features an extensible and flexible messaging library. While each message is covered in detail in the users guide, the following is a brief overview of the message structure:
-  * **Header** -- The header contains the formal addressing of the frame, various communications flags, the protocol version, and various security and message-control information.
-  * **Body** -- The body carries information between two or more MOSH nodes. The MOSH message library includes various node, element, and virtual-wire level status and control messages.
-  * **Footer** -- The footer marks the end of the message, and also includes checks checksums for integrity.