Professor Falken wrote:Awesome plugin!
I had this up and running on the first attempt. Really cool.
Also looking forward to trying out the gifs.
I especially like the idea you mentioned of having the plugin's "triggers" being separate from those in BI (if I understood this correctly) such that BI would still log "Alerts" and tag the recoded video as it always does, but Indigo could control whether BI "triggers" actually perform the various Indigo actions. This will be useful (I think) in the scenario I posted a few pages back to prevent my neighbor's 4:30 am headlights on my lawn from triggering a motion-overnight notification every night.
Thanks for the feedback.
Probably would move to the http server version currently at version 0.6.6 - in Server Branch and help test that.
https://github.com/Ghawken/IndigoPlugin ... /tag/0.6.6It is working well (for me!) and more robust, quicker and likely less future issues. (plus gets ride of log entries)
re: 4:30am scenario:
Yes exactly.
The Camera Device Custom State -
PluginTriggeringEnabled.
This defaults to enabled - so any camera based trigger will run. It also becomes enabled when plugin starts or restarts.
But if set to Disabled via an Action (specific Action to turn on/off) then no trigger for this camera will run until it is re:enabled, or Indigo, or the Plugin restarts.
With BlueIris everything will continue, recording, motion etc. Its just turning of Indigo triggering - so could use overnight; or when home to stop Gif's being sent etc. (& BI will still record)
a few questions:
1) Should I go ahead and paste the variable based code into the alert boxes in BI to create the camera triggers back to I7, or is that system about to change so much with the http server that I should just wait for the current Beta to merge with the released version before adding that functionality?
To get the most out of the plugin (at least triggering) there does need to be feedback to Indigo from Blue Iris.
I would update to http server version (to help testing) and use the web alert suggested in that documentation. This enables On and Off sensing (and will soon aid trigger for motion off)
Also adds another Device Camera State:
lastMotionTriggerType - which tells us the type of BI camera event occur, from motion, to test, to audio etc.
2) What do you do when you add a new camera to your overall system? I am still building my security camera system. If I add a camera, then add it to BI, do I need to go back to the config and re-trigger the "search for cameras" button. If so, does this leave previously created plugin camera devices and their dependencies intact, or will they all have to be deleted/recreated? When I tried adding a new camera device via the usual Indigo add-device method, it didn't seem like it asked for enough info to really add a new camera from BI.
Just click the generate Cameras Button. Won't delete any devices, and will aid any new cameras found.
Admin Users - also can access different Cameras I have found (e.g. disabled ones)
Do Not add a Camera Device yourself - might work if you get everything right - but more likely will cause some major issues.
Likewise do not add Main Server Device yourself - use the button
3) Best practices question: Does it matter, when I give the plugin my BI credentials, whether I use my own admin ones or should I create a new user with Admin privileges to be used by the Indigo plugin?
Not sure matters - but different user would be my advice - so at least when look in BI look can see logins/etc.
4) Maybe I'm thinking about this wrong, but might there be a way for the plugin to erase its various saved images/gifs after a period of time? I'm picturing folders filling up with days/weeks/month's worth of triggered images/GIFs that were sent along as a notification. Does the plugin keep all of these, or does it just overwrite in the same location each time? Obviously this data is also being robustly saved back on the blue iris drive if needed more permanently, are these images/GIFs also saving on my Indigo Mac in the plugin created folders?
Decided not to erase old images currently - certainly easier to see what is working/not working.
But does reuse everything - so no risk of major increase in storage. Once created once, will not get any bigger in size.
They are stored locally at
- Code: Select all
/Users/Username/Documents/Indigo-BlueIris/ & /CameraName/Animated.gif
Hence can use them to be sent as Imsg or notification.
Welcome to keep the questions coming!
Glenn