Actron Que and Home Assistant

Sheldon: “I’d love to, but I’m too busy falling back in love with Windows 98.”
Leonard: “Seriously? You haven’t used this desk in years. The second I want to get rid of it you’re up here working.”
Sheldon: “I can’t talk right now. I have several thousand updates to install.”

I’m very pleased to say that the add-on I created to enable the Actron Connect module to be accessed from Home Assistant has been getting quite a bit of use, not only by myself. However, Actron now have a new device available called the Actron Que. I’ve had a couple of queries now about having an add-on/integration for Que and Home Assistant, so I’ve decided to create a new add-on to interface between those systems.

I’m only just starting on it, so it will be in beta for a few weeks. I don’t have a Que at home, so am reliant on some kind souls temporarily giving me credentials to their Que system for a bit of testing. Please feel free to volunteer if you’d like to help.

I’ll update this page as the add-on progresses. At this stage, it looks like the add-on will simply be accessing the Que API on the cloud service, and registering an air conditioner entity with temperature, compressor state, fan speed, mode etc; a series of switches – one per zone; and potentially a series of temperature sensors – if you have a different temperature sensor per zone. As such, you’ll need to configure the add-on with the credentials for your Que account.

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 – just ensure you have discovery enabled.

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.

Installation

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: https://github.com/MikeJMcGuire/HASSAddons. It should install fairly quickly, the add-on is about 200mb.

Untitled

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.

You will also need to specify:

  • Your Que username and password.

Development Update (23 Aug v0.18):

  1. Create authentication/token system – done.
  2. Retrieve current state of the AC – polling every X seconds, and display that data on a climate entity in Home Assistant – done.
  3. Retrieve current state of the zones – polling every X seconds, and display that data on switch entities in Home Assistant – done.
  4. Push changes from Home Assistant’s climate or zone switch entities back to the Que web service – done.
  5. Change from polling to an event based service – assuming the Que service provides an event feed, or HTTP long poll type capability so that the add-on reflects changes instantly without the constant polling – in progress.
  6. After submitting a change (i.e. on/off, temperature, zone), the add-on should pull new events from the cloud service at a much faster rate until the changes are acknowledged. This should shorten the time it takes to update HA – done.
  7. Provide an option for a per-zone climate entity in HA to enable the adjustment of the set temperature per zone – done.
  8. Provide an option for specifying the Que Serial number if you have multiple Que units on your account – done.
  9. Register all of the MQTT entities against a single device, so that the HA reflects them on the MQTT integration page – done.

The add-on has been compiled for all platforms and uploaded, so its available for testing. If you need to get in touch due to an issue with the add-on, leave a comment below and I’ll reach out.

Other notes:

  • It is currently polling for events/changes every 30 seconds, however this is now configurable. The add-on only asks for new events so its not downloading a full 20k status, but rather 600 or so bytes if there are no changes to report.
  • The add-on will now auto-discover the serial number of the Que unit, and auto-discover the zone count and zone names. If you were to add/remove a zone, simply restart the add-on to discover the zone changes.
  • You will need to set the PerZoneControls configuration option to true in order to see the per-zone climate entities.

Update (12/02/2021): The add-on now supports the Neo unit as well – see here for details.

Update (28/05/2021): The add-on now supports MQTT on alternate ports, and TLS security for the MQTT communications.

Update (26/07/2021): If your MQTT entities are not being discovered by Home Assistant, ensure that the add-on is authenticating to your MQTT server (you’ll need to specify a valid user name and password).

Update (31/07/2021): Added an entity to represent the current humidity reading at the controller.

Update (30/08/2021): Added entities for outdoor temperature, compressor capacity and zone positions. Zones that are off will also now receive temperature set point updates. Thanks @DanielNagy for the information.

Update (02/12/2021): Added some self-healing to the add-on to accommodate client devices being unregistered through the Actron portal, or by Actron support. The add-on will retry for 10 minutes before attempting to reregister itself.

Update (07/12/2021): There’s a new behaviour observed with a Neo unit that doesn’t report event changes or incremental changes to its status. The add-on will now auto detect that behaviour and switch to full status polling every 30 seconds (and on change initiated through Home Assistant). Hopefully this is a one off device issue as polling instead of being event driven is a less optimal solution – it’s slower to reflect changes and it consumes more data.

~ Mike

133 thoughts on “Actron Que and Home Assistant

  1. Hi Mike

    Sorry to be a pain. I still can’t see it to be accepting any commands. really appreciate your time and any help you can provide!

Leave a Reply to John Cancel reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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