Skip to content

Releases

HydraHop 1.5.0

Choose a tag to compare

@kesh33w kesh33w released this 21 Nov 17:23
da64352

Added

  • HydraHop status on the Dashboard (web UI). One card shows, per network, bridged and repeated packets, each antenna's identity codes, which antenna's copy neighbours relay more when sent first, and Internet Link peers.
  • Retired one-byte codes are shown (web UI and repeater). The Dashboard, Analytics → Antennas and Crossing diagnostics name the radio, the code and the relay that caused it; the API gives retired_reasons.
  • HydraHop features are marked in the menu (web UI): an HH badge on Bridge, Antennas, Bridge settings and Radio Names, and a dot on pages changed in this release until opened.

Changed

  • Pins move to hydrahop-v1.5.0. Core is unchanged from 1.4.0 (same commit, tagged again).

HydraHop 1.4.2

Choose a tag to compare

@kesh33w kesh33w released this 21 Nov 15:29
b8af7ef

Fixed

  • One-byte codes were retired by relays far away (repeater). Adverts reach the Pi from across the state, and 1.4.1 retired three of its four codes at startup over repeaters 5 to 9 hops away. Only a repeater or room heard within 2 hops now retires a code.

Changed

  • Pins move to hydrahop-v1.4.2. Core and web UI are unchanged from 1.4.0 (same commits, tagged again).

HydraHop 1.4.1

Choose a tag to compare

@kesh33w kesh33w released this 21 Nov 15:12
63e7066

Added

  • One-byte antenna identity codes (repeater). tx_identity_experiment.one_byte, e.g. {g3909: [d4, "14"], rak909: ["12", d3]}, gives a transmitter a hand-picked 1-byte code (plus one for bridged hops), so 1-byte floods are tagged and Analytics → Antennas / GET /api/relay_stats can tell the copies apart. Pick bytes no relay on that radio's mesh uses. A code is retired as soon as a repeater or room advertising that byte is heard, live or in the last 30 days of stored adverts.

Fixed

  • Relay stats could credit the wrong copy (repeater) when an older hop in the path shared a code's bytes.

Changed

  • Pins move to hydrahop-v1.4.1. Core and web UI are unchanged from 1.4.0 (same commits, tagged again).

HydraHop 1.4.0

Choose a tag to compare

@kesh33w kesh33w released this 20 Nov 22:40
5121a68

Added

  • Which copy did neighbours relay? (repeater and web UI). For packets a TX group sends through two radios, Analytics → Antennas and GET /api/relay_stats show how often neighbours relayed each radio's copy, split by whether it went first or second, and which neighbours relayed which copy. It reads the identity code each copy carried from the relays this node hears back, so it needs per-radio identity codes (tx_identity_experiment with mode: tx); copies on 1-byte paths or direct routes cannot be told apart and are counted separately.
  • Random double-TX order (core and repeater). fabric.topology.tx_group_orders: {g3909: random} shuffles which radio sends first for every send, so neither radio wins relays just by going first. Default fixed.

Changed

  • Pins move to hydrahop-v1.4.0.

HydraHop 1.3.3

Choose a tag to compare

@kesh33w kesh33w released this 20 Nov 20:56
7a02f1b

Added

  • Pause between double-TX sends (core and repeater). fabric.topology.tx_group_gaps_ms, e.g. {g3909: [300, 1200]}, waits a random time in that range (ms) before a TX group's second radio sends, instead of keying up the instant the first finishes, when neighbours are rebroadcasting the first copy. Off unless set; config file only.

Fixed

  • Shadow radios could be configured as TX-group transmitters (core and repeater). Shadow radios are receive-only: a TX group naming one is now refused at startup and at send time, and the web UI no longer offers one. receiver radios can still be the second transmitter.

Changed

  • Pins move to hydrahop-v1.3.3. The web UI is unchanged from 1.3.1 (same commit, tagged again).

HydraHop 1.3.2

Choose a tag to compare

