Local ekon server for device

hllhll / HomeAssistant-EKON-iAircon

EKON iAircon / Tadiran climate component written in Python3 for Home Assistant. On the bases of Gree Climate component for easier interfacing with HASS

GNU General Public License v3.0

14 stars 7 forks source link

Local ekon server for device #19

Closed hllhll closed 3 years ago

hllhll commented 4 years ago

You should not yet try the commands below, this was only confirm to not-brick the device by me, but there's a really small bricking chance, reset with the button should solve everything in case of issues, also in case of issues I Have managed to reclaim the device using ESPTouch SmartConfig app, but if you are no expert you shouldn't be doing this)

I'll document here some info I've gathered regarding how it might be possible to redirect traffic to local LAN server and implement locally without cloud.

First, app uses ESP Smart config/ESP Touch to add the ESP device into the wifi network. This can also be done without the original app, using ESPTouch SmartConfig app. After the device is in the wifi LAN the app goes on to configure the server it will be using, this is done by POSTing to the device (ip address: Airconet+ server, activate-ac.com)

POST /config?command=client HTTP/1.1
User-Agent: LuaSocket 2.0.2
Content-Length: 157
Content-Type: application/json; charset=utf-8
Host: <your pc workstation address>

{"client_set":[{"ip":"3.137.73.173","port":9533,"protocol":"UDP","local_port":80},{"protocol":"","ip":""},{"protocol":"","ip":""},{"protocol":"","ip":""}]}

If you want to remove the device and disconnect from Wifi (I'm not sure if it restores factory settings):

POST /config?command=restore HTTP/1.1
User-Agent: LuaSocket 2.0.2
Content-Length: 2
Content-Type: application/json; charset=utf-8
Host: <your pc workstation address>

As seen above the device communicates using udp datagrams to the server. I Have tested switching the server to my pc address and I'm able to record messages sent from the device.

hllhll commented 4 years ago

UDP Communication alaysis update: Device->Cloud only (over UDP) unsigned shorts - 2 bytes; MSByteF

Heartbeat packets - starts with 00 01 total len: 0x14 bytes
Data packets - starts with 01 03 total len: 0x15 bytes. These are the same as the data that comes from the Websocket JSON requestBytes

Data packet format: 01 03 ?? 00 <on> 00 ?? 00 <hvac> 00 <fan> 00 00 <ct> <ct> <tt> <tt> ?? ?? <cs> <cs>

on: Same as the code EKON_VALUE_ON=0x55; EKON_VALUE_OFF=0xAA

hvac: Same as EKON_VALUE_MODE_X

EKON_VALUE_MODE_COOL = 17 = 0x11
EKON_VALUE_MODE_HEAT = 34 = 0x22
EKON_VALUE_MODE_AUTO = 51 = 0x33
EKON_VALUE_MODE_FAN = 68 = 0x44
EKON_VALUE_MODE_DRY = 85 = 0x55

fan: 01 02 03 fan speed
tt: target_temp*10
ct: current_temp*10
cs - Checksum(?)