home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
69.61k stars 28.79k forks source link

Apple TV integration doesn't work with tvOS 18 #119588

Closed neominik closed 6 days ago

neominik commented 1 week ago

The problem

Since upgrading my apple TV 4k to tvOS 18 developer beta 1, the controls in HA (media_player and remote) show as "off".

What version of Home Assistant Core has the issue?

core-2024.6.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

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?

2024-06-13 10:28:52.740 DEBUG (MainThread) [homeassistant.components.apple_tv] Discovering device Schirm
2024-06-13 10:28:52.741 DEBUG (MainThread) [pyatv.core.scan] Auto-discovered Schirm at 192.168.1.146:7000 via Protocol.AirPlay ({'acl': '0', 'btaddr': '47:1A:D8:07:4D:32', 'deviceid': 'EA:D7:AA:98:CC:DC', 'fex': '1d9/St5/F7w4oQ4', 'features': '0x4A7FDFD5,0xBC177FDE', 'flags': '0x18644', 'gid': '13FD28EF-DA25-5788-B3AE-7A9CEEEE14E1', 'igl': '1', 'gcgl': '1', 'gpn': 'Schirm', 'psgsz': '3', 'psgtp': '1', 'psgid': '13FD28EF-DA25-5788-B3AE-7A9CEEEE14E1', 'pgm': '0', 'pgmid': '0', 'model': 'AppleTV6,2', 'protovers': '1.1', 'pi': 'e7bcee51-5fd3-4a1c-9eea-df1c3d3af172', 'psi': 'E9D7AA98-CCDC-489C-898B-85B139E26CD2', 'pk': '4eb54b472d922f0be07bbe2bd0dc6b507981303492cbf9136d669201df1cf784', 'srcvers': '800.55.3', 'osvers': '18.0', 'vv': '1'})
2024-06-13 10:28:52.741 DEBUG (MainThread) [pyatv.core.scan] Auto-discovered Schirm at 192.168.1.146:49153 via Protocol.Companion ({'rpmac': '2', 'rphn': '07e153912ac7', 'rpfl': '0x8B6782', 'rpha': 'c8cc8ac9ad68', 'rpmd': 'AppleTV6,2', 'rpvr': '600.21.5', 'rpad': 'b38e1385cada', 'rphi': '9bc42a9595a3', 'rpba': 'C5:22:45:81:3F:47', 'rpmrtid': 'E9D7AA98-CCDC-489C-898B-85B139E26CD2'})
2024-06-13 10:28:52.742 DEBUG (MainThread) [pyatv.core.scan] Auto-discovered EAD7AA98CCDC@Schirm at 192.168.1.146:7000 via Protocol.RAOP ({'cn': '0,1,2,3', 'da': 'true', 'et': '0,3,5', 'ft': '0x4A7FDFD5,0xBC177FDE', 'sf': '0x18644', 'md': '0,1,2', 'am': 'AppleTV6,2', 'pk': '4eb54b472d922f0be07bbe2bd0dc6b507981303492cbf9136d669201df1cf784', 'tp': 'UDP', 'vn': '65537', 'vs': '800.55.3', 'ov': '18.0', 'vv': '1'})
2024-06-13 10:28:52.743 DEBUG (MainThread) [homeassistant.components.apple_tv] Failed to find device Schirm with address 192.168.1.146

Additional information

No response

home-assistant[bot] commented 1 week ago

Hey there @postlund, mind taking a look at this issue as it has been labeled with an integration (apple_tv) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `apple_tv` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign apple_tv` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


apple_tv documentation apple_tv source (message by IssueLinks)

romanr commented 6 days ago

Under tv Settings > AirPlay > Allow access mine had selected "users". Maybe that was set by the update.
Changed to "Same network" and was able to pair with HomeAssistant.

neominik commented 6 days ago

The setting was still set to "Same network" for me. However, today I was able to add the tv to home assistant again and it seems to be working now. Not sure what the problem directly after the update was ¯\_(ツ)_/¯