The Android TV integration provides control over Android TV devices through the Android Debug Bridge (ADB) protocol. It enables power control, app detection, media playback tracking, and remote control commands for Android TV boxes, smart TVs, and streaming devices.
This integration is the older ADB-based approach (the newer Android TV Remote integration is generally preferred). It requires enabling developer mode and ADB debugging on the Android TV device, then connecting from Home Assistant over the network.
HA DocumentationHow Android Debug Bridge Works with Home Assistant
Getting Android Debug Bridge connected to Home Assistant and running reliably.
Discover & connect
Home Assistant discovers Android Debug Bridge media devices on your network automatically. Add them to see playback controls, volume, source selection, and grouping options.
Multi-room audio
Group Android Debug Bridge speakers with devices from other brands for synchronized whole-home audio. Control each room independently or as zones.
Event-driven media
Build automations that play specific audio based on events — doorbell rings, morning alarms, or custom announcements. Route different media to different rooms.
Common Android Debug Bridge Issues
The problems installers run into with Android Debug Bridge and Home Assistant — and how a managed setup prevents them.
ADB authentication requirements
ADB connections require RSA key authentication. The initial connection prompts an on-screen confirmation dialog on the TV, and keys can be invalidated by factory resets or ADB setting changes.
Conflict with Android TV Remote integration
Running both the ADB-based Android TV integration and the newer Android TV Remote integration simultaneously causes duplicate entities, state conflicts, and increased network traffic.
Developer mode security implications
Enabling ADB debugging on an Android TV opens a network port that could be exploited if the device is accessible from untrusted networks. Proper network segmentation is essential.
Why installers choose managed Android TV setups
- Single integration strategy selected per device to avoid conflicts
- ADB debugging secured with proper network segmentation
- Reliable power and input switching configured per device model
Android Debug Bridge devices we deploy
Hardware from the Selora catalog that runs on this integration. Every unit is tested and supported as part of a managed installation.
TVs & Streaming
9 devices
Fire TV Cube (3rd Gen)
The Fire TV Cube is Amazon's flagship streaming player, with wired Ethernet, Wi-Fi 6E, and hands-free Alexa. Home Assistant controls it locally over ADB through the androidtv integration: power, volume, app launch, and playback state, so it can anchor playback-aware lighting, doorbell pauses, and bedtime shutdown in the media room.
Fire TV Stick 4K Max (2nd Gen)
The Fire TV Stick 4K Max is Amazon's most powerful streaming stick, with Wi-Fi 6E and 4K Dolby Vision output. Home Assistant controls it locally over ADB through the androidtv integration: power, volume, app launch, and playback state, bringing any TV it is plugged into within reach of playback-aware scenes and bedtime routines.
Fire TV Stick 4K Plus
The Fire TV Stick 4K Plus is Amazon's current mainstream 4K stick with Wi-Fi 6. It still runs Fire OS, so Home Assistant controls it locally over ADB through the androidtv integration: power, volume, app launch, and playback state, a low-cost way to make an existing TV automation-ready.
F8D Series
The TCL F8D (2026) is TCL's budget QLED with Fire TV built in, sold from 50 to 98 inches on Amazon. Like every Fire OS set it is reachable from Home Assistant only over ADB through the androidtv integration, which works but needs the developer-options pairing kept in mind at handover.
QM64L Series
The TCL QM64L (2026) is TCL's QD-Mini LED set with Fire TV built in, sold exclusively through Amazon. The panel is close to the QM8L, but the platform is not: Fire OS has no Android TV Remote support, so Home Assistant reaches it only through the ADB-based androidtv integration.
QM6K Series
The TCL QM6K is TCL's entry QD-Mini LED Google TV, the cheapest set in the range that still gets full local control. Home Assistant pairs with it over androidtv_remote for power, volume, and app launch, which is enough to fold a guest room or basement TV into all-off and movie-night automations without a streaming player.
QM7L Series
The TCL QM7L (2026) is the mid-range SQD-Mini LED set, sold from 55 to 98 inches. Google TV underneath means the local androidtv_remote integration controls it exactly like the QM8L above it: power, volume, app launch, and key presses over the LAN, which makes it the value pick for secondary rooms on a Selora system.
QM8L Series
The TCL QM8L (2026) is TCL's mainstream SQD-Mini LED flagship and the model we specify most often from the brand. It runs Google TV, so Home Assistant pairs with it locally through androidtv_remote and gets power, volume, app launch, and D-pad control as a media_player and remote, with no TCL account in the path.
RM9L Series
The TCL RM9L (2026) is TCL's first RGB Mini-LED television, an 85 to 115 inch halo set built for dedicated media rooms. It runs the same Google TV platform as the rest of the range, so the local androidtv_remote integration gives Home Assistant power, volume, app launch, and remote key control without touching TCL's cloud.
Frequently Asked Questions
More Audio & Media Integrations
Ready to Install Android Debug Bridge Professionally?
Stop troubleshooting Android Debug Bridge integration issues. Let Selora handle the setup, monitoring, and maintenance so you can focus on your clients.