Understanding IR codes captured in base64 vs LIRC HEX

Configuration
1

Hi!
I am acquiring the IR codes a CD player remote. I am using a device that uses a ts1201 quirk and it works just fine.

The codes are encoded as base64 strings, that is fine as this is what needs to put in the script to issue the command.

However I was wondering if one could leverage better the existing databases of IR codes. For instance this remote is supported in the LIRC database
https://lirc.sourceforge.net/remotes/pioneer/CU-PD096
hence I got curious how I should translate the info on LIRC on base64

Some example base64 I acquired


POWER
BXQhwRAVAkABA0gGFQLgAwHAD0AHQANAAUAHwANAAUAL4AMBQA/AA+ADAeATE2AbAJbg/YfghIcCBhUC

PLAY
BXYhyRASAkABA04GEgLgAwHAD0AHQANAAUAHwANAAUALQAFAB8ADQAFAC+APAcAbQAfAAwFEluD9h+CEhwIGEgI=

PAUSE
EpIhmhAJAgkCQQIpBgkCCQJBAglgAQFBAsAPQAdAAwEJAsALgAdAAUALAAlgAUAHgAMCKQYJIAMCQQIJYAFABwRBAikGCeAAAwMJAkECQAPgAxMBLZbgK4cBCQJAA0ABBCkGQQIJYAHgAQcCKQYJIAMDQQIJAsADAQkCQA/AAwEJAkADAQkCwA9AB4CHBUECCQJBAkAPQAcACWABAUECwA9ABwUpBgkCCQJAB0ADBgkCKQZBAgkgAQUpBgkCCQJAC0ADQAEBQQJAE0ADAwkCQQKAAwQJAikGQeAAAwEJAkADAQkC4AMT4A2HAUECQAMFKQYJAgkCQAeAA+ABCwEJAkADQAGAB4AbAAlgAQNBAikGQAMFCQIJAkECgAMBCQJADwIpBkFgAwEJAkADDQkCKQYJAikGQQIpBkEC

NEXT
BYkhsBAYAkABBTMGwAEYAuABAQMzBhgCQAFAB0ADQAFAB8ADQAFAC+ALAYAXAlICGKABQA/gAwNAAeADDwE0luADhwMYAhgC4AU7QAFAF0ADQAFAB8ADQAFAC+AJAQFSAuAHF0AP4AMDQAHgAw/gAYfAOwJSAhigAUAnAxgCUgJAB0ADARgC4AELgA8BGALABwQYAlICGOACAeABF0ABAVICQA/gAwNAAeADD+AJh8ABgDsBGAKAB0AzARgC4AELgA8BGALABwMYAlIC4QPV4AEXQAEBUgJAD+ADA0AB4AMP4AGHARgCQBfgAQGAO0ABATMGwAuABwEzBoADQAFAC+AFAQJSAhggAQMzBlIC4AWXA1ICMwZAF4ADQAELMwYYAjMGGAIzBlIC

PREVIOUS
EoghtxAKAgoCQAI2BgoCCgJAAgpgAQFAAsAPQAdAAwEKAuABCwQ2BkACCiABBzYGCgIKAkACwAdACwAKIAEBNgaABwEKAkAHQAMDCgI2BsADwA8AQOAAEwEvluAzh4BHAQoC4AEHQAtAAwc2BgoCCgJAAoADQAEBQAJAE4ADAkACCiABQAcBNgZABwEKAuANhwFAAkADQB8BCgKAB+AHC+ADDwEKAoAjBAoCQAIKYAEBQALAH0ALAApgAQFAAkATgAMCQAIKIAEBNgZAAwBAYAfgCYdAAQFAAkADBTYGCgIKAkAHQAMDCgIKAoAHQAtAAwEKAoAPAQoC4AEHAApgAQFAAsAfAApgAUAHAUACQBPAAwEKAsAPBUACNgZAAg==

STOP
BXghtRARAkABA1EGEQLgAwHAD0AHQANAAUAHwANAAUALwAFAC0ADQAHAB8AB4AMPwAtAB8ADAUmW4P2HYIcCBhEC

How these relate to those in the LIRC config? I found [lirc2broadlink.pl - converts LIRC conf files to broadlink b64 codes for use in home assistant · GitHub](this perl script) which has operated the translation, but the codes do not work with my unit, e.g. POWER is converted to JgBIAAABG4gUDxQyFA8UDxQPFDIUDxQyFDIUDxQyFDIUMhQPFDIUDxQPFA8UMhQyFDIUDxQPFA8UMhQyFA8UDxQPFDIUMhQyFAANBQAAAAAAAAAAAAAAAAAAAAA which is really different from the code I captured …

Another resource is https://pasthev.github.io/sensus/ but not so much that I can understand

2

Hello foice,

Better late than never, I just saw your post and I have the answer… :slightly_smiling_face:

Your B64 strings are not Broadlink, but Tuya codes. Reason I know is that I just updated Sensus IR & RF Code Converter to implement the Tuya IR protocol.

POWER -  NEC "Short" command: a21c

PLAY -  NEC "Short" command: a217

PAUSE -  NEC "Short" command: a218
signal is poorly acquired here, repeated 4 times - you might want to replace it with this corrected string:
C5chpBAOAg4CQwIqBoAHQAXgAw9AB+AFC8AbgAvAL8ADwCPgAxfAQ+ABY+AFEwEslg==

NEXT -  NEC "Short" command: a210 (repeated 5 times)

PREVIOUS -  NEC "Short" command: a211 (repeated 4 times)

STOP -  NEC "Short" command: a216

Entirely my fault… my tool has been online for years now, and it is only today that I posted a documentation for it - here it is: pasthev/sensus: Sensus IR & RF Codes converter / analyzer for Lirc, Pronto, Broadlink & raw codes.

It should help you to easily interpret your Tuya codes, and the user guide explains how to “clean” the repeats in a signal, as well as how to convert Tuya to LIRC, and LIRC to Tuya - or Broadlink.

If too late for you, I hope this will help others,
Pascal

Example view of your Pause command within the tool, where the repeated signal can easily be spotted:

foice01
foice011915×1174 244 KB