SecuritySpy URLs
Hi,
I am trying to integrate SecuritySpy with OpenHAB home automation system.
I have managed to put one of my IP Camera's feeds on to the (HABPanel) custom homepage (via SecuritySpy) without displaying the header by using this URL:
http://192.168.1.248:8000/++video?cameraNum=5&viewMethod=0&imageSize=0&windowWidth=640x480
I can't seem reduce the size of the feed to fit in the window. Is there something I can put in the URL which would do this?
I am trying to integrate SecuritySpy with OpenHAB home automation system.
I have managed to put one of my IP Camera's feeds on to the (HABPanel) custom homepage (via SecuritySpy) without displaying the header by using this URL:
http://192.168.1.248:8000/++video?cameraNum=5&viewMethod=0&imageSize=0&windowWidth=640x480
I can't seem reduce the size of the feed to fit in the window. Is there something I can put in the URL which would do this?
Comments
http://192.168.1.248:8000/++video?cameraNum=5&width=320&height=240
You don't need the other parameters (viewMethod, imageSize or windowWidth).
In a short future, I want to install a jeedom server, and send some instructions to securityspy server.
I have not the jeedom server yet, I currently make some tests with my browser.
Securityspy is set with https server. When I want to access to this URL:
https://IP-securityspy:PORT/++image?cameraNum=3
The browser show the identification pop up (user/password).
Is it possible to specify directly user/password in the url?
https://username:password@IP-securityspy:PORT/++image?cameraNum=3
- Safari iphone identifies this address like a phishing site. Then I must ignore alert.
- Safari Mac os can't open this URL with the message "no application has been set to open this URL".
- Chrome PC is ok after the https alert
Some times, Safari wants to validate certificate...
Then, I want to do the sale thing with http, but Safari Mac OS give the same message (no app set to open this url).
It works with Chrome and Safari ios
There is another way, which is to add an "auth" parameter to the request. The value of this parameter is the Base64-encoded version of the string username:password.
So for example, if the username and password are both "admin", use the tool linked to above to convert "admin:admin" into Base64, which is "YWRtaW46YWRtaW4=". You then add this to the URL like this:
http://address:port/++image?cameraNum=3&auth=YWRtaW46YWRtaW4=
Hope this helps.
When I view the interface after the bigger web interface update, I no longer see the URL change as I browse different cameras, so I find it a bit difficult to make an URL that work. For instance, this doesn't work:
https://mydomain.viewcam.me:8001/&auth=YWRtaW46YWRtaW4=
How should the URL be set up?
Hi @Rick_Sanches_C137 I'm afraid the new web interface isn't designed to use this method for authentication - instead, it works via login and session cookies.
If you need it, the old web interface is still available at the /v5 subfolder, i.e.:
https://mydomain.viewcam.me:8001/v5/index.html&auth=YWRtaW46YWRtaW4=