Teken

Teken, did you ever get this to work for your setup? Hoopty, For the interim I have simply replicated all five TSTAT using your original program. I do however have a couple of questions for you. So if you don't mind taking the time to break it down for me, it would be greatly appreciated. Heating ran for a total of 0 cycles today. <-- Why does this not show a value?? Total heating run time was 10 hour(s) 146325 minute(s). <-- Why does the minutes calculate to this amount?? I read the initial thread about the seconds and how you had to divide the numbers etc. But, some how this math doesn't add up. Your insight would be appreciated ! Teken . . .

Hoopty, Thank you so very much for providing the screen shots. I have some questions for you or anyone else who may know. I have five of these thermostats installed and all of them also have the humidity sensor in place. I have copied the original program from the one TSTAT. This copy of the program has been renamed and also the secondary TSTAT has been assigned to as the device to be queried. How do I track this TSTAT and the other ones?? Teken . . .

Would one of you please post up a screen shot of each of the tabs with the above programs / variables in their respective places for me to see and compare. I just can't seem to get this up and running. Teken . . .

Would you mind posting up the final code once its confirmed to be working. As I have the same needs and requirements as well. Teken . . .

I am subscribing to this as I am trying to figure out how to accomplish the same goal. I have four of these TSTATS deployed right now and want to know when they turn on / off. This will allow me more insight as to the state of the home. Teken . . .

I will be pulling these guys out of service and have them replaced under warranty. There is no head way on this matter no amount of resetting and killing the power has any affect on these things. I don't know why my gut keeps telling me there is a conflict with the newest ISY firmware that is causing this issue to appear. Unfortunately I can't roll back the firmware to find out in this case . . . Teken . . .

Hrmmm that is a good point ELA. 1.5 volts isn't a large margin for the battery to go low. But, I believe it could still be done if they wanted to. The basic principle is still the same to monitor the voltage drop. I did however place my thoughts in the idea thread in the SH forum. Even if its in vain, but hey at least its up there for others to ponder or at least know that these devices do not incorporate any such feed back electronics. Teken . . .

I am going to place that as the next upgrade that needs to incorporated into these devices in the SH forum. Its 2012 now, this should be part and parcel and basic 101 for such devices . . . Teken . . .

Really? Damn it !! Teken . . .

Does the trigger linc also provide a one time alert like its 2420 motions sensor brother when it is in a low battery state? Teken . . .

Jeff, That is simply outstanding to say the least! I went the other direction as you, and invested in five Venstar 1800 thermostats along with the humidity sensors. Right now I am just playing around with programs to see if my logic is sound and IF it will do as I expect in the near future. I currently have one in the basement, living room, master bedroom, and hall way. The intent for me is to reduce my energy costs to the bare minimum. All the while taking advantage of all the wasted heat in the ceiling areas. My goal is to locate all the remote TSTAT's high up in the ceiling to read the actual temperatures up there. If a threshold is met (depends on winter / summer) the ceiling fans will turn on (forward / reverse) to move the air up or down to best utilize all that wasted hot / cool ambient air. The bigger picture is to have the whole HA be self aware and to react to the immediate temperature, light, energy, status of each device. It will then place the home in several states to ensure minimal power, while balancing heat, electrical needs for the home and family. I am currently on phase two of the goal and hope to be at phase six in the next 5 years. Thank you for your follow up and feed back. Please do keep us all updated with the end results of the other remote sensors etc. Teken . . .

Michel, This would explain the hanging login in window sitting in the for ground of my Opera browser. It eventually went away but based on your explanation the ISY did not shut down gracefully. Much thanks as always Sir. Teken . . .

This afternoon I was doing some maintenance and added in the first of five Venstar thermostats. Everything seems really good and first impressions is that these new Insteon enabled TSTATS will come in very hand and help me complete my HA system. Now, after logging out for several hours I wanted to create a few programs to see how they worked. I never got that far as the Admin Counsel did not provide me any sort of status updates of the various devices. I figured no problem, so I selected query all. This pop up message came up?? Teken . . .

Sorry for late reply as I did not subscribe to this thread correctly. As far as I am aware you can not use those external sensors with the ISY. Meaning, the ISY will have no interaction with those external sensors. Having said this I would be curious to see what would happen to the TSTAT, while it was connected to the ISY. As far as I am aware nobody has ever gone this route to find out what type of results would come out of this set up. If you decide to pursue this avenue please do keep us all informed as to the outcome and how it interacts with the ISY platform. Teken . . .

Have you asked him? No I haven't yet, but does it really matter if he used Yellow instead of Red? In the big scheme of things it doesn't matter. So long as you *The Owner* is aware of what the color means and how it affects future reno's etc. Teken . . .

I would ask you to first upgrade the ISY's firmware to the latest official 3.XX. As this has resolved a lot of Insteon issues as well as added support for various devices, and features. Next, I would ask you to remove the Icon device, perform a hard factory reset. Then, add the the Icon device via the automatic discovery. Then, try the same changes via the ISY Admin Center. Teken . . .

Here is the trace from the Ceiling Light. This device is V.38 and did work before several firmware changes came along. Below is the diagnostic trace records as per your request. Teken . . . Thu 02/02/2012 03:01:05 PM : [iNST-ACK ] 02 62 11.DC.42 0F 1F 00 06 GOF (FLAGS) Thu 02/02/2012 03:01:06 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 1F 00 GOF (FLAGS) Thu 02/02/2012 03:01:06 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 02/02/2012 03:01:06 PM : [All ] Writing 0 bytes to devices Thu 02/02/2012 03:01:06 PM : [iNST-ACK ] 02 62 11.DC.42 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 06 (00) Thu 02/02/2012 03:01:07 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 2E 00 (00) Thu 02/02/2012 03:01:07 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 02/02/2012 03:01:08 PM : [iNST-ERX ] 02 51 11 DC 42 13 24 E1 11 2E 00 01 01 00 FF 20 00 1B 08 00 00 00 2C 03 00 Thu 02/02/2012 03:01:08 PM : [Extended-Direct][11.DC.42-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Thu 02/02/2012 03:01:08 PM : [All ] Writing 0 bytes to devices Thu 02/02/2012 03:01:17 PM : [iNST-ACK ] 02 62 11.DC.42 1F 2E 00 01 06 64 00 00 00 00 00 00 00 00 00 00 00 06 (00) Thu 02/02/2012 03:01:17 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 2E 00 (00) Thu 02/02/2012 03:01:17 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 02/02/2012 03:01:17 PM : [All ] Writing 0 bytes to devices Thu 02/02/2012 03:01:23 PM : [iNST-ACK ] 02 62 11.DC.42 0F 1F 00 06 GOF (FLAGS) Thu 02/02/2012 03:01:24 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 1F 00 GOF (FLAGS) Thu 02/02/2012 03:01:24 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 02/02/2012 03:01:24 PM : [All ] Writing 0 bytes to devices Thu 02/02/2012 03:01:24 PM : [iNST-ACK ] 02 62 11.DC.42 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 06 (00) Thu 02/02/2012 03:01:25 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 2E 00 (00) Thu 02/02/2012 03:01:25 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 02/02/2012 03:01:26 PM : [iNST-ERX ] 02 51 11 DC 42 13 24 E1 11 2E 00 01 01 00 FF 20 00 1B 07 00 00 00 2D 05 00 Thu 02/02/2012 03:01:26 PM : [Extended-Direct][11.DC.42-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Thu 02/02/2012 03:01:26 PM : [All ] Writing 0 bytes to devices Thu 02/02/2012 03:01:30 PM : [iNST-ACK ] 02 62 11.DC.42 1F 2E 00 01 06 32 00 00 00 00 00 00 00 00 00 00 00 06 (00) Thu 02/02/2012 03:01:31 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 2E 00 (00) Thu 02/02/2012 03:01:31 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 02/02/2012 03:01:31 PM : [All ] Writing 0 bytes to devices Thu 02/02/2012 03:01:35 PM : CLI-WBug: Connecting to datafeed.weatherbug.com Thu 02/02/2012 03:01:35 PM : CLI-WBug: Successfully Processed WBug Response Thu 02/02/2012 03:01:35 PM : [MOD 2 2 1 11] 20000.000000 Weather - Wind Speed = 2 km/h Thu 02/02/2012 03:01:38 PM : [iNST-ACK ] 02 62 11.DC.42 0F 1F 00 06 GOF (FLAGS) Thu 02/02/2012 03:01:38 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 1F 00 GOF (FLAGS) Thu 02/02/2012 03:01:38 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 02/02/2012 03:01:38 PM : [All ] Writing 0 bytes to devices Thu 02/02/2012 03:01:39 PM : [iNST-ACK ] 02 62 11.DC.42 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 06 (00) Thu 02/02/2012 03:01:39 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 2E 00 (00) Thu 02/02/2012 03:01:39 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 02/02/2012 03:01:39 PM : [iNST-ERX ] 02 51 11 DC 42 13 24 E1 11 2E 00 01 01 00 FF 20 00 1B 07 00 00 00 2D 05 00 Thu 02/02/2012 03:01:39 PM : [Extended-Direct][11.DC.42-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Thu 02/02/2012 03:01:39 PM : [All ] Writing 0 bytes to devices

That would be correct. So is this OK or no? I'd really like to hammer out this issue before I decide on buying new switches. Don't want to buy anything until I know they are not going to get damaged. If I understand what LeeG is alluding to. He is asking whether or NOT the neutrals that are tied together are indeed on the same phase / leg. If they are no worries. If they are indeed tied into two different phase / legs of the electrical panel this may pose the problem you're seeing now. I find it hard to believe this problem just appeared after two years though?? Zick, you're the member from the GJ forum as well?? Teken . . .

Zick, What type of load is the switch in the mechanical room controlling?? Is it indeed a dimmable load?? Teken . . .

LeeG, I just read about this a few seconds before you replied. Thank you again for the clarification and insight as always. Teken . . .

oberkc, That was a most excellent write up! Follow question though, do you have any other check box's selected in the options window? Case in point do you have the *Relay follows input* enabled? Teken . . .

I could understand this point *IF* all things are were equal. But, in this case I can accept that the older i1 devices don't / won't be able to take advantage of the new software etc. But, one of them had always worked fine prior to any of these firmware upgrades. Now it doesn't work at all, and has a 0 value for the timer?? Then, there are the newer style v.38 devices . . . Only one of them seems to work in terms of the default timer of 15 minutes. Yet it can not be changed?? This device controls the stair lighting. The other v.38 device controls the ceiling lights which has the same v.38 and has the 255 minute default. Which previously had a 15 minute timer, now it can not be reset, or changed?? I am at a loss here and am looking for some assistance here . . . Teken . . .

For this reason, it is important that the KPL button be configured in "non-toggle on" (of course, the relay has to be configured to respond to "on" commands). This way, the only way for the KPL light to be off is from a sensor command. Being configured in this way gives one a high confidence that KPL off means garage door closed. I am one of those that LeeG mentioned as a fan of the wiki approach. oberkc, Would you mind documenting each of the steps to achieve this end goal. As I have tried this several times with out success, while others have done the same with positive results. I am trying to understand what steps were missed, or omitted while this task was done. This will also benefit the forum members in the future should they come across this same problem. Regards Teken . . .

So, where does this leave me then?? Teken . . .

The only problem as LeeG mentioned with using one KPL button to turn on / off the OH Garage Door. Is that the act of pressing the KPL button a second time to close the OH Garage Door will turn off the KPL LED before the door has actually closed. Using a remote control, or any hard wired OH Garage Door opener will in fact display the correct state of the door though. As aside: I am using a SmartLinc along with an ApplianceLinc to show me the door status independently of the ISY system. The reason for this is to ensure a level of access, confirmation, and feed-back. I work in a very high security environment and thus at times our fire wall blocks remote access to the ISY's true status of devices. Regards Teken . . .