Hi there all,
I just want to ask you all if it’s possible to link the Google Home Assistant to my
Android TV… I have a Philips Android TV.
The Google Home Assistens allready work on my Hassio with other commands.
This thread it’s about a lot of procedure and a lot of problems.
Is there any simple plugin in order to just have “Hey Google… turn on the TV”
Or maybe a step-by-step link on some web page.
I’ve got a problem retrieving the current state of my FireTV Stick. Getting states (playing, paused) for Netflix works very reliable (just with a little delay sometimes). But for prime video it’s going to paused very often though I’m still playing.
The reddish color is playing, green is paused. I’ve been playing a movie without pausing, though. the last part (saying “Spielt”) is played using netflix. As you can see, there are no false states.
I also experience this with Prime Video on my Nvidia Shield. From what I saw it’s reporting different values for the wake_lock_size. Sometimes it’s 4 when it’s playing and then 2 when it’s paused then other times it’s 3 when it’s playing an 1 when it’s paused. Not sure why that app in particular reports different values. Those are used to detect the state of the app. I haven’t looked closely at the custom state detection to see if you can specify 2 different values for play/pause or not.
media_player:
- platform: androidtv
name: Android TV
host: 192.168.0.222
state_detection_rules:
'com.amazon.tv.launcher':
- 'playing':
'wake_lock_size': 4 # this indentation is important!
'wake_lock_size': 3 # this indentation is important!
- 'paused':
'wake_lock_size': 2 # this indentation is important!
'wake_lock_size': 1 # this indentation is important!
- 'standby'
“GET_PROPERTIES” seems to fail when I try…probably a formatting issue as I wanted to see if I could pull data when the actual BBC app was playing but not sure how to achieve this.
Invalid config for [media_player.androidtv]: 'wake_lock_size' is not a valid state for the 'state_detection_rules' parameter for dictionary value @ data['state_detection_rules']['com.amazon.amazonvideo.livingroom']. Got [OrderedDict([('wake_lock_size', OrderedDict([(4, 'playing'), (3, 'playing'), (2, 'paused'), (1, 'paused')]))]), 'standby']. (See /config/configuration.yaml, line 164). Please check the docs at https://home-assistant.io/integrations/media_player.androidtv/
Could someone help me what is wrong with my configuration, particularly, with state_detection_rules that I actually copied from docs example:
media_player:
- platform: androidtv
host: 192.168.1.100
name: Android TV
adb_server_ip: 127.0.0.1
adb_server_port: 5037
apps:
org.droidtv.playtv: "TV"
com.google.android.youtube.tv: "YouTube"
com.netflix.ninja: "Netflix"
org.droidtv.tvsystemui: "Screensaver"
com.plexapp.android: "Plex"
com.google.android.tvlauncher: "Menu"
com.opera.sdk.example: "Browser"
org.xbmc.kodi: "Kodi"
state_detection_rules:
'com.plexapp.android':
- 'paused':
'media_session_state': 3 # this indentation is important!
'wake_lock_size': 1 # this indentation is important!
- 'playing':
'media_session_state': 3 # this indentation is important!
- 'standby'
Unfortunately, validator doesn’t accept it:
Configuration invalid
Invalid config for [media_player.androidtv]: [state_detection_rules] is an invalid option for [media_player.androidtv]. Check: media_player.androidtv->state_detection_rules. (See ?, line ?). Please check the docs at https://home-assistant.io/integrations/media_player.androidtv/
You are already connected to the Android TV / Fire TV via ADB from another device. Only one device can be connected, so disconnect the other device, restart the Android TV / Fire TV (for good measure), and then restart Home Assistant.
I am using 0.100.3 as i am having BIG problems installing and running 0.101.3.
Is there a release that will work with 0.100.3 as custom component?
I was always connected only with my fire tv… i discovered it changed ip address also if i set it as static IP
Must i restart FireTV again and connect with adb again?
I disconnected (deleting the adb keys) and restarted my fire tv.
Got the request for adb, the two adb keys were created again, clicked ok, restarted HA but still got the same advice !!!
So i need (in the meantime i solve the problem with the 0.101.3 release) of the previous release of the component that was working great…