EdgeX Device ONVIF Camera service fails to map credentials to devices. #347
Replies: 1 comment
-
Never mind,I use curl --location --request PUT \
'http://localhost:59890/api/v3/kvs/key/edgex/v4/device-onvif-camera/AppCustom/CredentialsMap/hik_secret' \
-H 'Content-Type: application/json' \
-d '{"value":"08:cc:81:f8:f0:e2"}' slove this problem.So complicated |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I followed the instructions in the following link to deploy EdgeX 4.0 Device ONVIF Camera:
I executed the following command:
The request completed successfully, but I still can’t access the camera. When I run a camera command from EdgeX UI, it returns:
I have confirmed that the camera supports ONVIF and that the relevant ONVIF settings have been enabled.
So I thought the issue might be because I didn’t map the credentials to the devices.
When I reached the “Map credentials to devices” step, the documentation instructed me to run the following command:
However, since Consul has been deprecated in version 4.0, I can no longer access port 8500. When I tried to use the core-keeper port instead, I got a Not Found error.
So how should I handle this step correctly in EdgeX 4.0?
Could you please help me solve this issue? Thank you!
Beta Was this translation helpful? Give feedback.
All reactions