apostolakisl

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.

You could do the same thing with the GC unit but use wifi instead of zwave. https://jet.com/product/detail/79850baa942c4baca6fe20a363a41af4?jcmp=pla:ggl:NJ_dur_Gen_Electronics_a1:Electronics_Computers__Accessories_Networking_Products_a1:na:PLA_785706707_43734981249_pla-292654441803:na:na:na:2&code=PLA15

Or, it would be cleaner to use enable/disable and avoid the variable 2 Copy - [ID 0153][Parent 0093] If On Sat Time is 1:00:00AM Then Wait 168 hours (Random) Enable Program '2 Copy Copy' Else - No Actions - (To add one, press 'Action') 2 Copy Copy - [ID 0154][Parent 0093][Not Enabled] If Time is Sunset Then Wait 3 seconds (Random) Do your stuff here Disable Program '2 Copy Copy' (this program) Else - No Actions - (To add one, press 'Action')

If you want it to happen on a random day of week, but at a specified time you need 1) 2 programs 2) a variable The first program sets a variable to 1 at some random time during the week The second program runs only if the variable is 1 at sunset. It waits a random amount of time for 3 hours and executes. You can't do Sunset to a specific time because sunset to that time changes every day. You would need to think about the exact timing of setting the variable to 1. As it stands now, if it randomly sets to 1 after sunset on the 7th day, the program won't run that week. Also, you would want to adjust so that there is an equal probability of it being one at sunset all days of the week. 2 Copy - [ID 0153][Parent 0093] If On Sat Time is 1:00:00AM Then Wait 168 hours (Random) $Int_RandomDay = 1 Else - No Actions - (To add one, press 'Action') 2 Copy Copy - [ID 0154][Parent 0093] If Time is Sunset And $Int_RandomDay is 1 Then Wait 3 hours (Random) $Int_RandomDay = 0 Do your stuff here Else - No Actions - (To add one, press 'Action')

You would use the "wait" and "random" feature 2 Copy - [ID 0153][Parent 0093] If On Sat Time is 1:00:00AM Then Wait 168 hours (Random) put whatever you want to happen here Else - No Actions - (To add one, press 'Action') There are 168 hours in a week. This program triggers once per week at the same time (makes no difference what day of week or time you pick), then it waits a random amount of time between 0 seconds and 168 hours (one week). The next line after the wait is where you put what you want to happen. Once it finishes the random wait time, it executes your desired action, then the program ends. The process restarts the random one week event starting at the "if" time. In summary, whatever your action item is, it will happen once per week at some random time during that week.

I solved it by 1) Rebooting ISY 2) Restoring Device

I actually tried that already, but again. . . ."request failed"

I just added two new 2477 dimmers to replace two older ones. ISY found the two devices, added them, then I did a "replace with" to replace the two old devices with these two new devices. All of this appeared to work. Then I tried to move the two devices into the folder they belong in. The one device worked fine. The second device failed to move. I then tried to query it and control it. I either get no response at all from ISY or it says request failed. I tried rebooting the admin console a couple times with no affect. What gives here? The device does seem to have been properly programmed as it does control and respond to scenes.

No worries, I understand that they have shut off electricity in SF today. That will keep the bill down. EDIT: And you are correct, programs with from/to times and nothing else in the "if" will trigger at the from and to times only. So they will not conflict with each other.

This is probably not what you want, however, you can get a global cache ir device. Via the network module, you can send tcp commands specific to each ir signal to the global cache, and it "shines" out the ir signal. It is only one way of course, you get no feed back from the unit. Basically, it is a learning remote, but instead of pushing buttons, you send tcp commands to it. The GC doesn't store the commands, rather, when you "learn" the commands, it gives you a long string of values that you put into your tcp command. They also have some libraries which I imagine include your mini-split system.

Yes, only UD can transfer the license for your modules to the new ISY. It is done remotely.

If you want the same message both times, then yes. I thought it would be nice to have the first statement say "pump turned on" and second one two minutes later to say "pump now on for 2 minutes".

I don't think you need variables at all. Now I am taking stusviews word on this that control synchrolink terminology is correct since I don't have any of those, but it looks good to me. If control synchrolink is switched on and control synchrolink is not switched off (when pump shuts off, this line kills the "then" wait and reruns the program, which is now false causing the else to run) Then send notification pump switched on wait 2 minutes send notification pump still on after 2 minutes optional additional wait 10 minutes send notification pump still on after 12 minutes etc. Else - - - blank optional send notification pump shut off

If you do it from the on/off switch on the unit I'm sure it won't. But you should also make sure that the same is true if you go from on to off to on again by pulling the power.

Yes, if you turn off, then back on too soon, the downstream refrigerant will still be under high pressure. So if the compressor tries to start against that load, it won't spin, electricity will flow, and the coils will overheat and fry. If you wait, after a few minutes, the pressure bleeds down until the suction side and the compressed side become equal. Then the compressor can start without undue loading. I'm assuming an Insteon thermostat has short-cycle protection built-in to its programming?

The simplest way to do that would be to put a switch on the power supply. But as mentioned, restoring power to the unit might not turn it on if it has any sort of "smart" control. It might come on to a standby mode requiring you to push a button on it.