Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Unable to start running telemetry via v0.14.13 #541

Closed
RedDogUK opened this issue Aug 29, 2022 · 6 comments
Closed

[BUG] Unable to start running telemetry via v0.14.13 #541

RedDogUK opened this issue Aug 29, 2022 · 6 comments
Labels
bug Something isn't working In progress question Further information is requested

Comments

@RedDogUK
Copy link

Describe the bug
When clicking on start telemetry I get an error message stating "Failed to start monitoring device telemetry: [object Object]". This error goes away if downgrading the version to 0.14.12.

To Reproduce
Steps to reproduce the behaviour:

  1. Go to 'devices'
  2. Click on one of the device IDs
  3. Click on Telemetry
  4. Clock on the "Start" button
  5. See error

Expected behaviour
The app should display the telemetry of the selected device.

Desktop (please complete the following information):

  • OS: Windows
  • OS Version: 10
  • App version: 0.14.13.0
@RedDogUK RedDogUK added bug Something isn't working needs review Review required by team member labels Aug 29, 2022
@YingXue
Copy link
Member

YingXue commented Aug 30, 2022

Hi @RedDogUK
We'd like to know if this error is consistent across different hubs.
In 14.13, we rolled out a fix towards exact the issue you see, and it happens when IoT hub is having intermintent connection issue and cann't connect to it's underlying Event hub.
Unfortunately we are not able to repro this issue in any version (without the help of a broken hub), so it will be great if you can help provide this information to help us triage it.

@YingXue YingXue added question Further information is requested In progress and removed needs review Review required by team member labels Aug 30, 2022
@helloE9
Copy link

helloE9 commented Sep 1, 2022

20220901163156
I can send msg to device but can do telemetry to inquire an input.

@christiannagel
Copy link

I'm seeing the same issue with version 0.14.13. The error is consistent with monitoring.

@YingXue
Copy link
Member

YingXue commented Sep 2, 2022

We apologize for the unreadable error message. We haven't been able to fix it. With the connection string update we did in version 0.14.13, we thought that the error is mitigated.
We are still suspecting that the connection between iot hub and the underlying event hub is causing this issue. If you can follow my instructions below and verify something for us that will be greatly appreciate.
In the meanwhile, we will roll back with a fix to mitigate the issue you see, but if you can help with this verification, it will be great help!

Instructions:
Please turn on 'Use built-in event hub' toggle and fill in the two values of the event hub, and then start the telemetry monitoring and check if you are still seeing the error.
image
The two values 'connection string' and 'event hub name' can be found on Azure portal:
image

@helloE9
Copy link

helloE9 commented Sep 5, 2022

20220905101539

with Custom event hub name, I can receive the event.

@YingXue
Copy link
Member

YingXue commented Sep 6, 2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working In progress question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants