2022.7.5 running but still getting the libav.hls errors.
Logger: libav.hls
Source: components/stream/worker.py:394
First occurred: 2:11:11 PM (24 occurrences)
Last logged: 2:11:45 PM
Packet corrupt (stream = 0, dts = 7032206874)
Packet corrupt (stream = 0, dts = 7032594864)
Packet corrupt (stream = 0, dts = 7032845694)
.
Packet corrupt (stream = 0, dts = 7033134864)
same for me,
since 2022.7.5 the stream is working ( very fast) but still have continuous "Packet corrupt " in log
Indeed. There are still countless warnings …
2022-07-16 17:40:12 WARNING (stream_worker) [libav.hls] Packet corrupt (stream = 0, dts = 2247729948)
2022-07-16 17:40:12 WARNING (stream_worker) [libav.hls] .
2022-07-16 17:40:14 WARNING (stream_worker) [libav.hls] Packet corrupt (stream = 0, dts = 2247909948)
2022-07-16 17:40:14 WARNING (stream_worker) [libav.hls] .
2022-07-16 17:40:16 WARNING (stream_worker) [libav.hls] Packet corrupt (stream = 0, dts = 2248089948)
2022-07-16 17:40:16 WARNING (stream_worker) [libav.hls] .
2022-07-16 17:40:18 WARNING (stream_worker) [libav.hls] Packet corrupt (stream = 0, dts = 2248269948)
2022-07-16 17:40:18 WARNING (stream_worker) [libav.hls] .
2022-07-16 17:40:21 WARNING (stream_worker) [libav.hls] Packet corrupt (stream = 0, dts = 2248449948)
2022-07-16 17:40:21 WARNING (stream_worker) [libav.hls] .
2022-07-16 17:40:21 WARNING (stream_worker) [libav.hls] Packet corrupt (stream = 0, dts = 2248629948)
2022-07-16 17:40:21 WARNING (stream_worker) [libav.hls] .
2022-07-16 17:40:23 WARNING (stream_worker) [libav.hls] Packet corrupt (stream = 0, dts = 2248809948)
2022-07-16 17:40:23 WARNING (stream_worker) [libav.hls] .
2022-07-16 17:40:25 WARNING (stream_worker) [libav.hls] Packet corrupt (stream = 0, dts = 2248989948)
2022-07-16 17:40:25 WARNING (stream_worker) [libav.hls] .
2022-07-16 17:40:27 WARNING (stream_worker) [libav.hls] Packet corrupt (stream = 0, dts = 2249169948)
2022-07-16 17:40:27 WARNING (stream_worker) [libav.hls] .
2022-07-16 17:40:29 WARNING (stream_worker) [libav.hls] Packet corrupt (stream = 0, dts = 2249349948)
2022-07-16 17:40:29 WARNING (stream_worker) [libav.hls] .
2022-07-16 17:40:31 WARNING (stream_worker) [libav.hls] Packet corrupt (stream = 0, dts = 2249529948)
2022-07-16 17:40:31 WARNING (stream_worker) [libav.hls] .
2022-07-16 17:40:33 WARNING (stream_worker) [libav.hls] Packet corrupt (stream = 0, dts = 2249709948)
2022-07-16 17:40:33 WARNING (stream_worker) [libav.hls] .
2022-07-16 17:40:35 WARNING (stream_worker) [libav.hls] Packet corrupt (stream = 0, dts = 2249889948)
2022-07-16 17:40:35 WARNING (stream_worker) [libav.hls] .
2022-07-16 17:40:38 WARNING (stream_worker) [libav.hls] Packet corrupt (stream = 0, dts = 2250069948)
2022-07-16 17:40:38 WARNING (stream_worker) [libav.hls] .
2022-07-16 17:40:40 WARNING (stream_worker) [libav.hls] Packet corrupt (stream = 0, dts = 2250249948)
2022-07-16 17:40:40 WARNING (stream_worker) [libav.hls] .
2022-07-16 17:40:42 WARNING (stream_worker) [libav.hls] Packet corrupt (stream = 0, dts = 2250429948)
2022-07-16 17:40:42 WARNING (stream_worker) [libav.hls] .
2022-07-16 17:40:44 WARNING (stream_worker) [libav.hls] Packet corrupt (stream = 0, dts = 2250609948)
2022-07-16 17:40:44 WARNING (stream_worker) [libav.hls] .
That’s the drawback of home assistant: with every new update, you run into issues without even changing a bit of configuration. Once you think it works and could stay that way, the next update is sure to break a feature.
Does anyone still has this issue? I am asking as I am confronted with the same since I have upgraded to 2022.10.
I have 3 Netatmo presence cameras, only one is showing a snapshot picture where it should show the livestream. The other 2 entities for the other cameras have disappeared and not available anymore. Webhooks for all cameras still work though.
Before 2022.10 everything was working perfectly.
Would appreciate your feedback.
ok, problem solved by just restarting each and every camera.
how do you restart them ? power off/on ?
you have to disconnect them from the grid, so for me basically switching off and on the electricity for the camera did the job
This should soon be a thing of the past and be handled more gracefully.
Does it mean. , that netatmo will integrate a reboot button ?!
Haha, no. But feel free to try 2022.11.0b4 (or later) as it contains the changes. Feedback is welcome.
I“m on 2022.11.0b3 
Almost there.
I“ll give a try…. and take a look …. I“m courious
Ok I“m now u2date 
Thanks for the feedback. Let’s hope it stays that way.