I used an Arduino Uno to capture and identify the IR codes transmitted alongside the BT by the BC-15A remote. I have previously done this successfully to obtain the codes for the RC-16A remote so the method should be fine. For the BC-15A, the device code seems to be 0x482c and by way of example the standby function button is 0x18 (which makes sense as other Topping remotes use 0x18 for this function). Other ways to express the power button are 482C18E7 (HEX); E7183412 (LSB); Device 18, subdevice 36, function 24 (NEC); and "0000 006C 0022 0002 015B 00AD 0016 0016 0016 0041 0016 0016 0016 0016 0016 0041 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0016 0016 0016 0016 0041 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0041 0016 0016 0016 0016 0016 0016 0016 0041 0016 0041 0016 0041 0016 0016 0016 0016 0016 0041 0016 0041 0016 0041 0016 06A4 015B 0057 0016 0E6C" (Pronto). Encouragingly, with Firmware 1.14, after programing an Android phone containing an IR blaster on which I run Unified Remote, the display of the DAC "woke" when any of the codes I identified were used, although it did not respond to the commands. I tried unpairing the bluetooth remote - no change. I then updated to v1.23 firmware and unpaired the bluetooth remote again. Surprisingly (given the firmware release notes), the DAC still does not respond to these codes and interestingly the display no longer wakes in response. Time to chase Topping for explanation again unless anyone has any ideas.