Developer Portal

Using the Afero Cloud to Keep Time on the MCU

ASR provides two different facilities for setting and keeping time on an MCU:

  • When ASR links to the Afero Cloud, a timestamp and UTC offset data are provided to the MCU via two attributes, and
  • If enabled, a periodic timestamp is supplied to the MCU from ASR once it’s connected to the Afero Cloud, also via attribute.

The first two attributes sent at link time can be used to set a Real-Time Clock (RTC) on the MCU if there is support for one. If your MCU doesn’t support RTC, you can use the periodic timestamp updates to provide a reasonably accurate clock for your device.

Time-of-Day Attributes Sent at Link Time

When ASR comes online, it will return two attributes to the MCU. These attributes contain a timestamp and UTC offset data and are always sent. No configuration is required to receive them, although you do have to listen for them in your application’s attribute handler. If you don’t need clock support in your MCU application, you can safely ignore these attributes.

The two attributes are described below:

  • 65015 - LINKED_TIMESTAMP (signed 32-bit long)

    This is a UNIX Epoch (number of seconds since 00:00:00 1/1/1970) UTC timestamp marking when ASR successfully last linked to the Afero Cloud. The timestamp is returned shortly after ASR reboots and should be reasonably close to actual current time.

    The latency from the Cloud back to the MCU is typically less than 1-2 seconds, but don’t rely on this timestamp being more accurate than +/- 10 seconds (worst case). If your time of day (TOD) requirements are not critical, this is a very convenient way of getting TOD with little work.

  • 65001 - UTC_OFFSET_DATA (byte[8])

    This byte array contains three pieces of information: the current local timezone offset from UTC, the next UTC offset, and a UNIX Epoch timestamp of when the “next” UTC offset is valid. Specifically:

    • [0-1] - Little-endian signed int containing the local timezone offset from UTC in minutes
    • [2-5] - Little-endian unsigned long containing an Epoch timestamp (UTC) for “next” offset validity
    • [6-7] - Little-endian signed int containing the “next” local timezone offset from UTC in minutes

    UTC Offset is determined by the Location attributes set (by you) for ASR and are not dynamic in any way. The UTC Offset can and will be wrong if the Location in the device configuration is incorrect. You can set the correct Location for your Afero device using the Afero mobile app, or by using the Afero Inspector developer tool at

Let’s look at examples of these attributes and the meanings of their values. These attribute values:


Translate to:

Link Time: 0x5a2b06c3 (Fri 2017-12-08 21:40:19 GMT)
Current UTC Offset: -300 minutes (0xFED4) (Eastern Standard Time, in this example)
UTC Offset Change: Sun 2018-03-11 07:00:00 GMT (0x5AA4D3F0) (Spring 2018 USA DST Time Change, 2am local time)
Next UTC Offset: -240 minutes (0xFF10) (Eastern Daylight Time, in this example)

Only assume that LINKED_TIMESTAMP is current when the state of ASR transitions to a connected state. You can use get_attribute to return the Linked Timestamp at any point, but remember the result returned will be the time ASR first linked or re-linked to the Cloud, which could be significantly in the past if the device has been connected for a long time. We strongly suggest not querying the LINKED_TIMESTAMP attribute and only handle it when it is sent unsolicited to the MCU.

Periodic Time-of-Day Attribute Updates

After ASR comes online, you can receive a periodic timestamp update from ASR via attribute. This attribute is sent to the MCU every 60 seconds starting at link time. This update is disabled by default but you can enable it for your device profile using the Afero Profile Editor as follows: on the Attributes Definition window, MCU Configuration section, select the Receive UTC Time checkbox. You must enable this attribute on a per-profile basis, and the feature requires that your device be running firmware Release 2.0 or higher.

  • 1201 - ASR_UTC_TIME (signed 32-bit long)

    This is a UNIX Epoch (number of seconds since 00:00:00 1/1/1970) UTC timestamp, returned by ASR once per minute, starting at the time ASR links to the Afero Cloud. So the first ASR_UTC_TIME stamp will equal the value of LINKED_TIMESTAMP described above.

    This timestamp is sent once per minute but not “on the minute” (“:00 seconds”) so you will need to account for that offset of +/- 30 seconds if you use this timestamp without an RTC.

afero_clock Example Code

In afLib3, we’ve included the afero_clock application, which provides a simple method for:

  • Listening for the Linked Timestamp and UTC Offset attributes in attrEventCallback under AF_LIB_EVENT_ASR_NOTIFICATION.
  • Listening for periodic ASR_UTC_TIME updates if enabled in your profile.
  • Setting a C time struct that can be manipulated within your application.

The example profiles provided in the afero_clock project enable the ASR_UTC_TIME attribute and will display the value when received.

Example Code Notes

  • For best results, use an RTC chip and use the Linked Timestamp and UTC Offset attributes to set the RTC. By doing this you’ll have access to a reasonably accurate clock. Remember, the Linked Timestamp is only sent to the MCU when ASR links or re-links to the Afero Cloud.

  • The device profile created using the Afero Profile Editor doesn’t need any specific support for Linked Timestamp or UTC Offset attributes, as they are system attributes and will be presented to the MCU as long as the Afero device profile has MCU support enabled. However, in order to receive the periodic ASR_UTC_TIME attribute updates, you must have selected the Receive UTC Time checkbox for your device profile (using the Profile Editor, Attribute Definition window, MCU Configuration section).

  • The example code provided in afLib3 includes some code that protects against accepting LINKED_TIMESTAMP when an MCU application requests that data via get_attribute. Since the value returned is the timestamp of when ASR last linked to the Afero Cloud, this value will not update except when ASR re-links its connection. If this level of paranoia isn’t needed, all references and checks to “timestamp_read” can be removed.

  • When ASR first boots, it will send an SYSTEM_UTC_OFFSET_DATA attribute update to the MCU; however, all data in this attribute will be zero. Since UTC Offset=0 is valid, you should check for the value of the UTC Offset Change Timestamp (the middle four bytes of the attribute value). If this timestamp is zero then the UTC Offset data is invalid and can be ignored. Once ASR links, you will receive the Linked Timestamp attribute and another UTC Offset attribute with valid data. In the case of a device with no Location or local timezone defined, the UTC_OFFSET_DATA attribute will remain all zeroes and can be safely ignored.

  • It is possible to receive a new SYSTEM_UTC_OFFSET_DATA attribute update at any time (for example, the passing of a Daylight Saving Time boundary). As long as the Offset Change Time Timestamp is greater than the Linked Timestamp (or the Current Timestamp if you have an RTC), then the update data should be considered valid and the RTC updated accordingly (typically by subtracting the “old” offset and adding the “new” offset to re-adjust the clock to the new timezone).

  • In C/C++, the strftime() call can be used to format either timestamp into human-readable forms.

  • Data types for the timestamp attribute values are:

    • int32_t linked_timestamp
    • int16_t utc_offset_now
    • int16_t utc_offset_next
    • int32_t utc_offset_change_time
    • int32_t asr_utc_time