Apple TV won't wake up for AirPlay request

I experience the same issues with only my iOS devices all of which, including the Apple TV, are fully up-to-date.

Strangely, when a friend used their iPhone (unknown iOS version but prob 8) it instantly woke the ATV!

After that all my devices were able to do the same....until she left! Will Apple address this temperamental behaviour please?

I've been having the same problems, messing around I discovered in control pannel if you turn on Bluetooth & wait a few seconds It will wake from AirPlay. It works for me but still waiting for an update fix!

Try turning on Bluetooth in the control pannel with wifi still on wait a few seconds & it should wake via AirPlay. Hope they fix this soon!

That worked for me thank you very much!

My friend has Bluetooth switched on always so that explains why she was able to wake it.

Hope Apple provide a fix for this.

Hi,

I did an update to my ATV and now my Macbook cant wake it up, I have to click on the remote control for it to wake up, anyone that can help me?

I have restored it without any help.

I have the same problem with my ATV3. After it goes into "sleep" mode, shortly after that it no longer shows up in Airplay - anywhere. Not on my iPad2, not in iTunes on my Windows 7 laptop, not on my iPhone or iPod touch. I must manually "wake" the ATV3 with the little silver remote that came with it. I did not used to have to do that! Somewhere over the past few months, an ATV3 software update got rolled out and this started happening.

I have tried everything - restart ATV, turn blue tooth on, off, you name it. I know some of that stuff has worked for others, but NONE of it works for me. Could it be something to do with a specific hardware version of the ATV3? There are so many variables involved here it is hard to tell anymore.

I have seen some posts about wired vs. wireless. Someone had an ATV3 with this problem that was wired via Ethernet, but another one of their ATV3 devices that was wireless did not have the problem. But - someone else later reported the OPPOSITE problem, which makes me thing it is something specific to the particular ATV itself. (Hardware version, some other setting, etc.)

I am basically stumped. The only thing you can really do if the problem persists (as it does for me) is disable the auto-sleep function. This means the blue light on the front stays on permanently. The whole unit stays active, which probably uses a little more power and shortens the life of the unit, but this does "force" airplay to ALWAYS be available for you.

If it is more important to have ATV3 always available via airplay, and you don't want to manually wake it with the remote, then this may be your only choice. Even when "sleep never" is selected, you can always manually put the ATV3 to sleep, like if you go on vacation or something. Just one more thing to remember.

AND - one more thing that USED TO WORK that does not anymore! I think Apple is losing track of things here.

I also would like to note that I checked my ATV3 to see if it is part of the recall program. Based on the serial number, it is NOT.

However, I still think it may be defective. The serial number range still may have something to do with this issue. (My serial number ends in DRHN, and the forth and fifth digits are JF.)

http://arstechnica.com/apple/2013/04/apple-tv-with-wi-fi-problems-you-could-get- a-free-replacement/

As a workaround, I have found that I can use a Wake On Lan client (such as Wake On LAN by Aquila Technologies) to wake the Apple TV so that it shows up again in airplay. From a windows box, I ping the apple TV continuously (-t option), and then I use the WOL client from Windows to wake the Apple TV. The pings start getting responses, and then I can see the Apple TV in Airplay.

What I really want is for the ATV to stay visible in Airplay all the time like it used to. Ever since one of the ATV software updates, I either have to manually wake the ATV using the tiny silver remote, or use the WOL utility and ping from my Windows PC.

Note that when I "wake" the ATV using the WOL utility and ping, the blue light does not come on. It is still "sleeping" to some degree, but now responds to the network and shows up in airplay.

I don't know what apple was trying to do when they broke this. Seems like they know about it and want it to be this way.

I'm also having this problem, started with my iPad, spread to my iPhone, then my wife's iPad, now my mac pro. The Bluetooth suggestion has not worked for me (Bluetooth always on). Have restarted all devices, and wifi router - AirPlay sometimes returns briefly but then freezes or drops out and AirPlay option disappears. I have just done a restore on the Apple TV without any change. I am now doing a factory reset of the Apple TV to see if this works. In the meantime, my fallback has been to use ChromeCast - fortunately most of my regularly used streaming apps (YouTube, Netflix, ABC iview, tunein radio and vimeo) are able to cast and work perfectly well even though AirPlay is cactus.

