[Utility] Powershell script to inventory and troubleshoot Blue Iris cloned cameras using new JSON 'camlist' values (6.0.7.4)

[jaydeel]

I've created a PowerShell utility to inventory and troubleshoot Blue Iris cloned cameras.

The script requires Blue Iris 6.0.7.4 or newer because it relies on the new JSON camlist values:
isClone
isCloneMaster

These values were added by Ken in response to my attempts to determine exactly how Blue Iris identifies cloned cameras (post).

Features:

• Groups cameras by shared IP address.
• Displays Blue Iris-reported Clone Master (user-configured) and Clone (BI-determined) status.
• Shows main and sub stream paths from the JSON camconfig command.
• Shows Camera settings > Video tab > Image Format settings.
• Shows Camera settings > Video tab > Max. rate settings.
• Highlights possible clone-related configuration anomalies.
• Exports results to CSV or JSON.
• Includes an optional registry comparison mode for troubleshooting.
• Does not make any changes to Blue Iris or the registry.

Example usage:
.\BI_clone_tool.ps1
.\BI_clone_tool.ps1 -Help
.\BI_clone_tool.ps1 -SuspectsOnly
.\BI_clone_tool.ps1 -All
.\BI_clone_tool.ps1 -Cam GT
.\BI_clone_tool.ps1 -ExportCsv
.\BI_clone_tool.ps1 -ExportJson
.\BI_clone_tool.ps1 -DevRegCompare GT,GT_

Example Screenshots:

In this example, Blue Iris recognizes the attempted clone, which has matching interrogated properties - except that it is hidden.

In this example, Blue Iris is recognizing both attempted clones despite the ImgFormat and MaxRate differences.

In this example, Blue Iris is not recognizing one attempted clone because it is NOT enabled.

Interesting observations:

• Cameras sharing the same IP address are not necessarily classified by Blue Iris as clones.
• Cameras may still be classified as clones even when some visible camera settings differ.
• The script can identify orphaned Clone Masters, multiple Clone Masters, and other unusual clone configurations.

Here's an example of an unusual attempted clone configuration that this tool helped uncover.

I had a camera that Blue Iris would not recognize as a clone, despite the fact that it shared the same IP address as the intended Clone Master. The script also showed that the main and sub stream paths, Image Format, and Max. rate settings all appeared to match.​

​

Using the -DevRegCompare option, I eventually realized that I had originally created the clone from a different physical camera that had occupied the same location years earlier and was later replaced. I had hidden the clone and simply overlooked it during the camera replacement (out of sight, out of mind).​

​

Although the current camera and its intended clone shared the same IP address and appeared identical in all obvious clone-adjacent settings, Blue Iris still refused to classify the camera as a clone.​

​

This suggests that Blue Iris may track additional camera-specific information beyond the settings exposed in the UI, JSON API, or obvious registry values. Recreating the clone from the current camera resolved the issue.​

The attached ZIP file contains 2 files:
BI_clone_tool.ps1
BI_clone_tool.user-settings.ps1

The included user-settings file must be edited before first use.

As always, review the script before running it.

If PowerShell blocks script execution, try:
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\BI_clone_tool.ps1
or
pwsh -NoProfile -ExecutionPolicy Bypass -File .\BI_clone_tool.ps1 -Help

Here's the help screen


The tool is discovery/reporting only and makes no Blue Iris or registry changes.

Feedback, bug reports, and enhancement suggestions are welcome.

 

[jaydeel]

It seems that the forum currently is not accepting my ZIP file attachment, I'll keep trying.

EDIT: FIXED - the file was finally accepted via a drag-n-drop operation vs the 'Attach files' button.

FIXED 6/17/2026 21:30... see post #1.

 

[David L]

Check your Help Screen, may need to reup the file...

UPDATE: It is fixed now, thanks....

Also, thanks for the share, I can see where this could be very handy...

 

[jaydeel]

Check your Help Screen, may need to reup the file...

View attachment 245022

Also, thanks for the share, I can see where this could be very handy...

Please try again. Of course, attempting to fix this broke the ZIP file upload again <sigh>.

 

[David L]

Please try again. Of course, attempting to fix this broke the ZIP file upload again <sigh>.

All seems to be fixed, I got the Zip file earlier...and now the help file.

I only have one Cloned CAM presently, use to have more at our other house. I am trying to keep up since I have not yet jumped to BI6 but have a newer PC planned for it when I do.

The Cloned CAM I still have is for AI, Deliveries (UPS, USPS, FED-EX, Amazon) Cloned CAMs are great...one of the many features BI shines at...

 

[jaydeel]

Script upload finally successful. See post #1.

The script has been updated to V1.1.
Changelog:

• Added 2 new output column values: 'ONVIF' (regkey pullpoint) and 'UUID2' (first 5 chars of regkey uuid)
• Added new user_setting $display_columns for customization of output table columns

 

[David L]

Here is a cap of the post #1: