Features Verticals Cameras Conferences Pricing Contact Log In Get Started
Integration Guide

FLIR / Lorex Integration Guide

Connect FLIR and Lorex cameras to AgenticEye for AI-powered visual and thermal monitoring. This guide covers RTSP streaming, ONVIF configuration, and thermal camera feed integration for the FLIR FX, Lorex 4K series, and FLIR thermal imaging cameras.

RTSP ONVIF Thermal HTTP API

Prerequisites

Before You Begin

  • A FLIR or Lorex IP camera connected to your network via Ethernet (PoE recommended for reliability)
  • Camera firmware updated to the latest version — check the FLIR or Lorex support portal for your model
  • Admin credentials for the camera (Lorex default is typically admin with a password set during setup)
  • Camera IP address — use the Lorex IP Utility or your router's DHCP lease table
  • Network access between AgenticEye and the camera on ports 554 (RTSP) and 80 (HTTP/ONVIF)
  • For thermal cameras: verify that the camera outputs a standard video stream (RTSP) in addition to radiometric data
  • AgenticEye platform account with an active subscription

Supported Models

This guide covers FLIR and Lorex cameras across multiple product lines. FLIR acquired Lorex, and many models share the same underlying firmware.

  • FLIR FX — Indoor/outdoor WiFi camera with cloud connectivity
  • Lorex LNB9292B — 4K Ultra HD bullet camera for outdoor perimeter security
  • Lorex LNE9292B — 4K Ultra HD dome for indoor/outdoor mounting
  • Lorex E893AB — 4K smart deterrence camera with color night vision
  • FLIR A310 — Fixed thermal camera for industrial temperature monitoring
  • FLIR A700 — Advanced thermal with radiometric streaming for process control
  • FLIR Duo Pro R — Dual-sensor (visible + thermal) for drone and fixed installations

Firmware Version Requirements

RTSP and ONVIF support varies significantly by firmware version. The following minimum versions are required:

  • Lorex 4K series: Firmware v2.680 or later for stable RTSP and ONVIF support
  • FLIR FX: Firmware v1.032.0007 or later for RTSP access (earlier versions only support cloud streaming)
  • FLIR A-series thermal: Firmware v10.x or later for ONVIF Profile S compliance
  • Always check the release notes for your specific model — some firmware updates add or remove RTSP/ONVIF support

Step-by-Step Setup

1
Access the Camera Web Interface

Both FLIR and Lorex cameras provide a web-based configuration interface.

  1. Open a browser and navigate to http://[camera-ip]
  2. Log in with your admin credentials
  3. For Lorex cameras connected to an NVR, you may need to access the camera directly (not through the NVR) to configure RTSP settings. Find the camera's individual IP under the NVR's camera management page
  4. For FLIR thermal cameras, the web interface may be at a non-standard port — check the camera's documentation or try http://[ip]:8080

Note: Some older Lorex cameras require Internet Explorer with an ActiveX plugin for full web interface access. For configuration only, Chrome or Firefox usually work. If you cannot access the web UI, use the Lorex Cloud app to find and update the camera's network settings.

2
Enable RTSP Streaming

RTSP must be explicitly enabled on many FLIR/Lorex models, as it is sometimes disabled by default for security.

  1. Navigate to Setup → Network → RTSP (or Network → Connection → RTSP on some models)
  2. Set RTSP to Enable
  3. Confirm the port is 554 (default)
  4. Set Authentication to Digest
  5. Navigate to Setup → Camera → Video → Video Stream and configure:
    • Main Stream: H.264, 3840x2160 (4K) or native resolution, 15 FPS, CBR 4096-8192 Kbps
    • Sub Stream: H.264, 1280x720, 10 FPS, CBR 1024-2048 Kbps
# FLIR/Lorex RTSP URL format:
rtsp://[username]:[password]@[ip]:554/cam/realmonitor?channel=[ch]&subtype=0

# Main stream, channel 1:
rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=0

# Sub stream, channel 1:
rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=1

# NVR — channel 4, main stream:
rtsp://admin:[email protected]:554/cam/realmonitor?channel=4&subtype=0

# Verify with ffprobe:
ffprobe -rtsp_transport tcp \
  "rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=0"
3
Configure ONVIF

ONVIF provides standardized device discovery and control. Enable it for AgenticEye's auto-discovery and event subscription features.

  1. Navigate to Setup → Network → ONVIF (or Network → Platform Access → ONVIF)
  2. Set ONVIF to Enable
  3. The default ONVIF port is 80
  4. Add an ONVIF user account. On many FLIR/Lorex cameras, ONVIF users are managed separately from system users:
    • Username: agenticeye
    • Password: choose a strong password
    • Role: Operator or Admin
  5. Enable WS-Discovery for network auto-detection
# ONVIF device service URL:
http://192.168.1.100:80/onvif/device_service

# Test ONVIF:
from onvif import ONVIFCamera
cam = ONVIFCamera('192.168.1.100', 80, 'agenticeye', 'YourPassword')
info = cam.devicemgmt.GetDeviceInformation()
print(f"Model: {info.Model}, Firmware: {info.FirmwareVersion}")
4
Add Camera to AgenticEye

Connect your FLIR or Lorex camera to the AgenticEye platform.

  1. Log in to your AgenticEye dashboard at app.agenticeye.com
  2. Navigate to Cameras → Add Camera
  3. Select FLIR or Lorex from the manufacturer dropdown
  4. Enter the RTSP URL for your camera stream
  5. For thermal cameras, select Thermal Camera as the camera type to enable thermal-specific AI processing
  6. Name the camera with a descriptive location label
  7. Select the appropriate AI agent vertical (thermal cameras work with industrial, security, and wildlife verticals)
  8. Click Test Connection, then Save & Activate

RTSP URL Format

FLIR / Lorex RTSP URL Structure

rtsp://[username]:[password]@[ip]:554/cam/realmonitor?channel=[ch]&subtype=0

Parameters:

  • [username] — Camera user account (typically admin)
  • [password] — Account password (URL-encode special characters)
  • [ip] — Camera or NVR IP address
  • [ch] — Channel number: 1 for standalone cameras, 1-N for NVR channels
  • subtype=0 — Main stream (high quality); subtype=1 — Sub stream (lower bandwidth)

Alternative URL formats (model-dependent):

# Some FLIR models use this format:
rtsp://[user]:[pass]@[ip]:554/live/ch[N]
rtsp://[user]:[pass]@[ip]:554/live

# FLIR thermal cameras (A-series) may use:
rtsp://[user]:[pass]@[ip]:554/avc
rtsp://[user]:[pass]@[ip]:554/thermal
rtsp://[user]:[pass]@[ip]:554/visible

ONVIF Configuration

ONVIF Setup Details

  • ONVIF Port: 80 (default on most models)
  • Device Service URL: http://[ip]:80/onvif/device_service
  • FLIR/Lorex cameras typically require ONVIF users to be created separately from system users
  • ONVIF Profile S is supported on most models for streaming
  • FLIR thermal cameras with ONVIF support expose both the visual and thermal streams as separate ONVIF media profiles
  • For NVRs, each connected camera channel appears as a separate ONVIF profile

Thermal Camera Feed Integration

Thermal Imaging Specifics

FLIR thermal cameras produce specialized image data that AgenticEye can process for temperature-based AI analysis. Understanding the different stream types is critical for effective integration.

  • Visual Stream: Standard RGB video from the visible-light sensor. Processed identically to any IP camera
  • Thermal Stream: Pseudo-color or grayscale video representing temperature data. Used by AgenticEye for heat-based anomaly detection
  • Radiometric Data: Raw temperature values per pixel. Available on FLIR A-series and higher-end models via the FLIR CGI/API interface. AgenticEye can ingest this for precise temperature threshold alerting
  • MSX (Multi-Spectral Dynamic Imaging): Fused visible + thermal overlay. Provides the best visual context for human review of AI alerts

Connecting Thermal Streams

Dual-sensor FLIR cameras expose multiple RTSP streams — one for each sensor and optionally a fused view.

# FLIR A-series thermal cameras:

# Thermal stream (pseudo-color or grayscale):
rtsp://admin:[email protected]:554/thermal

# Visible-light stream:
rtsp://admin:[email protected]:554/visible

# MSX fused stream (thermal + visible edges):
rtsp://admin:[email protected]:554/avc

# Radiometric data via CGI (temperature values):
http://192.168.1.100/api/image/thermal/snapshot?format=radiometric
# Returns a 16-bit TIFF where pixel values = temperature in deciKelvin

# Temperature spot measurement via API:
http://192.168.1.100/api/measurement/spots
# Returns JSON with configured measurement spot temperatures

AgenticEye Thermal AI Features

When a camera is configured as a thermal camera type in AgenticEye, additional AI capabilities are enabled:

  • Temperature Threshold Alerts: Set high/low temperature boundaries. AgenticEye triggers alerts when temperature crosses the threshold in any defined zone
  • Heat Anomaly Detection: AI identifies unusual heat patterns that may indicate equipment failure, fire risk, or unauthorized presence
  • Perimeter Intrusion (thermal): Detect human/vehicle presence in total darkness using thermal signatures — far more reliable than visible-light cameras in zero-light conditions
  • Equipment Monitoring: Track temperature trends of machinery, electrical panels, and industrial processes over time with automated reporting
  • Dual-Stream Correlation: AgenticEye can simultaneously analyze both thermal and visible streams, correlating thermal detections with visual identification for richer alerts

Recommended Thermal Camera Settings

