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
Comments
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. |
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. |
Thanks for the information, Varun. We will take a look and use RuntimeStatus to update the status in VS Code. |
This is related to #80 |
Closing this as it is a duplicate of #80 |
The EdgeHub module does not return connectionState, in VS Code, we cannot visualize the module states without it.
Expected Behavior
By returning the connectionState, customer can visualize edgeHub module states during development.
Current Behavior
Always blue because no connectionState
Steps to Reproduce
Context (Environment)
Device (Host) Operating System
All
Architecture
NA
Container Operating System
All
Runtime Versions
iotedged
Edge Agent
Edge Hub
Docker
Logs
Additional Information
The text was updated successfully, but these errors were encountered: