Skip to content

Connect ​

The Element serves its dashboard at http://sgt.local. Any browser on the same network can reach it — there's nothing to install. This page covers the two ways to get the unit onto that network, and what to do when the address doesn't resolve.

Which should I use? ​

EthernetAccess point
Choose whenYour hitting area is near a router or switchThere's no wired connection nearby
You'll needAn ethernet cable and a free router/switch portNothing — the Element broadcasts its own network
SetupPlug in and goA one-time handoff to your Wi-Fi
NotesMost reliable during a sessionDepends on Wi-Fi coverage at the hitting area

Both end in the same place: the Element on your network, reachable at http://sgt.local.

Ethernet ​

  1. Run an ethernet cable from the port on the Element to your router or switch.
  2. Power the unit on and wait for the front LEDs.
  3. From a device on the same network, open http://sgt.local.

The cable must go to a router or switch

A direct cable run from the Element to your computer will not work. The Element needs a network that can assign it an address.

Access point ​

Out of the box the Element broadcasts its own Wi-Fi network so you can reach the dashboard before it has any network of its own. The access point stays available until you join the unit to your Wi-Fi.

  1. On your phone, tablet, or computer, join the Element's network:
    • Scan the QR code on the Quick start card, or
    • Connect to sgt-ap using the password sgtsetup1.
  2. Open http://sgt.local.
  3. Go to Settings and select your Wi-Fi network.
  4. The Element joins your Wi-Fi and shuts down its access point. Your device drops off sgt-ap at this point.
  5. Reconnect your device to your normal Wi-Fi and reopen http://sgt.local.

The Element rejoins the saved network automatically on every subsequent power-on.

While your device is joined to sgt-ap it has no internet connection — some phones will quietly switch back to cellular or a remembered Wi-Fi network. If the dashboard stops loading mid-setup, check that you're still on sgt-ap.

Can't reach sgt.local while on the access point?

Browse to http://192.168.184.1 instead. That's the Element's own address while its access point is running, and it works even on devices that can't resolve .local names.

Getting the access point back ​

The access point returns on its own whenever the Element can't reach its saved Wi-Fi network — so if you've moved the unit, changed your Wi-Fi password, or replaced your router, just power it on and look for sgt-ap again.

If the unit is still joined to a network you want to move it off, reset it: press the small hole on the back of the unit with a straightened paper clip. The access point comes back and you can run through the steps above against the new network.

When sgt.local doesn't work ​

The .local address relies on mDNS, which most operating systems support but some handle unreliably — Android in particular, along with networks that filter multicast traffic. If the address doesn't resolve, the unit is usually fine and only the name lookup is failing.

Work through these in order:

  1. Check you're on the same network. Your browser device and the Element must be on the same network and subnet. Guest networks, VPNs, and routers with client isolation or "AP isolation" enabled will all block the connection even though both devices have working internet.

  2. Try a different browser or device. A laptop will often resolve sgt.local when a phone won't.

  3. Reach the unit by IP instead. Open your router's admin page and look through its list of connected clients for the Element, then browse to that address directly — for example http://192.168.1.42.

    Your router won't list the unit as sgt — each Element has its own hostname, in the form sgt- followed by six characters, printed on the device itself. Match it against the label to be sure you have the right address.

Note the address down before you need it

The Element shows its own IP address in Settings. It's worth writing down next time you're in the dashboard — if sgt.local stops resolving later, browsing straight to that address gets you back in without touching your router.

Still stuck ​

See Troubleshooting for connection drops, pairing problems, and the status indicator reference.