home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.67k stars 30.42k forks source link

Unreliability of HA after a few days #40471

Closed marcgarciamarti closed 3 years ago

marcgarciamarti commented 4 years ago

My HA instance seems to be collapsing randomly after some days running. There is no clear pattern of when that happens. I'm clueless of where to look to provide any log.

Environment

Problem-relevant configuration.yaml

I'm running HA OS on SSD with RPI 3B+ since 9 months or more (can't remember when I enabled that). My db is limited to 2 days with auto-purge. Additional to the USB powered SSD, I also have a C2351, a z-wave dongle and a rfxtrx dongle too. My gut feeling points me to my hardware but I don't have evidence just yet to prove my hunch right or wrong. ```yaml ``` ## Traceback/Error logs I wish I knew what log to provide but when it collapses I just can't log back in, hence no log can be provided. If anybody could possibly provide guidance on how to retrieve logs and where, I would happily get them. ```txt ``` ## Additional information See attached picture with today's behavior ![image](https://user-images.githubusercontent.com/12695572/93942680-30ab9f00-fd31-11ea-8896-45ebf1c6d07a.png)
Spartan-II-117 commented 4 years ago

Do you have samba or say add-ons installed? What you're looking for is a file called homeassistant.log in the configuration directory. Once home-assistant restarts it wipes it out, so you need to grab it before restarting the system

Spartan-II-117 commented 4 years ago

Are you restarting it for it to come online, or does it come back on its own?

If it comes back on its own is the last changed time for your entities recent or sometime before you lost HA?

marcgarciamarti commented 4 years ago

Are you restarting it for it to come online, or does it come back on its own?

If it comes back on its own is the last changed time for your entities recent or sometime before you lost HA?

It does come back up on its own sometimes. Some other times it just freezes and won't even allow me in over ssh. Am I right to say that when HA crashed and the ssh add-on is unresponsive, I should still be able to ssh into the host over port 22222? If I do the later, can I still somehow grab the file you refer earlier?

marcgarciamarti commented 4 years ago

Do you have samba or say add-ons installed? What you're looking for is a file called homeassistant.log in the configuration directory. Once home-assistant restarts it wipes it out, so you need to grab it before restarting the system

I have several add-ons installed. I also have HACS. Today it seems to be working fine, and this is what the cpu load looks like in a normal day.

image

I have several automations in node-red and node-red has been hanging a lot lately. I'm very positive about the fact that my automations could be a lot more eficient but I'm not really skilled to refine them more.

There definitely is something wrong with some of my configurations that kill the Pi.

Spartan-II-117 commented 4 years ago

when it comes back on it's own, try to grab homeassistant.log via either samba or SSH

marcgarciamarti commented 4 years ago

I'll see to it!

marcgarciamarti commented 4 years ago

@Spartan-II-117 for the first time after getting your indications above, my system hung today

Screen Shot 2020-09-26 at 22 52 42

when I logged in over ssh, all I found was the file you referred to above, whose logged activity seems to start right after the system recovered today

~ $ cat /config/home-assistant.log 
2020-09-26 17:44:11 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for nodered which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-09-26 17:44:11 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-09-26 17:44:12 INFO (MainThread) [homeassistant.setup] Setup of domain logger took 0.0 seconds
2020-09-26 17:44:13 INFO (MainThread) [homeassistant.setup] Setting up recorder
2020-09-26 17:44:13 INFO (MainThread) [homeassistant.setup] Setting up http
2020-09-26 17:44:13 INFO (MainThread) [homeassistant.setup] Setup of domain http took 0.0 seconds

is there any way you could think of accessing the information we need?

thanks!

Spartan-II-117 commented 4 years ago

Unfortunately not. Have you tried disabling the custom components for node-red and HACS?

marcgarciamarti commented 4 years ago

Hi again,

no I have not disabled the custom component. I could do that but I really don't have a clear indication it is the culprit. I installed that component long ago and it has been working flawlessly for months. But yes, I guess I could try disabling it. I'm open to doing so.

Look, today for example I catched the system during one of those glitches. Fortunatelly I was allowed to ssh into HA and saw this:

~ $ tail /config/home-assistant.log -f
2020-09-27 16:07:17 INFO (SyncWorker_45) [PyTado.interface] api call result: {"access_token":"xxxxxx.eyJhdWQiOlsicGFydG5lciJdLCJzdWIiOiI1YzAzMDRlNTRjZWRmZDAwMDg4NmJhMzQiLCJuYmYiOjE2MDEyMTU2MzcsInRhZG9fc2NvcGUiOlsiaG9tZS51c2VyIl0sInRhZG9fdXNlcm5hbWUiOiJtYXJjLmdhcmNpYS5tYXJ0aUBnbWFpbC5jb20iLCJpc3MiOiJ0YWRvIiwiZXhwIjoxNjAxMjE2MjM3LCJpYXQiOjE2MDEyMTU2MzcsInRhZG9fY2xpZW50X2lkIjoicHVibGljLWFwaS1wcmV2aWV3IiwianRpIjoiMWEzNGU2ZTktZjUwOS00OTMyLTk5YWUtZjNhNDQyMzAzYzVkIn0.FSa1DnJUiY0FczT_2lzb94EBnm6TeRznuWgX-Q44tDBwGP2OZ_yxlYI1JlD9D0qI3xsMfnqL_d98l5FNx-v85blDZXKZFvYeFrnbgP3VlnZYaNkBd73CLDc71yRCz4-tdmrSuxxxxxxxxxxxxxxxxxxxv1bxays8Wp9G5tgjMZz3JxLr-xC15vFK2EcmWtM_t2xzY2CSWrLgO59ks3BgwLl_7sQ210xSAneeMpezjizZ9ZN8ARYqqtjqk9wYZNMfE1soswX0BilOoJeYkhmwWKXuztqow55TuD4AAccSyF_tEuN1gPL04CtaFetveVumJd9fxvjOsqUYfKGg","token_type":"bearer","refresh_token":"eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOlsicGFydG5lciJdLCJzdWIiOiI1YzAzMDRlNTRjZWRmZDAwMDg4NmJhMzQiLCJuYmYiOjE2MDEyMTU2MzcsInRhZG9fc2NvcGUiOlsiaG9tZS51c2VyIl0sInRhZG9fdXNlcm5hbWUiOiJtYXJjLmdhcmNpYS5tYXJ0aUBnbWFpbC5jb20iLCJhdGkiOiIxYTM0ZTZlOS1mNTA5LTQ5MzItOTlhZS1mM2E0NDIzMDNjNWQiLCJpc3MiOiJ0YWRvIiwiZXhwIjoxNjAzODA3NjM3LCJpYXQiOjE2MDEyMTU2MzcsInRhZG9fY2xpZW50X2lkIjoicHVibGljLWFwaS1wcmV2aWV3IiwianRpIjoiY2IwYTU3ODctZTk5OC00YjAzLTk5NGUtNTA1NTU5MWNmOTg2In0.P8ZDh9HfkZLsI7fyD-ltU6dWY92hcTV-x2uD1Egad4JUIEAyRawVCRbblKEGkR2rQajHspH5gGs7bXmYOOwnzZc14P8Hxdjzye1FtpgpAsk87CkSat8nnoVOt76MUVQKXBMwmHNrdhY8QDlnzbSnAxdAW37C9LLGSUO-os3V5V1XRaDYs9-xxxxxx-utmQXzcMXSjMYx4Dr2x0cHaTXoFsAHBLioFun9MXjJSMb730sqwIvdOQuP707yKag","expires_in":599,"scope":"home.user","jti":"1a34e6e9-f509-4932-99ae-f3a442303c5d"}
2020-09-27 16:07:30 WARNING (MainThread) [homeassistant.components.onvif] Couldn't connect to camera 'A_ONVIF_CAMERA', but will retry later. Error: Cannot connect to host 192.168.1.32:80 ssl:default [Connect call failed ('192.168.1.32', 80)]
2020-09-27 16:07:30 WARNING (MainThread) [homeassistant.config_entries] Config entry for onvif not ready yet. Retrying in 80 seconds
2020-09-27 16:07:39 INFO (Thread-11) [pyhap.hap_server] Got connection with ('192.168.1.196', 51763).
2020-09-27 16:07:39 INFO (Thread-75) [pyhap.hap_server] 192.168.1.196 - "POST /pair-verify HTTP/1.1" 200 -
2020-09-27 16:07:39 INFO (Thread-75) [pyhap.hap_server] 192.168.1.196 - "POST /pair-verify HTTP/1.1" 200 -
2020-09-27 16:07:39 INFO (Thread-75) [pyhap.hap_server] 192.168.1.196 - "GET /accessories HTTP/1.1" 200 -
2020-09-27 16:07:40 INFO (Thread-75) [pyhap.hap_server] 192.168.1.196 - "PUT /characteristics HTTP/1.1" 204 -
2020-09-27 16:08:54 WARNING (MainThread) [homeassistant.components.onvif] Couldn't connect to camera 'A_ONVIF_CAMERA', but will retry later. Error: Cannot connect to host 192.168.1.32:80 ssl:default [Connect call failed ('192.168.1.32', 80)]
2020-09-27 16:08:54 WARNING (MainThread) [homeassistant.config_entries] Config entry for onvif not ready yet. Retrying in 80 seconds
2020-09-27 16:10:18 WARNING (MainThread) [homeassistant.components.onvif] Couldn't connect to camera 'A_ONVIF_CAMERA', but will retry later. Error: Cannot connect to host 192.168.1.32:80 ssl:default [Connect call failed ('192.168.1.32', 80)]
2020-09-27 16:10:18 WARNING (MainThread) [homeassistant.config_entries] Config entry for onvif not ready yet. Retrying in 80 seconds
2020-09-27 16:11:34 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection.1525754824] Disconnected: Did not receive auth message within 10 seconds
2020-09-27 16:11:42 WARNING (MainThread) [homeassistant.components.onvif] Couldn't connect to camera 'A_ONVIF_CAMERA', but will retry later. Error: Cannot connect to host 192.168.1.32:80 ssl:default [Connect call failed ('192.168.1.32', 80)]
2020-09-27 16:11:42 WARNING (MainThread) [homeassistant.config_entries] Config entry for onvif not ready yet. Retrying in 80 seconds
2020-09-27 16:12:43 INFO (Thread-11) [pyhap.hap_server] Got connection with ('192.168.1.196', 51768).
2020-09-27 16:12:43 INFO (Thread-76) [pyhap.hap_server] 192.168.1.196 - "POST /pair-verify HTTP/1.1" 200 -
2020-09-27 16:12:43 INFO (Thread-76) [pyhap.hap_server] 192.168.1.196 - "POST /pair-verify HTTP/1.1" 200 -
2020-09-27 16:12:43 INFO (Thread-76) [pyhap.hap_server] 192.168.1.196 - "GET /accessories HTTP/1.1" 200 -
2020-09-27 16:12:44 INFO (Thread-76) [pyhap.hap_server] 192.168.1.196 - "PUT /characteristics HTTP/1.1" 204 -
2020-09-27 16:13:04 ERROR (MainThread) [homeassistant] Error doing job: Unclosed client session
2020-09-27 16:13:04 ERROR (MainThread) [homeassistant] Error doing job: Unclosed client session
2020-09-27 16:13:04 ERROR (MainThread) [homeassistant] Error doing job: Unclosed client session
2020-09-27 16:13:04 ERROR (MainThread) [homeassistant] Error doing job: Unclosed client session
2020-09-27 16:13:04 ERROR (MainThread) [homeassistant] Error doing job: Unclosed client session
2020-09-27 16:13:04 ERROR (MainThread) [homeassistant] Error doing job: Unclosed client session
2020-09-27 16:13:08 WARNING (MainThread) [homeassistant.components.onvif] Couldn't connect to camera 'A_ONVIF_CAMERA', but will retry later. Error: Cannot connect to host 192.168.1.32:80 ssl:default [Connect call failed ('192.168.1.32', 80)]
2020-09-27 16:13:08 WARNING (MainThread) [homeassistant.config_entries] Config entry for onvif not ready yet. Retrying in 80 seconds
2020-09-27 16:14:32 WARNING (MainThread) [homeassistant.components.onvif] Couldn't connect to camera 'A_ONVIF_CAMERA', but will retry later. Error: Cannot connect to host 192.168.1.32:80 ssl:default [Connect call failed ('192.168.1.32', 80)]
2020-09-27 16:14:32 WARNING (MainThread) [homeassistant.config_entries] Config entry for onvif not ready yet. Retrying in 80 seconds
2020-09-27 16:14:54 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1612912192] Connection closed by client
2020-09-27 16:15:56 WARNING (MainThread) [homeassistant.components.onvif] Couldn't connect to camera 'A_ONVIF_CAMERA', but will retry later. Error: Cannot connect to host 192.168.1.32:80 ssl:default [Connect call failed ('192.168.1.32', 80)]
2020-09-27 16:15:56 WARNING (MainThread) [homeassistant.config_entries] Config entry for onvif not ready yet. Retrying in 80 seconds

