Hello @Rafael Ibanhez,
Thanks for reaching out on this forum,
We will help you on this issue!
It looks like there are several configuration issues with your Azure IoT Edge device based on the output of the iotedge check
command.
So I can think of below troubleshooting steps as an initial help on this issue!
- Check the value of the
device_connection_string
parameter in theconfig.yaml
file and make sure it is properly formatted.
Retrieve the connection string
- Check the URIs for the daemon management endpoint in the
config.yaml
file and ensure they are correct. - To get more details about the warnings and errors, you can re-run the
iotedge check
command with the--verbose
flag. - Check the config.yml file for any format issues
Here's an example config.yaml
file with a properly formatted connection string:
provisioning:
source: "manual"
device_connection_string: "HostName=myiothub.azure-devices.net;DeviceId=mydevice;SharedAccessKey=mykey"
agent:
name: "edgeAgent"
type: "docker"
env: {}
config:
image: "mcr.microsoft.com/azureiotedge-agent:latest"
auth: {}
env: {}
cmd: {}
hostname: "mydevice"
ports: {}
volumes: {}
status:
frequencySecs: 60
...
Please let us know in the below comment section if you need more help in this regard!