MOSH Wiki

architecture_map - created

mosh (mosh@undisclosed.example.com) — 2026-06-11T01:54:08+00:00

Architecture Map Purpose This page explains how the major MOSH subsystems relate to one another. Layered View Layer Responsibility MOSH smart-home logic, node behavior, elements, virtual wires IMC carrier abstraction and message boundary MTRP

start - created

mosh (mosh@undisclosed.example.com) — 2026-06-11T01:53:15+00:00

IMC Overview Purpose IMC is the layer between MOSH application behavior and the underlying transport or routing implementation. It exists so that MOSH does not need to talk directly to a specific radio, protocol, or link implementation. What IMC Does

start - created

mosh (mosh@undisclosed.example.com) — 2026-06-11T01:52:31+00:00

Getting Started This guide is the best starting point for understanding how MOSH is organized and where to go next. What MOSH Is MOSH is a modular smart-home and embedded networking platform built around reusable node behavior, message abstractions, and transport-independent routing.

start - [For Protocol Development]

mosh (mosh@undisclosed.example.com) — 2026-06-11T01:40:06+00:00

MOSH MOSH is a modular smart-home and embedded networking platform built around flexible nodes, reusable elements, and transport-independent communication. It is designed to let small devices, bridge nodes, and higher-capability controllers participate in one system while keeping routing, messaging, and application behavior clearly separated.

project_vision - created

mosh (mosh@undisclosed.example.com) — 2026-06-10T14:10:07+00:00

Mission Statement MOSH exists to allow individuals and developers to build reliable, private, and resilient IoT systems that function independently of the cloud, operate efficiently on resource-constrained hardware, and is fully modular and extensible.

sidebar - [MTRP]

mosh (mosh@undisclosed.example.com) — 2026-06-10T13:58:31+00:00

MOSH Wiki * Home Guides * Getting Started * First Node * Architecture Map MOSH * MOSH Overview * Architecture * Virtual Wires * Elements * Node Roles IMC * IMC Overview * Carrier Model * MTRP Carrier MTRP * Overview * Frame Format * Control Messages * Addressing * Routing Behavior * Routing Policies * Internal Tables * Transport Model * Security Model Hardware * Support Matrix * Official Nodes * Peripherals Legacy * Legacy Docs

supported_platforms

mosh (mosh@undisclosed.example.com) — 2026-06-10T13:55:24+00:00

This page is retained for historical reference and may not reflect the current MOSH/IMC/MTRP architecture. See architecture_map for the current model. MOSH Hardware Compatibility Matrix The following is a list of MCU's and SoC's that MOSH officially supports. While MOSH may run on other hardware, the following table represents the hardware in which MOSH development occurs.

transports

mosh (mosh@undisclosed.example.com) — 2026-06-10T13:55:12+00:00

This page is retained for historical reference and may not reflect the current MOSH/IMC/MTRP architecture. See architecture_map for the current model. MOSH Transports OSI Model -- Quick Overview The Open Systems Interconnect (OSI) model is a framework that describes how two or more computer systems communicate over a network. Each layer of the framework provides a specific purpose in communications. The OSI framework is as follows:

element_library

mosh (mosh@undisclosed.example.com) — 2026-06-10T13:55:02+00:00

This page is retained for historical reference and may not reflect the current MOSH/IMC/MTRP architecture. See architecture_map for the current model. MOSH elements do not contain independent logic. Instead, input elements (like buttons or sensors) generate status messages, and output elements (like relays or LEDs) subscribe to those messages via virtual wires.

virtual_wire_manager

mosh (mosh@undisclosed.example.com) — 2026-06-10T13:54:51+00:00

This page is retained for historical reference and may not reflect the current MOSH/IMC/MTRP architecture. See architecture_map for the current model. Virtual Wire Manager Before an element can communicate with other elements, it must be placed on a Virtual Wire. A

bridge

mosh (mosh@undisclosed.example.com) — 2026-06-10T13:54:38+00:00

This page is retained for historical reference and may not reflect the current MOSH/IMC/MTRP architecture. See architecture_map for the current model. moshbridge User Guide moshctl User Guide

protocol_details

mosh (mosh@undisclosed.example.com) — 2026-06-10T13:54:26+00:00

This page is retained for historical reference and may not reflect the current MOSH/IMC/MTRP architecture. See architecture_map for the current model. MOSH Protocol Specification (v1 Draft) Overview MOSH separates responsibilities into: * Core System * Element Manager * Message Router * Node Manager *

protocol_overview

mosh (mosh@undisclosed.example.com) — 2026-06-10T13:54:15+00:00

This page is retained for historical reference and may not reflect the current MOSH/IMC/MTRP architecture. See architecture_map for the current model. Architectural Overview 🧩 Element Manager The Element Manager is the hardware-to-MOSH interface, and is the subsystem responsible for managing all active elements on a MOSH node. It reads raw hardware data, and separates it into properties used by other MOSH elements. This separation allows an elements properties to reflect their intended use mo…

mosh_architecture.png - created

mosh (mosh@undisclosed.example.com) — 2025-06-26T19:50:02+00:00