Vega studio not detecting physical device

Vega Open Beta Q&A
1

Hello Team,

I’m facing an issue with my Vega extension in Vega Studio. Under the devices section, it is not detecting my physical device once the device is completely loaded and ready to use.

However, it does show the device while it is loading.

Active SDK Version: 0.22.6150

Vega CLI Version: 1.2.18

Please let me know if more info is required.

Thanks & Regards,

Amit Aggrawal

3

Hi @Amit_Aggrawal,

Thank you for your question about the Vega studio not detecting physical device.

The behavior you’re describing, device visible while loading but disappearing once fully booted, typically points to a device registration or developer mode issue. Here are a few things to check:

1. Verify device registration Go to Amazon Developer Sign-In and confirm your physical device’s serial number appears in the registered devices list. The device must be registered under the same Amazon developer account you’re logged into in Vega Studio.

2. Check device connectivity from CLI Run the following in your terminal to see if the CLI detects the device independently of Vega Studio:

vega device list

If the CLI also doesn’t see the device after boot, the issue is at the connection/registration level rather than the extension.

3. Validate your SDK setup Run:

vega sdk config doctor

This will check if all SDK components are properly installed and accessible.

4. Restart everything After confirming registration, restart both the physical device and Vega Studio (or reload VS Code entirely).

The device appearing during boot but disappearing once ready suggests the Studio extension loses connection after the Vega runtime completes initialization—this is often due to registration issues or an expired developer mode token.

Let us know what you find. If these steps don’t resolve the issue, we’re happy to help with further troubleshooting.

Best regards,
Aishwarya

5

Hello Aishwarya,

Thanks for your response. I validated all the steps you mentioned.

  1. Verify device registration: My device is registered and is visible on the portal.

  2. Check device connectivity from CLI: The behaviour is similar, I can see the device while in boot state but not once fully booted.

  3. Validate your SDK setup: Ran the command and everything is proper. Attaching result for your consideration.

    amit.aggrawal@ZL-BLR-MAC398 kepler % vega sdk config doctor

SDK Configuration Doctor Results:

  Validated components: 1

  Corrupted components: 0

  Removed components: 0

  4. Restart everything: Tried multiple times. Both device and VS code entirely.

  5. I also verified `npmrc` token and it is valid.

Please let me know if there is anything else I can try. Also, if there are any logs that can help to debug the situation, let me know where I can get them and I’ll upload here.

Thanks & Regards,

Amit Aggrawal

6

Hi @Amit_Aggrawal,

Thank you for validating those steps and providing the detailed information.

Since the device appears during boot but disappears once fully booted (both in CLI and Studio), I’d like to understand more about your connection setup:

How are you connecting the physical device to your development machine?

  • Are you using USB connection?

  • Are you using network/Wi-Fi connection?

  • If USB, have you tried different USB ports or cables?

Also, could you share the output of vega device list at these two points:

  1. When the device is visible (during boot)

  2. Right after it disappears (once fully booted)

This will help us understand if there’s a connection drop or if the device is entering a different state that’s preventing detection.

Best regards,
Aishwarya

7

Hello Aishwarya,

I’m using USB connection. I have not tried with different USB cables since the device is visible during boot, but I have tried multiple USB ports, and the result remains the same.

Output of vega device list

  1. During boot:
    Found the following device:
    G4N33M0335140180 : A1TGF7GBNNZ9EE
  2. After boot: No devices found

I would also like to mention that this issue happened when I updated my SDK to 0.21.+ and the device detection was working fine till v0.20.

Another thing that I’m curious about is that I installed 0.22.6150, whereas when I go and check https://developer.amazon.com/docs/kepler-tv/install-mac-linux.html, the latest version shown is 0.20.3719.

How is this possible? I mean, am I referring to the wrong doc, or is it not updated?

Thanks & Regards,

Amit Aggrawal

9

Hello Aishwarya,

I deleted my vega SDK and downloaded kepler version 0.20.3719 thinking it will work as it was working earlier. While this alone does not resolved the issue, following this ( Fix VDA Connection and Power Issues | Vega Troubleshooting ) thread afterwards helped.

Seems it was related to ADB server connection issue. I ran kepler exec vda connect [IP_ADDRESS]:5555 and device started showing up.

Not sure if I’ll have to do it again when my IP changes for whatever reasons. Can you please guide me on how I can close this ADB connection and rely on just USB connections.

I verified by updating the vega SDK back to 0.22.6150 and my device is getting detected and working fine now.

Thanks & Regards,

Amit Aggrawal

10

Hi @Amit_Aggrawal,

Glad it’s working now! To disconnect TCP/IP and switch to USB-only:

vega exec vda disconnect [IP_ADDRESS]:5555
vega exec vda usb

Once in USB mode, IP changes won’t affect you at all.

If the detection issue ever recurs, a quick VDA server restart usually fixes it:

vega exec vda kill-server
vega exec vda start-server

For reference:

Best regards,
Aishwarya

11

Thanks Aishwarya for your help.