Azure Device Explorer Twin Error about azure-iot-pcs-remote-monitoring-dotnet

[timlaverty]

I suspect you have more than one reader on the stream already. Please read the following:

• https://blogs.msdn.microsoft.com/gyan/2014/09/02/event-hubs-receiver-epoch/
• https://community.hortonworks.com/questions/80711/getting-connectionerrorexception-while-reading-dev.html
• Azure/amqpnetlite#162

If you stop these receivers deviceexplorer should be able to read from your eventhub sitting behind the IoTHub.

Also, in the future please file DeviceExplorer bugs here: https://github.com/Azure/azure-iot-sdk-csharp/issues

This tool is a CSharp SDK tool: https://github.com/Azure/azure-iot-sdk-csharp/tree/master/tools/DeviceExplorer

[faister]

I got the same issue. While @timlaverty is right to say that this is due to having more than one reader on the stream, it is still an issue nevertheless and I reckon that this should be called out as an Improvement. At the very least would be helpful to explain in this repo's documentation about how to circumvent this issue. The Telemetry Agent is already reading off the IoT Hub EH compatible endpoint with the consumer group $Default. Hence what I did was I use Azure CLI to create another consumer group. These are the steps:

1. az login
2. az iot hub consumer-group create --hub-name "{IoTHubname}" --name {consumer group name}
3. az iot hub consumer-group list --hub-name "{IoTHubname}"

You will see $Default and your new consumer group name. Then in your Device Explorer (Windows version), in the Data tab, click the Enable checkbox next to Consumer Group and enter your consumer group. You should be able to see the events streaming off IoT Hub for any of the simulated devices.

[timlaverty]

@faister thanks for adding the instructions. What we plan to do in the future is create a separate group, leaving the default alone. This should eliminate the bulk of cases (though still could happen if folks put multiple readers on the other stream). @ppathan @hegate for FYI.