OK, here is what I did this morning. I enabled the Remote Control program under lights. Then I went into my A12 device in HG, clicked the box to enable remote control, and then clicked the eye. Then from the HG android app I turned on A12. The light went on, and I can confirm that my program (A12 RF On) ran but there was no RF code captured - got a timeout.
So I tried it again (clicking the eye) and this time I clicked A12 on one of my X12 remote - this time it did capture a code:
20 64 9B 18 E3
So that confirms the formatting to be correct like that. The X10 RF mofule (one I had pictured in my prior post) also reflected that.
However, the code for A12 On in the HG-RF.txt file is: 20-64-9b-18-e7
Even if I format that as 20 64 9B 18 E7
that does not match the code that was received by the X10 remote: 20 64 9B 18 E3
I tried A12 off and that code is also different:
HG-FR.txt = 20-64-9b-38-c7
From X120 Remote: 20 64 9B 38 C3
I assume the values in the HG-RF.txt file should match what the X10 remote is giving. not really sure why they are different.
So I updated my programs for A12 RF ON and A12 RF OFF to use the codes I got from the X10 remote. Then tried to turn on the device - it didn't work. Changed them back to the HG-RF.txt values (including the dashes) and it worked again.
Thinking maybe I made a mistake, I tried it again - and using the code from the X10 remote did not work but changing back to the value from HG-RF.txt did work.
And it seems using either 20 64 9B 18 E7 or 20-64-9b-18-e7 works the same.
In all those cases, it does not appear that the transmitted RF code get displayed in the X10 RF module.
So not sure why the values between the X10 Remote and the HG-RF.txt are different, but it seems using the ones from the HG-RF.txt in either format do work where as trying to use the one given by the remote does not.
Not sure why but wanted to share. - perhaps someone can confirm my findings. Thanks