pyatv: Use of aiozeroconf causes issues in Home Assistant
Describe the bug
Having aiozeroconf
installed in the same environment as Home Assistant leads to various aiohttp
errors on unrelated components: https://github.com/home-assistant/core/issues/37303
To Reproduce
Have the latest apple_tv
custom component installed on Home Assistant 0.112.0+.
System Setup (please complete the following information):
- OS: Ubuntu 19.10
- Python: 3.8.3
- pyatv: 0.6.0
- apple_tv custom_component: https://github.com/postlund/hass-atv-beta/tree/d2a081ead8deb82896bb634d03ac5b4a1676262a
- Apple TV: AppleTV 4
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 21 (20 by maintainers)
Commits related to this issue
- scan: Migrate back to zeroconf from aiozeroconf As aiozeroconf causes problems (due to bugs) and is not maintained anymore, it's better to move back to zeroconf again. Since service discovery is alre... — committed to postlund/pyatv by postlund 4 years ago
- scan: Migrate back to zeroconf from aiozeroconf As aiozeroconf causes problems (due to bugs) and is not maintained anymore, it's better to move back to zeroconf again. Since service discovery is alre... — committed to postlund/pyatv by postlund 4 years ago
Oh, that is a bug in pyatv. I will look into that.
I have finished the migration back to
zeroconf
in #756, but I do need to test it live first to be sure it works as expected. Hope to be able to do that tonight. This should also conclude the changes I’m making for 0.7.0, just need to update some documentation before I can make the release. But if #756 works, I can hopefully make the release tonight and bump version in the beta component as well.