But here is the catch: I need to connect built-in protocol to device button since the remaining 30 or so functions are fine. I want to do some sort of a reverse keymove to my 5-8 button definitions. I wonder if my upgrade can in fact override that part of the built-in setup.
I’m not even sure how to ask this question, it’s something like this:
Bound device/Old key = small replacement setup code + new function key code.
Problem is, source isn’t a device, I’m not assigning it to device button. So is this too backwards to contemplate? Is there another way? Would something in protocol builder spreadsheet be appropriate? I haven’t used it, looked at it once.
I suspect my idea is looney. Then again, a solution might be simple, done before, and I’ve read about it and miss the connection. Bottom line: it being Bastille day today, I expect a revolution at home against bad button assignments
, so please help.
That's what I missed in this context. 'All you need is setup and hex code' to paraphrase what you answered me to some previous problems. So the absence of device assignment is no longer a showstopper 
! In other instances, when all upgrades were in front of my face in KM, the meaning of external functions was more obvious. Trying, now, to correct a built in thing seemed different.
.
I intend to compile the little list. Just the action of doing so may reveal I'm wrong. I may have to enable learning again to be sure. I'll keep you posted if you're interested.
in extender keymoves, found and fixed.