wpiman
Pulling my weight
I just wanted to share a feature of the latest update for Blue Iris that I find AWESOME. It hasn't hit to documentation yet.
I emailed the developer this request and he incorporated this pretty quickly.
If you use MQTT, the web post or some other export function: the motion &TYPE field will included the zone crossing information that causes the trigger.
For example, if you have a left Zone A, and a right Zone B... you can set up the trigger to fire when an object goes from A to B, or B to A.
This zone crossing info is now information in the &TYPE field.
Example, before this &TYPE field would say MOTION_AB no matter what how the trigger fired.
Now, if you configure the trigger "A>B,B>A", it will print
"MOTION_A>B" for left to right movement and "MOTION_B>A" for right to left.
If you are using HomeAssisstant or HomeSeer like me-- you can use this information to indicate whether a person is coming or going or if a car is approaching or leaving. Simple change but huge implications for those of use who incorporate these tools...
I emailed the developer this request and he incorporated this pretty quickly.
If you use MQTT, the web post or some other export function: the motion &TYPE field will included the zone crossing information that causes the trigger.
For example, if you have a left Zone A, and a right Zone B... you can set up the trigger to fire when an object goes from A to B, or B to A.
This zone crossing info is now information in the &TYPE field.
Example, before this &TYPE field would say MOTION_AB no matter what how the trigger fired.
Now, if you configure the trigger "A>B,B>A", it will print
"MOTION_A>B" for left to right movement and "MOTION_B>A" for right to left.
If you are using HomeAssisstant or HomeSeer like me-- you can use this information to indicate whether a person is coming or going or if a car is approaching or leaving. Simple change but huge implications for those of use who incorporate these tools...