This article walks you through connecting your iOS/Android devices (phones, tablets) to your Blue Iris server. It walks through all the dependencies and potential pitfalls when trying to setup your device.
If you prefer to watch the webinar associated with this article, checkout the Mobile Devices and Apps webinar.
If you are on an Android device, the Android gotchas article also has information the may help you self-correct the issue.
The Mobile Gotchas article is a list of past learnings from tickets. Good to review before creating a ticket.
There is no way for the mobile app to communicate with the Blue Iris server unless you setup your network to do so.
The Networking - Remote Access article will walk you through setting up the network correctly.
Checkpoint: Windows is setup correctly. The network is setup correctly.
This section is about setting up the mobile app to connect to the BI server.
At this point, we believe the network is setup correctly.
This section is about the Add a new server button / dialog so the mobile app can connect to the BI server.
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 Android 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)
The Server Manual Setup
FYI, you can choose to bypass the Server Wizard and go directly to setup page. Keep in mind the setup page only connects the mobile app to the BI server. You may still need to go through the iOS app settings to provide the right privileges. For example, you may need to allow the application to use your location if and when you activate geo-fencing.
The Lookup key is great for having BI populate your LAN / WAN address for you.
It helps prevent fat fingering the wrong values.
It also helps when you have an ISP provider that changes your WAN address a lot.
The Lookup key can be your best friend. However, for it to work, you have to enable the functionality on the BI server. On by default.
Register IP address to assist with client app connections. Global settings -> About tab.
Update to the latest version or the latest stable version of the BI server software.
Features/functionality on the mobile app are not guaranteed to run with older versions of the server.
Try connecting to the server from the LAN.
If successful, great! You have confirmed your mobile device has access to your BI server (license key, username, password, LAN address are all entered correctly) and you have confirmed at least some of the network requirements have been met like the BI web server is running and accessible from the LAN.
If you are facing issues connecting via the LAN check your User and Device permissions.
Global settings -> Mobile devices tab
If the mobile app connects successfully to your server, your device will be listed in the Global settings -> Mobile Devices tab.
If your device is NOT listed, then the mobile app still cannot register with the BI server.
Check the user permissions of the user trying to access the mobile app.
Now you can test whether the network is setup correctly.
- Logout of mobile app. Disconnect mobile phone from LAN/Wifi, i.e. use your cellular network.
- Try re-connecting app to server. If successful, confirmed remote access.
- If a problem, confirm WAN address is correct (not LAN).
If WAN address is correct, something is still wrong with the network setup.
Need to again review Networking article.
The App Settings section is about all the app settings.
Home tab -> Gear icon.
These settings need to be set correctly so the app meets your needs.
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.
In addition to App settings, you also have access to camera settings.
- Schedule : Camera settings -> Schedule -> Override global schedule for this camera
- PTZ preset cycle : Auto-cycle patrol
- PTZ event schedule : Camera settings -> Schedule -> Event schedule
- DIO output 1 : Turn first output to on/off
See Mobile Gotchas article before submitting a ticket.
Mobile app - Debug logs
Support sometimes needs to know what versions of the software are running (server & app), the make/model of the phone and the debug logs.
Follow steps below when providing the logs.
- Go through steps to reproduce the issue.
- After the issue occurs, send the debug log to YOURSELF. ? -> Debug log. The debug log will provide error details, if any.
After receiving the email, copy/paste the body of the email into a txt file.
Create/Reply to the support ticket by attaching the txt file. The logs can be quite large. A file attachment is preferred because of the length of debug log.
- For iOS users only: Send a support info email from the mobile app as well. ?-> Send feedback to Support. Send the email to YOURSELF, not SUPPORT. This will clarify the software version you are currently running. The Android app already provides the support info with the debug log. iOS will do so shortly. In the interim, send the feedback email to YOURSELF, not support. Once you receive the email, copy / paste body as a reply to the support email so all the information remains together. This information is much smaller then the debug logs so pasting to body of support email is fine.
- In iOS, creating a video is simple now. https://support.apple.com/en-us/HT207935
- Just as simple on an Android. Invoke Screen record.