Recently I had some people around my house trying to break in. All caught nicely with Blue Iris.
This made me think; what happens with these video’s when they would actually be succesfull, break in and steal my server…
To overcome this I now have a shell command that triggers a backup of BI video’s to Google drive when alarm is triggered. Basic steps can be found here. If more people interested I can write down how I did it in HASS in more detail.
On the PC running BI you need to install Eventghost
When you now do stuff on your PC you will actually see most of that logged in the window on the left
Now install Autoremote plugin into Eventghost. We need this plugin to catch the calls from HASS. The plugin is actually made for linking with mobile phones but you can ignore that. As far as I remember there was no need to setup a phone in the autoremote plugin. If you have to just put in a dummy.
It might be that you need to open your windows firewall to the ports mentioned in the plugin
Now you need to test if Eventghost received the calls! Go to your PI you are running HASS on, login via putty and make a call to your BI servers. For instance "curl -m 1 "http://IP_of_BIserver:port/?message=test"
you should receive that in the logging window of eventghost. Don’t progress before you have this working. If it works all the basics are in order!
Create a batch file on your windows machine. I only have one line in that: xcopy "F:\BlueIris\New" "F:\Google Drive\BackupBIVideo" /c /d /e /h /i /k /q /r /s /y /j /z . keep the parameters the same but of course change the locations to the ones you have/want to use.
Now setup the macro in Eventghost. Pls also check the post here for that. It should catch your ‘alarm’ message and then execute a batch script (the one from the step above). There are many manuals to be found how to do this so will nor repeat here.
Now add to your configuration.yaml in hass a shell command (the forum does now allow me to format correctly , so the ** are spaces):
shell_command:
**backup_bivideo: curl -m 1 http://192.168.1.40:1818/?message=alarm
Then in your automation that detects alarm add under actions: service: shell_command.backup_bivideo
Would really love some help on this one. I have motion detection enabled and have ticked “audio” also in Blue Iris. I’d really love to simply trigger an API call to Hass that sends a message to all notify candidates saying “Sound detected in the bedroom”. Is it possible to trigger a Hass push notification through the api and pass the message? If so can anyone advise the call I’d need to make from Blue iris? Many thanks in advance, and apologies in advance for my terrible case of the newbs.
Not sure, are you inside the LAN? Maybe goto blue iris and turn off authentication temporarily or modify security settings so they’re less strict for you to debug.
I tried sending the link from HA server to BI server and i am getting proper response but i am not seeing anything in eventghost. I can see rest of the events fine in EG. Any ideas
When is says: "curl -m 1 “http://IP_of_BIserver:port/?message=test” I mean the server that runs BI and the port the number you have set in autoremote (in my case 1818, i believe this was defaut). You also need to make sure that you have your windows firewall open for this port.
I came from Openhab and just made the switch last weekend. I had Blue Iris just posting a request to a web service utilizing openhab’s RESTful API. Changing the code a bit I got it to work, post an on status but I can’t get the off to work
Blue Iris’s alert to the HA web service is:
192.168.1.115:8123/api/states/binary_sensor.blue_iris_&CAM_Fr_Gar?api_password=xxxxxx
{“state”:“on”}
For off I have it set:
192.168.1.115:8123/api/states/binary_sensor.blue_iris_&CAM_Fr_Gar?api_password=xxxxxx
{“state”:“off”}
but it always stays to the on position once triggered. Any ideas what I’m doing wrong?
first off get rid of your password in your “off” statement…
Everything looks Ok in the code.
Did you make sure you have the tick mark selected for “when trigger is reset”? and you are using the “https:” setting as opposed to the “http:” setting for the reset?
Otherwise check for spelling errors or extra spaces at the end of the command or attributes. That’s gotten me more than once.
Also, since the entity isn’t there after a reboot until it’s triggered, what’s the best method of using a friendly name. Right now on a reboot that entity isn’t known so the friendly name doesn’t get applied.
Use the code posted up thread by @JesseWebDotCom around post 14. That will create persistent entities. It’s what I used and mostly worked for me.
I say mostly because I had one camera that took around thirty seconds to trigger an alert. It was pretty annoying when I was using it to trigger lights to turn on.
I eventually went to using the output directly from the camera and bypassing blue iris completely. I realized if the computer my blue iris was installed on had any issues I would completely lose functionality for all my camera functions (automations and live feeds). Using the camera output directly increased reliability by eliminating one step in the chain therefore one less point of potential failure