Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Catch Zeroconf exception #28728
If there is a running Home Assistant instance in the local network and the user start a second one then there is a traceback. It's more an issue which developers will encounter.
2019-11-12 10:09:16 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved Traceback (most recent call last): File "/usr/lib64/python3.7/concurrent/futures/thread.py", line 57, in run result = self.fn(*self.args, **self.kwargs) File "/home/fab/Documents/repos/ha/home-assistant/homeassistant/components/zeroconf/__init__.py", line 72, in zeroconf_hass_start zeroconf.register_service(info) File "/home/fab/Documents/repos/ha/home-assistant/lib64/python3.7/site-packages/zeroconf.py", line 1921, in register_service self.check_service(info, allow_name_change) File "/home/fab/Documents/repos/ha/home-assistant/lib64/python3.7/site-packages/zeroconf.py", line 2062, in check_service raise NonUniqueNameException zeroconf.NonUniqueNameException
Example entry for