Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello BW908,
Thank you for your question. In Torizon OS 6.7 and later, the auto-provisioning-overrides.sh script allows customization of device names and IDs for registration with Torizon Cloud. If a collision occurs—meaning a device name or ID already exists in the cloud—the registration process will typically fail, as each device must have a unique identifier.
To prevent such collisions, you can append a unique suffix to the device name or ID, such as a random string or timestamp, similar to your previous method. This can be implemented within the get_device_name and get_device_id functions in your overrides script.
Currently, Torizon does not have a built-in mechanism to automatically replace an existing device entry if a collision occurs. Therefore, ensuring unique identifiers during provisioning is crucial. If you need to replace an existing entry, you would typically need to manually remove the old entry from the cloud platform before re-registering the device with the same name or ID.
By managing device identifiers carefully and ensuring their uniqueness, you can avoid registration issues and maintain a smooth provisioning process in Torizon Cloud.
Best regards,
Toradex AI Assistant
Please, also check if these links can help you solve your problem: