Jump to content

Cannot adjust responder or local on level


Recommended Posts

Posted

I have an isy 99i running version 3.3.10 and switch links version 4.0. I have been unable to change the on levels of any switch links locally or through scene on levels without having to air gap the switch for setting to take effect. Example: I have a motion sensor controlling a switch link that turns on the bathroom light. During the day I want it to turn on 100% at night I want it to turn on 40%. I have set up an adjust scene program to do this and changes are reflected in the admin console but switch link is unaffected until I air gap the switch. Adjusting local switch on levels has the same effect.

Posted

Although older devices may need a power cycle to have Local values take affect, a Responder link record change should be immediate. Please post the Program that is issuing the Adjust Scene statements that are adjusting the Motion Sensor Responder link record in the SwitchLinc. It sounds like the In Scene parameter value may not be correct.

Posted

Scene is called upstairs bath motion

controller is upstairs bath-sensor

responder is upstairs bath dimmer

 

 

IF

FROM 11:00 PM

TO 6:00 AM (next day)

 

THEN

In scene 'upstairs bath motion' set upstairs bath dimmer 40% (on level)

 

ELSE

In scene 'upstairs bath motion' set upstairs bath dimmer 80% (on level)

 

change is reflected in the scene upstairs bath dimmer on level 40% but motion turns light to 100%

also when adjusting local on level through isy for the switch change is reflected on admin console but switchlink will not take settings till air gap

Posted

The Adjust Scene is setting the SwitchLinc Responder On Level when the Scene name is used (PLM is the Controller in that situation). Additional Adjust Scene statements are needed

 

 

Then

In scene 'upstairs bath-sensor' set 'upstairs bath dimmer' 40% (on level)

In scene 'upstairs bath dimmer' set 'upstairs bath dimmer' 40% (on level)

........

Else

In scene 'upstairs bath-sensor' set 'upstairs bath dimmer' 80% (on level)

In scene 'upstairs bath dimmer' set 'upstairs bath dimmer' 80% (on level)

........

 

Note that the Adjust Scene statement itself does not actually change the current On Level. The Controller has to send an On (or the paddle operated) for the Adjust Scene changes to take affect. A SwitchLinc power cycle is not needed for the motion sensor-sensor to use the new values. I don't think the SwitchLinc has to be power cycled for the next paddle press to see the changes.

Posted

Thanks lee I've made the changes and it seems to be working great now. For the other issue regarding the local on levels of the switch, if I adjust the local on level of an individual device through isy I still don't see the changes at the switch even if I cycle the paddle a few times the settings don't take effect until I air gap the switch. Is there any way to get around this?

Posted

What is the SwitchLinc firmware (displayed on 2nd line right side of node display)?

 

 

 

I know that some older devices required a power cycle for them to pick up a new Local On Level but I did not think that applied to SwitchLincs.

post-973-140474163257_thumb.jpg

Posted

I believe the ISY will not write a value to the Switchlinc unless it believes that value is different than what is already there. Try a different value then come back to the value you are trying to set.

 

-Xathros

Posted

I have a V40 SwitchLinc Dimmer and have no problem changing the Local On Level with an Adjust Scene statement. It takes effect immediately without a power cycle. If using a different On Level does not result in the Local On Level changing without a power cycle, run Tools | Diagnostics | Event Viewer at LEVEL 3. Issue the Adjust Scene statement using a value that is not set in the SwitchLinc and post the event trace.

Posted

i have run adjust scene to adjust local on level to 40% no change at the switch

 

Sat 03/29/2014 07:33:10 AM : [ Time] 07:33:14 0(0)

 

Sat 03/29/2014 07:33:10 AM : [ 19 50 89 1] OL 102

 

Sat 03/29/2014 07:33:10 AM : [iNST-TX-I1 ] 02 62 19 50 89 0F 28 0F

 

Sat 03/29/2014 07:33:10 AM : [iNST-ACK ] 02 62 19.50.89 0F 28 0F 06 SET-MSB(0F)

 

Sat 03/29/2014 07:33:11 AM : [iNST-SRX ] 02 50 19.50.89 22.FF.D5 2B 28 0F SET-MSB(0F)

 

Sat 03/29/2014 07:33:11 AM : [std-Direct Ack] 19.50.89-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Sat 03/29/2014 07:33:11 AM : [iNST-TX-I1 ] 02 62 19 50 89 0F 2B C5

 

