If you have to get local/remote access for their recorders without going through the FSEYE servers, I’d suggest creating two direct IP address devices on your app. One of these will be useful when you’re on the same network (i.e. via WiFi) as the CCTV system, and one will be for remote access (down the street, in the emergency bunker in a secret location, etc.).
To do that, these are the steps:
- Log into the FSEYE app on your device
- On the “Device Manager” screen, tap the “+” button or “Add device”
- On the “Add device” screen, tap the IP/Domain tab
- Use a name like “CCTV local”, and use the local IP address for your DVR/NVR (i.e. 192.168.1.188, 10.0.0.101, etc.)
- This is normally found in the NVR’s Settings>Network menu, as the “Device IP” or just “IP address”. Don’t use the “Gateway address”!
- Leave the port as 5800, and enter your username and password
- It may ask you on the next screen how many cameras/channels you have (1, 4, 8, etc.)
- And that’s it.
For the “CCTV remote” device, the steps are mostly the same. However, instead of the local IP address, you’ll need the external/WAN IP address for your modem/router. Easiest way to find it is to be on the same WiFi network, and point your browser at https://www.whatismyip.com/. Your public IPv4 address is the IP address you’ll use at step 4 above.
Keep in mind that these WAN addresses can and will change from time to time, unless the customer has paid for a static IP address from their ISP. If the WAN address changes, visit https://www.whatismyip.com/ again, and change the IP address in the app. Please note – most mobile broadband modems/routers change their WAN addresses more often than I change socks, so this isn’t a great option for those customers.
If they’re more tech-savvy, they could create a dynamic DNS service (through FreeDNS, DynDNS, No-IP, etc., etc.) and use that custom address instead of the IP address in Step 4 above.