wswartz

Thanks all for the replies and details on how motion sensors work. I'll try the sensing mode feature and see if that gets it for me. Will also look at adding the suggested programs. Thanks! BIll

In one instance, I have a single Switchlinc Relay that is coming on by itself. In addition, I have another set of dimmers which are doing something similar. For the switch, I've noticed it coming on in the morning at sunrise, apparently by itself. When it does this, the ISY does not recognize that the switch is on (ISY interface says it's OFF). Also, I set a notification to send me an email when it does come on. As you can imagine, since the ISY doesn't know it's on (when it is), I get no notification. I looked at the log and there is no indication that the light ever came on. Finally, I ran an event view and was able to capture the following: Mon 01/07/2013 08:11:56 AM : [iNST-TX-I1 ] 02 62 19 ED 3F 0F 2E 00 Mon 01/07/2013 08:11:56 AM : [iNST-ACK ] 02 62 19.ED.3F 0F 2E 00 06 (00) Mon 01/07/2013 08:11:56 AM : [iNST-SRX ] 02 50 19.ED.3F 19.74.C6 2B 2E 00 (00) Mon 01/07/2013 08:11:56 AM : [std-Direct Ack] 19.ED.3F-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 19.ED.3F is the address for the switch. 19.74.C6 is the address of my PLM. I don't know what the rest of this means, but I'd have to guess that means, turn on the switch! In another instance, I have a scene that seems to be invoking itself sometime after midnight. This is a set of dimmers and they are all coming on at just 6%. A rather odd level to be set at; I don't have any programs that set dimmers to such low level. These switches, and any associated programs, have been running flawlessly in my environment for the previous year. I've made no additions or changes to the programs relating to this area of the house. If I had to correlate this to some event, I did re-introduce a Keypadlinc into my system that had been previously removed. I surmised that it may be some rogue link in the KPL that set this off, but I've dismissed that because: 1. Hitting buttons on the re-installed KPL doesn't seem to affect the troubled switch. 2. The switch in question only seems to come on at sunrise. 3. It seems to be a programmatic event sent from the PLM (and thus, the ISY). My question is: how can I further diagnose this issue? I've gone through my programs associated with this area of the house and can't seem to find anything that would cause this. Also what's odd, in the case of my single switch, this is happening to only one switch when all the programs I have made for this area are based on invoking a scene. Any ideas are welcome! Bill

With further testing, I have a follow-up question. Say it's night and you trip the MS; the light goes to 50%. You want the light to be brighter so you hit the switch to take it to 100%. The moment the MS senses movement, it goes back to 50%. Any way to prevent this from happening? Bill

LeeG: THANKS! That worked just as I was looking for. Here is the code I used if anyone else is interested: If From 12:30:00AM To Sunrise - 45 minutes (same day) Then In Scene 'House / Main Floor / Master Bedroom / Master.MS.Closet-Sensor' Set 'House / Main Floor / Master Bedroom / Master.SD.Closet' 50% (On Level) In Scene 'House / Main Floor / Master Bedroom / Master.MS.Closet-Sensor' Set 'House / Main Floor / Master Bedroom / Master.SD.Closet' 4.5 Sec (Ramp Rate) Else In Scene 'House / Main Floor / Master Bedroom / Master.MS.Closet-Sensor' Set 'House / Main Floor / Master Bedroom / Master.SD.Closet' 100% (On Level) In Scene 'House / Main Floor / Master Bedroom / Master.MS.Closet-Sensor' Set 'House / Main Floor / Master Bedroom / Master.SD.Closet' 0.1 Sec (Ramp Rate)

Wow, good questions... If KPL1 button D is off and Scene2 turns on, I don't need button D to come on as well. Does it matter? Probably not. If kpl1 is on and you invoke scene2, do you want kpl1 to stay on? Does it matter? I think I would want both. When I wrote the question, I was thinking that, if Scene1 was on then Scene2 turned on, then Scene2 was turned off, that it would also turn off Scene1 (both SW1 and KPL1/D). However, your question got me thinking about another area in the house where I would like Scene1 to stay on. Thanks!

Recently purchased the climate module and trying to understand how to use temp in a program. Got this simple one to turn on a pond heater when the temp falls below freezing: If Module 'Climate' Temperature <= 32 °F Then Set Scene 'House / Garage / Scene.WaterFeature' On Else Set Scene 'House / Garage / Scene.WaterFeature' Off I see the temp in the climate module is less then 32deg, but nothing seems to happen. I guessed this was because there was no "event" that was testing the temp, so I added a schedule line that looks like this: If From 12:00:00AM To 11:59:59PM (same day) And Module 'Climate' Temperature <= 32 °F ... That seemed to make it work. So what's the problem? Just curious if there was a better way of doing this and if my assumptions were correct. Trying to understand this better Bill

Here's a diagram of what I have set up: My issue is, if I turn on Scene1 from KPL1, of course, button D lights up. If I then turn on Scene2 from KPL2, then turn it off again from KPL2, button D on KPL1 is still lit up on KPL1. I also have a similar situation where I invoke Scene2 as a Fast On from SW2 or SW3 and turn it off again with a Fast Off. If Scene1 is already on, button D will still be lit when SW2/SW3 turns it off. What's the best way to fix this and keep the button lights in sync. Do I need a program to monitor these and adjust the lights accordingly? Thanks, Bill

Hello, I have a motion sensor that is in a scene with a dimmer. During the day, I'd like the light to come on at 100%. At night, I'd like it to come on at 50%. I have a program that changes the scenes (if day, 100%, else, 50%). but when the MS is triggered, day or night, it comes on at 100%. I assume this is happening because the MS is sending an ON signal which is interpreted as, "come on at 100%." I know I could do this in a program (if day and motion, 100%, else, 50%). Is there any way to do this using scenes rather than a program? With a scene, the light comes on with motion and is near instantaneous, but there's a slight delay when using a program. Thanks, Bill

Sorry, need open this back up; still not working the way I want. So the program "DiningEvening" sets the local on level and ramp rate properly. However, when "Dining.SceneChange executes it's "Then", the On command takes the light to 100%. Using the local switch, or the "On" command from the ISY interface for this light works properly. Is there a difference between "On" from the ISY interface or local switch, and "On" from a program? Is there something I can send from a program that will do what I want? BS

Thanks, this works. I wasn't aware a program could call another program that was disabled. I can think of a bunch of other uses for this. Appreciate the tip. BS

Wondering if someone can help me out with this set of programs? Goal: At night, do a scene change on a light. If the light is already on, have it follow the change. This is what I came up with so far: DiningEvening: If From 12:00:00AM To Sunrise (same day) Then In Scene 'House / Main Floor / Dining / Dining.SD.Light' Set 'House / Main Floor / Dining / Dining.SD.Light' 20% (On Level) In Scene 'House / Main Floor / Dining / Dining.SD.Light' Set 'House / Main Floor / Dining / Dining.SD.Light' 6.5 Sec (Ramp Rate) Run Program 'Dining.ChangeScene' (If) Else - No Actions - (To add one, press 'Action') Dining.ChangeScene: If Status 'House / Main Floor / Dining / Dining.SD.Light' is not Off Then Set 'House / Main Floor / Dining / Dining.SD.Light' On Else - No Actions - (To add one, press 'Action') So this actually works; at midnight, the system adjusts the scene, runs "Dining.ChangeScene", and the lights follow the scene change. However, it has a nasty side effect. If you try to change the level at the switch, "Dining.ChangeScene" kicks in and puts the light right back to the scene On level (20%). Anyone think of a way to do this that would allow for the local switch to readjust the level at will? Thanks, Bill

FYI to the forum. I was having issues with my SwichLinc Relay devices as well. You could turn them on and off from ISY, but if turned on/off locally, ISY would not register these changes. For example, ISY would always show a switch off when it was really on. I deleted it from ISY and reinstalled it (like my dimmers), and this is now working.

The query didn't help, but deleting it and adding it back in did. Seems to be working now. Happy there's a resolution yet bummed as I installed a bunch of switches over the weekend and already applied programming to them so it looks like I might have to start over. Nonetheless, LeeG, thanks for your help in looking into this! Bill

