Actron Connect and Home Assistant

“Gentlemen, I am now about to send a signal from this laptop through our local ISP, racing down fiber-optic cable at the speed of light to San Francisco, bouncing off a satellite in geosynchronous orbit to Lisbon, Portugal, where the data packets will be handed off to submerged transatlantic cables terminating in Halifax, Nova Scotia, and transferred across the continent via microwave relays back to our ISP and the X10 receiver attached to this (clicks mouse, lamp switches on) lamp.” – Howard Wolowitz.

As mentioned in a previous post (here), I was able to integrate an Actron air conditioner using the ActronConnect Wi-Fi module with my home automation software. Recently however, I decided to create an add-on for Home Assistant so that it could interface with that unit.

The add-on needs an MQTT broker to handle messaging to Home Assistant. The default configuration assumes you’re using the Mosquitto MQTT broker that comes with Home Assistant, but you could use any other product if you preferred.

The add-on has been compiled for amd64, armhf, armv7, and i386, and tested on a Linux 64bit virtual machine, and a Raspberry Pi using a 32-bit Home Assistant image.


Add a new add-on repository to your Home Assistant deployment, and you should be able to access the compiled add-on.

Add On

The repository for the add-on is here: It should install fairly quickly, the add-on is about 200mb.

Add On

You need only configure a couple of settings to use it. If you leave the default MQTTBroker of ‘core-mosquitto,’ it will use the Mosquitto add-on of Home Assistant (core-mosquitto is the internal name of the Mosquitto add-on (when hosted by Home Assistant). You could also put the IP address/host name of your broker if you host it elsewhere.

The logging is a little intense at the moment, but I’ll back that off once its had a bit more testing.

Once the add-on is installed, you’ll need to configure your home DNS (whether its on your router or otherwise), to make the the add-on look like the cloud service used by the Actron Connect module.

You will need to create DNS entries for these hosts, and resolve them to the IP address of your Home Assistant. Once you’ve done that, a reboot of the air conditioner will force the ActronConnect to lookup those IP addresses again, and then connect to your Home Assistant. Entries:



Edit: I’ve released a couple of updates since the original release. The add-on can now create per-zone temperature sensors if your Actron has a per-zone temperature readout.

Update: I’ve created an add-on for Actron Que and Neo – here.

~ Mike

115 thoughts on “Actron Connect and Home Assistant

    1. The bulk of the code would be the same. You’d probably need to move the config file path to somewhere modifiable from outside the container, and maybe tweak the dockerfile slightly, then you could just run it as a standard container.

      1. Hi Mike,

        I’m having the Actron Que system installed next Tuesday. I’m a Hubitat hub user myself so would prefer control via that, but will setup Homeassistant on my Synology NAS if needed.

        You mentioned capturing info for the new Que – let me know what you need and I’ll try and make it happen to enable Que support.


  1. OK. I’ve installed in a docker container on RPi3 running Raspbian Lite. Previously I used the python virtual environment install for HA but you don’t get the add-on store with that option and I wanted to get my Actron Connect working with Siri ASAP. If anyone else is running HA and wants to switch to but running on Raspbian Lite, the guide for doing this is here: (there were a few RPi specific issues with the directions in that link; I’ll elaborate on the fixes for them once I get this working).

    I also setup dnsmasq on my Netgear R7000 running merlin xwrt-vortex firmware. Once I had that setup I put a DNS redirect on the router so those two urls point to the server.

    Installed the add-on from the store. Reconfigured all of my existing HA devices…. this took a while. I got a call from my wife to open the garage door because Siri wouldn’t do it for her – had to get up and do it manually. First world problems.

    Now, it looks like Actron Connect is talking to MQTT as per the logs:

    09-01-2019 19:06:51.71 DeviceController.Data() Client: ::ffff:
    09-01-2019 19:06:51.87 DeviceController.Data() Data: {“G”:”0″,”V”:2,”D”:6,”DA”:{“isOn”:true,”mode”:2,”fanSpeed”:2,”setPoint”:25.0,”roomTemp_oC”:25.0,”isInESP_Mode”:true,”fanIsCont”:0,”compressorActivity”:2,”errorCode”:””,”individualZoneTemperatures_oC”:[26.1,26.1,26.4,25.9,25.6,26.5,25.4,25.0],”enabledZones”:[0,0,0,0,0,0,0,1],”liveTimer”:null}}

    However I’m not seeing a climate component showing up on the overview screen. Do I need to add something to configuration.yaml?

    Thanks Mike!!

    1. Well, the add-on is hearing from the air conditioner which is good. MQTT on the other hand – not necessarily.

      What MQTT server are you using? The default configuration of the add-on is to use ‘core-mosquitto’ which is the internal network name for the mosquitto MQTT add-on. Does the MQTT addon show the air conditioner add-on log in to it?

      1. Fantastic! Got this up and running with a bit of debugging with Mike’s input (had to add MQTT discovery option to configuration.yaml). Amazing to have HA / Siri integration to control the Actron A/C and also discarding the slow and unencrypted cloud integration. Thanks for your impressive work on this add-on Mike.

  2. Thanks for your work Mike, incredible improvement to Home Assistant, and delivered where Actron wouldnt. I know, I tried asking.

  3. Thanks, this is awesome! Managed to get the docker container running on my Synology communicating with mosquitto (docker) to Home Assistant (docker) which in turn is also connecting to HomeKit. Can now ditch the Actron Connect iOS app and not have to worry about the online service being shut down. I additionally used the reverse proxy feature of the Synology to forward to the port 80 web service.
    One question though is there a way to set the fan speed to ESP and the additional ‘const’ modes?

    1. Glad you’re getting some use from it! Unfortunately even the original iOS app to my knowledge couldn’t set ESP mode. It can report on ESP mode, but it didn’t seem to have the option to change it.

    2. Hi Andreas,
      I am completely new to Home Assistant, but was am keen to get exactly what you have working too.
      I have Home Assistant installed as a docker image on my Synology NAS. But how do I get Mike’s add-on working with this?
      Can you point me to a blog or something?
      Any help is much appreciated!

      1. I guess my question is how do I install this add-on as a docker container on my synology nas?

      2. Basically you install it as you have installed the Home Assistant Docker container on the Synology NAS through the Docker app.
        The container for a + series Synology NAS is ‘mikejmcguire/mikejmcguire-hass-actron-amd64’
        You must specify:
        Volume: Mount path ‘/data’ to a folder where you’re keeping the configuration file
        Port Settings: Local Port: 8186; Container Port: 80

        Inside the folder you pointed ‘/data’ to you need to make a file called ‘options.json’. below is mine:
        “MQTTPassword”:”{your password here}”,
        “Zones”: [
        “Id”:4,”Name”:”Master Bedroom”
        “Id”:5,”Name”:”Bedroom 2″
        “Id”:6,”Name”:”Bedroom 3″

        This also brings up the point you need to setup an MQTTBroker Docker container too, I used Mosquitto .
        One thing I have noticed are that the commands sent to the Airconditioner are a bit laggy, can take 30 seconds to make a change. Also the Actron modules don’t show up under the MQTT integrations like other MQTT items.

  4. Hi Andreas,
    Many thanks for your reply!

    I have a mosquitto mqtt container up and running, and with your instructions, I now have the actron container running too. Couple of questions:

    How do I integrate the actron container with the home assistant container? Do I need to update the configuration.yaml file?

    I am going to have a problem setting the two required dns entries to point back to my home assistant container. I am using an eero router which does not support setting ip addresses for hostnames. Any ideas? I am thinking maybe another docker container that I can then use as a dns server.

    Thanks again for your help

    1. The only thing in the configuration.yaml is “discovery:”
      And in the Home Assistant UI go to ‘Configuration’ -> ‘Integrations’ -> Selected MQTT and add in the MQTT credentials.
      The Actron controls should be auto discovered as ‘climate.air_conditioner’ and the zones should appear as ‘switch.{name}_zone’

      1. I’ve solved my dns host name issue, but still getting no love. Here’s what I have:

        * I have the mikejmcquire-hass-actron-i386 docker container up and running. I am using the i386 image as my synology has an intel cpu. The docker container log shows that it starts up and then every 5 mins does an MQTT.SendMessage() hass-actron/status.
        I set up the options.json file for the actron contrainer. It only has the mqttbroker and zones, as I do not have a username/password for my boker.
        As far as I can tell, this container is working correctly.

        * Mosquitto MQTT is up and running as a docker container. It does not have a username/password, but I think that is OK. I can test it with MQTT.fx and can verify that I can connect, subscribe, and publish updates. I can see that the hass-actron container is connecting as I can see the following docker container log message “New client connected from as hass-actron (c1, k15, u”)”. So I also think that this working correctly.

        * I set up a DNSmasq docker container to allow me to set host names that resolve to my synology ip address. I then set my eero router to use this as the dns server for the whole network. I can correctly resolve the two hostnames in this article as my synology nas ip address. Also the actron app no longer works. So it also seems that this is working correctly.

        * I have my home assistant docker container up and running. It is integrated with my zwave hub, and to apple homekit. So this container is working. I also set up the mqtt integration.

        However, home assistant does not have any climate entities. So it seems that the auto config is not working, or I am missing a step to get the integration working.

        Almost there! Any ideas why the climate entities are not showing up?

        Many thanks!

  5. In the log for the container, are you seeing incoming web requests from the Air Conditioner to the add-on? It should be fairly verbose. If not, check that you’re forwarding port 80 from the nas IP to the container’s port 80. The air conditioner will *only* connect to the add-on on port 80. Based on you only seeing the status message every 5 minutes, you’re probably not getting a feed from the air conditioner itself.

    1. Also. Is MQTT discovery turned on within Home Assistant? You can do that in the configuration file, or the configuration of the MQTT integration. Without that, Home Assistant won’t discover the climate device from the MQTT server. You should be seeing this regardless of whether or not the airconditioenr is sending data to the add-on.

      1. Turning discovery on has allowed the discovery of the devices, so home assistant now has all the AC entities configured correctly.

        However, I cannot control the AC most likely as per Mike’s previous comment, as the AC cannot connect to the container on port 80.

        Last piece of the puzzle! 🙂

    2. I think this is exactly what is happening.

      The container is currently configured as “Port Settings: Local Port: 8186; Container Port: 80” as per Andreas’ suggestion.

      Andreas, if this is taking traffic from port 8186 on the nas and redirecting it to port 80 on the container, then what redirects the connection from the air conditioner on port 80 to port 8186?

      1. It’s working!!!!!

        I re-read Andreas’ original comments and setup reverse proxies for the two hostnames from port 80 to 8186. This is then mapped to port 80 on the container in the container settings.

        Mike, you are an absolute champion for putting this all together. From reverse engineering Actron, to creating a solution for yourself, and then also making docker images available for other people to use. And to make yourself available to answer questions from newbies. A huge thank you!

        Andreas, I want to also thank you for the help you gave me in getting this working. Also a huge thank you!


  6. You’ll either need to change the local port to 80 (recommended), or you’ll need some other network device proxying that traffic for you. Either way, something will need to be listening on 80 for the air con to connect to it.

  7. Hey Mike,

    I’ve spent the last 6 months or so tinkering in python to do what you have done. I have had success getting the actron to do a GET a command from my webserver (which changes the indoor unit) but after a few minutes the GET commands drop off and eventually stop. You mentioned that the airconditioner is probably unhappy about something but I just can’t work it out. I’ve tried to compare what you have done which is obviously more comprehensive than my very non-technical approach but I can’t work it out

    Do you have any capacity to check out my code and see if you can point me in the right direction?

  8. I’ll give it a go in the next few nights. It’s a bit tricky because I have to move some hardware around to do it but I’ll do it and report back


      1. I captured a bit more traffic between the indoor unit and the actron webserver and noticed that I only send the command I want processed ie {“tempTarget”:23} whereas actron’s webserver sends the entire message 4 or 5. Do you think that not getting the entire message might make the device unhappy? I thought the single command might be ok. I’ll do the same now with my webserver and see what happens

      2. Ok so I captured the traffic between the python service and the indoor unit. Its a lot so i’m not sure what is relevant so I’ve pasted a bit but can add more if something is missing:

        I also noticed an error (“Last”:”JsonErr(2)Expected”) at the second endpoint (2.json) :

  9. Mike you’re an absolute legend doing this. I have the addon installed on latest hassio, MQTT broker running fine (using it for tasmota) and enabled MQTT discovery. When I attempt to start the addon I see the following message in the log:

    19-07-24 13:37:15 ERROR (SyncWorker_6) [hassio.docker] Can’t start addon_e4641267_hass-actron: 500 Server Error: Internal Server Error (“driver failed programming external connectivity on endpoint addon_e4641267_hass-actron (edc4148e4ea36203e7…): Bind for failed: port is already allocated”)

    Any idea what’s causing this?

    1. Yep – the bind for means you’ve got another application listening on port 80 – i.e. if you can simply type a hostname/ip into the browser without a :port at the end. You’ve probably got another add-on or something listening on the standard HTTP port. HA listens on 8123 by default. The Actron add-on must be on port 80, as that’s what the air conditioner will try and connect on.

  10. Hi Mike,

    You’re doing a great service here for Actron owners! It’s nice work. I can see the hours and frustration that went into this.

    I have a question for you: Have you figured out how to set the temperature of individual zones (ESP Ultima system)? I have had a 5 min skim through your code and I have a feeling the answer is no, but before I go down the rabbit hole and try to make that work, I thought it prudent to ask if it was something you tried to figure out and whether it was worth me attempting.

  11. Fantastic work Mike, thank you for the add-on – this has finally made me pull the trigger and order an actron connect module. While waiting for it to arrive I’ve installed your add-on in a container built with docker-compose for anyone that doesnt run Hassio and wants to give it a shot (this is for a x64 install):

    version: “3.6”

    context: “”
    BUILD_FROM: “microsoft/dotnet:2.2-runtime”
    image: “mikejmcguire/hass-actron-amd64”
    container_name: “hass-actron”
    – “80:80”
    restart: always
    – PUID=${PUID}
    – PGID=${PGID}
    – TZ=${TZ}

    As Andreas mentioned in an earlier comment you will need to create the options.json and save it in the volume mounted to /data

    Also Mike, judging by your response to Brad’s question on the individual zone temp selection – I’m assuming there will be no to show the individual zone temps and target temps on the ESP ultima systems? If not – is the logging level verbose enough so that I may pick up the temps being sent in the message from the aircon and something you could look at including in the add-on?

    Once again, thanks for all of your work.

    1. Howdy, thanks for the feedback, good that its getting used. Yep – I have sample output now from a system with multiple zone temperature sensors. I just need to do an update that exposes those as sensors. I’ll email you separately – and get you to do the testing for me if that’s alright (mine doesn’t provide per zone temperatures).

  12. Mike, very cool. Thank you!
    I’m running this within hass 0.98.2 on a Synology diskstation. It’s working perfectly, climate control picked up and configured for a 4 zone system.

    One question, there is a long lag from changing a control, doesn’t matter if it’s turning aircon on/off, changing zone or temperature from within HA (lovelace) to it changing on the aircon, I’m guessing up to 40 seconds. This isn’t a major issue but wonder if you have any ideas what might be causing the delay?

    1. Howdy. The acrton connect should be polling roughly every 2 seconds for an updated command. However, the actron connect seems to be quite sensitive to connectivity issues – when I was first developing the add-on and not giving it the answers it wanted in a timely manner, it started polling at a much less frequent page. I’d check to make sure nothing on the synology is interfering with the add-on’s connectivity. Worst case, power off the air conditioner at the breaker box, give it a few seconds and then turn it on again (rebooting the actron connect basically).

      1. Mine also takes up to a minute to update, haven’t looked into it much, just assumed it was a limitation of the implementation. Sometimes it’s instant other times it takes about a minute, but generally always works.

  13. Thanks all.
    No proxy. I will try bouncing the main air conditioning unit to see if a reset of the Actron Connect box resolves it.

    That being said, it’s not a major issues as it does trigger successfully.

  14. Hi Mike
    Thank you for all your time and effort on this project.(can’t believe there sending unencrypted ssid and the passwords from the cloud)
    I’ve just ordered my new ACM2 and have set it up and its working from my iphone.
    I’m running
    hassio 0.99.3
    I’ve installed Mosquitto broker
    Do i have to configure any think in the add-on config before i install your Add-on
    I’m very new to this I’ve read through your blog to try and get as much info as i can and this i what I’m up to
    this was my last resort theres not a lot of youtube tutorials on this subject

  15. Hi Mike,

    Would you be able to share some links to the raspberry pi you tested with or recommend and the image you used for the testing?

    Do you know of any indoor sensors we could use in conjunction to set target tempuratures to automate switching on/off zones?

    I’d like to set this up + a pi-hole to be the DNS server with my Actron as well.

    So if you’re sharing affiliate links I’d be happy to buy through your links.


  16. Awesome work Mike – I followed one of your blog posts on this a while back, but never had the skills to work it out myself.

    We’ve got a Que system, which goes offline when I masq the DNS entries for it, however nothing is appearing in the logs for your component.

    Any starting pointers as to where to look?

    Cheers, Andrew

    (if I can get this working, it’ll finally give me the impetus to move from Hassbian to HassIO)

    1. Howdy, are you able to do a packet capture from the que to the internet, or alternatively, can you see which DNS entries the que is trying to resolve?

      Do you have the updated dns entries in place (I’ve added more to the list since the original post).

      1. I’ll have to see if I can do a capture on my network using wireshark or something… I don’t have any gear where I can span a port and my cable modem from Telstra is next to useless for traffic capture…

        I’ve got all 3 of the DNS entries you have listed in dnsmasq directing them back to the RPi running HassIO …

        not sure if it’s relevant, but the Que runs a massively locked down version of Android

  17. Hi Mike,
    What are you thoughts on the ActronAir BMS card ? Do you think that’s a better option then getting the Actron Connect System and integrating to

    1. Howdy, I’ve no experience with the BMS card, although my understanding was it was designed to use a serial connection to talk to a building management system. Theoretically you’d be able to achieve the same thing with both options, but one is more consumer driven and the other business/industrial. A quick opinion would be that the Actron Connect lets you connect wirelessly, where as the BMS module will need a device (computer or a Pi etc) with the serial connection. Then you’d need some software to translate between the BMS protocol and Home Assistant. All viable options. Just do a bit of checking first if you can find a BMS integration for Home Assistant or any other products you’re looking at.

    1. have stalled a bit with day to day work load and the Christmas Break/Fires but will try and get back to it with Mike once I can

  18. Hi Mike
    Would there be a problem with running pi-hole on the same RPi3 running hassio and the add-on.
    Would the pi-hole let the actron connect through to the hosts.

  19. Thanks Mike yes ive added those in the pi-hole add-on.
    Should the actron entities be discovered in integrations-MQTT when everything is working
    Thanks Again

  20. It’s all good I’m using the Mosquitto add-on so ill have to work out why its not auto discovering
    not sure what to put in the Mqttbroker part in the add-on

  21. Hi Mike its working!! I found the entities in the states/Current Entities page.
    Just can’t see them in the Integration Configuration page under Mqtt: Mosquitto Broker (Just a sonoff device)
    Looks like I can control the Aircon and create a automation only took me 3 months.
    Thanks Again

  22. Thank you so much for taking the time to create and publish this integration. The Action Connect app is an embarrassment but this is excellent!

  23. Hi Mike,
    Thanks for the awesome work. Any suggestions on how to create DNS entries in the Telstra smart gen2 modem to resolve the Actron hosts to the ip address of home assistant? If there is no option on Telstra modems, what are the other possible avenues?

    1. Hi Jade
      My Telstra modem had the no option to modify the hosts names and the DNS settings where locked.
      I had to ditch my Telstra modem and use a AirPort Extreme and installed pi-hole on a
      Raspberry pie
      Just point your DNS to your raspberry pie IP address
      You must reconnect all devices after you run pi-hole.

    2. Howdy, yep – Nick’s reply works. Alternatively – and I’m not sure if this is locked down as well – if you could disable DHCP on the router, and provide your own DHCP/DNS service, then you’d be able to control the DNS lookups.

  24. Hi Guys,
    I am setting this up and just wanted t see if anyone else had this problem. I have an Ultima ESP and just had the WiFi module installed this week.
    I have installed the addon and it is 90% working EXCEPT for zones 5-8 I cannot change the zone on or off status from Home Assistant. I can see the status if I change the wall controller. I can see the temperatures in all 8 zones. However, if I press my icon in Home Assistant it toggles for a while then reverts to the current status. Zones 1-4 work fine. Anyone seen this issue?

  25. Hey All, I am having massive troubles trying to get this working in my HA, reading all the messages i’ve tried the native approch of having Mosquitto as an intergration (But nothing shows up) i’ve also tried manually entering the discovery in the config yaml. But it doesn’t seem to want to show up ?

    1. Hi Ben,
      I’m possibly having a similar issue for the past month or so but haven’t done any proper troubleshooting or research yet due time, I think its possible something has happened with an update in HA.

      My issue is the MQTT messages are being received in HA ok and I can view them by listening in MQTT under developer settings, but the climate entity and associated sensors/switches have gone.

      In developer settings are you able to listen to any messages in MQTT by typing “actron/aircon/fanmode” under listen to topic? you should see a response with the value?

      1. Hey Mick, As mentioned in my reply – i think my problem is i am using the wrong aircon/app as i noticed that i could still control it even with the DNS re-writes in place… I then figured out i was using the “Easy Connect” app insteal of the Actron Connect app.. Which leads me to believe they connect differently! Might need to chat about getting some intagration with this one

      2. Sorry Ben, you replied while i was typing.

        Mike: Not appearing anywhere, even in the entities list under configuration no climate entities or sensors/switches related to it. I can see the aircon is getting to the addon and reporting the values every couple of seconds.

        MQTT logs show both home assistant and the wifi module connecting and I can even look at all the MQTT messages within HA in developer options e.g actron/aircon/zone1 actron/aircon/mode and they all report the correct status within HA but it still isnt appearing as an entity.

        As i mentioned I haven’t looked in depth yet but will try and have a proper look over the next few days.

  26. Would that be due to a move from States to Lovelace for the UI – does it appear under ‘unused entities’?

    Does the actron add-on show that it’s receiving data from the air conditioner?

    Does the MQTT add-on show that its receiving client connections from the actron add-on?

  27. Hi Mike

    Thanks for the add-on, Really cool.

    I got this stupid thing happening where it tells me that all Aircon related entities are read only as their IDs apparently are not unique even though they are.

    Did you come across this one before?



    1. Yep – its some HA functionality introduced a while back for using the GUI to manipulate entities if there’s additional configuration needed. The add-on provides all the configuration for the entities when it registers them. You can still customise the icon etc though through the normal HA customisation area.

  28. Wondering if anyone has come across this, I’ve been using the Actron/HA integration for a year or so without issue. I changed my router last week and hit a problem. I setup the new router with the same SSID and Password, I think the Actron hub has connected to the new router but interestingly I cannot see it under attached devices, that said other devices are not listed which I know are connected.

    In HA the AC and zones are all showing as ‘Unavailable’.

    What’s happening?
    The 4 Actron domains are correctly redirecting to post 80 on HA, I get the following when connecting: Last Update from Air Conditioner: 1/1/0001 12:00:00 am
    I’m using Adgard to do the DNS redirect and can see ‘something’ is trying to connect to the domains and being redirected.
    When listening to a topic of ‘actron/aircon/fanmode’ I get the following response ‘high’
    When listening to a topic of ‘actron/aircon/mode’ I get the following response ‘heat’

    Given I can see something trying to connect to the Actron domains and MQTT is responding I’m guessing the Actron hub is connected to wifi correctly.
    I’ve rebooted the hub multiple times (by hitting the main power to the AC), I’ve also manually connected to the hubs wifi and rest the wifi details.

    Still no luck, any suggestions?

      1. Howdy – have you looked in the log for the HA add-on. You may find its not receiving any requests/data from the Actron Connect. Is your HA server on the same IP address? Do you have the DNS entry as well?

  29. Hi Mike,

    DNS for setup correctly, getting ‘Last Update from Air Conditioner: 1/1/0001 12:00:00 am’ when going to it in browser. HA has the same IP as prior to router change. Nothing obvious in the logs:

    07-09-2020 21:58:43.74 Service.Start()
    07-09-2020 21:58:44.15 Service.Start() RegisterZoneTemperatures: False
    07-09-2020 21:58:44.15 Service.Start() ForwardToOriginalWebService: False
    07-09-2020 21:58:44.16 MQTT.StartMQTT()
    07-09-2020 21:58:44.22 AirConditioner.Configure()
    07-09-2020 21:58:44.34 AirConditioner.Configure() Zone: Master Bedroom, Id: 1
    07-09-2020 21:58:44.35 AirConditioner.Configure() Zone: Cerys Bedroom, Id: 2
    07-09-2020 21:58:44.35 AirConditioner.Configure() Zone: Spare Bedroom, Id: 3
    07-09-2020 21:58:44.35 AirConditioner.Configure() Zone: Livingroom, Id: 4
    07-09-2020 21:58:44.35 Service.MQTTRegister()
    07-09-2020 21:58:44.45 MQTT.SendMessage() homeassistant/climate/actronaircon/config
    07-09-2020 21:58:44.46 MQTT.SendMessage() homeassistant/switch/actron/airconzone1/config
    07-09-2020 21:58:44.46 MQTT.Subscribe() actron/aircon/zone1/set
    07-09-2020 21:58:44.47 MQTT.SendMessage() homeassistant/sensor/actron/airconzone1/config
    07-09-2020 21:58:44.47 MQTT.SendMessage() homeassistant/switch/actron/airconzone2/config
    07-09-2020 21:58:44.47 MQTT.Subscribe() actron/aircon/zone2/set
    07-09-2020 21:58:44.47 MQTT.SendMessage() homeassistant/sensor/actron/airconzone2/config
    07-09-2020 21:58:44.47 MQTT.SendMessage() homeassistant/switch/actron/airconzone3/config
    07-09-2020 21:58:44.47 MQTT.Subscribe() actron/aircon/zone3/set
    07-09-2020 21:58:44.47 MQTT.SendMessage() homeassistant/sensor/actron/airconzone3/config
    07-09-2020 21:58:44.47 MQTT.SendMessage() homeassistant/switch/actron/airconzone4/config
    07-09-2020 21:58:44.47 MQTT.Subscribe() actron/aircon/zone4/set
    07-09-2020 21:58:44.47 MQTT.SendMessage() homeassistant/sensor/actron/airconzone4/config
    07-09-2020 21:58:44.47 MQTT.Subscribe() actron/aircon/mode/set
    07-09-2020 21:58:44.47 MQTT.Subscribe() actron/aircon/fan/set
    07-09-2020 21:58:44.47 MQTT.Subscribe() actron/aircon/temperature/set
    07-09-2020 21:58:44.67 ASPNETCoreStartup.ConfigureServices()
    07-09-2020 21:58:45.57 ASPNETCoreStartup.Configure()
    07-09-2020 21:58:45.95 ASPNETCoreStartup.OnStarted()
    Hosting environment: Production
    Content root path: /app/
    Now listening on: http://%5B::]:80
    Application started. Press Ctrl+C to shut down.
    07-09-2020 21:58:54.16 MQTT.SendMessage() hass-actron/status
    07-09-2020 22:00:22.32 Instrumentation.Status() Client: ::ffff:
    07-09-2020 22:03:54.16 MQTT.SendMessage() hass-actron/status
    (last line keeps repeating every 5mins)

    Given I’m getting a response from ‘actron/aircon/fanmode’ is it safe to say the Actron hub is connected to wifi ok, MQTT is still very new to me!.

    1. Howdy, your MQTT server will have retained previous messages. The logs for the add-on are showing that the Actron Connect is not connecting to the add-on. Suggest confirming that you can see your Actron Connect in a web browser. If the Actron Connect is on the network, you should be able to put its IP in a web browser and confirm.

  30. Mike, the info about MQTT caching old data was the bit of info I needed! Turns out the Actron Connect was not connecting to the new router. It doesn’t seem to like the wifi! Setup the old router just for Actron and were up and running.


    1. Hi Ian,
      I’ve noticed this as well. I set up a Netgear Orbi mesh and can no longer get the Connect controller to connect to the network.
      I’d hate to be running an old router just to connect the Actron. Particularly frustrating since I’m one of those hypothetical people who ran ethernet into their roof becuase they like these things wired.

      Has everyone seen the new Actron controller coming out? Neo Connect.
      It has a different app.

      Curious whether this will work with existing systems and whether they have addressed your previous security concerns, Mike.


      1. Looks like specific systems so assuming not older units. Classic Series 2 and Advance. More info on models supported at bottom of this page:

        Que still seems to be their top of the line system but this looks like a good step up from Connect.

        Perhaps it will use the same or similar API’s as Que – only negative to that is no local controls – the API is accessible by cloud only so it and your internet need to be up.

      2. Yep – I’ve had similar issues when I was testing a new AP – I had to run two for a while. Recently moved to the Unifi stuff and the Actron is happy again. The Actron does seem a bit picky about wifi – it was 2.4 ghz only, wpa2/aes only.

        I haven’t looked into the Neo – I’ll stay on the Actron Connect here as I’m loving the instantaneous comms, but like I did with the Que – if there’s a guinea pig user that’s happy to let me look at their API account, I can probably create an add-on for it. Hopefully it uses the same API as the Que – or at least close to it.

  31. Hi Mike,

    I saw this thread 2 years back, i only have the time to finally do it during this school holiday break! 🙂 first of all this is really massive one for the actron users like us Thanks for that. im still having a bit of an issue here. im using the latest version of homeassistant on a Virtualbox. Mosquitto add on installed on the same HA. but im AC status still unavailable. i have AdGuard on the same HA which is the one that updates the DNS for these actron domains. ive reloaded the Home assistant too many times.

    this is the log i can see on my Actron addon..

    07-10-2020 20:17:46.86 Service.Start()
    07-10-2020 20:17:47.33 Service.Start() RegisterZoneTemperatures: False
    07-10-2020 20:17:47.33 Service.Start() ForwardToOriginalWebService: True
    07-10-2020 20:17:47.36 MQTT.StartMQTT()
    07-10-2020 20:17:47.46 AirConditioner.Configure()
    07-10-2020 20:17:47.68 AirConditioner.Configure() Zone: Master Bedroom, Id: 1
    07-10-2020 20:17:47.69 AirConditioner.Configure() Zone: Bedroom 2&3, Id: 2
    07-10-2020 20:17:47.69 AirConditioner.Configure() Zone: Living Room, Id: 3
    07-10-2020 20:17:47.69 AirConditioner.Configure() Zone: Study & Media, Id: 4
    07-10-2020 20:17:47.70 Service.MQTTRegister()
    07-10-2020 20:17:47.85 MQTT.SendMessage() homeassistant/climate/actronaircon/config
    07-10-2020 20:17:47.93 MQTT.SendMessage() homeassistant/switch/actron/airconzone1/config
    07-10-2020 20:17:47.94 MQTT.Subscribe() actron/aircon/zone1/set
    07-10-2020 20:17:48.01 MQTT.SendMessage() homeassistant/sensor/actron/airconzone1/config
    07-10-2020 20:17:48.01 MQTT.SendMessage() homeassistant/switch/actron/airconzone2/config
    07-10-2020 20:17:48.01 MQTT.Subscribe() actron/aircon/zone2/set
    07-10-2020 20:17:48.01 MQTT.SendMessage() homeassistant/sensor/actron/airconzone2/config
    07-10-2020 20:17:48.01 MQTT.SendMessage() homeassistant/switch/actron/airconzone3/config
    07-10-2020 20:17:48.01 MQTT.Subscribe() actron/aircon/zone3/set
    07-10-2020 20:17:48.01 MQTT.SendMessage() homeassistant/sensor/actron/airconzone3/config
    07-10-2020 20:17:48.01 MQTT.SendMessage() homeassistant/switch/actron/airconzone4/config
    07-10-2020 20:17:48.01 MQTT.Subscribe() actron/aircon/zone4/set
    07-10-2020 20:17:48.01 MQTT.SendMessage() homeassistant/sensor/actron/airconzone4/config
    07-10-2020 20:17:48.01 MQTT.Subscribe() actron/aircon/mode/set
    07-10-2020 20:17:48.05 MQTT.Subscribe() actron/aircon/fan/set
    07-10-2020 20:17:48.05 MQTT.Subscribe() actron/aircon/temperature/set
    07-10-2020 20:17:48.80 ASPNETCoreStartup.ConfigureServices()
    07-10-2020 20:17:51.88 ASPNETCoreStartup.Configure()
    07-10-2020 20:17:53.89 ASPNETCoreStartup.OnStarted()
    Hosting environment: Production
    Content root path: /app/
    Now listening on: http://%5B::]:80
    Application started. Press Ctrl+C to shut down.
    07-10-2020 20:17:57.36 MQTT.SendMessage() hass-actron/status
    06-10-2020 07:09:30.29 UpdateController.Log() Client: ::ffff: Message: Link Started:V0.18G
    06-10-2020 07:09:35.09 UsageController.Log() Client: ::ffff:
    06-10-2020 07:09:35.16 UsageController.Log() [0x00000000] Log Entry: The air conditioner was turned on locally.
    06-10-2020 07:10:43.07 UsageController.Log() Client: ::ffff:
    06-10-2020 07:10:43.63 UsageController.Log() [0x00000000] Log Entry: The air conditioner was turned on locally.
    06-10-2020 07:11:11.54 UpdateController.Log() Client: ::ffff: Message: Link Started:V0.18G
    06-10-2020 07:12:16.21 UsageController.Log() Client: ::ffff:
    06-10-2020 07:12:16.22 UsageController.Log() [0x00000000] Log Entry: The air conditioner was turned on locally.
    06-10-2020 07:12:44.10 UpdateController.Log() Client: ::ffff: Message: Link Started:V0.18G
    06-10-2020 07:13:49.84 UpdateController.Log() Client: ::ffff: Message: Link Started:V0.18G
    06-10-2020 07:14:12.12 MQTT.SendMessage() hass-actron/status
    06-10-2020 07:15:36.92 UsageController.Log() Client: ::ffff:
    06-10-2020 07:15:37.58 UsageController.Log() [0x00000000] Log Entry: The air conditioner was turned on locally.
    06-10-2020 07:15:42.38 Instrumentation.Status() Client: ::ffff:
    06-10-2020 07:15:46.62 Instrumentation.Status() Client: ::ffff:
    06-10-2020 07:15:47.72 Instrumentation.Status() Client: ::ffff:

      1. Power on/off not working in HA? HA doesn’t really have an on as such, but rather a mode. So you can set it to heat, cool, fan, off for example. Does that help?

  32. hi Mike yes. on off button is not working for me. yeah i can change the mode. the fan mode turn off and on the Console On/OFF LED, you can still hear the fan is on. Im not sure if this is the expected behavior.

  33. @Mike J McGuire – you mention (back in October) that you moved to Unifi. Can i ask, are you running the DNS redirects on the unifi gear, if so, what gear? I have a udm pro and just dont know where to start with the dns stuff… should i be looking at the NGINX addon you have available, OR, creating rules in the udmpro’s firewall, or even PiHole…

    Any help would be greatly appreciated.


    1. Howdy – I did – and just moved to a UDM Pro as well. Having said that, both DHCP and DNS are handled by a Windows server – I don’t use the networking equipment to provide those services. .

      For the UDM Pro, when you configure the DHCP settings (on the network configuration page), you’d need to specify manual DNS servers and point them to something that gives you a bit more control – like PiHole. Then you could implement the custom DNS there. Your DHCP clients will the use that for DNS (including the Actron Connect). Let me know how you go.

      1. Thank you for the prompt response and info. I understand exactly what you mean and will look to configure an instance of piHole.

        Thank you and I will let you know how it goes when i get to do it, (start of the new year).

  34. Hi mike, thanks for this add-on, I have finally installed the latest version of HA Image onto a Pi-4 and have been successful to get your add-on running. I have PiHole running so DNS is working as it should. The main reason for doing this is so I can automate the turning on and off of my Actron depending on time, say after 0700 and up to 2200Hrs and this is also dependant on the temperature in one zone.
    I am very GREEN to HA, this being my first install other than a quick look a couple of years ago, but I need some help on the automation side.
    I’m not sure exactly how to go about doing this so I thought I would first ask here seeing as it is strictly Actron related. I will look at lighting automation later as this is not my priority.

    What I want to do is the following but not sure in what order or exactly how to go forward.
    If it is after 0700 and before 2200 and the temperature in Zone xyz is above 32 degrees then turn on Zone xyz, turn off all other zones, then turn on AC.
    If it is after 0700 and before 2200 and the temperature in Zone xyz is below 26 degrees then turn off AC.

    If you or someone can help me with that as a start, for setting up the Automation, Scenes, Scripts then I should be able to sort out any further mods as I go (hopefully)


  35. Hi Mike,

    I had your addon working with my Pi Homeassistant setup for around 3 months. All working great and hooked into Amazon Alexa 🙂

    Then we had an issue with our Aircon which required a replacement of the both indoor and outdoor units, however the Wireless module was compatible with the new unit. Both units are identical in terms of models. However, obviously my new replacement unit is from 2020 rather than 2018. Since it was replaced I can no longer see my Actron status from Homeassistant. Just wondering if there is any extra information I could possibly show you to see if somehow my new model might not be compatible with your Actron module?

    Looking at my Actron Log I can see these messages:
    15-04-2021 01:39:03.71 MQTT.SendMessage() hass-actron/status
    15-04-2021 01:40:58.53 UsageController.Log() Client: ::ffff:
    15-04-2021 01:40:59.00 UsageController.Log() [0x00000000] Log Entry: The air conditioner was turned off locally.

    Which too me would indicate that its receiving the information but then maybe having issues parsing the information through the MQTT back to the Homeassistant interface?

    As long as I see the above logs in the Actron log, am I right in assuming its all working correctly from the air con to homeassistant?

    I’m kinda stumped on it being a MQTT issue I’ve tried reinstalling it a bunch of times the same way I originally set it up and I just cant get it to function.

    If you have any suggestions i’d really appreciate it.

    My MQTT shows some of these messages:
    1618414434: New connection from on port 1883.
    [01:33:55] INFO: [INFO] found mqttuser1 on local database
    1618414435: New client connected from as hass-actron (p2, c1, k15, u’mqttuser1′).
    1618414456: New connection from on port 1883.
    [01:34:16] INFO: [INFO] found homeassistant on local database
    1618414456: New client connected from as auto-0F09854F-94E2-6153-8059-4D730645A9C3 (p2, c1, k60, u’homeassistant’).
    1618414456: Client auto-0F09854F-94E2-6153-8059-4D730645A9C3 disconnected.
    1618414456: New connection from on port 1883.
    1618414456: New client connected from as 0i90A78Y8UuP9jCcCXHLsw (p2, c1, k60, u’homeassistant’).



    1. Howdy – do you have all of the URLs redirected as specified above? If its an older deployment, you may not have the newer DNS entry. If that’s not the issue, you may need to re-register the Actron Connect (use the app to reconfigure it). Let me know how you go.

  36. Thanks for coming back Mike,

    Yup all DNS entries are valid and working (its an older system, but I actually only set it up with your HomeAssistant addon in the past 4 months).

    I’ve reregistered the ActronConnect App (without the DNS entries first up) that’s gone through OK. However I’m still getting the same result.

    Because I see logging information in the Actron Addon I feel like it is talking to the HomeAssistant Addon on Port 80 (I’ve also confirmed port 80 is responding with OK in chrome).
    15-04-2021 12:29:03.71 MQTT.SendMessage() hass-actron/status
    15-04-2021 12:34:03.71 MQTT.SendMessage() hass-actron/status
    15-04-2021 12:34:36.63 UsageController.Log() Client: ::ffff:
    15-04-2021 12:34:36.65 UsageController.Log() [0x00000000] Log Entry: The air conditioner was turned off locally.
    15-04-2021 12:34:47.03 UpdateController.Log() Client: ::ffff: Message:
    15-04-2021 12:37:00.33 UsageController.Log() Client: ::ffff:
    15-04-2021 12:37:00.35 UsageController.Log() [0x00000000] Log Entry: The air conditioner was turned on locally.
    15-04-2021 12:39:03.71 MQTT.SendMessage() hass-actron/status
    15-04-2021 12:44:03.71 MQTT.SendMessage() hass-actron/status

    I feel like it might be something with MQTT or how its reading the payload information. Looking at the Devices I can see the MQTT Actron Air Conditioner, but I see everything with a status of offline:
    Subscribed topics:
    10 most recently received message(s)
    Received 12:09:03 PM
    QoS: 0
    Payload: offline
    Received 12:14:03 PM
    QoS: 0
    Payload: offline

    All the zones appear switched off, when they are on at the panel. All of the entities have a red exclamation mark on them to indicate they are not contactable.

    I wasn’t sure if maybe I needed some some how flush out any existing MQTT configurations, that still exist if you just delete the addon and reinstall it?

    The other thing I don’t think I’ve seen before is I have 2 Actron devices:
    1. Actron from MQTT
    2. Actron from Home Assistant Supervisor

    The 1st seems to be the air con device as mentioned above with no payload information
    The 2nd contains 3 options around firmware versions

    I was thinking maybe that was in a recent version update you did, I don’t think I’ve seen that in previous versions.

    I do appreciate any further support you could provide, happy to provide any logs or other information if its helps point to a solution.

    Many thanks,


  37. Yep, you’re getting messages from the device on UsageController.Log() but not DeviceController. That means the device is using the entry, but not the entry. That’s the one that provides all of the info. I’ll contact you privately and get you to send me some info from your AC.

  38. Strangely enough I needed to reboot my entire Air Conditioner system (from the main distribution board) as it must of had a cached DNS Record which it wasn’t releasing. Since the reboot, I reactivated the ActronConnect module and I was off and racing!

    Massive thanks to Mike for reaching out and providing some support. Huge thanks mate!

    1. Mike, great work you’re putting into the add-on – I’ve been using it for a few months now and it’s saved me a few times when I forgot to switch off the air conditioning and had to do it from work!! I’ve also set up lots of scripts, one to start it in the morning when it’s cold. So big thank you to Mike.

      Only problem is that my home assistant installation on Pi 3 stopped working and, unable to work out the issue, I bought a Pi 4 and started an install there. I had the exact same issue as Ash and was pulling my hair out trying to figure it out. But Ash’s solution did it for me. Went to the fuse box outside the house, stopped the power to the Actron for 10 seconds and BAM… it worked! I would never have thought of that so thanks to Ash as well.

      1. Hi Gents
        How about a mention of a Aircon reboot in the Add-on Info section in Home Assistant

  39. Hi Mike, I stumbled on your blog several years ago when you first hacked the Actron Connect. Since then “Hey Siri turn on the AC has been on the to-do list. I finally got a bit of time this week and spent a few late nights working on it. First setting up pi-hole as DNS server (and DHCP server since my ISP locks down the DNS settings on the router), then setting up home assistant, installing your add-on and integrating with Homekit. Now the vision is reality “but I couldn’t have done it without you, you first class legend. ‘Hey Siri, buy Mike a case of beers’

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s