Does this mean you’re using openHAB 3.3 Stable?
Please try the binding found here:
Index of /openhab/IpCameraBinding/ (pcmus.com)
Unzip it to your addons folder, uninstall the merged binding and install the Telstick binding to provide the missing dependencies.
This binding will check if the FFmpeg thread is crashed and will auto restart it. When this occurs the logs will have this line…
MJPEG was not being produced by FFmpeg when it should have been, restarting FFmpeg now.
Since I can not reproduce the issue, I can not test if this fixes the issue.
Great thanks for reporting it restarts, the only other 2 that need testing are GIF and MP4 recording to see what happens if the camera restarts in the middle of a recording. The rest should auto fix when the camera reboots if this works for mjpeg.
This just means that the FFmpeg thread that creates the mjpeg stream from RTSP is killed/stopped. When it is missing it means the thread that was started is probably frozen/crashed and the binding thinks it is opperating correctly and will not know it is not functioning.
The new binding will move all ffmpeg output to TRACE log level and will create more lines of text which the binding uses to know if the thread has crashed. No output from FFmpeg and the crash detection will know and kill the thread then auto restart it if it is still needed. At least that is what should happen since I can not test it here.