apostolakisl

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.

It sounds like you are saying that the thermostats only report a status change when the temp changes by more than 2 degrees? Not sure that mobile linc makes any difference here since mobile linc would be reporting whatever ISY has in its database. I'm using Agave, ISY Dashboard, and ISY Admin console. All 3 report the same values at any given time. But 2 degrees is kind of a lot. I'm thinking I may need to write a query program and have them query every 15 minutes or something.

I have noticed that the temps do not update in the ISY on their own. Or at least, they aren't updating for many hours. This morning for example, I had to manually query all the thermostats to get the current temp. The temp shown was at least 3 hours old, and perhaps many hours older than that. Should not the thermostat automatically transmit every time a value changes? Like how a light switch transmits every time it changes status. Or do I have something configured wrong? This does not seem to be a com issue since a query pops back with the correct value very quickly.

No, I made this wire. It is b at both ends. But I made it like 10 years ago. It is what was the standard cat5e wire at the time as far as wire quality, but the cat6 heavier gauge wire now is a lot better.

I am just starting to use ISY to control thermostats at my church. These are new heat pump units 2732-242 v11 I can not get them to enter into the program modes from ISY. Either from the admin main console or from programs, I can change them between off, cool, heat, and auto, but not program cool/heat/auto. If I change to one of those modes, ISY shows the change in the console, but if I query it, it shows that it is still whatever it was before. Same thing if I use a program to change the mode. They do go into program mode just fine from the actual thermostat and display as such when queried by ISY. and 5.0.8

The cable works for internet. Currently the ISY is using that cable to connect to the network (successfully). ISY I think is only 100mb, but I am pretty sure I have used that same cable for gigabit . . . meaning that all 4 pairs must work. It could be that the wire is even longer than 30 feet, I haven't measured it. However, based on your comment, I now feel pretty good about making a custom cat6 wire that is 20 feet.

I need to put the PLM in a bit of an open and central location to catch all the thermostats radio signal at my church. We only have the thermostats so there is no PLC or repeating going on here. I've got a great spot with robust communication and now need to run the wire back to the ISY. Currently I've got the ISY next to the PLM as a temporary setup, but I would prefer ISY to be in the network rack with everything else. Was wondering what sort of experience people had with the length of the cable. I tried a 30 foot cat5 I had sitting around and it failed. I have high end cat6 23 gauge in a box and plan to make a custom cable, but don't want to waste my time and effort putting ends on the wire to just find out it is too long. I could perhaps make do with 10 feet, but it would be a much cleaner run with about 20 feet.

I suspect you are correct. I'm not sure what it does with the links then. Does it load the orphaned links if it can't contact the device?

I haven't ever needed to crawl my network. But, when you go to link your first device, it asks you if you want to add all devices that are linked to it. If you click to do that and keep the existing links, then I believe this will crawl through your network adding all links and keeping all your scenes intact. If you instead tell it to add all devices and the devices that are linked to it, but delete the links, then you will get all devices added, but no scenes. So you would then need to create all your scenes from scratch. But the devices would all be there. I am not sure, but it might add your hub as a device even though it isn't online by virtue of the fact that it is linked to your other devices? Maybe not. HOwever, if it does add the hub, then you can delete the hub from ISY and ISY will go through and delete it from everything it is linked to. If you start from scratch, be aware that ISY makes creating scenes pretty quick work. It is just drag and drop. If you have the pro model, you can delay writing the links so you can create all your scenes, then click the button to write it all and go have a beer or two. When you get back it will be done.

The ISY can "crawl" your network. Not that this is brainless. All of your scenes and devices will have no names and you'll have to start figuring things out by trial and error and giving them all names. Then BACK IT UP!! ISY can be backed up and then restored. Also, the PLM can be restored from ISY. You'll still need to manually link battery operated devices and devices on your network that are on "islands". In other words, single devices or groups of devices that are not linked to any devices outside of themselves or their group. Basically, you need to manually enter at least one device on each "island".

According to this thread, yes. http://forum.universal-devices.com/topic/7587-capturing-air-conditioner-ir-commands-2411t-vs-itach-wf2ir/ And this forum has a way to use putty terminal emulator to get the raw output if you fail to get it using the software GC provides. https://forums.homeseer.com/showthread.php?t=170544 My bet is, if you PM the person in the first thread, perhaps they can just send you the codes already done.