Deploy device meshes with Device Connect and NATS
Introduction
Learn when to use Device Connect server for multi-network deployments
Run devices and an orchestrating agent on a Device Connect server
Next Steps
Deploy device meshes with Device Connect and NATS
Review frequently asked questions
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.
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.
Use the per-device NATS credentials you download from the portal for each specific device. Don’t reuse a single credential across multiple devices.
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.
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.
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.