IRIS+™ 2025.2

irisity is always looking for opportunities to provide the best features and improvements for your needs if you want to use the latest updates to the iris+ cloud, we highly recommend you read through our release content updates will be automatically applied to your system according to our policies this release will be accessible to all customers using the cloud hosted system on 08 april during our service maintenance window what's new? new event fields available in the insights module this update will include additional event statuses in the insights module these event statuses can be applied to widgets in an insights dashboard to show trends on how many events have been handled across time this new field can be found in the events data source here is an example of how we can compare the number of new events with true events generated across different cameras based on camera id to learn how to set this up in your insights dashboard, read more at getting started with iris+ insights w hat's improved? additional improvements to smoke & fire detection this update to iris+ provides customers with an improved detector for smoke & fire activities this improved version reduces false positives that were generated from smoke and flame changes in different flames this will ensure that there is only accurate event(s) generated for each smoke/fire incident that occurs on site improved system capacity management we're also updating the edge device warnings to notify the user when the cpu consumption is at 80% instead of 86% this helps alert customers earlier when edge devices are about to hit max resource capacity, which can lead to dropped events updated irisity eula for portal usage new users creating their accounts in iris+ for the first time will now need to accept the terms and agreements from the latest irisity end user license agreement (eula) this agreement contains the most recent information about your usage with iris+ what's fixed? bug found in camera setting where the portal does not allow sensor sync when the user datagram protocol (udp) mode is not configured issue found where the stopped vehicle rule defaults to cpu usage when a gpu is available webpage performance issue found when attempting to handle alarm event data