funkadelic Posted January 3, 2013 Posted January 3, 2013 I know that you can control the on & ramp levels of devices in a scene, eg. Using a Program to adjust On level/Ramp Rates for a Scene but is there a way to program the ISY994 to schedule the ON level of a SwitchLinc 2476D Dimmer switch itself and not a scene? I also tried creating a scene with only that switch & setting a schedule to adjust the ON level but it didn't appear to work (can a controller also be a responder in a scene?) For example, I'd like to make the ON level of my bathroom light set to 30% when it's 11pm-6am, and 100% otherwise. thanks
Vyrolan Posted January 3, 2013 Posted January 3, 2013 I know that you can control the on & ramp levels of devices in a scene, eg. Using a Program to adjust On level/Ramp Rates for a Scene but is there a way to program the ISY994 to schedule the ON level of a SwitchLinc 2476D Dimmer switch itself and not a scene? Yes, in the "Adjust Scene", pick the actual switch itself for the "In Scene" box and then pick the switch again in the second box...that will change actual locally-applied on level for the switch. If your switch only controls its own local load and not a scene, that is the best way to adjust the on level. an a controller also be a responder in a scene? Controllers that are also responders (like Switchlincs) are automatically a responder of a scene of which they are a controller.
funkadelic Posted January 4, 2013 Author Posted January 4, 2013 Thanks, i set up the scene as you suggested, but when I turn on the light locally at the switch (2476D SwitchLinc Dimmer v.27), the lights still turn on to 100%, BUT the ISY shows the state at 30%. Is there something that I might have missed? If From 11:00:00PM To 6:00:00AM (next day) Then In Scene 'Kitchen Overhead Lights' Set 'Kitchen Overhead Lights' 30% (On Level) Else In Scene 'Kitchen Overhead Lights' Set 'Kitchen Overhead Lights' 100% (On Level)
oberkc Posted January 4, 2013 Posted January 4, 2013 I continue to have memories of some of my older switches that require a power cycle before accepting such settings. Unfortunately, I find myself more frequently remembering things that did not happen. I have not memorized version numbers, but how old is your v27? Hopefully, someone can confirm whether this is a concern or not.
LeeG Posted January 4, 2013 Posted January 4, 2013 funkadelic oberkc is right on about some older devices having to be power cycled before the change to Local On Level takes affect. There are some other possiblilites as well. Right click the SwitchLinc Dimmer node in the My Lighting tree, select Diagnostics | Query Insteon Engine. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Change the Program to some other value than 30% as the ISY will not write a value it thinks has already been set. Use 25% or 35%. Right click on Program name and select Run Then. Post the event trace. The technique for physically updating the Local On Level has changed over time. I suspect the v.27 firmware does not handle the new technique. The event trace will show the commands being used to set the 25%/35%. That should tell us if the SwitchLinc has to be power cycled to pick up the Local On Level change. You can also pull the air gap switch for at least 30 seconds and push it back in. Be careful not to push the air gap switch past the level of the frame to avoid an unwanted reset.
Vyrolan Posted January 4, 2013 Posted January 4, 2013 If he does have an old device that requires a power cycle to change the level, then he won't be able to change it twice a day with his program. He'd have to replace the switch with a newer one that better handles the adjustments on the fly.
funkadelic Posted January 4, 2013 Author Posted January 4, 2013 the SwitchLinc v.27 in question is v3.1. Not sure exactly how old it is, but it's been several years (probably 4+). Here's a log of me setting the on level to 40% and ramp to 4.5secs Fri 01/04/2013 03:42:15 PM : [iNST-TX-I1 ] 02 62 06 D4 47 0F 11 66 Fri 01/04/2013 03:42:15 PM : [iNST-ACK ] 02 62 06.D4.47 0F 11 66 06 LTONRR (66) Fri 01/04/2013 03:42:15 PM : [iNST-SRX ] 02 50 06.D4.47 1F.21.C2 2B 11 66 LTONRR (66) Fri 01/04/2013 03:42:15 PM : [standard-Direct Ack][06.D4.47-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 01/04/2013 03:42:15 PM : [ 6 D4 47 1] ST 102 Fri 01/04/2013 03:42:15 PM : [ 6 D4 47 1] OL 102 Fri 01/04/2013 03:42:15 PM : [All ] Writing 1 bytes to devices Fri 01/04/2013 03:42:15 PM : [6 D4 47 1 ] Memory : Write dbAddr=0x0032 [66] cmd1=0x2E cmd2=0x00 Fri 01/04/2013 03:42:15 PM : [iNST-TX-I1 ] 02 62 06 D4 47 0F 28 00 Fri 01/04/2013 03:42:15 PM : [iNST-ACK ] 02 62 06.D4.47 0F 28 00 06 SET-MSB(00) Fri 01/04/2013 03:42:16 PM : [iNST-SRX ] 02 50 06.D4.47 1F.21.C2 2B 28 00 SET-MSB(00) Fri 01/04/2013 03:42:16 PM : [standard-Direct Ack][06.D4.47-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 01/04/2013 03:42:16 PM : [iNST-TX-I1 ] 02 62 06 D4 47 0F 2B 32 Fri 01/04/2013 03:42:16 PM : [iNST-ACK ] 02 62 06.D4.47 0F 2B 32 06 PEEK (32) Fri 01/04/2013 03:42:16 PM : [iNST-SRX ] 02 50 06.D4.47 1F.21.C2 2B 2B 7F PEEK (7F) Fri 01/04/2013 03:42:16 PM : [standard-Direct Ack][06.D4.47-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 01/04/2013 03:42:16 PM : [iNST-TX-I1 ] 02 62 06 D4 47 0F 29 66 Fri 01/04/2013 03:42:16 PM : [iNST-ACK ] 02 62 06.D4.47 0F 29 66 06 POKE (66) Fri 01/04/2013 03:42:17 PM : [iNST-SRX ] 02 50 06.D4.47 1F.21.C2 2B 29 66 POKE (66) Fri 01/04/2013 03:42:17 PM : [standard-Direct Ack][06.D4.47-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 01/04/2013 03:42:24 PM : [ 6 D4 47 1] RR 26 Fri 01/04/2013 03:42:24 PM : [All ] Writing 1 bytes to devices Fri 01/04/2013 03:42:24 PM : [6 D4 47 1 ] Memory : Write dbAddr=0x0021 [1A] cmd1=0x2E cmd2=0x00 Fri 01/04/2013 03:42:24 PM : [iNST-TX-I1 ] 02 62 06 D4 47 0F 28 00 Fri 01/04/2013 03:42:24 PM : [iNST-ACK ] 02 62 06.D4.47 0F 28 00 06 SET-MSB(00) Fri 01/04/2013 03:42:25 PM : [iNST-SRX ] 02 50 06.D4.47 1F.21.C2 2B 28 00 SET-MSB(00) Fri 01/04/2013 03:42:25 PM : [standard-Direct Ack][06.D4.47-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 01/04/2013 03:42:25 PM : [iNST-TX-I1 ] 02 62 06 D4 47 0F 2B 21 Fri 01/04/2013 03:42:25 PM : [iNST-ACK ] 02 62 06.D4.47 0F 2B 21 06 PEEK (21) Fri 01/04/2013 03:42:25 PM : [iNST-SRX ] 02 50 06.D4.47 1F.21.C2 2B 2B 1B PEEK (1B) Fri 01/04/2013 03:42:25 PM : [standard-Direct Ack][06.D4.47-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 01/04/2013 03:42:25 PM : [iNST-TX-I1 ] 02 62 06 D4 47 0F 29 1A Fri 01/04/2013 03:42:25 PM : [iNST-ACK ] 02 62 06.D4.47 0F 29 1A 06 POKE (1A) Fri 01/04/2013 03:42:26 PM : [iNST-SRX ] 02 50 06.D4.47 1F.21.C2 2B 29 1A POKE (1A) Fri 01/04/2013 03:42:26 PM : [standard-Direct Ack][06.D4.47-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 and then me turning on the lights at the switch Fri 01/04/2013 03:45:27 PM : [iNST-SRX ] 02 50 06.D4.47 00.00.01 CB 11 00 LTONRR (00) Fri 01/04/2013 03:45:27 PM : [standard-Group][06.D4.47-->Group=1] Max Hops=3, Hops Left=2 Fri 01/04/2013 03:45:27 PM : [ 6 D4 47 1] DON 0 Fri 01/04/2013 03:45:27 PM : [ 6 D4 47 1] ST 102 Fri 01/04/2013 03:45:28 PM : [iNST-SRX ] 02 50 06.D4.47 1F.21.C2 41 11 01 LTONRR (01) Fri 01/04/2013 03:45:28 PM : [standard-Cleanup][06.D4.47-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 Fri 01/04/2013 03:45:28 PM : [iNST-SRX ] 02 50 06.D4.47 1F.21.C2 41 11 01 LTONRR (01): Process Message: Ignored Fri 01/04/2013 03:45:28 PM : [standard-Cleanup][06.D4.47-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 When I got to the switch and turn it on, it goes on immediately to 100% without the configured 4.5sec ramp rate -- and the ISY "current state" indicates that it's @ 40% but it's really 100%. Here's a screenshot: I just checked with another 2476D that is v4.5 (though ISY says v.38 in it's interface) and the settings I apply in ISY work, so is it just that the v3.1 switch is incapable of setting its local settings via the ISY?
Brian H Posted January 5, 2013 Posted January 5, 2013 The hardware version number found on the white sticker will not match the firmware revision your ISY Controller shows. Like my old 2456S3 ApplianceLincs hardware revision 1.3 modules. Have a v.28 firmware revision reported by My Lighting.
LeeG Posted January 5, 2013 Posted January 5, 2013 Thanks for the trace data. Exactly what was needed. That old SwitchLinc will not react to the programmatic change in Local On Level and Local Ramp Rate without a power cycle. Makes that particular SwitchLinc not capable of doing what you want.
funkadelic Posted January 5, 2013 Author Posted January 5, 2013 Thanks for the trace data. Exactly what was needed. That old SwitchLinc will not react to the programmatic change in Local On Level and Local Ramp Rate without a power cycle. Makes that particular SwitchLinc not capable of doing what you want. thanks for the confirmation. Guess I'll swap the old Switchlinc with the newer one. Was there a particular line in the debug log that helped you determine this? I'm fairly new to using the ISY994 but would like to understand what to look for next time.
LeeG Posted January 5, 2013 Posted January 5, 2013 The commands used to set the Local On Level and Local Ramp Rate are Peek/Poke which are used to read and write device memory. These commands directly set memory such that the device is not aware of the changes. A power cycle establishes the new values. For devices with the newest firmware that supports the I2CS Insteon protocol (the latest in Insteon evolution) the Peek/Poke commands have been eliminated altogether. The newer devices use Extended configuration commands to set values like Local On Level and Local Ramp Rate. These commands instruct the device to change the respective values without the application (ISY) knowing anything about where the data is actually being stored. Now the device is directly aware the values are being changed, adjusting the values currently being used. There are always exceptions in Insteon. The above information is accurate but does not always apply to data changed with Peek/Poke. Link record data is often written with Peek/Poke (until I2CS came along) and have immediate effect because link records are accessed each time they are used.
Recommended Posts