Differences

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

--- mosh:overview [2025/07/11 14:01] – [MOSH Project Overview] mosh
+++ mosh:overview [2026/06/10 13:54] (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 Project Overview ======
@@ Line 34: / Line 39: @@
   * Usually built on a Pi or ESP32 with Wi-Fi
-===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.
@@ Line 73: / Line 78: @@
   * Write a MOSH elements properties (optional)
-====== 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.