Add Remko RKL 360/460/470/480-Series IR-Remote Codes

[sorryusernameisalreadytaken]

The only remko ird-codes I found are theese here:
Lucaslhm/Flipper-IRDB@c4e174e

Can somebody help me to translate them for IRremoteESP8266?

Unfortunately, I do not have the original remote control. However, I think all the data should be visible in the commit.

[NiKiZe]

Moved to discussions since it is request for help. And the required information or FAQ does not seem to have been read.

The linked codes mention NEC, have you tried using the address and commend as listed?

Have you any code written at all?

[sorryusernameisalreadytaken]

Thanks for moving it. That's a good idea.

No, I haven't written any code yet. I would like to try my hand at an existing integration in the next few days. For example this one from Trotec. Is that a good idea? Or should I make sure that I orient myself on an NEC-protocol device?
https://github.com/crankyoldgit/IRremoteESP8266/blob/master/src/ir_Trotec.h
https://github.com/crankyoldgit/IRremoteESP8266/blob/master/src/ir_Trotec.cpp

And what do you mean by "using the address and commend as listed?" Is there a chance to send these cmd's I a try'n'error way?

[crankyoldgit]

And what do you mean by "using the address and commend as listed?" Is there a chance to send these cmd's I a try'n'error way?

The data you linked to:
https://github.com/Lucaslhm/Flipper-IRDB/blob/b0beb46a37ed99cca8ee640fbd89502eb484c022/ACs/Remko/Remko_RKL.ir#L7-L11

name: POWER
type: parsed
protocol: NECext
address: 86 6B 00 00
command: 12 ED 00 00

I have no idea what format the "Flipper" database is using. You really need to get them to explain it somewhere.

Some protocols, like NEC, or NEC-like protocols, have part of their numeric code broken up into an address and a command. portion.

Take for example the Power IR command above.
NEC protocols are typically 32 bits long.
They list an Address of 86 6B, and a Command of 12 ED
They are 16-bits each, together, 32-bits.
So, potentially sending using irsend.sendNEC(0x866B12ED) might work, or try irsend.sendNEC(0x12ED866B);

Alternatively, try different bit orderings. i.e. Reverse the bits. Most Significant becomes the Least Significant, and vice-versa.

NEC could use this for encoding the address & the command. See:

IRremoteESP8266/src/ir_NEC.cpp

Lines 42 to 60 in ff045f1

	/// Calculate the raw NEC data based on address and command.
	/// Status: STABLE / Expected to work.
	/// @param[in] address An address value.
	/// @param[in] command An 8-bit command value.
	/// @return A raw 32-bit NEC message suitable for use with `sendNEC()`.
	/// @see http://www.sbprojects.net/knowledge/ir/nec.php
	uint32_t IRsend::encodeNEC(uint16_t address, uint16_t command) {
	command &= 0xFF; // We only want the least significant byte of command.
	// sendNEC() sends MSB first, but protocol says this is LSB first.
	command = reverseBits(command, 8);
	command = (command << 8) + (command ^ 0xFF); // Calculate the new command.
	if (address > 0xFF) { // Is it Extended NEC?
	address = reverseBits(address, 16);
	return ((address << 16) + command); // Extended.
	} else {
	address = reverseBits(address, 8);
	return (address << 24) + ((address ^ 0xFF) << 16) + command; // Normal.
	}
	}

But I think that's for NEC protocol, vs. what your suggested file is using, NECext .. NEC extension?!

Realistically, converting other peoples codes to work with our system is not something we really do, unless it is some well established standard. e.g. Pronto codes.

As for how to send it, try some of the code examples supplied with this library.