apostolakisl

You can avoid turning the light on or off. Assuming your load is not in a dimmed state, you click on when on or off when off and have both trip the same program with a then that executes your task. If your light is on, then click on, if your light is off, click off, either way, the same program runs and you get the same "then" executed and the light doesn't change.

Right, but a double top off, when already off is the same as not doing anything. Same for on. You have several options to use a load bearing switch as a trigger without affecting the load. if status on and control on If status off and control off If status on and control fast on If status off and control fast off As I mentioned, you can't use this when a light is other than on or off. I use If status off and control off All the time.

One thing you can do is off when already off, or fast off when already off, or vice-versa. If (status switch x is off and control switch x is switched off) OR (status switch x is on and control switch x is switched on) Then do something The above will let you use a switch to trigger something without changing the status of the switch and it's load. You can also do a fast on/off version of the same program. The only thing is if the light is in a partially on state, then you either have to go full on or full off.

Just to clarify here, IR models have a built-in IR receiver, but not a transmitter. You need to purchase something like a global cache to send ir. Insteon also makes one but it isn't very good compared to GC.

This is what concerns me. I don't want an always on vpn connection through my home when I'm out. Turning it on and off before running apps i want it on for seems like a time consuming hassle. I can just see a friend saying "show me that HA stuff" and I go through 5 minutes of poking around before I can even start.

The google cloud having access to your voice theoretically means they have access to whatever your voice can control and thus so does an intruder. So, just not allowing your alarm to be controlled by voice should handle it. How do you handle keeping a vpn connection going between your phone and home? I have not tried this but it seems like it would be a PITA. I have only done router to router vpn.

Unless the voice recognition part runs locally, I don't see how the cloud can be avoided no matter what. Even if ISY is controlled locally, if your voice gets sent to Google, decoded, and sent back to google home, which then controls ISY, there is still a cloud hack there. I do see the point about the portal. Hack my house, easier, reward is 1 ISY Hack portal, harder, but reward is lots and lots of ISY's. We all know even the biggest of the big guys can get hacked. EDIT: Well now I'm wishing I hadn't jumped on echo. Oh well, maybe I'll get both.

OK. Indeed this appears to be a 5.x firmware issue. I originally thought it was device specific, but I have now tested it on a couple other devices. So far, all devices I have tested on 5.x trigger status programs when progrmatically queried. I'll move this to 5.x forum.

The only issue you may have with this is that your weather module program has no hysteresis. So, if one of the parameters were bouncing around at the threshold level that program would keep switching back and forth. The one I fear the most on that issue is wind. You might consider dropping wind from it. Temp and rain aren't likely to bounce. To add hysteresis you would add a third program that has the other end of a range that is a sort of no man's land. Hysteresis 1 If wind speed is less than 15 then $state.windspeed = 1 Hysteresis 2 If wind speed is greater than 20 $state.windspeed = 0 In the above example, wind speed variable become true (1) when it is less than 15, and false when it is more than 20. In between those values, it retains its previous value. So you would use the variable in your weather program instead of the direct wind speed.

This is the exact program that does what you intended. BackLawnReSeed - [ID 008A][Parent 0089] If From 7:00:00AM on 2017/05/05 To 10:00:00PM on 2017/05/20 And ( From Sunrise + 4 hours To Sunset - 1 hour (same day) And Program 2 is true Then Repeat Every 2 hours Set 'Devices / dirNodeServers / RainMachine / RainMachine / Rear Lawn' Start Wait 10 minutes Set 'Devices / dirNodeServers / RainMachine / RainMachine / Rear Lawn' Stop Else Set 'Devices / dirNodeServers / RainMachine / RainMachine / Rear Lawn' Stop Program 2 If Module 'Climate' Temperature > 50 °F And Module 'Climate' Total Rain Today < 0.2 " And Module 'Climate' Wind Speed < 15 mph Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') Any false trigger in the main program turns off the water or prevents it from starting. False triggers include the aggregate of your weather module conditions becoming false. You end times (sunset or your hard times). It will also turn on with a true trigger. So, your aggregate of weather conditions become true between the designated times. Or your designated start time while the weather conditions are already true.

This case is different though. You do want the weather module triggers to stop the watering, but ONLY if they change to a value outside of the designated range. You want it to be looked at as the entire set of parameters as being either true or false and only a change from the entire thing true to false or false to true is a trigger, not every incidental change. You do this by using the true/false status of the program containing the weather module info as the trigger. The program stays true no matter how many times the temp or wind or whatever changes, so long as it stays within range. And it will trigger the sprinkler to stop sprinkling if it changes to a value out of range.

I want to say that your program as is will not work. During a wait or repeat, the "if" clause is open to being re-triggered. So any item in the "if" clause that triggers on a status change will re-trigger the program. I do believe this includes climate module value changes. Does this program work currently? I would expect it to not work since I would expect if the temp changed that the program would re-trigger and start over. Ie, during the 10 minutes wait, temp changes by one degree, program restarts from scratch and enters the 10 minute wait again (or worse, it now is false and the lawn keeps getting watered until the next day). Then, lets say the first 10 minute ends and now it is waiting for the 2 hour repeat, but temp changes again, so now program starts all over. Generally a program like this needs a trigger program (that just has the time constraints) and a second program with the just the weather module stuff. If time constraints and weather module program is true Then water routine Else Stop watering weather module program if weather module constraints Then blank Else blank At this point, if the weather module program becomes false, it will re-trigger the main program and it now runs false shutting down the sprinkler. In summary, you can't use "repeat while" since you have multiple parameters, so you use a second program.

Query from programs does trigger, at least on my thermostats in 5.0.10 I have a program set to query the thermostats every 15 minutes and I have email notifications set to send on hvac mode status change. As soon as I started the query program I started getting emails every 15 minutes for all hvac units even though they were all unchanged. Below is the query program and one example of the notify programs. Query T-stat - [ID 0002][Parent 0001][Not Enabled][Run At Startup] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Repeat Every 15 minutes Set 'Alter North' Query Wait 15 seconds Set 'Narthex' Query Wait 15 seconds Set 'Alter South' Query Wait 15 seconds Set 'Upstairs North' Query Wait 15 seconds Set 'Upstaris South' Query Else - No Actions - (To add one, press 'Action') Alter N Auto - [ID 0020][Parent 000A] If 'Alter North' Mode is Auto Then Send Notification to 'Lou and Stuart' content 'N Alter Set to Auto' Else - No Actions - (To add one, press 'Action')

5.0.10 And I guess that also kills my idea about a workaround. I was going to use a variable as an intermediary, but it sounds like that will do the same thing.

I have come to discover that if you query a device and there is a program containing a "status" of that device, the program will trigger even if the query did not result in a change in status. This, to me, is a flaw in the logic. "Status" programs are only supposed to trigger on a change in status. I don't think that a query should result in a trigger of that program unless the query produces a change in status.

I'm not sure what you mean. But "repeat while" is an option, I believe this is a new option in the 5.x It includes integer variables as options for repeat while, so I guess it actively checks with each cycle?

If you are going to do that, I would put it in the pull down column that includes the "for/while/etc".

If UD just put a note there that said "to end repeat, select repeat 1 times" that would take care of it.

NO doubt. But once learned is not forgotten.

Thanks. I'll play around with it and let you know what happens.

I have it all working great as is. I don't need any range extender or repeater. I just want to put the plm about 15 ft away from isy for aesthetics. When I get the time, I'm going to just make a 15 ft cat 6 and see how it goes. Mind you, this is 3 phase, so any repeaters would need to be on the same phase or else I need multiples and then I'll have these boxes plugged I random locations in a public building.

They are 2732-242 v11 heat pump models.

I wish they published the protocols so I wouldn't have to guess and do trial and error. For now, I set ISY to query every 15 minutes with a 15 second wait between each unit.

Perfect, fixed it. Also it got rid of "program cool" and "program heat" which are two modes that I don't think exist. EDIT: The ISY Dashboard still shows "program cool" and "program heat" even though the admin console does not. Also, those modes show up in Agave. I thought it was an Agave problem until I found the dashboard also has it. If I try setting to "program cool" the dashboard responds with an error that the device didn't respond.

They are 2732-242 v11 heat pump models. I just bought them so they should be the most recent firmware. 1.5 c is 3F. That is kind of a lot but is consistent with what I see. What you say about your query experience is not what I see with these. When I do a manual query the temp and humidity update to new values regardless of how small the change. For example, I just did a query on device and the temp changed from 72.5 to 73 and humidity changed from 68 to 69. These are not battery operated, they run on the 24vac from the furnace.