page-user page-user-brent-mcinnis-1257 template-account-profile page-status-200 theme-harmony user-guest

Company

Title

Hi <a href="/user/daren-porter-1148" data-id="1148" data-value="DarenPorter-1148" data-denotation-char="@" class="text-decoration-none mention">@DarenPorter-1148</a>​, thanks for the additional context! You're right that using the DeviceLink API does not add TrailerAttachments as well, so backwards compatibility is not easily achieved with this set-up. It is likely when you tested that we had not yet started using DeviceLinks in MyGeotab or Drive to determine trailer attachments, so switching the APIs would not have the same effect through the rest of the product.  This is a really good point, and one that I will bring up to our dev team next week for further discussion to ensure that when the documentation is released this is already set up in our product such that if integrators migrate early to the DeviceLink API that it will work throughout the entire product and not only in some areas. I'll get back to you once I learn more on our end. I'll make sure you and other integrators have as much time as possible to migrate existing integrations away from TrailerAttachments, and once we have a better idea on timeline we'll let you know, but we won't be sharing a timeline until after the DeviceLink documentation is shared and available to everyone to use successfully, and that is our next step for now.

DeviceLink Changes &amp; Implementation Assistance

DeviceLink Changes & Implementation Assistance

Certainly a new plan will be coming soon and this new API has not been forgotten. Not all products were ready to fully switch over from vehicles/trailers and TrailerAttachment to an asset-centric approach using DeviceLink in time for the plan that may have been shared previously. Apologies for the silence on this topic, but we are getting close to releasing the API documentation like I mentioned, and ensuring that we properly dog-food this API in our product to ensure that it works as expected for everyone. I'll make sure to share the documentation link here once it's ready to go.We'll work on a deprecation plan for TrailerAttachment after it is no longer is use by any native Geotab products, and our partners have had the chance to try out the DeviceLink API and provide any feedback that may come up with early adopters. I'll make sure this is not abrupt or done without notice to our partners.

Hi <a href="/user/jacob-purvis-1275" data-id="1275" data-value="JPurv-1275" data-denotation-char="@" class="text-decoration-none mention">@JPurv-1275</a>​ &amp; <a href="/user/lp-papillon-1145" data-id="1145" data-value="LPPapillon-1145" data-denotation-char="@" class="text-decoration-none mention">@LPPapillon-1145</a>​, Thanks for bringing up this important topic. I'll be taking on releasing the DeviceLink API documentation and migrating from TrailerAttachments to using DeviceLink in the future. We are close to releasing the API documentation for DeviceLink, however have no immediate plans to sunset TrailerAttachment, since we understand all partners need proper time to use the new API to ensure a smooth transition.  Since it sounds like both of you have attempted to use DeviceLink in the past already and mention it is on yet ready, could you clarify the difficulties you ran into (aside from it not being documented at the moment)? It sounds like it worked for some things but you were not able to make the API work for linking Tractors to Trailers and seeing the Driver Log display reflect both the Tractor and the Trailer - is this the only major problem you encountered in your previous testing?  The documentation we had planned to release shortly simply show the properties of this object and how it can be used, but potentially if there's one or two areas where there have been difficulties in your experience then we can try to further detail those use-cases at the same time or shortly after. Again, I would not have expected partners to try using DeviceLink before now due to a lack of documentation, so my question is only because it sounds like both of you have tried to use the API anyway. Any further information is appreciated, for now we'll still work on the documentation to share with you and the rest of our partners soon. Thanks,Brent McInnis

<a href="/user/carl-yendes-1686" data-id="1686" data-value="CYend-1686" data-denotation-char="@" class="text-decoration-none mention">@CYend-1686</a>​  thanks for raising this question. This has come up in the past and has been discussed as a potential future product offering from Geotab. We have the building blocks in place in order to achieve this:<ol><li>Ability to toggle a vehicle from being regulated or not (this is the Automatic HOS setting on the vehicle settings page)</li><li>Tracking the time periods where the vehicle was regulated or not (this is tracked by system logs called HosEnabled/HosDisabled)</li></ol> This is on our radar for further discussions/solutioning, and we are interested in solving this problem. Ideally we could implement an automated solution which determines when a vehicle may be regulated or not, but this may not be possible for a first implementation. In some cases, we've seen customers or resellers use the API to develop an add-in which allows drivers to switch the vehicle between regulated and unregulated, but nothing offered natively from Geotab just yet. No timeline to share today, but it is on our plate for the future. If you'd like to discuss your specific use-case or how this might be possible please let me know and we can set something up. Thanks,Brent

Recent Activity