Brand

Back
Learn
DODGE

Dodge

Brand

Asset types
Vehicles
Regions
United States
Reliability
Pending

Interventions

TitleIntervention IDAsset type
Re-link your Dodge account to re-enable communicationa64531e0-439a-561d-9f9f-2c5bb5d01193Vehicle
Accept the Dodge terms and conditions for communication with your device42039731-9279-515f-84e8-d45aba68e44cVehicle

Learn

Learn

This list represents a glossary of the terms you may encounter while browsing the overview of supported vendors.

  • Activation required

    Most brands are activated by default. However, certain brands’ asset types need to be activated upon request. They are highlighted with “Activation required”. A brand’s asset type will require activation if it has a status of Beta, is missing one or more capabilities, and/or has a poor Reliability score.

    CriteriaDescription
    Is in BetaThe brand has a Status of Beta
    Has limited capabilitiesMissing one or more capabilities
    Has low reliabilityThe brand has a Reliability of Poor

    Activating brands

    To activate one or more brands, you can enable them in your client's settings in the dashboard or reach out to your contact at Enode.

  • Capabilities

    Capabilities reflect what information we are able to fetch, and what actions we are able to perform via the vendor APIs. Missing capabilities are either due to missing hardware capabilities (e.g. a vehicle without an onboard GPS) or due to missing API endpoints from the vendor (e.g. inability to send start/stop commands to a vehicle).

    Information about coming capabilities

    We unfortunately can not provide any further information about whether certain capabilities will become available in the future, as these changes are driven by the vendors.

    Interventions

    For some brands and models, some or all capabilities need to be unlocked via an intervention performed by the user. Examples on this could be signing up for first-party user accounts, signing up for a subscription, changing settings in the first-party app or changing settings on the device itself.

    To see interventions for a specific vendor, navigate to the vendor and click on interventions next to the vendor name.

  • Regions

    Some vendors run their APIs and services in multiple region-based environments. This field reflects which regions are supported for the given brand or model.

    Users outside these regions

    Users in geographical areas outside these regions might still be able to connect their hardware, as long as their account or hardware model maps to one of these regions (e.g. users in Norway could be mapped to the EU region, or users in Canada could be mapped to the US region).

  • Reliability

    This score picks up factors such as the quality, stability, response times and data update frequency for the vendor APIs (e.g. a vehicle brand) we connect to. In some cases, even though we support a full set of capabilities for the brand and/or model, the vendor APIs might be unstable, experience issues on a frequent basis or be sensitive to frequent data requests.

    Stable (3 out of 3)Stable

    The vendor APIs are considered stable with quick response times, resulting in an overall optimal user experience.

    Medium (2 out of 3)Medium

    The vendor APIs are experiencing instability at times, and/or high response times, and/or are sensitive to frequent polling.

    What we recommend

    The user experience is expected to be sub-optimal at times. If you decide to activate brands or models with this score, we suggest giving your users a heads-up about this.

    Limited (1 out of 3)Limited

    The vendor APIs are experiencing frequent issues with stability, and/or response times, or are sensitive to frequent polling.

    What we recommend

    The user experience is expected to be degraded. If you decide to activate brands or models with this score, we suggest giving your users a heads-up about this.

    Pending

    The model is in Beta and a score is not established yet.

  • Status

    This flag reflects the status of our integration towards the vendor APIs for the specific brand or model.

    Live

    The integration work is complete. The Capabilities reflected match the currently available information and actions available through vendor APIs, and will not change unless vendor APIs change in the future.

    Beta

    The integration work is still in progress. Instability is to be expected. The full specification of Capabilities could change throughout the integration phase. The integration phase typically lasts for 3-6 months.