Support for Mitsubishi Heavy 88

[Wihanh]

Mitsubishi Heavy 88 Protocol as supported in Tasmota IR does not seem to work.

Firmware:

• version 1.18.298_irRemoteESP
• Generic Tuya IR Tranceiver
• Chip/model: BK7231N
• Device config IR Receive pin 8, transmit pin7, btn 9, wifi led 24

To Reproduce
Steps to reproduce the behavior:
I have not yet tested transmit, since I can't really since the library seems unsupported, or at least not working for me.
IR receive give me unknown IR in the logs
Info:IR:IR Unknown ffffffff,0x35AF8AB3,90
Info:MQTT:Publishing val {"IrReceived":{"Protocol":"UNKNOWN","Bits":90,"Data":"0x35AF8AB3"}} to obk1EFC1DF9/RESULT retain=0

This same AC works fine on Tasmota IR with Mitsubishi Heavy 88 as the protocol - bidirectional

Primary reason for the Bug Report is to check if this is known, and if so to offer any assistance where possible to make it work. If anyone else has it working feel free to share

[Wihanh]

Title: MITSUBISHIHEAVY88 decoder present in source but never matches — consistently returns "Unknown"

Firmware: 1.18.298_irRemoteESP, BK7231N, board generic-bk7231n-qfn32-tuya
Pins: IRSend:7, IRRecv:8, Btn:9, WifiLED:24
AC: Mitsubishi Heavy Industries — worked previously via Tasmota's tasmota_irhvac, protocol MITSUBISHI_HEAVY_88

Behavior: Pressing remote buttons (temp up/down, off) consistently produces clean 90-bit captures with a distinct hash per distinct action (not noise/garbage) — but always logs as Unknown, e.g.:

Info:IR:IR Unknown ffffffff,0x6D54E175,90
Info:IR:IR Unknown ffffffff,0x21050E98,90

Ran IREnable MITSUBISHIHEAVY88 1 (returns OK) with no change. Confirmed the Mitsubishi Heavy source files are present in the repo. Is this protocol actually wired into the receive-decode dispatch for this build variant, or is something else needed to activate it?

[divadiow]

Try this when it finishes building https://github.com/divadiow/OpenBK7231T_App/actions/runs/29851670272

[Wihanh]

Flashed with: OpenBK7231N_irremotesp8266_290_c0134bba5f46_irRemoteESP.rbl
however the protocol still shows as unknown:

