Ben Allfree

Mark Spencer lives in Coleville, down on the eastern slope of the Sierra where the mesh had never reached. We met at the Minden user-group summit about six months ago and kept in touch. His vertical antenna comparison is one of the more practical pieces on the site. In conversation he mentioned that Coleville still had no real mesh coverage and that he had once caught a brief glimpse of Meshtastic traffic, possibly from Mount Rose. That was enough for me. I offered to load up the Jeep and stake a node somewhere that could actually serve his town.

I fired up Peaky Finders and ran a goal-seeking pass toward Coleville. The algorithm pointed at Bald Mountain, a summit that already hosts ALERT wildfire cameras. From that ridge the model showed clean lines to McClellan Peak, Davidson Peak, and Flowery Peak above Virginia City. One well-placed repeater could light up Smith Valley, Coleville, Walker, and the whole Topaz Lake area. For the price of a single backbone node we could cover a basin that had been dark on our map. It felt worth a diversion from the other work on the calendar.

On the evening of April 13, 2026, a magnitude 5.7 earthquake struck near Silver Springs in Lyon County, about an hour east of Reno. Strong shaking rolled through Fallon, Carson City, and the Truckee Meadows. The USGS recorded more than two dozen aftershocks in the hours that followed.

While residents checked on neighbors and store aisles picked up the pieces, something else was happening on the air. The Nevada mesh network saw a sharp increase in traffic. Handheld nodes and repeaters kept passing messages through the event and its aftermath.

We call it Poitito, little Poito. It sits on a rocky flank of Poito Mountain, a short walk from Dave Metts's radio compound but not on it. Ever since we placed the main Poito repeater at the tower site, I have wondered whether sitting so close to all that existing radio equipment was causing interference. I ask the same question about McClellan Peak. It is slowly becoming confirmed through empirical data that co-locating on a radio tower is not always the best option, even when the option is available. The problem comes down to ideal placement, not proximity to steel.

When we deployed Russell Peak, Ruslito stayed behind as a soldier node. I wanted to compare two vantage points in close proximity and see which one performed better. I never meant to leave both nodes up for long. The comparison gave us useful data. Then Ruslito needed to come home.

That first Russell Peak trip I had almost no gear with me. Ruslito got the full jank treatment.

I was exhausted after several days of working the Reno backbone out to Gerlach and the Black Rock Desert, and I wanted to go home. One of my goals for the trip was a site survey on Fox Mountain: walk the summit, see what it hears, and figure out whether a repeater there is worth pursuing and where it should sit. I had been exploring around Soldier Meadows and playing around in the Jeep doing range tests out that way when onX Offroad told me I could get to Fox Mountain from where I was. It might even be true. Sometimes it sends me down the worst roads just because they are the shortest path on paper.

For a long time we could not get a response from Russell Peak. I assumed the worst. Maybe a storm had ripped the node off the mast, or wind and vibration had finally finished what desert summers start. The peak sits on a lonely stretch of the backbone toward Poito Mountain and the Black Rock corridor, and when a site like that goes dark you do not get many clues from Reno.

When I bought my first mesh radio, I honestly thought I would turn it on and start talking immediately. That is not what happened. I ran into settings, radio frequencies, and terminology I had never needed before. The app did not work very well either. The whole experience was sobering. If I was struggling, I could not imagine a busy parent having any luck at all.

That parent is the avatar I keep in my head. I picture a mom who drops something the size of an AirTag into her purse, opens an app on her phone, and gets help when she needs it. Flat tire, kids in the car, middle of the desert, no cellular reception. I want that to work without her needing a crash course in LoRa presets first.

I also think about the backpacking photographer who knows his trade and his camera gear cold, but not mesh networking. I want him to reach the farthest corners of Nevada, stay in touch with his group, or call for help without needing the equivalent of a ham operator's license to do it.

EnvyOS is what I am building toward: a comprehensive distribution with firmware, a bootloader, and client apps that fit together from the first launch. I am sharing it now because the pieces are starting to line up, not because the whole vision is finished.

The local and regional Meshtastic community in Nevada has grown enough that we are moving our Meshtastic repeaters to Medium Fast (MEDIUM_FAST). That is the preset we now recommend for anyone joining the MeshEnvy Meshtastic layer. If you run Meshtastic in Reno, Carson, or anywhere you can reach our community repeaters, this is the setting to match.

MeshEnvy is announcing a partnership with Burning Mesh, the community that has spent years bringing off-grid mesh communications to Black Rock City. They built the playa network that keeps camps, art cars, and adventurers connected when cell service disappears. We just closed the loop back to Reno. That is the hello Reno milestone we set our sights on for the 2026 burn, and Burning Mesh is the partner that makes the playa side of it real.

MeshEnvy is announcing a partnership with the Black Rock Amateur Radio Association (BRARA) in cooperation with the Black Rock Rangers and Ranger Outpost Gerlach (ROG). Together they gave us the final link we needed to carry messages from the playa back to Reno. That is the corridor we have been chasing since our first goal post, and I did not expect to close it on a day I thought was just an information-gathering trip.