Apple TV won't wake up for AirPlay request

Can you clarify some of your points above?

- When you ping the ATV on the guest network, the ATV is asleep, correct?

- When you "see" the Bonjour advertisements, where do you see them?

Also, did you see my previous post showing my dns-sd -B _raop._tcp command? The ATV seems to be doing something(?) every half hour. It does this when it is asleep too. Does yours do that? (Seems to Rmv, then Add. But I still can't ping it, and it is not available in iTunes or iOS devices airplay.)

When I do a dns-sd command, I just get the options list for that command. If I do dns-sd -B, it only shows me Service Type _http._tcp. If I want to see _airplay, I have to specify that by doing dns-sd -B _airplay.

When I do dns-sd -B _touch-able, I see an Instance name of 876D600A79DB9B66. I don't know what that is. Does not look like a MAC address (too long.)

Can you clarify some of your points above?

Of course!

- When you ping the ATV on the guest network, the ATV is asleep, correct?

Yes.

- When you "see" the Bonjour advertisements, where do you see them?

I can see them if I do a "dns-sd -B <port>" on the MacBook. I can also see them (and it is much easier and gives me more details) with the mDNS Watch app on my iPhone. It is a freebie - has the look and feel from several iterations ago of iOS, but the information it gives is good.

Also, did you see my previous post showing my dns-sd -B _raop._tcp command? The ATV seems to be doing something(?) every half hour. It does this when it is asleep too. Does yours do that?

I have not kept the MacBook on the guest network long enough to try this but since I just threw it on the charger I'll connect to that network and leave it running when I'm finished here. I found a handy reference with the "port" values for dns-sd a few days ago but can't seem to find it right now. I'll look through my browser history. Forgot to bookmark...

When I do dns-sd -B _touch-able, I see an Instance name of 876D600A79DB9B66. I don't know what that is. Does not look like a MAC address (too long.)

The mDNS Watch app gives more information, including the name of the Apple TV which is advertising.

Okay, thanks!

Can I setup one of my Airport Express units as a wireless router? Then I can put an ATV and a laptop on that "guest" network and see what it does.

Yes. You'd have to connect to your existing network with an Ethernet cable into the WAN port of the Express and configure it to do DHCP & NAT - and be sure to use a different DHCP range than your home network (click on Network Options after setting to DHCP & NAT). "Create a wireless network" on the wireless part. It might be easier to reset to factory defaults and use the wizard, but whatever works for you.

You'll get a double-NAT warning but as long as you are just using this for a testing setup that shouldn't be a big issue.

I found the reference to port numbers and names (you need to scroll past the numbered ports to see the named ones used in dns-sd).

jjkraw wrote:

dreohio99: Since you have an ASUS router, could you look at System Log -> Wireless Log when the ATV goes into deep sleep? See if the ATV's MAC address appears in the Stations List for the corresponding SSID and, if so, see what is says in the PSM (power save mode) column. Thanks.

It does appear in the list and says "Yes" under PSM. Here is a screenshot of the log with my iPad and AppleTV on it. Presently the AppleTV is in "deep sleep" and the iPad remote app does not see it on the network.

See if this makes sense:

I do a dns-sd -B _airplay while my ATV is sleeping and I see this:

Browsing for _airplay._tcp

Timestamp A/R Flags if Domain Service Type Instance Name

12:12:15.141 Add 2 18 local. _airplay._tcp. Apple TV

Then I go into iTunes, and sure enough, Apple TV is there. So I try to connect to it, and it fails, then Apple TV is REMOVED from the airplay list in iTunes, and then this pops up in the dns-sd -B _airplay command window:

It's as if the Apple TV was advertising itself, but when I tried to connect, it failed (just like ping fails), and then that caused the ATV to either stop advertising, or my PC to stop seeing it. Weird.

5 minutes later, it added itself back onto the list:

The ATV reappears in iTunes, so I try to connect to it again, but it fails, Apple TV is removed from the airplay list in iTunes, and the dns-sd shows this:

It's like the ATV is "there", but it's "not there" if you try and do anything to connect to it, such as Ping or use Airplay.

I just installed the mDNS watcher app. It looks like I see everything that I am supposed to see when the ATV is asleep. But when I try and do anything that involves connecting to it, it won't respond. (Such as ping, or use Airplay.) It's like the ATV is advertising what it is supposed to when asleep, and my network "sees" everything that it is supposed to, but when I connect, either the traffic fails to get routed to the ATV, or the responses back from the ATV fail to get routed back. (I don't see why ping would fail to get there, because the arp table shows the correct MAC address for the IP of my ATV.)

The other thing that I am noticing is with regards to the ATV popping in and out of the _raop._tcp. list. It says "Add", and then every half hour, I see a "Rmv" and then "Add" again right away. At that point, ping will start responding for about 15 seconds! This is all while the ATV is asleep.

It is almost as if something else is acting somewhat as a sleep proxy for it and then it won't wake up when it is supposed to (I have that issue with my iMac). Of course, Apple TVs aren't supposed to do any of that. I'm thinking a bit on that...

In the meanwhile, some behavior reports:

After 1 hr 40 min the only report for _raop.tcp was the initial Add when I started it. Nothing else.

I now have that same ATV on my normal 5GHz network and it is reporting No consistently for PSM. Hmmm....

Any chance either of you has Wireshark on your Mac, or would be willing to try it out? This might be a whole lot easier if we could see the network traffic (at least for me).

I don't have a mac, which could actually be part of the problem. But I can install Wireshark on my Windows 7 PC. Maybe I can do that tomorrow.

Would you be interested in resetting one of your ATVs to factory settings? Then do the updates to the latest ATV software, and just do the minimum to connect it to the network. I am just wondering if some setting on your unit is causing it to behave differently?

I am remembering the experiment where those of us who have the ATV sleep issue can disconnect the internet from the router, then reboot ATV. At that point, the ATV is up, but home screen does not fully load, due to no internet connectivity. Then when ATV sleeps, it behaves properly. It is only when the unit is able to "see" the internet and load fully up that the problems with sleep mode start. Not sure what that tells us.

I'm currently trying to set up Homekit with my Apple Tv 3 acting as a hub for when I'm not at home.
(you can read more about this here: http://arstechnica.com/apple/2015/01/report-homekit-uses-appletv-as-a-smart-home -hub-sometimes/ )

This feature (AFAIK) uses the ._sleep-proxy._udp service provided by a ATV 3.

Unfortunately, I also just get these from my eth-connected atv:
_appletv2._tcp

_airplay._tcp

_touch-able._tcp

_raop._tcp

I'm missing the sleep proxy

My network mainly consists of one Router (netgear wndr3700, running Openwrt)

- installed miniupnpd on the router for UpnP/Nat-PNP, since Homekit uses iCloud

- backtomymac works fine in my network

has this anything to do with this thread? Google told me so.

If you go back a page or so, you'll see a post from a user stating that after installing 6.1.4 the sleep proxy worked. There are many reports of sleep proxy not working with 7.* firmware.

Would you be interested in resetting one of your ATVs to factory settings?

Before I do that (and since I need to inventory the settings anyway), here is what I have set on the one I'd reset. Not everything, but things I've changed and/or think may be pertinent. So compare / contrast...

** General

Remotes:

Other: DirecTV AV2

Bluetooth: Off (another has it on... doesn't seem to make a difference for me)

Send Data to Apple: No

** Main Menu

quite a few apps hidden

** Screen Saver

Start After: Never

Show During Music: Yes

** iCloud

Not signed in (but signed in on another ATV - doesn't seem to matter)

** iTunes Store

Signed in

** AirPlay

AirPlay: On

Conference Room: Off

Play from iTunes in the Cloud: Auto

Security: None

** Computers

Home Sharing: On

Well, dang....

I didn't do a factory reset, just a reset all settings. And... I think I have it reproduced. It stops answering pings not long after going to sleep.

We might actually figure this out. More info as I gather it.

I now know why logical attempts to figure this out got nowhere. It took brute force...

After doing the "reset all settings", I started to put the Apple TV back together. After each step, I put it to sleep and checked to see if it would answer pings beyond 25 seconds or so. If it did, I backed that step out and continued. I found two settings that caused the ATV to "behave":

• Programming to use the AV2 setting on my DirecTV remote
• Setting "Sleep after" to 30 minutes (from the default 1 hour)

Each of these, individually and together, make the ATV reachable at all times for me.

Still no clue regarding Sleep Proxy, however.

Ok so I know that I've seen the sleep proxy some time ago on 6.x

BUT

I need 7.x for Homekit to work...

So I just did a factory reset, and still no sleep proxy!

BTW: My Apple TV has DRHN at the end of its serial and the fourth and fifth letters are J8.

I just called Apple Support, but my warranty (which is tied to the device) is over.

Wow. This was pretty much the first time I could seriously use this device as always powered on and now it doesn't work...