Sat 03/29/2014 07:33:11 AM : [iNST-ACK ] 02 62 19.50.89 0F 2B C5 06 PEEK (C5)

 

Sat 03/29/2014 07:33:11 AM : [iNST-SRX ] 02 50 19.50.89 22.FF.D5 2B 2B CC PEEK (CC)

 

Sat 03/29/2014 07:33:11 AM : [std-Direct Ack] 19.50.89-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Sat 03/29/2014 07:33:11 AM : [iNST-TX-I1 ] 02 62 19 50 89 0F 29 66

 

Sat 03/29/2014 07:33:11 AM : [iNST-ACK ] 02 62 19.50.89 0F 29 66 06 POKE (66)

 

Sat 03/29/2014 07:33:12 AM : [iNST-SRX ] 02 50 19.50.89 22.FF.D5 2B 29 66 POKE (66)

 

Sat 03/29/2014 07:33:12 AM : [std-Direct Ack] 19.50.89-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Sat 03/29/2014 07:33:12 AM : [iNST-TX-I1 ] 02 62 19 50 89 0F 28 00

 

Sat 03/29/2014 07:33:12 AM : [iNST-ACK ] 02 62 19.50.89 0F 28 00 06 SET-MSB(00)

 

Sat 03/29/2014 07:33:12 AM : [iNST-SRX ] 02 50 19.50.89 22.FF.D5 2B 28 00 SET-MSB(00)

 

Sat 03/29/2014 07:33:12 AM : [std-Direct Ack] 19.50.89-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Sat 03/29/2014 07:33:12 AM : [iNST-TX-I1 ] 02 62 19 50 89 0F 2B 32

 

Sat 03/29/2014 07:33:12 AM : [iNST-ACK ] 02 62 19.50.89 0F 2B 32 06 PEEK (32)

 

Sat 03/29/2014 07:33:13 AM : [iNST-SRX ] 02 50 19.50.89 22.FF.D5 2B 2B CC PEEK (CC)

 

Sat 03/29/2014 07:33:13 AM : [std-Direct Ack] 19.50.89-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Sat 03/29/2014 07:33:13 AM : [iNST-TX-I1 ] 02 62 19 50 89 0F 29 66

 

Sat 03/29/2014 07:33:13 AM : [iNST-ACK ] 02 62 19.50.89 0F 29 66 06 POKE (66)

 

Sat 03/29/2014 07:33:13 AM : [iNST-SRX ] 02 50 19.50.89 22.FF.D5 2B 29 66 POKE (66)

 

Sat 03/29/2014 07:33:13 AM : [std-Direct Ack] 19.50.89-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Posted

The command sequence being used at 3.3.10 is not what needs to be done. Here is the trace from 4.1.2 using a single Extended command to set the 40% On Level. The old sequence using Peek/Poke commands is why the SwitchLinc is not picking up the new Local On Level.

 

Sat 03/29/2014 11:15:20 AM : [ Time] 11:15:21 0(0)

Sat 03/29/2014 11:15:20 AM : [ 1D 23 6B 1] OL 102

Sat 03/29/2014 11:15:20 AM : [All ] Writing 1 bytes to devices

Sat 03/29/2014 11:15:20 AM : [1D 23 6B 1 ] Memory : Write dbAddr=0x0032 [66] cmd1=0x2E cmd2=0x00

Sat 03/29/2014 11:15:20 AM : [iNST-TX-I2 ] 02 62 1D 23 6B 1F 2E 00 01 06 66 00 00 00 00 00 00 00 00 00 00 65

Sat 03/29/2014 11:15:20 AM : [iNST-ACK ] 02 62 1D.23.6B 1F 2E 00 01 06 66 00 00 00 00 00 00 00 00 00 00 65 06 (00)

Sat 03/29/2014 11:15:20 AM : [iNST-SRX ] 02 50 1D.23.6B 22.80.0B 2B 2E 00 (00)

Sat 03/29/2014 11:15:20 AM : [std-Direct Ack] 1D.23.6B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Posted

Need to upgrade to a 994i.

 

If not running 3.3.10 on the 99i then upgrade to 3.3.10 which is the latest that runs on a 99i.

 

EDIT: sorry, I just reread the initial post. Need to upgrade to a 994i.

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...