External integration - Android TV Remote

[guim31]

I can’t stop now … I also started an Android TV Remote integration.

It allows you to connect and control Android TV and Google TV televisions and set-top boxes (Nvidia Shield, Chromecast with Google TV, Sony, Xiaomi Mi Box, TCL, etc.) directly on your local network.

---

Key Features

• Native Remote v2 Protocol (TLS): Secure connection on ports 6466/6467. No need to enable developer mode or ADB on the TV.
• Easy Pairing with PIN Code: Guided 2-step procedure directly in the Gladys interface (PIN code displayed on the TV screen).
• Real-Time Status Feedback: Instant feedback in Gladys of the on/off status, volume level, and mute status.
• Multi-TV Management: Pair and control multiple televisions independently.
• Full Control:
  • Power On/Off switch
  • Volume and Mute management
  • Navigation Buttons (D-Pad): Up, Down, Left, Right, OK, Back, Home, Menu
  • Media Buttons: Play, Pause, Stop, Previous, Next, Fast Forward, Rewind
• Application Shortcuts (Optional): Direct launch of your favorite apps (Netflix, YouTube, Prime Video, Disney+, Spotify, Plex, Arte, Molotov, myCANAL). An option in the settings allows you to disable them if you want to clean up your device card.

---

Ergonomics & Usage Tips (Scenes)

Note on Dashboard Display:
Gladys Assistant currently does not have a dedicated « Remote / Media Player » widget with a visual directional pad, so the device appears as the generic « Devices » widget (vertical list of buttons).

For smooth daily use, it is highly recommended to use Gladys Scenes:

• Create scenes for your key actions (« Turn on TV », « Movie Mode », « Pause », « Launch Plex »).
• Place Scene cards/buttons on your Gladys dashboard to trigger these actions properly in one click.
• For quick manual navigation in TV menus (browsing the Netflix catalog, typing text), the official Google TV app or the physical remote control remains the ideal companion.

---

Examples of Gladys Scenes

• Movie Mode: Turn on the TV + set volume to 20% + dim the living room lighting.
• Departure / Night Mode: Automatically turn off the TV when the house switches to away or night mode.
• Automatic Pause: Pause the TV when a call or connected doorbell is detected.

---

Installation & Configuration

1. Add the external integration to your Gladys Assistant instance:

   https://github.com/guim31/gladys-integration-android-tv-remote
   

2. Go to Integrations > Android TV Remote:
   • Step 1: Enter the IP address of your TV and launch the action. A 6-digit PIN code is displayed on the TV.
   • Step 2: Enter the PIN code and validate.
3. Launch a Device Search in the Discovery tab to add the TV to your devices.

---

Links & Source Code

• GitHub Repository: guim31/gladys-integration-android-tv-remote

I remind you that I am not a professional developer, I trust AI because I don’t have the skills to understand everything. Don’t hesitate to tell me if something is wrong or missing … !

[pierre-gilles]

You can’t stop us now! Welcome to the developer side, and don’t worry in the age of AI, the only thing that matters is motivation The technique is perfectly handled by Claude

[jean_bruder]

Good evening @guim31

Thank you for this integration that I just tested… and for which I am stuck at the moment of entering the IP address:

Integration status:

When I refresh the Gladys integrations page:

However, the container is indeed started:

I do not understand, however, why it cannot connect to Gladys via WS://gladys:8082, as the port is indeed available and listening:

Thanks in advance for your feedback,

Jean

[guim31]

Good evening Jean, thank you for the detailed feedback!
Good news: the integration itself is not the issue.
Your logs show that the container cannot open the WebSocket to Gladys (connect ETIMEDOUT 172.30.0.2:8082) — it therefore never managed to register, hence the action failure and the toggle that resets.

An ETIMEDOUT (and not « connection refused ») means that the packets are discarded along the way: this is typically a network problem between the two containers, not a port issue.

To check:

1. Compare the networks of the two containers:

docker inspect -f '{{json .NetworkSettings.Networks}}' <gladys-container> | jq
docker inspect -f '{{json .NetworkSettings.Networks}}' gladys-ext-guim31-gladys-integration-android-tv-remote | jq 

If they do not share any network (different subnets), that is the cause: Docker isolates the bridges from each other.

2. Test from the integration container:

docker exec gladys-ext-guim31-gladys-integration-android-tv-remote wget -qO- --timeout=5 http://gladys:8082 || echo KO 

3. How did you install Gladys?
   The official installation runs the Gladys container in network_mode: host — this is the expected configuration for external integrations. According to your capture, your Gladys is running in bridge (IP 172.30.0.2, mapping 8082:8082): if that is the case, switching back to host network should solve the problem.

4. If the networks are fine, check the host/NAS firewall (ufw, firewalld…), which may block inter-container traffic.

Let me know what points 1 and 3 yield — and as soon as the connection goes through, the integration will connect on its own (it retries continuously), no need to restart it.

[jean_bruder]

Hello @guim31

Thanks for your reply, here is already the result of your question 1:

Answer to question 2:

And to question 3:

The Gladys container was restarted after being modified so that the network is indeed of type « host ».

Despite this, the container still cannot connect to the WS:

I remain at your disposal and thank you in advance for your help,

Have a nice end of the morning,

Jean

[guim31]

Thanks, your screenshots confirm everything!

(if you could copy/paste logs next time, it would be easier to exploit than with screenshots )

Look at your logs: the error is no longer ETIMEDOUT but getaddrinfo ENOTFOUND gladys — the name gladys is no longer resolved.
This makes sense: before, this name was an alias for the Gladys container on the gladys-integrations network; by switching to host network, your Gladys container left this network and the alias disappeared. And the counter (« attempt 753 ») shows that the integration container has not been recreated since your switch: it is still running with the connection configuration generated for the old topology — it is frozen at the creation of the container, a restart does not regenerate it.

So:

