Explore related resources

Find more information about the topics in this Learning Path:

Give feedback

How would you rate this Learning Path?

Review frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
How do I know my tenant is ready before I commission devices?
After you sign in to the Device Connect portal, a private tenant is created. You should be able to download per-device NATS credentials and use them to commission a device. If the Python client can discover that device, your tenant is ready.
Which credentials should I use on the primary and secondary devices?
Use the per-device NATS credentials you download from the portal for each specific device. Don’t reuse a single credential across multiple devices.
What result should I expect when discovery works from the Python client?
The client lists commissioned devices in your tenant and can invoke their RPCs. Successful calls confirm that routing over the Device Connect server and NATS is working across networks.
What should I check if the client cannot discover a commissioned device?
Verify the device was commissioned to the same tenant and is running with the correct NATS credentials. Also confirm the client is targeting that tenant and repeat discovery after the device is online.
How do I connect a Strands AI agent to the same tenant?
Configure the agent with the tenant details and portal-issued credentials, then start it. The agent should appear under the tenant’s namespace and discover and invoke commissioned devices such as the Python client.

Share

Tell others about this Learning Path.

Back
Return to Embedded and Microcontrollers