Replies: 3 comments 6 replies
-
There could be multiple reasons for unreliable reception of IR signal 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. |
Beta Was this translation helpful? Give feedback.
-
Sorry, i don't have oscilloscope H/w tested: Esp32 (Came with beken chip, I swapped with esp32-c3-05) Esp8266: As for the same circuitry, i will swap esp8266 with one of tuya IR remote and redo the test. |
Beta Was this translation helpful? Give feedback.
-
I had a similar issue. It is not related to the used MCU. This IR Blasters are all weak in sending. |
Beta Was this translation helpful? Give feedback.
-
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
:Backlog Rule1; Rule2; Rule3
:Status 0
:weblog
to 4 and then, when you experience your issue, provide the output of the Console log:TO REPRODUCE
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)
Beta Was this translation helpful? Give feedback.
All reactions