Perte de Home Assistant + 2 thermostats pendant la nuit

mbdrlp · Mars 6, 2025, 2:29

Bonjour à tous,

cette nuit j’ai eu une mauvaise surprise sur mon Home Assistant. Je l’ai comme perdu quelques minutes pour une raison encore inconnu. Mais le plus genant dans tout ça, c’est que j’ai deux thermostats qui n’ont pas retrouvé leur état d’avant, et qui ont été setté à 5°C (les deux sur un reseau ZWave)

Lorsque je regarde mon Logbook, il y a un trou entre 12h17 et 12h21

Du coté du log du superviseur:

2025-03-06 00:19:19.327 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 258
2025-03-06 00:19:19.376 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API for a0d7b954_nodered closed
2025-03-06 00:19:39.319 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.
2025-03-06 00:19:55.304 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.
2025-03-06 00:20:31.355 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.
2025-03-06 00:20:36.305 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.
2025-03-06 00:20:49.434 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.
2025-03-06 00:20:49.815 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.
2025-03-06 00:20:49.821 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.
2025-03-06 00:20:49.827 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.
2025-03-06 00:20:49.842 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.
2025-03-06 00:20:49.851 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.
2025-03-06 00:21:05.027 WARNING (MainThread) [supervisor.misc.tasks] Watchdog missing application response from core_mosquitto
2025-03-06 00:21:09.619 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.
2025-03-06 00:21:19.153 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'mqtt'

Le log du Host (il se pase beaucoup de choses…)

2025-03-06 05:16:22.949 homeassistant systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

2025-03-06 05:17:43.684 homeassistant kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

2025-03-06 05:17:43.689 homeassistant kernel: ata1.00: failed command: FLUSH CACHE

2025-03-06 05:17:43.689 homeassistant kernel: ata1.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0

res 40/00:02:00:08:00/00:00:00:00:00/b0 Emask 0x4 (timeout)

2025-03-06 05:17:43.689 homeassistant kernel: ata1.00: status: { DRDY }

2025-03-06 05:17:48.696 homeassistant kernel: ata1: link is slow to respond, please be patient (ready=0)

2025-03-06 05:17:53.697 homeassistant kernel: ata1: device not ready (errno=-16), forcing hardreset

2025-03-06 05:17:53.699 homeassistant kernel: ata1: soft resetting link

2025-03-06 05:19:03.447 homeassistant kernel: clocksource: Long readout interval, skipping watchdog check: cs_nsec: 69667545392 wd_nsec: 69667539851

2025-03-06 05:19:03.486 homeassistant kernel: ata1.00: configured for MWDMA2

2025-03-06 05:19:03.486 homeassistant kernel: ata1.01: configured for MWDMA2

2025-03-06 05:19:03.486 homeassistant kernel: ata1.00: retrying FLUSH 0xe7 Emask 0x4

2025-03-06 05:19:03.486 homeassistant kernel: ata1: EH complete

2025-03-06 05:19:33.726 homeassistant dockerd[521]: time="2025-03-06T05:19:33.723948279Z" level=warning msg="Health check for container 636d9e0ef4533ff36aa8df559b2f1ed4fa398b3a4ba708d2670d54c3c277cde9 error: timed out starting health check for container 636d9e0ef4533ff36aa8df559b2f1ed4fa398b3a4ba708d2670d54c3c277cde9"

2025-03-06 05:19:33.936 homeassistant dockerd[521]: time="2025-03-06T05:19:33.935415646Z" level=warning msg="Health check for container 11e2d6ec65ced65d1ea478c42ef41ad9a3ac2061ffb6d02a2c40ee94f17d7a42 error: timed out starting health check for container 11e2d6ec65ced65d1ea478c42ef41ad9a3ac2061ffb6d02a2c40ee94f17d7a42"

2025-03-06 05:20:26.023 homeassistant NetworkManager[380]: <info> [1741238426.0209] dhcp4 (enp0s3): state changed new lease, address=192.168.0.40

2025-03-06 05:20:26.064 homeassistant NetworkManager[380]: <info> [1741238426.0361] dhcp4 (enp0s3): activation: beginning transaction (timeout in 45 seconds)

