i tried some things, can’t seem to manage the append function in pimatic at all. dont have a clue where to begin here.
-
Daikin wifi controller options
-
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:
-
Today with the help of @mwittig this project is finally finished. I will write a how’to ( this winter ) for controlling the daikin aircondioning.
Thanks again mwittig! -
@countjuh That’s great!
I am glad it finally works as expected and I am looking forward to your how-to article
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law