-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
IRSend Issues Greater than 32bits #8938
Comments
Sending IR messages is supposed to work up to 64 bits. Since the I suggest you open an issue here: https://github.com/crankyoldgit/IRremoteESP8266 Can you also give more data about the PIONEER issue? |
Thanks for the response. Will create an issue there as well. For Pioneer, example commands: From Tasmota-sent command: |
Updated above comment with full Pioneer commands |
Change IRRemoteESP8266 IR lib to pre-2.7.9, fixing Samsung and Pioneer protocols (#8938)
Change IRRemoteESP8266 library from v2.7.6 to v2.7.8.10, fixing Samsung and Pioneer protocols (#8938)
PROBLEM DESCRIPTION
A clear and concise description of what the problem is.
Using Tasmota 8.3.1, with both an ircustom.bin and ir.bin firmware files.
I have noticed that when sending IR messages greater than 32 bits (Samsung36 or Pioneer), the end device is unable to read the message.
Interestingly, another Tasmota device is able to read/decode the message successfully.
If I change SetOption57 to 1 and then send the RAW IR command via IRSend, the command is successfully read by the end device (and a second Tasmota device reads/decodes this message the same as the first one)
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
:(Please use
weblog 4
for more debug information)TO REPRODUCE
Steps to reproduce the behavior:
Example below is the MUTE command from a Samsung Sound Bar. Also experience similar with Pioneer devices.
Capture IR command from Samsung/Pioneer remote
Example capture from original remote:
{"IrReceived":{"Protocol":"SAMSUNG36","Bits":36,"Data":"0x0CF008E71","DataLSB":"0x0F300718E","Repeat":0,"RawData":[4544,4458,500,498,500,500,496,496,500,498,500,1464,530,1464,522,502,494,502,496,1470,524,1470,504,1464,522,1476,520,500,496,500,498,500,498,498,500,4460,530,492,494,504,496,500,496,500,496,1472,524,500,498,498,500,498,468,1474,522,1472,524,1470,526,498,500,498,500,1468,528,1466,530,1464,500,524,474,498,500,500,498,1466,530],"RawDataInfo":[77,77,0]}}
Send IR command via IRSend:
IRSend {"Protocol":"SAMSUNG36","Bits":36,"Data":"0x0CF008E71","DataLSB":"0x0F300718E","Repeat":0}
Note the device does not interpret the message (although another Tasmota device will). Note the RAW data is different to what is received from the initial capture.
Tasmota Device receives the following:
tele/tasmota_4EEF64/RESULT = {"IrReceived":{"Protocol":"SAMSUNG36","Bits":36,"Data":"0x0CF008E71","DataLSB":"0x0F300718E","Repeat":0,"RawData":[4456,4508,568,550,602,532,576,562,578,542,632,1616,578,1674,620,500,596,530,600,1654,630,1618,622,1626,568,1678,628,494,602,524,594,532,598,534,596,4480,596,530,600,528,602,526,604,524,596,1652,600,528,602,526,604,524,596,1656,626,1616,602,1646,604,522,596,532,598,1648,602,1652,630,1610,594,532,598,530,600,528,602,1644,604],"RawDataInfo":[77,77,0]}}
Send IR Raw Command (that works from initial capture):
Irsend 0,4544,4458,500,498,500,500,496,496,500,498,500,1464,530,1464,522,502,494,502,496,1470,524,1470,504,1464,522,1476,520,500,496,500,498,500,498,498,500,4460,530,492,494,504,496,500,496,500,496,1472,524,500,498,498,500,498,468,1474,522,1472,524,1470,526,498,500,498,500,1468,528,1466,530,1464,500,524,474,498,500,500,498,1466,530
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
The device should be able to read/decode the message when sent via IRSend, based on what it receives from IrReceived, without needing to encode RAW messages.
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
N/A
ADDITIONAL CONTEXT
Add any other context about the problem here.
It is worth noting that all 32 bit commands captured/resent appear to work fine. IRHvac commands also seem fine - just IRSend messsages >32 bits that dont.
Sample known bad commands:
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: