Domoticz

Some of my camera's have only basic authentication.
When I use them as a block 'camera' they won't start because there is no pop-up to fill in the username and password. (i just get a 'broken' image)
If I use the block 'frames' and then use the url to the camera, I do get a pop-up asking me to signin.

So now I have a workaround to open a new tab in my browser, go direct to the camera url and login, after that I refresh the page of dashticz and the blocks defined as 'camera' are working but stops after some hours. I get then again the 'broken' image.
After I login again on another tab on the camera, do a refresh and it works again for some hours.

Is it possible to get also the login when the 'camera' block is used? I think this solves both problems...

Normally you can add the user credentials to the url (depending on your camera type), like:
http://camera/video.cgi?username=admin&password=secret

or
http://admin:password@camera/video.cgi

What kind of camera do you have?

As an alternative, probably it also possible to open the video URL as an iframe, but that requires some code redesign.

Browsers don’t support the admin:pass@ipaddress anymore, it is blocked.
Unfortunately it is not possible for my cams to do it in other urls format.
I use NX witness to transform rtsp h.264 stream to an mjpeg stream to display on a browser.

But why is the camera after a few hours not visible anymore? What is the cause of that?

whoami wrote: ↑Tuesday 12 January 2021 22:17 Browsers don’t support the admin:pass@ipaddress anymore, it is blocked.
Unfortunately it is not possible for my cams to do it in other urls format.
I use NX witness to transform rtsp h.264 stream to an mjpeg stream to display on a browser.

But why is the camera after a few hours not visible anymore? What is the cause of that?

Most system store a cookie after login, but the cookie expires after a certain moment.

For basic authentication it's also possible to send username/password in the header of the http request.

When I have time, I can do some experiments.

Alternative:
WIth motioneye you can create an image stream without authentication. You can run motioneye as docker container.

Lokonli wrote: ↑Tuesday 12 January 2021 22:53

whoami wrote: ↑Tuesday 12 January 2021 22:17 Browsers don’t support the admin:pass@ipaddress anymore, it is blocked.
Unfortunately it is not possible for my cams to do it in other urls format.
I use NX witness to transform rtsp h.264 stream to an mjpeg stream to display on a browser.

But why is the camera after a few hours not visible anymore? What is the cause of that?

Most system store a cookie after login, but the cookie expires after a certain moment.

For basic authentication it's also possible to send username/password in the header of the http request.

When I have time, I can do some experiments.

That would be awesome! I tried motioneye, but it looks like the video is not that smooth as is with nx witness, even when I set framerate as high as possible.
I hope you have time to check for that http header.

I run motioneyeos on a seperate Pi, but I can't get any camara to work with it. Problem is that two of them are unbranded Chinese clones of ???

They do show up in AgentDVR (ispy) but can't figure away of using those IP's into either motioneye or dashticz (or even domoticz).

Lokonli wrote: ↑Tuesday 12 January 2021 22:53

whoami wrote: ↑Tuesday 12 January 2021 22:17 Browsers don’t support the admin:pass@ipaddress anymore, it is blocked.
Unfortunately it is not possible for my cams to do it in other urls format.
I use NX witness to transform rtsp h.264 stream to an mjpeg stream to display on a browser.

But why is the camera after a few hours not visible anymore? What is the cause of that?

Most system store a cookie after login, but the cookie expires after a certain moment.

For basic authentication it's also possible to send username/password in the header of the http request.

When I have time, I can do some experiments.

Did you try with the basic auth in the headers of the http request? It would be awesome and clicks are not needed anymoren

It would be great if one-time action for authorization only reason would be taken.
In my case opening extra tab in browser to enter login/pass work-arrounds this but if you have a few cams and need to do it for each of them it's a bit frustrating
Would be great to have kind of Initialisation option.

BR

Lokonli wrote: ↑Tuesday 12 January 2021 22:53

whoami wrote: ↑Tuesday 12 January 2021 22:17 Browsers don’t support the admin:pass@ipaddress anymore, it is blocked.
Unfortunately it is not possible for my cams to do it in other urls format.
I use NX witness to transform rtsp h.264 stream to an mjpeg stream to display on a browser.

But why is the camera after a few hours not visible anymore? What is the cause of that?

Most system store a cookie after login, but the cookie expires after a certain moment.

For basic authentication it's also possible to send username/password in the header of the http request.

When I have time, I can do some experiments.

Did you already had time to experiment with the http request?

Lokonli wrote: ↑Tuesday 12 January 2021 22:53

whoami wrote: ↑Tuesday 12 January 2021 22:17 Browsers don’t support the admin:pass@ipaddress anymore, it is blocked.
Unfortunately it is not possible for my cams to do it in other urls format.
I use NX witness to transform rtsp h.264 stream to an mjpeg stream to display on a browser.

But why is the camera after a few hours not visible anymore? What is the cause of that?

Most system store a cookie after login, but the cookie expires after a certain moment.

For basic authentication it's also possible to send username/password in the header of the http request.

When I have time, I can do some experiments.

Did you had time to implement this? If I use frames with an site where there is a basic authentication needed, the url wit the pswd and username are not allowed anymore....

Lokonli wrote: ↑Tuesday 12 January 2021 22:53

whoami wrote: ↑Tuesday 12 January 2021 22:17 Browsers don’t support the admin:pass@ipaddress anymore, it is blocked.
Unfortunately it is not possible for my cams to do it in other urls format.
I use NX witness to transform rtsp h.264 stream to an mjpeg stream to display on a browser.

But why is the camera after a few hours not visible anymore? What is the cause of that?

Most system store a cookie after login, but the cookie expires after a certain moment.

For basic authentication it's also possible to send username/password in the header of the http request.

When I have time, I can do some experiments.

Lokonli, did you had time to experiment?
Can I help testing?