You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both the RTSP stream directly from camera and the camera entity from ONVIF integration got "mse: streams: EOF" error sometimes, and both return to normal sometimes.
There are errors in homeassistant log:
Error from stream worker: Error opening stream (INVALIDDATA, Invalid data found when processing input, rtsp://:@192.168..:554/stream1)
The camera entity itself works fine and the RTSP stream can be played using VLC player on my computer with no problem, so I assmue the problem is with the WebRTC integration.
The text was updated successfully, but these errors were encountered:
Error from stream worker: Error opening stream (INVALIDDATA, Invalid data found when processing input, rtsp://:@192.168..:554/stream1)
Variants:
you have bad camera
your camera has bad connection (wi-fi, etc)
your camera is overloaded
I can assume you have a TP-Link.
Yes I am using TP-link, does TP-link camera have common issue like this? The TP-link app works good and the connection should be OK.
And what do you mean camera overloaded? Should I lower the bit rate or resoultion?
If these cameras are used correctly - they works fine.
they must have a good wifi connection
they must have only one connection, maximum 2 (for example you already have minimum three - from stream integration and two from this integration - not good)
better to disable recording and motion detection on the camera
Both the RTSP stream directly from camera and the camera entity from ONVIF integration got "mse: streams: EOF" error sometimes, and both return to normal sometimes.
There are errors in homeassistant log:
Error from stream worker: Error opening stream (INVALIDDATA, Invalid data found when processing input, rtsp://:@192.168..:554/stream1)
The camera entity itself works fine and the RTSP stream can be played using VLC player on my computer with no problem, so I assmue the problem is with the WebRTC integration.
The text was updated successfully, but these errors were encountered: