Gateway firmware setup and registration requires IT or super-admin access. See Gateway Firmware Setup for initial provisioning steps.
How Gateways work
A Gateway self-registers with Forager on first boot using Zero-Touch Provisioning (ZTP): it sends its hardware MAC to thegateway-claim endpoint and receives a cryptographic API key, which it stores in non-volatile storage (NVS). No manual key entry is required.
Once claimed, the Gateway:
- Initializes ESP-NOW immediately on boot to capture Raven broadcasts during LTE attach
- Connects to the cellular network via the Hologram SIM
- Batches incoming Raven check-ins in a ring buffer
- Uploads all buffered check-ins to Forager every 5 minutes over LTE-M
Gateway Fleet screen
Raven Fleet → Gateways tab shows all registered Gateways for your company:Signal quality guide
Placement guidelines
- One Gateway per floor is usually sufficient for most facilities. Add a second if the floor has large concrete sections or RF-blocking server rooms.
- Mount at a central point on the floor, elevated (above false ceiling tiles works well).
- Keep the LTE antenna unobstructed — avoid metal enclosures.
- Power via USB-C wall adapter or PoE injector with USB-C adapter. The Gateway has no battery — it requires continuous power.
- The Gateway needs cellular coverage. Check Hologram’s coverage map for your address if signal is poor.
LED status
The Gateway has a single status LED on GPIO 12:SIM management
Gateways use Hologram eUICC SIMs on the Global-3 plan. Manage SIMs at dashboard.hologram.io:- Connected — Gateway is active and has a data session open
- Idle — SIM is active but no current data session (normal between uploads)
- Deactivated — SIM needs to be reactivated
Troubleshooting
Gateway shows Offline in the fleet view- Check the SIM status in Hologram dashboard
- Confirm the LTE antenna is attached
- Connect via USB and check serial output (115200 baud) —
SHOW_SIGNALshows live RSSI
- Both Raven and Gateway must be on WiFi channel 1 — this is locked in firmware on both sides
- The Gateway initializes ESP-NOW before connecting to LTE. If Ravens broadcast before the Gateway has finished booting, reset the Raven manually once the Gateway serial output shows
[gw] ESP-NOW receiver ready - Check serial output on the Gateway — incoming ESP-NOW packets print
[gw] rx mac=...
HTTP 401— API key mismatch. The Gateway may need to be re-claimed: clearapi_key_hashin the database and power-cycle the Gateway to trigger ZTP againHTTP 500— Edge Function error. Check Supabase function logs- Connect error — cellular issue. Run
SHOW_SIGNALand check SIM status in Hologram dashboard