Cheers for that info back from both you guys! 
I was able to tweak my search terms to find the right info in the manual haha and spoke to my air con guy to get him back out next week to make the setting changes with the Daikin controller, Iāll probably turn both heat and cool fan cycles off. Cheers!
1 Like
Heating is fine to do with as it prevents cold drafts.
Donāt do it for cooling as you need airflow when the system cycles off. The default setting for cooling is set fan speed but for zoned systems setting it to LL setting is fine just donāt make it go off.
1 Like
I think LL means ālow lowā. For us without a bypass damper that didnāt work well, it still pushed air through the one north facing bedroom we were trying to cool which basically pushed warmer air through which defeated the point of trying to cool it.
I have just discovered something really weird with my AirTouch 5 - the main unit temperature is tracking a zone sensor!
- The Family Room Temp and main unit temp were tracking each over - exactly (when observed over the last 10 days).
- I poked-around on the console including into Installer Mode, but didnāt change anything
- I turned the aircon on (heat) and now the main unit temperature is the same as the Study Temp - but which is following the other?
- I blew the heat gun at the Study Temp sensor and the temperature shot up to 50 degrees - and so did the main unit temp (so the main unit is tracking the study temp now)
- I disabled the Polyair Airtouch custom integration and restarted HA - the main unit temp is still tracking the Study Temp (so nothing to do with the integration)
- I re-enabled the custom integration and nothing changed.
- I restarted the Airtouch console and nothing changed
Obviously the system is not going to work too well in this situation!
If your using it in economy or auto thatās what itās meant to do, it follows the on zone with the biggest gap between the setpoint and room temperature.
This what the control sensor is.
When you tap that temperature reading which is the one next to the main setpoint it tells you which room itās following.
Auto, once all the setpoints are reached it reverts back to the AC units indoor sensor.
Nothing follows each other.
thanks for that explanation. I knew it worked on the zone with the biggest difference, but hadnāt realised the operation was so visible, and thought the displayed main unit temperature was the actual return air temperature. (And was confused when it picked the zone with the biggest difference - even when the zone was way over itās setpoint (after being heated by a hot air gun))
The actual return air temperature doesnāt seem to be exposed by the integration - is that correct?
Many people donāt understand how that works/what itās showing. You also press and hold that temp reading for 5 seconds and it will pop up with the control sensor select option.
Donāt think itās exposed, the Airtouch only uses it when in fresh mode, Control sensor is set to AC or Auto.
Correct, the return air temperature is not available in the API. The control sensor name isnāt officially available either, so neither of them are available in the Home Assistant integration. I donāt think the return air temperature is even visible on the AirTouch console anywhere unless it is the current control sensor in Auto mode.
Been using the integration for a while, one thing I reckon would be handy to have exposed to HA is the current % the dampers are opened at any one time.
I have temp sensors in my zoned rooms, so I see the temp displayed on the main airtouch unit. But a few times Iāve wanted to see what the actual damper % was open - cases where a room has reached and is above the target temp but Iāve felt air still coming from the duct - had to go to the airtouch and login to the service and look at what the damper % was.
If youāre using the custom integration, there are sensors that show the current damper percentage
My main dashboard exposes the damper percentages so I can see them easily. I can share this if anyone wants it, I took a dashboard someone else made and extended it.
I also have some automations that do things like close down dampers if the room is 0.25C over the setpoint and the damper is relatively wide open. This shows how to access damper percentages. I have some more example automations here.
alias: ATP Master Overheat Fix
description: >-
If room is 0.3 degrees over setpoint reduce the damper
triggers:
- trigger: state
entity_id:
- climate.pa_master
attribute: current_temperature
conditions:
- condition: state
entity_id: climate.pa_daikin
state: heat
- condition: state
entity_id: cover.pa_master_damper
state: open
- condition: numeric_state
entity_id: cover.pa_master_damper
above: 42
attribute: current_position
below: 105
- condition: state
entity_id: climate.pa_master
attribute: control_method
state: temperature
- alias: Temperature is > 0.25 degrees above setpoint
condition: template
value_template: >-
{{ state_attr("climate.pa_master", "current_temperature") -
state_attr("climate.pa_master", "temperature") > 0.25}}
actions:
- alias: Reduce damper position
action: cover.set_cover_position
data:
position: 35
target:
entity_id: cover.pa_master_damper
- alias: Set room back to temperature control
metadata: {}
data:
temperature: "{{ state_attr('climate.pa_master', 'temperature') }}"
target:
entity_id: climate.pa_master
action: climate.set_temperature
mode: single
This card is nice want to send me your yaml on that?
Also if anyone is melbourne based and struggling with their install/wants amendments to their installs give me a ring Chirnside Air & Electrical happy to help out where i can. Iām cluey with HA and airtouch
Someone in Melbourne thatās knows what they are doing? They would be a first 
Iām always looking for people to do bypassās and installs for me down that way but they all seem to be clueless. Happy to send you some stuff potentially
Sure, Iāve just put it here on Github.
Best read the readme. Iāve left in the controls for the countdown timer, which wonāt work without an AppDaemon app I havenāt published, so probably best to remove that section.
Ah thanks for this, didnāt realise this existed and was using the built-in. Any reason I couldnt setup this side by side before transition over to line up my dash cards etc? Any reason they could conflict of both are active for short period?
There shouldnāt be any problems running them side by side since they use different domains and all of the state is on the AirTouch console. The entity names may come out a bit weird, but you can always rename them later.
1 Like
Has anyone built a dashboard to access the Airtouch on and off timers from Home Assistant theyād be willing to share? Iāve already built my own off timer, but Iād like to use the Airtouch feature if possible.
I was thinking of creating a dashboard that let me set the mode without turning the system on, and having some kind of interface to allow me to set the Airtouch to come on in X minutes or at a specific time. If someone else has already done it that would save some time.
Though I have to say, Gen AI is getting pretty good at Home Assistant actions and dashboards, it might do most of the work for me. Recently Claude created a moderately complex Grafana dashboard for long term monitoring of my solar panel output, I didnāt have to write a single line of code 
I just use Mushroom Entity Cards for the on and off timer entities and gave the off timer card a tap action that sets the timer in 30 minutes. Opening the details page for the time entities lets you enter an exact on/off time.
Dashboard looks like this:
Timer entity cards are:
type: custom:mushroom-entity-card
entity: time.panasonic_off_timer
name: "Off"
tap_action:
action: perform-action
perform_action: script.panasonic_off_timer_30_minutes
target: {}
icon: mdi:clock-end
Which calls this script:
action: airtouch.set_timer_from_delay
metadata: {}
data:
delay:
hours: 0
minutes: 30
seconds: 0
target:
entity_id: time.panasonic_off_timer
1 Like
Interesting, thanks Ben. I wanted more direct control from one dashboard, so I built a power control dashboard that uses with the Airtouch built in timers via your component. I probably wonāt use it quite like this, Iāll integrate the parts I need into the main dashboard, but I put it all together so others could use it like this if they wanted to.
If anyoneās interested I can put it up on GitHub, once I test it a bit more. To use it youād need a couple of custom components, and to edit the configuration to add some input fields and sensors, plus thereās four automations and two scripts to wire it all together. AI couldnāt write the dashboard for me, but it made it a bit faster to create some of the blocks.
Iāve put my Airtouch Timers dashboard and related automations / scripts / config changes onto Github. Itās new so thereās probably bugs, but it works ok. Comments / pull requests welcome.
