CPrince

I figured there is a lot more to this. So where can I go to learn more about this?

@mmb I hate learning new stuff! It seems you are using BI to trigger EISY. We are using EISY to trigger BI. This is interesting. I have done some research and see that REST is an API. I think i figured this out. I was able to set a variable in EISY through a browser with this knowledge. I like this. So now I assume: 192.168.0.106 is the EISY. (I thought it was BI) /rest calls the API /vars is the variable location on EISY /set is to set a variable /2 is state variable /38 is your variable /1 is the data

Glad I asked. Now I know why some of my programs don't work till the next day after a reboot. Keep forgetting about change of state. I will add in the repeat.

@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')

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?

@Athlon I had to do that too. I just used the IP address:8443 instead of polisy.local:8443 . Lots of info in that file!

@Guy Lavoie I would agree. This code was left over from some old sensors with actual heartbeats. Rather than remove some in-depth code and rewrite some new code; I patched the old. I was being lazy. But at the same token it was why reinvent the wheel. I was like it is all here, just use the "Else"!

@larryllix Thanks. "If anything triggers evaluation the two times with never be true and Else will always get run." This is exactly where I got stuck and did not know how to fix. My problem is my lack of good knowledge of integer and state variables. I changed the $SouthGate and $NorthGate variables to integer.

I kind of get why this is happening but I don't. Just can't wrap my head around it. I thought of breaking it up into 2 programs but don't think that will work. I am looking to clean up this program. It works fine with the exception that it runs the “Else” part at 3:01 AM when I update my flag in another program. The flag is a heartbeat flag. If the flag stays the same, it still runs at 3:01 AM. These are unnecessary messages. I only wat the 8:55 and 5:55 message. My gate sensor does not have a heartbeat. It does have a Unix time stamp. So, I look to see if yesterday’s stamp is less than today’s stamp and if so, set my flag to 1. If not, I set it to 2. Gate Sensor Problem - [ID 0076][Parent 006C] If ( Time is 8:55:00AM Or Time is 5:55:00PM ) And ( $sSouthGate is not 1 Or $sNorthGate is not 1 ) Then Send Notification to 'Chris email' content 'Gate Sensor Problem' Wait 5 seconds Send Notification to 'Pushover' content 'Gate Sensor Problem' Wait 5 seconds Set 'Notification Controller / UD Mobile' Send Message Content 20 Notification ID (ID=20) Else Send Notification to 'Chris email' content 'Gate Sensor Normal' Wait 5 seconds Send Notification to 'Pushover' content 'Gate Sensor Normal' Wait 5 seconds Set 'Notification Controller / UD Mobile' Send Message Content 21 Notification ID (ID=21)

Thanks. I am at 10.1 Must squirrel that link away.

Thanks I did that and it worked. 5.9.1 is the IoX. So what is the OS ver and where is it found? I know I am not at 10.3. I Thought the 10.3 OS in this latest 6.0.0 release referred to Mac OS.

I am at 5.8.4 and figured I should upgrade to 5.9.1 on my Polisy as 6.0.0 was just released and does not support Polisy. Anyone know where I can get the image and instructions? I figure if I hit Upgrade Packages I will go to 6.0.0 and brick my Polisy.

@CPrince Gee I just fixed it... How do I get my Echos to stop saying "Somebody is at Virtual Button..."? Amazon is always experimenting with new features, and one new feature is to automatically announce the pressing of your Virtual Buttons (what fun!). To turn this off, open your Alexa App and choose the Devices icon in the lower right part of the screen. Next choose All Devices and scroll through the list to find your Virtual Button XX device(s), select it, then switch the Doorbell Press Announcements slider to the off position. You might have to do this for each Virtual Button you own.

About 2 years ago I installed the VirtualButtons plugin on my Polisy. I started with 2 buttons and used 1 button to tell me that I have mail when my mailbox sensor gets triggered. This process is done through Alexa. For the most part the software works fine. Hardware has been an a slight issue. I just upgraded my mailbox sensor to a YoLink sensor for better reliability. So the other day I used my second button for my gate sensors. Now when a gate is opened, I get a verbal message through Alexa. Life is good. These 2 buttons work correctly. Today I added 3 more virtual buttons. They are not working the same. I have gone through Alexa routines, PG3 and Polisy. Can't find anything wrong. If I trigger my 3rd virtual button, I get my message "Test", a chime sound, then Alexa says "Someone has just pressed Virtual Button 3, followed by another chime sound. I just want Alexa to say "Test". I don't know where all this other stuff is coming from. The only difference I see is button 1 and 2 (my old buttons) look like this... Button 3,4 and 5 (my new buttons) look like this.... I have no idea how to change them from true to false or how that value gets assigned in the first place.

Update on the Z Wave Ring Outdoor Contact Sensor ver 2. It is as Z Wave as they come. I put a Zooz 700 dongle in my Home Assistant. Then I added the Ring contact sensor. The only difference was Home Assistant asked for the PIN which is printed on the device and Polisy did not. So if you have these laying around you can put them to use with Home Assistant. Maybe someone will come up with a Polyglot plugin for Ring?