Developer Tools
Find tools for your THOX release, collect useful diagnostics and use authorized remote access.
Use tools for your THOX release
Start with the installed product
Identify the application, release and operating system before following command-line instructions. THOX device runtimes, MeshStack apps and website demos have different interfaces.
Install from the published release
Use the download or installation instructions for that product. Check the publisher and release notes; do not assume that a package with a similar name is an official THOX tool.
Use the documented commands
If the release includes a CLI, follow its command reference and built-in help. This guide does not prescribe one set of commands for every device.
Collect useful diagnostics
Record the app and operating-system versions, the action you tried, the displayed state and a sanitized error message. Remove keys, cookies, private prompts and personal file paths before sharing logs.
Keep recovery changes controlled
Read the product-specific recovery instructions before resetting a device, deleting a model or rolling back software. Preserve the settings and files you need first.
Use authorized remote access
Confirm that SSH is supported
SSH access depends on the device and deployment. Use it only when the owner or administrator has enabled it and provided the correct host, port and account.
Verify the connection
Confirm the server fingerprint through an approved channel before trusting it. Use the authentication method set up for your deployment; there is no shared THOX password to try.
Limit the access
Use an account with the permissions needed for the task. Keep private keys on the authorized client and remove access when it is no longer needed.
Avoid broad network changes
Do not expose a device through router port forwarding to solve a connection problem. Follow your deployment networking policy and the documented remote-access path.
Read the failure before retrying
Connection refused can mean the service is not listening. Permission denied points to an access problem. A timeout can indicate a route or firewall issue. Check the relevant state before changing credentials or network rules.