Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File gets exported with IP as name #198

Open
knightofdemons opened this issue May 1, 2024 · 0 comments
Open

File gets exported with IP as name #198

knightofdemons opened this issue May 1, 2024 · 0 comments

Comments

@knightofdemons
Copy link

knightofdemons commented May 1, 2024

Problem:
The exported image gets the name of the ip-address of the camera (ex: 192_168_0_253.jpg)
This is usually not a problem but iam using 2nd old router as gateway to block any other traffic of multiple ipcams.
To still get access to the RTSP streams, im exposing the 554 tcp port of every camera on my camera-router on different ports (ex: Cam1 = 192.168.0.253:551, Cam2 = 192.168.0.253:552, Cam3 = 192.168.0.253:553, etc.).
So just 1 image file is created, which is overwritten by every camera.

Solution:
Make the exported file the same name as the camera-object in ioBroker, like it is found in \ioBroker\iobroker-data\files\cameras.0\cam1.jpg to avoid name collision with different streams from the same ip-address.

Workaround:
Configure each camera -> enable expert settings -> add a static path as command suffix (both files will be created by ffmpeg.exe but your custom path will not be overwritten)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant