Hi all.
Suddenly all my HACS addons keep switching off by themselves.
I switch on the “watchdog” option but it doesn’t work and every time I look at the HACS page after a stop all the watchdog switches are disabled.
Any idea what is going on?
Thank you
Andrea
Do you have anything in the addon logs?
Thank you very much for you replay . I took a look on logs and I did’t notice nothing of clearly broken. But maybe I am looking in th ewrong place in the wrong time .
I took a look in Settings - system - logs. But maybe I have to look elsewere .
I have home-assistant.log.1 home-assistant.log home-assistant.log.fault .
I am sorry but I never undestood whel how Homeassitant manage logs files
My logger.yaml is
default: warning
thank you
Go into your addon and click the log button (top or bottom of screen depending on size of your device), or in settings → system logs, top of screen where it says Homeassistant Core you can select different logs. Should find your addons in this list
There is no such thing as HACS addons.
HACS is only for custom components
I’m not sure what you are looking at.
The HA (not HACS) addon page doesn’t have a view that would tell you all watchdogs are disabled.
I am sorry I am using the wrong words . I am having problems with addons , non HACS 
Edited the title hope now it is ok
Ok I managed to grab all the logs of the addons.
The problem showed up at 05:30 am, usually, this happens in the night I don’t know if the cause could be my irrigation system that starts at that hour.
This time some addons survived es: frigate.
All add-ons have start on boot and watchdog enabled, after the stop all the watchdog switches are back to off.
If I restart home assistant all the addons remain off , I need to reboot
It seems to me all addons simply stop and don’t restart. Any idea?
Zigbee2MQTT
[
[2024-06-16 05:30:09] debug: zh:zstack:znp: SREQ: --> SYS - nvRead - {"sysid":1,"itemid":7,"subid":4,"offset":0,"len":12}
[2024-06-16 05:30:09] debug: zh:zstack:unpi:writer: --> frame [254,8,33,51,1,7,0,4,0,0,0,12,20]
[2024-06-16 05:30:09] debug: zh:zstack:unpi:parser: <-- [254,14,97,51,0,12,144,162,73,0,255,255,255,255,255,255,255,255,43]
[2024-06-16 05:30:09] debug: zh:zstack:unpi:parser: --- parseNext [254,14,97,51,0,12,144,162,73,0,255,255,255,255,255,255,255,255,43]
[2024-06-16 05:30:09] debug: zh:zstack:unpi:parser: --> parsed 14 - 3 - 1 - 51 - [0,12,144,162,73,0,255,255,255,255,255,255,255,255] - 43
[2024-06-16 05:30:09] debug: zh:zstack:znp: SRSP: <-- SYS - nvRead - {"status":0,"len":12,"value":{"type":"Buffer","data":[144,162,73,0,255,255,255,255,255,255,255,255]}}
[2024-06-16 05:30:09] debug: zh:zstack:unpi:parser: --- parseNext []
[2024-06-16 05:30:09] debug: zh:zstack:znp: SREQ: --> SYS - nvLength - {"sysid":1,"itemid":7,"subid":5}
[2024-06-16 05:30:09] debug: zh:zstack:unpi:writer: --> frame [254,5,33,50,1,7,0,5,0,21]
[2024-06-16 05:30:09] debug: zh:zstack:unpi:parser: <-- [254,4,97,50,0,0,0,0,87]
[2024-06-16 05:30:09] debug: zh:zstack:unpi:parser: --- parseNext [254,4,97,50,0,0,0,0,87]
[2024-06-16 05:30:09] debug: zh:zstack:unpi:parser: --> parsed 4 - 3 - 1 - 50 - [0,0,0,0] - 87
[2024-06-16 05:30:09] debug: zh:zstack:znp: SRSP: <-- SYS - nvLength - {"len":0}
[2024-06-16 05:30:09] debug: zh:zstack:unpi:parser: --- parseNext []
[2024-06-16 05:30:09] debug: zh:zstack:backup: fetched adapter network security material table (capacity=2, used=2)
[2024-06-16 05:30:09] debug: zh:zstack:backup: Following devices with link key are missing from new backup but present in old backup and database, adding them back:
[2024-06-16 05:30:09] info: zh:controller: Wrote coordinator backup to '/config/zigbee2mqtt/coordinator_backup.json'
[2024-06-16 05:30:09] info: zh:zstack:znp: closing
[2024-06-16 05:30:09] info: zh:zstack:znp: Port closed
[2024-06-16 05:30:09] info: z2m: Stopped zigbee-herdsman
[2024-06-16 05:30:09] info: z2m: Stopped Zigbee2MQTT
AdGuard Home
2024/06/15 21:12:10.654487 [error] dnsproxy: 8.8.6.6:53: response received over udp: "exchanging with 8.8.6.6:53 over udp: read udp 192.168.0.62:53442->8.8.6.6:53: i/o timeout"
2024/06/15 21:12:12.363482 [info] filtering: saving contents of filter 1688134138 into "/data/adguard/data/filters/1688134138.txt"
2024/06/15 21:12:12.376916 [info] filtering: updated filter 1688134138: 4544310 bytes, 211218 rules
2024/06/15 21:12:12.376941 [info] filtering: updated filter 1688134138; rule count: 211218 (was 210859)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service discovery: stopping
s6-rc: info: service nginx: stopping
s6-rc: info: service discovery successfully stopped
[05:29:05] INFO: Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service adguard: stopping
s6-rc: info: service init-nginx successfully stopped
2024/06/16 05:29:05.748428 [info] Received signal "terminated"
2024/06/16 05:29:05.748491 [info] stopping AdGuard Home
2024/06/16 05:29:05.748496 [info] stopping http server...
2024/06/16 05:29:05.748883 [info] stopped http server
2024/06/16 05:29:05.748927 [info] dnsproxy: stopping server
2024/06/16 05:29:05.749311 [info] dnsproxy: stopped dns proxy server
2024/06/16 05:29:05.752549 [error] querylog: closing: flushing log buffer: nothing to write to a file
2024/06/16 05:29:05.752657 [info] stopped
[05:29:05] INFO: Service Adguard Home exited with code 0 (by signal 0)
s6-rc: info: service adguard successfully stopped
s6-rc: info: service init-adguard: stopping
s6-rc: info: service init-adguard successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
ESPHome
2024-06-16 04:18:35,371 INFO 200 GET /devices (0.0.0.0) 2.16ms
2024-06-16 04:23:35,369 INFO 200 GET /devices (0.0.0.0) 2.96ms
2024-06-16 04:28:35,370 INFO 200 GET /devices (0.0.0.0) 2.78ms
2024-06-16 04:33:35,371 INFO 200 GET /devices (0.0.0.0) 3.07ms
2024-06-16 04:38:35,367 INFO 200 GET /devices (0.0.0.0) 2.09ms
2024-06-16 04:43:35,370 INFO 200 GET /devices (0.0.0.0) 2.92ms
2024-06-16 04:48:35,372 INFO 200 GET /devices (0.0.0.0) 4.10ms
2024-06-16 04:53:35,369 INFO 200 GET /devices (0.0.0.0) 2.85ms
2024-06-16 04:58:35,365 INFO 200 GET /devices (0.0.0.0) 1.28ms
2024-06-16 05:03:35,370 INFO 200 GET /devices (0.0.0.0) 3.46ms
2024-06-16 05:08:35,366 INFO 200 GET /devices (0.0.0.0) 1.48ms
2024-06-16 05:13:35,369 INFO 200 GET /devices (0.0.0.0) 2.78ms
2024-06-16 05:18:35,372 INFO 200 GET /devices (0.0.0.0) 3.50ms
2024-06-16 05:23:35,375 INFO 200 GET /devices (0.0.0.0) 4.25ms
2024-06-16 05:28:35,376 INFO 200 GET /devices (0.0.0.0) 2.57ms
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service discovery: stopping
s6-rc: info: service discovery successfully stopped
s6-rc: info: service nginx: stopping
[05:29:15] INFO: Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service esphome: stopping
s6-rc: info: service init-nginx successfully stopped
[05:29:15] INFO: Service ESPHome dashboard exited with code 256 (by signal 15)
s6-rc: info: service esphome successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-timezone: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service base-addon-timezone successfully stopped
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Mosquitto broker
2024-06-16 04:57:28: Client shellyht-F3916E has exceeded timeout, disconnecting.
2024-06-16 04:59:21: New connection from 172.30.32.2:48606 on port 1883.
2024-06-16 04:59:21: Client <unknown> closed its connection.
2024-06-16 05:00:42: Saving in-memory database to /data//mosquitto.db.
2024-06-16 05:01:21: New connection from 172.30.32.2:39088 on port 1883.
2024-06-16 05:01:21: Client <unknown> closed its connection.
2024-06-16 05:01:46: Client Nuki_3CFEF274 closed its connection.
2024-06-16 05:01:51: New connection from 192.168.0.118:62781 on port 1883.
2024-06-16 05:01:52: New client connected from 192.168.0.118:62781 as Nuki_3CFEF274 (p2, c1, k300, u'mqttuser').
2024-06-16 05:03:21: New connection from 172.30.32.2:44530 on port 1883.
2024-06-16 05:03:21: Client <unknown> closed its connection.
2024-06-16 05:04:24: New connection from 192.168.0.48:64104 on port 1883.
2024-06-16 05:04:24: New client connected from 192.168.0.48:64104 as shellyht-F3916E (p2, c1, k60, u'mqttuser').
2024-06-16 05:05:21: New connection from 172.30.32.2:55936 on port 1883.
2024-06-16 05:05:21: Client <unknown> closed its connection.
2024-06-16 05:06:04: Client shellyht-F3916E has exceeded timeout, disconnecting.
2024-06-16 05:07:21: New connection from 172.30.32.2:53516 on port 1883.
2024-06-16 05:07:21: Client <unknown> closed its connection.
2024-06-16 05:08:57: New connection from 192.168.0.48:58475 on port 1883.
2024-06-16 05:08:57: New client connected from 192.168.0.48:58475 as shellyht-F3916E (p2, c1, k60, u'mqttuser').
2024-06-16 05:09:21: New connection from 172.30.32.2:42304 on port 1883.
2024-06-16 05:09:21: Client <unknown> closed its connection.
2024-06-16 05:10:34: Client shellyht-F3916E has exceeded timeout, disconnecting.
2024-06-16 05:11:21: New connection from 172.30.32.2:59304 on port 1883.
2024-06-16 05:11:21: Client <unknown> closed its connection.
2024-06-16 05:13:21: New connection from 172.30.32.2:37692 on port 1883.
2024-06-16 05:13:21: Client <unknown> closed its connection.
2024-06-16 05:15:21: New connection from 172.30.32.2:48240 on port 1883.
2024-06-16 05:15:21: Client <unknown> closed its connection.
2024-06-16 05:17:22: New connection from 172.30.32.2:40476 on port 1883.
2024-06-16 05:17:22: Client <unknown> closed its connection.
2024-06-16 05:17:57: New connection from 192.168.0.48:57992 on port 1883.
2024-06-16 05:17:57: New client connected from 192.168.0.48:57992 as shellyht-F3916E (p2, c1, k60, u'mqttuser').
2024-06-16 05:19:22: New connection from 172.30.32.2:35470 on port 1883.
2024-06-16 05:19:22: Client <unknown> closed its connection.
2024-06-16 05:19:34: Client shellyht-F3916E has exceeded timeout, disconnecting.
2024-06-16 05:21:22: New connection from 172.30.32.2:36406 on port 1883.
2024-06-16 05:21:22: Client <unknown> closed its connection.
2024-06-16 05:22:49: Client Nuki_3CFEF274 closed its connection.
2024-06-16 05:22:54: New connection from 192.168.0.118:57187 on port 1883.
2024-06-16 05:22:55: New client connected from 192.168.0.118:57187 as Nuki_3CFEF274 (p2, c1, k300, u'mqttuser').
2024-06-16 05:23:22: New connection from 172.30.32.2:49884 on port 1883.
2024-06-16 05:23:22: Client <unknown> closed its connection.
2024-06-16 05:25:22: New connection from 172.30.32.2:35592 on port 1883.
2024-06-16 05:25:22: Client <unknown> closed its connection.
2024-06-16 05:26:57: New connection from 192.168.0.48:62635 on port 1883.
2024-06-16 05:26:57: New client connected from 192.168.0.48:62635 as shellyht-F3916E (p2, c1, k60, u'mqttuser').
2024-06-16 05:27:22: New connection from 172.30.32.2:59810 on port 1883.
2024-06-16 05:27:22: Client <unknown> closed its connection.
2024-06-16 05:28:34: Client shellyht-F3916E has exceeded timeout, disconnecting.
2024-06-16 05:29:22: New connection from 172.30.32.2:49594 on port 1883.
2024-06-16 05:29:22: Client <unknown> closed its connection.
2024-06-16 05:29:23: Client frigate disconnected.
s6-rc: info: service legacy-services: stopping
[03:29:36] INFO: Service restart after closing
2024-06-16 05:29:36: mosquitto version 2.0.18 terminating
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/acl\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/acl\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/acl\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/acl\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/acl\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/acl\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/acl\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/acl\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/acl\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/acl\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/acl\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="POST error: Post \"http://127.0.0.1:80/acl\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2024-06-16T05:29:36+02:00" level=error msg="Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
2024-06-16 05:29:36: Saving in-memory database to /data//mosquitto.db.
[03:29:36] INFO: Service restart after closing
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Samba share
idmap range not specified for domain '*'
idmap range not specified for domain '*'
idmap range not specified for domain '*'
idmap range not specified for domain '*'
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
create_connection_session_info: guest user (from session setup) not permitted to access this share (config)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
idmap range not specified for domain '*'
idmap range not specified for domain '*'
idmap range not specified for domain '*'
idmap range not specified for domain '*'
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nmbd: stopping
Got SIGTERM: going down...
[05:29:40] INFO: Service nmbd exited with code 0 (by signal 0)
s6-rc: info: service nmbd successfully stopped
s6-rc: info: service smbd: stopping
[05:29:40] INFO: Service smbd exited with code 256 (by signal 15)
s6-rc: info: service smbd successfully stopped
s6-rc: info: service init-smbd: stopping
s6-rc: info: service init-smbd successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[05:29:51] INFO: Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service php-fpm: stopping
s6-rc: info: service init-nginx successfully stopped
[05:29:51] INFO: Service PHP-FPM exited with code 0 (by signal 0)
s6-rc: info: service php-fpm successfully stopped
s6-rc: info: service init-tasmoadmin: stopping
s6-rc: info: service init-tasmoadmin successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Seems like all related to Network - Proxy Issues ( Auth. ? )
I Assume you also looked at your Core-Supervisor-Host log-files ?
Thank you for your feedback,I checked the log of supervisor in setting system logs but it was available only for the last hours can you tell me , next time the problem will occur where I can find the full logs?
I am not using a proxy.
Well, i just mentioned it to “verify” that you also very these logs , Supervisor-log is most likely not relevant.
Core would be
By excluding i.e Core ( By Running in “Safe Mode” Around the time it occurs " That is if it’s actually happens the same time every Day, or after a specific time" )
Safe-Mode exclude Add-ons/Integrations on after reboot
General troubleshooting - Home Assistant.
The “New” extensive Troubleshooting Guide could be your Next Step
2024.5+: Tracking down instability issues caused by integrations.
But First make sure you have your " Network Settings" under Control, i.e NGINX / Proxy /Authentication
You “Copied/Pasted” you “output” from various Logs.
However you never took the time to read them first, So you could have Posted them in a " Time-Line Manner "
Structure your Analyses in a Time-Line, would give you a better “Overview”
My Suggestion would be to Disable Adguard Home, And as mention,make sure your “Proxy Settings/Authentification” is Correct
Edit: I don’t know from where and why a “terminated” signal was received, nor which other i.e cloud-depended Integrations you are Running ( Sure your Irrigation could be depended upon the Cloud, So if you suspect this to be the cause, Disable It !, for a few days( Including templates/automation/scripts related to this ! ) ( Best way to exclude an Integration like that, as the cause )
However actually your ESP and Mosquitto( shellyht-F3916E has exceeded timeout ) seems to “complain” first , But i also don’t know if i.e Mq is an external server etc.
Isn’t that the time when there is a ?rollover/maintenance/…? in the DB?
I think DB-Maintenance is around 02.00AM, prick … Not You, but exact-time 
Hmmm, maybe You are right, there is some at 04.12am
However ones when i had Debug on the “Purge” occurred 02.00am
Thank you for your help, Maybe I found the problem. Home assistant Google Drive backup stopped all the addons before doing the backup but seems unable to restart after the backup is done. I switched off that option, let see what will happen.
By the way, I swear I tried to read the log but it is very difficult to understand what is happening for a simple home assistant user like me without high knowledge of Linux or advanced PC programming, imho.