[SOLVED] Unchangable "null" Time Series ID in Time Series Insights

AdamB-4111 346 Reputation points

Hi Folks!

I am bringing in a data source from Azure IoT Hub to Time Series insights and have an error where the Time Series ID is unchangeable and fixed as "null"

Here's the view in Time Series Insights


I'd ideally like to have the Time Series ID value be unique to the device, so I could put a sticker on the enclosure. Is there something I am missing for where to add the data when I send data to Azure IoT Hub? I am using an Azure Sphere RDB.


Azure Time Series Insights
Azure Time Series Insights
An Azure internet of things (IoT) analytics platform to monitor, analyze, and visualize industrial IoT analytics data at scale.
77 questions
0 comments No comments
{count} votes

Accepted answer
  1. AdamB-4111 346 Reputation points

    Hello Folks!

    I figured this out!

    To overcome the issue of Time Series Insights defaulting to a weird value on Azure Sphere, you must enrich the Azure IoT messages with your own deviceId value. This can be done by adding a value of "tags" to the device twin.

    Note about adding things to the device twin! It takes FOREVER for the system to update if you are using Azure Portal. Be patient.
    Also, I have not had any luck removing any text from a device twin JSON via Azure Portal.

    Step 1:
    Add tags to Azure Sphere device twin
    New value added "nickname" : "Rook" (Be Patient here, it will work eventually)


    Step 2:
    Create an enriched message


    Step 3:
    View the deviceId value representing your device in Azure Time Series Insights


    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. António Sérgio Azevedo 7,666 Reputation points Microsoft Employee

    Hi @AdamB-4111 can you share the full name of your device ID?

    The character limit for the Time Series ID's property name string is 128. For the Time Series ID's property value, the character limit is 1,024.
    If a unique property value for the Time Series ID is missing, it's treated as a null value and follows the same rule of the uniqueness constraint.

    See more here: Best practices for choosing a Time Series ID

    1 person found this answer helpful.