Meshtastic :: Esoteric Networks

MESH_LOGIN.TXT

What is Meshtastic?

Meshtastic is an open-source, decentralized LoRa mesh that lets inexpensive low-power radios exchange messages, positions, telemetry, and other small packets without requiring cell towers or internet service.

A phone or computer can talk to a nearby radio over Bluetooth, Wi-Fi/Ethernet, or serial. The radio transmits over LoRa. Other compatible nodes that hear a new packet may rebroadcast it, decrementing its hop limit until it reaches its destination or stops traveling.

Encrypted Channels sit on top of the shared radio mesh, allowing different groups to exchange readable traffic while nearby compatible nodes can still help move packets.

WHY_FLORIDA.NFO

Because the Sunshine State occasionally throws the furniture.

FLORIDA RESILIENCE MESH: Build and test a community communications layer that remains locally useful when cellular service, commercial power, internet backhaul, or ordinary communications become unavailable, patchy, or overloaded.

This is not a replacement for 911, public-safety radio, satellite communications, amateur emergency systems, or any other established life-safety path. The value is in adding one more independent layer.

HURRICANE / FLOOD / INFRASTRUCTURE FAILURE
                    |
                    v
       ordinary communications degrade
                    |
           +--------+--------+
           |                 |
      neighborhood       field teams
        check-ins       / damage checks
           |                 |
           +--------+--------+
                    |
             MESHTASTIC MESH
                    |
          +---------+----------+
          |                    |
    local gateway        elevated node
     / dashboard          / good horizon
          |
      ESONET log
      / bulletins

The useful traffic is small and concrete: welfare checks, road conditions, flooding, shelter status, resource availability, local observations, positions, and short operational messages.

DISASTER_TRAFFIC.CSV

Small packets can carry useful truths.

CHECK-IN HOUSE / TEAM / PERSON
OK / NEED HELP / UNKNOWN
POWER / WATER / COMMS

ROAD / FLOOD LOCATION
PASSABLE / BLOCKED / WATER
TIME OBSERVED

RESOURCE LOCATION
ICE / WATER / POWER / CHARGING
AVAILABILITY

SHELTER / SITE OPEN / CLOSED
GENERATOR / CAPACITY
VERIFIED TIME

WELFARE CHECK REQUEST
LAST CONTACT
STATUS WHEN VERIFIED

OPERATIONS TEAM POSITION
TASK / HANDOFF
SHORT FIELD UPDATE

A useful resilience protocol would need more than radios: agreed message formats, timestamps, source confidence, channel discipline, training, charging plans, and a clear rule for what should be escalated to established emergency services.

PACKET_PATH.ASC

How the packet moves

HUMANphone / handheld / keyboard

LOCAL RADIOBluetooth / serial / Wi-Fi

LORA MESHbroadcast + rebroadcast

RECIPIENTperson / sensor / gateway

packet heard → duplicate checked → hop decremented → packet forwarded

At the radio level, nodes must share compatible LoRa settings. Logical Channels then provide separate encrypted groups above that shared radio mesh.

FIELD_ROLES.DIR

Roles that matter to these projects

GENERAL

CLIENT / CLIENT_BASE

Human-facing nodes and stronger personal base stations. A natural fit for homes, vehicles, field kits, and local operations.

TELEMETRY

SENSOR

Prioritizes telemetry and supports a sleep → measure → transmit cycle. This is the role that makes SolarHive particularly interesting.

POSITION

TRACKER

Prioritizes GPS position traffic for people or assets when location updates matter more than ordinary chatter.

OPERATIONS

TAK / TAK_TRACKER

Firmware roles intended for ATAK integration, including position/PLI-oriented behavior for coordinated field operations.

INFRASTRUCTURE

ROUTER

A strategically placed infrastructure node that always rebroadcasts packets and appears in topology.

DEAD-SPOT TOOL

ROUTER_LATE

Provides additional coverage after other node types have had their chance to retransmit. Useful where a local cluster needs help without immediately dominating the mesh.

PROJECT_OPPORTUNITIES.DIR

Things this mesh could become around here

FLAGSHIP OPPORTUNITY

Florida Resilience Mesh

Pre-positioned and deployable neighborhood communications for hurricanes, flooding, cellular outages, and the first hours or days when ordinary infrastructure is unreliable.

EXISTING PROJECT

SolarHive Nodes

Bee-colony monitoring nodes that use Meshtastic for field telemetry during ordinary operation and can remain useful participants in the surrounding local mesh while solar power remains available.

FIELD RESEARCH

Field Coverage Atlas

Model expected coverage, walk or drive the network, record RSSI/SNR and packet paths, compare prediction to reality, then move or add nodes and repeat.

