After upgrading from 0.77.3 to 0.78.3, my iOS component cannot be loaded anymore (had no issues before and config is valid), I get a persistent notification mentioning zeroconf and ios:
2018-09-22 19:35:42 ERROR (MainThread) [homeassistant.setup] Error during setup of component zeroconf
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/setup.py", line 148, in _async_setup_component
component.setup, hass, processed_config) # type: ignore
File "/usr/lib/python3.5/asyncio/futures.py", line 380, in __iter__
yield self # This tells Task to wait for completion.
File "/usr/lib/python3.5/asyncio/tasks.py", line 304, in _wakeup
future.result()
File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
raise self._exception
File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
result = self.fn(*self.args, **self.kwargs)
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/zeroconf.py", line 55, in setup
zeroconf.register_service(info)
File "/srv/homeassistant/lib/python3.5/site-packages/zeroconf.py", line 1836, in register_service
self.check_service(info, allow_name_change)
File "/srv/homeassistant/lib/python3.5/site-packages/zeroconf.py", line 1952, in check_service
raise NonUniqueNameException
zeroconf.NonUniqueNameException
2018-09-22 19:35:42 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of ios. Setup failed for dependencies: zeroconf
2018-09-22 19:35:42 ERROR (MainThread) [homeassistant.setup] Setup failed for ios: Could not set up all dependencies.
I am having the same issue on my setup: Hass.io on an ubuntu virtual machine (installed by the script from github). Untill the last update everything was working, now the mentioned components won’t load.
Same issue after similar upgrade on hassbian. I have another older HA instance on my network, I saw a thread somewhere suggesting that could mess up zeroconf, but unless that is common to the rest of you I suspect that’s not it.
Thanks to @pplucky I found out I forgot about a second instance of home assistant running on my network (both had the same “name” in the configuration.yaml). Killed the docker container of my second -forgotten- instance and the error disappeared.