The SDK source code is hosted on GitHub at https://github.com/ARMmbed/mbed-cloud-sdk-java
This news file contains a log of notable changes to the SDK. Built artefacts, including previous versions, can be retrieved using any Java package manager (e.g. Gradle, Ant/Ivy, Maven) from Jcenter or Maven Central.
-
Modified the notification listener to use a websocket connection rather than long polling. (#1776)
-
Added a way to control the notification system directly from the SDK entry point. (#2138)
-
Added a way to get, set, execute resource values from the SDK entry point rather than through the Connect API (#2144)
-
Harmonised the naming in notification messages (#2170)
-
Added a master observer to listen to any notifications coming from the Cloud (#28062019)
-
Updated dependencies to fix security issues (#1)
-
Fix NullPointException during subscribing to connected devices. (#20190904)
-
Modified FirstDesktopApp example so that it works with devices set up using Pelion Device Management IoT Connection Tutorial (#1)
-
Replace old Campaign update example with new one based on foundation interface (#1955)
-
Added examples for resource value and subscription. (#2163)
-
Supports device groups (#1374)
-
Supports colour and image branding (#2031)
- Updated dependencies to fix security issues (#1)
- Updated dependencies to fix security issues (#1)
-
Device enrolment report download was improved (#160519)
-
Reduced javadoc warnings (#1605192)
- #1605193
-
First to Claim - to bulk upload for Enrolment Identities added to the Foundation Interface. (#1162)
-
Refactored the communication channel selection in connect. Introduced
NOTIFICATION_CHANNEL_FORCE_CLEAR
andNOTIFICATION_CHANNEL_SKIP_CLEANUP
environment variables for automated environments such as server-side applications. (#1302) -
First to Claim - to bulk delete for Enrolment Identities added to the Foundation Interface. (#1432)
-
Certificate entities added to the Foundation Interface. (#1438)
-
Update Campaigns statistics summary and events added to the Foundation Interface. (#1467)
-
Introduction of the Foundation Interface which adds a new 'Entities' based interface. (#1567)
-
Addition of server credentials entity to the Foundation Interface including ability to get all credentials in a single resource. (#1604)
-
Account Management entities to support Aggregators / Sub-Tenant accounts added to the Foundation Interface. (#1605)
-
It is now possible to carry out bulk (batch) device enrollment (#1727)
-
Foundation SDK layer was introduced: DAOs are now available for every Pelion Cloud entity/model (#1741)
-
Device Events entity added to the Foundation Interface. (#1768)
-
Addition of device entity to the Foundation SDK and support added for Certificate Renew. (#1827)
-
Rebranded the SDK to reflect its new name: Pelion Device Management SDK (#1911)
-
Pelion Device Management rebranding (previously Mbed Cloud). (#1915)
-
Support for Certificate Blacklist (Enrolment Denials) added to the Foundation Interface. (#1997)
-
Device Update support added to the Foundation Interface. (#2004)
-
Support for filtering list endpoints added to the Foundation Interface. (#2039)
-
Pre-Shared Key (PSK) added to the Foundation Interface. (#2339)
- Fixed various warnings across the project (#1)
- Changed the log level of
An error occurred when trying to fetch server date from API metadata
to remove confusion. (#2233)
- #1
-
It is now possible to renew certificates or manage Certificate issuers in the Security module. (#1868)
-
LWM2M actions on resources are now performed using solely Observers and RXJava introduced with Subscriptions. (#4)
Set
andexecute
resource value actions now use/v2/device-requests/
enpoint as former endpoints are deprecated (#1883)
- Added a generic client
GenericClient
which can be used by the user to call any endpoint of Pelion Cloud. (#1498)
-
Added a filter on Device ID in Campaign model (#1478)
-
Use pyautoversion to set SDK's version (#2)
-
Fixed
SpotBugs
gradle plugin failure with latestgradle
(#3)
-
It is now possible to download active devices and firmware updates reports in the Billing module. (#1398)
-
Settings can now be configured from
.env
files. See https://github.com/cdimascio/java-dotenv for more details. Host and API keys can be specified using the following environment variables: respectivelyMBED_CLOUD_SDK_HOST
andMBED_CLOUD_SDK_API_KEY
. (#927)
-
Added a preferences file for development on Eclipse [/config/eclipse] (#1)
-
Billing module was integrated. This provides the ability to fetch various reports regarding billing (e.g. Service package status, remaining quota, history of transactions) (#1216)
-
Updated account and user custom properties fields in AccountManagement (#1254)
-
Paginator and ListOptions objects used in the SDK to list elements now take
maxResults
andpageSize
to remove the ambiguity of former parameterlimit
. (#1296) -
Added an experimental single point of entry for using the SDK (MbedCloudClient) (#1348)
-
Removed custom properties field from user and account models (#1362)
-
Pre-shared keys registered in the Cloud can now be listed (#631)
-
Added new field (phase) to update campaign. (1057)
-
Added 'Resource value change' subscription channel. This supercedes 'presubscription' and 'subscription' behaviours to provide a uniform interface in line with the existing 'Device state change' channel. See Connect module > subscribe(). (1102)
-
Updated models regarding Users and Accounts to better manage custom properties. Added additional filters when listing users. (1225)
-
It is now possible to upload all device decryption keys for a campaign as a single blob when adding the firmware manifest (552)
-
Bootstrap module for Pre-Shared Keys was integrated. This provides the ability to set Pre-Shared Keys for device bring-up. (630)
- Updated Connect backend endpoint names (1235)
-
Exponential backoff in case of request call failure during notification pull was implemented. (1065)
-
Specified User Agent header when sending requests to Pelion Cloud (634)
-
Notification channels for device registration status notifications (4 events) were added. (722)
-
Updated Connector CA schema (1081)
-
Updated contribution guidelines (729)
-
Modified backends to avoid duplicate code leading to Android compilation issue (976)
The application source code is hosted on GitHub at https://github.com/ARMmbed/mbed-cloud-sdk-java Built artefacts can be retrieved using any Java package manager (e.g. Gradle, Ant/Ivy, Maven) from Jcenter or Maven Central.
- REST API changes:
- Device Directory
- Update
- Account Management
- Enrollment (First to claim) was introduced
- Account admin can upload a list of devices to claim and view the status of claimed devices
- Connect
- A new endpoint was introduced for retrieving resource values.
- Bug fixes and improvements:
- Get resource value bug listed in previous releases was fixed
- Added states to upload campaigns
- File upload to the cloud (correct filename)
- Bug regarding exceptions thrown when empty lists were retrieved
- Connect - deleteSubscriptions()
- Environments supported:
- Java > 1.7
- The Java SDK cannot currently be used on Android because of the following error.
com.android.build.api.transform.TransformException: com.android.dex.DexException: Multiple dex files define Lcom/arm/mbed/cloud/sdk/internal/JSON$1;
The application source code is hosted on GitHub at https://github.com/ARMmbed/mbed-cloud-sdk-java Built artefacts can be retrieved using any Java package manager (e.g. Gradle, Ant/Ivy, Maven) from Jcenter or Maven Central.
- REST API changes:
- Device Directory
- Update
- Bug fixes and improvements:
- Swagger codegen upgrade
- Paginator
- Developer certificate missing data
- File upload to the cloud
- Date conversion
- Filter issues
- Environments supported:
- Java > 1.7
- Testing shows that
getResourceValue
(Connect module) will fail when the cloud service returns a value directly, rather than through an open notification channel. This affects all previous versions. - The only known workaround at present is to ensure the cloud cache is not used by:
- Waiting between calls to get_resource_value
- Reducing the configured TTL on the cloud client image on the device
The application source code is hosted on GitHub at https://github.com/ARMmbed/mbed-cloud-sdk-java Built artefacts can be retrieved using any Java package manager (e.g. Gradle, Ant/Ivy, Maven) from Jcenter or Maven Central.
- Initial release tracking Pelion Cloud 1.2 APIs
- APIs supported:
- Account Management
- Certificates
- Connect
- Device Directory
- Update
- Environments supported:
- Java > 1.7
- Testing shows that
getResourceValue
(Connect module) will fail when the cloud service returns a value directly, rather than through an open notification channel. This affects all previous versions. - The only known workaround at present is to ensure the cloud cache is not used by:
- Waiting between calls to get_resource_value
- Reducing the configured TTL on the cloud client image on the device