Dimming during Evening Hours?

[jerlands]

I've just installed Switchlinc 2477D and 2476S. The dimmer is to control bathroom vanity lights and the switch is to control the ceiling fan. I want to dim the lights during evening hours locally (that is when pressing the paddle.) I'm running v.3.1.2 and my program looks like this...

 

If
       From     2:25:00PM
       To      10:25:00PM (same day)

Then
       In Scene 'Master Bathroom' Set 'Master Bathroom Vanity Lights' 20% (On Level)
       In Scene 'Master Bathroom' Set 'Master Bathroom Vanity Lights' 2.0 Sec (Ramp Rate)

Else
       In Scene 'Master Bathroom' Set 'Master Bathroom Vanity Lights' 100% (On Level)
       In Scene 'Master Bathroom' Set 'Master Bathroom Vanity Lights' 0.3 Sec (Ramp Rate)

 

-disregard the time range-

 

I've read where it's necessary to select the "switch" from the drop down menu from the options for "Adjust Scene/In Scene" but my devices aren't listed. I've also read where you can "power cycle" the device (older models) and this might help but I'm uncertain about how to "power cycle" other than to turn off the breaker. anywhoo...

 

Any suggestions appreciated.

 

Thanks,

 

Jon

[TJF1960]

As I recall the device needs to be in a scene as a controller. Once a scene is created with the device as a controller that device will appear in the drop down box. Then you may select the device as you were correctly trying to do.

 

To power cycle a SL you can just pull the set tab out at the bottom of the rocker switch for 10 or so seconds which removes power from the device.

 

Tim

[jerlands]

As I recall the device needs to be in a scene as a controller. Once a scene is created with the device as a controller that device will appear in the drop down box. Then you may select the device as you were correctly trying to do.

 

To power cycle a SL you can just pull the set tab out at the bottom of the rocker switch for 10 or so seconds which removes power from the device.

 

Tim

 

Still not getting it to work. I had both switches in the same scene but making the dimmer a controller caused the fan to run I also tried the power cycle but nothing. I know others have this working but it's just escaping me.

 

Thanks,

 

Jon

[TJF1960]

To test I just created a new scene with a SL Dimmer as a controller, no other devices are in the scene (although that shouldn't matter). Went back to a program, selected "adjust scene" and that SL Dimmer showed up in the drop down box for "In Scene" whereas that device wasn't an option before it was made a controller in the new scene.

 

I should have asked what platform version for the ISY are you on and what does the ISY report the version is for the dimmer you want to scene adjust?

 

Also, are there any devices showing in the drop down box or just scenes?

 

Tim

 

Edit: I just re-read your first post and see you are on 3.1.2 same as mine. Sorry. What is the version reported of the dimmer?

[jerlands]

I just re-read your first post and see you are on 3.1.2 same as mine. Sorry. What is the version reported of the dimmer?

it's new v.40.. I'm having some strange events in the console as graphics for ON/OFF and notifications not showing after I "restored the device." I did that because I understand from http://forum.universal-devices.com/viewtopic.php?p=10667#10667

Unlike using a program to test for a button press and then turn the light on to a certain level, the actual link within the device is updated.

If I get this.. the ISY should write to the dimmer the new instruction but this isn't happening. I'm unsure right now what's going on with my ISY but it's not 100%

[TJF1960]

Yes, the ISY writes the local on levels to the dimmer, what you are trying to do should work. Problems with the on/off status in the gui do indicate something is not right.

 

I have found sometimes rebooting the ISY and PLM will clear up strange issues, but aside from that I am sure LeeG or Michel can/will offer further assistance.

 

Tim

[LeeG]

jerlands

 

Does the Admin Console show a v.00 or an actual v.xx number for the firmware level of the Dimmer?

 

There is a question about what 3.1.2 is using for updating the Local On Level and Local Ramp Rate. Another user tried to change the Local On Level through the Admin Console and found it necessary to power cycle the device for the changes to take effect. This is the result of 3.1.2 using the old I1 Peek/Poke method for setting the Local values. The I1 technique requires some devices to be power cycled. For now I am assuming 3.1.3 will resolve this. This drop should be out very soon.

 

If the firmware version is v.00 then the Dimmer was not added using Auto Discover. The only way to correct this is to delete the Dimmer and add it back using Auto Discover. Although this is ultimately necessary it may not resolve the problem because of the possible glitch at 3.1.2. First, fix the device such that the firmware level is understood by the ISY. Second, change the Local On Level through the Admin Console and see if it takes effect without the power cycle. If not set the Local On Level again and pull the air-gap switch for 30 seconds. Be care when pushing the sir-gap back in not to push it past being flush with the frame as that can factory reset the Dimmer and the new Local On Level will be lost.

 

If the power cycle works then the Local On Level cannot be changed programmatically because the power cycle would be required twice each day. Hopefully 3.1.3 will resolve.

 

At this point we really do not know for sure what the issue is on your system. To get definitive information run Tools | Diagnostics | Event Viewer with the Device communications events selected from the pulldown (important). From the Admin Console, under Program summary, right click on the Program that is changing the Local On Level, select Run Then. Post the event trace. That will show if the I1 or I2 method is being used to update the Local information.

 

The alternative is to wait a few days for the 3.1.3 drop and see if that resolves the problem. Either way if the firmware level for the Dimmer is v.00, the Dimmer should be deleted and added back using Auto Discovery. May not fix the problem now but will likely be a requirement at 3.1.3.

 

Let us know what you want to do. I’ll be happy to look at the Event Trace if you want to spend some time on it at 3.1.2.

 

Lee

[jerlands]

jerlands

 

Does the Admin Console show a v.00 or an actual v.xx number for the firmware level of the Dimmer?

 

That will show if the I1 or I2 method is being used to update the Local information.

 

Let us know what you want to do. I’ll be happy to look at the Event Trace if you want to spend some time on it at 3.1.2.

 

Lee

 

Hi Lee,

 

Yes it shows v.40 in the console and "engine version i1" ... here's the log..

 

Thu 05/19/2011 11:34:28 PM : [ Time] 23:34:29 0(0)

Thu 05/19/2011 11:34:28 PM : [19 49 75 1 ] Link 1 : 0FF0 [A2180F9DBD660800] Saving [..........66....]

Thu 05/19/2011 11:34:28 PM : [All ] Writing 1 bytes to devices

Thu 05/19/2011 11:34:28 PM : [19 49 75 1 ] Using engine version i1 for 'Master Bathroom Vanity Light'

Thu 05/19/2011 11:34:28 PM : [19 49 75 1 ] Link 1 : 0FF0 [A2180F9DBD660800] Writing [..........66....]

Thu 05/19/2011 11:34:28 PM : [iNST-ACK ] 02 62 19.49.75 0F 28 0F 06 SET-MSB(0F)

Thu 05/19/2011 11:34:28 PM : [iNST-SRX ] 02 50 19.49.75 0F.9D.BD 2B 28 0F SET-MSB(0F)

Thu 05/19/2011 11:34:28 PM : [standard-Direct Ack][19.49.75-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Thu 05/19/2011 11:34:29 PM : [iNST-ACK ] 02 62 19.49.75 0F 2B F5 06 PEEK (F5)

Thu 05/19/2011 11:34:29 PM : [iNST-SRX ] 02 50 19.49.75 0F.9D.BD 2B 2B 66 PEEK (66)

Thu 05/19/2011 11:34:29 PM : [standard-Direct Ack][19.49.75-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Thu 05/19/2011 11:34:29 PM : [19 49 75 1 ] Link 1 : 0FF0 [A2180F9DBD660800] Saving [............08..]

Thu 05/19/2011 11:34:29 PM : [All ] Writing 1 bytes to devices

Thu 05/19/2011 11:34:29 PM : [19 49 75 1 ] Using engine version i1 for 'Master Bathroom Vanity Light'

Thu 05/19/2011 11:34:29 PM : [19 49 75 1 ] Link 1 : 0FF0 [A2180F9DBD660800] Writing [............08..]

Thu 05/19/2011 11:34:29 PM : [iNST-ACK ] 02 62 19.49.75 0F 28 0F 06 SET-MSB(0F)

Thu 05/19/2011 11:34:29 PM : [iNST-SRX ] 02 50 19.49.75 0F.9D.BD 2B 28 0F SET-MSB(0F)

Thu 05/19/2011 11:34:29 PM : [standard-Direct Ack][19.49.75-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Thu 05/19/2011 11:34:30 PM : [iNST-ACK ] 02 62 19.49.75 0F 2B F6 06 PEEK (F6)

Thu 05/19/2011 11:34:30 PM : [iNST-SRX ] 02 50 19.49.75 0F.9D.BD 2B 2B 08 PEEK (08 )

Thu 05/19/2011 11:34:30 PM : [standard-Direct Ack][19.49.75-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

If nothing comes of this I'll wait for 3.1.3 and see if that changes anything.

 

Thanks for the help.

 

Jon

[LeeG]

jerlands

 

The trace shows the Responder link record On Level and Ramp Rate are being changed, not the Local On Level and Local Ramp Rate. That makes the issue the way the Adjust Scene is defined. Can't say I have ever tried dynamically changing the Local On Level with an Adjust Scene. The problem I was describing before was related to statically changing the Local On Level through the Admin Console. Let me run some tests here to see how that is defined. May be tomorrow before I get back. Getting pretty late on the East coast.

 

Lee

[LeeG]

jerlands

 

The Adjust Scene should be defined as follows …

 

The In Scene field is the name of the SwitchLinc Dimmer

The Set field is the name of the SwitchLinc Dimmer

 

My SwitchLinc Dimmer is v38 so I would expect your v40 Dimmer to work when the Adjust Scene is defined correctly. The following is the Event Trace from a Program that issues an Adjust Scene defined as indicated above, setting the Local On Level to 50% (0x7F). Note that an I2 Extended Set/Get is used to set the Local On Level which takes effect immediately on my V38 SwitchLinc Dimmer.

 

 

Fri 05/20/2011 01:28:24 AM : [ Time] 01:28:39 2(0)

 

Fri 05/20/2011 01:28:24 AM : [All ] Writing 1 bytes to devices

 

Fri 05/20/2011 01:28:24 AM : [16 3F 93 1 ] Memory : Write dbAddr=0x0032 [7F]

 

Fri 05/20/2011 01:28:24 AM : [iNST-ACK ] 02 62 16.3F.93 1F 2E 00 01 06 7F 00 00 00 00 00 00 00 00 00 00 00 06 (00)

 

Fri 05/20/2011 01:28:25 AM : [iNST-SRX ] 02 50 16.3F.93 12.9F.E4 2B 2E 00 (00)

 

Fri 05/20/2011 01:28:25 AM : [standard-Direct Ack][16.3F.93-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Fri 05/20/2011 01:28:25 AM : [ 16 3F 93 1] OL 127

 

Lee

[jerlands]

jerlands

 

The Adjust Scene should be defined as follows …

 

The In Scene field is the name of the SwitchLinc Dimmer

The Set field is the name of the SwitchLinc Dimmer

 

Lee

 

I'll try tomorrow with the dimmer as a controller and see if it changes anything.

 

Thanks,

 

Jon

[jerlands]

Had a break and got it working. Initially I think the problem was I hadn't "Run Then" before testing so the link wasn't written to the dimmer. I eventually tried "restore device" but I doubt that did the same. I'll see in the morning if it turns on now 100%, as it should, or if it still dims

 

Thanks for the great help.

 

Jon

[LeeG]

jerlands

 

Glad it looks like it is working. The Action statements can be tested simply by doing a Run Then, exercise the SwitchLinc paddle, then Run Else and exercise the paddle again. That will not test the time aspects of the If but it should confirm the Adjust Scene statements in both the Then and Else clauses work as expected. Then if something does not work the If is about the only thing left.

 

Lee

[jerlands]

Still dimming this morning...

 

I tried "Run Else" and now at 100% but if I "Run Then" it reverts to dim.

 

Here's a copy of the program

 

If
       From    12:00:00AM
       To       5:00:00AM (same day)

Then
       In Scene 'Master Bathroom Vanity Light' Set 'Master Bathroom Vanity Light' 50% (On Level)
       In Scene 'Master Bathroom Vanity Light' Set 'Master Bathroom Vanity Light' 0.3 Sec (Ramp Rate)

Else
       In Scene 'Master Bathroom Vanity Light' Set 'Master Bathroom Vanity Light' 100% (On Level)
       In Scene 'Master Bathroom Vanity Light' Set 'Master Bathroom Vanity Light' 0.3 Sec (Ramp Rate)

 

Here's a copy of the log

 

Run Then

Fri 05/20/2011 09:46:54 AM : [ Time] 09:46:55 0(0)

Fri 05/20/2011 09:46:54 AM : [All ] Writing 1 bytes to devices

Fri 05/20/2011 09:46:54 AM : [19 49 75 1 ] Memory : Write dbAddr=0x0032 [7F]

Fri 05/20/2011 09:46:54 AM : [iNST-ACK ] 02 62 19.49.75 1F 2E 00 01 06 7F 00 00 00 00 00 00 00 00 00 00 00 06 (00)

Fri 05/20/2011 09:46:54 AM : [iNST-SRX ] 02 50 19.49.75 0F.9D.BD 2B 2E 00 (00)

Fri 05/20/2011 09:46:54 AM : [standard-Direct Ack][19.49.75-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Fri 05/20/2011 09:46:54 AM : [All ] Writing 0 bytes to devices

Fri 05/20/2011 09:46:54 AM : [ 19 49 75 1] OL 127

Paddle Exercise

Fri 05/20/2011 09:47:15 AM : [iNST-SRX ] 02 50 19.49.75 00.00.01 CB 11 00 LTONRR (00)

Fri 05/20/2011 09:47:15 AM : [standard-Group][19.49.75-->Group=1] Max Hops=3, Hops Left=2

Fri 05/20/2011 09:47:15 AM : [ 19 49 75 1] DON 0

Fri 05/20/2011 09:47:15 AM : [ 19 49 75 1] ST 127

Fri 05/20/2011 09:47:15 AM : [iNST-SRX ] 02 50 19.49.75 0F.9D.BD 41 11 01 LTONRR (01)

Fri 05/20/2011 09:47:15 AM : [standard-Cleanup][19.49.75-->ISY/PLM Group=1] Max Hops=1, Hops Left=0

Fri 05/20/2011 09:47:16 AM : [iNST-SRX ] 02 50 19.49.75 00.00.01 CB 13 00 LTOFFRR(00)

Fri 05/20/2011 09:47:16 AM : [standard-Group][19.49.75-->Group=1] Max Hops=3, Hops Left=2

Fri 05/20/2011 09:47:16 AM : [ 19 49 75 1] DOF 0

Fri 05/20/2011 09:47:16 AM : [ 19 49 75 1] ST 0

Fri 05/20/2011 09:47:16 AM : [iNST-SRX ] 02 50 19.49.75 0F.9D.BD 41 13 01 LTOFFRR(01)

Fri 05/20/2011 09:47:16 AM : [standard-Cleanup][19.49.75-->ISY/PLM Group=1] Max Hops=1, Hops Left=0

Run Else

Fri 05/20/2011 09:47:39 AM : [ Time] 09:47:40 0(0)

Fri 05/20/2011 09:47:39 AM : [All ] Writing 1 bytes to devices

Fri 05/20/2011 09:47:39 AM : [19 49 75 1 ] Memory : Write dbAddr=0x0032 [FF]

Fri 05/20/2011 09:47:39 AM : [iNST-ACK ] 02 62 19.49.75 1F 2E 00 01 06 FF 00 00 00 00 00 00 00 00 00 00 00 06 (00)

Fri 05/20/2011 09:47:39 AM : [iNST-SRX ] 02 50 19.49.75 0F.9D.BD 2B 2E 00 (00)

Fri 05/20/2011 09:47:39 AM : [standard-Direct Ack][19.49.75-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Fri 05/20/2011 09:47:39 AM : [All ] Writing 0 bytes to devices

Fri 05/20/2011 09:47:39 AM : [ 19 49 75 1] OL 255

Paddle Exercise

Fri 05/20/2011 09:47:53 AM : [iNST-SRX ] 02 50 19.49.75 00.00.01 CB 11 00 LTONRR (00)

Fri 05/20/2011 09:47:53 AM : [standard-Group][19.49.75-->Group=1] Max Hops=3, Hops Left=2

Fri 05/20/2011 09:47:53 AM : [ 19 49 75 1] DON 0

Fri 05/20/2011 09:47:53 AM : [ 19 49 75 1] ST 255

Fri 05/20/2011 09:47:53 AM : [iNST-SRX ] 02 50 19.49.75 0F.9D.BD 41 11 01 LTONRR (01)

Fri 05/20/2011 09:47:53 AM : [standard-Cleanup][19.49.75-->ISY/PLM Group=1] Max Hops=1, Hops Left=0

Fri 05/20/2011 09:47:54 AM : [iNST-SRX ] 02 50 19.49.75 00.00.01 CB 13 00 LTOFFRR(00)

Fri 05/20/2011 09:47:54 AM : [standard-Group][19.49.75-->Group=1] Max Hops=3, Hops Left=2

Fri 05/20/2011 09:47:54 AM : [ 19 49 75 1] DOF 0

Fri 05/20/2011 09:47:54 AM : [ 19 49 75 1] ST 0

Fri 05/20/2011 09:47:54 AM : [iNST-SRX ] 02 50 19.49.75 0F.9D.BD 41 13 01 LTOFFRR(01)

Fri 05/20/2011 09:47:54 AM : [standard-Cleanup][19.49.75-->ISY/PLM Group=1] Max Hops=1, Hops Left=0

 

Seems I have to run then/else to change from dimming/100%

 

Jon

[LeeG]

jerlands

 

The Adjust Scene statements generate an actual Insteon command only when the ISY thinks the value being set is different than what the device is currently set to. This saves issuing unnecessary powerline traffic. Looking at the event trace from the last post only the On Level is being updated. The Ramp Rate is not being updated because the ISY thinks the Ramp Rate is already set to .3 seconds. I think the testing got the ISY value and the device value out of sync such that it did not think it had to change to 100%.

 

I set up a similar Program using a From/To with the Then and Else setting the Local On Level to different values. The Then Clause ran at the From time and the Else Clause ran at the To time. Be sure the Local On Level is at 100% before midnight and have the Event Trace with Device communications event selected running before midnight. Leave the trace running through the To time.

 

I think what you have will work.

 

Lee

 

EDIT: also do a Save Changes to be sure the latest changes are actually in effect.

[jerlands]

I see.. I wasn't giving the program time to run.

 

Thanks,

 

Jon