cortandClaude Opus 4.7 ddb0dff3f1 release: bump to v4.8.0
Headline changes since v4.7.0: unit (private) call routing with user
cache + broadcast fallback, subscriber-pair hang time, cross-slot
forwarding, and optional propagation across HBlink4 outbound links;
DMR data-call classification so APRS/SMS streams are logged once
instead of fanning out as voice; RPTO empty-timeslot fix so
"Options=TS1=;TS2=..." correctly disables TS1 instead of silently
falling back to configured defaults.

See docs/RELEASE_NOTES_v4.8.0.md for the full change list and
migration notes.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-06 07:35:59 -05:00
2026-05-06 07:35:59 -05:00
2026-05-06 07:35:59 -05:00
2026-05-06 07:35:59 -05:00

HBlink4

HBlink4 is a DMR Server implementation using the HomeBrew protocol, developed by Cort Buffington, N0MJS. HBlink4 operates as an endpoint network server with granular per-repeater control; transit call-routing between DMR networks is limited.

There has been some chatter coming my way about what is "official" with respect to HBlink. I can't stop others from claiming they are the "official" source, or using account names that make them look officical. All I can say is that I'm the author, and I'm the copyright holder. What is the status?

  • HBlink (DEPRECIATED): Original Python2 based system, interacted with DMRlink for IPSC/HBP translations. Worked on a "system" level and supported internetworking via a "conference bridge" paradigm. Highly configurable for a time before DMRgateway.
  • HBlink3 (DEPRECIATED: Rewrite in Python3, mostly the same code base updated. Dropped direct support for IPSC/HBP translations.
  • HBlink4 (ACTIVE DEEVLOPMENT): Ground up re-write for modern times. Repeater, not system based. Supports full dynamic TGID subscription and TS/TGID translation based on "Options" configuration send by MMDVMHost or DMRGatway. Includes integrated dashboard application as part of the package.

For those who need Motorola IPSC connectivity, see my compantion project ipsc2hbp to convert from Motorola's proprietary network protocol to MMDVM's.

Architecture

HBlink4 focuses on being an efficient endpoint network server with the following design principles:

  • Per-repeater routing rules using TS/TGID tuples for precise call handling
  • Individual repeater management rather than server-level "system" groupings
  • Direct source connectivity without multi-hop relay complexity
  • Granular per-repeater control and monitoring
  • Tightly integrated web dashboard - Real-time monitoring with WebSocket updates

Features

  • Native dual-stack IPv4/IPv6 support - Simultaneous listening on both protocols for maximum compatibility
  • Modern Python implementation with type hints
  • Improved error handling and logging
  • JSON-based configuration
  • Enhanced repeater management
  • Built on Python's asyncio for single-loop UDP I/O with no external framework dependency
  • Tightly integrated web dashboard - Real-time monitoring with modern look and feel (see Dashboard Documentation)
  • Stream tracking with immediate DMR terminator detection (~60ms)
  • Real-time duration counter with 1-second updates
  • Two-tier stream end detection (immediate terminator + timeout fallback)
  • Per-repeater DMRD translation - slot/TGID remap and outbound rf_src override declared via RPTO (see DMRD Translation)
  • Unit (private) call routing - User cache with broadcast fallback, subscriber-pair hang time, cross-slot support, and optional forwarding over outbound server links (implicit reverse-path tree when peers are HBlink4)
  • Pattern-based repeater configuration and blacklisting
  • Per-slot transmission management

Installation

⚠️ IMPORTANT: Clone and run HBlink4 as the same user account. The systemd service files are configured to run as the user who owns the installation directory. The dashboard writes files for persistence across restarts and needs write access as well.

  1. Clone this repository:
git clone https://github.com/yourusername/HBlink4.git
cd HBlink4
  1. Create a virtual environment and activate it:
python3 -m venv venv
source venv/bin/activate  # On Windows: venv\Scripts\activate
  1. Install requirements:
pip install -r requirements.txt

Configuration

Copy the sample configuration file and modify it for your needs:

cp config/config_sample.json config/config.json

See the Configuration Guide for complete documentation of all settings.

Running

Production (systemd services)

For production deployments with automatic startup, see SYSTEMD.md.

Development

# Start all services together
./run_all.sh

# Or start services separately:
python3 run.py              # HBlink4 server
python3 run_dashboard.py    # Web dashboard (in another terminal)

Access the dashboard at http://localhost:8080. See Dashboard Documentation for features and configuration.

Documentation

Comprehensive documentation is available in the docs/ directory:

Support

No end-user support is provided. The development team for this software is exactly 1 person, with limited resources and no ability to duplicate environments for testing. Flagging genuine code issues is apprecicated, but please to not open issues because it doesn't work the way you'd like it to. There are no feature requests.

Contributing

Contributions are welcome! Please feel free to submit a Pull Request. Do not submit a Pull Request to the main branch for added features without consultation first. Added features may collide with other mainline features under development, and additions that are inconsistent with the goals of the project may not be accepted. If you want to add a feature, it's best to discuss it first. Use alternative branches named for the feature being added.

License

Copyright (C) 2016-2025 Cortney T. Buffington, N0MJS n0mjs@me.com This project is licensed under the GNU GPLv3 License - see the LICENSE file for details.

Acknowledgments

  • Original HBlink3 by Cort Buffington, N0MJS
  • The MMDVM and DMR community
S
Description
No description provided
Readme
3.8 MiB
0 Stars 1 Watchers 0 Forks
Languages
Python 77.9%
HTML 20%
Shell 2.1%