Amazon Developer

Console

as

Settings
Sign out
Notifications
Alexa
Amazon Appstore
Ring
AWS
Documentation
Support
Contact Us
My Cases

Console

as

Get Started
Design and Develop
Publish
Reference
Support
Skip to main content
This page provides solutions to common VDA connection and power problems when working with Fire TV devices. Each issue includes the underlying cause and step-by-step resolution instructions. If you don’t find a solution to your specific problem here, post an issue in the Developer Forum for additional support.

​
Random USB disconnection from Fire TV Stick

Symptoms:
  • Both vda devices and kepler devices list commands return empty results
  • The device becomes unresponsive and unavailable for debugging
  • Disconnecting or reconnecting temporarily resolves the issue, but the problem recurs
Cause: The Fire TV Stick randomly disconnects during debug sessions due to faulty or incompatible USB cables. Solution: Replace the USB cable with a different one. For recommended USB specifications, see Troubleshoot Fire TV Stick issues.

​
Connection or power issues

Cause: Insufficient power, faulty cables, or system power management settings interfere with device connectivity. Solution:
  • Use the original USB cable that came with your Fire TV device
  • Disable automatic sleep mode and “Selective Suspend” feature in your operating system
  • If using a USB hub, make sure it provides adequate power and avoid connecting too many devices
  • Unplug the power supply of your Fire TV device, wait a few seconds, then reconnect
  • Unplug and replug the USB port, then reconnect your Fire TV device
  • Restart your host computer and reconnect your VDA
After reconnecting the VDA, examine the issue using:

​
Undetected Fire TV device

Cause: USB hubs, virtual machines, or intermediate devices interfere with direct communication between the host and the Fire TV device. Solution:
  1. Connect your Fire TV device directly to the host computer.
  2. Remove any USB hubs or intermediate devices.
  3. Disable virtual machine (VM) or port forwarding from other hardware like the Raspberry Pi.

​
Chrome USB discovery conflicts

Cause: Chrome Developer Tools’ USB discovery feature conflicts with VDA device detection. Solution: Disable the USB discovery feature:
  1. Open Chrome Developer Tools.
  2. Navigate to Settings > Remote Devices.
  3. Deselect the “Discover USB devices” checkbox.
  4. Reconnect your Fire TV device.

​
Fire TV device doesn’t show up over TCP/IP

Cause: Network connectivity issues, incorrect IP address, or firewall blocking the connection port. Solution:
  1. Verify both devices are on the same Wi-Fi network:
    • macOS: Click the Wi-Fi icon in the menu bar to view connected network
    • Linux: Click the network icon in the system tray or run iwconfig
    • Fire TV: Go to Settings > Network/Wi-Fi to check connected network
  2. Verify the correct IP address while connected through USB:
  3. Check firewall settings and ensure the firewall doesn’t block port 5555, or temporarily disable firewall for testing.

​
Fire TV device stuck in TCP/IP mode

Cause: Device stops working after switching to TCP/IP mode and gets stuck. Solution:
  1. Perform a factory reset to revert to USB mode. This process erases all data. Back up your device settings and data.
  2. Complete the Out-of-Box Experience (OOBE) setup process.
  3. Review the requirements and steps in Enable VDA over TCP/IP before attempting TCP/IP mode again.

​
Ubuntu 64-bit compatibility issues

Cause: VDA is a 32-bit application requiring 32-bit architecture support on 64-bit Ubuntu systems. Solution:
  1. Install 32-bit shared libraries:
  2. If VDA devices show no devices, configure proper udev rules.
  3. If permission errors occur, add yourself to the plugdev group:

​
VDA server isn’t responding

Cause: VDA server process becomes unresponsive or fails to start properly. Solution:
  1. Stop the VDA server:
  2. Restart the VDA server:
  3. Check the device list:

​
TCP/IP connection fails

Cause: VDA daemon not running in TCP/IP mode, network connectivity issues, or incorrect port configuration. Error messages:
Solution:
  1. Ensure VDA daemon operates in TCP/IP mode:
  2. Verify both devices are on the same network.
  3. Kill the VDA server:
  4. Restart the VDA server:
  5. Restart your Fire TV device and attempt connection again.
  6. Try an alternative port if issues persist:

​
VDA permission issues

Cause: Insufficient system permissions prevent VDA from accessing USB devices. Error messages:
Solution:
  1. Disconnect VDA from your Fire TV device:
  2. Create permission rules:
  3. Add permissions to the rules:
  4. Restart the udev service:
  5. Restart VDA:

​
Device detection issue

Cause: The host system may not recognize the Fire TV device at the hardware level, preventing proper connection. Solution: On Linux:
  1. Run lsusb in the terminal.
  2. Look for “Lab126 Alexa” entry with your Fire TV device serial number.
On Mac:
  1. Install lsusb: brew install lsusb.
  2. Run lsusb in the terminal.
  3. Look for “Lab126 Alexa” entry with your Fire TV device serial number.
  4. Alternatively, check System Report > USB devices for “Lab126 Alexa” device.

​
Device detection fails on current host

Cause: The issue may be specific to your host system rather than the Fire TV device itself. Solution:
  1. Connect your Fire TV device to another Mac or Linux machine.
  2. Open the terminal on the alternate host.
  3. Run kepler vda devices.
  4. Check if your Fire TV device appears in the output.
Last modified on November 14, 2025