Jump to content

Keypadlinc button number


MarkJames

Recommended Posts

I'm probably having a seniors moment here but maybe someone could refresh my memory.

 

So if I look at a KPL-8, for instance, grouped in my admin console I see all 8 buttons with the meaningful names I gave them.  But what happens if I can't see the KPL from where I'm sitting or I've pulled the buttons off it so that I don't know which is which.  There was (is?) a place where  the interface told me which button was which - if memory serves it  used to look like the devices were like ab.cd.ef.1 and ab.cd.ef.2 etc. up to ab.cd.ef.8

 

Is that still somewhere that I'm not seeing or has that been deprecated?

 

 

mark

Link to comment

lol - no, I know that...

 

Once you rename them, though, how can you tell which one is which without looking at your labels?

 

When you first link it it will name it

 

newdevice - A

newdevice - B

newdevice - C

etc

 

But once I change it to 

 

Room Light

Table Lamp

Reading light

etc

 

How can I tell which button is, say, A, from the ISY admin panel without looking at the physical KPL.  I'm not sure if it was ISY or one of the other platforms I used prior to it that labelled them in the main device list with .1, .2, .3 or maybe it was .a, .b, .c...

 

mark

Link to comment

The Event Trace shows button number.

 

Thu 06/02/2016 12:24:01 PM : [iNST-SRX    ] 02 50 1B.57.F8 00.00.06 CB 13 00    LTOFFRR(00)
Thu 06/02/2016 12:24:01 PM : [std-Group   ] 1B.57.F8-->Group=6, Max Hops=3, Hops Left=2
Thu 06/02/2016 12:24:01 PM : [D2D EVENT   ] Event [1B 57 F8 6] [DOF] [0] uom=0 prec=-1
Thu 06/02/2016 12:24:01 PM : [  1B 57 F8 6]      DOF   0
Thu 06/02/2016 12:24:01 PM : [D2D EVENT   ] Event [1B 57 F8 6] [sT] [0] uom=0 prec=-1
Thu 06/02/2016 12:24:01 PM : [  1B 57 F8 6]       ST   0
Thu 06/02/2016 12:24:01 PM : [iNST-SRX    ] 02 50 1B.57.F8 22.80.0B 41 13 06    LTOFFRR(06)
Thu 06/02/2016 12:24:01 PM : [std-Cleanup ] 1B.57.F8-->ISY/PLM Group=6, Max Hops=1, Hops Left=0
Thu 06/02/2016 12:24:01 PM : [iNST-DUP    ] Previous message ignored.
Link to comment

Thanks Lee - I was just looking at that....

 

Didn't the UI used to display it before?  

 

I was sure that when you went into the Main tab and clicked on the root node of a KPL it brought up in the main properties window the name with the address and device type as it does now but with a suffix for which button it represented so that when you looked at the load button it would say 

 

                     KPL-GARAGE

0A.AB.1E-1 (2486D)  Keypadlinc Dimmer v.2A

 

but when you looked at button B it would say 

 

                     KPL-Driveway

0A.AB.1E-2 (2486D)  Keypadlinc Dimmer v.2A

 

Am I imagining this?

Link to comment

lol - no, I know that...

 

Once you rename them, though, how can you tell which one is which without looking at your labels?

 

When you first link it it will name it

 

newdevice - A

newdevice - B

newdevice - C

etc

 

But once I change it to 

 

Room Light

Table Lamp

Reading light

etc

 

How can I tell which button is, say, A, from the ISY admin panel without looking at the physical KPL.  I'm not sure if it was ISY or one of the other platforms I used prior to it that labelled them in the main device list with .1, .2, .3 or maybe it was .a, .b, .c...

 

mark

 

You could append the button letter to the name i.e.  Room Light (a),  etc.

Link to comment

I pressed the button.

 

I've tried 3.3.10 on a 99i.  It does not show button number on the normal UI display of any of the buttons. 

 

lol - direct approach.

 

I was sitting here in the house trying to reconfigure the buttons on a KPL down on my dock.  I couldn't remember which button was which as I've changed their functionality quite a bit.  I was trying to figure it out without walking down to the dock and either looking at it or - as you did - pressing the button.

 

mark

Link to comment

I'm not - I use the button names.

 

It's just for organization.  I wanted to make the left button on the second row into a controller for a different scene than it was already assigned to.  Without going down and looking at it I didn't know which scene the left button on the second row was already assigned to.  

 

I suppose if I'd taken all the buttons off a KPL without noting what they were assigned to it would be a bigger problem - I'd have to reinstall it and press each button individually to figure out which was which.  

 

mark

Link to comment

I understand your dilemma. 3 of mine are in direct view of the computer and I turned their scenes on and off to see which one.

 

The others I wirenuted a cable with a plug, set them up at the computer for full functionality, then go install in their final home.  

 

One other idea to do at the beginning is to add prefixes to the key names at configure time:

 

A-Lights, B-Garage door, etc. The AC alphabetizes the devices as they're renamed and that's when they move out of order

 

Paul

Link to comment

This is what I do when I originally set up a KeyPad:

 

 

 

 

 The AC alphabetizes the devices as they're renamed and that's when they move out of order

 

Paul

 

Yep - I definitely *could have* or *should have* put a designation of some sort with each of my 160 KPL buttons but you know what they say about hindsight...

 

The alphabetizing is the problem.  If there was either a way to turn the alphabetizing off or to have the UI indicate which button is which I think that would be an improvement.  Perhaps I'll put this in as a feature request...

Link to comment

The alphabetizing is the problem.  If there was either a way to turn the alphabetizing off or to have the UI indicate which button is which I think that would be an improvement.  Perhaps I'll put this in as a feature request...

 

Just use a letter or number as the suffix (e.g., Kitchen Light_C)

Link to comment

Yep - I definitely *could have* or *should have* put a designation of some sort with each of my 160 KPL buttons but you know what they say about hindsight...

 

The alphabetizing is the problem.  If there was either a way to turn the alphabetizing off or to have the UI indicate which button is which I think that would be an improvement.  Perhaps I'll put this in as a feature request...

 

Mark 

 

I'll support that for sure. I keep saying I'm done implementing keypads, but...  :mrgreen:

 

As a suggestion, the requirement could be to add menu options when the keys are grouped under Main...Add menu options on the right-click for alpha order, or native (A-B-C) order. Just a thought

 

Paul

 

Paul

Link to comment

Archived

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


×
×
  • Create New...