-
-
Notifications
You must be signed in to change notification settings - Fork 28.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apple Integration Broken Following iOS 16.2 Devices Update #84233
Comments
Hey there @postlund, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) apple_tv documentation |
I didn't upgrade to 16.2 becuase of this issue but a week ago decided to upgrade to 16.2 and touch wood I have not encountered this issue. I'm not sure what is different in my setup but I am running HA in a docker container with host networking. |
My three Apple TV's auto updated sometime in the last week and since then I've noticed that there is no linger a "Standby" power state reported. Since I rely on the state to turn on/off an old stereo, that no longer works. All other states, media info, apps etc are all being updated correctly in the states information of the entity so thats still working nicely. I am using the ATV beta add on (Hacs) since the native plugin hasn't worked for me since tvOS15. |
Thanks @kernelkraut - I will take a look at the ATV beta as I just can’t get my ATV or HomePods to pair with HA anymore. I’ve also had to completely wipe all my HomeKit data on the Apple cloud (via downloaded profile) and rebuild just to get a working HA Bridge back into HomeKit. Seems Apple have screwed up big time with the implementation of this Architectural update. |
I've since replaced my Apple TV with a Chromecast 4K. Broken HA integration
is a deal breaker for me.
…On Mon, Jan 16, 2023, 4:14 AM Sooty70 ***@***.***> wrote:
Thanks @kernelkraut <https://github.com/kernelkraut> - I will take a look
at the ATV beta as I just can’t get my ATV or HomePods to pair with HA
anymore. I’ve also had to completely wipe all my HomeKit data on the Apple
cloud (via downloaded profile) and rebuild just to get a working HA Bridge
back into HomeKit. Seems Apple have screwed up big time with the
implementation of this Architectural update.
—
Reply to this email directly, view it on GitHub
<#84233 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALZKNHRBURSUG4IBRPT33K3WSUGQHANCNFSM6AAAAAATDIVF2Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hi, Having the same issue!! No response after updating to 16.2. Deleting and repairing hub with 100 + Accessories is not working, after first reboot all devices became not responsible again! damn this is so bad! What can we do with this? Is there any working solution? I cant take a hours of mi life to fix this. All my devices connected to homekit using home assistant.! This is fail of century! Also Homebridge bridge is working without any issues. |
Does the Apple TV HACS integration work better @Sooty70? |
I don’t see an Apple TV HACS integration (I think the original made it into HA Core). Thus sadly still can’t get my TV or HomePods into HA. |
The beta is really old, don't use that. Go into the Home app and make sure you change access settings for HomePods to everyone on the same network. HomePod works for me so it's likely that reason. |
Thankyou @postlund - pairing working now! |
@postlund I don't know if that solves the issue I'm seeing - once I changed AirPlay access settings all I get is constant disconnects and reconnects. Maybe a separate issue but certainly related to 16.2 Happy to provide better debugging and more in-depth logs if you're able to look into it. |
For some more details, I am on 16.2 Apple TV, HA 2023.1.4. The Apple TV is connected via Ethernet and set to allow connections from everyone using the Apple TV’s internal menu for Airplay & HomeKit. To start I deleted the device and integration, then went through the process of re-adding via IP address entering 3 different airplay passcode prompts.It works fine until I put it to sleep. Then, this happens: `Logger: homeassistant.components.apple_tv Failed to connect As well as this error: `Logger: pyatv.protocols.airplay Failed to set up remote control channel And these warnings: `Logger: homeassistant.components.apple_tv Connection lost to Apple TV "Basement (2)" ` Once I then turn it back on again, it will not re-initialize state and will show as “Idle” even with media playing. Restarting home assistant WILL properly initialize the state of the Apple TV. @postlund let me know if I can do more digging for you. And if I’m conflating issues here, let me know and I can copy this over to another issue and delete my comments so people aren’t confused. |
I updated to 16.3 yesterday and the integration started working again without doing anything 🎉 |
Media devices setting change to allow everyone to access fixed issue. |
The problem
Following Apple's recent release of 16.2 devices from Home Assistant take a long time (hours) to update in the Apple Home App. The slow process repeats itself each time you add a new device or there is a restart of HA.
Interestingly the import of entities into Home Assistant from HomeKit Controller is working fine, however, the AppleTV integration is definitely broken.
And when you open the config for each device you get the following;
I've tried rebooting all the apple devices and reloading the integration with no change...
What version of Home Assistant Core has the issue?
Home Assistant 2022.12.7 Supervisor 2022.11.2 Operating System 9.4 Frontend 20221213.1 - latest
What was the last working version of Home Assistant Core?
Home Assistant 2022.12.7 Supervisor 2022.11.2 Operating System 9.4 Frontend 20221213.1 - latest
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Apple TV
Link to integration documentation on our website
https://www.home-assistant.io/integrations/apple_tv/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: