Hi,
2026-01-04T05:00:00Z
working with this jetson orin nano 3766
Downloaded ands installed to SD card
Dashboard does not have local access and cant enable it. what do I need to do? Thank you!
I can see the device locally
Hi, you cannot enable/disable local mode from the Summary page. You need to go to the Settings page to do so. You can see the button to navigate there in the sidebar on the left.
in settings the local mode is grayed out and says not yet provisioned.
We have a changelog in the bottom left-hand corner of the page (at the bottom of the sidebar). Which version do you see there? We had a bug with that recently and it should have been resolved in version 31.5.21
says 31.5.24
Hi @mykeylynx,
Can you enable local mode on the device using the CLI with the balena device local-mode command? See https://docs.balena.io/reference/balena-cli/latest/#device-local-mode
Thank you here is the debug output from the Cli.
sudo balena device local-mode 448fe5e --enable --debug
[debug] new argv=[/Users/michael/.local/share/balena-cli/client/23.2.14-df95136/bin/node,/Users/michael/.local/share/balena-cli/client/23.2.14-df95136/bin/run,device:local-mode,448fe5e,–enable] length=5
[debug] Deprecation check: 6.40596 days since last npm registry query for next major version release date.
[debug] Will not query the registry again until at least 7 days have passed.
[debug] Event tracking error: Timeout awaiting ‘response’ for 0ms
Device is not yet fully provisioned
Error: Device is not yet fully provisioned
at checkLocalModeSupported (/Users/michael/.local/share/balena-cli/client/23.2.14-df95136/node_modules/balena-sdk/es2018/util/local-mode.js:18:15)
at Object.enableLocalMode (/Users/michael/.local/share/balena-cli/client/23.2.14-df95136/node_modules/balena-sdk/es2018/models/device.js:1230:54)
at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
at async DeviceLocalModeCmd.run (/Users/michael/.local/share/balena-cli/client/23.2.14-df95136/build/commands/device/local-mode.js:10:13)
at async DeviceLocalModeCmd.\_run (/Users/michael/.local/share/balena-cli/client/23.2.14-df95136/node_modules/@oclif/core/lib/command.js:182:22)
at async Config.runCommand (/Users/michael/.local/share/balena-cli/client/23.2.14-df95136/node_modules/@oclif/core/lib/config/config.js:456:25)
at async run (/Users/michael/.local/share/balena-cli/client/23.2.14-df95136/node_modules/@oclif/core/lib/main.js:97:16)
at async /Users/michael/.local/share/balena-cli/client/23.2.14-df95136/build/app.js:73:13
at async Promise.all (index 2)
at async oclifRun (/Users/michael/.local/share/balena-cli/client/23.2.14-df95136/build/app.js:108:5)
For further help or support, visit:
https://www.balena.io/docs/reference/balena-cli/#support-faq-and-troubleshooting
Hi,
Based on your original screenshot, the reason that local mode is disabled on our dashboard & isn’t settable via the balena-cli, is that the device hasn’t yet reported its OS version & variant and supervisor version.
That means that the supervisor of the devices hadn’t yet ever reached our backend, and as a result the device is considered not yet fully provisioned.
Do you face the same issue after provisioning a different new device. If so, do you also face the issue when provisioning devices of other device types as well?
Kind regards,
Thodoris
Should I just create a new account?
Same result with a new account. I will try opening up the firewall.