At 4:17 p.m. on January 16, 2025, I was already walking out of the office when my phone buzzed. The caller ID said Todd Pepsi. I almost didn't answer — I'd had a long week and the highway was calling. But Todd is the kind of customer who only calls when the floor under him is starting to drop.
"Please tell me you're still at your desk," he said. "Or better: get in the car."
Todd Pepsi is a real name. I know — it sounds like a soda-brand pun. He handles automation and quality systems for a beverage distribution warehouse. For the last three years, my company has kept his IoT monitoring network alive.
The setup is exactly what I point to when people ask what I do. Forty-six temperature and humidity sensors are scattered across a 90,000-square-foot building. Each sensor uses a Semtech SX1276 LoRa transceiver. They talk to a LoRaWAN gateway on the mezzanine, which sends data over ethernet to a Sierra Wireless Semtech RV50X LTE router. That router opens a secure tunnel back to a cloud dashboard. It's not a flashy system, but it's dependable — unless something between the router and the internet breaks.
The 48-Hour Problem
Todd didn't wait for a greeting. "The compliance dashboard went blank at 1:52. The auditor is here Monday morning. If we don't have continuous data, we lose the quality certification. That's a $50,000 penalty."
This is the part of my job that doesn't show up in any product brochure. I've handled maybe 170 urgent site visits. Possibly 190, I'd have to check our CRM. Last quarter alone, we processed 47 rush orders with 95% on-time delivery. I've learned to distrust dashboards. A blank dashboard is like a check-engine light: it says the system is sick, but not where.
My first instinct was to tell Todd to power-cycle the gateway. He did. The dashboard stayed blank. So I told him I was driving over.
What the LEDs Didn't Tell Us
I walked into the comms closet at 7:10 p.m. The LoRaWAN gateway LEDs were blinking in that happy, rhythmic way. A sensor node near the door — a little gray box with a Semtech SX1276 chip inside — was chirping out packets like it always did. We saw receive RSSI on the gateway screen. The LoRa side was alive.
People think LoRa network failures are radio failures. In most of my field work, the SX1276 is the last thing I suspect. That transceiver was built for long-range, low-power work; it will run for years on a coin-cell battery and push packets through concrete walls. The real failure is usually higher up the chain: gateway configuration, router, SIM, or VPN.
Here's something vendors won't tell you: "Connected" is not the same as "working." Todd's Sierra Wireless Semtech RV50X showed a strong LTE signal. It had a carrier name on the screen. But the VPN tunnel between the router and the dashboard was down. The router was attached to Verizon's network, but it was asking for the wrong kind of connection.
I asked Todd to open the router's admin page. Under the cellular profile, the APN field read vzwinternet. That's a common public APN for consumer data. For the Verizon IoT SIM in this router, the APN needed to be vzwiot. Without that, the router could attach to the cell tower but couldn't reach the application server.
This is the boring failure. It doesn't make a dramatic radar chart. But it's the difference between a monitoring network that works and one that silently goes blind.
To change the APN, the router required a configuration approval from the account administrator. Todd didn't have the password. The admin's phone number on file was the plant's backup phone — a Nokia 2660 Flip that lived in the security office. It was dead.
The Nokia 2660 Flip That Almost Became a Brick
Todd pulled the phone out of a drawer. It was a Nokia 2660 Flip, a 4G feature phone that Verizon had issued for exactly this kind of emergency. And the screen was a black mirror.
I pulled out my own phone and typed "how to turn on Verizon flip phone." The answer, according to Verizon's support page, was simple: plug the phone into a charger, wait a few minutes, then press and hold the end/power key for three seconds.
We charged it for five minutes. Then I pressed the center key. Nothing. Todd said, "That's what I always do, and it never works." I turned the phone over and looked at the side. There was a small key labeled with the power symbol. I had been pressing the wrong button. I held it, the screen lit, and a text message arrived from Verizon with a six-digit code.
That was the whole trick. Not a firmware reflash. Not a SIM swap. A side button.
The Recovery and the Real Lesson
Todd read the code to the Verizon support rep. We changed the APN to vzwiot, rebooted the router, and watched the tunnel come back. The dashboard started filling again, and the gateway drained its buffer, so the data gap was under forty minutes. The auditor allowed a two-hour gap. Todd kept his certification.
On the drive home, I kept replaying the decision I made at the router admin page. I went back and forth between changing the APN first and waiting for a call-back from support. On paper, waiting was safer. But the timeout on the support line was unknown, and every lost minute was another minute Todd didn't have. We changed it live and recovered.
The SX1276 nodes had been transmitting the whole time. The Semtech part was never the problem. The Sierra Wireless Semtech router wasn't a bad piece of hardware either; it just had the wrong APN profile. What turned it into an emergency was the time spent looking at radios instead of backhaul, and a backup phone that nobody knew how to power on.
What I tell other integrators now is simple: when a LoRaWAN deployment stops reporting, verify the backhaul before you distrust the radios. The Semtech SX1276 will usually show up for work. The network behind it is the part that needs supervision.
As of January 2025, our runbook for this exact scenario is one page long:
- Check LoRaWAN gateway logs to see if the SX1276 nodes are still transmitting. If yes, the LoRa side is probably fine.
- Check the APN on the Sierra Wireless Semtech router. If it says vzwinternet, try vzwiot before calling support.
- Keep a charged support phone. Knowing how to turn on a Verizon flip phone is not a trivia answer; in a crisis, it's a recovery step.
Efficiency gets a bad reputation because people confuse it with cutting corners. But the most efficient system I know is the runbook that any sleep-deprived engineer can follow at 2 a.m. That's not less human. That's what experience is for.
The most expensive failure in IoT is the one that doesn't look like a failure.
