Troubleshooting Guide

Every setup goes quiet once in a while — a hub that won't check in, a gateway with no lights, a far node that keeps dropping out. The good news is that almost all of it comes down to a short list of causes, and most of them you can sort out yourself in a few minutes. This guide walks through each piece of the system in turn, and I'll tell you exactly when to stop fiddling and let me look at it from my end.

When Your Cellular Sensor Hub Shows Offline#

Go to the hub and, before touching anything, look at the button light — is it flashing, breathing, or something else? That first observation tells us a lot, so make a note of it.

If the light is off completely, wait at least 30 seconds before you do anything. The hub tries to power-cycle itself when it can't connect, so give it a chance to come back on its own.

If it doesn't, power it off — including unplugging the USB — wait 10 to 20 seconds, and turn it back on. See if it connects then.

Still nothing? Move it to another location — take it home with you — and see if it connects anywhere else. This is the single most useful test, because it tells us whether we're dealing with a hub problem or a cellular-signal problem at your site. On my end I can see the device's last carrier, tower, and signal strength, so relocating it helps me rule out hardware versus carrier.

One more thing to keep in mind: if the battery drops below 5%, the hub hibernates and won't recover until it has power again. If that's your situation, see the Power & Battery guide.

When Your Gateway Shows Offline#

A few things to check, in order:

  • Lights on the bottom of the unit. No lights means it isn't getting power at all.
  • The Ethernet cable is plugged into the "POE" side of the PoE injector, not the LAN side. This is the common mistake — it's an easy one to make.
  • How long it's been powered and trying to connect. Give it some time before you conclude it's dead.
  • What uplink you have there — cellular only, or Wi-Fi/Ethernet? That changes what we look at next.

Once it's powered correctly, the bottom lights blink and the gateway comes online, ready for nodes.

One more root cause I've seen in the field: a gateway hitting a SIM data limit. That one you can't fix on site — I resolve it on my end, so just reach out.

Nodes That Keep Dropping Out#

Usually it's the farthest nodes that give you trouble. Diagnose before you rearrange anything.

Sort out what kind of problem it is#

Power a node on and watch the LED. Then bring it close to the hub and power-cycle it:

  • If it connects up close, you've got a range, antenna, or repeater issue.
  • If it won't connect even right next to the hub, it's likely battery or hardware.
  • If multiple nodes are down at once, check that the hub itself is online before blaming the nodes.

For links that are weak or keep flapping, I can read hops and signal strength under the device settings. One pattern to know: a node that's physically close to its repeater but showing very low signal usually means a bad antenna. Swap the antenna — or move the node right next to the hub to confirm the diagnosis.

Getting a far node back after a hub swap or reboot#

Put the hub in burst mode, wait about 10 minutes, then power the node off and back on. That gets the far node reconnected.

The long-term fix for a property that's fighting range#

If you're constantly battling to keep distant nodes connected, my usual recommendation is upgrading the hub to a gateway. Nodes talk straight to the gateway — no repeater games — and it's much more consistent. Your existing nodes are compatible; they just need a software update you can do yourself.

Send me a rough map of your property with the node locations and I'll lay out a path for you.

FAQs

It depends whether it's fleet-wide or just you, and I can tell from my back-end by comparing the device count before and after. If our main cellular provider has an outage, it can knock out a big chunk of the fleet at once — those recover on their own, and typically the fleet is back within 1–2 hours once the carrier resolves it. If it's just your device, it's usually the standard offline flow above (or it quietly reconnected on its own already). Outages like this are rare, but they can happen — reach out and I'll confirm which one it is.

Yes. Sometimes a device stays connected but stops sending data. I can "give it a kick" and reboot it from my side, and it starts sending again. It's rare — only a few cases across the whole fleet — and normally once we kick it, it's good from there. If you notice it happening again, let me know.

App-side "offline" is a different animal from a device being offline. It's usually just an expired login — log out and log back in from the three-bar menu and it clears right up.

Probably not. Your gateway can be online and working in our back-end — processing node messages — while the separate remote-management portal (WISDM, from the gateway maker) shows it offline. Often that's because firewall rules on your router block traffic to that console. It doesn't really matter as long as the nodes reach the SapSpy backend and forward their data — that's the critical piece. I wouldn't worry about the gateway showing offline as long as sensor data is flowing; we can dig into it at the end of the season.

Was this helpful?

Have a question this doesn't answer? Email info@sapspy.com or call 920-809-4811 — we're producers too.