2025-03-06 05:20:26.065 homeassistant NetworkManager[380]: <info> [1741238426.0366] dhcp4 (enp0s3): state changed no lease

2025-03-06 05:20:26.065 homeassistant NetworkManager[380]: <info> [1741238426.0462] dhcp4 (enp0s3): state changed new lease, address=192.168.0.40

2025-03-06 05:20:26.239 homeassistant systemd[1]: Starting Network Manager Script Dispatcher Service...

2025-03-06 05:20:26.426 homeassistant systemd[1]: Started Network Manager Script Dispatcher Service.

2025-03-06 05:20:36.496 homeassistant systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

2025-03-06 05:20:36.674 homeassistant kernel: CIFS: VFS: \\192.168.0.10 has not responded in 180 seconds. Reconnecting...

2025-03-06 05:21:33.769 homeassistant systemd[1]: Starting Network Manager Script Dispatcher Service...

2025-03-06 05:21:33.795 homeassistant systemd[1]: Started Network Manager Script Dispatcher Service.

2025-03-06 05:21:43.814 homeassistant systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

2025-03-06 05:21:43.918 homeassistant NetworkManager[380]: <info> [1741238503.9163] dhcp4 (enp0s3): state changed new lease, address=192.168.0.40

2025-03-06 05:21:43.966 homeassistant systemd[1]: Starting Network Manager Script Dispatcher Service...

2025-03-06 05:21:44.002 homeassistant systemd[1]: Started Network Manager Script Dispatcher Service.

2025-03-06 05:21:54.048 homeassistant systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

2025-03-06 05:22:29.716 homeassistant NetworkManager[380]: <info> [1741238549.7164] dhcp4 (enp0s3): state changed new lease, address=192.168.0.40

2025-03-06 05:22:29.761 homeassistant systemd[1]: Starting Network Manager Script Dispatcher Service...

2025-03-06 05:22:29.780 homeassistant systemd[1]: Started Network Manager Script Dispatcher Service.

2025-03-06 05:22:39.808 homeassistant systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

2025-03-06 05:23:23.496 homeassistant NetworkManager[380]: <info> [1741238603.4950] dhcp4 (enp0s3): state changed new lease, address=192.168.0.40

2025-03-06 05:23:23.536 homeassistant systemd[1]: Starting Network Manager Script Dispatcher Service...

2025-03-06 05:23:23.570 homeassistant systemd[1]: Started Network Manager Script Dispatcher Service.

2025-03-06 05:23:33.599 homeassistant systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

2025-03-06 05:23:59.276 homeassistant systemd[1]: docker-24b589451bbb66abcac3978dd8727a0f91e64f708d33e31cd0b8f6eeba5d44d7.scope: Deactivated successfully.

2025-03-06 05:23:59.277 homeassistant kernel: audit: type=1334 audit(1741238639.273:2838): prog-id=764 op=UNLOAD

2025-03-06 05:23:59.277 homeassistant systemd[1]: docker-24b589451bbb66abcac3978dd8727a0f91e64f708d33e31cd0b8f6eeba5d44d7.scope: Consumed 17min 32.656s CPU time.

2025-03-06 05:23:59.425 homeassistant dockerd[521]: time="2025-03-06T05:23:59.423846084Z" level=info msg="ignoring event" container=24b589451bbb66abcac3978dd8727a0f91e64f708d33e31cd0b8f6eeba5d44d7 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"

2025-03-06 05:24:01.211 homeassistant kernel: audit: type=1325 audit(1741238641.208:2839): table=nat:255 family=2 entries=1 op=nft_unregister_rule pid=1589636 subj=unconfined comm="iptables"

2025-03-06 05:24:01.211 homeassistant kernel: audit: type=1300 audit(1741238641.208:2839): arch=c000003e syscall=46 success=yes exit=512 a0=3 a1=7fff57065850 a2=0 a3=7fff5706583c items=0 ppid=521 pid=1589636 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-nft-multi" subj=unconfined key=(null)

2025-03-06 05:24:01.211 homeassistant kernel: audit: type=1327 audit(1741238641.208:2839): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D74006E6174002D4400444F434B4552002D7000746370002D6400302F30002D2D64706F72740038343835002D6A00444E4154002D2D746F2D64657374696E6174696F6E003137322E33302E33332E323A383438350000002D690068617373696F

2025-03-06 05:24:01.243 homeassistant kernel: audit: type=1325 audit(1741238641.240:2840): table=nat:256 family=2 entries=1 op=nft_unregister_rule pid=1589638 subj=unconfined comm="iptables"

2025-03-06 05:24:01.243 homeassistant kernel: audit: type=1300 audit(1741238641.240:2840): arch=c000003e syscall=46 success=yes exit=604 a0=3 a1=7ffea0d4bff0 a2=0 a3=7ffea0d4bfdc items=0 ppid=521 pid=1589638 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-nft-multi" subj=unconfined key=(null)

2025-03-06 05:24:01.243 homeassistant kernel: audit: type=1327 audit(1741238641.240:2840): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D74006E6174002D4400504F5354524F5554494E47002D7000746370002D73003137322E33302E33332E32002D64003137322E33302E33332E32002D2D64706F72740038343835002D6A004D415351554552414445

2025-03-06 05:24:01.275 homeassistant kernel: audit: type=1325 audit(1741238641.270:2841): table=filter:257 family=2 entries=1 op=nft_unregister_rule pid=1589640 subj=unconfined comm="iptables"

2025-03-06 05:24:01.275 homeassistant kernel: audit: type=1300 audit(1741238641.270:2841): arch=c000003e syscall=46 success=yes exit=652 a0=3 a1=7ffc0a921d60 a2=0 a3=7ffc0a921d4c items=0 ppid=521 pid=1589640 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-nft-multi" subj=unconfined key=(null)

2025-03-06 05:24:01.275 homeassistant kernel: audit: type=1327 audit(1741238641.270:2841): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D740066696C746572002D4400444F434B45520000002D690068617373696F002D6F0068617373696F002D7000746370002D64003137322E33302E33332E32002D2D64706F72740038343835002D6A00414343455054

2025-03-06 05:24:01.850 homeassistant kernel: veth54d6a6a: renamed from eth0

2025-03-06 05:24:01.859 homeassistant kernel: hassio: port 1(veth38d486e) entered disabled state

2025-03-06 05:24:01.957 homeassistant NetworkManager[380]: <info> [1741238641.9371] manager: (veth54d6a6a): new Veth device (/org/freedesktop/NetworkManager/Devices/112)

2025-03-06 05:24:04.765 homeassistant kernel: hassio: port 1(veth38d486e) entered disabled state

2025-03-06 05:24:04.766 homeassistant kernel: veth38d486e (unregistering): left allmulticast mode

2025-03-06 05:24:04.766 homeassistant kernel: veth38d486e (unregistering): left promiscuous mode

2025-03-06 05:24:04.767 homeassistant kernel: hassio: port 1(veth38d486e) entered disabled state

2025-03-06 05:24:04.767 homeassistant kernel: audit: type=1700 audit(1741238644.758:2842): dev=veth38d486e prom=0 old_prom=256 auid=4294967295 uid=0 gid=0 ses=4294967295

2025-03-06 05:24:04.789 homeassistant kernel: audit: type=1300 audit(1741238644.758:2842): arch=c000003e syscall=44 success=yes exit=32 a0=d a1=c0007e9900 a2=20 a3=0 items=0 ppid=1 pid=521 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dockerd" exe="/usr/bin/dockerd" subj=unconfined key=(null)

2025-03-06 05:24:04.796 homeassistant kernel: audit: type=1327 audit(1741238644.758:2842): proctitle=2F7573722F62696E2F646F636B657264002D480066643A2F2F002D2D636F6E7461696E6572643D2F72756E2F636F6E7461696E6572642F636F6E7461696E6572642E736F636B

2025-03-06 05:24:05.951 homeassistant kernel: audit: type=1334 audit(1741238645.949:2843): prog-id=767 op=UNLOAD

2025-03-06 05:24:06.216 homeassistant systemd[1]: var-lib-docker-overlay2-f37000745c99a69dd18066ed0f8c596f33b10a530f455e4374c31a964e9b2186-merged.mount: Deactivated successfully.

