Device Description
Device: Xiaomi Smart TV (Remote Model: Standard IR/Bluetooth Hybrid)
Firmware: Tasmota v15.2.0 (or latest) on ESP32
Library Version: Latest Tasmota-IRHVAC
Problem Description
I am trying to integrate my Xiaomi TV into Home Assistant using a Tasmota-flashed ESP32 IR Blaster. While the receiver captures the signal, it is identified as Protocol: UNKNOWN with a consistent bit length of 84 bits.
Since Xiaomi TV is a very popular device, having native support for this specific 84-bit protocol (likely a variant of XMP or a proprietary Xiaomi encoding) would be highly beneficial for the community.
Captured Data (Tasmota Console)
When pressing the Power button on the remote, the console returns:
JSON
03:07:07.416 MQT: tele/tasmota_82ED70/RESULT = {"IrReceived":{"Protocol":"UNKNOWN","Bits":84,"Hash":"0xF6521CD8","Repeat":0}}
Raw Data (Captured with Sensor29 1)
Please replace the example below with your actual RawData from the Tasmota Console:
JSON
{"IrReceived":{"Protocol":"UNKNOWN","Bits":84,"RawData":[4500,4450,600,1650,600,550,600,1650,600,550,600,550,600,1650,600,550,600,550],"RawDataInfo":[171,171,0]}}
Attempts to Resolve
Tried sending via IRSend {"Protocol":"UNKNOWN","Bits":84,"Data":"0xF6521CD8"}, but Tasmota rejects the UNKNOWN protocol string.
Tried forcing Protocol":"XMP", but the timing seems slightly off for this specific 84-bit implementation.
Successfully controlled the TV using IRSend 0,raw_data..., but this is difficult to manage for complex HVAC-like integrations or mapping multiple buttons in Tasmota-IRHVAC.
Expected Behavior
Ideally, this 84-bit protocol should be recognized natively (e.g., as XIAOMI_TV or similar), allowing users to easily map buttons like Power, Volume, and Source within the Tasmota-IRHVAC component.
Device Description
Device: Xiaomi Smart TV (Remote Model: Standard IR/Bluetooth Hybrid)
Firmware: Tasmota v15.2.0 (or latest) on ESP32
Library Version: Latest Tasmota-IRHVAC
Problem Description
I am trying to integrate my Xiaomi TV into Home Assistant using a Tasmota-flashed ESP32 IR Blaster. While the receiver captures the signal, it is identified as Protocol: UNKNOWN with a consistent bit length of 84 bits.
Since Xiaomi TV is a very popular device, having native support for this specific 84-bit protocol (likely a variant of XMP or a proprietary Xiaomi encoding) would be highly beneficial for the community.
Captured Data (Tasmota Console)
When pressing the Power button on the remote, the console returns:
JSON
03:07:07.416 MQT: tele/tasmota_82ED70/RESULT = {"IrReceived":{"Protocol":"UNKNOWN","Bits":84,"Hash":"0xF6521CD8","Repeat":0}}
Raw Data (Captured with Sensor29 1)
Please replace the example below with your actual RawData from the Tasmota Console:
JSON
{"IrReceived":{"Protocol":"UNKNOWN","Bits":84,"RawData":[4500,4450,600,1650,600,550,600,1650,600,550,600,550,600,1650,600,550,600,550],"RawDataInfo":[171,171,0]}}
Attempts to Resolve
Tried sending via IRSend {"Protocol":"UNKNOWN","Bits":84,"Data":"0xF6521CD8"}, but Tasmota rejects the UNKNOWN protocol string.
Tried forcing Protocol":"XMP", but the timing seems slightly off for this specific 84-bit implementation.
Successfully controlled the TV using IRSend 0,raw_data..., but this is difficult to manage for complex HVAC-like integrations or mapping multiple buttons in Tasmota-IRHVAC.
Expected Behavior
Ideally, this 84-bit protocol should be recognized natively (e.g., as XIAOMI_TV or similar), allowing users to easily map buttons like Power, Volume, and Source within the Tasmota-IRHVAC component.