I'm wondering if my onvif cameras could be the culprit. I have one camera that is mostly disabled because that is my preference while I'm at home.

Although I asked it earlier, to the risk of sounding a bit tiresome (apologies) I will ask it again: If I ssh into the host over port 22222, is there any chance I can still log into HA and grab the file? I'm sure that's the way forward. Otherwise I will need to keep enabling and disabling stuff and the worst is that the system won't hung immediately after doing any of these changes; one needs to give it some time until it glitches. I'm gonna give this a shot: https://developers.home-assistant.io/docs/operating-system/debugging/#checking-the-logs

marcgarciamarti commented 4 years ago

Ok. I think I have it all set. I've enabled access over ssh on port 22222. Once you do that, you need to type login on the prompt and then

docker logs homeassistant

I really don't know if this will make any difference when home assistant is toasted. If it won't allow me in over ssh, I'm not that confident going through the underlying OS is going to make a difference but we will see.

Spartan-II-117 commented 4 years ago

The onvif stuff mostly seemed to be warnings, but try disabling that camera and see how it goes.

Spartan-II-117 commented 4 years ago

If you are unable to get into the host OS, the problem will s likely with either your particular installation or with your hardware. You could try running a virtual machine with HA from your desktop.

On Tue, Sep 29, 2020, 12:22 marcgarciamarti notifications@github.com wrote:

Hi, my system is currently not responding. I've tried ssh-ing into the HA container and it won't respond. Tried to ssh over port 22222 and it won't react either. I have not disabled the onvif integration just yet (did not get around to doing so). Any idea would be helpful... thanks a million!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/40471#issuecomment-700929869, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABFYSQAAOTK32NIBUW4OLLTSIIXW5ANCNFSM4RWJTRQA .

marcgarciamarti commented 4 years ago

@Spartan-II-117 I seem to have managed to log into the HA container over ssh during one of those blackouts and managed to capture some errors. See the two referenced cases. What do you think?

Spartan-II-117 commented 4 years ago

That tado error looks more serious than the effergy one, as a test, try disabling tado for a few days, if that clears up your instability, put it back together n and enable debug logging for tado, and add the relevant logs to your tado issue.

marcgarciamarti commented 4 years ago

That tado error looks more serious than the effergy one, as a test, try disabling tado for a few days, if that clears up your instability, put it back together n and enable debug logging for tado, and add the relevant logs to your tado issue.

ok. Will do as suggested. For some reason my gut feeling is pointing me towards my SSD. Do you have any idea on how to test the HDD performance and errors? thanks!

Spartan-II-117 commented 4 years ago

Yeah, you can use smart tools to view the drive controller statistics.

freemann commented 4 years ago

Here also "random" restarts of HA since 0.116.0bX Have to say that I've added a ffmpeg_noise sensor to my config, so that could also be cause.

An hour ago I downgraded my Docker image from 0.116.0b3 to 0.115.6 to see of 0.115.6 is stable with my current config. If its stable, then I will upgrade to 0.116.x to see what happens.

marcgarciamarti commented 4 years ago

Hello again @Spartan-II-117 and thanks for your continuous helps throughout this. I've so far disabled the Efergy and Tado integration yet today in the morning the system went down again, even with those components out of the picture. I just collected the logs and this is what I see

2020-10-06 06:00:38 WARNING (MainThread) [homeassistant.components.onvif] Couldn't connect to camera 'A_ONVIF_CAMERA', but will retry later. Error: Cannot connect to host 192.168.1.32:80 ssl:default [Connect call failed ('192.168.1.32', 80)]
2020-10-06 06:00:38 WARNING (MainThread) [homeassistant.config_entries] Config entry for onvif not ready yet. Retrying in 80 seconds
2020-10-06 06:02:02 WARNING (MainThread) [homeassistant.components.onvif] Couldn't connect to camera 'A_ONVIF_CAMERA', but will retry later. Error: Cannot connect to host 192.168.1.32:80 ssl:default [Connect call failed ('192.168.1.32', 80)]
2020-10-06 06:02:02 WARNING (MainThread) [homeassistant.config_entries] Config entry for onvif not ready yet. Retrying in 80 seconds
2020-10-06 06:03:26 WARNING (MainThread) [homeassistant.components.onvif] Couldn't connect to camera 'A_ONVIF_CAMERA', but will retry later. Error: Cannot connect to host 192.168.1.32:80 ssl:default [Connect call failed ('192.168.1.32', 80)]
2020-10-06 06:03:26 WARNING (MainThread) [homeassistant.config_entries] Config entry for onvif not ready yet. Retrying in 80 seconds
2020-10-06 06:04:50 WARNING (MainThread) [homeassistant.components.onvif] Couldn't connect to camera 'A_ONVIF_CAMERA', but will retry later. Error: Cannot connect to host 192.168.1.32:80 ssl:default [Connect call failed ('192.168.1.32', 80)]
2020-10-06 06:04:50 WARNING (MainThread) [homeassistant.config_entries] Config entry for onvif not ready yet. Retrying in 80 seconds
2020-10-06 06:06:13 ERROR (MainThread) [homeassistant] Error doing job: Unclosed client session
2020-10-06 06:06:13 ERROR (MainThread) [homeassistant] Error doing job: Unclosed client session
2020-10-06 06:06:13 ERROR (MainThread) [homeassistant] Error doing job: Unclosed client session
2020-10-06 06:06:13 ERROR (MainThread) [homeassistant] Error doing job: Unclosed client session
2020-10-06 06:06:13 ERROR (MainThread) [homeassistant] Error doing job: Unclosed client session
2020-10-06 06:06:13 ERROR (MainThread) [homeassistant] Error doing job: Unclosed client session
2020-10-06 06:06:16 WARNING (MainThread) [homeassistant.components.onvif] Couldn't connect to camera 'A_ONVIF_CAMERA', but will retry later. Error: Cannot connect to host 192.168.1.32:80 ssl:default [Connect call failed ('192.168.1.32', 80)]
2020-10-06 06:06:16 WARNING (MainThread) [homeassistant.config_entries] Config entry for onvif not ready yet. Retrying in 80 seconds
2020-10-06 06:07:40 WARNING (MainThread) [homeassistant.components.onvif] Couldn't connect to camera 'A_ONVIF_CAMERA', but will retry later. Error: Cannot connect to host 192.168.1.32:80 ssl:default [Connect call failed ('192.168.1.32', 80)]
2020-10-06 06:07:40 WARNING (MainThread) [homeassistant.config_entries] Config entry for onvif not ready yet. Retrying in 80 seconds
2020-10-06 06:09:05 WARNING (MainThread) [homeassistant.components.onvif] Couldn't connect to camera 'A_ONVIF_CAMERA', but will retry later. Error: Cannot connect to host 192.168.1.32:80 ssl:default [Connect call failed ('192.168.1.32', 80)]
2020-10-06 06:09:05 WARNING (MainThread) [homeassistant.config_entries] Config entry for onvif not ready yet. Retrying in 80 seconds
2020-10-06 06:21:23 WARNING (Thread-6) [homeassistant.components.mqtt] Disconnected from MQTT server core-mosquitto:1883 (1)
2020-10-06 06:21:32 INFO (Thread-11) [pyhap.hap_server] Got connection with ('192.168.1.6', 49761).
2020-10-06 06:21:33 INFO (Thread-169) [pyhap.hap_server] 192.168.1.6 - "POST /pair-verify HTTP/1.1" 200 -
2020-10-06 06:21:33 INFO (Thread-169) [pyhap.hap_server] 192.168.1.6 - "POST /pair-verify HTTP/1.1" 200 -
2020-10-06 06:21:34 INFO (Thread-169) [pyhap.hap_server] 192.168.1.6 - "GET /accessories HTTP/1.1" 200 -
2020-10-06 06:21:37 INFO (Thread-169) [pyhap.hap_server] 192.168.1.6 - "PUT /characteristics HTTP/1.1" 204 -
2020-10-06 06:21:39 INFO (Thread-6) [homeassistant.components.mqtt] Connected to MQTT server core-mosquitto:1883 (0)
2020-10-06 06:21:51 INFO (Thread-11) [pyhap.hap_server] Got connection with ('192.168.1.196', 57502).
2020-10-06 06:21:53 INFO (Thread-170) [pyhap.hap_server] 192.168.1.196 - "POST /pair-verify HTTP/1.1" 200 -
2020-10-06 06:21:53 INFO (Thread-170) [pyhap.hap_server] 192.168.1.196 - "POST /pair-verify HTTP/1.1" 200 -
2020-10-06 06:21:54 INFO (Thread-170) [pyhap.hap_server] 192.168.1.196 - "GET /accessories HTTP/1.1" 200 -
2020-10-06 06:21:55 INFO (Thread-170) [pyhap.hap_server] 192.168.1.196 - "PUT /characteristics HTTP/1.1" 204 -
2020-10-06 06:22:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.snmp_switch_netgear_1 is taking over 10 seconds
2020-10-06 06:22:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.snmp_switch_netgear_2 is taking over 10 seconds
2020-10-06 06:22:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.snmp_switch_netgear_3 is taking over 10 seconds
2020-10-06 06:22:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of weather.dark_sky is taking over 10 seconds
2020-10-06 06:22:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of vacuum.xiaomi_vacuum_cleaner is taking over 10 seconds
2020-10-06 06:22:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.season is taking over 10 seconds
2020-10-06 06:22:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.home_assistant_v2_db is taking over 10 seconds
2020-10-06 06:22:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.disk_free is taking over 10 seconds
2020-10-06 06:22:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.ipad_de_marc_battery_level is taking over 10 seconds
2020-10-06 06:22:02 ERROR (MainThread) [homeassistant.components.ipp] Error fetching ipp data: Invalid response from API: Timeout occurred while connecting to IPP server.
2020-10-06 06:22:02 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1742723944] Connection closed by client
2

