andyf0

In the Alexa app select "Forget All Devices" and then re-discover.

I spent the day at a food bank helping feed the hungry.

I have found that you can also trigger a program with a state variable change by using: if $MyState is $MyState This allows you to trigger without having to use some mythical number.

The problem with your program is that when the door is closed the status of the door sensor changes which causes the program to start again from the beginning. Since the door is closed the "else" portion of your program is executed. Since it's empty, it just ends. If your door sensor is an Insteon device you can use the "if control" statement as mentioned above. If it is a Z-Wave sensor then you'll need two programs: if Status "entry door sensor" is on then Run Program "turn light on" (if or then) else Program "turn light on" if then Set Scene "turn hall light" On Wait 10 mins Set Scene "turn hall light" Off else I would have thought that if the door is closed you'd want the light off anyway, in which case you can simply turn the light off in the "else" clause. If status "entry door sensor" is on Then Set scene "hall light switch" on Wait 10 minutes Set scene "hall light switch" off Else Set scene "hall light switch" off

http://forum.universal-devices.com/topic/21225-isy994i-2844-222-motion-and-fw/

You can try MobiLinc Lite for free to see if you like it. It has a # devices limitation. If you like it then you can upgrade it to the full version. Warning, if you are running the 5.X Alpha software on your ISY, some things won't work correctly.

The current program is stopped and the "if" is re-evaluated.

Can I assume that we shouldn't be messing with these until we have 5.0.9?

I have Honeywell Z-Wave thermostats. In 4.X you can say "if calling for Heat/Cool/Idle". In 5.x I think you do "if Heat/Cool State". I haven't done anything with Fan but I'm sure there's a "if fan mode". You don't use "if control" or "if status". The darn things are so reliable I haven't needed to change or the view the programs in such a long time, this is from memory.

The are two Sonos packages on the Wiki for Network Resources. I'm pretty sure I saw volume up and down in one of them. I only use Mute & Unmute functions in my ISY.

if "Keypad button" is Switched On then Wait 30 mins Set Scene "Keypad Button Scene" Off NOTE. The "if" statement tests the actual button, the "then" statement turns off the scene the button is in. If the button is turned off to turn heater off manually then the program will terminate.

If one of the motion sensors turns off before the other, the program will trigger again and start the 20:15 minute wait all over again. So you could be waiting for up to 40 minutes for the lights to turn off. Both motion sensors would have to turn off at exactly the same time to do what you want, which is likely impossible. Take out one of the sensors in the "if" statement to test if that is what's happening.

I haven't used that scenario. Not sure that CONTROL will work with a Z-Wave device, typically it doesn't, but I hope it works for you. If not, you may want to split this up into 2 programs. if door unlocked run program 2 program 2 if sunset to sunrise turn entry light on and set program 2 to disabled so it doesn't run automatically at sunset.

The program triggers at sunset and sunrise. The access code, once set to 1 stays at 1. So at sunset the program triggers and sees the access code is set to 1 and turns on the entry lighting. Somehow you need to reset the access code. Maybe by doing a lock from the ISY. I haven't played with trying to reset the door lock status.

The lock does not appear in the "Smarthome" skill but if you add the original ISY skill then you can ask or tell "IZZY" to lock or unlock your door.

You said you had it working apart from the last command to close the valve. Open Valve Repeat 4 times Start Zone 1 Wait 5 minutes Start Zone 2 Wait 5 minutes ...... Repeat 1 time Close Valve

To end a repeat cycle add a "Repeat 1 time" to the end of the repeat body. Then you can add another program line to shut off your valve.

You are substituting "phone" & "phone2" with the IP address of your phones right? What you show is just protecting your phone's IP address?

Larryllix, I don't think you understand his method exactly, then again it wasn't described very clearly. Here's what I get from the description. There's a Geofence program on his phone that will set a variable from 140 to 150 on the ISY when he's 5 - 8 minutes out. There's program running on a Pi that is looping every 10 seconds, looking for that variable to be changed to 150. When the Pi program sees the value of 150, it starts looping, looking for the phone's IP address to show up in his Pi device list? It would appear that if the phone is not found in the device list that he sleeps for 60 secs and starts over. When the phone is found in the Pi device list, a different variable is updated, which triggers the ISY to run his "arrive" programs and the original variable is set back to 140. So it appears to be using a combination of GeoFence 5 - 8 mins out and then waiting until his Pi sees the phone before telling ISY he's home. There's no looping on the ISY, that's done on the Pi. Not sure why the two stage check, surely the Pi could just keep looking for the phone to appear in it's device list without the need for a GeoFence on the phone.

Does your program for the switch test for CONTROL On or STATUS On? If CONTROL then only pressing the paddle will cause the program to trigger. If you want to let Alexa trigger the programs then you must use STATUS.

Because I hadn't thought of that Also, wouldn't REST require direct access to the ISY with Port Forwarding in the router etc. Wouldn't that expose your username & password to snooping? (that was for MWareman) Might be too much for some folks. As you can see I don't know much about REST.

Nooo ... Don't be confused by UDI terminology. You don't need IFTTT services. In your mind replace ISY Portal IFTTT section with "Create URL into ISY Portal". IFTTT is not needed. The IFTTT portal section is merely used for creating web URLs into the portal and your ISY. I think we were all confused by this in the beginning.

OK, I'll give it a shot: Log into the portal Click on Select Tool, highlight over Connectivity then select IFTTT Click on Add "SCENE" Type in an Event Name, e.g. Approaching Click on the drop down menu and select All Lights ON Click on the bar below the word Action and Select ON Click on Save There will be a tiny blue arrow to the left of your Event Name, click on it and it will display the URL to POST. If you want to turn the scene OFF create a new event with a different Event Name, e.g. Leaving, select the same scene and set Action to OFF. Enter that URL into Locative, make it a POST. Authentication is not required. I'm assuming you know your way around around Locative. Personally, I prefer to set a state variable to 0 and 1 for leaving / approaching. That way you can test the variable in programs to perform multiple actions. It allows for growth as you become more comfortable with how it works without having to create multiple events in the portal.

I thought you were supposed to put the ISY in linking mode BEFORE pressing the set button on the device. Does it matter?

Exactly my thinking when deciding what to put on the UPS. If power goes out all the switches and outlets go out whether Z-Wave or Insteon. There's nothing to talk to except Z-Wave battery powered devices and they don't talk without being triggered or woken up. Presumably your internet connection goes out too so you can't even send a notification. It's much more useful to run a program on restart to let you know the power fail happened. You can do a Query All automatically on restart by checking the box on the configuration screen. Also, my Z-Wave locks have a number pad on them so I can (gasp!) use my finger if power is lost.