Yes, it is the standard HK IR signal for Discrete On. However, the Pronto Hex represention, while accurately showing the learned signal, is probably not exactly the signal GC wants to see.
As learned:
0000 006D 0026 0000 0156 00AB 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 003F 0016 0016 0016 0016 0016 0016 0016 0016 0016 003F 0016 003F 0016 003F 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 003F 0016 003F 0016 003F 0016 003F 0016 003F 0016 003F 0016 003F 0016 003F 0016 0016 0016 0016 0015 0685 0157 0055 0016 0E40 0157 0055 0015 4634

Better:
0000 006D 0022 0002 0156 00AB 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 003F 0016 0016 0016 0016 0016 0016 0016 0016 0016 003F 0016 003F 0016 003F 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 003F 0016 003F 0016 003F 0016 003F 0016 003F 0016 003F 0016 003F 0016 003F 0016 0016 0016 0016 0015 0685 0157 0055 0016 0E40

This means 22H (34 decimal) burst pairs of the IR signal, followed by 2 burst pairs that are a "ditto", or a repeat.  The learned signal doesn't divide up the regular and repeated parts, and includes a partially completed second ditto.

So in IRscope, go to the Export Menu and change "Export from learned" to "Export from decode".  That will clean up the signals, and probably GC will be happier.
You'll need the irp file, which is part of the MakeHex distribution.  Get the MakeHex GUI also.

BTW, you'll likely find some device 130.114 signals also.