DEPLOYABLE INFRASTRUCTURE

Elevated Event / Recovery Node

The Balloon Node question becomes broader: how much coverage can one well-positioned temporary node restore after a storm or across a large event footprint?

GATEWAY IDEA

ESONET Mesh Handoff

Selected bulletins could move outward to a mesh channel while selected field reports are logged back into ESONET. Not an ANSI terminal over LoRa, but a useful asynchronous bridge.

LOCAL-FIRST

Mesh Operations Console

A Pi-hosted local dashboard for nodes, positions, battery condition, telemetry, RF observations, SolarHive data, and resilience status without depending on the commercial internet.

FIELD OPERATIONS

ATAK-Capable Nodes

Use Meshtastic's TAK-oriented roles for position and coordinated field work while keeping the ordinary neighborhood mesh accessible to people who do not need a tactical interface.

OPTIONAL CONVERGENCE

Smart Inventory Presence

Compact inventory state could ride the mesh later if the sheds become part of a wider field network. The existing focused LoRa pilot does not need to be rewritten simply because Meshtastic exists.

SOLARHIVE_SENSOR_BUS.CSV

Why SolarHive and Meshtastic fit unusually well

HIVE / NODE SIGNAL	MESHTASTIC PATH	NOTES
Temperature / humidity	Native telemetry sensor support	Multiple supported I²C sensor families
Battery / solar current	Native power telemetry	Supported current / voltage monitors
Hive weight	NAU7802 differential ADC path	Suitable interface class for load-cell / Wheatstone bridge work
Light / UV / weather context	Native telemetry sensor support	Useful environmental context around colony behavior
Entrance activity	Custom sensor / second-controller path	Likely project-specific processing before compact mesh reporting
Acoustics / vibration	Custom sensor / second-controller path	Process locally, transmit useful derived observations rather than raw audio

DUAL-PURPOSE INFRASTRUCTURE: A SolarHive node exists to observe living systems. If it is already solar-powered, field-hardened, and carrying a LoRa radio, the communications layer can also contribute to local resilience without changing the reason the project exists.

GATEWAY_PATHS.SYS

Getting packets into useful local systems

MESHTASTIC FIELD MESH
         |
    gateway radio
         |
   USB / TCP / BLE
         |
    Raspberry Pi
         |
   +-----+--------------------+
   |          |               |
 dashboard   logs           ESONET
 nodes       telemetry      selected
 maps        RF weather     bulletins
 battery     positions      reports

OPTIONAL WHEN INTERNET EXISTS:
         |
        MQTT
         |
 custom broker / remote island / web services

The Python API exposes node information, positions, telemetry, text and other well-known packet types. Meshtastic's MQTT module can also uplink and downlink selected Channels when a gateway has Wi-Fi or Ethernet and internet connectivity.

The local Pi layer should remain useful when MQTT and the wider internet disappear. Cloud connectivity is an extension, not the foundation.

ATAK_FIELD_LAYER.NFO

Field teams get a different interface than the neighborhood.

Meshtastic includes TAK and TAK_TRACKER device roles intended for ATAK integration and position-oriented field operations.

That suggests a useful split: ordinary community participants can use normal Meshtastic clients for check-ins and local information, while trained field teams can use ATAK-oriented nodes for position and coordinated operational awareness.

STATUS: Strong research path, not deployed capability. A resilience system should be tested, documented, trained, and exercised before anybody depends on it during an actual disaster.

MESHTASTIC_VS_RETICULUM.NFO

Neighbors, not competitors.

MESHTASTIC

A ready-made LoRa field mesh with radios, clients, Channels, messaging, positions, telemetry, device roles, and gateways.

RETICULUM

A networking stack that can span several very different link types, including RNode/LoRa, local networks, serial links, and IP transports.

A future field box may contain both capabilities. That does not make their over-the-air protocols interchangeable. Any bridge between them should be deliberate and visible.

What is Reticulum? >>

HONEST_LIMITS.NFO

The radio still has to live in the real world.

This is resilience infrastructure, not a distress beacon. Life-threatening emergencies should use every available established emergency path.

LoRa airtime is finite. Payloads are small. Extra routers are not automatically better. Poor placement can be more important than transmit power. Dense traffic can burden a mesh. Store-and-forward history itself can temporarily increase airtime usage.

A serious Florida resilience deployment therefore needs coverage testing, power planning, weather protection, spare hardware, channel discipline, documented operating procedures, and humans who have practiced with it before the lights go out.

REFERENCE_LINKS.URL

Official documentation behind the packet weather

RETURN_PATH.URL

Back to the wider signal.

ESOTERIC
NETWORKS RETICULUM
STACK LIVING
SYSTEMS DIGITAL
GARDEN