Closed ferbulous closed 1 year ago
There could be multiple reasons for unreliable reception of IR signal What is the receiving hardware ? Is it the same circuitry between the ESP8266 and the ESP32 boards ? If not are you sure the circuitry used on ESP32 have the proper sensitivity ?
Probably looking at the signal on the GPIO with an oscilloscope and comparing between ESP8266 and ESP32 could give some clues on a possible hardware issue.
Sorry, i don't have oscilloscope Receiving hardware is the same device, I have 2 units for each one.
H/w tested:
Esp32 (Came with beken chip, I swapped with esp32-c3-05) 1) Tuya IR remote S-08 2) Aubess IR Remote
Esp8266: ESP-01M
As for the same circuitry, i will swap esp8266 with one of tuya IR remote and redo the test.
I had a similar issue. It is not related to the used MCU. This IR Blasters are all weak in sending. Just many IR diodes does not make a good transmitter. Solved the issue using a old IR Remote for sending. The IR diodes are sending with way more power since the are feed with 9v and more peak current.
PROBLEM DESCRIPTION
A clear and concise description of what the problem is.
If I try to send IR command continuously, IR signal doesn't get picked up by the target device I would need to wait at least 1-2 seconds before sending the next command.
And sometimes sending IR command doesn't work on the first attempt and I have to send the same command again
This doesn't happen on an esp8266 remote.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:Status 0
:TO REPRODUCE
1) Use a second IR remote to capture IRHVAC signal 2) Increase/decrease temperature for the AC continously (18 C to 27 C)
EXPECTED BEHAVIOUR
Some commands not received by target (unknown as indicated in the logs by ir receiver). No issues doing the same test on esp8266 remote.
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)