<a data-id="1969" data-value="danielaramirez-1969" data-denotation-char="@" href="/user/danielaramirez-1969" class="text-decoration-none mention">@danielaramirez-1969</a> is correct they come in two separate files. In the future we plan to implement a way to choose if you want them seperated or not. I do not have a timeline on when this will happen though. Thanks for tagging me in <a data-id="1969" data-value="danielaramirez-1969" data-denotation-char="@" href="/user/danielaramirez-1969" class="text-decoration-none mention">@danielaramirez-1969</a> !!

Why do Go Focus video download with the audio separate?

Hello <a data-id="10763" data-value="User-10763" data-denotation-char="@" href="/user/user-10763" class="text-decoration-none mention">@User-10763</a> , Thank you for asking your question in our community. I am sorry to hear you have been running into this issue! I will be happy to help you troubleshoot this. The &quot;high volume of failed video upload&quot; message on the Cameras page is typically a connectivity issue. The GO Focus camera uses its own built-in SIM card for cellular connectivity and uploads footage directly to the cloud. When the vehicle is operating in areas with poor or no cellular signal, uploads will fail and this health status will appear. To answer your specific questions: Will re-calibration help? No — calibration on GO Focus cameras is for the ADAS sensors (accelerometer), not related to video upload connectivity. Re-calibrating won't resolve upload failures. Is it only because of cell coverage? Cellular signal is the most common cause, but it's also worth checking that the camera is powered on and healthy — check the camera's LED status and look for any engine faults in the database that might be affecting power to the device. Will the videos eventually upload? Yes. The camera stores footage locally on its SD card when connectivity is unavailable and will automatically upload it once it returns to an area with sufficient cellular signal. So the footage is not lost — it just needs connectivity to sync. If the camera continues to show failures even in areas with good signal, that would be worth opening a support ticket to investigate further, as it may indicate a deeper issue with the device. Feel free to reach out if you have any other questions — we are here to help. Have a great day! Eishi FUN

Go Focus- High Volume of Failed uploads

Hello <a data-id="1351" data-value="CristianHernndez-1351" data-denotation-char="@" href="/user/cristianhernndez-1351" class="text-decoration-none mention">@CristianHernndez-1351</a> , Thank you for asking your question in our community. Today the wake up is based on accelerometer movement which is 0.05G detected by the accelerometer. Once this threshold is met it will wake up and start recording. There is a sentry mode that is set to deploy at some point to wake up the camera when movement is detected such as a person walking up to the vehicle but this is not currently available. I know it is being worked on but that is about all I know I can share at this time. Let us know if you have any other questions. Always happy to help! Have a good one! Eishi FUN

parameter for the GoFocus to start streaming video

Thank you for the detailed feedback — and you are absolutely right that this is a gap. The camera section currently offers a basic client-side CSV export, which does not have the rich reporting features you're used to elsewhere in MyGeotab. We hear this consistently from customers and it's a fair call-out. The good news is that improvements to camera reporting are actively on our roadmap for this quarter. The intent is to bring the reporting experience for cameras in line with what you'd expect from the rest of the platform — including better integration with MyGeotab's reporting capabilities. I can't commit to a specific release date, but this is a current priority for the team. In the meantime, if you haven't already, the Device Online and Offline report (https:&#x2F;&#x2F;support.geotab.com&#x2F;product-updates&#x2F;improved-device-status-reporting-offline-device) does include cameras and may help with some of the device health visibility you're looking for while the full reporting improvements are in progress. We appreciate you sharing this — feedback like this helps us prioritize. Feel free to reach out if you have any other questions. Have a great day! Eishi FUN

GO FOCUS Health status template and automatic reports

Hi everyone, When downloading a requested video from the GO Focus Plus, it appears that the audio track is saved in an independent folder, completely separate from the video file. How can I merge both the video and audio files into a single playback file? Is there a recommended tool or a native method to do this automatically? Thank's in advance!

How to merge separate audio and video files from GO Focus Plus downloads?

Hello, We have run tests, and I can confirm that it indicates when the camera is connected to the GO device.

What does the IOX Smarter AI camera measurement represents on the GO Focus device (0 = Disconnected, 1 = Connected).

We've had trouble viewing the live video from the cameras, as when requesting the live video, the error message "Video Unavailable" appears.

Have you detected any problems with Mygeotab viewing live video from Go Focus?

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! ​  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"

<pre data-language="plain">Hi Daniela,

I recommend downloading a report based on communication logs—specifically, using one GO device that isn't associated with a GO Focus and another one that is.

Try to match the conditions so you can compare the logs and reach a conclusion.</pre>