Core: Apple TV does not update status

[dwest576]

Home Assistant release with the issue:

Component/platform:

When AppleTV is turn on from within HASS, what is playing and its status is updated. After a period of time, the status does not change. If a TV show or movie stops playing, the Apple TV within HASS continues to show playing.

If I turn off the Apple TV within HASS and immediately turn back on, it updates to get its current state.

[fabaff]

No warnings/errors in the log?

[dwest576]

Yes, there are!

A error occurred: Cannot connect to host 10.32.103.33:3689 ssl:False [Connect call failed ('10.32.103.33', 3689)]

A error occurred: None

A error occurred: failed to login: 503

Unknown data: b'103'

I am seeing all these throughout

[jjlawren]

I get these login failure errors about once a week. Only reliable way I've found to fix it is to restart the AppleTV.

[postlund]

Try disabling home sharing, restart the ATV and enable it again. Should work. It's a big or something that Apple introduced a while back, other projects talking to the ATV has reporters this behavior as well.

[dwest576]

I did that over the weekend. I even tried to reset the Apple TV to factory defaults.

On Jun 11, 2018, at 9:35 AM, Pierre Ståhl [e-mail] wrote:

Try disabling home sharing, restart the ATV and enable it again. Should work. It's a big or something that Apple introduced a while back, other projects talking to the ATV has reporters this behavior as well.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/home-assistant/home-assistant/issues/14860#issuecomment-396305460, or mute the thread https://github.com/notifications/unsubscribe-auth/AbzQBCBPWabZ4Yn81PPdYQMO8G4aRQl0ks5t7pxLgaJpZM4Ue2Hc.

[dwest576]

The weird part is: Turning off the Apple TV in the HASS interface and turning it back on fixes the issue temporarily, but doing this in the HASS interface does nothing to the actual Apple TV AFAIK. Wouldn't that point to something in the component updating the Apple TV from within HASS?

[dwest576]

Update: Was in my system this morning watching it. Hulu changed shows, but I didn't see the show change in the HASS interface. Turned off the AppleTV in Hass and back on, and the show instantly changed. There are no errors in the logs at this time.

[stephenyeargin]

Confirming that I'm also getting A <class 'pyatv.exceptions.AuthenticationError'> error occurred: failed to login: 503 in my logs and the status hangs. I have a 4th Generation Apple TV. My 2nd generation one works fine.

EDITED TO ADD: The login_id for both devices is identical.

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[Hammertime84]

I still have this problem. It happens about once a week. Restarting the Apple TV seems to work. This problem happens on both my Apple TV's (1x 4th gen and 1x 4k)

I am running HA version 0.84.5 and the latest TVOS

[postlund]

Please try manually pairing (with "atvremote pair") and use the login id you get, it seems to work better for most people.

[thejeffreystone]

Is this still an issue you are experiencing? Can you please try upgrading to the latest version of Home Assistant (0.90) and report back if this is still a problem? I noticed mine was working again after my .90 upgrade, so not sure that fixed everyone. Thanks!

[lucacri]

Still happens to me, even on 0.91.1

[pyatv.tag_definitions] Unknown data: b'103'
[homeassistant.components.apple_tv.media_player] A <class 'pyatv.exceptions.AuthenticationError'> error occurred: failed to login: 503

[sylarevan]

Got the same here with 0.91.1 (thousands of lines with the same message in log file) :

2019-04-12 17:11:42 WARNING (MainThread) [pyatv.tag_definitions] Unknown data: b'103'
2019-04-12 17:11:42 WARNING (MainThread) [homeassistant.components.apple_tv.media_player] A <class 'pyatv.exceptions.AuthenticationError'> error occurred: failed to login: 503

[jjlawren]

@lucacri & @sylarevan does restarting the AppleTV make the problem go away? I have a feeling this is a device issue and possibly something the integration can't easily fix.

[sylarevan]

@jjlawren After a reboot, the message disappers from the log file for a few days ... and then comes back. Just after the reboot, I get:

2019-04-12 17:15:13 WARNING (MainThread) [pyatv.tag_definitions] Unknown data: b'103'
2019-04-12 17:15:13 WARNING (MainThread) [homeassistant.components.apple_tv.media_player] A <class 'pyatv.exceptions.AuthenticationError'> error occurred: failed to login: 503
2019-04-12 17:15:33 WARNING (MainThread) [homeassistant.components.apple_tv.media_player] A <class 'concurrent.futures._base.TimeoutError'> error occurred: 
>>>>>  Apple TV REBOOT HERE
2019-04-12 17:15:44 INFO (MainThread) [pyatv.daap] Logged in and got session id 1
2019-04-12 17:15:45 INFO (Thread-2464) [pyhap.hap_server] Got connection with ('192.168.1.101', 49156).
2019-04-12 17:15:45 INFO (Thread-6903) [pyhap.hap_server] 192.168.1.101 - "POST /pair-verify HTTP/1.1" 200 -
2019-04-12 17:15:45 INFO (Thread-6903) [pyhap.hap_server] 192.168.1.101 - "POST /pair-verify HTTP/1.1" 200 -
2019-04-12 17:15:45 INFO (Thread-6903) [pyhap.hap_server] 192.168.1.101 - "GET /accessories HTTP/1.1" 200 -
2019-04-12 17:15:45 INFO (Thread-6903) [pyhap.hap_server] 192.168.1.101 - "PUT /characteristics HTTP/1.1" 204 -
2019-04-12 17:15:45 INFO (Thread-6903) [pyhap.hap_server] 192.168.1.101 - "PUT /characteristics HTTP/1.1" 204 -
2019-04-12 17:15:45 INFO (Thread-6903) [pyhap.hap_server] 192.168.1.101 - "PUT /characteristics HTTP/1.1" 204 -

[sylarevan]

FYI, this issue is still present with 0.95.4. Thousands of lines with the 503 error above. Nothing after a reboot ... for a few days.

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.