January Updates

New Features

  • The new Dropped Equipment Alert notifies managers when equipment is left behind at a job site, helping reduce lost or misplaced equipment. 
  • We’re improving data freshness and consistency across connected vehicle integrations by enabling 30 second data refresh intervals for supported OEMs. This enhancement delivers faster visibility into vehicle activity while maintaining reliability across platforms. 

Improvements

  • Firmware version 20250926_1531-1.4 has been released for Next Gen SafetyCam Plus and Pro. This update improves overall system stability and reliability, helping ensure a smoother and more dependable camera experience without impacting existing features or behavior. 
  • We’ve implemented an important access control update to ensure the Azuga Fleet Web Portal is used only by its intended audience. This enhancement strengthens role based access controls, improves platform security, and ensures a clear separation between fleet management and driver workflows. 

New Features

New Alert Type: Dropped Equipment 

A new alert type called Dropped Equipment is now available in Azuga Fleet. This alert notifies managers when equipment appears to be left behind at a job site. The alert is sent when an equipment beacon is not detected by Azuga for more than a user-defined, configurable amount of time. 

Navigation: 

  • Go to Admin → Alerts → Add Alert → Dropped Equipment Alert 

How This Works: 

  • Equipment status changes from WITH to DROPPED when it is unloaded from a truck or trailer. 
  • During normal operations, equipment may remain DROPPED temporarily while work is in progress. 
  • To avoid unnecessary alerts, the system waits for a configurable time threshold before sending a notification. 

An alert is triggered only when: 

  • Equipment status = DROPPED 
  • The equipment has remained DROPPED for longer than the configured number of minutes
  • The equipment has not returned to WITH status during that time. 

Example: 

If a user configures the alert for 30 minutes

  • Equipment is unloaded at 3:00 PM (status becomes DROPPED) 
  • Equipment remains DROPPED past 3:30 PM 
  • The system sends a Dropped Equipment alert shortly after 3:30 PM. 

Alert Configuration: 

When creating a Dropped Equipment alert, users must: 

  • Select Dropped Equipment from the Alert Type dropdown. 
  • Provide a unique alert name
  • Set the time threshold in minutes using: 

    “Alert when Equipment is Dropped for more than ___ minutes” 

This time threshold determines how long equipment can remain DROPPED before an alert is sent. 

Notifications and Recipients: 

Dropped Equipment alerts can be delivered via EmailWeb, and Mobile

  • Email alerts are sent immediately when triggered, with one alert per event (no summary alert). 
  • Alerts can be sent to individual usersdriversadminsor groups, following the same permission rules as other Fleet alerts. 

Sample Alert Message: 

  • For Web and Mobile: 

DROPPED EQUIPMENT ALERT - [date/time] 

[Equipment1 name] DROPPED at [street address] last detected by [asset name] at [date/time] [Equipment2 name] DROPPED at [street address] last detected by [asset name] at [date/time] [Equipment3 name] DROPPED at [street address] last detected by [asset name] at [date/time]  

  • For email notifications, the same information may be displayed in a tabular format for improved readability. 

 

Important Notes: 

  • Alerts are typically sent within a few minutes after the configured time threshold is exceeded. 
  • Updates to the time threshold apply to future alerts only. 
  • If equipment is picked up before the threshold is reached, no alert is sent. 

Benefits: 

  • Helps prevent equipment from being accidentally left behind at job sites 
  • Reduces alert noise by filtering out temporary equipment drops 
  • Allows teams to respond quickly to real issues 
  • Provides clear context on what was left, where, and when 

 

30 Second Data Refresh for Connected Fleets 

Vehicle data refresh frequency can vary based on OEM platform capabilities. As part of our ongoing platform enhancements, we’ve aligned supported OEM integrations to a 30 second refresh interval wherever possible, ensuring more timely and actionable fleet insights. 


OEM Frequency Matrix: 

OEM 

Data Refresh Interval 

Ford 

30 seconds 

Stellantis 

30 seconds 

GM 

30 seconds 

Toyota 

30 seconds 

 

What’s New: 

  • 30 Second Data Refresh Enabled for Ford, Stellantis, and GM fleets 
  • Improved consistency across supported OEM integrations 

Key Benefits: 

  • Faster Data Visibility – Near real time access to vehicle events and status 
  • Improved Operational Awareness – Quicker insights for dispatch, safety, and performance monitoring 
  • Consistent Experience – Standardized refresh behavior across supported OEMs 
  • Scalable Performance – Optimized to support growing fleets and higher data volumes 

Customer Impact: 

  • No action is required from customers 
  • This enhancement is automatically applied to eligible fleets 
  • Customers may notice faster updates in vehicle status, events, and reporting 

Availability: 

  • Available to all supported connected vehicle fleets 
  • Applied automatically as part of ongoing platform improvements 

Improvements

Next Gen SafetyCam (Plus & Pro) Firmware Update

A minor firmware update has been released for Next Gen SafetyCam Plus and SafetyCam Pro cameras. This update focuses on improving overall system reliability and stability, without impacting existing camera features or behavior. 


Firmware Version Update: 

  • Previous version: 20250926_1531 
  • Current version: 20250926_1531-1.4 

What’s Improved: 

  • Enhanced system stability and operational reliability 
  • Improved support for faster issue resolution 

This update delivers a more stable and dependable camera experience. 

 Driver Access Restriction for Fleet Web Portal 

The Fleet Web Portal is designed exclusively for fleet managers and administrators. Drivers are intended to access Azuga through the Azuga Fleet Mobile App

With this update, access is now strictly enforced based on user roles to prevent unintended usage. 


Where to Find It: 

This update applies when users attempt to access the Fleet Web Portal (fleet.azuga.com) using Driver mobile credentials. 

What’s New: 

  1. Role Based Access Enforcement: 
  • Users with the Driver role can no longer log in to the Fleet Web Portal. 
  • Authentication now correctly validates user roles before granting access. 
  1. Dedicated Driver Landing Page: 
  • Drivers attempting to access the Fleet Web Portal are redirected to a dedicated landing page. 
  • The page clearly informs drivers that web access is not supported and guides them to use the mobile app. 

 

  1. Clear Platform Separation: 
  • Fleet management features remain available only on the web portal. 
  • Driver workflows are fully supported through the Azuga Fleet Mobile App. 

 

Key Benefits: 

  • Stronger Access Control – Only authorized users can access fleet level dashboards. 
  • Reduced Role Confusion – Drivers and fleet managers use the right tools for their needs. 
  • Improved Platform Integrity – Prevents misuse of features not designed for driver operations. 
  • Scalable Security Model – Supports future enhancements and growth. 

 

Availability: 

  • Applies To: All customers on the Azuga Fleet platform 
  • Impact: Drivers will no longer be able to log in to the Fleet Web Portal and must use the Azuga Fleet Mobile App. 

PDF Copy: [Customer] Fleet Web Release Notes - Jan_v26.1

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.