-
Notifications
You must be signed in to change notification settings - Fork 215
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
Error getting device scope result from IoTHub for OPC-UA endpoint IoT Device (Unauthorized) #831
Comments
I would recommend upgrading to 2.7.199, since we fixed some issues related to device scoping running in the transparent gateway mode for the iotedge modules. |
Hi I updated the services to 2.7.199.
I cleared IoT Edge's cache and restarted, and the edge hub still reports the error:
Any clue what I can still try? Thank you ! |
The same problem is now also happening on another device (which is running at a different location):
I thought maybe it could be the IoT Hub's message limit, but at the moment of the error it's: |
@deanwyns, can you please also send us the support bundle from this IoT Edge device ? Preferably, for at least 6 or 12 hours. It will contain the logs of all modules running on this IoT Edge device, so we can understand if OPC Publisher has started publishing telemetry or not. The warning that you are seeing is most probably cause by a non-child leaf device that is used in OPC Twin module. And while |
Will release in 2.7.2xxx some time early Jan. |
Describe the bug
The edge hub is unable to authorize the device against IoT Hub (connected OPC-UA endpoint).
To Reproduce
I am not sure how this is reproduced. IIoT gets into a state where the device is unauthorized.
We are using version 2.7.170.
Expected behavior
OPC-UA endpoint device should connect successfully and send telemetry.
Screenshots
N/A
Desktop (please complete the following information):
Not really applicable but:
Edge Hub logs
I have tried clearing IoT edge's cache and restarting the daemon but that doesn't help.
The text was updated successfully, but these errors were encountered: