Hi Geotab Community, I have some questions regarding the event configuration for the GO Focus Plus/Pro cameras, specifically concerning the "Near Collision" event.While reviewing the "Geotab Video - GO Focus Plus/Pro Triggers &amp; Thresholds" document, I noticed this event triggers based on negative G-Force (deceleration) levels:Low: -0.65GMedium: -0.45GHigh: -0.30G I recently experienced two instances on the road where another vehicle dangerously cut in front of me, resulting in a near miss. In both cases, I had to swerve to avoid them instead of braking hard. The camera did not detect these incidents automatically. Fortunately, I was able to press the manual record button in time, and the video was saved successfully.I have a few questions for the experts here: How should these G-Force levels be interpreted in practice? I understand it relates to braking force, but does the camera rely solely on the accelerometer (specifically harsh braking/negative Gs), or does it also use machine vision/ADAS to detect the actual proximity of the vehicle that cut in?Why didn't the camera detect it automatically? If a vehicle cuts in but the driver swerves or doesn't brake hard enough to hit that specific negative G-Force threshold, does the "Near Collision" event simply fail to trigger? Does the system account for lateral G-force from swerving in these near-miss scenarios?What sensitivity or configuration do you recommend? My goal is to automatically capture these types of scenarios (vehicles cutting off or crossing dangerously) so we don't have to rely on the driver pressing the manual button during a stressful moment. Any advice, documentation, or shared experiences would be greatly appreciated. Thanks in advance!

Questions about "Near Collision" G-Force parameters and automatic detection (GO Focus Plus/Pro)

Hey Geotabbers! I've been testing the GO Focus Plus camera over the past few weeks, and I've recently run into a slight issue. The physical button meant for manual recording only seems to work maybe 1 or 2 times per trip and sometimes not at all. Previously, it was working normally without any issues. Has anyone else encountered a similar problem? Could this be related to the device's storage/memory or a specific configuration setting? Thanks in advance for your help!

GO Focus Plus - Physical recording button working inconsistently

Hi community! I've been testing some custom rules with the GO FOCUS PLUS camera and I've noticed an intermittent issue. Sometimes the event is captured correctly, but other times (about 50/50), when I try to view the video evidence, it displays the following message: "No sensor items selected for display." Does anybody know why this happens only on certain events? Also, how can I select a sensor item for display to resolve this? Thanks in advance!  

GO FOCUS PLUS: "No sensor items selected for display" error on video events

Hey community! During a test run of the GO FOCUS PLUS, an "unknown driver" drove the vehicle while I (a registered driver in the database) was in the passenger seat. I enabled two rules for this test:A rule to detect when a registered driver (myself) is identified.A rule to detect when an unregistered driver is identified. After a trip of 3.5 km (about 11 minutes), I am the one who appears as the driver in the Trip History. However, in the Video -&gt; Events section, those events are not associated with my profile at all.To make things more confusing, during previous tests where I was the actual driver, the system flagged me as an "unknown driver," but under Video -&gt; Events, it did associate the events to my profile correctly. Has anyone encountered a similar discrepancy between Trip History and Video Events? Could it be that during the first test, the camera detected me in the passenger seat and mistakenly chose to associate the entire trip with me, even though I wasn't driving?Thanks! Thanks!

GO FOCUS PLUS associating trip to passenger instead of the actual driver

Hey Community! ​  I've been using a Go Focus Plus camera and I've noticed that sometimes, mostly for events during short trips (&gt;50 meters and about 60 seconds), I can't review the video evidence on myGeotab. ​  The events have been stuck as "Upload Pending" for over 24 hours. During that time, I've been using the vehicle and even tried leaving it turned on for about 20 minutes to let the videos finish uploading, yet none of those events became available afterward. ​ Has anyone encountered a similar issue? If so, how did you manage to get the event videos? Thanks! 

GO FOCUS PLUS Video events not available, shown as "Video Upload Pending"

Hi fellow Geotabbers! Currently, when I try to open certain event videos on the Events page in MyGeotab, they appear as "Video Unavailable." &gt; I've noticed that for these specific events, although a thumbnail image is visible, the usual "GIF" preview does not play when I hover over it. This is different from the events that work correctly, where the preview plays and the video opens normally. The trip was less than 48 hours ago and the camera detected some Events. Has anyone encountered a similar issue? If so, how did you solve this to retrieve the event video? Image of "Video Unavailable" when clicked at Events page: Thanks in advance!​

Issues with "Video Unavailable" on the Events Page

page-user page-user-ivan-allegre-9898 template-account-profile page-status-200 theme-harmony user-guest

Company

Title

Hi <a href="/user/eishifun" data-id="1044" data-value="EishiFUN" data-denotation-char="@" class="text-decoration-none mention">@EishiFUN</a>​  and <a href="/user/genevieve-bouchard-1051" data-id="1051" data-value="Genevieve-1051" data-denotation-char="@" class="text-decoration-none mention">@Genevieve-1051</a>​ , Thanks for the update! No worries at all, I know how tricky troubleshooting these types of issues can get. I really appreciate you keeping me in the loop. Take your time, and I'll keep an eye out for <a href="/user/jaime-lox-1754" data-id="1754" data-value="jlox-1754" data-denotation-char="@" class="text-decoration-none mention">@jlox-1754</a>​  insights whenever he has a chance to review the case. Best,

Hello <a href="/user/eishifun" data-id="1044" data-value="EishiFUN" data-denotation-char="@" class="text-decoration-none mention">@EishiFUN</a>​  and <a href="/user/andrew-dominguez-10564" data-id="10564" data-value="ADomi-10564" data-denotation-char="@" class="text-decoration-none mention">@ADomi-10564</a>​ , thanks for bringing me into this great discussion! To address your first question: yes, alert fatigue is a very common issue. In my experience working with clients ranging from small fleets to large corporate enterprises, a constant barrage of static alerts frequently leads to drivers getting frustrated and viewing the camera as an enemy rather than a helpful tool, which reduces the effectiveness of the in-cab coaching system. Your proposed dynamic model is spot-on. I'd love to add another critical variable to this dynamic approach: adjusting alert sensitivity based on real-time vehicle telemetry, specifically vehicle speed. I recently carried out tests over 2 weeks with the GO Focus Plus. During my operational analysis, I identified a risk regarding the time thresholds the camera requires to trigger a cell phone use alert.Here is what I found: <ul><li>Tests showed that if a driver uses their phone "quickly" (Changing a song, viewing a message, actions that take &gt;1s), the system does not detect it.</li><li>I mapped out the meters a unit travels "blind" based on the time it takes the AI to validate the event, evaluating Low (7s), Medium (5s), and High (1s) sensitivity settings.</li><li>For example, traveling at 90 km/h with a 5-second validation time (Medium Sensitivity) results in advancing 125 meters without full attention to the road.</li><li>Therefore, I believe this sensitivity rule would benefit greatly by being dynamic and becoming stricter as the unit's speed increases.</li></ul> Integrating your idea of rolling driver performance trends with real-time dynamic thresholds (like shrinking the cell phone validation window as vehicle speed increases) would make these systems much more efficient and less frustrating in daily operations. Looking forward to seeing how this concept evolves. Happy to share more about my testing if anyone is interested!

Dynamic performance-based adaptive monitoring model for dash camera systems using early-trip and rolling performance scoring

Hi Eishi, Thank you so much for the detailed response and the troubleshooting steps! I think Point 1 could potentially be what is happening here. On the other hand, I am fairly confident we can rule out Point 2, as I have checked the engine data and I haven't encountered any of those camera fault codes (605/606/607/608) on the device. I would like to try your third suggestion first and make sure the firmware is up to date. I checked MyGeotab and saw a version listed as 2025.38.76-release. I also checked with my team, and they mentioned we don't have a way to manually push or force a firmware update to the camera from our end. Could you give me some pointers on how we can trigger or request this firmware update to get the camera to v59? Thanks again for your great help!

Hi Geotab Community, I have some questions regarding the event configuration for the GO Focus Plus/Pro cameras, specifically concerning the "Near Collision" event.While reviewing the "Geotab Video - GO Focus Plus/Pro Triggers &amp; Thresholds" document, I noticed this event triggers based on negative G-Force (deceleration) levels:<ul><li>Low: -0.65G</li><li>Medium: -0.45G</li><li>High: -0.30G</li></ul> I recently experienced two instances on the road where another vehicle dangerously cut in front of me, resulting in a near miss. In both cases, I had to swerve to avoid them instead of braking hard. The camera did not detect these incidents automatically. Fortunately, I was able to press the manual record button in time, and the video was saved successfully.I have a few questions for the experts here: <ol><li>How should these G-Force levels be interpreted in practice? I understand it relates to braking force, but does the camera rely solely on the accelerometer (specifically harsh braking/negative Gs), or does it also use machine vision/ADAS to detect the actual proximity of the vehicle that cut in?</li><li>Why didn't the camera detect it automatically? If a vehicle cuts in but the driver swerves or doesn't brake hard enough to hit that specific negative G-Force threshold, does the "Near Collision" event simply fail to trigger? Does the system account for lateral G-force from swerving in these near-miss scenarios?</li><li>What sensitivity or configuration do you recommend? My goal is to automatically capture these types of scenarios (vehicles cutting off or crossing dangerously) so we don't have to rely on the driver pressing the manual button during a stressful moment.</li></ol> Any advice, documentation, or shared experiences would be greatly appreciated. Thanks in advance!

Hey Geotabbers! I've been testing the GO Focus Plus camera over the past few weeks, and I've recently run into a slight issue. The physical button meant for manual recording only seems to work maybe 1 or 2 times per trip and sometimes not at all. Previously, it was working normally without any issues. Has anyone else encountered a similar problem? Could this be related to the device's storage/memory or a specific configuration setting? Thanks in advance for your help!

Hey Eishi,​Haha totally! We're officially GO Focus bros at this point. Thanks for breaking this down so well, it actually makes a lot of sense. I didn't realize the telemetry data and the video clip lived on separate layers, but that explains the 50/50 split. I'm going to check the Media Upload Settings and mess around with that gear icon in the viewer to see if it fixes it. If it keeps acting up, I'll definitely open a ticket—looks like we might have found another little bug! I'll let you know how it goes. Have a great weekend! Best, Ivan

Hey Eishi, Always great to hear from you! No worries at all about sending me to support, I totally get it. It looks like a logic gap that the product team should check out. I'll open a ticket and make sure to reference you and this post so they have all the context. Thanks for the help, as always. Have a good one too! Best, Ivan

Hi community! I've been testing some custom rules with the GO FOCUS PLUS camera and I've noticed an intermittent issue. Sometimes the event is captured correctly, but other times (about 50/50), when I try to view the video evidence, it displays the following message: "No sensor items selected for display." <img src="/forum/plugins/gcs-uploads/files/069Pd000015BtQwIAK.png" alt="What shows when you click the Event in order to see the video evidence" /><img src="/forum/plugins/gcs-uploads/files/069Pd000015D4KDIA0.png" alt="How the Event is displayed in the Events tab" />Does anybody know why this happens only on certain events? Also, how can I select a sensor item for display to resolve this? Thanks in advance!

No worries at all! Thank you for the update, Eishi. I'll be sure to open the support ticket and reference that ID. Thanks again for your help!

Viimeaikaiset toiminnot

Questions about "Near Collision" G-Force parameters and automatic detection (GO Focus Plus/Pro)

GO Focus Plus - Physical recording button working inconsistently

GO FOCUS PLUS: "No sensor items selected for display" error on video events