Thanks! Any updates on your progress yet?
I’m making lots of progress with pyatv but I wouldn’t expect any real updates to home Assistant before end of year. But it might be both earlier or later. Working as fast and hard as I can!
8 Likes
Appreciate your work on this! My ATV is the only thing I’m having to control via infrared now, thanks to Apple. 
It was bound to happen (deprecation of legacy protocols). It was mainly I that was slow adapting, I implemented most stuff almost two years ago. So… But I will hopefully get something up and running by next week that is testable.
4 Likes
Thanks Pierre, we need your help.
I have pushed something that is testable now (far from complete), would love some feedback. Basic instructions are here:
Unfortunately I can’t test it right now. but your hard work is much appreciated. I currently use the workaround from chamberlain which works somewhat okayish for the time being. If I find the time to help test it I will try it. But I have the utmost confidence in you!
Thanks again @postlund for all your hard work!
Keep up the good work. I really want ATV to be working again.
A beta version of the component (that can be installed with HACS for instance) is now available here:
Be sure to read the instructions before installing.
I need at least the stack trace in order to debug. Can you check the log?
I got error when adding it manually as a custom component, bit after setting up HACS and installed the Appke TV beta from there it worked perfectly.
Ok, great! Main thing is that it works.
Thanks for your hard work on this @postlund. The beta integration worked perfectly for me!
Is there anything special required to also associate an apple remote controller? For some reason, I have never been able to get the apple tv to wake by using the media_player.turn_on service, however, it used to work for me via the remote.turn_on and that does not seem to have come across with the integration…
What exactly do you mean when you say “apple remote controller”? The remote is there, like before, but turning on or off is not implemented yet. Code-wise, the media player and the remote is exactly the same when it comes to turn_on and turn_off (even in the component that is currently in Home Assistant).
Since it’s not really possible to turn off a device without hacks (e.g. navigating menus), I won’t be able to implement it fully. I can do suspend (on Apple TV 4 or later) but that doesn’t play with CEC, so other devices will not turn off. Turning on is pretty much the same thing. A device will turn on itself (and CEC devices) whenever someone talks to it. It is not possible to “see” if a device is on, so if CEC is used, TV is off and home Assistant is restarted, then everything will turn on. Nothing has changed in this area and this is the way Apple has designed it (I’m afraid). The start_off setting was added to circumvent this at least a little I will introduce that setting in this component as well.
Hi @postlund. I have an early version of an LG TV (WEBOS) which is connected to my Apple TV V4.
The only way I have been able to turn on the LG TV using Home Assistant is by turning on the Apple TV first which then wakes the TV via the HDMI connection.
I have never been able to do this with the media_player.turn_on service for the Apple TV itself ( I get a “update_playing” not defined when calling the service). However, I have in the past been able to do this using turn_on for the remote entity_id. Sadly this is also no longer working - hence my question to you.
I can turn off everything by using the media_player.turn_off on the LG TV and this, in turn, also shuts down the Apple TV too (via HDMI).
That is weird since it’s the same code. I don’t understand. Apparently something happens under the hoods. Can you figure out the exact error message from the logs?
Ah yes, that is from the fork that @chamberlain2007 created. It seems to work differently compared to the original component and it do have a bug (missing self.). So that explains it. In the beta component it will work like it’s supposed to.
LOL - I am glad you understand what is going on!
I’m no techy, but do I take it that I should update/replace something or do I just wait until the bug is fixed in a later release?