All entities going off/unavailable permanently

Installation Home Assistant OS
1

I’m having the same issue, I’m using the generic x86-64 Home Assistant x86 OS home assistant in a HP Elitedesk 800 G2 mini Intel i5, after the installation of Home Assistant discovered all my equipment’s and everything was working perfectly, but 1 hour later all entities went off or unavailable and they stayed that way permanently. I have installed several times the OS and keeps apening every time. Don’t know what is the problem!?

Please any help!!
Thank´s

2

Look at your logs for clues, Settings → System → Logs.

1 Like
3

Full logs:

2022-08-15 03:02:15.947 WARNING (MainThread) [homeassistant.config_entries] Config entry ‘Quarto Principal’ for apple_tv integration not ready yet: Not found at 192.168.0.35, waiting for discovery; Retrying in background

2022-08-15 03:02:15.949 WARNING (MainThread) [homeassistant.config_entries] Config entry ‘Color 0x531d6fb’ for yeelight integration not ready yet: Failed to read from the socket at 192.168.0.198:55443: [Errno 111] Connect call failed (‘192.168.0.198’, 55443).; Retrying in background

2022-08-15 03:02:16.114 WARNING (MainThread) [homeassistant.components.dlna_dms] Failed connecting to recently alive device at http://192.168.0.100:32469/DeviceDescription.xml: UpnpConnectionError(‘ClientConnectorError(ConnectionKey(host=‘192.168.0.100’, port=32469, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=-8625894658308676900), ConnectionRefusedError(111, “Connect call failed (‘192.168.0.100’, 32469)”))’, None)

2022-08-15 03:02:16.371 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can’t connect to ESPHome API for athom-smart-plug-02b14d @ 192.168.0.250: Error connecting to (‘192.168.0.250’, 6053): [Errno 111] Connect call failed (‘192.168.0.250’, 6053)

2022-08-15 03:02:16.390 ERROR (Thread-5) [pychromecast.socket_client] [Quarto principal(192.168.0.236):8009] Failed to connect to service ServiceInfo(type=‘mdns’, data=‘google-nest-hub-dd56ce902b54f623dae2ece1eb051780._googlecast._tcp.local.’), retrying in 5.0s

2022-08-15 03:02:16.943 WARNING (MainThread) [homeassistant.config_entries] Config entry ‘Color 0x531d6fb’ for yeelight integration not ready yet: Failed to read from the socket at 192.168.0.198:55443: [Errno 111] Connect call failed (‘192.168.0.198’, 55443).; Retrying in background

2022-08-15 03:02:20.032 WARNING (MainThread) [homeassistant.config_entries] Config entry ‘PC Escritorio HS110(EU)’ for tplink integration not ready yet: Unable to connect to the device: 192.168.0.152: [Errno 111] Connect call failed (‘192.168.0.152’, 9999); Retrying in background

2022-08-15 03:02:20.034 WARNING (MainThread) [homeassistant.config_entries] Config entry ‘LED 3 KL50(UN)’ for tplink integration not ready yet: Unable to connect to the device: 192.168.0.60: [Errno 111] Connect call failed (‘192.168.0.60’, 9999); Retrying in background

2022-08-15 03:02:22.154 WARNING (MainThread) [aioshelly.block_device] device 192.168.0.19 initialize error - ClientConnectorError(ConnectionKey(host=‘192.168.0.19’, port=80, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=-8625894658308676900), ConnectionRefusedError(111, “Connect call failed (‘192.168.0.19’, 80)”))

2022-08-15 03:02:24.448 WARNING (MainThread) [zigpy_znp.zigbee.application] Your network is using the insecure Zigbee2MQTT network key!

2022-08-15 03:02:24.624 ERROR (MainThread) [pyatv.protocols.airplay] Failed to set up remote control channel
2022-08-15 03:03:47.165 WARNING (MainThread) [aioshelly.block_device] device 192.168.0.19 initialize error - ClientConnectorError(ConnectionKey(host=‘192.168.0.19’, port=80, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=-8625894658308676900), ConnectionRefusedError(111, “Connect call failed (‘192.168.0.19’, 80)”))

2022-08-15 03:04:00.169 WARNING (MainThread) [aioshelly.block_device] device 192.168.0.19 initialize error - ClientConnectorError(ConnectionKey(host=‘192.168.0.19’, port=80, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=-8625894658308676900), ConnectionRefusedError(111, “Connect call failed (‘192.168.0.19’, 80)”))

2022-08-15 03:04:15.170 WARNING (MainThread) [aioshelly.block_device] device 192.168.0.19 initialize error - ClientConnectorError(ConnectionKey(host=‘192.168.0.19’, port=80, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=-8625894658308676900), ConnectionRefusedError(111, “Connect call failed (‘192.168.0.19’, 80)”))

2022-08-15 03:04:24.159 WARNING (MainThread) [aioshelly.block_device] device 192.168.0.19 initialize error - ClientConnectorError(ConnectionKey(host=‘192.168.0.19’, port=80, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=-8625894658308676900), ConnectionRefusedError(111, “Connect call failed (‘192.168.0.19’, 80)”))

2022-08-15 03:04:26.154 WARNING (MainThread) [aioshelly.block_device] device 192.168.0.19 initialize error - ClientConnectorError(ConnectionKey(host=‘192.168.0.19’, port=80, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=-8625894658308676900), ConnectionRefusedError(111, “Connect call failed (‘192.168.0.19’, 80)”))

2022-08-15 03:04:28.165 WARNING (MainThread) [aioshelly.block_device] device 192.168.0.19 initialize error - ClientConnectorError(ConnectionKey(host=‘192.168.0.19’, port=80, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=-8625894658308676900), ConnectionRefusedError(111, “Connect call failed (‘192.168.0.19’, 80)”))

2022-08-15 03:04:32.159 WARNING (MainThread) [aioshelly.block_device] device 192.168.0.19 initialize error - ClientConnectorError(ConnectionKey(host=‘192.168.0.19’, port=80, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=-8625894658308676900), ConnectionRefusedError(111, “Connect call failed (‘192.168.0.19’, 80)”))

2022-08-15 03:04:44.157 WARNING (MainThread) [aioshelly.block_device] device 192.168.0.19 initialize error - ClientConnectorError(ConnectionKey(host=‘192.168.0.19’, port=80, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=-8625894658308676900), ConnectionRefusedError(111, “Connect call failed (‘192.168.0.19’, 80)”))

2022-08-15 03:04:48.160 WARNING (MainThread) [aioshelly.block_device] device 192.168.0.19 initialize error - ClientConnectorError(ConnectionKey(host=‘192.168.0.19’, port=80, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=-8625894658308676900), ConnectionRefusedError(111, “Connect call failed (‘192.168.0.19’, 80)”))

2022-08-15 03:04:51.159 WARNING (MainThread) [aioshelly.block_device] device 192.168.0.19 initialize error - ClientConnectorError(ConnectionKey(host=‘192.168.0.19’, port=80, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=-8625894658308676900), ConnectionRefusedError(111, “Connect call failed (‘192.168.0.19’, 80)”))

2022-08-15 03:04:58.156 WARNING (MainThread) [aioshelly.block_device] device 192.168.0.19 initialize error - ClientConnectorError(ConnectionKey(host=‘192.168.0.19’, port=80, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=-8625894658308676900), ConnectionRefusedError(111, “Connect call failed (‘192.168.0.19’, 80)”))

2022-08-15 03:05:00.156 WARNING (MainThread) [aioshelly.block_device] device 192.168.0.19 initialize error - ClientConnectorError(ConnectionKey(host=‘192.168.0.19’, port=80, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=-8625894658308676900), ConnectionRefusedError(111, “Connect call failed (‘192.168.0.19’, 80)”))

2022-08-15 03:05:00.948 ERROR (MainThread) [pyatv.protocols.airplay] Failed to set up remote control channel

4

First thing that comes to mind network issue.
It wouldn’t surprise if your dhcp lease time is exactly 1 hour?(which would actually confirm my suspicion :thinking:)
What happens if you give HA a static IP?

1 Like
5

Exactly, turned on DHCP, and everything is working!!

Thanks mate!

6

Do you really want DHCP though? Wouldn’t you be better off setting a static IP on your HA? js

1 Like
7

Yes i prefer static because i have Adguard Home installed, but i don’t know what seems to be the issue.

8

Did you set a static IP before you turned on DHCP? If you had set a static IP in a non-DHCP range then you shouldn’t have had an issue that could have been fixed by turning on dhcp.

If you did set a static ip, how did you set it? I’m gonig to guess you set a ‘static lease’ and not a ‘static ip’.

1 Like
9

i have setup static IP right after installing the OS,

my config:

ip adress:
192.168.0.251/32
gateway:
192.168.0.1
dns:
1.1.1.1

10

How? In your router? In HAOS UI? When you set that static ip, is it in the DHCP range? A static IP shouldn’t be in a DHCP range. Alternatively, you could set a ‘static dhcp lease’ in your router so you router will always give the same IP via DHCP.

1 Like
11

Just a tip, instead of using static, use dhcp reservation.
In that way a device will always get the same IP address (based on MAC), and you always have an up-to-date of all your static IP’s at hand😉

Looks like this is what @calisro ment :yum:

I have IP reservations (outside my scope) for all my devices, so i know exactly what IP’s are used and for what (no need to keep a separate list; it’s already in my router, although every now and then i make a backup, so i won’t loose the list in case my router dies)

1 Like
13

In my router i have the DHCP range from 192.168.0.150 to 254 and im setting up the static network in HAOS, i have changed to:

ip adress:
192.168.0.50
gateway:
192.168.0.1
dns:
1.1.1.1

But the entities continue to be off…my router is not that advanced, it doesn´t have dhcp reservation option.

14

After setting that static IP in HA UI, have you rebooted HA RPI?

1 Like
15

yes i did, still the same!

16

What about Simple DHCP addon?

1 Like
17

Will give it a try, thanks!

18

throwing another dhcp server on his network is going to cause conflicts between whats in his current router and whats now being handed by the new server.

How is this going to fix the issue of his current install not getting a static IP and now making his HA installation a requirement to be ‘up’ for other devices to get their dhcp IPs?

1 Like
19

yeah, if you run that, you should disable the router’s dhcp server, but i assumed that was logical :vulcan_salute: