Fixed. There's some additional weirdness, if it's in mute mode and i try to set swing mode to swing, this happens:

Jul 23 22:54:25 raspberrypi broadlinkac2mqtt[28041]: {"level":"debug","device":"c8f74291b0a6","payload":"swing","topic":"/aircon/c8f74291b0a6/swing_mode/set","time":"2023-07-23T22:54:25+04:00","caller":"/home/gerben/src/broadlinkac2mqtt/app/mqtt/subscriber/subscriber.go:50","message":"new update swing mode message"}
Jul 23 22:54:26 raspberrypi broadlinkac2mqtt[28041]: {"level":"debug","status":{"FanMode":"mute","SwingMode":"auto","Mode":"cool","Temperature":25},"device":"c8f74291b0a6","time":"2023-07-23T22:54:26+04:00","caller":"/home/gerben/src/broadlinkac2mqtt/app/service/service.go:460","message":"The converted current device status"}
Jul 23 22:54:27 raspberrypi broadlinkac2mqtt[28041]: {"level":"debug","status":{"FanMode":"mute","SwingMode":"","Mode":"cool","Temperature":25},"device":"c8f74291b0a6","time":"2023-07-23T22:54:27+04:00","caller":"/home/gerben/src/broadlinkac2mqtt/app/service/service.go:460","message":"The converted current device status"}
Jul 23 22:54:27 raspberrypi home-assistant/38264391d62a[667]: 2023-07-23 22:54:27.800 ERROR (MainThread) [homeassistant.components.mqtt.climate] Invalid swing_modes mode: 
Jul 23 22:54:39 raspberrypi broadlinkac2mqtt[28041]: {"level":"debug","status":{"FanMode":"mute","SwingMode":"","Mode":"cool","Temperature":25},"device":"c8f74291b0a6","time":"2023-07-23T22:54:39+04:00","caller":"/home/gerben/src/broadlinkac2mqtt/app/service/service.go:460","message":"The converted current device status"}

Note how SwingMode is "".

But, no segfaults, and no repeated beeping due to status messages.

Originally posted by @infernix in #19 (comment)

After latest updates, my HA logs are reporting:

Logger: homeassistant.components.hassio.data
Source: components/hassio/data.py:497
integration: Home Assistant Supervisor ([documentation](https://www.home-assistant.io/integrations/hassio), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+hassio%22))
First occurred: 09:16:21 (16 occurrences)
Last logged: 10:31:21

Could not fetch changelog for 97e9acfb_broadlinkac2mqtt:

and

Logger: homeassistant.components.hassio.handler
Source: components/hassio/handler.py:612
integration: Home Assistant Supervisor ([documentation](https://www.home-assistant.io/integrations/hassio), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+hassio%22))
First occurred: 09:16:21 (16 occurrences)
Last logged: 10:31:21

Client error on /addons/97e9acfb_broadlinkac2mqtt/changelog request 0, message='Attempt to decode JSON with unexpected mimetype: application/octet-stream', url=URL('http://172.30.32.2/addons/97e9acfb_broadlinkac2mqtt/changelog')

Nothing else in Supervisor logs. I assume the issue is with this add-on and not Supervisor itself.
P.S. There are no issues with functionalities of the add-on.

Hello, I have an air conditioner which uses Broadlink and I used this add-on with it.
I updated the add-on a few minutes ago and now it crashes with the error "wrong mac" even though I double and triple checked it is the correct one.
Any fix for this bug?

Update to 1.5.1 is not showing for me in Add-ons in Home Assistant (HAOS). Have rebooted HA instance and manually checked for add-on updates. Is it supposed to be available or not? I'm guessing version has to be bumped in https://github.com/ArtemVladimirov/hassio-add-ons

Hi i try to install this on my home assistant, home assistant is hosted to Esxi Server.

Show this error when i try to install

The command '/bin/ash -o pipefail -c if [ "${BUILD_ARCH}" = "armhf" ]; then wget -O broadlinkac2mqtt.tar.gz https://github.com/ArtemVladimirov/broadlinkac2mqtt/releases/download/${BUILD_VERSION}/broadlinkac2mqtt-${BUILD_VERSION}-linux-arm.tar.gz; elif [ "${BUILD_ARCH}" = "armv7" ]; then wget -O broadlinkac2mqtt.tar.gz https://github.com/ArtemVladimirov/broadlinkac2mqtt/releases/download/${BUILD_VERSION}/broadlinkac2mqtt-${BUILD_VERSION}-linux-arm7.tar.gz; elif [ "${BUILD_ARCH}" = "aarch64" ]; then wget -O broadlinkac2mqtt.tar.gz https://github.com/ArtemVladimirov/broadlinkac2mqtt/releases/download/${BUILD_VERSION}/broadlinkac2mqtt-${BUILD_VERSION}-linux-arm64.tar.gz; elif [ "${BUILD_ARCH}" = "i386" ]; then wget -O broadlinkac2mqtt.tar.gz https://github.com/ArtemVladimirov/broadlinkac2mqtt/releases/download/${BUILD_VERSION}/broadlinkac2mqtt-${BUILD_VERSION}-linux-386.tar.gz; elif [ "${BUILD_ARCH}" = "amd64" ]; then wget -O broadlinkac2mqtt.tar.gz https://github.com/ArtemVladimirov/broadlinkac2mqtt/releases/download/${BUILD_VERSION}/broadlinkac2mqtt-${BUILD_VERSION}-linux-amd64.tar.gz; else echo 'NOT VALID BUILD'; exit 1; fi && tar -xzf broadlinkac2mqtt.tar.gz && rm broadlinkac2mqtt.tar.gz && chmod a+x ./run.sh && mkdir config && apk add --no-cache gcc g++ make && pip3 install --no-cache-dir -U pyyaml' returned a non-zero code: 1

Hi Artem, first of all, great job. An now, to make your addon even better, could you add AntiF and Health functions? To make your addon work, I had to lose AC Freedom, and now I can't activate these functions. As not all AC have this function, you can add a separate switch, like Led control, that works fine with my AC
Thanks

I'm unable to download, build and use the addon, I got the following error: docker: no matching manifest for linux/arm64/v8 in the manifest list entries.

Sorry, maybe this is a lame issue, I'd appreciate every suggestion.

Thanks!

ac freedom work fine, but not code

broadlinkac2mqtt    | {"level":"error","error":"read udp 172.20.0.6:34487->192.168.1.111:80: i/o timeout","time":"2023-08-17T22:08:23Z","caller":"/go/src/broadlinkac/app/app/webClient/client.go:43","message":"Failed to read the response"}
broadlinkac2mqtt    | {"level":"error","error":"read udp 172.20.0.6:34487->192.168.1.111:80: i/o timeout","input":{"Command":101,"Payload":"RTRS5/ku2pWDRJMINe+abftpLcNwuQRDrFzWP7tTrfoIgUyn+M9BcQAyjlcMO4bJTQVwhEmjieKa4QRUNqBb3dwCwWGvEyXofhmw99HOBo0=","Mac":"ec0baee44a79"},"device":"ec0baee44a79","time":"2023-08-17T22:08:23Z","caller":"/go/src/broadlinkac/app/app/service/service.go:666","message":"failed to send a command"}
broadlinkac2mqtt    | {"level":"error","error":"read udp 172.20.0.6:34487->192.168.1.111:80: i/o timeout","input":{"Mac":"ec0baee44a79"},"time":"2023-08-17T22:08:23Z","caller":"/go/src/broadlinkac/app/app/service/service.go:140","message":"failed to send command"}
broadlinkac2mqtt    | {"level":"error","error":"read udp 172.20.0.6:34487->192.168.1.111:80: i/o timeout","device":"ec0baee44a79","time":"2023-08-17T22:08:23Z","caller":"/go/src/broadlinkac/app/main.go:156","message":"Failed to Auth device ec0baee44a79. Reconnect in 3 seconds..."}

Hi,

I recently switched from liaan/broadlink_ac_mqtt to this, and am having some issues with an AUX AC.

One is that the swing mode sometimes seems to get stuck on a loop, and it keeps submitting a state which makes the AC beep until I restart. It looks as if this happens if fan mode is in auto and i set swing mode to anything other than auto. Here's the log for that:

Jul 23 02:52:21 raspberrypi broadlinkac2mqtt[8980]: {"level":"debug","status":{"FanMode":"mute","SwingMode":"top","Mode":"cool","Temperature":25},"device":"c8f74291b0a6","time":"2023-07-23T02:52:21+04:00","caller":"/home/gerben/src/broadlinkac2mqtt/app/service/service.go:460","message":"The converted current device status"}
Jul 23 02:52:23 raspberrypi broadlinkac2mqtt[8980]: {"level":"debug","device":"c8f74291b0a6","payload":"auto","topic":"/aircon/c8f74291b0a6/fan_mode/set","time":"2023-07-23T02:52:23+04:00","caller":"/home/gerben/src/broadlinkac2mqtt/app/mqtt/subscriber/subscriber.go:31","message":"new update fan mode message"}
Jul 23 02:52:24 raspberrypi broadlinkac2mqtt[8980]: {"level":"debug","status":{"FanMode":"mute","SwingMode":"top","Mode":"cool","Temperature":25},"device":"c8f74291b0a6","time":"2023-07-23T02:52:24+04:00","caller":"/home/gerben/src/broadlinkac2mqtt/app/service/service.go:460","message":"The converted current device status"}
Jul 23 02:52:25 raspberrypi broadlinkac2mqtt[8980]: {"level":"debug","status":{"FanMode":"auto","SwingMode":"top","Mode":"cool","Temperature":25},"device":"c8f74291b0a6","time":"2023-07-23T02:52:25+04:00","caller":"/home/gerben/src/broadlinkac2mqtt/app/service/service.go:460","message":"The converted current device status"}

I then set fanmode to bottom, and then this just loops forever, beeping once per ~1-2 seconds, until I restart broadlinkac2mqtt:

Jul 23 02:52:30 raspberrypi broadlinkac2mqtt[8980]: {"level":"debug","device":"c8f74291b0a6","payload":"bottom","topic":"/aircon/c8f74291b0a6/swing_mode/set","time":"2023-07-23T02:52:30+04:00","caller":"/home/gerben/src/broadlinkac2mqtt/app/mqtt/subscriber/subscriber.go:50","message":"new update swing mode message"}
Jul 23 02:52:31 raspberrypi broadlinkac2mqtt[8980]: {"level":"debug","status":{"FanMode":"auto","SwingMode":"top","Mode":"cool","Temperature":25},"device":"c8f74291b0a6","time":"2023-07-23T02:52:31+04:00","caller":"/home/gerben/src/broadlinkac2mqtt/app/service/service.go:460","message":"The converted current device status"}
Jul 23 02:52:32 raspberrypi broadlinkac2mqtt[8980]: {"level":"debug","status":{"FanMode":"auto","SwingMode":"bottom","Mode":"cool","Temperature":25},"device":"c8f74291b0a6","time":"2023-07-23T02:52:32+04:00","caller":"/home/gerben/src/broadlinkac2mqtt/app/service/service.go:460","message":"The converted current device status"}
...

The other problem is a SEGFAULT which also happens when changing the swing mode. Seems to happen if fan mode is on mute and i set swing mode to anything other than what it is set to. Here's the output:

Jul 23 02:49:33 raspberrypi broadlinkac2mqtt[8813]: {"level":"debug","ambientTemp":26,"device":"c8f74291b0a6","time":"2023-07-23T02:49:33+04:00","caller":"/home/gerben/src/broadlinkac2mqtt/app/service/service.go:293","message":"Ambient temperature"}
Jul 23 02:49:34 raspberrypi broadlinkac2mqtt[8813]: {"level":"debug","status":{"FanMode":"mute","SwingMode":"top","Mode":"cool","Temperature":25},"device":"c8f74291b0a6","time":"2023-07-23T02:49:34+04:00","caller":"/home/gerben/src/broadlinkac2mqtt/app/service/service.go:460","message":"The converted current device status"}
Jul 23 02:49:38 raspberrypi broadlinkac2mqtt[8813]: {"level":"debug","device":"c8f74291b0a6","payload":"auto","topic":"/aircon/c8f74291b0a6/swing_mode/set","time":"2023-07-23T02:49:38+04:00","caller":"/home/gerben/src/broadlinkac2mqtt/app/mqtt/subscriber/subscriber.go:50","message":"new update swing mode message"}
Jul 23 02:49:38 raspberrypi broadlinkac2mqtt[8813]: panic: runtime error: invalid memory address or nil pointer dereference
Jul 23 02:49:38 raspberrypi broadlinkac2mqtt[8813]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x305c38]
Jul 23 02:49:38 raspberrypi broadlinkac2mqtt[8813]: goroutine 34 [running]:
Jul 23 02:49:38 raspberrypi broadlinkac2mqtt[8813]: github.com/ArtemVladimirov/broadlinkac2mqtt/app/service.(*service).StartDeviceMonitoring(0x1494480, {0x3e56c0, 0x1494300}, 0x1494330, 0x1410210)
Jul 23 02:49:38 raspberrypi broadlinkac2mqtt[8813]:         /home/gerben/src/broadlinkac2mqtt/app/service/service.go:1116 +0x70c
Jul 23 02:49:38 raspberrypi broadlinkac2mqtt[8813]: main.(*App).Run.func1()
Jul 23 02:49:38 raspberrypi broadlinkac2mqtt[8813]:         /home/gerben/src/broadlinkac2mqtt/main.go:171 +0x310
Jul 23 02:49:38 raspberrypi broadlinkac2mqtt[8813]: created by main.(*App).Run
Jul 23 02:49:38 raspberrypi broadlinkac2mqtt[8813]:         /home/gerben/src/broadlinkac2mqtt/main.go:150 +0x478

This is running 1c4e744 and it was the same before the refactor, so doesn't look like a recently introduced issue.

Let me know if you need more debug data.

When you turn on the air conditioner, does it go for updates?

broadlinkac2mqtt:
"failed to send a command","err":"read udp 172.30.33.2:51552->192.168.83.250:80: i/o timeout",

Hey,
I could update the add-on to 1.4.0 after your fix, but the latest version does not start. Here is the add-on log:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
/bin/ash: /broadlinkac2mqtt/broadlinkac2mqtt: not found
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Hello,
I have noticed that the program limits the ambient reading temperature to 32.

For HA integration, using the temperature sensor of the AC is useful to avoid buying a separate one.

Ive tried to integrate this code. However, sometimes the reads of the temperature jumps over 100 °C, Could it be integrated somehow? I am testing different values.

Hi, Artem!

I’ve faced with some checksum error. The log says:

{"level":"error","input":{"Command":106,"Payload":"FLucRpm5EV2o+VxYVGBZjg==","Mac":"ec0bae0c170a"},"time":"2023-04-24T17:21:24Z","caller":"/go/src/broadlinkac/app/app/service/service.go:332","message":"Checksum is incorrect"}
{"level":"error","error":"ErrorInvalidResultPacket","device":"ec0bae0c170a","time":"2023-04-24T17:21:24Z","caller":"/go/src/broadlinkac/app/app/service/service.go:1130","message":"Failed to get AC States"}

Any guess?
Thanks!

I have the app up and running under a docker container but seems it can not connect to the AC.

Logs below:

broadlinkac2mqtt  | {"level":"debug","time":"2023-06-22T16:44:32+02:00","caller":"/go/src/broadlinkac/app/config/config.go:47","message":"Start reading a config file"}
broadlinkac2mqtt  | {"level":"info","time":"2023-06-22T16:44:32+02:00","caller":"/go/src/broadlinkac/app/app/mqtt/mqtt.go:42","message":"Connected to MQTT"}
broadlinkac2mqtt  | {"level":"error","error":"read udp 172.22.0.2:50757->192.168.1.56:80: i/o timeout","time":"2023-06-22T16:44:42+02:00","caller":"/go/src/broadlinkac/app/app/webClient/client.go:43","message":"Failed to read the response"}
broadlinkac2mqtt  | {"level":"error","input":{"Command":101,"Payload":"RTRS5/ku2pWDRJMINe+abftpLcNwuQRDrFzWP7tTrfoIgUyn+M9BcQAyjlcMO4bJTQVwhEmjieKa4QRUNqBb3dwCwWGvEyXofhmw99HOBo0=","Mac":"ec0baed30ddb"},"device":"ec0baed30ddb","time":"2023-06-22T16:44:42+02:00","caller":"/go/src/broadlinkac/app/app/service/service.go:703","message":"failed to send a command"}
broadlinkac2mqtt  | {"level":"error","error":"read udp 172.22.0.2:50757->192.168.1.56:80: i/o timeout","input":{"Mac":"ec0baed30ddb"},"time":"2023-06-22T16:44:42+02:00","caller":"/go/src/broadlinkac/app/app/service/service.go:140","message":"failed to send command"}
broadlinkac2mqtt  | {"level":"error","error":"read udp 172.22.0.2:50757->192.168.1.56:80: i/o timeout","device":"ec0baed30ddb","time":"2023-06-22T16:44:42+02:00","caller":"/go/src/broadlinkac/app/main.go:170","message":"Failed to Auth device ec0baed30ddb. Reconnect in 3 seconds..."}

BTW, not sure how to chose a correct port number of AC. I tries to scan it by nmap, it does return nothing. Seems every port are closed.

My current config

service:
  update_interval: 10 # In seconds. Default: 10
  log_level: error    # Supported: info, disabled, fatal, debug, error. Default: error

mqtt:
  broker: "mqtt://mqtt-broker-address:1883"
  auto_discovery_topic: homeassistant

devices:
  - ip: ac-ip-address
    mac: ac-mac-address
    name: Livingroom AC
    port: 80

Any thoughts?

Trying to run the integration, but seems that it failing to connect to the AC. Not sure whether it has different protocol version? something else?

{"time":"2024-05-27T07:04:19.001619917Z","level":"ERROR","source":{"function":"github.com/ArtemVladimirov/broadlinkac2mqtt/app/webClient.(*webClient).SendCommand","file":"/go/src/broadlinkac/app/app/webClient/client.go","line":43},"msg":"Failed to read the response","err":"read udp 192.168.3.24:43333->192.168.3.21:80: i/o timeout"}
{"time":"2024-05-27T07:04:19.001819383Z","level":"ERROR","source":{"function":"github.com/ArtemVladimirov/broadlinkac2mqtt/app/service.(*service).SendCommand","file":"/go/src/broadlinkac/app/app/service/service.go","line":720},"msg":"failed to send a command","err":"read udp 192.168.3.24:43333->192.168.3.21:80: i/o timeout","device":"e811576872fc","input":{"Payload":"WqWqVVqlqlUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADL7wAAKk5lAAni6BZWaHL8AAAAAKHDAABFNFLn+S7alYNEkwg175pt+2ktw3C5BEOsXNY/u1Ot+giBTKf4z0FxADKOVww7hslNBXCESaOJ4prhBFQ2oFvd3ALBYa8TJeh+GbD30c4GjQ==","Ip":"192.168.3.21","Port":80}}
{"time":"2024-05-27T07:04:19.001907338Z","level":"ERROR","source":{"function":"github.com/ArtemVladimirov/broadlinkac2mqtt/app/service.(*service).AuthDevice","file":"/go/src/broadlinkac/app/app/service/service.go","line":137},"msg":"failed to send command","err":"read udp 192.168.3.24:43333->192.168.3.21:80: i/o timeout","input":{"Mac":"e811576872fc"}}
{"time":"2024-05-27T07:04:19.001944908Z","level":"ERROR","source":{"function":"main.(*App).Run.func1","file":"/go/src/broadlinkac/app/main.go","line":162},"msg":"failed to Auth device e811576872fc. Reconnect in 3 seconds...","err":"read udp 192.168.3.24:43333->192.168.3.21:80: i/o timeout"}

config,yml:
devices:

• ip: 192.168.3.21
  mac: E811576872FC
  name: Childroom AC
  port: 80

  Temperature Unit defines the temperature unit of the device, C or F.

  If this is not set, the temperature unit is Celsius.

  temperature_unit: C

`~/tmp/tf> sudo nmap -sU -p80 192.168.3.21
Starting Nmap 7.93 ( https://nmap.org ) at 2024-05-27 13:37 IDT
Nmap scan report for AC_SMT-68-72-fc (192.168.31.21)
Host is up (0.050s latency).

PORT STATE SERVICE
80/udp open|filtered http
MAC Address: E8:11:57:68:72:FC (Hangzhou BroadLink Technology)

Nmap done: 1 IP address (1 host up) scanned in 0.68 seconds`

I do have a dedicated app running on my phone and it works fine

Thanks

Hi, thanks for this!

I'm trying to get this to work and I've tried both the docker and stand-alone app, but I fail to connect to my MQTT broker, a mosquitto instance running with SSL (on port 8883) and username/password required. The app logs:

DBG config/config.go:45 > Start reading a config file 
ERR app/main.go:156 > Failed to connect mqtt 
fatal app/main.go:260 > failed to get a new App | error=network Error : EOF

I didn't see an option in the config.yml to support SSL. Is that perhaps the issue?

Hi,

I have 3 Vortex AC units (2 from 2016 and 1 from 2022)
I had no issues connecting the ones from 2016 but unfortunately the one from 2022 is not connecting:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
{"level":"debug","time":"2023-09-13T14:33:38Z","caller":"/app/broadlinkac2mqtt/config/config.go:47","message":"Start reading a config file"}
{"level":"error","error":"read udp 172.30.33.4:60992->192.168.0.49:80: i/o timeout","time":"2023-09-13T14:33:48Z","caller":"/app/broadlinkac2mqtt/app/webClient/client.go:43","message":"Failed to read the response"}
{"level":"error","error":"read udp 172.30.33.4:60992->192.168.0.49:80: i/o timeout","input":{"Command":101,"Payload":"RTRS5/ku2pWDRJMINe+abftpLcNwuQRDrFzWP7tTrfoIgUyn+M9BcQAyjlcMO4bJTQVwhEmjieKa4QRUNqBb3dwCwWGvEyXofhmw99HOBo0=","Mac":"ec0bae566d7a"},"device":"ec0bae566d7a","time":"2023-09-13T14:33:48Z","caller":"/app/broadlinkac2mqtt/app/service/service.go:665","message":"failed to send a command"}
{"level":"error","error":"read udp 172.30.33.4:60992->192.168.0.49:80: i/o timeout","input":{"Mac":"ec0bae566d7a"},"time":"2023-09-13T14:33:48Z","caller":"/app/broadlinkac2mqtt/app/service/service.go:139","message":"failed to send command"}
{"level":"error","error":"read udp 172.30.33.4:60992->192.168.0.49:80: i/o timeout","device":"ec0bae566d7a","time":"2023-09-13T14:33:48Z","caller":"/app/broadlinkac2mqtt/main.go:156","message":"Failed to Auth device ec0bae566d7a. Reconnect in 3 seconds..."}

Any idea what I can do?

Is there a way to define change or convert the temperature unit from Celsius to Fahrenheit?

Hi Artem,
This is not an issue, I think that I don't know how can I install this addon in my home assistant.
How can I install in aarch64? When I try to create a stack in portainer with your compose command I get: Deployment error
failed to deploy a stack: broadlinkac2mqtt Pulling no matching manifest for linux/arm64/v8 in the manifest list entries

and running docker command in my linux i get:
Docker: "no matching manifest for linux/arm64/v8 in the manifest list entries"

Could you make an addon repository to install addon easily like https://github.com/Arbuzov/hass-broadlink-ac-mqtt ?
Thanks mate

Hi Artem!
I have AUX Delta 2 climate (AUX ASW-H12C5C4 / JER3DI-B8-2), I set up with AC Freedom, and I configured your intergation:
The climate info:
IP: 192.168.1.49, MAC: EC:0B:AE:D3:AA:ED, Hostname: AC_SMT-d3-aa-ed

Firewall info:

Src. address: 192.168.1.49:62551
Dst. Address: 52.2.9.65.95:1885
6(tcp)

Config file:

service:
  update_interval: 10 #Seconds
  log_level: error

mqtt:
  ## Use mqtts for SSL support
  broker: "mqtt://192.168.1.6:1883"
  user: mosquitto
  password: *****
  client_id: aircac2
  topic_prefix: aircon2
  auto_discovery_topic: homeassistant
  auto_discovery_topic_retain: true
  ## CA certificate in CRT format.
  # certificate_authority: "./config/cert/ca.crt"
  ## Don’t verify if the common name in the server certificate matches the value of broker
  # skip_cert_cn_check: true
  ## Authorization using client certificates
  # certificate_client: "./config/cert/client.crt"
  # key-client: "./config/cert/client.key"

devices:
  - ip: 192.168.1.49
    mac: ec0baed3aaed
    name: Nappali AC
    port: 62551

Looks like the climate communicate on the 62551 port, I tried it, but always get an error. Of course I tried the default 80 port too.

jún 05 20:32:32 xxx.xxx.net broadlinkac2mqtt[1590]: {"level":"error","error":"read udp 172.17.0.2:49144->192.168.1.49:62551: read: connection refused","input":{"Mac":"ec0baed3aaed"},"time":"2023-06-05T18:32:32Z","caller":"/go/src/broadlinkac/app/app/service/service.go:140","message":"failed to send command"}
jún 05 20:32:32 xxx.xxx.net broadlinkac2mqtt[1590]: {"level":"error","error":"read udp 172.17.0.2:49144->192.168.1.49:62551: read: connection refused","device":"ec0baed3aaed","time":"2023-06-05T18:32:32Z","caller":"/go/src/broadlinkac/app/main.go:170","message":"Failed to Auth device ec0baed3aaed. Reconnect in 3 seconds..."} 

Have you any advance to solve this? Thank you!

Hi Artem,

In one of your posts on the HA forum you mentioned that you could read the packeges from the ACs to find out what's going on. The situation here is as follow:

• I reset the AC, and use the AC Freedom app to connect
• Somehow the Freedom app instructs the AC to connect to WiFi (I guess via a hidden wifi channel?)
• The AC then connects to the WiFi, and established connection to the cloud service. From that moment on, the AC won't respond to anything on the local network. Port 80 is filtered and remains quiet whatever I throw at it.

I've captured the communication from the AC to the cloud using tcpdump directly on the WiFi access point. You can find the pcap here: https://we.tl/t-NNlcCMe2HO

as you can see, there is absolutly zero communication between Freedom App and the AC once it's connected to the cloud.

I've seen more people having this issue, it seems that in newer FW the local access is disabled.

@ArtemVladimirov , thanks for this awesome solution, today we are facing this issue:

Some MQTT entities have an entity name equal to the device name. This is not expected. The entity name is set to null as a work-a-round to avoid a duplicate name. Please inform the maintainer of the software application that supplies the affected entities to fix this issue.

This stops working in version 2024.2.0. Please address before upgrading.

https://developers.home-assistant.io/blog/2023-057-21-change-naming-mqtt-entities/