v0.7.2

Astarte Device SDK Zephyr v0.7.2 release.

CHANGELOG

Changed

• All the library samples have been merged into a single sample called astarte_app.

Removed

• Dependency to CONFIG_SYS_HASH_FUNC32 which is not required.

Fixed

• Memory leaks in kv_storage driver and device creation process.
• Destroy function properly frees all cached MQTT messages.

v0.7.1

Astarte Device SDK Zephyr v0.7.1 release.

CHANGELOG

Fixed

• Connection callback is correctly called also when session present is true.

v0.7.0

Astarte Device SDK Zephyr v0.7.0 release.

CHANGELOG

Added

• Support for Zephyr 3.7.
• Support for MQTT sessions. The device will retain MQTT session information in between connections.
• Device ID generation utilities. The functions astarte_device_id_generate_random and
  astarte_device_id_generate_deterministic can be added to generate a valid device ID to connect
  a device to Astarte.
• Method astarte_device_get_property. This method can be used to read values of properties
  stored in persistent storage.
• Interface generation target that can be enabled by following
  [build time interfaces definition generation]
  (README.md#build-time-interface-definitions-generation).

Changed

• Dependencies for the Astarte device SDK library are specified using depends on instead of
  select.
• ASTARTE_PAIRING_DEVICE_ID_LEN has been renamed to ASTARTE_DEVICE_ID_LEN.

Removed

• Support for Zephyr 3.6 in the code samples and tests.
• The UUID utilities. As their only purpose was to generate device IDs and have been replaced by
  the device_id.h utilities.
• The configuration option CONFIG_ASTARTE_DEVICE_SDK_GENERATE_DEVICE_ID. Generating a device ID
  should be performed using the device_id.h utilities that are always available.

v0.6.1

Astarte Device SDK Zephyr v0.6.1 release.

CHANGELOG

Fixed

• Device state is changed to CONNECTED or DISCONNECTED before calling the appropriate callback.

v0.6.0

Astarte Device SDK Zephyr v0.6.0 release.

CHANGELOG

Added

• Device ID as a field in the astarte_device_config_t and a parameter of the astarte_pairing_register_device function. This makes it possible to specify a device ID at runtime.
• Utilities functions to convert an UUID to a base64 and base64 url and filename safe string.
• Preprocessor define ASTARTE_PAIRING_DEVICE_ID_LEN representing the fixed length of a device ID string.

Changed

• Renamed the astarte_value_t type to astarte_individual_t to better reflect its content.
• Renamed the astarte_value_pair_t type to astarte_object_entry_t to better reflect its content.
• Renamed the mqtt_connected_timeout_ms field to mqtt_poll_timeout_ms in the astarte_device_config_t struct.

Removed

• Kconfig option CONFIG_ASTARTE_DEVICE_SDK_DEVICE_ID. Device ID should be defined using the astarte_device_config_t struct during device initialization.
• The session_present flag from the struct astarte_device_connection_event_t.

v0.5.0

Astarte Device SDK Zephyr v0.5.0 release.

CHANGELOG

Added

• Method to stream device-owned object aggregated datastreams.
• Methods to set and unset device-owned properties.
• Mapping type astarte_mapping_t. To be used to store Astarte mapping definitions.
• West command to generate interfaces definitions from .json files.
• Macro ASTARTE_UUID_STR_LEN specifying the length in characters of the string representation of
  a UUID.

Fixed

• Incorrect hardcoding of MQTT client ID. The client ID is now unique for each Astarte device in a
  single Astarte instance.

Changed

• The astarte_device_data_cbk_t callback has been replaced by three separate callbacks.
  One for set properties, one for unset properties, one for datastreams individual, and one for
  datastreams objects.
  Each callback can be enabled independently from the others using the astarte_device_config_t
  struct.
• All the data callback events now contain a generic astarte_device_data_event_t, placed inside a
  callback-specific event containing additional information. The unset property callback is an
  exception as it gives the user an astarte_device_data_event_t directly.
• The received data is provided to the user in the form of an astarte_value_t or an array of
  astarte_value_pair_t instead of a BSON document.
• The transmission of data to Astarte has been moved outside of the reception callbacks and into a
  separate thread.

Removed

• BSON serializer utilities from bson_serializer.h.

v0.5.0-alpha

Astarte Device SDK Zephyr v0.5.0-alpha release.

CHANGELOG

Added

• Initial SDK release, supports pairing and publish/receive of basic Astarte types.