This protocol update brings new properties to the supported dataset. In addition to that, three new capabilities are introduced:
Level 13 is fully backwards compatible with Level 12 and introduces no breaking changes. All new SDK releases provide native support for Level 13, while REST API v4 has been updated to support the new properties. You'll find the full changelog on GitHub.
New AutoAPI level 13 binary-to-swift and back parser.
This release is mostly additive, with only minor API changes:
The AutoAPI spec can always be inspected for more details here.
This release is mostly additive, with minor API changes:
The first public release of the Fleet SDK. See the release announcement for more info.
Crypto implementation in Java. Used for Fleet SDK and other crypto.
Rename Runtime enum to Environment, which contains values Owner and Vehicle.
From now on, Java packages will be published on mavenCentral(). Their group ID will be changed from `com.highmobility` to `com.high-mobility`. All of the previous releases will retain their group ID and will be available until the closing of JCenter on February 1st 2022.
The protocol has been upgraded with new data points and capabilities, some highlighted here:
More details can be found here.
New AutoAPI level 12 binary-to-swift and back parser.
Auto API Level 12 spec is used.
All of the new capabilities/properties have been added/updated/deprecated.
This version includes the source code and documentation for easier developing. Also, the release is pushed to jcenter(). This means adding High-Mobility Artifactory url is not necessary anymore.
This is a helper package meant to be used with HMKit Android to queue Bluetooth and telematics commands.
These releases add support for Gradle versions greater than 4.6.
The binary format of the AutoAPI has been changed to unify properties across commands and simplify the range of different value-types. In addition, the change was done to facilitate automatic generation of platform specific libraries from the AutoAPI spec.
Updates to the binary format makes this release not compatible with previous versions.
Most capabilities support requesting just a single or more, specific, properties (in addition to the entire state).
This is now automatically generated from the AutoAPI spec and many namings could be a bit different from the previous versions.
Check the AutoAPI change log for more info.
Fixed the iOS 13 shared key generation issues.
Fix for HMDebugTree.
The AutoAPI library is now automatically generated from the specification. This means some class names have changed. Please refer to the AutoAPI specificationfor up to date class names.
Colour values are now from 0-255, not 0-1.
Version 2.5.8 also updated to Xcode 11, Swift 5.1, SPM and XCFrameworks.
This version fixes an issue where certificates were not deleted.
Fixes crash when parsing invalid command data.
This release includes breaking changes to public API. Note that it's still possible to use the previous Node.js SDK version.
New version of the REST API. V1 will still work for some time but it is recommended to upgrade to newer API as soon as possible. Only v2 is enabled for production vehicle data access.
This Auto API version includes the public interface changes reflecting the level 10 protocol.
All values are now wrapped in a Property. This means to access the property value, property.getValue() should be called. Property also has the failure and timestamp components. All of these components are optional. See Property Structure for more information.
Guide for migrating to 2.10.0:
Add refresh token support for OAuth.
This version includes parsing support for MultiCommand and MultiState. See the code reference for more information.
Auto API level 10 brings protocol updates to properties on a binary level. Properties now include data, timestamp and failure components. This allows for better SDK handling of all possible scenarios when getting data across different car brands. The new protocol is defined in on the Auto API Properties overview page.
Additional updates in level 10 follows.
Added a new type HMBytesConvertable and made the following types conform to it: Bool, Date, Double, Float, String, URL, signed and unsigned integers.
This updates the Java Auto API to level 10. Mind that the percentage values are now double instead of float. Mind that there are no time zones for dates anymore, which always correspond to UTC time.
Fix possible Bluetooth authorisation failures.
Fix OAuth showing blank screen.
This release included only internal changes to Auto Api level 10 property component handling logic. There were no changes in the public API.
This release fixes issues with the OAuth2 flow.
This platform release has incremental updates to the API by introducing Auto API Level 9 along with OAuth2 updates. Each component has further improvements.
This update brings Auto API level 9 support.
This platform release includes several URL changes based on new server architecture that is being rolled out. Note that "sandbox" is being used to refer to any endpoints for working with the car emulators during the development of apps.
Sandbox base URL changed to https://sandbox.api.high-mobility.com/hm_cloud/
Sandbox base URL changed to https://sandbox.api.high-mobility.com/v1
Sandbox base URL changed to https://sandbox.rest-api.high-mobility.com/v1
This is a major release across all SDKs, APIs and emulators that introduces Auto API level 8.
The latest version of the Auto API comes with internal protocol improvements and an expanded data set of vehicle data. In summary:
This release adds support for Auto API level 8. Please note that the release is not compatible with level 7 Auto API (package 1.8.0) and your Auto API code probably needs updating.
This release introduces some changes for the public API of the SDK.
There are some internal changes to the SDK-s logic:
These updates might be useful for the users of the HMKit-OEM library.
Starting with this release all of our Java SDK public methods use our custom Bytes class instead of the byte. For instance it can now be used to access certificate properties or send link commands.
Bytes class can also be used for new constructors and some convenience methods like Bytes.getHex() and Bytes.equals().
Refer to the downloads page for the latest version numbers.
This update follows the releases of Swift 4.1 and Xcode 9.3 bringing compatibility of the HMKit libraries to both. Full details:
This release has been tested on iOS and macOS, and should work on tvOS, watchOS and Linux as well; usable with the Swift Package Manager.
This is a major release across all the SDKs, APIs and the user interface of the Developer Center itself.
The latest version of the Auto API comes with a new internal protocol that brings consistency and flexibility for different car capability variations. Each capability (such as Diagnostics) has now a list of properties. Here's how they work:
In terms of capabilities, it's no longer the case that each capability defines its own format of what is included in the Capabilities message:
There are many new properties that have been added to existing capabilities. There are however some entirely new capabilities:
HMKit Core, the component that all SDKs implement, have been updated with the following:
The Android SDK is from now on available through the JCenter and downloaded directly as a Gradle dependency. As part of this, the SDK has been divided into separate modules: HMKit-Android, HMKit-AutoAPI, HMKit-Crypto and HMKit-Utils. The Auto API library has been updated to level 6 and is open sourced on GitHub.
The iOS SDK has been updated to support the latest core changes. The Auto API library has been updated to level 6 and is open sourced on GitHub.
The Node.js SDK has been updated to support Auto API level 6 and other core changes.
This is a completely new interface for working with Auto API. With the REST API it's possible to work with car data and APIs on any platform.
Good news for Windows users! This release includes support for Windows 10. Just get the latest version from npm or download the sample app.
This is only a minor update with a bug fix for the AccessCertificate.isExpired()method.
This is a bigger release to be compatible with Apple's update to iOS 11. With this release we are adding a Swift 4 (beta) SDK in addition to the stable 1.8.5 release to the download site. In the upcoming months we will phase out the Swift 3 build however.
This release includes a bug fix and an improvement:
This release includes helper functions for sending and parsing all remaining Auto API commands that were not included in the first release - except for Get Capabilities and Get Vehicle Status. We're still hard at work with Windows support but making good progress.
The scaffold sample app has been updated too to best reflect the latest version.
Next up in the backlog is more informative error handling and the final two Auto API commands.
Starting from this release the iOS SDK is shipped with a script AppStoreCompatible.sh that should be used before releasing to App Store. The script removes iPhone simulator related code.
Other updates and bug fixes:
Here's what's new in this release:
An additional app "Basic OAuth" has been added to the samples.
This release includes the following bug fixes:
This is a first release of HMKit for Node.js and the first SDK destined for backend server applications. The SDK supports working with the Auto API through Telematics. For instructions to try it out, follow the Tutorial.
There's two bigger limitations on the first experimental release. First off, it can only be run on Linux and OS X. Windows support coming in upcoming versions. This is due to native C bindings that it used for crypto and internal protocol.
Version 0.1.1 does not yet have helper methods for all Auto APIs. Helpers for the following capabilities are included:
Any feedback for the public methods, especially Auto API handling, is taken into account for next releases.
Here's what's new in this iOS SDK release:
Here's what's new in this Android SDK release: