I have new ANDE/AUX AC. Perhaps it uses the new method. How could we see if it does?
I have a two docker installations "broadlinkac/broadlink_ac_mqtt] and [ghcr.io/artemvladimirov/broadlinkac2mqtt:latest] installed. Unfortunately they both won’t connect to the AC device (AC1 AUX AC Freedom).
I read about that you should stop (and delete the app) half way the wifi configuration process. I have tried everything. Even blocking url by using the firewall and DNS server (AdGuard).
Docker still refuses to connect to the AC unit.
Ping from docker works and finds the AC device.
With nmap i do get the following information back:
# nmap -sU -p80 192.168.1.34
Starting Nmap 7.94 ( https://nmap.org ) at 2023-06-14 13:39 CEST
Nmap scan report for 192.168.1.34
Host is up (0.40s latency).
PORT STATE SERVICE
80/udp open|filtered http
MAC Address: EC:0B:AE:A6:80:4B (Hangzhou BroadLink Technology)
It seems port 80 UDP is open but filtered.
My question is if you all also experience this?
Must this port be completely open before it will connect?
Wondering of people who made it work wat their results are when a doing port check with nmap?
Thanks.
device info:
"Firmware":"v52020",
"Data Cloud":"Europe",
"SDK":"2.17",
It does not seem to be the issue. Mine are in the same open|filtered and working fine with artemvaldimirov build.
It worked perfectly for me, but I need to restart the addon every time the system restarts
I’ve the same. There is absolutly no response from the AC (AUX) when I send the UDP packet at 80. When I wireshark the Freedom APP it goes outside using some Amazon server. SOme suggested to look at the device info @ Freedom APP to find the correct port but none is listed. It seems there is no local connection at all (which is the whole idea!)
The log
2023-07-13 12:49:55,086,86 DEBUG [monitor.py:375] Traceback (most recent call last):
File “C:\Users\marti\OneDrive\Documenten\Sources\repos\myAUX\myAUX\broadlink_ac_mqtt\classes\broadlink\ac_db.py”, line 288, in send_packet
response = self.cs.recvfrom(1024)
socket.timeout: timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File “C:\Users\marti\OneDrive\Documenten\Sources\repos\myAUX\myAUX\monitor.py”, line 344, in start
devices = AC.make_device_objects(config[‘devices’])
File “C:\Users\marti\OneDrive\Documenten\Sources\repos\myAUX\myAUX\broadlink_ac_mqtt\AcToMqtt.py”, line 76, in make_device_objects
device_objects[device[‘mac’]] = broadlink.gendevice(devtype=0x4E2a, host=(device[‘ip’],device[‘port’]),mac = bytearray.fromhex(device[‘mac’]), name=device[‘name’],update_interval = self.config[‘update_interval’])
File “C:\Users\marti\OneDrive\Documenten\Sources\repos\myAUX\myAUX\broadlink_ac_mqtt\classes\broadlink\ac_db.py”, line 22, in gendevice
return ac_db(host=host, mac=mac,name=name, cloud=cloud,devtype= devtype,update_interval = 0)
File “C:\Users\marti\OneDrive\Documenten\Sources\repos\myAUX\myAUX\broadlink_ac_mqtt\classes\broadlink\ac_db.py”, line 385, in init
if self.auth() == False:
File “C:\Users\marti\OneDrive\Documenten\Sources\repos\myAUX\myAUX\broadlink_ac_mqtt\classes\broadlink\ac_db.py”, line 208, in auth
response = self.send_packet(0x65, payload)
File “C:\Users\marti\OneDrive\Documenten\Sources\repos\myAUX\myAUX\broadlink_ac_mqtt\classes\broadlink\ac_db.py”, line 294, in send_packet
raise ConnectTimeout(200,self.host)
broadlink_ac_mqtt.classes.broadlink.ac_db.ConnectTimeout: (200, (‘10.30.1.72’, 80))
2023-07-13 12:49:55,086,86 ERROR [monitor.py:376] (200, (‘10.30.1.72’, 80))
2023-07-13 12:49:55,087,87 INFO [monitor.py:169] Stopping
The bad news is that none of the current methods work with the new Aircons. It appears that only one TCP port is active; the previous UDP methods are no longer available. Maybe someone can figure out what the communication is or what this port is used for in order to obtain some statistics.
nmap -p 12416 10.10.1.100
Host is up (0.071s latency).
PORT STATE SERVICE
12416/tcp open unknown
I am using this for 1 month and it is awsome!!
I have only 1 problem, the commands to AIRCON work great, the state of FAN, Temperature, Swing, etc., all works great apart the state of the system. When i start it is COOL mode it is OK, but after some seconds the state is changes to “OFF”. Sometimes the state last longer.
Any hint why the state is reset to OFF and how this can be fixed?
Thanks a lot!!
Razvan
I forgot to mention that i am using HAOS, so i have installed this as an ADD-ON in HACS. The Aircon is VORTEX, being connected to WIFI on 2.4 GHz and initially controlled by using “AC Freedom” app.
Hi
Thanks for this integration, it works. But I have a problem with dashboard. I’m not getting ambient temp and slider. What am I missing?
Edit: I solved it. Problem was that I used upper/lower cases in different places (MQTT proxy config and mqtt.yaml). When changed to lower cases, everything was ok.
Its unfortunate, but I have not been able to use the add-on. I ended up soldering my own wifi modul using the description: https://github.com/GrKoR/esphome_aux_ac_component/blob/864ad07699606963b0eeaafeba101195efe3eb3e/README-EN.md
I have new AUX machines. I asked AUX local main supplier and they mentioned that they are not going to help.
They mentioned that Enterprise AUX machines received or going to receive a kind of BUS interface, but the consumer version is not yet planned.
No luck for me getting the addon to listen to the AC unit.
s
6-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
something went wrong, no devices found
Starting Monitor...
Stopping
something went wrong, no devices found
Starting Monitor...
Stopping
something went wrong, no devices found
Starting Monitor...
Stopping
something went wrong, no devices found
Starting Monitor...
Stopping
something went wrong, no devices found
Starting Monitor...
service:
daemon_mode: true
update_interval: 10
self_discovery: true
bind_to_ip: false
mqtt:
host: 192.168.100.57
port: 1883
client_id: ac_to_mqtt
user: mqtt-user
passwd: "1111111"
topic_prefix: /aircon
auto_discovery_topic: homeassistant
auto_discovery_topic_retain: false
discovery: false
devices:
- ip: 192.168.100.28
mac: $$$$$$$$$
name: Living Room
port: 80
Hi, did You resolve connection problem with ANDE? Did You find solution?
No, not yet. But looks like I will need to change the WiFi module to get the unit controlled locally via HA.
Im fighting with the same problem but yesterday i saw on dashboard that AC module is connected and i can manage it. After 10 minutes still the same problem came back…
Pozdrowienia z Poznania tak przy okazji. Ciekaw jestem czy wymiana modułu coś da w tym przypadku. Śledzę temat i szukam rozwiązania jakby co.
That’s interesting. I never saw any response from the AC. Perhaps there are some occasions when it is open for local communication?
martijnDutch managed to get the new WiFi module installed and could control his AC. See: Broadlinkac2mqtt - Control your broadlink-based air conditioner with Home Assistant - #32 by martijnDutch
Hi any luck with this ?
Hi,
Having the same issue like others here
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
Could somebody help solve it, please, any ideas where to look would be mutch appritiated.
I also ended up by using HW solution described here: esphome_aux_ac_component/README-EN.md at b10a2f5dab20bb68979c65ee412376983f811eeb · GrKoR/esphome_aux_ac_component · GitHub
Hardest task was finding and ordering the electronic parts but soldering and programming was easier than it first appeared.
2 Likes
Would you mind linking where you bought the electronic parts? I’m also struggling to find the correct ones