Info:MAIN:Time 114, idle 18682/s, free 39424, MQTT 1(1), bWifi 1, secondsWithNoPing 25, socks 4/38 
Info:MAIN:Time 115, idle 17395/s, free 62824, MQTT 1(1), bWifi 1, secondsWithNoPing 26, socks 2/38 
Info:MAIN:Time 116, idle 16041/s, free 62824, MQTT 1(1), bWifi 1, secondsWithNoPing 27, socks 2/38 
Info:MAIN:Time 117, idle 13243/s, free 51120, MQTT 1(1), bWifi 1, secondsWithNoPing 28, socks 3/38 
Info:IR:IR Unknown ffffffff,0x76AE37E9,90
Info:MQTT:Publishing val ffffffff,0x76AE37E9,90 to obk1EFC1DF9/ir/get retain=0
Info:IR:IR MQTT publish IR Unknown ffffffff,0x76AE37E9,90 took 5ms
Info:MQTT:Publishing val {"IrReceived":{"Protocol":"UNKNOWN","Bits":90,"Data":"0x76AE37E9"}} to obk1EFC1DF9/RESULT retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obk1EFC1DF9/ir/get
Info:MAIN:Time 118, idle 16895/s, free 51120, MQTT 1(1), bWifi 1, secondsWithNoPing 29, socks 3/38 
Info:MAIN:Time 119, idle 19803/s, free 62608, MQTT 1(1), bWifi 1, secondsWithNoPing 30, socks 3/38 
Info:MAIN:Time 120, idle 18219/s, free 51120, MQTT 1(1), bWifi 1, secondsWithNoPing 31, socks 3/38 
Info:GEN:dhcp=0 ip=10.10.10.33 gate=10.10.10.1 mask=255.255.255.0 mac=bc:35:1e:fc:1d:f9
Info:GEN:sta: 1, softap: 0, b/g/n
Info:GEN:sta:rssi=-39,ssid=IOT,bssid=d6:01:c3:bb:92:c2,channel=12,cipher_type:CCMP
Info:MAIN:Time 121, idle 15874/s, free 62824, MQTT 1(1), bWifi 1, secondsWithNoPing 32, socks 2/38 
Info:MAIN:Time 122, idle 17760/s, free 51120, MQTT 1(1), bWifi 1, secondsWithNoPing 33, socks 3/38 
Info:MAIN:Time 123, idle 17739/s, free 62824, MQTT 1(1), bWifi 1, secondsWithNoPing 34, socks 2/38 
Info:MAIN:Time 124, idle 18079/s, free 51120, MQTT 1(1), bWifi 1, secondsWithNoPing 35, socks 3/38 
Info:IR:IR Unknown ffffffff,0xE769EC0C,90
Info:MQTT:Publishing val ffffffff,0xE769EC0C,90 to obk1EFC1DF9/ir/get retain=0
Info:IR:IR MQTT publish IR Unknown ffffffff,0xE769EC0C,90 took 9ms
Info:MQTT:Publishing val {"IrReceived":{"Protocol":"UNKNOWN","Bits":90,"Data":"0xE769EC0C"}} to obk1EFC1DF9/RESULT retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic obk1EFC1DF9/ir/get
Info:MAIN:Time 125, idle 15055/s, free 62824, MQTT 1(1), bWifi 1, secondsWithNoPing 36, socks 2/38 
Info:MAIN:Time 126, idle 17735/s, free 51120, MQTT 1(1), bWifi 1, secondsWithNoPing 37, socks 3/38 
Info:MAIN:Time 127, idle 16085/s, free 51120, MQTT 1(1), bWifi 1, secondsWithNoPing 38, socks 3/38 

Would I have to set anything other than the receiver pin for the IR sensor? Working under the assumption that the IR Receive pin is correct, since I am getting the IR Unkown when I use the remote, just that protocol is not implemented or understood?

[Wihanh]

I did notice the file at: https://github.com/openshwprojects/OpenBK7231T_App/blob/main/src/libraries/IRremoteESP8266/src/IRremoteESP8266.h
does contain MITSUBISHI_HEAVY_88, but not sure if it has been entirely built, or ported over or it if is still WIP.

[Wihanh]

more info, not sure if useful. On ESPHome I managed to get transmit to work with Mitubishi Heavy ZJ, receive however still does not work.
raw ir dumps from esphome:

`Power on, cool, 24c:
18:53:53
[I]
[remote.raw:026]
Received Raw: 3094, -1625, 374, -438, 343, -1219, 375, -437, 344, -437, 375, -1219, 375, -406, 375, -1218, 375, -437, 344, -438, 343, -1250, 344, -1218, 375, -1219, 375, -437, 344, -1218, 375, -437, 375, -1187, 407, -1187, 406, -1187, 375, -437, 375,
18:53:53
[I]
[remote.raw:026]
-406, 375, -438, 343, -438, 374, -1188, 406, -1187, 375, -437, 375, -1187, 375, -1220, 374, -437, 375, -406, 649, -913, 406, -440, 341, -438, 375, -1187, 375, -437, 375, -437, 344, -1187, 406, -1187, 406, -406, 375, -1187, 406, -1188, 375, -1218, 375,
18:53:53
[I]
[remote.raw:026]
-437, 375, -437, 344, -1187, 406, -1188, 406, -1187, 375, -437, 375, -1187, 375, -437, 375, -1188, 406, -1187, 375, -437, 375, -406, 375, -437, 344, -1219, 375, -437, 375, -1187, 375, -1219, 374, -1219, 375, -443, 338, -1228, 372, -1180, 406, -1187,
18:53:53
[I]
[remote.raw:026]
407, -1201, 361, -437, 375, -406, 375, -437, 375, -1187, 375, -438, 375, -406, 375, -406, 375, -437, 375, -406, 375, -1218, 375, -1187, 406, -406, 375, -411, 370, -438, 375, -406, 375, -1219, 375, -1190, 403, -437, 344, -406, 406, -1187, 375, -1219,
18:53:53
[I]
[remote.raw:035]
375, -1187, 406, -1187, 406, -406, 375

Power off:
18:54:12
[I]
[remote.raw:026]
Received Raw: 3095, -1624, 375, -437, 344, -1218, 375, -438, 343, -438, 375, -1218, 344, -437, 375, -1218, 375, -406, 396, -417, 343, -1242, 352, -1218, 375, -1219, 375, -406, 375, -1218, 375, -438, 343, -1219, 375, -1218, 375, -1218, 344, -437, 375,
18:54:12
[I]
[remote.raw:026]
-438, 375, -406, 374, -407, 406, -1187, 406, -1187, 375, -406, 406, -1188, 374, -1219, 375, -406, 406, -406, 375, -1187, 407, -406, 375, -406, 375, -1218, 375, -406, 406, -406, 375, -1187, 406, -1187, 406, -406, 375, -1188, 406, -1187, 375, -1218,
18:54:12
[I]
[remote.raw:026]
375, -406, 406, -407, 374, -1188, 406, -1187, 375, -1218, 375, -406, 406, -1187, 375, -406, 407, -1187, 406, -1187, 375, -406, 406, -407, 375, -406, 377, -1216, 375, -406, 406, -1187, 375, -1219, 374, -1187, 407, -406, 375, -1218, 375, -1187, 407,
18:54:12
[I]
[remote.raw:026]
-1187, 406, -1187, 375, -406, 406, -406, 375, -406, 375, -1218, 375, -407, 406, -406, 375, -406, 375, -406, 406, -406, 375, -1188, 406, -1187, 406, -1187, 375, -406, 406, -407, 375, -406, 375, -1218, 375, -1218, 376, -405, 375, -406, 407, -406, 402,
18:54:12
[I]
[remote.raw:035]
-1191, 391, -1171, 406, -1187, 375, -437, 375`

I have read somewhere the timing of the received signal is handled differently on Beken, and it may be why transmit works, but not recieve, at least on ESPHome, not sure if the issue is similar on this platform.

[divadiow]

hmm interesting. as far as I can tell the irremoteesp8266 library contains the full support for Mitsubishi Heavy 88.
I missed a load of fixes out of the run in the link above so here's a new one https://github.com/divadiow/OpenBK7231T_App/actions/runs/29897401798

no idea if it'll be any better.

fixes ref: #2167 (comment)

[DeDaMrAzR]

OpenBK7231N_IR_rework_ISR_1.zip

Test OTA file is attached, I need comments and feedback,

Suggested use is to increase tolerance to 30-40% and see if the new learn remote is going to decode that protocol.

Info:IR:IR learning started timeout=60s tolerance=40%
Info:IR:IR edge frame rawlen=180 edges=180 protocol=MITSUBISHI_HEAVY_88 expected=AUTO expected_ok=1 same=2 overflow=0
Info:IR:IR learned command: IRSendState MITSUBISHI_HEAVY_88,AD513CD92610EF08F7D12E
Info:IR:Received AC code:MITSUBISHI_HEAVY_88
Info:IR:IR learning started timeout=60s tolerance=40%
Info:IR:IR edge frame rawlen=180 edges=180 protocol=MITSUBISHI_HEAVY_88 expected=AUTO expected_ok=1 same=2 overflow=0
Info:IR:IR learned command: IRSendState MITSUBISHI_HEAVY_88,AD513CD92610EF08F7D12E
Info:IR:Received AC code:MITSUBISHI_HEAVY_88

[Wihanh]

Sorry, I have been slack. I will test it this weekend.

[divadiow]

hmm. I've seen my Sherwood 6095RDS amp's remote give 'EPSON' readings before, maybe it was with the problematic BK7238 mostly recently, or also actually with BK7231N in the past, anyway the ISR build is always showing it to be Epson.

the power button should be Info:IR:IR IR_NEC 0x4583 0x11 0 (32 bits)

(seen here https://www.elektroda.com/rtvforum/topic4031123.html)

I am testing ISR build with this same device

[DeDaMrAzR]

@divadiow any change if you lower or increase tolerance percentage?

[divadiow]

Give the latest build from this PR a go #2194

Please post feedback in that pr