Protocol Unknown when receiving from Trane Runtru (GREE) HVAC or its remote but works when sending commands to it

[SylvainGa]

This is a somewhat duplicate of this post in Tasmota Git.

Pressing the iFeel button brought this:

08:31:10.478 MQT: tele/HVAC-IR/RESULT = {"IrReceived":{"Protocol":"GREE","Bits":64,"Data":"0x1C06605000C40080","Repeat":0,"IRHVAC":{"Vendor":"GREE","Model":"YAW1F","Command":"Control","Mode":"Heat","Power":"On","Celsius":"On","Temp":22,"FanSpeed":"Min","SwingV":"Auto","SwingH":"Off","Quiet":"Off","Turbo":"Off","Econo":"Off","Light":"On","Filter":"Off","Clean":"Off","Beep":"Off","Sleep":-1,"iFeel":"On","SensorTemp":null}}}
08:31:10.718 MQT: tele/HVAC-IR/RESULT = {"IrReceived":{"Protocol":"UNKNOWN","Bits":18,"Hash":"0x85963258","Repeat":0}}

(So it's a GREE unit).
Pressing Temperature increase brought this:

08:33:20.464 MQT: tele/HVAC-IR/RESULT = {"IrReceived":{"Protocol":"UNKNOWN","Bits":140,"Hash":"0x3676B741","Repeat":0}}
08:33:20.679 MQT: tele/HVAC-IR/RESULT = {"IrReceived":{"Protocol":"UNKNOWN","Bits":18,"Hash":"0x85963258","Repeat":0}}

Pressing Temperature decrease brought this:

08:33:26.640 MQT: tele/HVAC-IR/RESULT = {"IrReceived":{"Protocol":"UNKNOWN","Bits":140,"Hash":"0xFC5A8347","Repeat":0}}
08:33:26.804 MQT: tele/HVAC-IR/RESULT = {"IrReceived":{"Protocol":"UNKNOWN","Bits":18,"Hash":"0x85963258","Repeat":0}}

Waiting around 10 minutes (believed intervals between iFeel reports) brought this:

08:41:09.892 MQT: tele/HVAC-IR/RESULT = {"IrReceived":{"Protocol":"UNKNOWN","Bits":18,"Hash":"0xB35C26D7","Repeat":0}}

Same for 10 minutes later

08:51:09.976 MQT: tele/HVAC-IR/RESULT = {"IrReceived":{"Protocol":"UNKNOWN","Bits":18,"Hash":"0xB35C26D7","Repeat":0}}

So, looks like the "Bits":140 are the temperature increase/decrease commands and the "Bits":18 are the iFeel response from the remote. However, sending "Command": "iFeel Report", "SensorTemp": "18" to the head unit actually shuts down the head unit, so maybe it's using another way or reporting back (especially since my IR Receiver it can't decode what it receives from the remote)? Beside that 'hash', is there a way to view the raw data received? I know I can send 'raw data' but I want the receive, view the received raw data.

Thanks.

[NiKiZe]

There is a issue template which you seem to have ignored and deleted? It brings up several parts that you mention, with links to FAQ with explanations.
It also contains information on how to collect the data.

For ACs it's uncommon to see any up/down commands, it has state. Except for some protocols which instead of having on/off states instead has toggles.

[SylvainGa]

? I don't see any templates when creating a Q/A. Do you have that link?

[NiKiZe]

I'm sorry, I got the feeling this was an issue.
I do apologise! You can start opening an issue and you will get the template, otherwise do read thru the FAQ.

[SylvainGa]

Found how to do it. See arendst/Tasmota#24281 (comment)

It would be nice if this GREE iFeel protocol for a model YAW1F be included in this lib so others can benefit from it. Although I've worked with other Arduino libs in the past, my knowledge here isn't enough and to include it myself, it would take quite a lot of my time. So if someone with more knowledge here want to implement it, see that post I link. It has the detail on how to make it work. It's pretty simple. The payload is the temperature (in Celsius) in a 8bit format (LSB first) followed by another byte with value 0xA5. That's it.

[NiKiZe]

As explained in faq as well, raw data from original remote and which bits maps to what.
But also how to distinguish remotes with this support compared to others.