Verified that both Firmware and UI show v3.2.4. Below are the results of the diagnostics. The on level was set to 34% and the ramp rate to 21.5 sec. A progress bar appeared briefly after each setting. Once the on level was set, the light dimmed (presumably to 34%). I then turned the switch off, then back on. The switch went to 100% immediately. Bill Tue 04/10/2012 08:13:34 PM : [iNST-TX-I1 ] 02 62 1B C0 C4 0F 11 56 Tue 04/10/2012 08:13:34 PM : [iNST-ACK ] 02 62 1B.C0.C4 0F 11 56 06 LTONRR (56) Tue 04/10/2012 08:13:35 PM : [iNST-SRX ] 02 50 1B.C0.C4 19.74.C6 2B 11 56 LTONRR (56) Tue 04/10/2012 08:13:35 PM : [standard-Direct Ack][1B.C0.C4-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Tue 04/10/2012 08:13:35 PM : [ 1B C0 C4 1] ST 86 Tue 04/10/2012 08:13:35 PM : [ 1B C0 C4 1] OL 86 Tue 04/10/2012 08:13:35 PM : [All ] Writing 1 bytes to devices Tue 04/10/2012 08:13:35 PM : [1B C0 C4 1 ] Memory : Write dbAddr=0x0032 [56] cmd1=0x2E cmd2=0x00 Tue 04/10/2012 08:13:35 PM : [iNST-TX-I1 ] 02 62 1B C0 C4 0F 28 00 Tue 04/10/2012 08:13:35 PM : [iNST-ACK ] 02 62 1B.C0.C4 0F 28 00 06 SET-MSB(00) Tue 04/10/2012 08:13:35 PM : [iNST-SRX ] 02 50 1B.C0.C4 19.74.C6 2B 28 00 SET-MSB(00) Tue 04/10/2012 08:13:35 PM : [standard-Direct Ack][1B.C0.C4-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Tue 04/10/2012 08:13:35 PM : [iNST-TX-I1 ] 02 62 1B C0 C4 0F 2B 32 Tue 04/10/2012 08:13:36 PM : [iNST-ACK ] 02 62 1B.C0.C4 0F 2B 32 06 PEEK (32) Tue 04/10/2012 08:13:36 PM : [iNST-SRX ] 02 50 1B.C0.C4 19.74.C6 27 2B BF PEEK (BF) Tue 04/10/2012 08:13:36 PM : [standard-Direct Ack][1B.C0.C4-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Tue 04/10/2012 08:13:36 PM : [iNST-TX-I1 ] 02 62 1B C0 C4 0F 29 56 Tue 04/10/2012 08:13:36 PM : [iNST-ACK ] 02 62 1B.C0.C4 0F 29 56 06 POKE (56) Tue 04/10/2012 08:13:36 PM : [iNST-SRX ] 02 50 1B.C0.C4 19.74.C6 2B 29 56 POKE (56) Tue 04/10/2012 08:13:36 PM : [standard-Direct Ack][1B.C0.C4-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Tue 04/10/2012 08:13:41 PM : [ 1B C0 C4 1] RR 22 Tue 04/10/2012 08:13:41 PM : [All ] Writing 1 bytes to devices Tue 04/10/2012 08:13:41 PM : [1B C0 C4 1 ] Memory : Write dbAddr=0x0021 [16] cmd1=0x2E cmd2=0x00 Tue 04/10/2012 08:13:41 PM : [iNST-TX-I1 ] 02 62 1B C0 C4 0F 28 00 Tue 04/10/2012 08:13:41 PM : [iNST-ACK ] 02 62 1B.C0.C4 0F 28 00 06 SET-MSB(00) Tue 04/10/2012 08:13:41 PM : [iNST-SRX ] 02 50 1B.C0.C4 19.74.C6 2B 28 00 SET-MSB(00) Tue 04/10/2012 08:13:41 PM : [standard-Direct Ack][1B.C0.C4-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Tue 04/10/2012 08:13:41 PM : [iNST-TX-I1 ] 02 62 1B C0 C4 0F 2B 21 Tue 04/10/2012 08:13:41 PM : [iNST-ACK ] 02 62 1B.C0.C4 0F 2B 21 06 PEEK (21) Tue 04/10/2012 08:13:41 PM : [iNST-SRX ] 02 50 1B.C0.C4 19.74.C6 2B 2B 1A PEEK (1A) Tue 04/10/2012 08:13:41 PM : [standard-Direct Ack][1B.C0.C4-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Tue 04/10/2012 08:13:41 PM : [iNST-TX-I1 ] 02 62 1B C0 C4 0F 29 16 Tue 04/10/2012 08:13:41 PM : [iNST-ACK ] 02 62 1B.C0.C4 0F 29 16 06 POKE (16) Tue 04/10/2012 08:13:42 PM : [iNST-SRX ] 02 50 1B.C0.C4 19.74.C6 2B 29 16 POKE (16) Tue 04/10/2012 08:13:42 PM : [standard-Direct Ack][1B.C0.C4-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Tue 04/10/2012 08:13:46 PM : [iNST-SRX ] 02 50 1B.C0.C4 00.00.01 CB 13 00 LTOFFRR(00) Tue 04/10/2012 08:13:46 PM : [standard-Group][1B.C0.C4-->Group=1] Max Hops=3, Hops Left=2 Tue 04/10/2012 08:13:46 PM : [ 1B C0 C4 1] DOF 0 Tue 04/10/2012 08:13:46 PM : [ 1B C0 C4 1] ST 0 Tue 04/10/2012 08:13:46 PM : [iNST-SRX ] 02 50 1B.C0.C4 19.74.C6 41 13 01 LTOFFRR(01) Tue 04/10/2012 08:13:46 PM : [standard-Cleanup][1B.C0.C4-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 Tue 04/10/2012 08:13:46 PM : [iNST-SRX ] 02 50 1B.C0.C4 19.74.C6 41 13 01 LTOFFRR(01): Process Message: Ignored Tue 04/10/2012 08:13:46 PM : [standard-Cleanup][1B.C0.C4-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 Tue 04/10/2012 08:13:49 PM : [iNST-SRX ] 02 50 1B.C0.C4 00.00.01 CB 11 00 LTONRR (00) Tue 04/10/2012 08:13:49 PM : [standard-Group][1B.C0.C4-->Group=1] Max Hops=3, Hops Left=2 Tue 04/10/2012 08:13:49 PM : [ 1B C0 C4 1] DON 0 Tue 04/10/2012 08:13:49 PM : [ 1B C0 C4 1] ST 86 Tue 04/10/2012 08:13:49 PM : [iNST-SRX ] 02 50 1B.C0.C4 19.74.C6 41 11 01 LTONRR (01) Tue 04/10/2012 08:13:49 PM : [standard-Cleanup][1B.C0.C4-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 Tue 04/10/2012 08:13:49 PM : [iNST-SRX ] 02 50 1B.C0.C4 19.74.C6 41 11 01 LTONRR (01): Process Message: Ignored Tue 04/10/2012 08:13:49 PM : [standard-Cleanup][1B.C0.C4-->ISY/PLM Group=1] Max Hops=1, Hops Left=0

LeeG, I just upgraded to v3.2.4 and unfortunately, the problem still remains for me. For example, from the device level, I set the on level to 50% and ramp ramp rate to 8.5 seconds. Turning on the switch goes to 100% immediately. I set up a scene with these same settings and made the device a controller for this scene; same results. If I pull the air gap and reset the switch, it accepts the changes and works as expected. I upgraded from v3.1.4 to get my new ApplianceLink module to work, but I use the on level and ramp rate setting feature more. Considering going back to v3.1.4 until this is resolved. Would there be any issue in downgrading to a lower version?

Also, looking for feedback on my program. Is there a better way to accomplish this? Thanks!

Running v3.2.3 Beta. Is this something that will be addressed in a future release? I can wait for that fix rather than running around and resetting my switches. Thanks, Bill

Main issue: Trying to configure the local On Level and Ramp Rate for a SwithcLinc Dimmer in ISY but these seem to have no effect. For example, I set the On Level to 30% and the ramp rate to 2 seconds. When hit, the switch turns on to 100% immediately with no ramp. I added a number of new switches this weekend and tried this on several others and get the same results. Could be pilot error, but I upgraded to v3.2.3 Beta to get an ApplianceLink to work properly so maybe that could be part of it? I discovered this while trying to do the following for a bathroom light: if time is 1am - sunrise and Bathroom light is switched on then set Bathroom light 30% else set Bathroom light on The "if" in this program doesn't work as desired; the light first goes to 100% for just a second; when the program kicks in, it goes back down to 30%. I suppose this is because the switch is using it's local On Level first. So I thought I'd set the On Level to 30% by default for this switch, then let the program move it up to 100% if it's day time (basically reverse the "then" and "else"); that's when I ran into the issue above. If I set the on level manually at the switch the reversed logic seems seems to work; the switch goes to 30%, then after a second the program kicks in and goes to 100%. I might be able to smooth this out with an increased ramp rate time. Looking for an answer on the On Level, Ramp Rate thing, but if there is a better way to accomplish my end goal, please let me know. Thanks, Bill

Thanks for the information. I upgraded to v3.2.3 Beta and I'm now able to control the ApplianceLinc from my KPL. Bill

In the process of upgrading my system; adding some things and moving some around. Here is what I'm planning: 1. Replacing 3 ToggleLinks with SwitchLinks. 2. Moving the 3 TL's to another part of the house that isn't Insteon yet. 3. Replacing a KPL dimmer with a SwitchLink dimmer. 4. Moving the scenes from the KPL above to a new on/off KPL in another location. 5. Moving the KPL removed in #3 to another part of the house with new scenes. What is the best way to accomplish these adds/moves? Simply delete the scenes and start over, or is there an easy way to do this in ISY? Thanks, Bill

Yes, please tell me, what is I2CS mean? I've not heard this term before.

Hello, Just purchased an ApplianceLinc and added it to my ISY system. I can control the ApplianceLinc with no problem as an individual device; that is, I can turn it on and off from the ISY interface with no problem. However, my trouble is when using it from within a scene. For example, I put the ApplianceLinc in a scene along with a KeypadLink button as a controller. Hitting the KL button shows the scene is on, but the ApplianceLinc is actually off. Same thing from the ISY interface; I can turn the scene on, the KL button turns on, but the ApplianceLinc is still off. Again, I can go to the ApplianceLinc instance in ISY and turn it on and off with no problem. Ideas? Thanks, Bill

Confirmed. I'm at v3.1.16. WS

OK, understand now how it works. Need linking mode not only for initialization, but also for updates. BTW, I just upgraded to v3.1.16, deleted all the TL config and reset it to factory defaults. Unlike your 'EDIT2" above, I still didn't get a dialog box asking me to put the TL in linking mode. I then proceeded to run through my steps 1-4 which worked. At step 5, I put the TL back into linking mode and proceeded to add it to the scene which also worked. No need for steps 6-8. Thanks for all the assistance! WS

OK, this is darn weird. I got it working; here's what I did: 1. Manually setup up the TL under Link Management, New INSTEON Device per documentation (didn't hit OK yet). 2. Put the TL in linking mode. 3. Hit OK on the New INSTEON Device screen. 4. Let it discover the device, rename it and add it to the proper folder. The TL was still in linking mode so I turned that off. 5. Added the TL to a scene with a KPL. Got a communications error (red ! next to device). Strangely enough, the link to the KPL worked (didn't notice that before) 6. Right clicked on the TL and selected Diagnostics, Show Device Links Table. 7. At this point I got the dialog box I'd expect to get after my step 3 above, that is, a box telling me to put the TL in linking mode. Put it in linking mode. 8. Green arrows saying, "Writing", appeared next to the TL's. Soon after that, all the errors went away. 9. Everything is working as expected. Just for fun, I deleted the device, factory reset the TL, then ran through these steps once again. Did it the same way a second time. Thanks for all the responses. WS