Build your own DMR hotspot: the complete guide
A hotspot is a tiny box about the size of a matchbox that turns your digital radio into a full-fledged network node, even if the nearest repeater is two hundred kilometres away. Essentially it is a miniature 10–20 mW transceiver that picks up the signal from your radio, packs the voice into IP packets and sends them out to the network over your home internet. The return path is the same: whatever is said on your talkgroup arrives over the internet and goes out on the air for the couple of metres to your radio.
If you are new to DMR and want to get on the air not just when you happen to hear a repeater, a hotspot is the first thing worth building. Below we break down what it is made of, what hardware to buy, how to flash the image and get going in ten minutes, and where newcomers usually trip up.
What a DMR hotspot is and why you need one
The classic digital-comms chain looks like this: radio → repeater → internet network → another repeater → someone else's radio. A repeater is an expensive fixed piece of kit on a mast, and they are far from being everywhere. In most regions of Russia there are simply no DMR repeaters, and the ones that exist are often closed departmental systems.
A hotspot solves the problem radically: it plays the role of a personal micro-repeater itself. You keep it at home on the windowsill, the radio talks to it at minimal power, and the home internet handles all the long-haul "leg". No mast, no frequency coordination — just a small "stub" antenna and USB power.
On our network a hotspot gives you everything at once: your own talkgroups, private calls by DMR ID to a specific operator, text DMR SMS straight from the radio, and a Last Heard list of who got on the air and when. For duty traffic in a group, or simply to stay in touch with fellow hobbyists, that is more than enough.
What a hotspot is made of
Structurally it is extremely simple — there are literally four parts:
- A single-board computer — usually a Raspberry Pi. This is the brain: it runs the OS, the hotspot software and the connection to the network.
- An MMDVM modem — a "hat" board (HAT) that mounts onto the Pi's GPIO header. This is what contains the radio part: the transceiver and the microcontroller that handles DMR modulation. For more on the internals and choosing a modem, see the article on building an MMDVM hotspot.
- An antenna — a short SMA whip for the band you need (usually 70 cm / UHF, less often 2 m / VHF). It comes bundled with the modem.
- Power — a decent 5 V supply rated at 2–3 A and a good cable. This is not a trifle, and we will come back to it.
Optionally the modem may have a little OLED display that shows who is currently on the air, the frequency and the mode. It is a nice touch, but not essential — there is a separate note about it.
Choosing hardware: what a beginner should buy
The single-board computer
From on-air experience: for a simplex hotspot a Raspberry Pi Zero 2 W is more than enough. It is cheap, tiny, has built-in Wi-Fi, and handles the job without breaking a sweat. There is no point buying a Pi 3B or Pi 4 — that is overpaying and extra heat, and the hotspot does not need their power. If you cannot get a Zero 2 W, an old Zero W will do too, but it is noticeably slower during the initial setup.
The modem: simplex or duplex
There are two kinds of board here, and they often confuse newcomers:
- Simplex (HS_Hat and similar) — one frequency for receive and transmit, alternately. Cheaper, simpler, runs cooler. This is the workhorse for a personal hotspot.
- Duplex (Dual_Hat, MMDVM_HS_Dual) — two frequencies at once, two independent timeslots. Needed for a full repeater, or if you really want to sit on two TS simultaneously. More expensive and harder to calibrate.
We cover the difference in detail in the article HS_Hat or Dual_Hat. In short, for our network: get the simplex board. We work on TS2, an ordinary operator does not need duplex — it is extra money and extra fiddling with setup for a feature you will not use.
What to watch out for when buying
Marketplaces are full of clones of varying quality. Try to buy boards based on the ADF7021 chip with proper shielding. Really cheap "no-name" modems often drift off frequency and hold calibration poorly — you will end up fighting them.
Flashing the image and the first boot
This is where the line is drawn between "built it in an evening" and "still poking at it on the third weekend". The classic route is to install Pi-Star and manually enter the callsign, frequency, network settings and keys. It works, but it requires understanding what you are doing.
We took a different route. The RadioStar image is a ready-made system tailored to our network, where almost everything configures itself. The procedure is as follows:
- Download the RadioStar image and write it to a microSD card (8 GB or larger, class 10) using Raspberry Pi Imager or balenaEtcher. The detailed step-by-step is in the article about the RadioStar image.
- Insert the card into the Pi, fit the modem, connect the antenna, apply power.
- On first boot the hotspot brings up its own Wi-Fi access point, RadioStar-Setup. You connect to it from a phone or laptop, enter your home Wi-Fi and password — nothing else needs typing by hand.
- From there the hotspot goes to the portal itself and pulls its configuration from there: frequency, the binding to your account, network parameters. All you have to do is specify your DMR ID on the portal.
After setup the system keeps itself current on its own: updates arrive over the air (OTA), you do not need to rewrite the card or dig into the console over SSH. If you used to run Pi-Star and want to switch over, there is a separate walkthrough on migrating from Pi-Star to RadioStar.
Network and NAT: no port forwarding needed
A beginner's most common fear: "but I have a private IP / an ISP router / NAT — so I have to forward something, right?" No. And this is important to understand.
The hotspot always initiates the outbound connection itself to the network server. It reaches out, the server replies within the already-open session — exactly the way your browser opens a website. NAT is transparent for outbound connections; no port forwarding on the router needs to be configured.
This works behind a home router, behind an ISP's NAT, over mobile internet from a phone's tethering, and even behind double NAT. If the hotspot still will not get on the network, the cause is almost never port forwarding but a wrong Wi-Fi password, a dropped internet connection, or outbound traffic being blocked on the router. We covered the systematic diagnosis of this case in the article about a hotspot behind NAT and in the general checklist when the hotspot is offline.
Calibration and typical problems
Say the hotspot is on the network, visible on the portal, but the radio "cannot hear" it or hears it with a crackle. Nine times out of ten it comes down to one of two things.
Frequency drift
The crystal on cheap modems wanders, and the modem's actual frequency can differ from nominal by several hundred hertz. The cure is calibration — finding the correction (RX/TX offset) at which the link becomes clean. Our image has a convenient mechanism for this right in the panel, so you do not have to sweep the frequency by hand in the console. The full breakdown is in the article about frequency calibration.
Power
I will say it again, because it is problem number one: poor power kills the link. A cheap 1 A charger or a thin Chinese cable causes a voltage sag, the Pi starts misbehaving, errors pile up in the logs, and from the outside it looks like "the modem is glitching". Get a 5 V / 2.5–3 A supply and a short, thick cable. If you see a lightning-bolt / undervoltage icon in the corner of the display or in the logs, change the power supply first thing.
Other pitfalls
- The radio and the hotspot on different frequencies/timeslots. Check that the radio's channel has the same frequency, color code (CC) and timeslot (TS2 on our network) as the hotspot.
- An antenna for the wrong band. A UHF whip on a VHF modem (or vice versa) — the link will break up within a couple of metres.
- Clean logs, but the radio is not receiving. If everything is perfect on the hotspot side and there is still no reception, dig into the firmware and settings of the radio itself — the cause is often there.
Build your hotspot and get on the air today
DMRhub is a private DMR network with its own talkgroups, private calls by DMR ID and DMR SMS. Create an account, get a DMR ID, and the hotspot will configure itself from the portal.
Summary
A DMR hotspot is the cheapest and fastest way to get into digital radio where there is no repeater. The hardware needed is minimal: a Pi Zero 2 W, a simplex MMDVM modem, an antenna and a decent power supply. No port forwarding needs to be configured — the hotspot reaches out on its own. The main sources of trouble are predictable: power, frequency calibration, and matching the radio's settings to the hotspot.
And all the hassle of manual Pi-Star setup is gone with us: the ready-made RadioStar image brings up the RadioStar-Setup access point, pulls its configuration from the portal and then updates over the air. You create an account, bind your DMR ID — and in ten minutes you are on the air, with your own talkgroups, private calls, DMR SMS and Last Heard. The voice meanwhile passes through a server-side AMBE vocoder, so the hotspot needs no paid codec licenses. Welcome to the network.
Sources
- G4KLX, MMDVMHost — source code and documentation for the MMDVM host software (GitHub)
- Pi-Star — the project's official site, images and guides
- EA7EE/CA6JAU, MMDVM_HS — firmware for HS_Hat/Dual_Hat modems (GitHub)
- DMRhub Knowledge base materials: the RadioStar image, frequency calibration, diagnosing a hotspot behind NAT.