NiKiZe
commented
8 months ago Closing as the issue template seems unchanged. Recommendation is to search existing issues before opening new ones.
Closed Tinyu-Zhao closed 8 months ago
NiKiZe
commented
8 months ago Closing as the issue template seems unchanged. Recommendation is to search existing issues before opening new ones.
Version/revision of the library used
v.2.8.6
Describe the bug
To Reproduce
What steps did you do, and what did or didn't actually happen? How can we reproduce the issue?
e.g. 1. Initialise the IRsend class. 2.
IRsend.sendFoobar(0xdeadbeef);3. Foobar BBQ went into Cow(er)-saving mode and fried me a couple of eggs instead.Example code used
Include all relevant code snippets or links to the actual code files. Tip: How to quote your code so it is still readable in the report.
Expected behaviour
What steps did you do and what should it have done? A clear and concise description of what you expected to happen.
e.g. 1. Initialise the IRsend class. 2.
IRsend.sendFoobar(0xdeadbeef);3. Foobar branded BBQ turns on and cooks me some ribs.Output of raw data from IRrecvDumpV2.ino or V3 (if applicable)
Include some serial text of the raw dumps of what the device saw.
Note: Output from Tasmota is not acceptable. We can't easily use their raw format.
What brand/model IR demodulator are you using?
Brand/Model code or None
_If VS1838b: That is likely your problem. Please buy a better one & try again. Reporting a capture or decode issue when you use one of these is effectively wasting our & your time. See the FAQ_
Circuit diagram and hardware used (if applicable)
Link to an image of the circuit diagram used. Part number of the IR receiver module etc. ESP8266 or ESP32 board type.
I have followed the steps in the Troubleshooting Guide & read the FAQ
Yes/No.
Has this library/code previously worked as expected for you?
Yes/No. If "Yes", which version last worked for you?
Other useful information
More information is always welcome. Be verbose.