what*

This is interesting, we will have a look at the possibility of a SecuritySpy plugin for Home Assistant, I think that would be a good idea.

The "Generic MJPEG IP Camera" plugin seems to be the best one to use currently. The MJPEG URL to supply would be something like this:

http://ss-server-address:8000/++video?cameraNum=0

(see the SecuritySpy Web Server Specification document for a full description of the ++video request.

You can obtain the correct camera number from the Camera Info window in SecuritySpy - if you don't currently have this column displayed, click the header bar where you see the column names, and you will get a pop-up menu that allows you to add the Camera Number column.

I am working with Home Assistant to develop a series of switches that arm and disarm individual cameras. The benefit will be to enable the switches to be used with other automatons or scripts within Home Assistant. Here is the yaml I am using in my Home Assistant configuration.yaml.

switch:
- platform: command_line
switches:
camera_arm:
command_on: '/usr/bin/curl -k "http://{ip}:8000/++ssControlMotionCapture?cameraNum=3&arm=1&auth={authkey}"'
command_off: '/usr/bin/curl -k "http://{ip}:8000/++ssControlMotionCapture?cameraNum=3&arm=0&auth={authkey}"'
command_state: '/usr/bin/curl -k --silent "http://{ip}:8000/++cameramodes?cameraNum=3&auth={authkey}" | grep -oP "(?<=M:).*"'<br /> value_template: '{{ value == "ARMED" }}'

where {ip} = my camera IP address and {authkey} = my authentication. Ignore the not sure why that keeps popping up value_template is a separate line in the yaml.

I suspect my error is in the syntax of the grep command because when I use curl on the command line in terminal to fetch the state of the camera it returns

C:DISARMED
M:DISARMED
A:DISARMED

however, as soon as I add the grep command it fails. If I can get this working I should be able to control this camera's motion capture, notifications, etc.. with switches in Home Assistant.

Hi jjbanker
This: {authkey} will not work in a command_line switch. Either you will have to type the full Auth Key or you will have to put the whole line in the secrets file with the typed auth key and then just do something like:
command_on: !secret cam1_on
command_off: !secret cam1_off
command_state: !secret cam1_state

Your value template is fine and so is you grep command. I use exactly the same and it works.

Things I've done with SS/HASS.

Cameras display in the HASS dashboard.
PIR sensors (or any sensors or event changes) in HASS trigger SS recordings.
Telegram notifications with camera screenshots when an event is triggered.

I can probably do a write up if people are interested?

Thanks for the info Boxgrove, pretty self explanatory. I'll tweak my setup based on your info.

Hi @bonfireva the ++video request is for the MJPEG live video stream itself. So there is no associated HTML page with titles etc. It sounds like you are referring to the "live" request, which gets you an HTML page with the titles and other text that you describe, containing the video image.

This "live" page comes from an HTML template, which you can edit to remove the stuff you don't want. Please see Customising SecuritySpy’s Web Interface.