DeviceExplorer returns error when using Call Method On Device form when using latest API version 2016-11-14 about azure-iot-sdk-csharp

[damonbarry]

It looks like the device isn't connected (ErrorCode:DeviceNotOnline). Are you sure the device is connected, and is it connected via MQTT? Cloud-to-device methods are only supported currently for devices connected over MQTT.

[tedvanderveen]

@damonbarry yes the device is connected via MQTT. Also what is strange is that the error says Timed out waiting for device, but the error response is returned in less than a second while timeout is set to 60 secs as you can see.
Any help is very much appreciated.

[tedvanderveen]

I searched for the Tracking ID in the IoT Hub instance diagnostic logs, but cannot find that record. Maybe someone in the IoT Hub team can look it up for more details about this error?

[tedvanderveen]

Is there a working end to end sample/test code available so we can see Direct Methods in action?

[jasmineymlo]

Below is the sample code for Methods on mqtt
https://github.com/Azure/azure-iot-sdk-csharp/blob/master/device/samples/DeviceClientMethodMqttSample/Program.cs

[tedvanderveen]

@jasmineymlo that sample is not applicable to this use case as it uses Devices Client and in our case we need to call the method from the Cloud.

[olivierbloch]

Hi @tedvanderveen
You can find a sample here: https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-csharp-node-direct-methods
We will need to update this doc to replace the device side code with the new C# samples that Jasmine was pointing to. In this doc you will find the service side of the sample in C#.

[tedvanderveen]

Thanks @olivierbloch but I tried it, still exactly same error. Did you try it and got successful results?

[olivierbloch]

Hi @tedvanderveen.
I was indeed successful with both a device using the node sdk and also using the C# direct method sample.
Here is how I proceeded:

• For Node

  • I cloned the https://github.com/azure/azure-iot-sdk-node
  • navigated in a prompt to the folder device/samples
  • Ran the following commands
    npm install
    node device_method.js mydeviceconnectionsting
    (using an actual connection string)
  • then I used the Device Explorer tool (just installed from latest release of this repo) to invoke the method "getDeviceLog"
  • Got response in Device Explorer

• For the C# sample:

  • Cloned the current repo
  • Opened the solution device/iothub_client_deviceclient.sln
    - In the project Samples/DeviceClientMethodMqttSample, I edited the connection string, then built and ran (only this project, not the full solution)
  • Then I used the Device Explorer tool to invoke the method "GetDeviceName"
      - Got response in Device Explorer.

Are you able to see telemetry data from the device in Device Explorer when running the sample DeviceClientMqttSample with the same connection string as the one you use for testing Methods?

[tameraw]

@tedvanderveen - Closing. Please reopen if you're still having an issue.

[epaulson]

Sorry for posting on an old topic, but for what it's worth, I hit this error when I connected directly via MQTT with mosquitto, but forgot to include the API version in the -user .azure-devices.net//api-version=2016-11-14.

If you leave off the /api-version bit, you can connect via mosquitto and get data on the /devices//messages/devicebound topic just fine, but the device twin and direct methods don't work.