It is very sad that the new air conditioners do not have the possibility of local control. I live in a region where the internet is not very stable. Moreover, I try not to buy devices without local management, because one day the proprietary cloud may simply disappear and all devices will stop working. There are already many such cases
OK. Perhaps something with the environment setupā¦ Anyways it looks like we need advice from some Home assistant docker guru, who knows how to correctly start these scripts.
Itās not docker causing the issue. The newer aux have the local control possibility disabled. Without going politically here this is a very dangerous situation we create for ourselves by having all those high power equipment controlled by a central organisation / government. If someone, either by accident or not, turns on all the AC in a region, the power grid will fail.
Thatās interesting. How can we check whether local control is blocked?
There is zero response from the module once connected to the cloud service. From what I understood in the past versions, there was a response to a specific formed broadcast message. Using tcpdump on the WiFi access point itself I couldnāt find any (udp) response to the probing of the python scripts. Furthermore, any connection attempts to port 80, to actually send commands, are being blocked.
Can you share the scripts/packets so that I can try them on my new ANDE(formerly AUX) AC?
Finally, I found the issue with creating an addon for hassio.
Now everyone can add the addon to their instance!
It takes a long time to installing (3-10 min), but it works!
I managed to run the addon but it does not see the AC. My config:
service:
update_interval: 10
log_level: error
mqtt:
broker: mqtt://addon_core_mosquitto:1883
user: mqtt
password: ***
client_id: aircon
topic_prefix: aircon
auto_discovery_topic: homeassistant
auto_discovery_topic_retain: false
certificate_authority: ca.crt
skip_cert_cn_check: true
certificate_client: client.crt
key-client: client.key
devices:
- ip: 192.168.8.41
mac: ec0baea6416b
name: Living room AC
port: 80
In the logs I see the following:
{"level":"error","input":{"Command":101,"Payload":"RTRS5/ku2pWDRJMINe+abftpLcNwuQRDrFzWP7tTrfoIgUyn+M9BcQAyjlcMO4bJTQVwhEmjieKa4QRUNqBb3dwCwWGvEyXofhmw99HOBo0=","Mac":"ec0baea6416b"},"device":"ec0baea6416b","time":"2023-07-19T19:43:36Z","caller":"/app/broadlinkac2mqtt/app/service/service.go:703","message":"failed to send a command"}
{"level":"error","error":"read udp 172.30.33.5:35588->192.168.8.41:80: i/o timeout","input":{"Mac":"ec0baea6416b"},"time":"2023-07-19T19:43:36Z","caller":"/app/broadlinkac2mqtt/app/service/service.go:140","message":"failed to send command"}
{"level":"error","error":"read udp 172.30.33.5:35588->192.168.8.41:80: i/o timeout","device":"ec0baea6416b","time":"2023-07-19T19:43:36Z","caller":"/app/broadlinkac2mqtt/main.go:156","message":"Failed to Auth device ec0baea6416b. Reconnect in 3 seconds..."}
I am running HA on RPi4. Does WiFi need to be up and in the same SSID/network as AC during discovery?
@homy2023 same issue here. The Broadlink seems to be locked to the cloud service. End of the line. After my vacation (>4 weeks) Iāll try this
It will replace the entire Broadcom wifi module for 2-3 euro worth of componements.
Yeah, it requires a bit of soldering. I would rather not do that but if there is no other option then perhaps will have to go for it
Would really like to know how it went for you!
Iām new to Home Assistant so Iām sorry for the obvious questions. I 've set up MQTT, installed and configured Broadlinkac2mqtt addon and I think it runs fine. Now what should I do? I cannot find an AC device nor similar entities. I see broadlinkac2mqtt device but it doesnāt have AC related entities. Can someone help me what step am I missing?
Ok, prototype is running
It took 10 minutes of soldering and some messing around with uploading esphome. Next step is creating a proper board and 3d print housing, and then mass produce it for my 5 unitsš
It looks cool (pun intended). Can you control the AC unit from HA as well - like changing temperature/mode and so on?
Perhaps you can mass produce one more unit (for reasonable price) for me as well?
I might. Itās quite a bit of work to solder it and then flash. It seems to be able to control a lot of rebranded aircos.
A similar problem. Addon Log:
{"level":"error","error":"read udp 172.30.33.10:47563->192.168.0.163:80: i/o timeout","time":"2023-09-11T20:09:11Z","caller":"/app/broadlinkac2mqtt/app/webClient/client.go:43","message":"Failed to read the response"}
{"level":"error","error":"read udp 172.30.33.10:47563->192.168.0.163:80: i/o timeout","input":{"Command":101,"Payload":"RTRS5/ku2pWDRJMINe+abftpLcNwuQRDrFzWP7tTrfoIgUyn+M9BcQAyjlcMO4bJTQVwhEmjieKa4QRUNqBb3dwCwWGvEyXofhmw99HOBo0=","Mac":"ec0bae19435b"},"device":"ec0bae19435b","time":"2023-09-11T20:09:11Z","caller":"/app/broadlinkac2mqtt/app/service/service.go:665","message":"failed to send a command"}
{"level":"error","error":"read udp 172.30.33.10:47563->192.168.0.163:80: i/o timeout","input":{"Mac":"ec0bae19435b"},"time":"2023-09-11T20:09:11Z","caller":"/app/broadlinkac2mqtt/app/service/service.go:139","message":"failed to send command"}
{"level":"error","error":"read udp 172.30.33.10:47563->192.168.0.163:80: i/o timeout","device":"ec0bae19435b","time":"2023-09-11T20:09:11Z","caller":"/app/broadlinkac2mqtt/main.go:156","message":"Failed to Auth device ec0bae19435b. Reconnect in 3 seconds..."}
Checking the port:
Hi / Hoi Martijn, looks promising.
Just ordered the products to do the same. Wondering if everything is still working smoothly and also if you have any tips or tricks? Flashing and installing ESPHome? Easy job?
Thx.
Marnix
Would you mind writing a guide on how to accomplish this?
Hi, any solution for the āFailed to Auth deviceā massage for some AUX models ?
I am new to Home assistant and Broadlink, but have managed to setup one RM4 Pro and four of the RM4 miniās. I have also setup one room into the broadlink app and also managed to get scripts into Home assistant. I encountered an issue with getting the Air cons showing up in Lovelace as a card something like those thermostat cards.
Upon searching the web I stumbled upon this page.
- Can I clarify if this addon is meant to work with those scripts I created and does it incorporate a dashboard card etc or I am missing the intent of this addon?
- Does it work for all Air cons? I have Fujitsu, Daikin, Panasonic, LG and Mitsubishi.
Thanks
Hi !
I would like to mention that I am not a home assistant specialist. All the integrations I made were completed just by reading this forum and trying to figure out how each one works.
In this case below I have a dilemma.
I have a Vortex air conditioner (with wifi) that I control through the āAc freedomā application and from the home assistant I only give it on/off commands learned through tuya IR.
I recently read about broadlinkac2mqtt. I managed to make it work through this add-on but I do NOT understand how it works.
I will tell you the steps I took.
-
I deleted the Ac device from the āAc freedomā application
-
I reset wifi Ac
-
in the add-on I filled in the ip and mac of Ac (and mqtt)ā¦ (information I knew since it was connected through the Acfreedom app)
-
in Broadlink (RM4) I did not find the integration for Ac Vortex and tried other brands. I found AEG on the list, which correctly sends IR commands to Ac Vortex.
-
I restarted the home assistant and found with surprise that it works.
My question is how did the air conditioner connect to the router, being deleted from the Acfreedom application.