Skip to main content

Atym Hub Troubleshooting

This section covers common issues and solutions related to the Atym Hub, including device connectivity, authentication, and container management problems.

Connection Issues​

Device connection problems are among the most common issues when working with the Atym Hub. This section covers troubleshooting steps for devices that fail to connect.

Device Not Showing "Client connected." Message​

If your device is not displaying the "Client connected." message after reboot, follow these troubleshooting steps:

1. Check Device Configuration on Board​

Verify that the configuration on your actual device is correct. On your device console, run:

atym config show

Carefully verify the following values match what you expect:

  • deviceUUID: Should match the deviceUUID returned when you added the device to the Hub
  • pskSecret: Should match the pskSecret value returned when you added the device to the Hub
  • tenantID: Should match your tenantID from atym show config on your development machine
  • server/endpoint: Should be set to coapgw.prod.atym.io
  • server/port: Should be set to 5684

If any of these values are incorrect, update them using the atym config set command on your device and then press the reset button to apply the configuration.

2. Test DNS Resolution​

Ensure DNS is working on your network, as the device cannot connect to the Hub without proper DNS resolution. On your device console, run:

net ping coapgw.prod.atym.io

If you see "Invalid IP Address" or other related output in the response, this indicates a DNS resolution problem.

Resolution:​

Fix DNS issues on your network or move to a different network that has proper DNS resolution. After making any configuration changes, restart your device and wait 5-10 seconds for the connection to establish.