Mirabella Genio IR controller (Kmart) integration

Hardware
1

Just finished setting up Mirabella Genio IR controller from Kmart and flashed using OTA Tuya-Convert.

Here is a quick how-to for anyone wondering:

Follow https://github.com/ct-Open-Source/tuya-convert to flash the device using the default tasmota firmware. Later you will upgrade it to the latest version.

Find latest version of tasmota-ir.bin firmware from http://thehackbox.org/tasmota/release/. tasmota-ir has the complete IR code for most devices. Follow OTA upgrade to flash the device (https://tasmota.github.io/docs/#/Upgrading)

Apply https://templates.blakadder.com/mirabella_genio_I002577.html template (https://tasmota.github.io/docs/#/Templates)

Configure the MQTT and the device is ready.

Below you can find the snippet from my configuration.yml and automation triggers. I followed the technique discussed here Enhanced version of MQTT HVAC (Climate platform) with proper History Chart

# configuration.yml
climate:
  - platform: mqtt
    name: "Living room"
    modes:
      - "off"
      - "cool"
      - "heat"
      - "fan_only"
    fan_modes:
        - "Auto"
        - "Min"
        - "Low"
        - "Med"
        - "High"
        - "Max"
    power_command_topic: "ac/power/hvac"
    mode_command_topic: "ac/mode/hvac"
    fan_mode_command_topic: "ac/fan/hvac"
    temperature_command_topic: "ac/temperature/hvac"

I am using Mitsubishi split AC. To find your device IR code, open Tasmota console in the WebUI, point your remote to the device and press a button. If your device is compatible, you will see the IR code. Find out more at https://github.com/arendst/Tasmota/wiki/Tasmota-IR

# automation.yml
- id: '1579216888278'
  alias: AC power controller
  description: 'Custom MQTT message to send to IR Transceiver '
  trigger:
  - platform: mqtt
    topic: ac/power/hvac
  condition: []
  action:
  - data_template:
      payload: '{"Vendor":"Mitsubishi_Heavy_152", "Power":"On"}

        '
      topic: smartir/cmnd/irhvac
    service: mqtt.publish
- id: '1579259449046'
  alias: AC mode change
  description: ''
  trigger:
  - platform: mqtt
    topic: ac/mode/hvac
  condition: []
  action:
  - data_template:
      payload: '{"Vendor":"Mitsubishi_Heavy_152", "Power": "On", "Mode": "{{ trigger.payload
        }}" }

        '
      topic: smartir/cmnd/irhvac
    service: mqtt.publish
- id: '1579260073284'
  alias: AC change temperature
  description: ''
  trigger:
  - platform: mqtt
    topic: ac/temperature/hvac
  condition: []
  action:
  - data_template:
      payload: '{"Vendor":"Mitsubishi_Heavy_152", "Power": "On", "Temp": {{ trigger.payload
        }} }

        '
      topic: smartir/cmnd/irhvac
    service: mqtt.publish
- id: '1579260228395'
  alias: AC change fan speed
  description: ''
  trigger:
  - platform: mqtt
    topic: ac/fan/hvac
  condition: []
  action:
  - data_template:
      payload: '{"Vendor":"Mitsubishi_Heavy_152", "Power": "On", "FanSpeed": "{{ trigger.payload
        }}" }

        '
      topic: smartir/cmnd/irhvac
    service: mqtt.publish

Update July 2020:
Added temperature reading from another sensor. See Google Assistant working with sensors?

7 Likes
2

Thanks for the detailed instructions, excited to see it’s possible.

Unfortunately when I tried to upload the tasmota-ir firmware it failed with “upload buffer miscompare”.
Just checking your device was model HKWL-IR02W ?

3

@ChickenLittle…
If the tasmota-ir package didn’t load straight away, try the same version tasmota-minimal first. If this works, then try the ir again. It should work a treat.

4

I bought one of these today. Unfortunately the flashing failed. The supplied firmware must have been updated :sob:

5

I just bought one today - did you get anywhere with it? I’m tempted to try this guide to see if I can get it into esphome, but thought I’d check before going to the effort.

6

I can confirm I successfully flashed ESPHome onto this device using the ESPHome online application as of 27/07/24.

I used a CH340G USB to TTL device, used the original power supply for the IR Blaster, grounded IO0, connected Tx & Rx and attached ground from the CH340G to the IR blaster board.

FWIW - My board had v1.1 written on it.

Only things that caught me up was that my particular CH340G board had a UART and PROG switch.
Switched between those until it worked.

The ESP8266 chip is a TYWE3S variant. I don’t think you can lock these down via firmware.

Hopefully this helps someone out! Took a couple of days to get it sorted.