sceaton

Hello! My 994i/ir is misbehaving. Yesterday I turned the kitchen lights off from a switchlinc, took a few steps away and they turned back on again! I decided to restart the isy and when I did, the power, RX & TX lights all stay lit. The MEM light flickers a bit at startup, but the other three never go out. I tried resetting the PLM. No dice. I tried unplugging the PLM for a long time. No help. I tried logging in to the ISY, but I can't. The PLM light is lit and blinks when there is traffic on the network. It's the older non-dual-band version. The ISY was powered via the PLM so I plugged it in using the power adapter, but that didn't help. Any ideas? Bad PLM? Bad ISY?

Those setpoint updates came back only after I manually queried the thermostat from the Admin Console -- I didn't get them automagically after changing the setpoints on the thermostat. It seems I'm never getting updates when the thermostat is supposed to send them "on its own". If I ask for them (query) it will respond (except the fan) but it not sending updates on its own accord. Yes, this is the only thermostat. Do you think it or the adapter could be defective? Thanks!

So when I change the setpoint on the thermostat, the new setpoint is NOT reflected in the ISY. If I manually query the thermostat from the admin console, the setpoint values are updated correctly (except for the fan status, which remains at "ON"). I added the thermostat in the OFF mode originally, but to be sure, I removed from ISY, and re-added. I then changed the setpoint via the admin console to create a heat demand (see below code) and waited 4 minutes, but didn't see anything in the log and of course my program didn't trigger. Mon 03/22/2010 05:32:56 PM : [iNST-ACK ] 02 62 14.06.CC 0F 6B 06 06 (06) Mon 03/22/2010 05:32:56 PM : [iNST-SRX ] 02 50 14.06.CC 0C.A5.8D 23 6B 06 (06) Mon 03/22/2010 05:32:56 PM : [standard-Direct Ack][14.06.CC-->ISY/PLM Group=0] Max Hops=3, Hops Left=0 Mon 03/22/2010 05:32:56 PM : [ 14 6 CC 1] CLIMD 3 Mon 03/22/2010 05:32:56 PM : [iNST-ACK ] 02 62 14.06.CC 0F 6A 20 06 (20) Mon 03/22/2010 05:32:57 PM : [iNST-SRX ] 02 50 14.06.CC 0C.A5.8D 23 6A 20 (20) Mon 03/22/2010 05:32:57 PM : [standard-Direct Ack][14.06.CC-->ISY/PLM Group=0] Max Hops=3, Hops Left=0 Mon 03/22/2010 05:32:57 PM : [iNST-SRX ] 02 50 14.06.CC 0C.A5.8D 03 6A 9C (9C) Mon 03/22/2010 05:32:57 PM : [standard-Direct][14.06.CC-->ISY/PLM Group=0] Max Hops=3, Hops Left=0 Mon 03/22/2010 05:32:57 PM : [ 14 6 CC 1] CLISP 32 Mon 03/22/2010 05:32:57 PM : [ 14 6 CC 1] CLISPC 156 Mon 03/22/2010 05:32:57 PM : [ 14 6 CC 1] CLISPH 32 Mon 03/22/2010 05:33:16 PM : [iNST-ACK ] 02 62 14.06.CC 0F 6D 94 06 (94) Mon 03/22/2010 05:33:17 PM : [iNST-SRX ] 02 50 14.06.CC 0C.A5.8D 23 6D 94 (94) Mon 03/22/2010 05:33:17 PM : [standard-Direct Ack][14.06.CC-->ISY/PLM Group=0] Max Hops=3, Hops Left=0 Mon 03/22/2010 05:33:17 PM : [ 14 6 CC 1] CLISP 148 Mon 03/22/2010 05:33:17 PM : [ 14 6 CC 1] CLISPH 148 Mon 03/22/2010 05:37:55 PM : [iNST-ACK ] 02 62 14.06.CC 0F 6D 90 06 (90) Mon 03/22/2010 05:37:55 PM : [iNST-SRX ] 02 50 14.06.CC 0C.A5.8D 23 6D 90 (90) Mon 03/22/2010 05:37:55 PM : [standard-Direct Ack][14.06.CC-->ISY/PLM Group=0] Max Hops=3, Hops Left=0 Mon 03/22/2010 05:37:55 PM : [ 14 6 CC 1] CLISP 144 Mon 03/22/2010 05:37:55 PM : [ 14 6 CC 1] CLISPH 144 I also changed the setpoint from the thermostat, waited 5 minutes and the change was not reflected in the ISY. I manually queried the thermostat: Mon 03/22/2010 05:56:55 PM : [iNST-ACK ] 02 62 14.06.CC 0F 6A 00 06 (00) Mon 03/22/2010 05:56:55 PM : [iNST-SRX ] 02 50 14.06.CC 0C.A5.8D 23 6A 94 (94) Mon 03/22/2010 05:56:55 PM : [standard-Direct Ack][14.06.CC-->ISY/PLM Group=0] Max Hops=3, Hops Left=0 Mon 03/22/2010 05:56:55 PM : [ 14 6 CC 1] ST 148 Mon 03/22/2010 05:56:56 PM : [iNST-ACK ] 02 62 14.06.CC 0F 6B 02 06 (02) Mon 03/22/2010 05:56:56 PM : [iNST-SRX ] 02 50 14.06.CC 0C.A5.8D 23 6B 03 (03) Mon 03/22/2010 05:56:56 PM : [standard-Direct Ack][14.06.CC-->ISY/PLM Group=0] Max Hops=3, Hops Left=0 Mon 03/22/2010 05:56:56 PM : [ 14 6 CC 1] CLIMD 3 Mon 03/22/2010 05:56:56 PM : [iNST-ACK ] 02 62 14.06.CC 0F 6A 20 06 (20) Mon 03/22/2010 05:56:56 PM : [iNST-SRX ] 02 50 14.06.CC 0C.A5.8D 23 6A 8E (8E) Mon 03/22/2010 05:56:56 PM : [standard-Direct Ack][14.06.CC-->ISY/PLM Group=0] Max Hops=3, Hops Left=0 Mon 03/22/2010 05:56:57 PM : [iNST-SRX ] 02 50 14.06.CC 0C.A5.8D 02 6A 9A (9A) Mon 03/22/2010 05:56:57 PM : [standard-Direct][14.06.CC-->ISY/PLM Group=0] Max Hops=2, Hops Left=0 Mon 03/22/2010 05:56:57 PM : [ 14 6 CC 1] CLISP 142 Mon 03/22/2010 05:56:57 PM : [ 14 6 CC 1] CLISPC 154 Mon 03/22/2010 05:56:57 PM : [ 14 6 CC 1] CLISPH 142 Mon 03/22/2010 05:56:57 PM : [iNST-ACK ] 02 62 14.06.CC 0F 6A 60 06 (60) Mon 03/22/2010 05:56:57 PM : [iNST-SRX ] 02 50 14.06.CC 0C.A5.8D 23 6A 4C (4C) Mon 03/22/2010 05:56:57 PM : [standard-Direct Ack][14.06.CC-->ISY/PLM Group=0] Max Hops=3, Hops Left=0 Mon 03/22/2010 05:56:57 PM : [ 14 6 CC 1] CLIHUM 76 And the setpoint updated correctly in the ISY, but the fan still said "ON". If I can query the thermostat and get the correct setpoints back, then the access point shouldn't be the problem since that proves 2-way communication between the ISY and the thermostat, right? It still seems as though this thermostat isn't sending updates like it should. Anything else to try?

Hi Michel! The program is enabled, and the back of the adapter says "Rev 2.0" The ISY reports the thermostat adapter as "v.91" Indeed my L3 event viewer comes up empty. I adjusted the setpoint on the thermostat so that it was calling for heat, and no traffic was observed. I'm still old school with signalincs for phase coupling and just added a dual-band lamplinc for the thermostat. I know there have been issues with the DB lamplincs but other communication to the thermostat has been flawless. Programs change mode and setpoints just fine. It seems as though the thermostat isn't sending out its status updates like it should. I don't have the adapter linked to any other device, I just added it through the ISY admin console. (I read that it will only send updates to the last linked device.) Should I remove the thermostat and re-add? As a separate issue: Looking at the node in the admin console, the Fan Status often says "ON" even though the thermostat is set to Auto. This remains incorrect, even after I query the device. The other info (temp, setpoints, etc.) are correct. Manually selecting "Auto" (does nothing, since the thermostat is already in auto) then Selecting "ON" turns the fan on, and changing back to "Auto" turns the fan Off. I'm not sure how the ISY loses sync with the fan status, and further why it doesn't re-sync when manually Queried. Anything else to try? TIA! ~shawn

Hello all! This program: If Status 'Thermostat' is Calling for Heat Then Send Notification to 'Email Shawn' Else Send Notification to 'Email Shawn' ... never triggers when the thermostat calls for heat. If I manually run the program the notfications are sent properly (so notifications are working), but when the thermostat calls for heat, the program does not run. I wanted to see how many cycles and how long the heat runs so I wanted an email when it turned on, and another when it turned off. What am I missing? BTW, I upgraded from 2.7.6 to 2.7.12 flawlessly, then again to 2.7.13, again without issue. Thanks!

Here here! A toast to Michel and Chris! I must say it has been a lot of fun being on the "front line" of the ISY development, solely to the credit of UDI ... their "community" involvement is second to none. Cheers! ~shawn

If I "replace" a KPL for a new V1.5 KPL, any programs referencing the buttons on the "old KPL" were not updated in programs. For example, after the update my programs look like this: If X10 'D2/On (3)' is Received Or Control is switched On Then Set Scene 'TV' On Else - No Actions - (To add one, press 'Action') Is the ISY capable of updating programs when devices are replaced? ... if not, maybe the msg box that pops up that explains that after the updating process, the window will close, etc. can also contain a note to update any programs referencing the old device. cheers! ~shawn

Same thing here. New v1.5 received today and I too got the "Request Failed" message after adding via "New Insteon Device" Apparently the 1.5's have a whole new batch of quirks. whoohoo!

I just retested and indeed if the program has ONLY the wait action in the "Then" and is run manually, the interface blinks "Running Then" in red, then goes back to "idle" and the status changes to and stays "True" indefinitely. It will only revert to False if I explicitly set it to "run else" after the "wait". (and yes, i was using an old gui before ... that's all better now, thanks!) cheers! ~shawn

From this thread at SH: http://www.techmall.com/topic.asp?TOPIC_ID=2230&whichpage=1 Trevor indicates that the new KPL firmware now allows: I'm mainly interested in #1 -- Was this issue limited to the KPL in such a way that it's business-as-usual for the ISY and now that the KPL firmware is fixed, the sub-buttons will control the local load appropriately too? This doesn't mean that each button can be directly controlled, right? In order to change LED status, we still need to add it to a scene by itself, then control that scene? Just wondering what the new KPL firmware means in the ISY realm. Thanks!

doh! Indeed, old GUI. You'd THINK I'd learn Off Topic, but the UD close page doesn't work with firefox like it does w/ IE. No big deal, I just close it manually. It might be nice to just add some text to that page that says something like "UDI Session Ended. You can close this window." Cheers!

I'd like to have a flag program that resets itself after X time. I tried making a test program with just a "Wait 15 seconds" in the "Then" but after I "Run" the program, it doesn't change to "False" after the 15 seconds. I just added the Run Else line and it works as expected: Program "test wait" If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 15 seconds Run program 'test wait' (Else Path) Else - No Actions - (To add one, press 'Action') Any problems with having a program stop itself like this?

ALL of my programs show "true", even those that shouldn't, for example: Folder Conditions for 'Security' Add conditions to limit when programs in this folder are allowed to run. If From Sunset To Sunrise (next day) Then Allow the programs in this folder to run. It's not yet sunset and this says "True"

Ahh, yes. Sometimes it's hard to see the forest for all of the trees! I'll give this a shot tonight. Thanks! ~shawn

I have the "away" KPL button working pretty well: I'm leaving for the evening so I press the KPL "away" button. An "all off" command is sent, and the button lights up. At sunset, and because the status of the away button is ON, an "away at sunset" scene comes on. Later when I arrive home, I trip the X10 motion in the driveway which turns on my "welcome home" scene. Then I ran into the scenario of "leaving" after sunset. Pressing the away button sent an "all off" command AFTER the "away at sunset" scene would have normally come on. So I added a program to fix that. NOW, the problem is that suppose it's after sunset: I press the Away button ... everything is good, except that I can't get OUT of the driveway without tripping the motion sensor! I think's ive come home and turns on the lights! SO I need a way to "disable" a program for, say 15 minutes. So that the "return home" programs don't run when I trip the motion on my way out. I thought I'd put them in a folder and have a program set the folder "false" for a WAIT period, then set it true again, but I don't see how to set a FOLDER true/false. Any ideas on how to accomplish this? Thanks!