# Android TV components

**URL:** <https://discourse.nodered.org/t/android-tv-components/28661>\
**Category:** General\
**Created:** [20 June 2020 12:51 UTC](https://discourse.nodered.org/t/android-tv-components/28661 "2020-06-20T12:51:57Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![afelix](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/afelix/32/9743_2.png) [@afelix](https://discourse.nodered.org/u/afelix)\
**Post date:** [20 June 2020 12:57 UTC](https://discourse.nodered.org/t/android-tv-components/28661/3 "2020-06-20T12:57:34Z")

</div>

Sadly, not that I'm aware of. Every single brand implements their own layer for control on top of Android, and especially for connecting and controlling them it has to be reverse engineered for every single brand/model. Sometimes you're lucky and a series of TVs are compatible, but most of the time it's working from scratch. No such thing as a general Android TV control, as each manufacturer does things on their own. As for philips, it might be worth doing a general search online for `philips <model of your tv> remote reverse engineering` to see what is available. I see on that result a `pylips` library, which guessing by the name is Python based, and it says it has MQTT support, meaning you could use it next to your Node-RED install and connect to it over MQTT. And yes, it has ambilight support. I think this would be your best option.

> **[eslavnov/pylips](https://github.com/eslavnov/pylips)**
>
> Control Philips TVs (2015+) and Ambilight (+ Hue) through their reverse-engineered API (+ MQTT support!) - eslavnov/pylips

---

_[View the full topic](https://discourse.nodered.org/t/android-tv-components/28661)._