Troubleshooting
Chrome doesn’t find my device
Section titled “Chrome doesn’t find my device”- Check that you’re using Chrome on macOS at
https://app.suta.dev. - Allow Chrome to use Bluetooth in System Settings > Privacy & Security > Bluetooth.
- Wait for the Pi to finish its first boot. This can take a couple of minutes.
- Close any other browser tab or terminal that is setting up the same device.
- If you reflashed the card, forget the old device in your Mac’s Bluetooth settings, then try again.
suta device add doesn’t find my device
Section titled “suta device add doesn’t find my device”- On macOS, allow your terminal app to use Bluetooth in System Settings > Privacy & Security > Bluetooth.
- For Ethernet, your computer and the Pi must be on the same network, and the network must allow mDNS. Over a direct cable, wait a little longer.
- When the 30-second scan ends, choose to scan again.
The installer stops with a conflict
Section titled “The installer stops with a conflict”The Pi already has an account or file named suta that Suta didn’t create.
Suta won’t take it over. Rename or remove it, then run the installer again.
Connection
Section titled “Connection”Device stays offline
Section titled “Device stays offline”A device is online only while it sends heartbeats. Check that:
- The Pi has power and has finished starting.
- It has internet access. On the Pi,
curl -I https://app.suta.devshould work. - The Suta agent is running:
systemctl status suta-agent.
To change its Wi-Fi, see Fix a device’s network.
Measurements look old
Section titled “Measurements look old”When a device is offline, Suta shows the last values it reported, with the time of the report. They update when the device reconnects.
Access
Section titled “Access”“Permission denied” in the dashboard or CLI
Section titled ““Permission denied” in the dashboard or CLI”Your role doesn’t include that permission. Run suta auth status to see your
permissions, and ask a workspace admin to change your role. See
Permissions.
Commands say remote access isn’t ready
Section titled “Commands say remote access isn’t ready”Open remote access first with suta device access enable <device>, then wait
until suta device access status <device> shows it’s ready.
My AI agent says it needs approval
Section titled “My AI agent says it needs approval”The agent should give you a link. Open it, review the request and select Approve access. Then tell the agent to continue. See Connect an AI agent.
A CI job gets “403” with an API token
Section titled “A CI job gets “403” with an API token”Tokens can’t open terminals, run commands or open remote access, and they can only do what their role allows. See API tokens for CI.
My AI connector keeps sending me to /oauth/authorize
Section titled “My AI connector keeps sending me to /oauth/authorize”It was set up with an older sign-in method. Remove the connector and add it
again with https://app.suta.dev/mcp.
Still stuck?
Section titled “Still stuck?”Open an issue on GitHub, with the
device ID from suta id and what you tried.