@kesh33w kesh33w released this 20 Nov 20:16
25c2901

Fixed

  • Double-TX radios showed zero transmit airtime (repeater). Each leg of a TX group is now recorded against its own radio in tx_radio_ids, so the dashboard airtime chart, per-radio packet rates and MQTT tx_radio_ids count the group's second radio (e.g. rak909, rak910). Rows stored before the upgrade keep the old attribution.

Changed

  • Pins move to hydrahop-v1.3.2. Core and web UI are unchanged from 1.3.1 (same commits, tagged again).

HydraHop 1.3.1

Choose a tag to compare

@kesh33w kesh33w released this 20 Nov 17:29
ad9e6f9

Fixed

  • Antenna and bridge statistics (repeater and web UI), after an independent review:
    • the antenna signal comparison uses the same radio frame only (same packet, same relay, within 1 s), leads with SNR and states how many frames it rests on; coverage still counts distinct packets;
    • neighbours repeating packets this node bridged are left out of coverage and signal, and counted separately;
    • each antenna shows whether the running topology sends on it, and "no data" / "not recorded" are no longer shown as zero;
    • bridge antenna codes come from the bytes actually sent, not today's settings;
    • a failed history read is reported as an error, not as an empty report.
  • Reproducible installs: the repeater pins core to an exact commit (including its hardware extra) instead of following core's branch.

Changed

  • Pins move to hydrahop-v1.3.1.

HydraHop 1.3.0

Choose a tag to compare

@kesh33w kesh33w released this 20 Nov 14:20
c4df344

Added

  • Antenna comparison (repeater and web UI): a new Analytics → Antennas page shows, for each network, which antennas heard each packet and how many only one antenna caught, the signal difference between antennas, and per antenna the noise floor, corrupted packets, repeaters heard, sends and channel-busy waits. It reads stored history (GET /api/antenna_stats).

Changed

  • Pins move to hydrahop-v1.3.0.

HydraHop 1.2.0

Choose a tag to compare

@kesh33w kesh33w released this 20 Nov 04:00
7eba003

Added

  • Bridge statistics (repeater and web UI): a new Analytics → Bridge page shows packets bridged each way between the two networks, local repeats, why heard packets were not sent, and sends per antenna pair with each pair's antenna code, over 1 h to 7 days. It reads the repeater's stored packet history (GET /api/bridge_stats), so it needs no new tracking and survives restarts.

Changed

  • Pins move to hydrahop-v1.2.0.

kesh-2026.11.19

Choose a tag to compare

@kesh33w kesh33w released this 19 Nov 13:51
7249b8a

Changed

  • Pins move to kesh-2026.11.19. No radio behaviour changes: this release fixes the reported version and the upgrade guide, and readies the repositories for outside readers.
  • The upgrade guide targets kesh-2026.11.19.
  • README opens with a "Start here" overview of the four repositories, and makes this repository's issues the single place for feedback on all of them.
  • The upgrade guide now switches the plugin manager's drop-in along with the repeater's, and backs up, verifies and rolls back both. Before this, upgrades left the plugin manager on an old release.
  • The upgrade guide records the 19 Nov 2026 Pi cleanup, replaces the one-off removal list with a general check before deleting a release, and explains why /opt/openhop_repeater/ stays (waterfall-metadata uses its venv).
  • The Antenna identities row points at the web UI setting.

Fixed

  • Reported version. enrollment/pi_enrollment_entry.py overwrote the repeater and core versions with hardcoded 61e5ffa.ilinkui20261105 strings, so every release since 5 Nov 2026 reported itself as that build in the web UI, the update check and observer MQTT software_version. The override is removed; the installed package versions are reported.
  • A duplicate ### Changed heading under kesh-2026.11.18.1.

Component pins

Component Commit Tag
openhop_core 3402687 kesh-2026.11.19
openhop_repeater 0f9737c kesh-2026.11.19
openHop_RepeaterUI b695f13 kesh-2026.11.19

Install with docs/upgrade.md.