News & Notes

Notes from the foothills.

Technology, preparedness, and lessons in emergency communications — written slowly, when there is something worth saying. For anything happening right now, the Live Feed is the place.

Why GMRS repeaters are kept local

For a lot of foothill households, a General Mobile Radio Service (GMRS) radio is the simple fallback for when the cell bars and the power go at the same time — a licensed two-way band that works handset to handset with no tower in the path. A recent federal enforcement action is a useful reminder of one boundary on what a GMRS repeater is allowed to do, and why that boundary sits where it does.

The action

On August 10 the FCC’s Enforcement Bureau issued a Notice of Violation to the head of a Georgia GMRS group whose system had grown to nearly two dozen repeaters connected to one another over the internet. Agents had observed in February that the linked repeaters were relaying a single message across all of them for simultaneous transmission over a wide area. That, the notice says, violates Section 95.1749 of the FCC’s rules. The licensee was given 20 days to respond.

The rule itself is short. A GMRS repeater “may be connected to the public switched network or other networks” — but only “for the sole purpose of operation by remote control.” Wiring repeaters together to pass traffic between them, so a conversation carries past the range of the radios actually in it, is not remote control. It is linking, and for GMRS it is not permitted.

Why the line is drawn there

The reason is spectrum, not caprice. GMRS shares eight repeater channel pairs nationwide among more than 300,000 licensees, the FCC’s notice notes. On a standalone repeater those channels are reused constantly — a canyon in California and a valley in Georgia hold entirely separate conversations on the same pair, because neither hears the other. Link a chain of repeaters together and one conversation occupies the channel across every place the chain reaches, crowding out everyone else on a resource there is very little of.

Amateur (“ham”) radio, which requires an exam and is allotted far more spectrum, does permit repeater linking. GMRS, which asks only a $35 license and no test, keeps each repeater local instead. That is the trade that comes with the low doorway in.

What it means for a home plan

For anyone weighing GMRS as part of a household or neighborhood communications plan, the practical read is straightforward. A single well-sited repeater covering a watershed is exactly what the service is built for, and it is legal. A wide-area, internet-linked GMRS “network” advertised as reaching across counties is not — and a plan that leans on one is leaning on something the FCC can order shut down. If you join a local net, it is worth knowing whether the repeater you reach is a standalone machine on a ridgeline or a node in an internet-linked chain. The first is GMRS as designed.

Those eight shared channels are the whole reason for the rule. Keeping each repeater local is what lets them carry hundreds of thousands of separate local conversations at once — the ordinary, license-light service a foothill household is actually reaching for.

How to read a Red Flag Warning

Through the back half of a foothill summer, two phrases show up in the forecast often enough to blur together: Fire Weather Watch and Red Flag Warning. They are not the same alert, and the difference is the useful part. This week is a live example — the National Weather Service has the Sierra foothills under elevated fire weather conditions alongside a heat advisory, with valley and foothill highs of 102 to 108 through Sunday. Elevated is the middle rung. Here is the rest of the ladder.

Watch versus Warning

A Fire Weather Watch is about potential. The weather service issues one when the ingredients for dangerous fire weather — some combination of low humidity, wind, and dried-out fuel — look likely to come together in the next day or two, but are not here yet. It is a heads-up with lead time attached.

A Red Flag Warning is about the present. The weather service issues it, in its own words, “to alert land managers to an ongoing or imminent critical fire weather pattern” — the conditions are happening now, or will within hours. A Watch can firm up into a Warning as forecasters gain confidence, or expire without one if the wind never arrives.

Neither is a prediction that a fire will start. Both describe weather that would let a new start spread fast and burn hot: dry air pulling moisture out of the grass and brush, wind to carry embers past a control line. The exact thresholds are set locally. NWS Sacramento, the office that forecasts for Calaveras and Tuolumne, keys its warnings to the low humidity and sustained wind its forecasters know move fire in this terrain.

Where you already see it

The Live Feed carries a fire-weather status on the same ladder the weather service uses: Normal, Elevated, Red Flag. When it reads Red Flag, it is mirroring an active NWS Red Flag Warning for the area — not a judgment of our own. The authoritative product, the one that names which zones and until when, lives with NWS Sacramento. The Live Feed points to it; the weather service is the source.

Of the two alerts, the Watch is the one with room to act in it. It is the window before the weather arrives — time to top off water, check the generator fuel, and settle how the household will reach each other if the power goes out and the cell bars follow it down. A Red Flag Warning, by the time it posts, is confirmation that the window has closed and the weather is doing what it was forecast to do.

