#Hi all I keep running into this Unable
1 messages ยท Page 1 of 1 (latest)
Were your problems on the same device before?
I'd guess that the problem is that your device is losing WiFi connection 
No, I'm using a usb network adapter, I'm not running a server on wifi, and the network is up because I can ping the ip and I can see the home assistant screen except it says "Unable to connect to Home Assistant. retry in X seconds"
Then check the logs
Both Supervisor, Host, and Core
The HA screen is cached by your browser ๐
I couldn't find any log that right around the time when it's happening, for example, it happened again this morning around 7:10 or so, this is the core logs:
[140610892975552] from 72.143.232.94 (Mozilla/5.0 (Linux; Android 12; GM1917 Build/SKQ1.211113.001; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/117.0.0.0 Mobile Safari/537.36 Home Assistant/2023.9.2-11226 (Android 12; GM1917)): Disconnected: Did not receive auth message within 10 seconds
7:28:54 AM โ (WARNING) Home Assistant WebSocket API
Invalid state specified for light.smart_plug_03_green_led: unavailable
7:00:00 AM โ (WARNING) Light
m5clock-chain @ 10.0.0.144: Connection error occurred: [Errno 104] Connection reset by peer
5:00:44 AM โ (WARNING) runner.py - message first occurred at October 10, 2023 at 10:44:58 PM and shows up 12 times
[Living Room speaker(10.0.0.11):8009] Failed to connect to service ServiceInfo(type='host', data=('10.0.0.11', 8009)), retrying in 5.0s
5:00:29 AM โ (ERROR) /usr/local/lib/python3.11/site-packages/pychromecast/socket_client.py - message first occurred at 3:23:09 AM and shows up 7 times
[Living Room speaker(10.0.0.11):8009] Heartbeat timeout, resetting connection
5:00:20 AM โ (WARNING) /usr/local/lib/python3.11/site-packages/pychromecast/socket_client.py - message first occurred at 3:22:54 AM and shows up 5 times
[Home group(10.0.0.12):32237] Error communicating with socket, resetting connection
4:52:33 AM โ (WARNING) /usr/local/lib/python3.11/site-packages/pychromecast/socket_client.py - message first occurred at 4:51:46 AM and shows up 2 times
[Home group(10.0.0.12):32237] Error reading from socket.
4:52:33 AM โ (ERROR) /usr/local/lib/python3.11/site-packages/pychromecast/socket_client.py - message first occurred at 4:51:46 AM and shows up 2 times```
here's the supervisor logs:
23-10-11 06:44:23 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
23-10-11 07:13:45 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running
23-10-11 07:13:45 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/system
23-10-11 07:13:45 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server
23-10-11 07:13:45 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core
23-10-11 07:13:45 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
23-10-11 07:13:45 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system
23-10-11 07:13:45 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system
23-10-11 07:13:45 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addon
23-10-11 07:13:45 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server
23-10-11 07:13:45 INFO (MainThread) [supervisor.resolution.checks.base] Run check for trust/supervisor
23-10-11 07:13:45 INFO (MainThread) [supervisor.resolution.check] System checks complete
23-10-11 07:13:45 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
23-10-11 07:13:45 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
23-10-11 07:13:45 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
23-10-11 07:13:45 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
23-10-11 07:14:17 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
23-10-11 07:14:24 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
for the host logs, I've no idea where to look, the time it shows is in the future like this:
Oct 11 13:50:01 homeassistant systemd-timesyncd[420]: Network configuration changed, trying to establish connection.
Oct 11 13:50:01 homeassistant systemd[1]: Started Journal Gateway Service.
Oct 11 13:50:01 homeassistant systemd-timesyncd[420]: Contacted time server 162.159.200.1:123 (time.cloudflare.com).
Oct 11 13:50:02 homeassistant systemd-journal-gatewayd[12493]: microhttpd: MHD_OPTION_EXTERNAL_LOGGER is not the first option specified for the daemon. Some messages may be printed by the standard MHD logger.```
@supple granite When using Discord's Reply feature it defaults to pinging the person you reply to, which can get frustrating for the target. Use Shift + click on the Reply option, or click @ ON to @ OFF to stop this - on the right side of the compose bar.
You have to change this every time (thank the Discord devs for that).
it does have a systemd-timesyncd[420] error that seems weird, but other than that I don't see anything out of place, also while posting this, I lost connection to my HA again...
Go looking for logs for the time you lose connection
the logs I'm posting is around the time I lost connection the 1st time, except the host logs like I said, the time isn't correct for that
sorry I don't see that option, I don't use discord a lot...
And the image shows the option when you use Reply
Just look on the right, where you see those other icons
ok found it, sorry about that
The only other thing to do is to check the Observer port, and any other add-ons that have their own UI
Port 4357 rather than 8123
Supervisor: Connected
Supported: Supported
Healthy: Healthy ```
Right, but the next time you have problems, check then ๐
I can't connect right now, the web ui is still saying "Unable to connect to Home Assistant."
Worth doing - much easier to debug stuff like this
Because Samba doesn't give you all the logs
ah... got you, I will go find some tutorial online to see how to setup SSH next time I can go in
interesting how the observer says everything is working but I can't even log in the UI...
Points to a problem with Core, probably
ok got SSH set up, when trying to connect, I'm guess the user name is my username in HA settings? and hostname should just be my ip address right?
ssh: connect to host 10.0.0.40 port 22: Connection refused
wish I can send screenshots, but yeah I added in my public key via the UI and started the addon without any issue
Please use imgur or other image sharing web sites, and share the link here.
Image posting is blocked in most channels to discourage people from sharing text as images. Sharing text as images assumes that everybody sees the world as you do, which isn't the case. Some people are colour blind, or have visual impairment that means they can't make sense of an image of text.
https://imgur.com/a/N8eIiEs, while grabbing the screenshot, I lost connection to the UI again ๐
I don't see a place to put in username in the addon configuration, it's not using the HA username?
i think this is the problem: [08:10:08] WARNING: SSH port is disabled. Prevent start of SSH server.
ok looking into the docs right now: ```To enable SSH connectivity, you need to:
Provide authentication credentials - a password or SSH key(s)
Specify which TCP port to bind to, on the Home Assistant host
You can then connect to the port specified, using the username root.```
ok finally got it working, I can remote in now if it loses connection again, but I'm a total linux noob, what log should I be look into? ~/config/home-assistant.log?
That, plus Supervisor and Host
Hi sorry to bug you again after so long, it's been running fine since last time when we talked on Oct 11th, but today it's starting to crash almost every hour again. ๐
I check the home-assistant, supervisor and host logs but couldn't find anything interesting.
The only thing that's standing out a bit to me is the host logs all have the wrong time in the entries, like this:
Oct 25 17:42:48 homeassistant systemd[1]: Starting Time & Date Service...
Oct 25 17:42:48 homeassistant systemd[1]: Started Time & Date Service.
Oct 25 17:43:18 homeassistant systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Oct 25 17:43:18 homeassistant kernel: audit: type=1334 audit(1698255798.752:2311): prog-id=1084 op=UNLOAD
Oct 25 17:43:18 homeassistant kernel: audit: type=1334 audit(1698255798.752:2312): prog-id=1083 op=UNLOAD
Oct 25 17:43:18 homeassistant kernel: audit: type=1334 audit(1698255798.752:2313): prog-id=1082 op=UNLOAD
Oct 25 17:43:18 homeassistant systemd[1]: systemd-timedated.service: Deactivated successfully.
Oct 25 17:43:19 homeassistant kernel: audit: type=1334 audit(1698255799.010:2314): prog-id=1087 op=UNLOAD
Oct 25 17:43:19 homeassistant kernel: audit: type=1334 audit(1698255799.010:2315): prog-id=1086 op=UNLOAD
Oct 25 17:43:19 homeassistant kernel: audit: type=1334 audit(1698255799.010:2316): prog-id=1085 op=UNLOAD
Oct 25 17:44:09 homeassistant NetworkManager[349]: <info> [1698255849.3140] dhcp4 (enp0s20f0u1u3): state changed new lease, address=10.0.0.40
the observer shows everything is fine:
Home Assistant observer
Supervisor: Connected
Supported: Supported
Healthy: Healthy
The time is UTC
so these messages are fine?
The times are likely fine
this is from home-assistant.log around the time it last crashed:
2023-10-25 12:32:56.413 WARNING (Thread-7) [pychromecast.socket_client] [Living Room speaker(10.0.0.11):8009] Heartbeat timeout, resetting connection
2023-10-25 12:33:26.447 ERROR (Thread-7) [pychromecast.socket_client] [Living Room speaker(10.0.0.11):8009] Failed to connect to service ServiceInfo(type='host', data=('10.0.0.11', 8009)), retrying in 5.0s
2023-10-25 12:42:54.830 ERROR (MainThread) [homeassistant.components.google_assistant.http] Request for https://homegraph.googleapis.com/v1/devices:reportStateAndNotification failed: 503
2023-10-25 12:45:42.473 ERROR (MainThread) [homeassistant.components.google_assistant.http] Request for https://homegraph.googleapis.com/v1/devices:reportStateAndNotification failed: 503
and this is from the supervisor log:
23-10-25 12:16:31 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/esphome/home-assistant-addon repository
23-10-25 12:16:31 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/addons repository
23-10-25 12:16:31 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
23-10-25 12:16:33 INFO (MainThread) [supervisor.store] Loading add-ons from store: 72 all - 0 new - 0 remove
23-10-25 12:16:33 INFO (MainThread) [supervisor.store] Loading add-ons from store: 72 all - 0 new - 0 remove
23-10-25 12:20:12 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
23-10-25 12:50:13 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
23-10-25 12:53:29 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from core_ssh
23-10-25 12:53:29 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from core_ssh
23-10-25 12:53:29 INFO (MainThread) [supervisor.api.middleware.security] /host/info access from core_ssh
23-10-25 12:53:29 INFO (MainThread) [supervisor.api.middleware.security] /core/info access from core_ssh
see anything out of the ordinary?
oh and it crashed around 12:40
Well... if that crashed at 12:40 UTC then the logs show no such crash
that's the weird part about this, during the crash, I can't open the web interface, but the observer shows everything as fine
There's no sign of any crash in the log
If HA had restarted you'd have a fresh log file
oh ok, so is there any other reason I couldn't access the web ui? By the way I'm using duckdns to access it, I also tried direct local ip in case this is related to duckdns, but same problem
wired, through a tp-link switch, there's also a raspberry pi connecting to the same switch. I tried to connect to the pi during the crash, no problem at all
What hardware is it on? Have you tried a different switch port and cable?
It's on my old surface pro 4, I didn't try a different port yet, because I can still access the observer during the crash which is on the same server, I can also SSH into the server, so I assume the network connection is good
this is really frustrating, especially when the same exact issue was also present in my docker installation, that's the reason I switched to HaOS because people say it's more stable ๐