This article walks you through connecting your iOS device (iPhone, iPad) to your Blue Iris server. It walks through all the dependencies and potential pitfalls when trying to setup your device.
Windows and Blue Iris
There is no way for the BI server to communicate with your LAN devices unless Windows settings are not in conflict with your BI server. The Windows System Tuning article will walk you through all the checks.
There is no way for the mobile app to communicate with the Blue Iris server once you leave your LAN, i.e. home network, unless you setup your network to do so.
The Remote Access Wizard walks you through the steps to setup your network. The Remote Access webinar guides you through the process. https://www.youtube.com/c/BlueIrisSupport.
- Most users are using NGROK (ddns) these days since it's easier. The NGROK section in the Help file provides details.
- Tech saavy folks still use port forwarding. In the webinar, I walk through port forwarding via an AT&T Pace gateway device. Setting up your specific router/gateway is beyond BI support.
Coming soon: SSL connections with https (STunnel).
Checkpoint: Windows is setup correctly. The network is setup correctly.
iOS App - Phone settings
First try connecting through the LAN, i.e. Wi-Fi connection. Then turn off the Wi-Fi connection and try connecting via the cellular network, i.e. WAN address.
Easiest way to setup your phone settings to connect and work well with the BI App is to use the Wizard within the Add New Server function.
FYI, the BI Mobile App can connect to multiple servers.
The iOS Server Setup Wizard (helps configure iOS device settings)
The final step is to Scan the QR Code. Where is the QR Code?
The QR Code is located in one of the last pages in the Remote Access Wizard. (see below)
BI Mobile App Settings (~ Global Settings)
Most of the setting descriptions are intuitive or can be understood by simply turning them on/off. Below I highlight the ones that raise tickets and cause confusion.
What are the blue badges on my alerts?
Mobile App Gotchas
Case 1: Playback is not smooth. Live view is choppy.
- Test 1: Need to make sure live stream and playback are first smooth on the BI Server. Garbage in = Garbage out.
- Test 2: If you open a browser and go to the BI web interface (UI3), are the live view and playback a good experience. If so, then you know the problem is not with the network.
I highlighted the values I changed from the default settings:
- First, I turned on Constant Bit Rate (CBR). This settings caps the amount of data going to the player at 1024 kbps.
- Next, I reduced the resolution to 856 x 480. You are streaming to a mobile device, so reducing the resolution will probably have no affect on your viewing experience. I played with "Retain aspect ratio within frame". On iOS devices, the setting seemed fine. But I noticed instability and crashes on some Android devices. It does not really change/help the user experience, so my conclusion was to just leave it off unless required for another reason.
Once I made the stream adjustments, I went to the mobile app settings and chose the appropriate settings for my LAN and WAN connections.
Case 2: Cannot playback alerts or clips.
Issue: If you are recording Direct to Disk (D2D) and the key frame interval is sub-par, e.g. <1, then it is possible the file is open for recording, but no key frames have actually been recorded yet so BI cannot playback.
- Check the key frame interval in the Status -> Camera tab.
- If the key frame interval is <1, go to your camera settings (not in Blue Iris) and raise the key frame interval. The Camera Stream Optimization article has details.
Based on diagram, ISP provider originally assigend 188.8.131.52 as your WAN address. Based on diagram, the router assigned the BI Server 192.168.1.7 as the LAN address.
After the router restart:
- ISP could have assigned a new WAN address. 184.108.40.206 -> 220.127.116.11
Consequence: Mobile devices will no longer be able to connect to the BI server from the WAN.
Fix: Logout of BI Mobile App -> Edit -> Lookup key. You should observe the WAN address update.
- Router could have assigned BI a new IP address. 192.168.1.7 -> 192.168.1.15.
Consequence: The router's port forwarding is broken.
Fix: Update the router's port forwarding to the new IP address. Also change the router setting to provide a Static IP Address to the BI server so it never changes again to prevent future issues.