
HALO · Private long-range mesh · v0.1.0
The network arrives with you.
A self-forming, self-healing HaLow mesh with edge command built in. No tower to lose, no carrier to wait on, no cloud in the loop.
- 01
Drop it.
Flash the image and power the board. A first-boot provisioner reads halo.toml and brings it up as a gateway or a node.
halo.toml → role = "node" · halo-mesh enabled - 02
It finds its peers.
Nodes discover each other over 802.11ah HaLow in the sub-GHz band, with multi-kilometer range at low power.
wlan0 · 802.11s mesh point · 920 MHz · peers 3 - 03
It addresses itself.
batman-adv routes across the mesh at Layer 2, and the gateway hands every node its address. Nobody types an IP.
bat0 10.41.0.17/24 · DHCP from gateway - 04
It locks every link.
On first boot each node registers its own WireGuard key. All control traffic rides the encrypted overlay.
POST /v1/mesh/wg-register → 10.42.0.2 - 05
It reports in.
Radio, system, GPS, power, camera and I2C telemetry, every five seconds, to a gateway drawing under 5 W.
heartbeat ✓ · every 5 s · 6 nodes reporting - 06
Lose one. It heals.
A peer drops. HALO rediscovers, then restarts the radio, then reloads the driver. Traffic routes around the gap.
peer lost → rediscover → radio restart → re-peered - 07
Under 90 seconds.
From cold boot to full encrypted reach, typically. Reboot one node, the gateway, or the whole network, and it comes back on its own.
wg0 up · mesh reachable · operator actions: 0
- <90 sCold boot to full encrypted reach, typically.
- <25 MBEach binary. An update is a file push and a restart.
- <5 WThe gateway, running the whole control plane.
- 0Cloud services needed to run it.
Through the stack
Follow one reading.
And the Portal shows 21.4 °C.
One reading. Every node sends its own, every five seconds.
Try it
Break it. It heals.
This is the example mesh, live. Take nodes down and watch traffic find another way to the gateway, then each node bring itself back.
Click any node to take it down.
- Nodes up
- 6 / 6
- Routes to gateway
- 6
- Operator actions
- 0
mesh up · 6 nodes · all routes to gateway
Time compressed. Recovery follows HALO's order: rediscover, radio, driver.
HALO Flows
Make it act.
Flows turns a reading into a response: a trigger, a condition and an action, running on the gateway. Read it as a sentence, and change it.
Tap any underlined part to change it.
, : .
- TriggerSensor value
sensor_value - ConditionThreshold
threshold - ActionWebhook
webhook_out
{ "text": "Node Neuron-04 i2c.ina219.voltage_v hit 11.3 (threshold 11.5)." }Runs on the gateway. The scheduler ticks every 30 seconds, and sensor triggers are checked the moment the reading arrives. Templates can use {node_name}, {metric}, {value} and {threshold}.
Sensors
Plug it in. It reports.
Wire a sensor to a node's I2C bus. Within 60 seconds it is identified and its readings are on the mesh. No firmware, no rebuild.
- 0x40INA219Current and voltageACK
- 0x76BME280Temperature, humidity, pressureACK
- 0x23BH1750Ambient lightACK
- 0x48ADS1115Analog in, four channelsACK
- 0x40HDC1080Temperature and humidityACK
- 0x44SHT31Temperature and humidityACK
- 0x68MPU6050Motion: accel and gyroACK
- 0x29VL53L0XDistance, time of flightACK
- 0x3CSSD1306A small display, drivenACK
$ haloctl local i2c scan Nine built in. Anything else is a TOML template dropped in /etc/halo/i2c-templates/, picked up in under a minute.
HALO Field
Answers in your hand.
- Mesh and tunnelMesh state, gateway latency and the WireGuard tunnel, served by the node itself.
- SignalLive signal from the node’s HaLow radio.
- GPS and distanceFix, satellites and the distance to the gateway. Distance still works with the link down.
12:04:05 −61 1.42 km 4.8 Mb/s12:04:10 −62 1.44 km 4.6 Mb/s12:04:15 −64 1.47 km 4.1 Mb/s- Field testPress start and walk. A row every 5 seconds with signal, position, distance and throughput, saved as CSV.
- Speedtest2 MB down, 1 MB up, through the encrypted tunnel: what the mesh really carries.
- No login, no laptopJoin the node’s hotspot with a phone. It answers even when SSH won’t.
HALO Portal
All of it, in a browser on the gateway.
Dashboard
Terminal
Wireless
IO
Flows
Where it goes
For where the network isn't.
- 01Expeditionary & defense
A network that moves with the team and needs no carrier.
- 02Disaster response
Up before the grid is, on hardware a responder can carry.
- 03Remote sites
Kilometers of coverage where no one is ever going to run a cable.
- 04Sensor networks
Measure, decide and act at the edge, with the data staying in the field.
No tower. No carrier. No cloud.
v0.1.0 · active development
HALO v0.1.0 is an early release, running on live hardware. Formats, the API and configuration are still settling, and it is proven in pilot deployments before it ships wide. It is built against real requirements and funded by our own services work. If you own a field gap, a directive or a program need, this is the stage where a partner shapes what ships.
ETHRX builds operational software for the environments where reliability, discretion, and accountability are not optional. HALO runs on small ARM boards with HaLow radios, managed from a browser, and is part of the ETHRX product line. HALO is in active development; features may change before general availability. © 2026 ETHRX LLC.
