logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

How to Integrate Qlima Monoblock AC WBR1 with OpenBeken as Home Assistant Climate Entity?

Wara125 252 9
ADVERTISEMENT
Reply | New topic
  • #1 21605793
    Wara125
    Level 3  
    Hello everyone,

    I’ve successfully flashed my Qlima Monoblock Air Conditioner (model with Tuya JWBR2S and WBR1 Wi-Fi chip) with OpenBeken (OpenRTL87X0C firmware). After the flash, I’ve managed to get everything working using the following Tasmota parameters I found here:
    https://templates.blakadder.com/electriq_IQOOL-SMART12HP.html

    What’s working so far:
    I’ve set the air conditioner to various modes like Cooling, Drying, Fan-Only, and Heating, and configured these as fan speeds in the autoexec.bat.
    Integration with Home Assistant works through MPPT (MQTT), and I can control the unit using MQTT commands.
    However, the controls work as individual switches (cooling, heating, fan, etc.), and I’ve set up the functions as fan speed commands in the autoexec.bat file.

    The problem:
    What I’m trying to achieve is to integrate the air conditioner into Home Assistant as a Climate entity. Currently, I’ve manually created an MQTT climate entity that sends different payloads to control the AC, but it only works partially. Specifically:
    The AC cannot be turned on/off from Home Assistant.
    The AC only works as a remote controller (status updates from the physical remote don’t reflect in the Home Assistant Climate card).
    There is no feedback from the AC when settings are changed via the physical remote (the status in Home Assistant doesn’t update when I change something locally).

    My question:
    Is it possible to create a direct Climate entity from OpenBeken's autoexec.bat without needing to set it up manually in Home Assistant? Could this be done by sending the correct MQTT payloads directly from the autoexec.bat to Home Assistant to allow:
    Control of the AC’s on/off state?
    Feedback to Home Assistant when changes are made physically (e.g., via remote)?
    I’m aware that creating a custom MQTT integration or using a climate platform in Home Assistant might be the answer, but I wanted to check if it’s possible to simplify this directly from the OpenBeken firmware. Has anyone done something similar, or does anyone have suggestions on how I might go about this?

    Thanks in advance!

    Code: text Expand Select all Copy to clipboard
    startDriver TuyaMCU
tuyaMcu_defWiFiState 4

setChannelType 1 Toggle

setChannelType 2 temperature
setChannelType 3 temperature

setChannelType 4 ACmode
setChannelType 5 LowMidHigh

setChannelType 6 Toggle
setChannelType 7 Toggle

linkTuyaMCUOutputToChannel 1 bool 1

linkTuyaMCUOutputToChannel 2 int 2
linkTuyaMCUOutputToChannel 3 int 3

linkTuyaMCUOutputToChannel 4 enum 4
linkTuyaMCUOutputToChannel 5 enum 5