Optimize your thermal camera for AgenticEye's AI pipeline:

  • Palette: Use Iron or Rainbow palette for best AI detection contrast. Avoid grayscale for AI analysis
  • Temperature Range: Set the range to match your monitoring scenario (e.g., -20 to 120C for industrial, -40 to 550C for fire detection)
  • Frame Rate: 9 FPS is standard for thermal cameras and sufficient for AI analysis. Higher frame rates are available on some models but rarely needed
  • Resolution: Thermal sensors are typically 320x240 or 640x480. AgenticEye's thermal AI models are optimized for these resolutions
  • NUC (Non-Uniformity Correction): Enable automatic NUC to prevent image artifacts from sensor drift. Be aware that NUC causes a brief stream interruption (1-2 frames)

Troubleshooting

RTSP not available — firmware version too old

Many FLIR and Lorex cameras shipped with firmware that did not include RTSP support. This is the most common issue with these cameras.

  • Check your current firmware version in Setup → System → Information
  • Visit the Lorex support site (lorex.com/support) or FLIR support (flir.com/support) and download the latest firmware for your exact model
  • Lorex 4K cameras: Firmware v2.680+ is required for RTSP. Older versions only support proprietary Lorex Cloud streaming
  • FLIR FX: Firmware v1.032.0007+ adds local RTSP access. Earlier versions are cloud-only
  • After updating firmware, the camera will reboot. RTSP settings may need to be enabled manually after the update
  • If no firmware update is available for your model, contact FLIR/Lorex support to request RTSP/ONVIF support
Port 554 blocked or camera uses a different port

Some FLIR/Lorex models use non-standard RTSP ports, or port 554 may be in use by the NVR if the camera is connected through one.

  • Check the RTSP port in Setup → Network → RTSP or Network → Port
  • Common alternate ports: 7447, 8554, 10554
  • If connecting through a Lorex NVR, the NVR may remap camera RTSP ports. Access cameras directly by their individual IPs instead
  • Use nmap to discover open ports on the camera:
# Scan for RTSP ports:
nmap -p 554,7447,8554,10554 192.168.1.100

# Try each discovered port:
ffprobe "rtsp://admin:[email protected]:7447/cam/realmonitor?channel=1&subtype=0"
Authentication fails — Lorex-specific password issues

Lorex cameras have specific password format requirements that can cause authentication failures:

  • Some Lorex models truncate passwords longer than 16 characters — if your password is longer, try the first 16 characters only
  • Special characters in the password must be URL-encoded in the RTSP URL: @→%40, :→%3A, #→%23
  • If you set the password through the Lorex app, try also setting it through the web interface — the app sometimes applies different encoding
  • Create a dedicated user for RTSP access with a simple alphanumeric password to avoid encoding issues
  • Verify the user has Monitor or Live View permissions
Thermal stream shows incorrect colors or temperatures

Thermal stream appearance depends on camera configuration:

  • The thermal stream is a pseudo-color representation — the color palette is configurable on the camera. AgenticEye's thermal AI works best with Iron or Rainbow palettes
  • If temperatures appear incorrect, verify the camera's emissivity setting matches your target surface (0.95 for most objects, lower for metals)
  • Check the temperature range setting — if set too narrow, the image may appear washed out; if too wide, thermal differences may be hard to detect
  • NUC (Non-Uniformity Correction) artifacts can cause temporary banding — enable auto-NUC and allow 30 seconds after camera startup for calibration
  • For radiometric data integration, ensure the camera is configured to output 16-bit radiometric frames, not just visual pseudo-color
ONVIF discovery finds camera but cannot get stream

This typically indicates a mismatch between ONVIF profiles and actual stream configuration:

  • Verify that RTSP is enabled in addition to ONVIF — ONVIF relies on RTSP for the actual stream delivery
  • Check that the ONVIF user has sufficient permissions (Operator or Admin)
  • On dual-sensor thermal cameras, ONVIF may expose 4+ profiles (main/sub for each sensor). Test each profile token to find the one you need
  • Some FLIR models require a firmware update to fix ONVIF GetStreamUri returning incorrect URLs. Update to the latest firmware
  • If ONVIF returns a URL with localhost or 0.0.0.0 as the host, manually replace it with the camera's actual IP address
NVR channel streams are unstable or disconnecting

When pulling streams through a FLIR/Lorex NVR, the NVR must transcode and restream, which can cause instability under load:

  • Limit the number of simultaneous RTSP connections to the NVR. Most consumer NVRs support 4-8 concurrent streams before performance degrades
  • Use sub streams (subtype=1) for AgenticEye to reduce NVR transcoding load
  • If possible, connect directly to individual camera IPs instead of through the NVR — this bypasses the NVR bottleneck
  • Reduce the main stream bitrate on cameras to ease NVR network throughput requirements
  • Check the NVR's CPU and memory usage — high utilization causes stream drops. Close any other active viewing sessions

Need Help With Your Integration?

Our integration team specializes in FLIR and Lorex setups, including thermal camera configurations for industrial and security applications.

Contact Our Integration Team