Thanks Marian. Yes the sensors seem to read ok.
Iāve just a had a look at my HA instance this morning, and it seems the integration lost connection with the Airtouch panel at some point. This is running v1.4.3. My logs have been flooded with:
2022-07-06 21:16:39 ERROR (MainThread) [custom_components.polyaire.airtouch4] Connection error in receiver!
and then later on
2022-07-07 19:10:49 ERROR (MainThread) [custom_components.polyaire.airtouch4] Error sending message! Deleting existing connection and retry sending in 5 seconds...
The wierd thing is, between 5pm and 10pm on the 6th, the ITCs were still updating the tempratures inspite of the the error messages in the logs. Unfortunately I donāt have the debug level wound up at the moment, so thats all I have in the logs.
The other thing I have just noticed is, since updating to 1.4.3, the turbo zone sensors have appeared (one for each zone), but the spill zone has not appeared.
My integration stopped updating ITC sensors for the period when the AC was off overnight.
On a separate note I found that many of the āConnection error in receiverā messages coincide with my NodeRed flow that tweaks a temperature setting by 0.1 degree up then down in one zone in an attempt to keep the ITC sensors updating.
If this is helpful hereās the log showing when I manually changed a program setting on the tablet (turning off a program that was only temporarily on).
2022-07-08 12:41:27 DEBUG (MainThread) [custom_components.polyaire.airtouch4] Message received with expected header!
2022-07-08 12:41:27 DEBUG (MainThread) [custom_components.polyaire.airtouch4] Message received with unknown type: 0x3d
2022-07-08 12:41:27 DEBUG (MainThread) [custom_components.polyaire.airtouch4] b'\x01\x01\x00 \x00\x7fMyProg\x00\x00\x00\x07\x00\x00\x00\x00\x00\x00\x00\x01\x00\x08\x00\x11\x1a\x14\x00\x80\x00\x1a\x1a\x80\x00\x01\x00Program2\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x80\x00\x1a\x1a\x80\x00\x80\x00\x1a\x1a\x80\x00\x02\x00Program3\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x80\x00\x1a\x1a\x80\x00\x80\x00\x1a\x1a\x80\x00\x03\x00Program4\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x80\x00\x1a\x1a\x80\x00\x80\x00\x1a\x1a\x80\x00\x04\x00Program5\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x80\x00\x1a\x1a\x80\x00\x80\x00\x1a\x1a\x80\x00\x05\x00Program6\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x80\x00\x1a\x1a\x80\x00\x80\x00\x1a\x1a\x80\x00\x06\x00Program7\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x80\x00\x1a\x1a\x80\x00\x80\x00\x1a\x1a\x80\x00\x07\x00Program8\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x80\x00\x1a\x1a\x80\x00\x80\x00\x1a\x1a\x80\x00'
2022-07-08 12:41:27 DEBUG (MainThread) [custom_components.polyaire.airtouch4] Message received with expected header!
2022-07-08 12:41:27 DEBUG (MainThread) [custom_components.polyaire.airtouch4] Message received is AC message!
2022-07-08 12:41:27 ERROR (MainThread) [custom_components.polyaire.airtouch4] Connection error in receiver!
2022-07-08 12:41:27 INFO (MainThread) [custom_components.polyaire.airtouch4] Message receiver lost connection, trying to reconnect...
2022-07-08 12:41:27 INFO (MainThread) [custom_components.polyaire.airtouch4] (Re)connecting...
2022-07-08 12:41:27 DEBUG (MainThread) [custom_components.polyaire.airtouch4] open socket connection to the airtouch...
2022-07-08 12:41:28 INFO (MainThread) [custom_components.polyaire.airtouch4] (Re)connected!
2022-07-08 12:41:28 INFO (MainThread) [custom_components.polyaire.airtouch4] Message receiver task (re)started...
And another pattern of the āConnection error in receiverā message that is pretty frequent in the logs. It always follows a list of all the zones like this:
2022-07-08 12:50:33 DEBUG (MainThread) [custom_components.polyaire.airtouch4] Message received with expected header!
2022-07-08 12:50:33 DEBUG (MainThread) [custom_components.polyaire.airtouch4] Message received is AC message!
2022-07-08 12:50:33 DEBUG (MainThread) [custom_components.polyaire.protocol] Updated AirTouchACStatus 0 status, calling: <bound method Entity.async_write_ha_state of <Entity ITC Kitchen: auto>>
2022-07-08 12:50:33 DEBUG (MainThread) [custom_components.polyaire.protocol] Updated AirTouchACStatus 0 status, calling: <bound method Entity.async_write_ha_state of <Entity ITC Dining: auto>>
2022-07-08 12:50:33 DEBUG (MainThread) [custom_components.polyaire.protocol] Updated AirTouchACStatus 0 status, calling: <bound method Entity.async_write_ha_state of <Entity ITC Blue: off>>
2022-07-08 12:50:33 DEBUG (MainThread) [custom_components.polyaire.protocol] Updated AirTouchACStatus 0 status, calling: <bound method Entity.async_write_ha_state of <Entity ITC Study: auto>>
2022-07-08 12:50:33 DEBUG (MainThread) [custom_components.polyaire.protocol] Updated AirTouchACStatus 0 status, calling: <bound method Entity.async_write_ha_state of <Entity ITC Green: off>>
2022-07-08 12:50:33 DEBUG (MainThread) [custom_components.polyaire.protocol] Updated AirTouchACStatus 0 status, calling: <bound method Entity.async_write_ha_state of <Entity ITC Orange: off>>
2022-07-08 12:50:33 DEBUG (MainThread) [custom_components.polyaire.protocol] Updated AirTouchACStatus 0 status, calling: <bound method Entity.async_write_ha_state of <Entity AC Fujitsu: heat>>
2022-07-08 12:50:33 DEBUG (MainThread) [custom_components.polyaire.protocol] Updated AirTouchACStatus 0 status, calling: <bound method Entity.async_write_ha_state of <Entity ITC Master: off>>
2022-07-08 12:50:33 DEBUG (MainThread) [custom_components.polyaire.protocol] Updated AirTouchACStatus 0 status, calling: <bound method Entity.async_write_ha_state of <Entity ITC Lounge: auto>>
2022-07-08 12:50:33 ERROR (MainThread) [custom_components.polyaire.airtouch4] Connection error in receiver!
2022-07-08 12:50:33 INFO (MainThread) [custom_components.polyaire.airtouch4] Message receiver lost connection, trying to reconnect...
2022-07-08 12:50:33 INFO (MainThread) [custom_components.polyaire.airtouch4] (Re)connecting...
2022-07-08 12:50:33 DEBUG (MainThread) [custom_components.polyaire.airtouch4] open socket connection to the airtouch...
2022-07-08 12:50:33 INFO (MainThread) [custom_components.polyaire.airtouch4] (Re)connected!
2022-07-08 12:50:33 INFO (MainThread) [custom_components.polyaire.airtouch4] Message receiver task (re)started...
- you donāt need to keep the ITC sensors updating
- well maybe you do. the ITC sensors are updating as long as the AC is on.
- 0.1 might be a problem, the target temperature is integer. If you need this running, use 1C/
Until afirmware update fixes the issue with ITC not updating temperature, I am doing ITC temperature update when the AC updates the temperature. So having the AC off => no AC temp update => no ITC temp update. It doesnāt bother me so much as this is temporary and should be fixed by Polyaire.
@spry-salt do you have 2 ACs ? I see ACStatus update calling AC Fujitsu, which is wrong.
Just one AC. Thatās how it auto-configured.
EDIT: Just deleted it and recreated it, same result. Itās automatically called ac_fujitsu.
Has anyone noticed performance issues with this latest version installed ?
I previously had the official integration installed - disabled it on Wednesday last week and installed 1.4.3 through the custom repository.
Running HA on a VM using HassOS 8.1 and Core 2022.7
The old integration had been running for about 3 months with no problems at all.
Installed @mihailescu2m version and disabled the other integration and both my app on my Android Phone, App on Ipad and the Main Android Console are all very slow to respond to commands etc.
I have just disabled @mihailescu2m integration, restart the VM that HA is on and then rebooted the Airtouch console and it is responding again as are the Apps on the phone and IPAD.
I will leave it for the rest of today and see if it glitches again before i re-enable the integration and try again.
Craig
Craig @craigcurtin what is going slow? What did you disable on your phone? You should only need to disable the integration in one place, on your VM. Did you restart your HA and Airtouch to see if that helped?
Iāve been using this integration for months with no performance issues.
The Airtouch application on my phone and my IPAD - as well as the main Android console for Airtouch - all of them were unresponsive - i could press a button (for instance to power on the AC) and it would not register for between 10 and 30 seconds (and sometimes not at all)
So in the end i power cycled the Airtouch Android Tablet, then power cycled the main AC system at the breaker in the siwtchboard.
Whilst this was all off i disabled the integration in HA and then restarted the VM
Yes i figure someone else may have reported if there were issues - but are you using the latest HA ? 2022.7 ? and the latest version of 1.4.3 of Marions integration ?
Craig
Iām using 2022.6.6 because 2022.7 had a bug with Open Weather Map. Iām using the latest version of the plugin. I donāt know why the Airtouch application would be running slowly, itās independent of HA. Iād have tried a couple of restarts first. If the other integration works for you though, might as well just use that.
Separate question for everyone. Iād like to put a fan control onto my dashboard, but the only way I know to do this is add the heat pump main node, click it, and change it in there (see the pic). Does anyone know how Iād get a low / medium / high fan control directly on the dashboard?
Iād also like to have an easy way to toggle between ITC and damper mode, and manually change damper percentage like I do with the Airtouch app
I donāt use the AirTouch app just HA. No performance issues with latest versions of everything.
Only thing I see is the frequent āConnection error in receiver!ā error messages in the log.
Hmm,
Thanks guys - been runnign fine today (just the Airtouch app on the Android Console, Phone and IPAD) and as responsive as they usually are.
I may revert to the official integration as i use MQTT to push the ITC values to my Node Red server for other automation and i have just noticed that 1.4.3 has stopped pushing them when the AC system is shutdown
Craig
The Airtouch stopped updating about 7.30pm this evening.
2022-07-10 19:34:32 ERROR (MainThread) [custom_components.polyaire.airtouch4] Connection error in receiver!
2022-07-10 19:34:32 INFO (MainThread) [custom_components.polyaire.airtouch4] Message receiver lost connection, trying to reconnect...
2022-07-10 19:34:32 INFO (MainThread) [custom_components.polyaire.airtouch4] (Re)connecting...
2022-07-10 19:34:32 INFO (MainThread) [custom_components.polyaire.airtouch4] (Re)connected!
2022-07-10 19:34:32 INFO (MainThread) [custom_components.polyaire.airtouch4] Message receiver task (re)started...
2022-07-10 20:12:56 ERROR (MainThread) [custom_components.polyaire.airtouch4] Connection error in receiver!
2022-07-10 20:12:56 INFO (MainThread) [custom_components.polyaire.airtouch4] Message receiver lost connection, trying to reconnect...
2022-07-10 20:12:56 INFO (MainThread) [custom_components.polyaire.airtouch4] (Re)connecting...
2022-07-10 20:12:56 INFO (MainThread) [custom_components.polyaire.airtouch4] (Re)connected!
2022-07-10 20:12:56 INFO (MainThread) [custom_components.polyaire.airtouch4] Message receiver task (re)started...
A restart of Home Assistant seemed to force a reconnect and things updated
2022-07-10 20:17:19 INFO (MainThread) [custom_components.polyaire.airtouch4] (Re)connecting...
2022-07-10 20:17:21 INFO (MainThread) [custom_components.polyaire.airtouch4] (Re)connected!
2022-07-10 20:17:21 INFO (MainThread) [custom_components.polyaire.airtouch4] Message receiver task (re)started...
2022-07-10 20:17:21 INFO (MainThread) [custom_components.polyaire.airtouch4] Message sender task (re)started...
2022-07-10 20:17:21 INFO (MainThread) [custom_components.polyaire.airtouch4] Received all status information from AirTouch, ready to go!
First of all, thank you for creating this integration, having the option to locally control the Airtouch system and integrate this with Home Assistant is awesome. The installation of the integration was a very smooth and fast process, but it seems like Iāve run into an issue with the integration.
Setup
- 2 AC units with multiple ducted rooms
- No ITC sensors
- Updated Airtouch 4 touch panel (running Android 11, console version 1.3.3, main module version 2.1.0.2 )
- Home Assistant core 2022.7.2
Issues
- During the setup a binary sensor for low ITC battery is generated for each room, however no ITC sensors are installed in the rooms (not sure if this behaviour is expected or not).
- When turning on / off the AC through the climate entity in Home Assistant, the integration usually (but not always) causes the integration to become unresponsive and prevents any further updates to the system such as turning on/of AC, changing modes, or changing damper settings. Even the official Airtouch mobile app becomes unresponsive where changes to the AC unit or dampers are not being processed anymore. Disabling the integration does not solve the issue, only a full reboot of Home Assistant seems to fix the issue. After / during the reboot of Home Assistant the official Airtouch mobile app becomes responsive again and the integration will work for a while again.
Debug log
A message with the unknown type ā0x2f ā is received at time where the system becomes unresponsive (right after sending the on / off command for the AC unit).
2022-07-10 15:17:25 INFO (MainThread) [custom_components.polyaire.airtouch4] Message receiver task (re)started...
2022-07-10 15:17:46 DEBUG (MainThread) [custom_components.polyaire.airtouch4] Message received with expected header!
2022-07-10 15:17:46 DEBUG (MainThread) [custom_components.polyaire.airtouch4] Message received with unknown type: 0x2f
2022-07-10 15:17:46 DEBUG (MainThread) [custom_components.polyaire.airtouch4] b'\x03\xffV\x90!3#\x0b!\x02\x00\x00\t\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00Polyaire\x00\x00\x00\x00\x00\x00\x00\x00\xa0\x88\x0c6\x00\x06\x05\x00\x80\x88\x1f\x1f#\x11AC1\x00\x00\x00\x00\x06\x03\x05\x00\x80\x88\x1f\x1d#\x11AC2\x00\x00\x00\x00\t\x00\x00\x00\x80\x88\x1f\x1d \x10UNIT3\x00\x00\x00\t\x00\x00\x00\x80\x88\x1f\x1d \x10UNIT4\x00\x00\x00Room1\x00\x00Room9\x00\x00Room2\x00\x00Room3\x00Room4Room5Room6\x00\x00\x00\x00Room7\x00Room8GroupA\x00\x00GroupB\x00\x00GroupC\x00\x00GroupD\x00\x00GroupE\x00\x00GroupF\x00\x00GroupG\x00\x00\xff\xff\xff\xff\x80\x00FAV1\x00\x00\x00\x00\x00\x00FAV2\x00\x00\x00\x00\x00\x00FAV3\x00\x00\x00\x00\x00\x00FAV4\x00\x00\x00\x00\x00\x00\x80\x00\x80\x00\x80\x00\x80\x00\x80\x00\x80\x00\x80\x00\x80\x00@\x11\x14\x00QG\x00\x00\x01\x12\x13\x00N\xc7\x00\x00\x02\x00\x16\x00\xff\xe7\xff\xfe\x03\x00\x17\x00\xff\xe7\xff\xfe\x00\x0f\x19\x00\xff\xe7AF\x19F\xff\xe7B(\x19(\xff\xe7C(\x19(\xff\xe7Dd\x19d\xff\xe7Ed\x19d\xff\xe7F2\x192\xff\xe7Gd\x19d\xff\xe7H#\x19#\xff\xe7Id\x19\x00>\x87Jd\x19\x00>\x87Kd\x19\x00>\x87Ld\x19\x00>\x87Md\x19\x00>\x87Nd\x19\x00>\x87Od\x19\x00>\x87'
2022-07-10 15:18:13 WARNING (MainThread) [asyncio] Executing <Task pending name='Task-6388' coro=<api_data.<locals>._wrapper() running at /usr/src/homeassistant/homeassistant/components/hassio/handler.py:42> wait_for=<Future pending cb=[shield.<locals>._outer_done_callback() at /usr/local/lib/python3.10/asyncio/tasks.py:857, Task.task_wakeup()] created at /usr/local/lib/python3.10/asyncio/base_events.py:429> cb=[gather.<locals>._done_callback() at /usr/local/lib/python3.10/asyncio/tasks.py:720] created at /usr/local/lib/python3.10/asyncio/tasks.py:636> took 0.175 seconds
2022-07-10 15:19:11 DEBUG (MainThread) [custom_components.polyaire.airtouch4] Message received with expected header!
2022-07-10 15:19:11 DEBUG (MainThread) [custom_components.polyaire.airtouch4] Message received is AC message!
2022-07-10 15:19:11 DEBUG (MainThread) [custom_components.polyaire.protocol] Updated AirTouchACStatus 0 status, calling: <bound method Entity.async_write_ha_state of <Entity AC 1: off>>
2022-07-10 15:19:11 ERROR (MainThread) [custom_components.polyaire.airtouch4] Connection error in receiver!
2022-07-10 15:19:11 INFO (MainThread) [custom_components.polyaire.airtouch4] Message receiver lost connection, trying to reconnect...
2022-07-10 15:19:11 INFO (MainThread) [custom_components.polyaire.airtouch4] (Re)connecting...
2022-07-10 15:19:11 DEBUG (MainThread) [custom_components.polyaire.airtouch4] open socket connection to the airtouch...
2022-07-10 15:19:11 INFO (MainThread) [custom_components.polyaire.airtouch4] (Re)connected!
2022-07-10 15:19:11 INFO (MainThread) [custom_components.polyaire.airtouch4] Message receiver task (re)started...
2022-07-10 15:19:15 DEBUG (MainThread) [custom_components.polyaire.airtouch4] Message received with expected header!
2022-07-10 15:19:15 DEBUG (MainThread) [custom_components.polyaire.airtouch4] Message received is AC message!This text will be hidden
@tamorix an AirTouch without temperature sensors in each room seems to defeat the purpose of the system. Iām curious why itās set up like that? The integration may assume that ITC control is available on every AirTouch, Iāve not heard of one without it before.
Iām using my own temperature sensors which are connected to Home Assistant to control the dampers of the Airtouch system (instead of the ITC sensors).
Edit - I decided to try this option after reading this comment (so it has been done before). With the current integration I am able to control all the AC units and dampers as expected, apart from the described unresponsiveness issue. But I agree itās not a typical installation 
@tamorix Very cool.
@mihailescu2m Did Polyaire happen to give you any idea of when they might be updating the firmware?
@tomwaldnz Sometimes Iāve found that refreshing the browser window or force quitting the Companion app and relaunching makes those flat lines disappear. Which raises other questions.
The happen in the web browser too. Restarting HA usually fixes it, sometimes I need to restart the Airtouch tablet.