Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TECO recieved but sended copy is not read in target device #1950

Open
whoim2 opened this issue Jan 21, 2023 · 6 comments
Open

TECO recieved but sended copy is not read in target device #1950

whoim2 opened this issue Jan 21, 2023 · 6 comments

Comments

@whoim2
Copy link

whoim2 commented Jan 21, 2023

Version/revision of the library used

v2.8.4 from Library Manager in Arduino IDE 1.8.19

ESP8285 (ESP-M3) and recieve / send modules and IR-diodes with mosfet.
nonos-sdk-2.2.1 +100 (190703)
This problem only at TECO protocol, NEC and LG worked perfecly.
This is my universal IR center with http, mqtt and IR control: https://github.com/whoim2/esp-ir-center-and-relays

Describe the bug

Readed string from IR remote / climat device: 25060053C, TECO, 35 bits.
Send this code:

struct ir_data { //for store IR full packet
  uint64_t value;
  decode_type_t decode_type;
  uint8_t bits;
};
...
ir_data _action_ir1;
...
//load values from memory and debug it
Serial.println("action1 started");
Serial.println(_action_ir1.value, HEX);
Serial.println(_action_ir1.decode_type, DEC);
Serial.println(_action_ir1.bits, DEC);
//send
if(_action_ir1.decode_type > 0 && _action_ir1.value != 0) {
    irsend.send(_action_ir1.decode_type, _action_ir1.value, _action_ir1.bits);
    Serial.println("action1 sended");
 }

Result from serial debug:

action1 started
25060053C
55
35
action1 sended

Diodes flashed in camera view. Device ("Besshof" climat separated device) not view this code, not beep as original ir-remote.

To Reproduce

Read TECO data from IR-remote and send copy of this code.

@NiKiZe
Copy link
Collaborator

NiKiZe commented Jan 21, 2023

Have this worked before?
What is the output from the dumpv2 application? (As described in the issue template) also have a read in the FAQ?

@whoim2
Copy link
Author

whoim2 commented Jan 21, 2023

I worked with nec, lg and also exported with some kind of protocol, not an exporter. The same code is executed using the console, by the value of the log line in littlefs (value, decode_type, bits) and by the trigger mqtt or http is called via send. It works right now with nec and lg, but does not work with teco, although the receiver always recognizes it perfectly, it turns out that this remote is teco.
Tomorrow I will try to master the dump.

@crankyoldgit
Copy link
Owner

I've reviewed the library code, and I can't see anything obvious that could cause a problem.
We will need to see a dump of the original remote to work backwards from there.

@whoim2
Copy link
Author

whoim2 commented Jan 23, 2023

Ok, im dump remote in 2-3 days

@crankyoldgit
Copy link
Owner

How did you go?

@whoim2
Copy link
Author

whoim2 commented Jan 31, 2023

How did you go?

No time now, trouble with health. Need many time for this, sorry. Maybe, end of this week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants