There area a bunch of posts that talk about integrating Hubitat and Blue Iris. But I can't seem to find an example of a critical piece, what to add for the POST value in Blue Iris. I get that I need to add my Hubitat address for http in Blue Iris. I've looked all over Hubitat and on Google and I can't seem to find any examples for the POST value. I can find the process to create the alert in Blue Iris and some very generic, basic help for what to do on the Hubitat side to create the device but nothing about how to handle the POST values or how Hubitat handles them http call from Blue Iris.
So anyone knows, I need to capture the motion sensors in my Reolink cameras. I have a lot of wild animals around here including wild board/pigs which destroy my lawns. I want to turn on my outdoor spotlights around the house to scare them off and turn on a siren when they get close.
Can anyone point me in the right direction on how to add and handle the POST parameters?
Haven't played with this, but the simplest approach may be to set up a rule in RM with the trigger being the post from Blue Iris to handle the down stream requirements - lights, sirens, water spray, etc.
You will need the virtual motion sensor to go inactive, so that you can do other things on inactive state change.
My front camera turns on the outside lights with motion, by triggering a virtual motion sensor via Maker API. That virtual sensor is used in an automation to turn on the lights. I made a virtual motion sensor driver that has an auto inactive timer, so when it goes inactive, the lights turn off by an automation, just like using a regular motion sensor that goes inactive after a motion timeout.
If the camera keeps triggering motion to the API, the driver will keep pushing out the inactive timeout until no motion is sent within the timeout setting, also like a real motion sensor.
Makes sense now. I've never used MakerAPI before. A LOT of stuff online says start with Blue Iris to configure the alert then go into HE and add the device and then create the rule. That doesn't work because you need the ID for the device to build the URL in the BI alert. So you need to install MakerAPI, add the device in HE, then create the alert in BI, then finish with the Rule.
And I get what user2574 is saying. I'm going to do that. I want the lights to flash on and off. As I said, the problem is animals in my yard and garbage. I have the wild pigs, racoons, armadillos and an occasional bobcat comes through. The bobcat is harmless. He just sits there and stares into nowhere. The pigs tear up my lawn to the tune of about $2,000 each time. The racoons get into my garbage. Both of these are scared off with lights flashing. The armadillos? Nothing really fazes them. They just turn and stare at you or the lights and keep on walking.
I just finished creating the devices for 9 cameras and added the alerts to BI. Now I need to create the rules and test everything.
Really old post but still a good reference (esp for me since I'm still on Blue Iris 4):
Note: (this was written for BI 4, not sure if it'll work in 5)
BI Control is one way, Hubitat to Blue Iris. BUT... there is a way to receive alerts from Blue Iris just using Rule Machine!
Note: This was written for BI4. If using BI5 results may vary.
In Rule Machine:
'Create New Rule', 'Define a Trigger', 'Name the Trigger'
'Select Trigger Events', 'Select capability' = 'Local End Point'
Note: you will need the 'Local End Point URL' in Blue Iris
'Select Actions' to do whatever you like!
In Blue Iris
Select the Camera to use as a Trigger then 'Right Click' and select 'Camera Properties'.
Select 'Alerts' and then check-off 'Post to a web address...' and then click 'Configure'
Under the heading 'When Triggered', make sure that "Http://" is selected
Then next to that box, put in the 'Local End Point' URL from Hubitat. Note: do not include the Http:// ... just start with the ip address. (ie. 192.168.1.123/apps/api/....)
@dcioffii, fwiw the initial replies are very consistent with how we integrate BI and HE. We use BI of course to trigger cameras (often but not always using AI to identify people, cars, pets, etc.). And then BI sends http commands that activate/inactive virtual motion sensors in HE. Right now, we do it a bit brute force (e.g., Dining Room Pet Sensor, Dining Room Person Sensor), even though there are ways for BI to pass to HE not just the event but also what triggered it (dog, person, boat, etc.)
We also use the integrations the reverse way from HE to BI -- when HE changes modes, it is reflected in the BlueIris "profile".
Are there specific use-cases you want help with? Just say the word! The BI documentation which @trunzoc pasted above is what your looking for, I'd imagine.
I saw BI Control - Local Blue Iris control when I was looking around and I did install it. For now I just need to trigger some (virtual) motion sensors in HE. I don't use any HE modes since I really don't need them. I don't have any cameras inside the house. The motion detectors I do have inside are used to trigger lights when someone walks into a room. The lights stay on since the sensor is constantly triggered.
I like having the virtual motion sensors since I can display them in a dashboard. I have two wide screen monitors in my office on my wall above my 4 PC monitors on an older Gen 5 HP Mini. All it does is display a dashboard from HE and will eventually display the cameras on Blue Iris. Right now it's displaying the (Reolink) cameras using their PC Client which kind of sucks. I also have a Reolink NVR in my garage in a wall mounted rack just for recording. It has a 10 tb external hard drive plus the 4 tb drive that the NVR came with.
Now all I need to do is figure out how to stop the cobwebs from forming on a few of my cameras which cause the camera to detect "motion" at night. The IR Leds are behind the cobwebs and the wind/breeze makes them move and the camera sees them as motion.
