I have a massive Blue Iris system. While it is not prefect I figured I would help it out a bit with IoX triggers. Example. I have a camera pointed at a door. Blue Iris fails to see someone at the door for what ever reason. At the door I have a motion sensor to turn the light on at might when someone shows up after porch light hours. So I have the IoX fire off a Blue Iris trigger any time the motion sensor goes off. It works really nice. I have other things like this setup. Like when the mail man opens my mailbox. Smile mail man!

(Normal status shown below)

Here is the problem. For what ever reason "Server Status" or "Node Server Online" may change state to "Disconnected". This causes the triggers to stop working. Clicking "Re-Connect" on Blue Iris Plugin will fix either disruption. So I figured I would write a few programs.

Blue Iris Reconect - [ID 00FE][Parent 0001]

If

'Blue Iris' NodeServer Online is Disconnected

Then

Set 'Blue Iris' Re-Discover

Wait 5 minutes

Else

- No Actions - (To add one, press Action')

And this second program

Blue Iris watchdog - [ID 0100][Parent 0001]

If

'Blue Iris' Server Status is Disconnected

Then

Set 'Blue Iris' Re-Discover

Wait 5 minutes

Else

- No Actions - (To add one, press 'Action')

These programs never run. Maybe it runs once and never again? I have to go in and manually click "Re-Discover". Do I have to set these to run at startup? Maybe set my wait to 1 minute?

There conditions besides "disconnected" that will be there when it is disconnected. Like "red". Anyway, use backward logic.

Blue Iris Re-Discover - [ID 00F9][Parent 0172][Run At Startup]

If

'Blue Iris' NodeServer Online is not Connected

Or 'Blue Iris' Server Status is not Green

Then

Wait 1 minute

Repeat Every 1 hour

Send Notification to 'apo' content 'Blue Iris Disconnected'

Set 'Blue Iris' Re-Discover

Else

- No Actions - (To add one, press 'Action')

This works for me.

Problem for whatever reason is if Blue iris goes offline (reboot the computer, power outage, or some hiccup), either Blue Iris needs to restart or you need to rediscover. This is a bug in the node server that they can't seem to correct.

@apostolakisl Thanks for the the reply. Seems you have made this routine bullet proof and repetitive. I am trying to better understand the logic.

Run on start up, why? Shouldn't the if 'Blue Iris' NodeServer Online is not Connected Or 'Blue Iris' Server Status is not Green be enough? I thought of run on startup too, but didn't know why.

Then if the logic is true, it runs every hour; sending a notification and Re-Discover for ever?

I changed mine to combine 2 programs in to 1 using reverse logic as suggested, changed the duration and position of the wait and added the run on start up. I didn't add the repeat as I was unsure what it was repeating. Thanks for you help

Blue Iris watchdog - [ID 0100][Parent 0001][Run At Startup]

If

'Blue Iris' NodeServer Online is not Connected

And 'Blue Iris' Server Status is not Green

Then

Wait 1 minute

Set 'Blue Iris' Re-Discover

Else

- No Actions - (To add one, press 'Action')

8 hours ago, CPrince said:

@apostolakisl Thanks for the the reply. Seems you have made this routine bullet proof and repetitive. I am trying to better understand the logic.

Run on start up, why? Shouldn't the if 'Blue Iris' NodeServer Online is not Connected Or 'Blue Iris' Server Status is not Green be enough? I thought of run on startup too, but didn't know why.

Then if the logic is true, it runs every hour; sending a notification and Re-Discover for ever?

I changed mine to combine 2 programs in to 1 using reverse logic as suggested, changed the duration and position of the wait and added the run on start up. I didn't add the repeat as I was unsure what it was repeating. Thanks for you help

Blue Iris watchdog - [ID 0100][Parent 0001][Run At Startup]

If

'Blue Iris' NodeServer Online is not Connected

And 'Blue Iris' Server Status is not Green

Then

Wait 1 minute

Set 'Blue Iris' Re-Discover

Else

- No Actions - (To add one, press 'Action')

It only repeats every hour if it fails to be connected. So if something is wrong with Blue Iris that keeps being wrong, it will keep trying to reconnect. I also get an email every hour pestering me to go find out what is up with Blue Iris.

The program will only trigger on a change of status of BI. This is why you need the run at startup (and also why you need the repeat). You need to get the repeat every hour thing going if at boot of ISY BI is offline.

Edited 12 hours ago12 hr by apostolakisl