Curious about the network? Get in touch via the contact page.

What the MeshCore trademark fight can't touch

The open-source software that runs the LoRa mesh relays in these foothills has spent the summer in a legal dispute — not over how it works, but over its name. It is worth understanding what that fight does and does not put at risk.

MeshCore is the routing protocol S.I.E.R.R.A’s solar relays run on: the software that lets a network of low-power LoRa radios pass short text messages hop by hop when there is no cell tower in the path. After a split in the project’s core team earlier this year, a former member filed to register “MeshCore” as a trademark — in the United Kingdom in late March and the European Union in April, by the project’s own account. The remaining team, which treats the name as the community’s, is opposing both filings. As of late July the opposition is formally lodged and the trademark sits in “opposed” status — in the team’s own words, “a waiting game,” with no guaranteed outcome. The project estimated roughly $18,000 in legal fees to see it through and raised that through a community fundraiser that concluded in late July.

That is the news. The more useful part is what a trademark actually governs.

A name and its code are separate things

A trademark is a claim on a name and a logo — on branding. It is not a claim on software. MeshCore’s firmware and core libraries are released under the MIT License, one of the most permissive open-source licenses there is: anyone may use, modify, and redistribute the code, for any purpose, commercial included. That grant is already made. It cannot be pulled back by a later dispute over the name, and it does not depend on who wins one.

So whatever a trademark office eventually decides, the code already on a repeater stays exactly as free to use as it was — still readable, patchable, and rebuildable by whoever maintains it. The project has said development carries on regardless, with a 1.17 firmware release in progress.

Why the license is the part that matters

This is the quiet argument for building resilient infrastructure on open-source rather than a vendor’s product. A company can fold. A product can be discontinued and its servers switched off. A brand can be sold or contested, as this one is now. None of that reaches MIT-licensed code that is already in hand — the version compiled onto a relay is yours to keep, run, and maintain even if everything else about the project changed tomorrow.

For anyone deciding whether to put weekends into learning a platform — or a district weighing what to standardize on — the license is the part worth reading first. It is what separates infrastructure you operate from infrastructure you only rent. The MeshCore name may be settled by a trademark office over the coming months. The terms that let a community depend on the software were settled the day the code was published under a license that cannot be revoked.

S.I.E.R.R.A Applies for Calaveras Grant

In foothill and mountain communities like Calaveras County, staying connected isn’t just a matter of convenience—it can be a vital lifeline. Between winding mountain terrain, seasonal wildfires, winter storms, and Public Safety Power Shutoffs (PSPS), traditional cellular and internet infrastructure can easily drop out right when residents need it most.

To help solve this challenge, S.I.E.R.R.A has officially applied for competitive grant funding through the Calaveras Community Foundation. If awarded, it will fund the expansion of our off-grid MeshCore network along the critical Highway 4 Corridor, bringing 10 brand-new repeaters and educational workshops to local residents.

Who is the Calaveras Community Foundation?

For those unfamiliar with local philanthropic efforts, the Calaveras Community Foundation (CCF) is a 501(c)(3) public charity dedicated to enhancing the quality of life across Calaveras County. Since its inception in 2000, the Foundation has distributed over $3.3 million in grants, assistance, and scholarships to support worthy local projects. It runs a competitive grant cycle each year for local nonprofits, schools, and units of government; in 2024 it awarded grants to 29 organizations.

10 New Repeaters Along Highway 4

The Highway 4 Corridor stretches through diverse elevation changes—from Angels Camp up through Murphys, Arnold, and beyond into Bear Valley. The region’s rolling hills and dense timber frequently create cellular dead zones where standard mobile service fails.

If awarded, this grant will fund the purchase and deployment of 10 strategic MeshCore repeaters.

What Are MeshCore Repeaters?

  • Decentralized & Off-Grid: MeshCore uses low-power LoRa (Long Range) radio frequencies. Nodes communicate directly with each other without relying on cell towers, satellite links, or grid power.
  • Solar & Battery Powered: Repeaters can be mounted on rooftops, towers, or elevated property and run on solar and battery power rather than the grid.
  • Deliberately Placed & Maintained: MeshCore is not a self-healing swarm. It relies on a small number of deliberately placed, maintained repeaters that hold known routes between them. If a repeater goes down, its route is restored by the team that keeps it running, not by nodes re-routing on their own.

Empowering the Public: Educational Seminars

Technology is only as effective as the community using it. A core pillar of our grant proposal is hosting a series of free educational seminars across Calaveras County. Our Goal: Demystify off-grid radio communications and put accessible messaging tools directly into the hands of everyday residents. These public workshops will cover:

  1. MeshCore 101: What mesh networking is, how it differs from Wi-Fi or cellular service, and how it operates during major utility power shutoffs or disasters.
  2. Getting Started on a Budget: Demonstrating how affordable, pocket-sized LoRa radio devices—commonly in the $60–$100 range, such as the RAK WisMesh Pocket v2, which listed for $84.97 at Rokland as of July 2026—connect via Bluetooth to your smartphone to send off-grid text messages.
  3. Emergency Preparedness Workflows: How families, neighborhood watch groups, and local volunteers can set up private channels for neighborhood check-ins during storms or evacuations.

What Does This Mean for You?

For the general public, the goal of an expanded MeshCore network along Highway 4 is a way to send short text messages that does not run through a cell carrier or depend on grid power—if the grant lands and the network is built out.

Looking Ahead

As climate shifts and extreme weather events continue to challenge conventional utilities, building grassroots infrastructure is no longer optional—it’s essential. S.I.E.R.R.A is proud to take this next step. We hope to receive grant notification later this year. In the meantime, keep an eye on our community announcements for upcoming meeting dates, node placement updates, and seminar schedules! Be Safe and Stay Connected
Jay Goldberg, Founder

What a fire-country radio net needs to work

A canyon with one road out and thin cell coverage is a familiar setup in the Calaveras and Tuolumne foothills. It is also the exact problem two mountain communities elsewhere have been solving with volunteer radio, and their networks are worth a look at the height of fire season — because the part that makes them work is not the equipment.

The fast part, and the slow part

In May, residents of Weber Canyon in Utah’s Summit County switched on a solar-powered GMRS repeater built on a donated half-century-old television tower on the canyon’s northern ridgeline. GMRS — the General Mobile Radio Service, a licensed UHF two-way band — carries voice between handhelds with no cell tower in the path, and a single ridgeline repeater extends that range across a whole watershed; the Weber Canyon net now reaches out to Oakley, Kamas, and Park City. The project began after a resident watched a documentary about the 2018 Camp Fire and recognized his own canyon in it: sparse cell service, one way in and out. The license is a flat $35 for ten years, no exam, and the repeater itself needed FCC approval.

The radio was the fast part. About 30 people now check in on a monthly roll call — first Tuesday, 8 p.m. That standing net is the point. A radio that has sat in a drawer since the day it was bought is not a communications plan; a group that keys up together every month, on a known channel at a known time, is. The roll call is where a member learns whether their handheld actually reaches the repeater from their own property — which is not something to find out during an evacuation.

The longer proof

California’s own fire country has the longer-running version. After the 2015 Valley Fire destroyed 1,300 structures and killed 4 people in Lake County, survivors in Cobb built the Cobb Alert Net, documented by the Fire Adapted Communities Learning Network. It now counts 270 participants across 85 square miles and 7 hamlets, organized in three tiers: a small core of licensed amateur (“ham”) radio operators, 34 GMRS operators who serve as neighborhood leaders, and residents who use the simplest license-free Family Radio Service walkie-talkies. It practices weekly, 20 to 60 minutes at a time.

The tiers are what let it scale. A neighbor can join at whatever level they are ready for — an FRS radio off a store shelf, a $35 GMRS license, or a full ham ticket — without being left out of the net. Nobody has to clear the highest bar to be reachable.

What carries across

Two things translate to the Highway 4 and Highway 49 corridors. First, the hardware is the cheap, quick part; the network is the people who practice with it. Second, both nets were built deliberately, before the season they were meant for — the same order of operations as clearing defensible space or packing a go-bag. A GMRS license covers an entire household and takes no exam, which makes it the low doorway in. The higher-value step is finding out whether your road, ridge, or water district already runs a net. In Calaveras County, one already does: the Ebbetts Radio Safety Net, the volunteer GMRS net that S.I.E.R.R.A grew out of, holds three practice nets a week — Monday out of Murphys, Wednesday and Saturday out of Arnold. Where no such net exists yet, a handful of neighbors and one repeater is all Cobb and Weber Canyon started with.

Both communities stood up their nets in an ordinary month rather than a dangerous one. The monthly or weekly schedule is what turned a pile of radios into a network that answers.

Signal Desk is S.I.E.R.R.A’s automated news desk. Drafts are reviewed by a member before publication. How it works: /colophon.