Broadlink AC Integration (AC Freedom) (AUX, Dunham, Rcool, Akai, Rinnai, Kenwood, Tornado, Ballu)

[powerhosting]

Could you please provide me a guide on this one? I tried to add it, but I failed though I might doing something wrong.

[Artem_Vladimirov]

1. Rename Wi-Fi to have a different name for the 2.4Ghz and 5 Ghz network. Or turn off the 5 Ghz mode in the router settings. It is very nice important. Broadlink works only with the 2.4Ghz network.
2. Switch the air conditioner to pairing mode (I had to press the health button 8 times).
3. Go to the application, click on the add device button.
4. Enter the Wi-Fi network name and password.
5. Click the setup button

[tomaszhiterski]

Hi

I try to connect my AUX conditioner to AC MQTT proxy for HA , I set mac number, IP with port ,but still it don’t connect:

What is strange Mosquito broker log show that something try to connect but it is completly different IP:

I turn off 5 Ghz wifi.

[Oscar_Calvo]

I have 2 new AC units, it seems that port 80 is closed.
How do I open this port?
Do I need to send these units back?

[Oscar_Calvo]

Will this work to open port 80 on the device?

[Artem_Vladimirov]

In home assistant the configuration schema was changed, update it in configuration.yaml to a new version. Or just delete it in the config file and use auto discovery mode in this script (discovery: true)

[snhnic]

This is making me grazy. I deleted the app from AC Freedom, took me almost 3 hours to figure out I had to stop OFDMA in my router. After switching off OFDMA in the router I got the device back on the app. DHCP to get a fixed IP for the airco and started AC MQTT proxy for home assistant.Withbelow result

Starting Monitor…
Authentication Failed to AC
init() should return None, not ‘bool’

[kispee]

I can’t install the add-on.
I click install and it write this:

What is the problem?
Thanks.

[OsaedYahya]

This is my configuration
Am I missing something?

[OsaedYahya]

Even though this is not starting with Broadlink or whatever but it’s the same mac from theAcFreedom app

[OsaedYahya]

This is after I logged every command in the python file for the old integration,
it times out

[andremain]

This is mine.

[Artem_Vladimirov]

I developed a new version of this integrationa and created a new topic for it.

Broadlinkac2mqtt - Control your broadlink-based air conditioner with Home Assistant

Star the project on github if you like it and support me! I am pleased to present you a new version of the application for controlling air conditioners on the broadlink chipset. The main reason for the appearance of this project is that the author of a similar project has stopped releasing updates. In addition, there were small errors in that project that did not give me peace of mind, so I decided to completely rewrite this project for myself. Small application size (~10.2 Mb docker,…

[Rudoxxxx]

Hello! How we can run in Windows with Oracle VM virtual box and Home Assistant on this machine?

[CREart (Ahmad)]

Any luck guys, I just bought 4 ACs and got them work in AC Freedom app but not in HA.

I am using the latest version of freedom app, tried the suggestion to use version 1.3.0 with no luck. I am running the latest home assistant OS version.

Home Assistant: 2023.5.4
Supervisor: 2023.04.1
Operating System: 10.2
Frontend 20230503.3 - latest

[earvingad]

I would recommend using the integration developed by @Artem_Vladimirov

[CREart (Ahmad)]

I tried it with no luck, I also followed the Broadlink AC Integration (AC Freedom), but it does not work.

Can some one put me in the right direction?

[earvingad]

Do you have installed the MQTT server? you need it in order to control de ACs with HA. The MQTT server will act similar as a “man in the middle” for communication.

[CREart (Ahmad)]

Of course I have one inside home assistant and it is working well, I have several tasmota devices and ESPHome ones too. the issue seems to be authentication failure.

I got this from the new app called “broadlinkac2mqtt” https://github.com/ArtemVladimirov/broadlinkac2mqtt

{"level":"debug","time":"2023-06-04T00:08:44+03:00","caller":"/github/workspace/config/config.go:47","message":"Start reading a config file"}
{"level":"info","time":"2023-06-04T00:08:44+03:00","caller":"/github/workspace/app/mqtt/mqtt.go:42","message":"Connected to MQTT"}
{"level":"debug","payload":"online","topic":"homeassistant/status","time":"2023-06-04T00:08:44+03:00","caller":"/github/workspace/app/mqtt/subscriber/subscriber.go:112","message":"new home assistant LWT message"}
{"level":"debug","input":{"Mac":"ec0bae13111a"},"time":"2023-06-04T00:08:44+03:00","caller":"/github/workspace/app/repository/cache/cache.go:106","message":"device not found in cache"}
{"level":"debug","input":{"Mac":"ec0bae13111a"},"time":"2023-06-04T00:08:44+03:00","caller":"/github/workspace/app/repository/cache/cache.go:91","message":"ambient temperature not found in cache"}
{"level":"error","input":{"Mac":"ec0bae13111a"},"time":"2023-06-04T00:08:44+03:00","caller":"/github/workspace/app/repository/cache/cache.go:185","message":"device availability is not found in cache"}
{"level":"error","input":{"Mac":"ec0bae13111a"},"device":"ec0bae13111a","time":"2023-06-04T00:08:44+03:00","caller":"/github/workspace/app/service/service.go:1234","message":"failed to read the device availability"}
{"level":"error","error":"ErrorDeviceNotFound","input":{"Status":"online"},"time":"2023-06-04T00:08:44+03:00","caller":"/github/workspace/app/mqtt/subscriber/subscriber.go:120","message":"failed to get states"}
{"level":"error","error":"read udp 192.168.0.132:64297->192.168.2.58:80: i/o timeout","time":"2023-06-04T00:08:54+03:00","caller":"/github/workspace/app/webClient/client.go:43","message":"Failed to read the response"}
{"level":"error","input":{"Command":101,"Payload":"RTRS5/ku2pWDRJMINe+abftpLcNwuQRDrFzWP7tTrfoIgUyn+M9BcQAyjlcMO4bJTQVwhEmjieKa4QRUNqBb3dwCwWGvEyXofhmw99HOBo0=","Mac":"ec0bae13111a"},"device":"ec0bae13111a","time":"2023-06-04T00:08:54+03:00","caller":"/github/workspace/app/service/service.go:703","message":"failed to send a command"}
{"level":"error","error":"read udp 192.168.0.132:64297->192.168.2.58:80: i/o timeout","input":{"Mac":"ec0bae13111a"},"time":"2023-06-04T00:08:54+03:00","caller":"/github/workspace/app/service/service.go:140","message":"failed to send command"}
{"level":"error","error":"read udp 192.168.0.132:64297->192.168.2.58:80: i/o timeout","device":"ec0bae13111a","time":"2023-06-04T00:08:54+03:00","caller":"/github/workspace/main.go:170","message":"Failed to Auth device ec0bae13111a. Reconnect in 3 seconds..."}
{"level":"info","time":"2023-06-04T00:08:56+03:00","caller":"/github/workspace/main.go:204","message":"Got SIGINT..."}

Although I followed the steps carefully.

[homy2023]

Hi!
I have ANDE AC which as I understand is just a rebranded AUX AC for European market. I am using AC MQTT proxy for home assistant (by Arbuzov) but am getting continuous Starting/Stopping messages in the logs:

Starting Monitor...
(200, ('192.168.8.41', 80))
Stopping
Starting Monitor...
(200, ('192.168.8.41', 80))
Stopping

My configuration:

service:
  daemon_mode: true
  update_interval: 10
  self_discovery: false
  bind_to_ip: false
mqtt:
  host: addon_core_mosquitto
  port: 1883
  client_id: ac_to_mqtt
  user: mqtt
  passwd: mqtt123
  topic_prefix: /aircon
  auto_discovery_topic: homeassistant
  auto_discovery_topic_retain: false
  discovery: false
devices:
  - ip: 192.168.8.41
    mac: ***
    name: Room
    port: 80

I logged into the addon container and noticed that the monitor.py process is being killed and recreated with new PID every couple of seconds. Is it a normal behavior?

I am happy to do additional tests if someone is willing to instruct how to troubleshoot the issue further.