6.0.9.0 I would tell you what is new but...

[Tinman]

I assume we have to find out ourselves.

 

[bp2008]

I really have to wonder what their release process is, considering how often it comes out without any change log or notes. It could be a simple matter of their cloudflare proxy not having caching configured properly for the changelog URL too. But the smart money is on it being human error during a manual release process, forgetting to update the release notes.

 

[bp2008]

He included UI3-332 at least. So ... you can have UI3's change log I guess.

Version 332​

• Added Check for Updates button to UI Settings > Server Control based on a proposed updatecheck API which is not currently implemented in Blue Iris. Includes automatic fallback to a much simpler update checking interface and a link to the API proposal and documentation.

Version 331​

• Password input fields should now all have a button to make the password visible.
• Fixed a bug where using the "Apply" button to change a profile name caused future attempts to change the name to fail until the profile editor was closed and reopened.

Login page version 35​

• The "user" and "pw" URL parameters are now read by login.htm if they exist and credentials are not already saved.
• Password input fields should now all have a button to make the password visible.

The ball is in their court for implementing the update check API that will allow UI3's new manual update check capability to function. If/when Ken implements that in Blue Iris, UI3 will begin giving you a clone of the Blue Iris News and Updates panel from the local console. It'll be particularly helpful for anyone who (like me) uses UI3 for remote access and finds it cumbersome to log in with remote desktop or equivalent.

 

[IAmATeaf]

I really have to wonder what their release process is, considering how often it comes out without any change log or notes. It could be a simple matter of their cloudflare proxy not having caching configured properly for the changelog URL too. But the smart money is on it being human error during a manual release process, forgetting to update the release notes.

Don't forget that quite frequently the update released on their website isn't what it claims to be!

 

[bp2008]

It has been two days and 6.0.9.0 is still not in the changelog. I guess this rules out any cloudflare caching issue. They just neglected to update the change log.

 

[CrazyAsYou]

The change log as a PDF is stupid IMO - I really don't understand why it's not a much more user-friendly text based web page or even better something similar to what's used on GitHub repos - with a simple release list/history, here is one example of what I'd prefer Releases · Wheemer/simple-thermostat

 

[bp2008]

I very much agree. HTML is generally more accessible, lighter-weight, and it is very easy to produce automatically assuming the source is markdown or something.

Look what happens when you copy and paste directly out of the PDF!

[6.0.1.20] – 2026-1-20Fixed• An issue introduced in 6.0.1.16 where pre-trigger image objects may not have beenmarked as static• On Settings/AI the server address will be automatically parsed to remove protocolspecifier and place the port number into the port box.• An issue where a camera selection for features of several action set actions (suchas email, include an image from another camera) will alter the behavior of &NAMEand other camera-specific macros.• An issue where the static/periodic scan was not giving enough weight to similarcategory objects such as car/truck, which the detection often confuses inlow-confidence scenarios.Added• Experimentation with a replacement ALPR OCR ONNX. If this file is found in theAI/models folder it will be used in place of the initially installed module:

https://github.com/ankandrew/fast-plate-ocr/releases/download/arg-plates/cct_s_v1_global.onnx

Or if I paste into a text editor first, it at least preserves line breaks better but does not keep bold text or other formatting. Also it has hard line breaks wherever text was wrapped in the PDF, but it is better than what you see above where words are just jammed together like protocolspecifier when the line breaks were all lost.

[6.0.1.20] – 2026-1-20
Fixed
• An issue introduced in 6.0.1.16 where pre-trigger image objects may not have been
marked as static
• On Settings/AI the server address will be automatically parsed to remove protocol
specifier and place the port number into the port box.
• An issue where a camera selection for features of several action set actions (such
as email, include an image from another camera) will alter the behavior of &NAME
and other camera-specific macros.
• An issue where the static/periodic scan was not giving enough weight to similar
category objects such as car/truck, which the detection often confuses in
low-confidence scenarios.
Added
• Experimentation with a replacement ALPR OCR ONNX. If this file is found in the
AI/models folder it will be used in place of the initially installed module:

https://github.com/ankandrew/fast-plate-ocr/releases/download/arg-plates/cc

t_s_v1_global.onnx

But compare that to copying release notes from a github page where the release notes are rendered as HTML. Most formatting, links, and list nesting is preserved.

Version 332​

• Added Check for Updates button to UI Settings > Server Control based on a proposed updatecheck API which is not currently implemented in Blue Iris. Includes automatic fallback to a much simpler update checking interface and a link to the API proposal and documentation.

Version 331​

• Password input fields should now all have a button to make the password visible.
• Fixed a bug where using the "Apply" button to change a profile name caused future attempts to change the name to fail until the profile editor was closed and reopened.

Login page version 35​

• The "user" and "pw" URL parameters are now read by login.htm if they exist and credentials are not already saved.
• Password input fields should now all have a button to make the password visible.

Version 326​

• Added some additional context menu functionality to help UI extension authors modify UI3's context menus.
  • For now, only video player context menus are supported via new custom events "BeforeRegisterCanvasContextMenuLive", "BeforeRegisterCanvasContextMenuRecord", "BeforeRegisterCanvasContextMenuTimeline".
  • Simplified context menu item enabled/disabled state changes (hopefully correctly) in order to better support menu items added by UI extensions.
  • Modified jquery.contextmenu library so the applyrule method no longer uses the name field on each rule; it was adding unnecessary complexity for me.
  • Example Local Overrides Sample: Local Overrides Sample: Add Context Menu Button "Pause Schedule".

Version 325​

• MP4 clips can now be opened in a new browser tab. Upon first use, the user is asked whether to "Open in UI3" or "Open in Browser Tab" and given the option to not ask again.
• Added "Toggle Flag" hotkey, unset by default.
• Added keybind for closing the topmost dialog, bound to the escape key.
• Hotkeys can now be used while dialogs are open if they have a property allowInDialogs: true.
• Fixed bug where dialogs could not be brought to the front of the display order by clicking their title bar (required clicking their body).

The release process has been revised to prevent specific development environment folders from being copied into releases, wasting space (affected UI3-323 and UI3-324).

 

[Techie007L]

@bp2008 Speaking of updating Blue Iris via UI3, unless you fixed this already, it has a bug where it shows the latest version available and provides an update button even if the Blue Iris subscription is expired. Hitting the update button causes it to update anyway (something that's grayed out in Blue Iris), putting Blue Iris in demo mode. Rolling back to the last supported version is not easy.

 

[bp2008]

@bp2008 Speaking of updating Blue Iris via UI3, unless you fixed this already, it has a bug where it shows the latest version available and provides an update button even if the Blue Iris subscription is expired. Hitting the update button causes it to update anyway (something that's grayed out in Blue Iris), putting Blue Iris in demo mode. Rolling back to the last supported version is not easy.

I've been aware of that issue for some time, with fixes proposed to Ken since about 14 months ago when the update notification was implemented originally. What it boils down to is that all UI3 is told is that version "6.0.9.0" or whatever is available. No notice of whether installing the update will cause BI to enter demo mode. I believe it did get resolved more or less in a more recent Blue Iris release a few months ago now but if you're on an older Blue Iris version then you won't have the fix. You can at least disable the update notice in UI3's settings if it is annoying.