search

Azure / azure-iot-explorer

Cross-platform UI for interacting with devices attached to Azure IoT Hub. This tool is meant for learning and testing, not for production environment.
MIT License
220 stars 70 forks source link

Telemetry from device that has NOT been selected. #635

Open codeputer opened 11 months ago

codeputer commented 11 months ago

Describe the bug Start Telemetry from a device (in my case GFSDev002), and I'm getting telemetry from device GFSDev001.

To Reproduce Each device has its own connection string. image

Expected behavior Starting telemetry for GFSDev002, should only show Telemetry sent by GFSDev002.

Screenshots image

Desktop (please complete the following information):

Additional context I'm thinking the IOT Explorer is subscribing to the Consumer Group, rather than the device? If so, then the title is confusing as it clearly states it Telemetry from GFSDev002.

tverschoof-axians commented 11 months ago

I've had this happening to me as well. Steps to reproduce:

  1. Listen to device A's Telemetry
  2. Instead of pressing "Stop", return to the "Devices" list
  3. Start listening to device B's Telemetry

Result: device A's telemetry is shown in between device B's telemetry.

Suspect: Forgot to unsubscribe from telemetry after navigating away from a device's telemetry page?

Workaround: Always remember to press "Stop" before returning to the devices list for now

codeputer commented 11 months ago

Seen this happen many times, but didn't realize the sequence of events to cause it. This is definitely a bug!

bmasotta-lcg commented 8 months ago

same here

YingXue commented 3 months ago

Event hub does not support filtering on device. Yes we can only subscribe to the Consumer Group like @codeputer you've pointed out. We do unsubscribe when the component unmount (when the page closes), but there will be a lag. As long as the telemetry won't keep showing after about 10s, we will not able to fix this issue due the constraints we face.