Cant see IOTHubMonitor readings when monitoring device
Closed this issue · 3 comments
Issue Type: Bug
Ran through the steps in this tutorial yesterday - https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-vscode-iot-toolkit-cloud-device-messaging - and was able to see my device messages in VS Code. Today I recreated the exercise and I cannot duplicate the test. After clicking Start Monitoring Built-in Event Endpoint it creates the 4 partitions and then does not display anything in the Output window even though I can see messages being sent by the simulator and they are showing up in blob storage after being routed. Am I doing something wrong here?
Extension version: 2.12.0
VS Code version: Code 1.39.2 (6ab598523be7a800d7f3eb4d92d7ab9a66069390, 2019-10-15T15:35:18.241Z)
OS version: Windows_NT x64 10.0.17763
System Info
Item | Value |
---|---|
CPUs | Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz (4 x 2712) |
GPU Status | 2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software oop_rasterization: disabled_off protected_video_decode: enabled rasterization: enabled skia_deferred_display_list: disabled_off skia_renderer: disabled_off surface_synchronization: enabled_on video_decode: enabled viz_display_compositor: disabled_off webgl: enabled webgl2: enabled |
Load (avg) | undefined |
Memory (System) | 15.89GB (4.70GB free) |
Process Argv | |
Screen Reader | no |
VM | 0% |
@dforrestdev you can try bellow steps to see output message when monitoring device.
Steps:
- right-click one device (pi3bplus)
- start monitoring built-in event endpoint
- right-click pi3bplus again and send d2c message to IoT Hub
- click "send" button in "send d2c message" page
- check the message received in output .
if the message can be send , Monitoring Built-in Event Endpoint work well.
if you send D2C message via your program for device pi3bplus, the output message not display, maybe your program not work.
Closing due to inactivity. Please reopen this issue or create a new issue if you need more help.