There are guys and gals here that are far more advanced than me as users, but here's my version:
In AHP you design one macro to do all the light on functions and one macro do take care of lights off.
When creating the macro, you assign the macro it's trigger command (i.e.: A5 ON or B6 OFF, etc)
You don't assign a button ON, the PalmPad, you assign the address or command that you SEND with the PalmPad Remote. And, if you are going to set up buttons on your HomeLink visor, you don't even need the PalmPad in your vehicle, as long as the CM15a is located where it can receive the HomeLink signal, if not another receiver could be installed nearby that will repeat the command on the powerline.
I hope that makes sense...you design the macro to turn on the lights with trigger A1 ON
When you drive in (you have already assigned the Homelink button the address A1 ON) you push that button...HomeLink sends A1 ON to the receiver (CM15a) and the macro is executed.
If you want to do the same with another HomeLink button with the address A1 OFF, then you would trigger your lights off macro.
IF you push either the A1 ON or A1 OFF buttons on the PalmPad, it would accomplish the same thing.