linkTuyaMCUOutputToChannel 101 bool 6
linkTuyaMCUOutputToChannel 104 bool 7


    Code: text Expand Select all Copy to clipboard
    mqtt:
  - climate:
      name: AIRCO
      optimistic: false
      modes:
        - "off"
        - "cool"
        - "fan_only"
        - "dry"
        - "heat"
      fan_modes:
        - "low"
        - "medium"
        - "high"
      power_command_topic: "AIRCO/1/set"
      power_command_template: >-
        {% set values = { 'off':'0', 'on':'1'} %}
        {{ values[value] if value in values.keys() else '0' }}
      mode_command_topic: "AIRCO/4/set"
      mode_command_template: >-
        {% set values = { 'cool':'0', 'fan_only':'1',  'dry':'2', 'heat':'3'} %}
        {{ values[value] if value in values.keys() else '0' }}
      temperature_command_topic: "AIRCO/2/set"
      fan_mode_command_topic: "AIRCO/5/set"
      fan_mode_command_template: >-
        {% set values = { 'low':'0', 'medium':'1',  'high':'2'} %}
        {{ values[value] if value in values.keys() else '0' }}
      swing_mode_command_topic: "AIRCO/7/set"
      swing_mode_command_template: >-
        {% set values = { 'off':'0', 'on':'1'} %}
        {{ values[value] if value in values.keys() else '0' }}
      precision: 1.0
      min_temp: 10
      max_temp: 25
      retain: true
      qos: 0


    AI: When you change settings on the AC using the physical remote, do you see any MQTT messages or state updates published by OpenBeken (for example, on status or telemetry topics)? If so, could you share some examples of those messages?
    Yes, state changes come trough in the normal individual entities, but shown as fan speeds because that was the only way to get it work in the autoexec.bat
    AI: Do you know if the TuyaMCU protocol on your specific AC model and with OpenBeken firmware supports reporting state changes (like power, mode, temperature) back to the controller when changed locally, or is it strictly one-way control from MQTT to the device?
    Yeah, temps en everything shows up nicely in the OBK website
  • ADVERTISEMENT
  • #2 21605864
    p.kaczmarek2
    Moderator Smart Home  
    What a coincidence, I've been recently looking into adding climate entities to HA! I already did similar think for this topic:
    https://www.elektroda.com/rtvforum/topic4119999.html
    However, in your case, it seems that your device is using TuyaMCU, right? And you have dpIDs more or less figured out, and you just need ability to feed it to HA?

    I see.... I think I will be happy to add this for you, actually, I've been looking for someone with AC to help me testing that.

    So, for clarity, before I begin, can you provide a bit more info on your autoexec.bat? Which temperature is target, which is current, etc? Which toggle does what? Is your device fully functional in OBK? I think we can get it fully working in OBK, and then I will add HA Discovery for you. How does it sound?
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #3 21605899
    Wara125
    Level 3  
    Wow, that’s fantastic! I’m really glad to hear you're looking into adding climate entities to Home Assistant, and I’d be happy to help with testing. Yes, my device uses TuyaMCU, and I’ve already figured out most of the dpIDs for the various functions. What I’m struggling with now is getting everything properly integrated into Home Assistant, specifically making it work as a Climate entity.

    To clarify your questions:
    All the dpIDs: 
    dpID1: Boolean Toggle AC on/off
    dpID2: Integer set temperature
    dpID3: Integer actual temperature
    dpID4: Enum Mode setting. 0= cooling 1=Fan-Only 2=Dry 3=Heat
    dpID5: enum Fan speed. 0=Low 1= medium 2=high
    dpID19: Enum sets temperature unit C or F. (0 C/1 F.)
    dpID101: Boolean Silent mode. 0= off 1= on
    dpID104: Boolean Swing mode. 0= off 1=on

    Modes: I set the modes like Cooling, Drying, Fan, Heating through fan speed settings in the autoexec.bat using The (Off)LowMedHigh setting as u see in my autoexec.bat file.

    Full Functionality in OBK: Yes, the device is fully functional in OpenBeken (OBK), What I’m really aiming for is to have the entire air conditioner work as a single Climate entity in Home Assistant, so I can control the on/off state, temperature, and mode (cooling, heating, fan) from one place, with proper feedback to the interface.
    All the individual MQTT controls are functional, but I’m looking for a way to merge them into a single integrated entity that combines everything for easier control.


    Screenshot showing air conditioner settings in the OpenBeken app with dpID values for climate functions.

    Actually, this device is a white label product, which means it’s sold under several different brands. Some of the brands that sell this same unit include Qlima, electriQ, Trotec, AirExchange, Profile, Maxxhome, and Fintek.
    These units are typically referred to as Monoblock or Wall Mounted Air Conditioners.
    I thought that might be helpful context, in case you’re looking into firmware for similar devices.

    Let me know if you need any additional details from my side.
  • #4 21605952
    divadiow
    Level 34  
    thanks for the custom read of Tuya config section from 0x1D5000. It was still in tact.

    from that we can get
    Code: Text
    Log in, to see the code


    Added after 13 [minutes]:

    if this image/name is correct

    How to Integrate Qlima Monoblock AC WBR1 with OpenBeken as Home Assistant Climate Entity?

    then I believe the full dpID list to be
    Code: JSON
    Log in, to see the code
  • ADVERTISEMENT
  • #5 21605964
    Wara125
    Level 3  
    The actual model is:
    Qlima Monoblock 229 PTC.

    How to Integrate Qlima Monoblock AC WBR1 with OpenBeken as Home Assistant Climate Entity?
    The PTC Heating element function only works via IR or Local control I read somewhere.
  • Helpful post
    #6 21607906
    p.kaczmarek2
    Moderator Smart Home  
    I've started AC wrapper for TuyaMCU. It's not hard, but it's time consuming. It's not ready for testing, but if you want, you can view code here:
    https://github.com/openshwprojects/OpenBK7231T_App/pull/1720
    Helpful post? Buy me a coffee.
  • #7 21607997
    Wara125
    Level 3  
    Thanks so much for your work on the AC on TuyaMCU! I really appreciate the time and effort you're putting into it. Looking forward to testing it once it's ready.
    Let me know if you need any feedback or help during the process!
  • ADVERTISEMENT
  • #8 21607998
    p.kaczmarek2
    Moderator Smart Home  
    Sure, I will request some testing later, but most of the testing will be done on my side,in Windows simulator. It's just that HA expects hardcoded values and I will probably have to map them by hand or add new channel types...

    Added after 1 [minutes]:

    Btw what is that?
    Code: text Expand Select all Copy to clipboard
    
setChannelType 4 ACmode

    We don't have such channel type yet, do we? I think I need to add one like that.
    Helpful post? Buy me a coffee.
  • #9 21608010
    Wara125
    Level 3  
    Oh you can ignore that. That is obviously not working. I have set that one up with OffLowMediumHigh now.
    It needs to send a payload of 0 to 3 for each mode. I read ACmode somewhere in a different driver config so I tried it at some point.
  • #10 21608018
    p.kaczmarek2
    Moderator Smart Home  
    No no, it's actually useful. It will act like a bridge between TuyaMCU and HA. I will add such channel type later and reply here.

    Basically we need to cover those dpIDs with channel types and later I will forward them to HA
    Helpful post? Buy me a coffee.
Reply | New topic
Report a violation of the law

Topic summary

A user has successfully flashed a Qlima Monoblock Air Conditioner (model 229 PTC with Tuya JWBR2S and WBR1 Wi-Fi chip) using OpenBeken (OpenRTL87X0C firmware) and configured it with Tasmota parameters for basic control via MQTT in Home Assistant (HA). The device uses TuyaMCU with identified dpIDs for functions such as power toggle, set temperature, actual temperature, mode selection (cooling, fan-only, dry, heat), fan speed, temperature unit, silent mode, and swing mode. The user currently controls the AC through individual MQTT switches and fan speed commands scripted in autoexec.bat but aims to integrate it as a unified Climate entity in HA. A community member offered assistance to enhance integration by adding HA Discovery support and requested detailed information about the autoexec.bat configuration and dpID usage. The user confirmed full functionality in OpenBeken and shared dpID mappings and mode settings. It was noted that the PTC heating element operates only via IR or local control. Additional technical details were extracted from the Tuya configuration memory section, supporting further development of the integration.
Summary generated by the language model.
Popular Topics
ADVERTISEMENT