core: Zeroconf error - even though zeroconf not in my setup
Home Assistant release with the issue: 103.6
Last working Home Assistant release (if known): Not seen this before today, have had 103.6 installed since the day it was released
Operating environment (Hass.io/Docker/Windows/etc.): Hassio >Docker > Debian > Proxmox
Integration: Zeroconf
Description of problem: Error in log at startup as below
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
N/A - zeroconf isn’t in my config (I don’t use default_config - so I guess it must be a dependency of something else I’m using but I don’t know what??)
Traceback (if applicable):
2020-01-15 13:09:27 WARNING (zeroconf-Engine) [zeroconf] Choked at offset 0 while unpacking b'\n\xba\x10\x00'
2020-01-15 13:09:27 WARNING (zeroconf-Engine) [zeroconf] Exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/zeroconf/__init__.py", line 690, in __init__
self.read_header()
File "/usr/local/lib/python3.7/site-packages/zeroconf/__init__.py", line 713, in read_header
) = self.unpack(b'!6H')
File "/usr/local/lib/python3.7/site-packages/zeroconf/__init__.py", line 700, in unpack
info = struct.unpack(format_, self.data[self.offset : self.offset + length])
struct.error: unpack requires a buffer of 12 bytes
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 1
- Comments: 32 (15 by maintainers)
@Kane610 - yup, but zeroconf is not a dependency for tp-link, so something tp-link is doing is interfering with the zeroconf service. I don’t think trying to sort out both ends of the problem is an unreasonable idea.