A/C with wifi module integration

This @fredrike idea is very good and it may solve the problems with the update of the current status of the device.
It would be nice to do some tests and see if there is a broadcast packet every time we use the remote control, apart from the ones we get periodically. This way we could update the status of the component right away.

Are there issues with updates now?

Feel free… :stuck_out_tongue: I don’t even have that AC model.

Did you (@phenriques3000, @pavlo) manage to get some XML examples I can continue work on?

Hi @fredrike,

I finally got some time to debug problems :blush:

First thing I can see is that probably the seq number is not set fine:
Sending message: b’<msg msgid=“SyncStatusReq” type=“Control” seq="-3600">\n<SyncStatusReq></SyncStatusReq></msg>’

-3600 doesn’t seem fine. We know that apart from the SyncStatusReq, the rest of the commands should have a different seq number every time. -3600 seems to be fixed.

Edit: Confirmed the seq number is wrong also when sending another command:
Sending message: b’<msg msgid=“SetMessage” type=“Control” seq="-3600">\n<SetMessage><SetTemp>79.34</SetTemp></SetMessage></msg>’

I can also confirm that you can send messages like the following:

<msg msgid="SetMessage" type="Control" seq="19563">

When you get the status, you correctly get:

<msg msgid="statusUpdateMsg" type="Control" seq="999">
    <DeviceName>Katie AC</DeviceName>

I also could find out that the AC is sending a broadcast message every two seconds of this kind:

<message  msgid="Declaration">
  <DevName>Katie AC</DevName>

And when it is switched on you get the same thing plus some messages like the following at least one every 6 seconds (some of them may come even more frequently):

<msg msgid="statusUpdateMsg" type="Notify" seq="1234">

I hope this is enough info to let us continue working on this component.

What address is the broadcast sent to?

I’ve updated the seq on gist.

Hi @fredrike and @pavlo,
The broadcast is to all the network (, is that your question @fredrike?

Yes. And it’s sent to port 7777?

I’m not planning to implement the broadcast support (it might change though) my plan was to help you out with a working base and then you can glue parts of other implementations together to support local push and auto discovery.

Do you need support for more than on AC unit? Because that should be fairly easy to fix.

I’ll take a look in updating the code with complete settings with every update as that seems to be the best way according to @pavlo.

Hi @fredrike,

Don’t know if this help but I think there is a little problem (see log)

2019-01-31 21:03:07 WARNING (SyncWorker_14) [custom_components.climate.tfiac] Sending message: b'<msg msgid="SyncStatusReq" type="Control" seq="1548968587006">\n<SyncStatusReq></SyncStatusReq></msg>'
2019-01-31 21:03:07 WARNING (SyncWorker_14) [custom_components.climate.tfiac] Current status {'BaseMode': 'heat', 'TurnOn': 'off', 'Opt_display': 'on', 'Opt_ECO': 'off', 'Opt_super': 'off', 'SetTemp': '73', 'WindSpeed': 'Auto', 'Degree_Half': 'off', 'Opt_healthy': 'off', 'Opt_antiMildew': 'off', 'Opt_StereoWind': 'off', 'Opt_heating': 'off', 'Countdown_Timer_Off': '00:00', 'Countdown_Timer_On': '00:00', 'Infrared_Direct': 'off', 'Infrared_TurnOn': 'off', 'HumidityEnable': 'off', 'CleannessEnable': 'off', 'WindDirection_H': 'off', 'WindDirection_V': 'on', 'IndoorTemp': '63', 'Opt_sleepMode': 'off:0:0:0:0:0:0:0:0:0:0', 'BeepEnable': 'off', 'DeviceName': 'TAC_E88C95', 'WifiVer': '1'}
2019-01-31 21:03:08 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/service.py", line 287, in _handle_service_platform_call
    await getattr(entity, func)(**data)
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/climate/__init__.py", line 506, in turn_off
    raise NotImplementedError()

First I can’t connect the unit because I never see the command to power on it, I think it’s best to send always the <TurnOn>on</TurnOn> parameter and in that case we are assured that even if the AC unit of off it will ON in case a new state is sended (don’t know what you and @pavlo think about this approach).

Second I see there is a line break being sent in the message \n (just before the <SyncStatusReq>)

There is also a error in Python, don’t know if matters but I send it to you.

And by the way very thanks, for someone who don’t have a AC unit like that you are doing an amazing job! Thanks

I’ve updated the gist now, with what I believe could be the best way to send commands and control the AC unit.

The following XML is generated and sent (without \n and spaces) I’ve added WindSpeed to the message and hope that does not break the whole command:

<msg msgid="SetMessage" type="Control" seq="1549016192340">


<msg msgid="SetMessage" type="Control" seq="23">

If I understand you correct are the status updates working.

During this weekend I will try to send the following message:

<msg msgid="SetMessage" type="Control" seq="1549016192340">

So you can send the whole thing in only one message.

BTW, could you move the gist code to github repo where I can do a fork and then a pull request. I may have some time this weekend to do some improvements in the code.

You mean something like this :stuck_out_tongue: https://github.com/fredrike/home-assistant/blob/tfiac/homeassistant/components/climate/tfiac.py (might have bet you by 5 min or so).

That would actually make the code more complex, but it would be nice to just have one message to send.

1 Like

@krash I got a custom component already working. It is a preview version but it seems to work fine. Let me know if you want to test it. It may be helpful for us to squash some bugs.

@fredrike and I are still working in the component.

Hey @pavlo i would definately love to help out, my coding knowledge is limited but i’ll do whatever i can.
Also, i’m mainly using the units remotely, meaning my Hassio is in different place than the a/c units, will it still work?

I highly doubt that the implementation we have now will work on different networks.

Unless you have a VPN connection to the network where your a/c units are located, or you open an UDP port in your router to access your a/c units from internet, @fredrike is right it won’t work in different networks. The option of openning a port would be very insecure.

What about installing a local home assistant where your ac units are located? You just need a new Raspberry Pi, then you can think of connecting two different home assistants.

With an raspberry-pi as gateway at the “different place” you could set up a UDP port forwarding tunnel and reach your unit remotely.