The system stop responding to my monitoring around 6:12am and started responding at around 6:18am. I can't see any error message in home-assistant.log that may help narrow down what is going on. I've logged into the host on port 22222 and checked the folder /var/log but couldn't see any relevant file.

Do you happen to know where I should look for evidences once I'm in the host? I'm really a beginner when it comes to docker systems. Any information to help me narrow down what is going on would be very much appreciated.

One last thing, even though I don't have evidences pointing towards it,I yesterday jumped the gun and purchased a new enclosure triggered by this https://community.home-assistant.io/t/hass-io-transfer-from-sd-card-to-ssd-or-usb/97452/518?u=kitus

thanks

marcgarciamarti commented 4 years ago

Here also "random" restarts of HA since 0.116.0bX Have to say that I've added a ffmpeg_noise sensor to my config, so that could also be cause.

An hour ago I downgraded my Docker image from 0.116.0b3 to 0.115.6 to see of 0.115.6 is stable with my current config. If its stable, then I will upgrade to 0.116.x to see what happens.

I'm still running version 0.115.x but this random lockups have been happening to me for several weeks/months I would say (I can't really put my finger on it though). Do you happen to know how to check logging on the host? thanks!

Spartan-II-117 commented 4 years ago

I'm afraid that I can't help you any further, it appears that all your integration issues are likely being caused by your hardware. Upgrading to an SSD (or a NUC) will hopefully solve your issues. If you continue having issues I would suggest starting from scratch and add one component at a time to see where the problem starts occuring.

bdraco commented 3 years ago

Please try to get a py-spy and a profile when this happens

https://community.home-assistant.io/t/python3-high-cpu-usage/160012

marcgarciamarti commented 3 years ago

Hello,

quick update: by disabling both InfluxDB and Grafana, my setup has gone back to normal. No more issues. The only thing is that I've lost my ability to have insights into my environment. 2 weeks so far now with a solid environment.

I've disabled this after much of a trial and error. I would rather have preferred to be able to conclude that but at least I am really not aware how to do so. Neither of the logs that I've reviewed pointed towards those two add-ons.

I could now close this case but if I did that, nobody would evaluate if there is any room for improving the logging of the system.

Regards

github-actions[bot] commented 3 years ago

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.