Torizon Cloud Device not found anymore

I have a device registered in the Torizon Cloud that was shown properly in the Dashboard yesterday. Now today I still see my devices in the device list, also as being online, but when I click on the device I get the info that the device was not found.

I am able to access the device remotely via SSH. So the device is online and internet connection is fine.

Why is that? How to resolve that?

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.


I don’t have specific information in the available sources about the exact behavior you’re experiencing where devices appear online in the device list but show “device not found” when clicked.

However, based on the Torizon Cloud API documentation, this could be related to device UUID inconsistencies or synchronization issues between different parts of the cloud platform. The API endpoints show that devices are accessed using specific UUIDs(1)(2), and if there’s a mismatch or caching issue, you might see this behavior.

Troubleshooting Steps

To help resolve this issue, could you provide more details about your setup:

  1. Platform Information: Which Torizon OS version are you running? You can check this using the tdx-info command on your device. For more details about this command, see: Getting Device Information with Tdx-Info | Toradex Developer Center

  2. Device Provisioning: Was this device recently re-provisioned or re-flashed? According to the community discussion, device registration can fail if there are conflicts with existing device IDs or names(3).

  3. Recent Changes: Did you make any changes to the device configuration, network settings, or perform any updates recently?

Potential Causes

Based on the available information, this issue could be related to:

  • Device UUID conflicts or inconsistencies
  • Synchronization delays in the cloud platform
  • Network connectivity issues affecting device registration
  • Recent device re-provisioning that may have created duplicate entries

If the device was recently re-flashed or re-provisioned with the same device ID, this could cause registration conflicts as mentioned in the community discussion(3).

For immediate assistance with this specific cloud platform issue, I recommend checking these resources:

Would you like me to provide a general approach to troubleshooting device connectivity issues if you can share more details about your specific setup?

Best regards, Toradex AI Assistant.


Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

Greetings @mbcel,

Are you still seeing this issue? On my own account I can’t reproduce it:

Is this happening only on a specific device in your account, or all devices? Does changing the internet browser make a difference?

Best Regards,
Jeremias

Actually I just checked with our Cloud team. It seems there was a server hiccup around the time you reported this. It should be resolved now though. Could you confirm that the issue is resolved on your end.

Best Regards,
Jeremias

Hi Jeremias, thanks for the info. It is working normally now again.

Glad we were able to clarify this for you.

Best Regards,
Jeremias