Can't find a posting

[andrew77]

I know it's been covered but I can't find a posting anywhere.

 

I have an ALL OFF scene but not all the KPL LEDs shut off even though the load is off.

 

When I try to add the KPL D button as a responder (just an example) it says it's already a member of the scene.

 

If someone could point me to the posting or answer this post, that would be great.

 

Thanks,

Drew

[LeeG]

andrew77

 

If the KeypadLinc lost a link record delete the node from the Scene and add it back. If that does not resolve the problem try a Restore Device against the KeypadLinc. If neither resolves the problem the next thing to look at is powerline quality to that KeypadLinc. To turn a Scene Off the ISY issues a single command that is not directed at any specific device. If some devices respond and some do not the ISY has issued the single command. Either a link record problem in the device or the device is not receiving the command.

 

Lee

[andrew77]

I'm not entirely clear on your response.

I'm not sure what a "link record" is. The scene works fine. I just want to have the LEDs of the KPLs in the scenes shut off when I press the "ALL OFF"

scene.

i.e. The hall light goes off (it's the load on the KPL or the MAIN or A button) but the D button LED stays on. I'd like that to shut off too.

 

I'm not sure what you're talking about when you say "node".

And I don't believe I need to restore the KPL.

 

And it's not a powerline quality issue.

 

I could make a button grouping but then I can't have two scenes on the same KPL running at the same time.

 

Drew

[oberkc]

I believe LeeG was suggesting removing the offending keypad button(s) from the scene, then readding.

 

If you do this, confirming that all desired devices and buttons are in the "All Off" scene, identified as controllers and responders as you desire, and still have problems, then I generally suspect communication errors. This assume there are no device failures.

 

How are you turning the scene off? What do you mean by "load is off"? Is the device controlling the load defined as a controller of the "all off" scene?

[andrew77]

I can't add the button to the scene as its the D button of a KPL that is in the all off scene. If I try to add it into the scene it tells me its already part of the scene.

 

I turn the scene off from another KPL that triggers the scene.

When I say the load is off, the light that is wired to the KPL is off.

It is not a controller but a responder to the scene. There's only one controller to the scene. (that's on a different KPL)

[LeeG]

andrew77

 

A Scene operates as a result of a link being created between the Controller and the Responders. In this scenario the Controller is the ISY PLM and the Responders are whatever devices have been added to the Scene as other Controllers or Responders. The KeypadLinc will have a Responder link record for the load control button (Main A) and it will have a Responder link record for button D. From the symptom it sounds like the Responder link record for button D is missing or has been corrupted.

 

Without the button D Responder link record the KeypadLinc does not know to turn Off button D when it receives a command to turn Off the Scene. The Responder link record for Main A exists because Main A turns Off. Since button D does not turn Off the existence of a valid Responder link record for button D is in question.

 

The suggestions in my previous post will cause the ISY to rewrite the Responder link record for button D.

 

UPDATE: I defined a Scene with the KPL load button as a Controller and a Secondary button as a Responder and found the link records were incorrectly written. A Show Device Links Table issued for the KeypadLinc with a subsequent Compare shows the ISY Link Record information for button D does not match the actual link record in the KeypadLinc for button D.

 

Suggest running a Show Device Links Table (right click KPL main node Main A, select Diagnostics | Show Device Links Table). When the display is complete click the Compare button. Do any of the link records indicate Mismatch?

 

I see this on 3.1.10. What ISY firmware is being used?

 

Lee

[oberkc]

If I try to add it into the scene it tells me its already part of the scene.

 

Thus the suggestion to first REMOVE it from the scene, then to add it back.

[andrew77]

Hi oberkc;

 

I probably wasn't clear.

 

When I have the "MAIN" or "A" button in the scene, as I do,

and I try to ADD the "D" button from the same KPL to the scene to shut off the LED of the "D"

button, it THEN tells me that it is already part of the scene.

[LeeG]

Obviously that is not correct. What ISY firmware are you using?

 

EDIT;

 

appoligies for the wrong direction in diagnosing the problem. When the initial post said the secondary KPL button D would not turn Off I assumed the conditions to make that work had been established and were not working rather than not be able to establish the condition at all.

 

EDIT2:

 

Am I correct in the assumption that KPL button D was NEVER added to the Scene. Is it possible it was added before, is not working now but was added earlier. It would make more sense that it is not working as a defined Responder rather than can never be added as a Responder

[oberkc]

I probably wasn't clear

 

You are partly correct, I was not fully understanding your problem. It now sounds as if you have two problems?

 

One, you have a scene defined which has devices (not keypad D) that don't respond. Two, you cannot add a particular keypad button (Keypad D) to that scene.

 

When you select the scene at the admin panel, and it shows the included devices, which of those does not turn off? Furthermore, you confirm that keypad button D is not listed in the included devices, correct?

 

If you find keypad D in the admin panel device listing, and select it, you should notice (at the right extreme of the admin panel) a list showing "controls" and "is controlled by". Is there any indication here that keypad D is controlled by the device that is controller of your "all off" scene?

 

I still suspect communication issues.