2025-03-06 05:24:06.218 homeassistant systemd[1]: mnt-data-docker-overlay2-f37000745c99a69dd18066ed0f8c596f33b10a530f455e4374c31a964e9b2186-merged.mount: Deactivated successfully.

2025-03-06 05:24:13.761 homeassistant systemd[1]: var-lib-docker-overlay2-2568b1809a9c55244cb7ad3f2a04eac9ff57f163aa45c9a13b2790f0cb4218c2\x2dinit-merged.mount: Deactivated successfully.

2025-03-06 05:24:13.762 homeassistant systemd[1]: mnt-data-docker-overlay2-2568b1809a9c55244cb7ad3f2a04eac9ff57f163aa45c9a13b2790f0cb4218c2\x2dinit-merged.mount: Deactivated successfully.

2025-03-06 05:24:20.098 homeassistant NetworkManager[380]: <info> [1741238660.0977] dhcp4 (enp0s3): state changed new lease, address=192.168.0.40

2025-03-06 05:24:20.147 homeassistant systemd[1]: Starting Network Manager Script Dispatcher Service...

2025-03-06 05:24:20.167 homeassistant systemd[1]: Started Network Manager Script Dispatcher Service.

2025-03-06 05:24:23.960 homeassistant kernel: hassio: port 1(veth2604b53) entered blocking state

2025-03-06 05:24:23.960 homeassistant kernel: hassio: port 1(veth2604b53) entered disabled state

2025-03-06 05:24:23.961 homeassistant kernel: veth2604b53: entered allmulticast mode

2025-03-06 05:24:23.961 homeassistant kernel: veth2604b53: entered promiscuous mode

2025-03-06 05:24:23.961 homeassistant kernel: hassio: port 1(veth2604b53) entered blocking state

2025-03-06 05:24:23.961 homeassistant kernel: hassio: port 1(veth2604b53) entered forwarding state

2025-03-06 05:24:23.961 homeassistant kernel: audit: type=1700 audit(1741238663.954:2844): dev=veth2604b53 prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295

2025-03-06 05:24:23.961 homeassistant kernel: audit: type=1300 audit(1741238663.954:2844): arch=c000003e syscall=44 success=yes exit=40 a0=d a1=c000b41e30 a2=28 a3=0 items=0 ppid=1 pid=521 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dockerd" exe="/usr/bin/dockerd" subj=unconfined key=(null)

2025-03-06 05:24:23.961 homeassistant kernel: audit: type=1327 audit(1741238663.954:2844): proctitle=2F7573722F62696E2F646F636B657264002D480066643A2F2F002D2D636F6E7461696E6572643D2F72756E2F636F6E7461696E6572642F636F6E7461696E6572642E736F636B

2025-03-06 05:24:23.961 homeassistant kernel: hassio: port 1(veth2604b53) entered disabled state

2025-03-06 05:24:23.975 homeassistant NetworkManager[380]: <info> [1741238663.9739] manager: (vetheaeda44): new Veth device (/org/freedesktop/NetworkManager/Devices/113)

2025-03-06 05:24:23.990 homeassistant NetworkManager[380]: <info> [1741238663.9855] manager: (veth2604b53): new Veth device (/org/freedesktop/NetworkManager/Devices/114)

2025-03-06 05:24:28.506 homeassistant kernel: audit: type=1325 audit(1741238668.496:2845): table=nat:258 family=2 entries=1 op=nft_register_rule pid=1589713 subj=unconfined comm="iptables"

2025-03-06 05:24:28.506 homeassistant kernel: audit: type=1300 audit(1741238668.496:2845): arch=c000003e syscall=46 success=yes exit=508 a0=3 a1=7ffde27ce3e0 a2=0 a3=7ffde27ce3cc items=0 ppid=521 pid=1589713 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-nft-multi" subj=unconfined key=(null)

2025-03-06 05:24:28.506 homeassistant kernel: audit: type=1327 audit(1741238668.496:2845): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D74006E6174002D4100444F434B4552002D7000746370002D6400302F30002D2D64706F72740038343835002D6A00444E4154002D2D746F2D64657374696E6174696F6E003137322E33302E33332E323A383438350000002D690068617373696F

2025-03-06 05:24:28.513 homeassistant kernel: audit: type=1325 audit(1741238668.510:2846): table=nat:259 family=2 entries=1 op=nft_register_rule pid=1589715 subj=unconfined comm="iptables"

2025-03-06 05:24:28.513 homeassistant kernel: audit: type=1300 audit(1741238668.510:2846): arch=c000003e syscall=46 success=yes exit=600 a0=3 a1=7ffcfa587df0 a2=0 a3=7ffcfa587ddc items=0 ppid=521 pid=1589715 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-nft-multi" subj=unconfined key=(null)

2025-03-06 05:24:28.513 homeassistant kernel: audit: type=1327 audit(1741238668.510:2846): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D74006E6174002D4100504F5354524F5554494E47002D7000746370002D73003137322E33302E33332E32002D64003137322E33302E33332E32002D2D64706F72740038343835002D6A004D415351554552414445

2025-03-06 05:24:28.525 homeassistant kernel: audit: type=1325 audit(1741238668.523:2847): table=filter:260 family=2 entries=1 op=nft_register_rule pid=1589717 subj=unconfined comm="iptables"

2025-03-06 05:24:30.198 homeassistant systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

2025-03-06 05:24:31.561 homeassistant systemd[1]: Started libcontainer container 94c520989b92023550b1bf22f7651175c634de3c7e96fc53f485aca67ce532ab.

2025-03-06 05:24:31.686 homeassistant kernel: kauditd_printk_skb: 2 callbacks suppressed

2025-03-06 05:24:31.687 homeassistant kernel: audit: type=1334 audit(1741238671.681:2848): prog-id=1128 op=LOAD

2025-03-06 05:24:31.699 homeassistant kernel: audit: type=1334 audit(1741238671.682:2849): prog-id=1129 op=LOAD

2025-03-06 05:24:31.700 homeassistant kernel: audit: type=1300 audit(1741238671.682:2849): arch=c000003e syscall=321 success=yes exit=16 a0=5 a1=c0001a1998 a2=78 a3=0 items=0 ppid=1589726 pid=1589737 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="runc" exe="/usr/bin/runc" subj=unconfined key=(null)

2025-03-06 05:24:31.701 homeassistant kernel: audit: type=1327 audit(1741238671.682:2849): proctitle=72756E63002D2D726F6F74002F7661722F72756E2F646F636B65722F72756E74696D652D72756E632F6D6F6279002D2D6C6F67002F72756E2F636F6E7461696E6572642F696F2E636F6E7461696E6572642E72756E74696D652E76322E7461736B2F6D6F62792F39346335323039383962393230323335353062316266323266

2025-03-06 05:24:31.701 homeassistant kernel: audit: type=1334 audit(1741238671.700:2850): prog-id=1130 op=LOAD

2025-03-06 05:24:31.707 homeassistant kernel: audit: type=1300 audit(1741238671.700:2850): arch=c000003e syscall=321 success=yes exit=18 a0=5 a1=c0001a1730 a2=78 a3=0 items=0 ppid=1589726 pid=1589737 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="runc" exe="/usr/bin/runc" subj=unconfined key=(null)

2025-03-06 05:24:31.707 homeassistant kernel: audit: type=1327 audit(1741238671.700:2850): proctitle=72756E63002D2D726F6F74002F7661722F72756E2F646F636B65722F72756E74696D652D72756E632F6D6F6279002D2D6C6F67002F72756E2F636F6E7461696E6572642F696F2E636F6E7461696E6572642E72756E74696D652E76322E7461736B2F6D6F62792F39346335323039383962393230323335353062316266323266

2025-03-06 05:24:31.707 homeassistant kernel: audit: type=1334 audit(1741238671.704:2851): prog-id=1130 op=UNLOAD

2025-03-06 05:24:31.707 homeassistant kernel: audit: type=1300 audit(1741238671.704:2851): arch=c000003e syscall=3 success=yes exit=0 a0=12 a1=0 a2=0 a3=0 items=0 ppid=1589726 pid=1589737 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="runc" exe="/usr/bin/runc" subj=unconfined key=(null)

2025-03-06 05:24:31.707 homeassistant kernel: audit: type=1327 audit(1741238671.704:2851): proctitle=72756E63002D2D726F6F74002F7661722F72756E2F646F636B65722F72756E74696D652D72756E632F6D6F6279002D2D6C6F67002F72756E2F636F6E7461696E6572642F696F2E636F6E7461696E6572642E72756E74696D652E76322E7461736B2F6D6F62792F39346335323039383962393230323335353062316266323266

2025-03-06 05:24:32.361 homeassistant kernel: eth0: renamed from vetheaeda44

2025-03-06 05:24:32.371 homeassistant kernel: hassio: port 1(veth2604b53) entered blocking state

2025-03-06 05:24:32.371 homeassistant kernel: hassio: port 1(veth2604b53) entered forwarding state

2025-03-06 05:24:32.378 homeassistant NetworkManager[380]: <info> [1741238672.3776] device (veth2604b53): carrier: link connected

Questions:

Qu’est ce qu’il s’est passé exactement?
Comment éviter que ça se reproduise?
Et surtout, pourquoi j’ai deux thermostats qui n’ont pas retrouvé leur reglage initial?

ddfdom · Mars 6, 2025, 2:34

J’ai pas de boule de cristal

Idaho947 · Mars 6, 2025, 2:38

Tu as pas eu une maj du superviseur ? Tu es en quelle version a ce niveau parce qu’il y a eu une nouvelle sortie hier.

Pour tes thermostats sont les deux mêmes? C’est quelle marque/ model ? Tu en a d’autres identique qui ont fonctionné ?

mbdrlp · Mars 6, 2025, 2:47

Non?
Excuse moi pour la formulation, j’aurais du dire: Est ce que vous avez une idée de ce qu’il aurait pu se produire

mbdrlp · Mars 6, 2025, 2:48

Je suis en 2025.2.5, je n’ai pas encore fais la mise à jour.
Oui, les deux thermostats sont les meme (Stelpro STZW402+), mais j’en ai deux autres identiques qui ont retrouvé leur état initial

Idaho947 · Mars 6, 2025, 2:51

Ca c’est la version du core moi je parle de la version du superviseur.

mbdrlp · Mars 6, 2025, 2:51

J’ai regardé du coté de mon NAS, et il a fait un backup de 00:00 à 00:29, comme par hasard au meme moment. En theorie il n’est pas censé redemarrer la machine virtuelle. D"ailleurs si je regarde du coté de Home Assistant, il me dit que le dernier boot a été fait il y a 2 semaines

mbdrlp · Mars 6, 2025, 2:52

Désolé

Core 2025.2.5
Supervisor 2025.03.0
Operating System 14.2
Frontend 20250221.0

Idaho947 · Mars 6, 2025, 2:54

Donc c’est pas ça tu es pas passé sur la 3.2…

Tu as regardé côté log du broker ?

mbdrlp · Mars 6, 2025, 3:10

Tu veux parler du Mosquitto broker?

2025-03-06 00:19:03: Client mqttjs_71f87154 has exceeded timeout, disconnecting.
2025-03-06 00:19:03: Client 71kxG4Eb527xzMcIO7TV6V has exceeded timeout, disconnecting.
2025-03-06 00:19:04: New connection from 172.30.32.2:39042 on port 1883.
2025-03-06 00:19:04: Client <unknown> closed its connection.
2025-03-06 00:19:51: Client auto-A23AFBE9-1CB5-084D-8211-AE587685CB6D has exceeded timeout, disconnecting.
2025-03-06 00:20:31: Client jeedomzb572 closed its connection.
2025-03-06 00:21:04: New connection from 172.30.32.2:41806 on port 1883.
2025-03-06 00:21:05: Client <unknown> closed its connection.
2025-03-06 00:21:19: New connection from 192.168.0.20:48579 on port 1883.
time="2025-03-06T00:21:46-05:00" level=error msg="http request error: Post \"http://127.0.0.1:80/authentication\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
time="2025-03-06T00:21:46-05:00" level=error msg="Post \"http://127.0.0.1:80/authentication\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
2025-03-06 00:21:19: Bad socket read/write on client auto-6A0BCE90-6E33-E769-0ECE-EBCF69BAF5C9: Unknown error.
2025-03-06 00:21:51: New connection from 192.168.0.20:58449 on port 1883.
2025-03-06 00:21:51: New client connected from 192.168.0.20:58449 as auto-7D8615AE-393E-61DF-7649-72269713791F (p2, c1, k30, u'mqtt').
2025-03-06 00:21:56: New connection from 172.30.32.1:38907 on port 1883.
2025-03-06 00:21:56: New client connected from 172.30.32.1:38907 as 71kxG4Eb527xzMcIO7TV6V (p2, c1, k60, u'mqtt').
2025-03-06 00:21:56: New connection from 172.30.33.2:50456 on port 1883.
2025-03-06 00:21:56: New client connected from 172.30.33.2:50456 as mqttjs_71f87154 (p2, c1, k60, u'mqtt').
2025-03-06 00:23:03: New connection from 192.168.0.20:37496 on port 1883.
2025-03-06 00:23:03: New client connected from 192.168.0.20:37496 as jeedomzb572 (p2, c1, k60, u'mqtt').
2025-03-06 00:23:05: New connection from 172.30.32.2:40934 on port 1883.
2025-03-06 00:23:05: Client <unknown> closed its connection.
2025-03-06 00:23:59: Client mqttjs_71f87154 closed its connection.
2025-03-06 00:25:02: New connection from 172.30.33.2:56402 on port 1883.
2025-03-06 00:25:02: New client connected from 172.30.33.2:56402 as mqttjs_5668ce09 (p2, c1, k60, u'mqtt').
2025-03-06 00:25:05: New connection from 172.30.32.2:58126 on port 1883.
2025-03-06 00:25:05: Client <unknown> closed its connection.

mbdrlp · Mars 6, 2025, 3:36

De ce que je peux trouver sur internet, c’est peut etre un problème de Cache avec les disques de mon Synology. Ca pourrait faire du sens, vu que c’est arrivé en meme temps que le backup de mon Synology. Mais mon Synology fait un backup quotidien, alors je m’attends à avoir le problème plus frequemment. Je vais surveiller ça de près

Idaho947 · Mars 6, 2025, 4:00

Peut-être un coup de mou a ce moment là. A voir demain en effet.

mbdrlp · Mars 6, 2025, 4:03

oui, j’ai encore de quoi lui fournir de la RAM et de l’espace disque si besoin

ddfdom · Mars 6, 2025, 5:39

C’est quand même pas simple a diagnostiquer ce genre de soucis furtif
Ça peut être tellement de choses ou juste un coup de calcaire qui 'e de reproduira plus

mbdrlp · Mars 8, 2025, 1:42

J’espère mais j’ai encore le traumatisme de mon Jeedom dont je n’avais plus aucune confiance dans la stabilité
En tout cas jusqu’à présent aucun regret d’avoir fait le switch!

mbdrlp · Mars 13, 2025, 1:00

Bon, la mauvaise nouvelle, c’est que ca vient de se reproduire sur les 2 meme thermostats. La temperature du thermostat physique a été configuré à 5°C au redémarrage de Home Assistant.
La bonne nouvelle, c’est que c’est arrivé lorsque je l’ai redemarré manuellement (C’esst un restart, pas un reboot). C’est donc reproductible « facilement » et je devrais être en mesure de le debuggué.

Pour résumer:

ça se produit sur les deux même thermostats
Ce sont les même modèles de thermostats
J’ai d’autres thermostats du même modèle qui n’ont pas ce problème
J’utilise Versatile Thermostat

Ce se ne serait donc pas lié à HA directement, mais à Versatile Thermostat ou à une automation que je fais sur ces deux thermostats… Je vais aller analyser ça

Idaho947 · Mars 13, 2025, 1:02

Compare les paramètres zwave de ceux qui fonctionnent normalement et celui des autres aussi.

mbdrlp · Mars 13, 2025, 2:32

Je viens de trouver mon problème, il vient de mon flow Node Red

Lorsque HA demarre, le flow est executé. Je viens verifier que la porte est fermée. Si ce n’est pas le cas, alors le chauffage est coupée.
J’ai le meme capteur de portes dans ces pièces, et au demarrage, l’état est inconnu.
L’option retain dans Zigbee2Mqtt n’était pas coché pour ces deux capteurs.
Problème reglé!