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

I am getting the following - something went wrong, no devices found
Starting Monitor…
Stopping

Wonder what I could be doing wrong?

Does not work for me either.

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
services-up: info: copying legacy longrun broadlink-ac-mqtt (no readiness notification)
s6-rc: info: service legacy-services successfully started
Starting Monitor…
Stopping
something went wrong, no devices found
Starting Monitor…
Stopping
something went wrong, no devices found
Starting Monitor…
Stopping

Here is my addon configuration file:

service:
daemon_mode: true
update_interval: 10
self_discovery: true
bind_to_ip: false
mqtt:
host: addon_core_mosquitto
port: 1883
client_id: ac_to_mqtt
user: mqtt-user
passwd: “mypassword”
topic_prefix: /aircon
auto_discovery_topic: homeassistant
auto_discovery_topic_retain: false
discovery: false
devices:

  • ip: 10.10.10.139
    mac: c8f742348bec
    name: Living Room AC
    port: 80
  • ip: 10.10.10.80
    mac: a043b008e504
    name: Office AC
    port: 80
  • ip: 10.10.10.79
    mac: a043b0088f14
    name: Home Cinema AC
    port: 80

I got the same error. In my case

self_discovery: false

Fixed the problem. Looks like sef_discovery and devices did not work together.

Thanks that solved it!

By the way since you are at it, can you also fix the ambient reading issue, as i think above 31 degrees or something it starts from 1 again.

Thank you to trust in me :slight_smile:
Is it a reading or visualization issue?
Could not reproduce it on my side:
image
image

No thank you for putting the time and effort in making this addon!

I think it is neither. I believe their is a sensor limit somewhere in the code and once it passes lets say 32 degrees it starts over.

For example the AC Freedom app shows Living Room AC as 38 degrees ambient (i know it’s a lot! :grin:) while HA show it as 6. Please see pics bellow.

This is up and running for me. Thank you for this Arbuzov!

Perfect!!! it’s Ok for Baxi AC device. :+1:

Is there any method to change the values to Fahrenheit? It’s set that way when using the remote, but the integration reverts it to Celsius.

Error:

Starting Monitor...
Authentication Failed to AC
__init__() should return None, not 'bool'
Stopping
Starting Monitor...
Authentication Failed to AC.....
......

help:)

Does anyone happen to know when I restart home assistant why the entity becomes unavailable.
If I go to addon and press restart it works again.
Is there a solution for this?

Idk if it will help (if this even is a problem), but you can set auto_discovery_topic_retain: False in the ac2mqtt config

Next problem


Starting Monitor…
[Errno -2] Name does not resolve
Stopping

Hi!

I get same error.
What was your solution??
(AUX air conditioner)

thx!

Hello,
Has anyone found the solution?
,

I have the same error:

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
services-up: info: copying legacy longrun broadlink-ac-mqtt (no readiness notification)
s6-rc: info: service legacy-services successfully started
Starting Monitor...
Authentication Failed to AC
__init__() should return None, not 'bool'
Stopping
Starting Monitor...
Authentication Failed to AC
__init__() should return None, not 'bool'
Stopping
Starting Monitor...
Authentication Failed to AC
__init__() should return None, not 'bool'
Stopping
Starting Monitor...
Authentication Failed to AC
__init__() should return None, not 'bool'
Stopping
Starting Monitor...
Authentication Failed to AC
__init__() should return None, not 'bool'
Stopping
Starting Monitor...
Authentication Failed to AC
__init__() should return None, not 'bool'
Stopping
Starting Monitor...
Authentication Failed to AC
__init__() should return None, not 'bool'
Stopping`

Anyone running this in Docker ?

[email protected]:/app/ac2mqtt# ./monitor.py -s
Starting Monitor…
something went wrong, no devices found
Stopping
[email protected]:/app/ac2mqtt# ./monitor.py -S
No devices found, make sure you are on same network broadcast segment as device/s
[email protected]:/app/ac2mqtt#

Can’t put this to work.

You have to add yours AC with older AC Freedom APP f.e. 1.3.0 . You will lose AC Freedom integration but will be able to use it in HA.

@ Szajman11 was that for me ?

Hoping that someone can help me here or have some tips to continue my research.

When using the AC Freedom App 2.x, it will get the following errors when starting the integration:

Starting Monitor...
Authentication Failed to AC
__init__() should return None, not 'bool'
Stopping

This is as the author mentioned because it doesn’t work for the 2.x App. But every AC Freedom App 1.2x I tried downloading from the APK Pure website just crashes after startup. (tried different devices)

As @Szajman11 suggested I tried the AC Freedom 1.3.0 App. Which does startup, but when I tried to connect the AC device to the WIFI it just keeps failing every time. If I try it again on the AC Freedom 2.x App, it is successful on the first attempt. So I am pretty sure it is not the WIFI, but the App.

Summary:

  • AC Freedom App 2.x works, but not for the integration
  • AC Freedom App 1.2x crashed
  • AC Freedom App 1.3 starts, but fails to connect a device to wifi

Extra info of the device I am using:

  • Firmware = v42037
  • SDK = 2.17.3
  • Data Cloud = Europe

Any tips would be appreciated.