Envirogreen

IndyMike, Thank you for your suggestions: Question 1- queried and down to 6 responding Question 2 - 2413S Question 3 - basement near the service panel Suggestions: 1) I get a Request Failed error and nothing is written to the event log file...when I query Insteon engine nothing happens. 2) Queried Insteon Engine - first two were showing the exclamation mark, third had previously worked when I did the query, but as you can see failed on this try and now shows an exclamation mark log file - can't add as file so copy and paste below Sun 03/24/2013 01:54:27 PM : [All ] Writing 0 bytes to devices Sun 03/24/2013 01:54:33 PM : [All ] Writing 0 bytes to devices Sun 03/24/2013 01:54:37 PM : [All ] Writing 1 bytes to devices Sun 03/24/2013 01:54:37 PM : [iNST-TX-I1 ] 02 62 1D 28 A8 0F 0D 00 Sun 03/24/2013 01:54:37 PM : [iNST-ACK ] 02 62 1D.28.A8 0F 0D 00 06 (00) Sun 03/24/2013 01:54:46 PM : [iNST-TX-I1 ] 02 62 1D 28 A8 0F 0D 00 Sun 03/24/2013 01:54:46 PM : [iNST-ACK ] 02 62 1D.28.A8 0F 0D 00 06 (00) Sun 03/24/2013 01:54:55 PM : [iNST-TX-I1 ] 02 62 1D 28 A8 0F 0D 00 Sun 03/24/2013 01:54:55 PM : [iNST-ACK ] 02 62 1D.28.A8 0F 0D 00 06 (00) Sun 03/24/2013 01:54:59 PM : [ 1D 28 A8 1] ERR 1

