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

The GA edgeHub does not return connectionState #39

Closed
shizn opened this issue Jul 19, 2018 · 5 comments
Closed

The GA edgeHub does not return connectionState #39

shizn opened this issue Jul 19, 2018 · 5 comments
Labels
bug Something isn't working customer-reported iotedge

Comments

@shizn
Copy link

shizn commented Jul 19, 2018

The EdgeHub module does not return connectionState, in VS Code, we cannot visualize the module states without it.
image

Expected Behavior

By returning the connectionState, customer can visualize edgeHub module states during development.

Current Behavior

image
Always blue because no connectionState

Steps to Reproduce

  1. Expand an active IoT Edge device in VS Code and look into the module list.

Context (Environment)

Device (Host) Operating System

All

Architecture

NA

Container Operating System

All

Runtime Versions

iotedged

Edge Agent

Edge Hub

Docker

Logs

Additional Information

@darobs
Copy link
Contributor

darobs commented Jul 19, 2018

Hello @shizn,

Thank you for the report, Xin.

This is in the reported properties of the $edgeHub module twin, correct? I will mark this as a bug and put it in our back log.

@darobs darobs added the bug Something isn't working label Jul 19, 2018
@varunpuranik
Copy link
Contributor

Hi Xin,

So this behavior is because IoTHub uses the D2C telemetry link status to determine if the device is connected or now. But since the EdgeHub doesn't send any telemetry, it never opens that link. So the module shows up as disconnected.

Either of those will be hard to fix at this point. Can you use the RuntimeStatus of the module in the EdgeAgent reported properties instead? That should give you an accurate status of which modules are running and which are not.

@shizn
Copy link
Author

shizn commented Jul 20, 2018

Thanks for the information, Varun. We will take a look and use RuntimeStatus to update the status in VS Code.

@myagley
Copy link
Contributor

myagley commented Aug 24, 2018

This is related to #80

@myagley
Copy link
Contributor

myagley commented Sep 18, 2018

Closing this as it is a duplicate of #80

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working customer-reported iotedge
Projects
None yet
Development

No branches or pull requests

5 participants