As others, I've been dealing with this error for quite some time now. I've tried everything suggested to no avail.
Announcement
Collapse
No announcement yet.
Is the Motion error going to get fixed for BI5?
Collapse
X
-
It doesn't seem like a lot of development has been going on with this plugin as of late. It's just an observation and I'd love to be mistaken.
It's frustrating to have this particular functionality broken, it's caused some grief and the wife-acceptance-factor has been affected negatively. This is something that would be great to have fixed soon, especially with HS4 on the horizon.
-
Hey there... not to usurp a PI author's ability to sell their plugin, but if you need a workaround, this can be done reliably without the PI. I current use motion detection in blue iris to change a virtual motion detector I created in HS3. From there you can fire whatever event you want.
In blue iris, in the camera properties/alert tab, configure a new "on alert' action... then "configure a web request"
This is the command for the web request to change your VD motion detector to 'motion'
<HS3 IPort>/JSON?request=controldevicebylabel&ref=<VDmotionDetector Reference ID>&label=Motion
When motion is detected, it fires an event. At the end of the event I have it set the VD motion detector back to 'no motion'.... and set to not rerun for 5 minutes).
Hope that helps. let me know if you have any questions.
- Likes 1
Comment
-
Originally posted by Tomgru View PostHey there... not to usurp a PI author's ability to sell their plugin, but if you need a workaround, this can be done reliably without the PI. I current use motion detection in blue iris to change a virtual motion detector I created in HS3. From there you can fire whatever event you want.
In blue iris, in the camera properties/alert tab, configure a new "on alert' action... then "configure a web request"
This is the command for the web request to change your VD motion detector to 'motion'
<HS3 IPort>/JSON?request=controldevicebylabel&ref=<VDmotionDetector Reference ID>&label=Motion
When motion is detected, it fires an event. At the end of the event I have it set the VD motion detector back to 'no motion'.... and set to not rerun for 5 minutes).
Hope that helps. let me know if you have any questions.
Thanks!
Comment
-
ha... i'm same. took some trial and error to get this right. Screen shots below should help! Assume you have triggers figured out in BI (as I found that software a bit tricky at times!. On my Front Door camera, right click , select camera settings, then alerts tab. from that screen, select On alert button at bottom in the Action Pane, and hit the "+" to add an action.
This is what mine looks like. (per the JSON request in my earlier post):
in Homeseer (I have both HS3 and BI on the same server, so IP is the same, FYI)...My Front Door Motion Sensor VD looks like this. The reference number on the advanced tab (468 in my case) is what is used in the BI action you created above.
Then I created an event that runs if motion is detected. this kicks of a separate event to change my tablets to the camera view of the front door, then it resets the motion VD back to NO MOTION (key).
Here is the action camera event. NOTE: I have this setup so it cannot re-run for 5 minutes, so people hanging out at the front door doesn't keep tripping the event. Notice in prior event I have "run only if other event conditions are TRUE" to ensure this works. After 1:30 min, the tablets are set back to the home page.
- Likes 1
Comment
-
Anyone else having issues with the BlueIris Alerts firing? I have a couple of camera's configured to send motion alerts to my MQTT server. If I manually trigger motion the MQTT message is sent. If the Camera triggers based on actual motion the MQTT message is not sent.
Any ideas why this would be happening
Comment
-
Originally posted by jim@beersman.com View PostAnyone else having issues with the BlueIris Alerts firing? I have a couple of camera's configured to send motion alerts to my MQTT server. If I manually trigger motion the MQTT message is sent. If the Camera triggers based on actual motion the MQTT message is not sent.
Any ideas why this would be happening
Comment
-
Originally posted by jim@beersman.com View Post
Yes, it's recording the alert
the other thing could be the profile. I have alerts set to trigger on certain profiles only, and often don't realize that BI has changed the profile.
Comment
-
Originally posted by Tomgru View Post
Just so I understand... you know the alert is occurring because the camera is recording when motion triggers it? Just a shot, but do you have 'minimum time between alerts" checked and if so, how much time?
the other thing could be the profile. I have alerts set to trigger on certain profiles only, and often don't realize that BI has changed the profile.
As for profiles all cameras run under Profile 1.
Also have the red outline on the camera image so I'm very sure it's firing.
Comment
-
I use a Z-Wave transmitter on my mailbox to trigger an event in HS3 which sets a Blue Iris profile. The BI profile records video and takes 3 snaps from 2 cameras. BI sends me 1 snapshot for review very reliably. If cameras are set sensitive enough to record motion you would get way to many false alerts. I record 100's of motion events a day, I don't want a bunch of message alerts. I use Z-wave motion detectors and switches to trigger reliable alerts.1 Photo
Comment
Comment