All, Thank you for your comments. I did delete one devisce and tried to add it back and was not able to - I got a Cannot determine Insteon Engine Error (message attached) Regarding your suggestion to run queries to hopefully give you some indication of whats going on: Queried 3 lights that showed as working Queried 2 that showed as not working. Can't seem to add the log file. so copying and pasting instead of attaching: --- Sun 03/24/2013 01:35:28 PM : [iNST-TX-I1 ] 02 62 1D 2E 0D 0F 19 00 Sun 03/24/2013 01:35:28 PM : [iNST-ACK ] 02 62 1D.2E.0D 0F 19 00 06 LTSREQ (LIGHT) Sun 03/24/2013 01:35:29 PM : [iNST-ERX ] 02 51 1D 2E 0D 0F 9D 50 1B 01 E8 94 51 00 00 20 20 1D 00 7F 3C C0 00 00 00 Sun 03/24/2013 01:35:29 PM : [Ext-Direct ] 1D.2E.0D-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 03/24/2013 01:35:38 PM : [iNST-TX-I1 ] 02 62 1D 2E 0D 0F 19 00 Sun 03/24/2013 01:35:38 PM : [iNST-ACK ] 02 62 1D.2E.0D 0F 19 00 06 LTSREQ (LIGHT) Sun 03/24/2013 01:35:47 PM : [iNST-TX-I1 ] 02 62 1D 2E 0D 0F 19 00 Sun 03/24/2013 01:35:47 PM : [iNST-ACK ] 02 62 1D.2E.0D 0F 19 00 06 LTSREQ (LIGHT) Sun 03/24/2013 01:35:51 PM : [ 1D 2E D 1] ERR 1 Sun 03/24/2013 01:35:58 PM : [ELK 0 17 0] Zone : 2nd Flr Motion : Violated (51/2/0) Sun 03/24/2013 01:35:58 PM : [ELK 0 17 0] Zone : 2nd Flr Motion : Open (52/1/0) Sun 03/24/2013 01:35:58 PM : [ELK 1 0 0] Area : The Goldstein's : Not Ready To Arm (2/0/0) Sun 03/24/2013 01:36:00 PM : [iNST-TX-I1 ] 02 62 1D 28 A8 0F 19 00 Sun 03/24/2013 01:36:00 PM : [iNST-ACK ] 02 62 1D.28.A8 0F 19 00 06 LTSREQ (LIGHT) Sun 03/24/2013 01:36:01 PM : [iNST-SRX ] 02 50 1D.28.A8 0F.9D.50 23 01 00 (00) Sun 03/24/2013 01:36:01 PM : [std-Direct Ack] 1D.28.A8-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Sun 03/24/2013 01:36:01 PM : [ 1D 28 A8 1] ST 0 Sun 03/24/2013 01:36:01 PM : [ 1D 28 A8 1] OL 229 Sun 03/24/2013 01:36:01 PM : [ 1D 28 A8 1] RR 28 Sun 03/24/2013 01:36:03 PM : [ELK 0 17 0] Zone : 2nd Flr Motion : Normal (51/0/0) Sun 03/24/2013 01:36:03 PM : [ELK 0 17 0] Zone : 2nd Flr Motion : Short (52/3/0) Sun 03/24/2013 01:36:03 PM : [ELK 1 0 0] Area : The Goldstein's : Ready To Arm (2/1/0) Sun 03/24/2013 01:36:42 PM : [iNST-TX-I1 ] 02 62 21 08 D8 0F 19 00 Sun 03/24/2013 01:36:42 PM : [iNST-ACK ] 02 62 21.08.D8 0F 19 00 06 LTSREQ (LIGHT) Sun 03/24/2013 01:36:43 PM : [iNST-SRX ] 02 50 21.08.D8 0F.9D.50 23 15 00 LTBRITE(00) Sun 03/24/2013 01:36:43 PM : [std-Direct Ack] 21.08.D8-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Sun 03/24/2013 01:36:43 PM : [ 21 8 D8 1] ST 0 Sun 03/24/2013 01:36:43 PM : [ 21 8 D8 1] OL 255 Sun 03/24/2013 01:36:43 PM : [ 21 8 D8 1] RR 28 Sun 03/24/2013 01:37:09 PM : [iNST-TX-I1 ] 02 62 1D D5 68 0F 19 00 Sun 03/24/2013 01:37:09 PM : [iNST-ACK ] 02 62 1D.D5.68 0F 19 00 06 LTSREQ (LIGHT) Sun 03/24/2013 01:37:18 PM : [iNST-TX-I1 ] 02 62 1D D5 68 0F 19 00 Sun 03/24/2013 01:37:18 PM : [iNST-ACK ] 02 62 1D.D5.68 0F 19 00 06 LTSREQ (LIGHT) Sun 03/24/2013 01:37:25 PM : [ELK 0 17 0] Zone : 2nd Flr Motion : Violated (51/2/0) Sun 03/24/2013 01:37:25 PM : [ELK 0 17 0] Zone : 2nd Flr Motion : Open (52/1/0) Sun 03/24/2013 01:37:25 PM : [ELK 1 0 0] Area : The Goldstein's : Not Ready To Arm (2/0/0) Sun 03/24/2013 01:37:27 PM : [iNST-TX-I1 ] 02 62 1D D5 68 0F 19 00 Sun 03/24/2013 01:37:27 PM : [iNST-ACK ] 02 62 1D.D5.68 0F 19 00 06 LTSREQ (LIGHT) Sun 03/24/2013 01:37:30 PM : [ELK 0 17 0] Zone : 2nd Flr Motion : Normal (51/0/0) Sun 03/24/2013 01:37:30 PM : [ELK 0 17 0] Zone : 2nd Flr Motion : Short (52/3/0) Sun 03/24/2013 01:37:30 PM : [ELK 1 0 0] Area : The Goldstein's : Ready To Arm (2/1/0) Sun 03/24/2013 01:38:08 PM : [iNST-TX-I1 ] 02 62 1D DD EE 0F 19 00 Sun 03/24/2013 01:38:08 PM : [iNST-ACK ] 02 62 1D.DD.EE 0F 19 00 06 LTSREQ (LIGHT) Sun 03/24/2013 01:38:17 PM : [iNST-TX-I1 ] 02 62 1D DD EE 0F 19 00 Sun 03/24/2013 01:38:17 PM : [iNST-ACK ] 02 62 1D.DD.EE 0F 19 00 06 LTSREQ (LIGHT) Sun 03/24/2013 01:38:23 PM : [ELK 0 17 0] Zone : 2nd Flr Motion : Violated (51/2/0) Sun 03/24/2013 01:38:23 PM : [ELK 0 17 0] Zone : 2nd Flr Motion : Open (52/1/0) Sun 03/24/2013 01:38:24 PM : [ELK 1 0 0] Area : The Goldstein's : Not Ready To Arm (2/0/0) Sun 03/24/2013 01:38:26 PM : [iNST-TX-I1 ] 02 62 1D DD EE 0F 19 00 Sun 03/24/2013 01:38:26 PM : [iNST-ACK ] 02 62 1D.DD.EE 0F 19 00 06 LTSREQ (LIGHT) Sun 03/24/2013 01:38:28 PM : [ELK 0 17 0] Zone : 2nd Flr Motion : Normal (51/0/0) Sun 03/24/2013 01:38:28 PM : [ELK 0 17 0] Zone : 2nd Flr Motion : Short (52/3/0) Sun 03/24/2013 01:38:29 PM : [ELK 1 0 0] Area : The Goldstein's : Ready To Arm (2/1/0) ---- By the way: - No access points in the system as I have over 40 devices (vast majority dual band - I think there are 2-3 non-dual band). All in RF range. Never an issue prior to last night (I hadn't accessed the console in the past week but rules were working). Nothing has changed in the system for about 2 weeks - no new surge protectors, new tech toys, plm still directly plugged into the wall, etc).

swapped ISY and same issue - so its not the ISY (at least my working assumption) I'm going to put the 994 back in and then delete one or two of the switches and see if that resolves the issue. Will be LOTs of work, but the only way I can see forward at this time.

did restore PLM - no change. did scene test but not sure what the information tells me....lots of failures but not sure what to do with this informaiton. I have my old isy 99pro...so I'm going to switch that in and see what that does...should tell me if its the ISY or something else.

Nothing has been added or changed I'll try the scene test Can I reset the palm and what are the implications Thank you

Major issue. My ISY stopped recognizing most of my insteon devices. I have tried restoring from a back up - but that didn't make any difference. I have only had the 994 for a few weeks (upgraded from the isy 99) and it had been working perfectly prior to last night when I went in to make a change. Attached a screen shot to give an example of the non-communication going on. Suggestions?

The key reason I purchased the Weatherbug module was for the light information, but the two stations that are anywhere close to me (Location ID- CYYZ and CYTZ) do not have the light information. Online I also found a backyard Network, but can't find that one in the ISY. Any suggestions on what I can do? By the way if it helps I am located in Toronto, ON, Canada (M4G 1M5)

That did the trick. Thank you

One of those answers that is so obvious...when someone tells you Thank you I'll try that tomorrow morning

I have a kpl button controlling a lamp which I only want to go on at 70% I have the kpl button as a controller in a scene and the lamp module as responder I've set the lamp module at 70% but the kpl button can only be set on The result is that when I press the button the lamp goes on at 100% instead of the desired 70% Any suggestions?

updated to 3.3.10 and issue resolved

v 3.3.9 unsupported device 2.44 I'll try updating to 3.3.10 and see if that helps

I had two 2487s keypads, one of which I had to replace and during the reinstall I went into the drop down and no longer could find 2487s, used auto discover and its showing up as unsupported. I also found that my other 2487s is showing as not supported. I'm sure I'm doing something wrong - is there something I need to do to get this to work properly?

Got it - that's good to know. So the load are several extension cords stringing several strings of fairly old christmas lights together. Is that the type of thing that creates noise? Any suggestions or is this just not a good use for insteon? I can always go back to the light sensing (non-insteon) timers

I ran the Scene test on all 3 sets of lights...2 consistently pass and the third passed only 1 out of 4 times. This one is for outside Holiday lights. Its my only Insteon product outside my home. Product is 2456s3e. I then proceeded with a device restore - about halfway through it gives a failure to communicate error. Should I go to a PLM restore next (what are the implications)?

By the way I thought I should add that everything works perfectly when manually controlling the lights. Oberkc - yes I have several scenes. Not sure what you mean by a scene test?

Oberkc - that was my thought...but not sure how to test this or why this would be happening (I have some 50 dual band devices installed so would seem to be sufficient to have solid communication). arw01 - looking at the Error log it shows nothing around sunset. Looking at the log it shows that the three rules ran and turned the lights on to a value of 255 (today 2 out of the 3 lights went on). I have now set the the Event Log to Level 3 so hopefully I'll have more to report tomorrow.

I have 3 lights that I want to come on at sunset and turn off at different times, for each light I have an ON rule, and then path to an off rule with a Wait. The trouble I am having is that they don't always turn the light on at sunset (although I can see that the rules have run). On some days all lights come on perfectly, and others (like yesterday) only 1 of the 3 come on. Any ideas on what could be going on? Here is an example of one of the rules...i moved to this structure from a simple if, then, else

any progress? For the 4 buttons leveraging the 6 button frame, did you need to do any hardware hacking? It sounds like you didn't make any changes to the frame but I wanted to confirm. I'm very interested in doing this, but don't have the skill to start messing with the frames (I can get extra double buttons and include those for the middle two sections, but that is about the extent of my skills). Would a similar approach work for the 8 button KPL?

Thank you for your responses I'm not at home at the moment, but I didn't see any place to drag and drop the LLP buttons. On the left side it only shows one item under my lighting Re reset - I assume this is a must otherwise I'll have a performance hit. Is that correct?

I have created 3 scenes, and I would like to add each to the A, B and C buttons on 3 different keypads. 1. How do I add a button from a keypad to the scene so that it is a controller? 2. Do I then have to write to the keypad so that it is updated (and would work if the ISY went down) or is this done automatically 3. Can I add the A button's from each of the 3 keypads to the same scene? Would one be the controller and the others be responders? Would the LED on the buttons stay in sink? 4. If one of the lights in the scenes is turned on will the button also turn on? 5. Can I make a Scene of a scene (it doesn't look like it), so that D can be an aggregation of A, B and C? Last item - I have manually programmed these buttons (but that quickly becomes very difficult to manage - is there a way to remove all the links on the buttons that have been manually linked (I went to the button group and saw a reset button and it came with a big warning about not using it...so I want to ask before doing anything) Thank you for your help with this.

so I unlinked the switch, factory reset, re-linked everything ... and still the exact same issue. At this point since the problem really only occurs during testing use case vs real life use case I'm going to give up on this issue. Its strange behaviour but one I can live with for now. Lee - Thank you for your help.

duplicate

Lee, That is definitely interesting. I changed the rule as you suggested and with light off being automated (no paddle press) door opened (6 times), light when on (and then off) as expected/desired. So that's really good news. The paddle seems to work, when used normally (without the light being programatically turned on). I have also found that by turning the lights off with the paddle, the door open will not turn on the lights (so open door, lights go on, paddle off, open door, lights don't go on, paddle off, open door, lights still won't go on, however, if I don't paddle off the lights will go on when the door is next opened). I hope this makes sense. While there is a resolution when paddle off is not used, I expect that people will at times paddle off and don't want to create problems. Thank you again.

forgot to mentioned ramp rate is 0.5 secs