1. In Gladys → Integrations → Android TV Remote → Supervision → « Force update » (this button recreates the container, that’s what we want). Failing that: uninstall/reinstall the integration.
2. Then check the logs: you should see either the connection being established, or at least a new target (no longer ws://gladys:8082 towards a dead name).
3. If it still fails, two tests to decide:
   • from the container: docker exec gladys-ext-guim31-gladys-integration-android-tv-remote wget -qO- --timeout=5 http://172.30.0.1:8082 (172.30.0.1 = your host seen from the bridge — this tests reachability by bypassing DNS);
   • on the host: ss -tlnp | grep 8082 (check that Gladys is listening on all interfaces and not just 127.0.0.1).
     If the first fails while the second is good, it’s your firewall that blocks the bridge → host traffic on 8082 (with ufw: sudo ufw allow from 172.30.0.0/24 to any port 8082).

Keep me posted after the « Force update »!

[jean_bruder]

Hi again @guim31

Following all your instructions, everything is now working perfectly in terms of integration: TV connected

Thanks to you, I will now play with this integration: if possible, add something to control the TV from the Gladys interface (from my smartphone/tablet in the living room) and define scenes to limit its use during the day for mini-me

Have a great day,

Jean

[guim31]

Awesome!

I think that as long as we don’t have a « remote control » type widget, the main thing is the scenes

[jean_bruder]

Hi again @guim31

I’m taking the liberty of providing some more feedback, which may be useful for making corrections and improvements that will benefit everyone

When the TV is turned off, the integration keeps trying to contact it:

Also, if the TV is off and you try to interact with the integration interface, errors appear:

Also, if I add a « TV (Power) » button to a dashboard and try to turn on the TV, the integration again starts a long series of unsuccessful connection attempts…

Have a nice evening,

Jean

[AlexTrovato]

Great initiative! I have an Android TV box at home, I’m willing to test.

Analyzed with the help of Claude (AI), reviewed and approved by me.

[guim31]

Hello @jean_bruder!! I’m so sorry, I didn’t see your message!

Thank you so much for these detailed feedbacks, with screenshots — that’s exactly what we need to fix it.

Good news: the three issues actually came from the same cause, and it’s fixed.

What was happening: the library that manages the Android TV protocol restarts the connection every second, indefinitely, as soon as the TV is unreachable. TV turned off = logs flooded with EHOSTUNREACH (your first screenshot) and network continuously solicited. As a bonus, it masks connection errors, so pressing « Power » from a dashboard remained stuck for long seconds before failing… and restarting the loop behind.

What changes:

• When the TV is turned off, the integration calms down: it retries in the background with a delay that doubles with each failure (5 s, 10 s, 20 s… capped at 2 minutes). As soon as the TV becomes reachable again (turned back on, network wake-up), it is automatically resumed and the rhythm starts over from zero. No more flood of logs.
• Pressing « Power » (or any command) with the TV turned off attempts an immediate connection and fails cleanly in 2-3 seconds with a clear message, instead of staying stuck. A quick reminder: the Remote v2 protocol can only wake up a TV in network standby — a TV completely powered off must be turned back on with the remote or via HDMI-CEC.
• Removing the device in Gladys now also cuts its connection and its retries on the integration side.

Regarding the error « when deleting this device » (your second screenshot): this message comes from the core of Gladys, not from the integration. The fix removes the most likely cause, but if you see it again TV turned on after the update, don’t hesitate to let me know with the logs — it would then need to be investigated on the Gladys side.

The fix is published: update the integration to version 1.0.5 (or :latest) and restart the container.

Have a great day, and thank you again for your feedback

[spenceur]

I can’t find this integration on Gladys
Did you forget the topic?

No way to do a network search to see Android TVs?
On LG I use SSDP to search the network

[spenceur]

Couldn’t you have a dynamic select like for LG for the apps to launch?

LG side:

Otherwise, no push on the apps so we can’t launch them and the rest I’ll do my tests as I go along

My mibox is running and the power is at 0 in the interface ^^.
Can’t we get the status? Maybe a simple ping?

[guim31]

Absolutely! I had forgotten the topic ^^ thanks!

I’ll check for your return

[guim31]

Re @spenceur ,

The three points are addressed, it’s available in 1.1.0

The application selector: The buttons per application are replaced by a single « Application » selector, usable from the dashboard and the scenes. And that also explains your « no push »: the old buttons were declared in a category that Gladys treats as a sensor (like a Zigbee button that sends clicks), so nothing was clickable — the selector fixes that. The current app even displays as selected when the TV reports it. After the update: restart a device search and click « Update » on your MiBox to get the selector.

Power at 0 for turned-on MiBox: The MiBox never announces its power state, unlike TVs. I implemented your ping idea: an unreachable TV is marked as off, and a device that accepts the connection without announcing its state is considered on after 5 s. Your MiBox should therefore go to 1 as soon as the next connection.

Cherry on top: If you provide the MAC address of your MiBox (new action « Provide the MAC address of a paired TV »), « Turn on » will send a Wake-on-LAN when it is completely off.

[spenceur]

Some feedback.
I had to uninstall the integration and reinstall it to get my TV back (I had no update proposal.

Great for app selection but I have apps in the list that I don’t have and others that are not present

Other info, WOL doesn’t work (what address do you send to? To the TV? Or to x.x.x.255?):

The logs with a couple of weird things

Gladys Assistant
Android TV Remote
Devices
Discovery
Configuration
Supervision
Logs
Logs
[2026-08-17T16:47:23.419Z] [INFO] [gladys-sdk] connected to Gladys (http://172.30.0.1:8455)
[2026-08-17T16:47:23.456Z] [INFO] [AndroidTV] Integration started
[2026-08-17T16:47:43.623Z] [INFO] [AndroidTV] Running action: start_pairing
[2026-08-17T16:47:43.624Z] [INFO] [AndroidTV] Initiating pairing sequence with TV at 192.168.1.128...
Start Pairing Connect
Error: connect ECONNREFUSED 192.168.1.128:6467
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '192.168.1.128',
  port: 6467
}
192.168.1.128 Pairing Connection closed true
false
[2026-08-17T16:50:36.847Z] [INFO] [AndroidTV] Running action: start_pairing
[2026-08-17T16:50:36.848Z] [INFO] [AndroidTV] Initiating pairing sequence with TV at 192.168.1.57...
Start Pairing Connect
192.168.1.57 Pairing connected
192.168.1.57 Pairing secure connected 
Receive : 7,8,2,16,200,1,90,0
Receive : {"protocolVersion":2,"status":"STATUS_OK","pairingRequestAck":{}}
Receive : 16,8,2,16,200,1,162,1,8,18,4,8,3,16,6,24,1
Receive : {"protocolVersion":2,"status":"STATUS_OK","pairingOption":{"outputEncodings":[{"type":"ENCODING_TYPE_HEXADECIMAL","symbolLength":6}],"preferredRole":"ROLE_TYPE_INPUT"}}
Receive : 8,8,2,16,200,1,250,1,0
Receive : {"protocolVersion":2,"status":"STATUS_OK","pairingConfigurationAck":{}}
[2026-08-17T16:50:37.882Z] [INFO] [AndroidTV] PIN code displayed on the screen of the TV at 192.168.1.57.
[2026-08-17T16:50:59.437Z] [INFO] [AndroidTV] Running action: submit_pin
[2026-08-17T16:50:59.438Z] [INFO] [AndroidTV] Submitting PIN code to TV at 192.168.1.57...
Sending code :  1EAF7B
Receive : 42,8,2,16,200,1,202,2,34,10,32,30,35,42,82,32,208,136,221,246,38,107,114,167,70,149,177,3,204,230,48,75,245,33,202,214,129,211,176,30,183,34,224
Receive : {"protocolVersion":2,"status":"STATUS_OK","pairingSecretAck":{"secret":"HiMqUiDQiN32Jmtyp0aVsQPM5jBL9SHK1oHTsB63IuA="}}
192.168.1.57 Paired!
192.168.1.57 Pairing Connection closed false
Start Remote Connect
192.168.1.57 Remote secureConnect
192.168.1.57 Receive : {"remoteConfigure":{"code1":639,"deviceInfo":{"model":"MIBOX4","vendor":"Xiaomi","unknown1":1,"unknown2":"9","packageName":"com.google.android.tv.remote.service","appVersion":"6.9.906821247"}}}
Create Remote {"remoteConfigure":{"code1":622,"deviceInfo":{"model":"Docker Container","vendor":"Synology","unknown1":1,"unknown2":"1","packageName":"androitv-remote","appVersion":"1.0.0"}}}
Sending {"remoteConfigure":{"code1":622,"deviceInfo":{"model":"Docker Container","vendor":"Synology","unknown1":1,"unknown2":"1","packageName":"androitv-remote","appVersion":"1.0.0"}}}
[2026-08-17T16:51:00.813Z] [INFO] [AndroidTV] Remote session ready with 192.168.1.57
[2026-08-17T16:51:00.816Z] [INFO] [AndroidTV] Pairing with 192.168.1.57 succeeded, certificate obtained.
192.168.1.57 Receive : {"remoteSetActive":{}}
Create Remote {"remoteSetActive":{"active":622}}
Sending {"remoteSetActive":{"active":622}}
192.168.1.57 Receive : {"remoteStart":{"started":true}}
192.168.1.57 Receive : {"remoteSetVolumeLevel":{"unknown1":11,"unknown2":9,"playerModel":"MIBOX4","unknown4":1}}
192.168.1.57 Receive : {"remoteImeKeyInject":{"appInfo":{"appPackage":"com.google.android.tvlauncher"}}}
[2026-08-17T16:51:29.269Z] [INFO] [AndroidTV] Running action: set_mac
[2026-08-17T16:51:37.047Z] [INFO] [AndroidTV] Running action: test_connection
[2026-08-17T16:51:57.806Z] [INFO] [AndroidTV] Scan requested, publishing discovered devices
[2026-08-17T16:51:57.822Z] [INFO] [AndroidTV] Publishing 1 paired TV(s).
[2026-08-17T16:53:36.787Z] [INFO] [AndroidTV] Set value <- ext:ext-guim31-gladys-integration-android-tv-remote:tv:192_168_1_57:app = plex
[2026-08-17T16:53:36.788Z] [INFO] [AndroidTV] Opening app plex:// on 192.168.1.57
Create Remote {"remoteAppLinkLaunchRequest":{"appLink":"plex://"}}
Sending {"remoteAppLinkLaunchRequest":{"appLink":"plex://"}}
192.168.1.57 Receive : {"remoteImeKeyInject":{"appInfo":{"appPackage":"com.plexapp.android"}}}
[2026-08-17T16:53:47.593Z] [INFO] [AndroidTV] Set value <- ext:ext-guim31-gladys-integration-android-tv-remote:tv:192_168_1_57:app = spotify
[2026-08-17T16:53:47.593Z] [INFO] [AndroidTV] Opening app spotify:// on 192.168.1.57
Create Remote {"remoteAppLinkLaunchRequest":{"appLink":"spotify://"}}
Sending {"remoteAppLinkLaunchRequest":{"appLink":"spotify://"}}
192.168.1.57 Receive : {"remoteError":{"value":true,"message":{"remoteAppLinkLaunchRequest":{"appLink":"spotify://"}}}}
[2026-08-17T16:53:47.784Z] [ERROR] [AndroidTV] Protocol error reported by 192.168.1.57: RemoteError {
  value: true,
  message: RemoteMessage {
    remoteAppLinkLaunchRequest: RemoteAppLinkLaunchRequest { appLink: 'spotify://' }
  }
}
192.168.1.57 Remote Connection closed  false
[2026-08-17T16:53:47.788Z] [WARN] [AndroidTV] Connection closed for 192.168.1.57
[2026-08-17T16:53:52.792Z] [INFO] [AndroidTV] Connecting to 192.168.1.57..
```.
Start Remote Connect
192.168.1.57 Remote secureConnect
192.168.1.57 Receive : {"remoteConfigure":{"code1":639,"deviceInfo":{"model":"MIBOX4","vendor":"Xiaomi","unknown1":1,"unknown2":"9","packageName":"com.google.android.tv.remote.service","appVersion":"6.9.906821247"}}}
Create Remote {"remoteConfigure":{"code1":622,"deviceInfo":{"model":"Docker Container","vendor":"Synology","unknown1":1,"unknown2":"1","packageName":"androitv-remote","appVersion":"1.0.0"}}}
Sending {"remoteConfigure":{"code1":622,"deviceInfo":{"model":"Docker Container","vendor":"Synology","unknown1":1,"unknown2":"1","packageName":"androitv-remote","appVersion":"1.0.0"}}}
[2026-08-17T16:53:53.968Z] [INFO] [AndroidTV] Remote session ready with 192.168.1.57
192.168.1.57 Receive : {"remoteSetActive":{}}
Create Remote {"remoteSetActive":{"active":622}}
Sending {"remoteSetActive":{"active":622}}
192.168.1.57 Receive : {"remoteStart":{"started":true}}
192.168.1.57 Receive : {"remoteSetVolumeLevel":{"unknown1":11,"unknown2":9,"playerModel":"MIBOX4","unknown4":1}}
192.168.1.57 Receive : {"remoteImeKeyInject":{"appInfo":{"appPackage":"com.plexapp.android"}}}
[2026-08-17T16:53:56.394Z] [INFO] [AndroidTV] Set value <- ext:ext-guim31-gladys-integration-android-tv-remote:tv:192_168_1_57:app = netflix
[2026-08-17T16:53:56.394Z] [INFO] [AndroidTV] Opening app https://www.netflix.com/title on 192.168.1.57
Create Remote {"remoteAppLinkLaunchRequest":{"appLink":"https://www.netflix.com/title"}}
Sending {"remoteAppLinkLaunchRequest":{"appLink":"https://www.netflix.com/title"}}
192.168.1.57 Receive : {"remoteImeKeyInject":{"appInfo":{"appPackage":"com.netflix.ninja"}}}
[2026-08-17T16:54:07.498Z] [INFO] [AndroidTV] Set value <- ext:ext-guim31-gladys-integration-android-tv-remote:tv:192_168_1_57:key:home = 1
[2026-08-17T16:54:07.499Z] [INFO] [AndroidTV] Sending keycode 3 (home) to 192.168.1.57
Create Remote {"remoteKeyInject":{"keyCode":3,"direction":3}}
Sending {"remoteKeyInject":{"keyCode":"KEYCODE_HOME","direction":"SHORT"}}
192.168.1.57 Receive : {"remoteImeKeyInject":{"appInfo":{"appPackage":"com.google.android.tvlauncher"}}}
[2026-08-17T16:55:27.370Z] [INFO] [AndroidTV] Set value <- ext:ext-guim31-gladys-integration-android-tv-remote:tv:192_168_1_57:power = 0
[2026-08-17T16:55:27.370Z] [INFO] [AndroidTV] Sending keycode 26 (power) to 192.168.1.57
Create Remote {"remoteKeyInject":{"keyCode":26,"direction":3}}
Sending {"remoteKeyInject":{"keyCode":"KEYCODE_POWER","direction":"SHORT"}}
192.168.1.57 Receive : {"remoteStart":{"started":true}}
192.168.1.57 Receive : {"remoteStart":{"started":false}}
[2026-08-17T16:55:42.567Z] [INFO] [AndroidTV] Set value <- ext:ext-guim31-gladys-integration-android-tv-remote:tv:192_168_1_57:app = disneyplus
[2026-08-17T16:55:42.567Z] [INFO] [AndroidTV] Opening app https://www.disneyplus.com on 192.168.1.57
Create Remote {"remoteAppLinkLaunchRequest":{"appLink":"https://www.disneyplus.com"}}
Sending {"remoteAppLinkLaunchRequest":{"appLink":"https://www.disneyplus.com"}}
[2026-08-17T16:55:50.170Z] [INFO] [AndroidTV] Set value <- ext:ext-guim31-gladys-integration-android-tv-remote:tv:192_168_1_57:power = 1
[2026-08-17T16:55:50.170Z] [INFO] [AndroidTV] Sending keycode 26 (power) to 192.168.1.57
Create Remote {"remoteKeyInject":{"keyCode":26,"direction":3}}
Sending {"remoteKeyInject":{"keyCode":"KEYCODE_POWER","direction":"SHORT"}}
timeout
192.168.1.57 Remote Connection closed  false
[2026-08-17T16:56:00.179Z] [WARN] [AndroidTV] Connection closed for 192.168.1.57
[2026-08-17T16:56:05.181Z] [INFO] [AndroidTV] Connecting to 192.168.1.57...
Start Remote Connect
[2026-08-17T16:56:08.408Z] [INFO] [AndroidTV] Set value <- ext:ext-guim31-gladys-integration-android-tv-remote:tv:192_168_1_57:power = 0
[2026-08-17T16:56:08.409Z] [INFO] [AndroidTV] No live session with 192.168.1.57, trying to reconnect...
[2026-08-17T16:56:08.409Z] [INFO] [AndroidTV] Connecting to 192.168.1.57...
[2026-08-17T16:56:09.313Z] [INFO] [AndroidTV] Set value <- ext:ext-guim31-gladys-integration-android-tv-remote:tv:192_168_1_57:power = 1
[2026-08-17T16:56:09.313Z] [INFO] [AndroidTV] No live session with 192.168.1.57, trying to reconnect...
[2026-08-17T16:56:09.313Z] [INFO] [AndroidTV] Connecting to 192.168.1.57...
Start Remote Connect
192.168.1.57 Remote Connection closed  true
[2026-08-17T16:56:14.137Z] [INFO] [AndroidTV] Waking the TV at 192.168.1.57 with a magic packet to 24:18:c6:5a:1b:7e...
192.168.1.57 Error: connect EHOSTUNREACH 192.168.1.57:6466
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16) {
  errno: -113,
  code: 'EHOSTUNREACH',
  syscall: 'connect',
  address: '192.168.1.57',
  port: 6466
}
EHOSTUNREACH
[2026-08-17T16:56:19.218Z] [INFO] [AndroidTV] Connecting to 192.168.1.57...

[guim31]

Android TV Remote — version 1.2.0

Thanks @spenceur for the detailed feedback and logs, the three issues are fixed

Fixed

• Launching an app not installed on the TV: The TV refused to open (remoteError) and cut the connection, but Gladys displayed a success. The error is now clearly reported (« application probably not installed »).
• Wake-on-LAN: The magic packet was only sent to 255.255.255.255, which many networks do not deliver. It is now sent to the subnet broadcast of the TV (e.g., 192.168.1.255), then as a fallback to 255.255.255.255 and the TV’s IP.
• Update not offered: Issue with publishing the image fixed, future versions will arrive normally.

New

• « Hide Apps »: Removes apps that your TV doesn’t have from the selector. Ex: Spotify, Arte
• « Custom Apps »: Add your own, in the form Name = link, separated by ;. Ex: France TV = https://www.france.tv ; Aptoide TV = aptoidetv://
  → An entry named like a built-in app replaces its link (useful if the default link doesn’t work on your model).
• Enhanced built-in list: Twitch, Crunchyroll, YouTube Music, Apple TV.

After the update

Set the two new fields in the configuration, then run a device search and click Update on each TV to retrieve the selector.

Also, enable Wake-on-LAN / Network Wake-up in your TV settings (on Wi-Fi: « Wake-on-WLAN »).

[spenceur]

I’ll take a look at that, thanks again !

Just some user feedback for the config.

For the 3 following actions, add a selector so the user can select their box/TV.

Check the LG part if needed:

[lmilcent]

I’ll test this tonight on my GoogleTV Chromecast, it should work, right?

[guim31]

I certainly hope so! Don’t hesitate to tell me