Daikin wifi controller options
Hi all,
I was experimenting with my Daikin online controllers ( wifi ) to control my airconditioning in my house. IFTTT supports full functional control of the Daikin airco’s. This works fine. But does anyone know how to import IFTTT buttons for this commands in Pimatic? Would be awesome to controle my airconditioning with pimatic. Any ideas?
@countjuh said in Daikin wifi controller options:
Would be awesome to controle my airconditioning with pimatic.
Another possibility is to use a client library to control daikin directly rather than using IFTTT. If you have some basic programming skills you may want to have a look at https://github.com/Apollon77/daikin-controller. It should be relatively easy to write some node app which can be integrated using “pimatic-shell-execute” or by writing a plugin. There also is an unofficial API documentation project which may be helpful to better understand what the API does and provides. https://github.com/ael-code/daikin-control
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
Hi mwittig,
Thanks for the quick reply and the detailed info. To bad i dont have basic skills for programming. I guess i have to wait for anyone who can do this for me ( and ofc all the Daikin users ) or… I have to learn it 
i now dont have a clue where to begin.
@mwittig said in Daikin wifi controller options:
@countjuh said in Daikin wifi controller options:
Would be awesome to controle my airconditioning with pimatic.
Another possibility is to use a client library to control daikin directly rather than using IFTTT. If you have some basic programming skills you may want to have a look at https://github.com/Apollon77/daikin-controller. It should be relatively easy to write some node app which can be integrated using “pimatic-shell-execute” or by writing a plugin. There also is an unofficial API documentation project which may be helpful to better understand what the API does and provides. https://github.com/ael-code/daikin-control
I have made it to get 2 buttons ( dummyswitch ) and execute html commands to get the airco on and off. Since i cant program i didnt knew a better solution for now. Maybe someone can help me with the following. I can get info from my daikin using a html command. Can i get these variables out and translate them into my pimatic?
I get this line:
ret=OK,pow=0,mode=3,adv=,stemp=21.0,shum=0,dt1=25.0,dt2=M,dt3=21.0,dt4=25.0,dt5=25.0,dt7=25.0,dh1=AUTO,dh2=50,dh3=0,dh4=0,dh5=0,dh7=AUTO,dhh=50,b_mode=3,b_stemp=21.0,b_shum=0,alert=255,f_rate=3,f_dir=0,b_f_rate=3,b_f_dir=0,dfr1=5,dfr2=5,dfr3=3,dfr4=5,dfr5=5,dfr6=5,dfr7=5,dfrh=5,dfd1=0,dfd2=0,dfd3=0,dfd4=0,dfd5=0,dfd6=0,dfd7=0,dfdh=0
@countjuh said in Daikin wifi controller options:
Can i get these variables out and translate them into my pimatic?
Yes. I think the easiest and most flexible tool is to use the pimatic-log-reader plugin. I have drafted an example for you which transforms three values (power status, operating mode, and target temperature) of the data set to pimatic attributes which can even be displayed in the devices view.
Here is the device config:
{
"file": "/home/pi/status.log",
"attributes": [
{
"name": "power",
"type": "boolean",
"acronym": "POW",
"discrete": true
},
{
"name": "mode",
"type": "string",
"acronym": "M",
"discrete": true
},
{
"name": "targetTemperature",
"type": "number",
"unit": "°C",
"acronym": "TT"
}
],
"lines": [
{
"match": ",pow=1",
"power": true
},
{
"match": ",pow=0",
"power": false
},
{
"match": ",mode=[017]",
"mode": "AUTO"
},
{
"match": ",mode=2",
"mode": "DEHUMDIFICATOR"
},
{
"match": ",mode=3",
"mode": "COLD"
},
{
"match": ",mode=4",
"mode": "HOT"
},
{
"match": ",mode=6",
"mode": "FAN"
},
{
"match": ",stemp=([\\d\\.]+)",
"targetTemperature": "$1"
}
],
"xAttributeOptions": [],
"id": "daikin",
"name": "Daikin Status",
"class": "LogWatcher"
}
],
The device can also be edited with device editor except for transformations to boolean attributes as the device editor expects a string value where true or false must be given. You may also notice an error message like "Invalid config of device "daikin": Property "#/lines/0/power" Should have type string, was: boolean in /lines/0/power, Property "#/lines/1/power" Should have type string, was: boolean in /lines/1/power". It is safe to ignore that for now.
For the result of the status command you need to append (use >> operator) this to a log file, in the given example it is /home/pi/status.log. As you probably do not want to fill up the log file with a long history of result data set you can keep short as follows:
# Call the following each time when a status command result is available
# The following line will truncate the log file or create it when it does not yet exist
truncate --size 0 /home/pi/status.log
# The following assumes the result of the status command has been stored in shell variable named RESULT
echo ${RESULT} >> /home/pi/status.log"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
For the result of the status command you need to append (use
>>operator) this to a log file, in the given example it is/home/pi/status.log. As you probably do not want to fill up the log file with a long history of result data set you can keep short as follows:# Call the following each time when a status command result is available # The following line will truncate the log file or create it when it does not yet exist truncate --size 0 /home/pi/status.log # The following assumes the result of the status command has been stored in shell variable named RESULT echo ${RESULT} >> /home/pi/status.log
Good morning Marcus,
Thanks for the Super example. I can get to the above stuff. Then i dont know what you mean anymore. Append. Doesnt give me a clue. Im sry for my bad knowledge. I try to begin somewhere with basic programming but its hard 
I have insert all and i made the logfile in home/pi
I have this as a result now.
Maybe i forget something? or can it be that i have 2 airco’s controlled with the wifi?
@countjuh said in Daikin wifi controller options:
Then i dont know what you mean anymore. Append. Doesnt give me a clue.
Ok, no worries. Do you already have Shell-Script to query the status of your daikin device? If yes, please share it with me. If not, please post the command sequence you have executed to obtain the status and I’ll draft a shell script for you.
or can it be that i have 2 airco’s controlled with the wifi?
I am not sure, but I think the status query is for a single device. That’s my understanding from the docs - https://github.com/ael-code/daikin-control
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
Thanks! Well i havent a shell script yet. Didnt even knew i need that. Omg i feel quite dumb 😂. The command is for airco 1:
http://192.168.2.7/common/basic_info
I get this as return in the browser:
ret=OK,type=aircon,reg=eu,dst=1,ver=2_6_0,pow=0,err=0,location=0,name=%73%6c%61%61%70%6b%61%6d%65%72%20%6f%75%64%65%72,icon=3,method=polling,port=30050,id=countjuh,pw=ylolgefn,lpw_flag=0,adp_kind=2,pv=0,cpv=0,cpv_minor=00,led=0,en_setzone=1,mac=98F1705F36D4,adp_mode=run,en_hol=0,grp_name=,en_grp=0
For airco 2 i do in browser:
http://192.168.2.8/common/basic_info
I get this respons:
ret=OK,type=aircon,reg=eu,dst=1,ver=2_6_0,pow=0,err=0,location=0,name=%73%6c%61%61%70%6b%61%6d%65%72%20%49%73%61,icon=3,method=polling,port=30051,id=countjuh,pw=ylolgefn,lpw_flag=0,adp_kind=2,pv=0,cpv=0,cpv_minor=00,led=0,en_setzone=1,mac=A408EAC4259A,adp_mode=run,en_hol=0,grp_name=,en_grp=0
i tried some things, can’t seem to manage the append function in pimatic at all. dont have a clue where to begin here.
Good morning Mwittig. Did you allready made some?
Hi all. Anyone interested in helping me out on this topic? It would be amazing if i could let it work. I have made buttons for the 2 airco units. With on / off / status. With status i get the info returned in pimatic, but i just dont get how to grep info from it and translate it to get it into variable. Thanks for replies. Best regards, marcel
Since i was convinced i was on the right way i kept on tryin. Maybe its not the best possible solution but i managed it to work.
If people have Daikin Airco they can make it happen in Pimatic!
This is the result. And you can add alot more features if you like out of the data provided from the wifi module.
@countjuh Nice. It’ll be great if you are ready to share your findings with other users. How about writing a short “How-To” article along with the configuration snippets required. I am happy to help with editorial stuff (review, formatting) if fancied.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
Good idea. Im gonna make it complete and make a simple how to. And if i need anything, i will let u know. Thanks for the support!
@mwittig
I have a problem in updating the present values from the logfiles created. I have read about truncate files. I have added this line now:
sudo curl -s 'http://192.168.2.9/aircon/get_control_info' :> /home/pi/status.log | >> /home/pi/status.log
This is in the command line from the device shell sensor.
I see that the file is written correct, but the info on pimatic doesnt refresh. When i edit device logwatcher and save the info is updated good. But when i dont do that it wont refresh. Maybe u have an idea?
@countjuh I am not sure you can use “:>” in the command sequence for a ShellSensor directly as it will be executed by a restricted shell as far as I remember. It works as part of bash script for sure. Alternatively you may want to try the following:
truncate -s0 /home/pi/status.log && curl -s 'http://192.168.2.9/aircon/get_control_info' >> /home/pi/status.log
or try
/bin/bash -c "curl -s 'http://192.168.2.9/aircon/get_control_info' :> /home/pi/status.log""It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
@mwittig
Thanks for the quick reply! appriciate it. I treid both lines without succes. First line works ( no errors ) but give the same result. After saving the device logwatcher it updates. If i dont do that nothing changes.
Update 12:00. Strange. It seemed to work. Ive tested it like 10 times and the status etc updated perfect with the first line. After aprox 2 mins it stopped working and now it doesnt work anymore.
The second line gives result can not execute command.
Just to be sure here is my config for the shellsensor
@countjuh said in Daikin wifi controller options:
Update 12:00. Strange. It seemed to work. Ive tested it like 10 times and the status etc updated perfect with the first line. After aprox 2 mins it stopped working and now it doesnt work anymore.
What is the content of the status.log file now? Does it contain a single line with device status data as expected?
An issue might be the short update interval you have chosen. If the curl command does not complete with 5 seconds for some reason the next execution cycle will start already and may produce unexpected results. Please check the process table to see whether or not commands pile up. You may also want to give a try with a more relaxed updated cycle of, say 20 seconds (20000).
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
Content of the logfile is single lined as expected. Changing the curl interval to 20 secs doesnt work out. log file contains good info, only not bein updated correct to the logwatcher device. But, now after a long wait ( say sometimes within the minute, sometimes after a few minutes, sometimes not ) So it seems to work / not work.
When i see the file i mostly see the correct info. But when i check random i got this line in the status.log:
'ret=OK,pow=0,mode=3,adv=,stemp=21.0,shum=0,dt1=25.0,dt2=M,dt3=21.0,dt4=21.0,dt5$
<TITLE>302 Moved</TITLE></HEAD><BODY>
<H1>302 Moved</H1>
The document has moved
<A HREF="http://www.google.nl/?gfe_rd=cr&dcr=0&ei=3IkRWv-hH6HVXo-gtNAM"$
</BODY></HTML>'
Also i have seen this in the logfile:
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-885$
<TITLE>ERROR: The request could not be satisfied</TITLE>
</HEAD><BODY>
<H1>ERROR</H1>
<H2>The request could not be satisfied.</H2>
<HR noshade size="1px">
Bad request.
<BR clear="all">
<HR noshade size="1px">
<PRE>
Generated by cloudfront (CloudFront)
Request ID: 00CHxeU-a8jK9sd0f5w1DhcBLN627e82EKj5MvipHWY4SMx6mapj3Q==
</PRE>
<ADDRESS>
</ADDRESS>
</BODY></HTML>
Think u mean the /proc ? Think this is it:
