Toggle sidebar Toggle sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

tvOS 27 and HomePod Issue

SteveLV702

SteveLV702

macrumors 6502
Original poster
So tvOS 27 Beta 1 no issues and then beta 2 no issues for almost a week and then starting yesterday. Both of my AppleTV’s running tvOS 27 Beta 2 keep getting this “unable to connect” error. And hit okay just comes back.. Only way to temporarily fix it is to Unplug and replug back in (aka restart) the AppleTV.

Anyone else having this issue? Any way to fix it? Submitted a Feedback Report with Apple.

Guess hope be fixed in the Beta 3 or even when HomePod OS 27 comes out whenever that is. IMG_3324.jpeg
 
  • Like
Reactions: jhfenton, jeremz1ne, zobby and 1 other person
I’m seeing this too. The root cause seems to be some sort of network issue, the AppleTV flaps on the network for about 3 minutes every 15 minutes or so. In between those spasms the device works normally.

It doesn’t seem to be a memory leak. And the sudden on set is odd, my timeframe roughly lines up with yours. I’m think something on Apple’s side or a server side resource it’s choking on. From the behaviour at the Home Screen I’m not sure it isn’t the AppleTV preview video.
 
  • Like
Reactions: SalisburySam
Yes getting this since yesterday seems a lot of people are. Also, this morning my primary home hub my living room apple tv stopped responding and now it switched to my other apple tv wonder how long before it stops responding too.
 
SteveLV702 said:
So tvOS 27 Beta 1 no issues and then beta 2 no issues for almost a week and then starting yesterday. Both of my AppleTV’s running tvOS 27 Beta 2 keep getting this “unable to connect” error. And hit okay just comes back.. Only way to temporarily fix it is to Unplug and replug back in (aka restart) the AppleTV.

Anyone else having this issue? Any way to fix it? Submitted a Feedback Report with Apple.

Guess hope be fixed in the Beta 3 or even when HomePod OS 27 comes out whenever that is.View attachment 2642468
Click to expand...
Saw this situation last night. I unplugged the ATV from both power and HDMI for minutes. That seemed to have worked. Then, the ATV turned ON itself and the TV -- twice. Ethernet used for nextwork.
Looked again. Same “unable to connect” error is back.
 
Last edited:
mhmercer said:
Saw this situation last night. I unplugged the ATV from both power and HDMI for minutes. That seemed to have worked. Then, the ATV turned ON itself and the TV -- twice. Ethernet used for nextwork.
Click to expand...
Ya what I did and also using Ethernet for networking…. But it will go away while I am actively using tv/watching the tv…. But if leave it alone for a while and come back I get it again… So like all day be watching tv in livingroom and then go to bedroom and turn on tv and immediately get this error and restart everything and will work fine until I go to bed and turn everything off then wake up error again…. Then go to livingroom and error again.
 
DblHelix said:
Yes getting this since yesterday seems a lot of people are. Also, this morning my primary home hub my living room apple tv stopped responding and now it switched to my other apple tv wonder how long before it stops responding too.
Click to expand...
I've also seen my Home go completely 'No Response' more in the last few days than I think I ever have, despite my Apple TV almost always being on one beta or another. Bring on beta 3 next week!
 
  • Like
Reactions: DblHelix
SteveLV702 said:
So tvOS 27 Beta 1 no issues and then beta 2 no issues for almost a week and then starting yesterday. Both of my AppleTV’s running tvOS 27 Beta 2 keep getting this “unable to connect” error. And hit okay just comes back.. Only way to temporarily fix it is to Unplug and replug back in (aka restart) the AppleTV.

Anyone else having this issue? Any way to fix it? Submitted a Feedback Report with Apple.

Guess hope be fixed in the Beta 3 or even when HomePod OS 27 comes out whenever that is.View attachment 2642468
Click to expand...
Yes, same issue for the last week or so. Tried all the remedies mentioned to no avail.
Thought it might have been my phone with AirPlay interference. Nope!
Also, having audio breakup on some programs, especially YouTube.
 
Was having this exact same problem, with the audio dropouts too.
What seems to have helped is turning off AirPlay in the settings as a temporary fix.
Hope they get round to correcting this in the third beta.
 
Same error message here but only on one of my Apple TV boxes. I have to reset it from the remote every time I switch to the Apple TV box input. Hold down back and TV button together for those that don’t want to unplug their box every time.

Also, Sonos speakers here, not HomePods but same error message.
 
Started for me yesterday when I updated to tvOS 27 build 24J5315i. Happens to both of my AppleTVs. One has a Sonos soundbar, the other just uses the TV speakers. HomeKit seems flaky too, timed automations (turn off the light after it’s been on for 10 min) constantly fail. I have to turn off lights manually, like an animal!
 
I've been experiencing this exact problem for the past few days. On the Apple TV, you probably need to disable AirPlay. On my iPhone, in the Home app, I changed the home hub to the HomePod. I then created a new room and moved the HomePod into that room, which seems to dissociate it from the Apple TV. When I move the HomePod back into the same room as the Apple TV, it prompts me to pair it with the Apple TV again. For now, I'm leaving it in the new room and not pairing it with the Apple TV until this issue is resolved. I can still use the HomePod for Siri requests, but it's no longer paired with the Apple TV. At this point, I'm still not sure whether this will temporarily resolve the problem.
----
After 24 hours with this configuration, it doesn’t seem to have fixed the issue. The message came back.
 
Last edited:
Last night, I didn’t get the error message anymore. Either my changes fixed the bug, or Apple worked on the issue remotely.
 
I started having the error this morning for the first time. I was still on beta 2, so I updated to beta 3. Unfortunately, I came home this evening to the same bug, followed by some app and Apple TV crashing. I have it unplugged for the moment, and I'm watching the Roku TV directly.

ETA: It is borked. After waiting a bit it still crashed on boot, and booted into restore. I'm trying Reset All Settings first to see if that gets it up and running.

ETAA: And…now it booted up with a warning symbol and a URL for instructions on how to restore the Apple TV, which for an Apple TV 4K tell you to get it serviced.

ETAAA: I made an appointment at the Apple Store for this afternoon, and Apple wants $199 to replace it. So it's officially dead unless it magically decides to come back to life. I'll try a few more things, and I'll hold onto it for a little while in case this turns out to be a widespread thing and Apple changes their policy for developers who had Apple TV's borked.
 
Last edited:
AL2TEACH said:
Probably the beta but it's sad that beta testers don't have some kind of protection using betas.
Click to expand...
Yeah. It was my mistake. I'm not working on an Apple TV app, but I wanted to check out the enhanced HomeKit video options. Of course, in reality there's nothing to check out yet because developers haven't updated their apps yet.

I learned my lesson. I will never update an out-of-warranty/Apple care non-user restorable device with a beta again unless I absolutely need to do it for testing.
 
  • Like
Reactions: ignatius345 and AL2TEACH
monkeyboyone said:
Started for me yesterday when I updated to tvOS 27 build 24J5315i. Happens to both of my AppleTVs. One has a Sonos soundbar, the other just uses the TV speakers. HomeKit seems flaky too, timed automations (turn off the light after it’s been on for 10 min) constantly fail. I have to turn off lights manually, like an animal!
Click to expand...
The AirPlay notifications have stopped. I’m not sure it was anything I did or something Apple was able to change with the service.
The only setting I changed was to manually select a HomePod that isn’t running an os27 beta for the Home Hub.
The change hasn’t affected the new os27 HomeKit notifications and other features on my other os27 devices but I’m glad to say HomeKit reliability is back to normal.
 
AL2TEACH said:
Probably the beta but it's sad that beta testers don't have some kind of protection using betas.
Click to expand...
There is protection using betas. It’s called waiting until the actual release comes out 🙂

I get it, I’ve been tempted before, only to see my old MacBook run hot, slow and unreliably. Never did it again.

Bugs are not only to be expected, they’re to be welcomed because that means they’re being surfaced by testers so they can be fixed for people who download the final release later this year. Thank you for your service!
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back