Closed nefh closed 3 years ago
I'm not sure how to categorize this issue. However, this is a configuration issue IMHO.
OSError: [Errno 50] Network is down
Python isn't able to access the network for Zeroconf as it seems, which is not a Home Assistant issue.
The core installation is made according to the guides:
https://www.home-assistant.io/docs/installation/virtualenv/ https://community.home-assistant.io/t/installation-of-home-assistant-on-your-freenas/195158
I've seen during my research that other people also have problem with no network accessible to zeroconf - they usually ignore it, because HA seems to be working fine, but I assume they just don't use zeroconf in their setup.
If the problem is that Python venv configured according to the documentation can't access zeroconf network, then the issue is with Home Assistant documentation and it would be nice if we can update it to ensure network connection for zeroconf.
BTW, earlier I've posted this issue on HA forum for configuration topics: https://community.home-assistant.io/t/homeassistant-core-homebridge-not-responding-mdns-avahi-zeroconf-issue/240979
You are pointing to a community guide, that is not a supported method. We do not control your operating system and cannot take any responsibility for your jailing.
One of the guides is community guide and the other is official one. All points from official one are fullfilled. The jail itself should not be a problem - I have the same jail setup with homebridge standalone and there avahi in node.js zeroconf in python is working fine.
Edit: In homebridge standalone there is avahi used by node.js. I've found someone with similar problem on python-zeroconf github, but that problem was already solved: https://github.com/jstasiak/python-zeroconf/issues/221
I only want to clarify what is the issue here, get some notes how to troubleshoot the problem further. If I find solution, I will add this information to the guides, so others don't came to the same problem.
The linked python-zeroconf issue, has been fixed upstream and released and is already in Home Assistant, thus not part of the issue.
The official guide on setting up a venv, does not describe setting up a jail, networking or any other network related things. Configuring your network correctly is not a scope we can do anything about, but part of your responsibility.
Nevertheless, I do agree, this might be a specific case of compatibility with the chosen operating system. However, FreeBSD is not an officially supported system by our project.
See: https://github.com/home-assistant/architecture/blob/master/adr/0016-home-assistant-core.md
Ok, clear. I'll investigate this issue further, if I came to something, I will share notes here. Please keep this thread open, if possible. Maybe someone else will also share their inputs. Thanks!
I've got zeroconf working. It needs jail to use VNET. With virtual network stack no any additional configuration is needed, just plain:
homekit:
The only question now is why homebridge standalone works without VNET and HA homebridge not. But since its working, then this is not a very serious issue now.
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 has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
The problem
Pairing to homebridge integration is not possible - no response from bridge or devices. Running homeassistant-core in Jail on XigmaNAS (OS based on FreeBSD, similar to FreeNAS). No docker, no add-ons, no Linux. I had the same problem with standalone installation of homebridge (without HA) and I found fix:
I've tinkered with troubleshooting from HA website, but nothing seems to work. There is no firewall, the homebridge ports are accessible through nmap.
Zeroconf is reporting "OSError: [Errno 50] Network is down" during boot. I've googled this error, people usually ignore it, but maybe they do not use zeroconf for anything? The network connection is of course working for other HA integrations, i.e. MQTT integration to Mosquitto or UPS NUT.
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information