Vera Blue Iris Unofficial Plugin

I’ve been playing with the motion trigger and record capabilities of the Plug in and I’m very impresses. I have my cameras connected on my Secondary Vera 3 in a bridged environment and although there is a slight delay for the Motion Sensor status to transmit to the Primary Vera it appears usable.

i have configured a PLEG to detect the Camera Camera Motion Sensor state and combine it with the state of the Front Door Open/Closed sensor to prevent any Blue Iris recording activity when the door is opened first … i.e. someone is leaving the house. This way I will only get recordings when someone approaches the closed front door. Its still not working as intended but I expect it will once I get everything configured properly.

The real reason for this post is to suggest that if possible you embed the WGET Record command on the “Record” button of the Camera Icon and expose that to PLEG. This way configuring the functions would be a straightforward device level function selection and not involve fiddling with LUA code in the PLEG Action function. All of the values for the WGET are already available in the Camera Device.

Thanks for this great tool.

Further to my earlier post I’ve plugged this luup code into the Action of a PLEG:

luup.inet.wget (“http://xxx.xxx.xxx.xxx:9080/admin&Camera=Entry&trigger&user=name&pw=pass”)

and when the PLEG activates nothing records.

i used “http://xxx.xxx.xxx.xxx:9080/admin&Camera=Entry&trigger&user=name&pw=pass” in a web browser and got back “signal=green” but no recording.

I know its something simple but i’m not seeing it.

It looks like you might have a space after wget. If so, then you need to remove it.

In my Blue Iris Web Server settings, I have Authentication=Non-LAN only and the Secure only box unchecked (but I still need to put the user and pw in the html string). EDIT: Clarification: With Secure Only unchecked, I think you still need the user/pw. I was fooled once since I could get it to work in the browser without user/pw. But that was because I had authenticated earlier. Once I quit the browser, then the trigger wouldn’t work anymore without user/pw.

Make sure you are using the camera short name and not the “regular” name in the camera’s Blue Iris General tab. This has screwed me up many times (until I decided to change all short names and full names to be identical).

Also: I use TeamViewer a lot on my LAN and believe that the copy/paste is unreliable. It seems to sometimes miss characters or use non-standard characters. So I sometimes paste into a plain text editor and then re-copy/paste from there. If that doesn’t work, then I just manually re-type. It’s confusing since the pasted text looks OK but then re-typing solves the problem.

Thanks, it’s probably something as stupidly simple like an extra space :slight_smile:

But since you were having trouble with getting it to work in the web browser, the extra space doesn’t explain that failure. :wink:
Also try using a browser other than Chrome.
Edit: FYI - You can enter in a lot of “bad” commands/typos via the browser and still receive the “signal=green” response. So “signal=green” isn’t super helpful in troubleshooting.

[quote=“fcol, post:165, topic:181819”]But since you were having trouble with getting it to work in the web browser, the extra space doesn’t explain that failure. :wink:
Also try using a browser other than Chrome.
Edit: FYI - You can enter in a lot of “bad” commands/typos via the browser and still receive the “signal=green” response. So “signal=green” isn’t super helpful in troubleshooting.[/quote]

Now that you mention it that’s true.

I tried it in FireFox and got the same result, “signal=green” but no recording happened.

Is the process sensitive to the path/location of WGET?

I’ve been playing around some more. I’m finding this works a lot better in my scenes:

local status, result = luup.inet.wget("http://XXX:XXX/admin?camera=SHORTNAME&trigger&user=XXX&pw=XXX")

I have no idea why adding "local status, result = " works but this seems to be the most reliable way for my setup.

I also just noticed that when testing in the browser, I DO need the user/pw. I had it working without user/pw but once I quit the browser and tried again, then it wouldn’t work. So it must authenticate once and then subsequent http commands work without user/pw. But the bottom line is that I need user/pw in my luup

Sorry clippermiami - I’m not sure what else to tell you. I feel like it has to be something like typo in shortname or your user/pw (since you’re getting the signal=green). You could try some of the other Blue Iris command requests such as http://IPXXX:PORTXXX/admin?profile=X (Temporarily change the active profile to x. Use x=-1 to toggle the lock status). Other commands can be found in the built-in Blue Iris help under “The Web Server” section.

And apologies to undertoe if we hijacked this thread… Maybe we should start another?

Im still having issues.

Ive tried with the http:// and without but still no joy. Testing directly through a browser works every time using Safari, so I know the URL is correct. Ive tried the suggestion of adding local status…etc…but also no joy

Ill keep playing around with it and keep you guys updated, but any more suggestions would be a great help.

[quote=“rafonline, post:168, topic:181819”]Im still having issues.

Ive tried with the http:// and without but still no joy. Testing directly through a browser works every time using Safari, so I know the URL is correct. Ive tried the suggestion of adding local status…etc…but also no joy

Ill keep playing around with it and keep you guys updated, but any more suggestions would be a great help.[/quote]

Did you ever setup a trigger? Save and name it and everything. Maybe it’s not working because the scene is incomplete.

Fcol lol I was just about to say that. Be nice if we could start a BI tech support forum. I do know some of BI support is on the vera forum.

I think with my latest plugin once properly test will solve all your issues. In very easy to use calls and no need for long luup scripts. I also put in some feature request for specific urls for BI to make things more intergrated.

Fcol lol I was just about to say that. Be nice if we could start a BI tech support forum. I do know some of BI support is on the vera forum.

I think with my latest plugin once properly test will solve all your issues. In very easy to use calls and no need for long luup scripts. I also put in some feature request for specific urls for BI to make things more intergrated.

I had to power cycle the WiFi Access Point that services the cameras and after it came back up and the cameras reattached i noticed that the Tile reflects “Camera Not Responding” but clicking View displays the camera contents (screen captures attached.)

Is this normal? Is there any way to force the Tile to update/track the actual camera data?

I have seen that before but not recently. I thinking its more a interface bug than anything. Cause the couple times i did see it i just reloaded and it went away. I don’t think that view updates frequently as when you maximize it.

Just FYI, I reloaded the Vera and it didn’t change. Clearly it isn’t the end of the world, but its just disconcerting :slight_smile:

I think this is a VERA issue. Had it a number of times with the camera alone with the BI plugin. That image doesn’t refresh for some time. And when it does it should go back to normal.

I think this is a VERA issue. Had it a number of times with the camera alone with the BI plugin. That image doesn’t refresh for some time. And when it does it should go back to normal.[/quote]

Like i said not the end of the world :slight_smile:

Great plugin. Would anyone know why when viewing the camera I get a constant popping noise. I don’t have the noise when viewing in Blue Iris or the Foscam camera program.

Remove tick box in user section in bi for play sound on conect :slight_smile:

I don’t think that it. I have the same problem. It’s a constant noise when your listening to audio from the camera threw this plugin.

not the pop when you login.

If this is not related to the plugin functionality inside vera please start a separate thread. this thread is strictly for plugin support and improvements.