Skip to main content

Geotab Drive app shows HOS in gray and says "vehicle not supported". Why is this happening?

VVarg-1205
Original Poster

When In log in to my Geotab drive, I go to dashboard and we're it says “hos” it in gray and says vehicle not supported. Why is this happening?

0692J000008hKfMQAU.jpg

Join the conversation

You need to be logged in to reply to this post and participate in the Geotab Community discussions.

Top Answers

Hey, @VVarg-1205​!

 

Like @KellyS-2958​ mentioned, this is probably a device plan issue. If your reseller uses the standard Geotab device plans, there are currently four different plans available:

 

Base --> basic tracking only, no accelerometer or engine data

Regulatory --> basic tracking with minimal engine data (odometer) for ELD compliance

Pro --> robust engine and accelerometer data

ProPlus --> active tracking (vehicles move on map), all 3rd-party integrations

 

All plans cover the previous plans' stuff plus the added info. That's just a short summary, but you can see all the plan info here if you're interested:

Geotab Software Packages

 

You need at least the Regulatory plan to have HOS supported.

 

Hope this helps! :)

 

Best,

Joy @FleetNavSystems-1081

Hi @VVarg-1205​ 

In addition on what @jjake-8255​ and @KellyS-2958​ mentioned, This message will also appear whenever the GO device is missing any of these engine measurements:

  • Engine operational time
  • Engine road speed
  • Odometer

 

These measurements could be affected if this info is not supported by your vehicle either by the make/year, or being missed by vehicle health (active engine codes related to these measurements).

 

I mean, your Geotab Plan could be the right one, but it is limited by the information provided by the vehicle.

 

Hope this helps.

 

Marco

11 Replies

This is usually due to a GO Device is having a device plan issue and it's missing any of the engine measurements. 

 

Check your device plans, and make any adjustments needed so the device can communicate.

Hey, @VVarg-1205​!

 

Like @KellyS-2958​ mentioned, this is probably a device plan issue. If your reseller uses the standard Geotab device plans, there are currently four different plans available:

 

Base --> basic tracking only, no accelerometer or engine data

Regulatory --> basic tracking with minimal engine data (odometer) for ELD compliance

Pro --> robust engine and accelerometer data

ProPlus --> active tracking (vehicles move on map), all 3rd-party integrations

 

All plans cover the previous plans' stuff plus the added info. That's just a short summary, but you can see all the plan info here if you're interested:

Geotab Software Packages

 

You need at least the Regulatory plan to have HOS supported.

 

Hope this helps! :)

 

Best,

Joy @FleetNavSystems-1081

Hi @VVarg-1205​ 

In addition on what @jjake-8255​ and @KellyS-2958​ mentioned, This message will also appear whenever the GO device is missing any of these engine measurements:

  • Engine operational time
  • Engine road speed
  • Odometer

 

These measurements could be affected if this info is not supported by your vehicle either by the make/year, or being missed by vehicle health (active engine codes related to these measurements).

 

I mean, your Geotab Plan could be the right one, but it is limited by the information provided by the vehicle.

 

Hope this helps.

 

Marco

We don't really use HOS here but could this also be caused by the HOS setting being turned off under the More Details section of the vehicle details?

Interesting idea, @TonyFC-1053​. I tried this out in my demo database, but couldn't replicate the issue. Mind you, I didn't drive after setting the HOS setting to "Off", but I will try again after I do some driving just to confirm that this isn't one of the reasons. (Should be, 'though...)

I can't even get the Drive app to open any more so I can't even test it on my unit.

Hey, @TonyFC-1053​!

 

I have verified that turning this off and driving still doesn't change the HOS log options.

 

Best,

Joy

Ahh well, it was just a thought, ignore me then.

@VVarg-1205​ I hope someone else was able to help solve your problem.

It was an interesting thought. I'm glad we now know for sure that can't be it. 😎

Tony we had that issue after some phone updates. When we deleted the app and reinstalled it the issue was corrected.

I just tried reinstalling and it's still not working :(

Still have questions?