Apple TV just finished its factory reset. It has been able to connect to my computer's library, but the mac pro cannot detect the Apple TV, and the Apple TV does not appear under AirPlay on any of our iOS devices. I guess I'll be using Chromecast until the next Apple TV comes out (unless I've gotten too used to using Chromecast to bother buying a new Apple TV by the time the new one is released).

For those running into this problem: Are there any other Apple networking devices, such as Airport or Time Capsule, on the network?

There is another thread from a few days agoabout how the ATV3 will not act as a sleep proxy (even though advertised that it should) and I'm wondering if there is some connection here. My knowledge about how sleep proxy works is limited, but I'm interested enough to do some research.

In my own case, I have three ATV3s and all will wake up for AirPlay. However, I also have a Time Capsule and a sometimes-on Airport Express (only gets used for AirPlay audio these days).

Unlike what Straightbourbon has seen, if I do a continuous ping for any of my ATVs that are in sleep mode, I get responses. This differs from a Mac that is in sleep mode. In that case, the Time Capsule (acting as sleep proxy) responds to the ARP and then sends a host redirect in response to the ICMP Echo (which is the underlying IP packet that does the "ping"). That tells me that Boujour Sleep Proxy doesn't seem to come into play, at least in my case.

Straightbourbon: After the ATV has been asleep for a while undisturbed, when you see no responses from the pings, could you do an "arp -a" to see if you have an entry for the ATV, and if so, if the MAC address reported matches the one on the ATV Settings->General->About screen?

I'm wondering if there is some combination of equipment / devices / environment that cause this to not work for some while working OK for others...

After the ATV was asleep and turned off all night (undisturbed), I tried pinging it. There was no response. There is also no entry for it in the arp table. That is why I am getting "Reply from 192.168.1.103: Destination host unreachable." (192.168,1,103 is my local machine.)

I used arp -s 192.168.1.15 [mac address of ATV] to manually put the ATV Mac address in the arp table. Now when I ping, I get "Request timed out."

Seems pretty certain that ATV is in a sleep state that does not respond to ping or arp requests. It does however respond to Wake on LAN.

Lets compare notes to see if there is anything different about our ATVs.

Mine: A1427 (3rd gen, NOT rev a). Software 7.2 (7512). Connected via Ethernet.

Also, when you say "sleep state", is that from inactivity timeout (value in Settings -> General -> Sleep After), do you manually sleep it using Settings -> Sleep Now, or something else. In my case, I manually put it to sleep.

Just for grins I'll move my ATV onto a wireless network to see if that makes any difference.

Mine: A1427. Software 7.2 (7512). Connected via Wi-Fi.

I usually put mine to sleep manually, but I have also observed it when ATV puts itself to sleep (set to sleep after 1 hour.) Does not seem to make any difference how it sleeps.

Once mine goes into this "deep sleep", I cannot "see" it in Airplay on any of my iOS devices, or in iTunes on the PC. Sometimes it does show up in iTunes, but when I connect, it fails, and when I deselect ATV, it then disappears from the airplay list in iTunes.

If I ping it with a -t and then use a WOL program to send Wake on LAN command, then it wakes up. The blue light stays off, and there is no video output. So it is like there are 3 different levels of "awake-ness" on the ATV:

1) Full power

2) regular sleep (no blue LED on front, no video output, but visible in Airplay, and responds to ping)

3) "deep sleep", which is the one where it is not ping-able, will not be visible in Airplay, cannot connect to it with itunes. The "deep sleep" mode requires me to ping and use WOL to wake (or use ATV silver remote to wake it up to full power.)

I just want the ATV to never go into deep sleep. I want it to stay pingable, and visible in Airplay, just like it used to before one of the ATV software updates changed the behavior. The fact that it responds to WOL when in deep sleep is interesting. It's almost like Apple wants it to to that?

Also, I used the command dns-sd -B _raop._tcp in windows cmd line, and it shows the Instance Name of the ATV, but the MAC address is off by one digit! (Last digit in Instance Name is "8", but on ATV unit, in settings-> about, it shows a "7", and the arp table shows "7" as the last digit as well. Weird.

My router is a Linksys E1700.