I started using ADT with the samples provided, and the "occupancy-quickstart" project created an IoT Hub automatically. I can send events to it and redirect them to another location using endpoints, but I don't see the hub anywhere in our subscription, and as such, I cannot manage it. Also, it doesn't appear when I run the "az iot hub list" command in the Azure console.
So, how can we access that hub? Or maybe a best practice would be to create one hub beforehand and assign it to the root of the ADT space tree by hand?
Thanks for clarifying this.
Regards

I made a setup using the csharp ProvisionSample flow.

Simplified the user defined function to just set the sensor value in the graph:

function process(telemetry, executionContext) {

try {
// Log SensorId and Message
log(`Sensor ID: ${telemetry.SensorId}. `);
log(`Sensor value: ${JSON.stringify(telemetry.Message)}.`);

// Get sensor metadata
var sensor = getSensorMetadata(telemetry.SensorId);

// Retrieve the sensor reading
var parseReading = JSON.parse(telemetry.Message);

// Set the sensor reading as the current value for the sensor.
setSensorValue(telemetry.SensorId, sensor.DataType, parseReading.SensorValue);

} catch (error) {
log(`An error has occurred processing the UDF Error: ${error.name} Message ${error.message}.`);
}
}

Created some spaces, with a device in one of them, with a iothub resource in the space, added sensors (with unique hardware ids each) to the device, created matchers for the space with the device, created the UDF with said matchers and added role assignment for the UDF.

I made myself a simple iothub device client script so I can manually push the data and verify that values show up in the graph.

Noticed that for some hardware ids (all shorter length than 72 - they have 30 at most) data doesn't get shown in the graph.

I tested by running the iothub client script after creating the sensor (and matcher and everything), then by updating its hardware id with PATCH requests to /sensors API. Most of the times I couldn't push data to a sensor with hardware id containing a space character, but I couldn't find a pattern beside that.

Are there other constraints for sensor hardware id besdies maximum length of 72 ?
Could this be a problem with iothub and not digital twins ?

Hello,

I am trying to replace an already existing endpoint to make it point to a different Events Hub instance. Checking the swagger documentation for my Digital Twins, I saw the PUT /endpoints/{id} which should do just that.
But, I am currently getting a surprising error:
{
"error": {
"code": "400.600.000.000",
"message": "An eventhub endpoint with DeviceMessage eventType has already been created. Only one endpoint of this combination can be created."
}
}

This is a similar body to the one that I am using:
{
"type": "EventHub",
"eventTypes": [
"DeviceMessage"
],
"connectionString": "Endpoint=sb://my-namespace.servicebus.windows.net/;SharedAccessKeyName=full-permissions;SharedAccessKey=someKey;EntityPath=my-entity",
"secondaryConnectionString": "Endpoint=sb://my-namespace.servicebus.windows.net/;SharedAccessKeyName=full-permissions;SharedAccessKey=someKey;EntityPath=my-instance",
"path": "my-instance"
}

Is that an intended behaviour? I can delete my existing endpoint and recreate it. From my point of view, it defeats the purpose of a PUT REST API endpoint to not be able to replace that entity.

Kind regards,
Tudor Mazilu