Hi Sorry all the UUIDs should match with the UUID of your home assistant acting as the client connecting to the daikin unit. I have updated my post to reflect this. When I pasted my output it was from a previous attempt where i had a different uuid. In terms of line 40 which file do you mean? Did you mean line 41 of config_flow.py? I changed the default timeout of (10) to (60). This gives the unit extra time to respond. I’m not sure about yours but I find that when using the Daikin Mobile Controller iOS app my units take nearly 20 seconds or more before they display there current state. Seems a long time to respond to me.
But, the UUID is sent in the header so if we register one UUID with:
curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” -v “https://daikinac-IP/common/register_terminal?key=0135keyforC42”
It should be okto use that for the whole session? What is the key is that something you have configured via the app or is it static?
I’m trying to understand how the pydaikin can be changed. It looks like just registering an “random” UUID and then continue to use that should be enough… (Could you confirm that using a static UUID works)
Hi Fredrike I believe the UUID I am using is a random one set in the /config/.uuid file. The key is the number on the back of the daikin wireless adapter. This is the same key you use when using the daikin app on your phone. If you can think of the process the phone uses, home assistant needs to go through the same process. Eg when you register the wireless adapter using the phone app it is using the UUID of your phone and using the key on the side of the wireless adapter. Now when you run the curl command on home assistant you are essentially going through the same process. I hope that makes sense.
Yes that makes sense. Did you find this information online?
I’ll try to add add this to the package.
Hi @fredrike I was reading some of your other posts and tried a few commands and got some good output. I also saw you are the main contributor for the daikin intergration. I want to say a huge thank you to you and @nzhook to helping get this going. At my place I have 2 daikin split systems. 192.168.10.90 is a 3.5kw US7 FTXZ35NV1B which has a heap of features with the remote but not many with the app. Here is the output for this unit.
~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.90/aircon/get_model_info”
ret=OK,model=NOTSUPPORT,type=N,pv=1,cpv=0,mid=NA,s_fdir=0,en_scdltmr=1~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.90/aircon/get_price”
ret=OK,price_int=27,price_dec=0~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.90/aircon/get_sensor_info”
ret=OK,htemp=23.0,hhum=-,otemp=22.0,err=0,cmpfreq=6~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.90/aircon/get_target”
ret=OK,target=0~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.90/aircon/get_week_power”
ret=OK,today_runtime=653,datas=0/0/0/0/0/0/0~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.90/aircon/get_year_power”
ret=OK,previous_year=0/0/0/0/0/0/0/0/0/0/0/0,this_year=0/0/0/0~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.90/common/basic_info”
ret=OK,type=aircon,reg=th,dst=0,ver=1_13_7,rev=4335040,pow=1,err=0,location=0,name=%4d%61%73%74%65%72%20%42%65%64%72%6f%6f%6d,icon=2,method=home only,lpw_flag=0,adp_kind=3,pv=1,cpv=0,cpv_minor=00,led=0,en_setzone=1,mac=DCF505XXXXXX,ssid=DaikinAP40543,adp_mode=ap_run,en_hol=0,enlver=1.00,grp_name=,en_grp=0,en_secure=1,port=30050,id=,pw=~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.90/common/get_holiday”
ret=OK,en_hol=0~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.90/common/get_notify”
ret=OK,auto_off_flg=0,auto_off_tm=- -~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.90/common/get_remote_method”
ret=OK,method=home only,notice_ip_int=3600,notice_sync_int=60~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.90/aircon/get_control_info”
ret=OK,pow=1,mode=0,adv=,stemp=24.0,shum=0,dt1=24.0,dt2=M,dt3=25.0,dt4=25.0,dt5=25.0,dt7=24.0,dh1=0,dh2=50,dh3=0,dh4=0,dh5=0,dh7=0,dhh=50,b_mode=0,b_stemp=24.0,b_shum=0,alert=255~ $
~ $
The other unit is a 2.5kw CORA FTXV25UVMA which required an extra cable for the wi-fi unit to work but adds extra features like swing mode in the app compared to the more expensive US7 model.
Here is the output of the CORA
~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.91/aircon/get_model_info”
ret=OK,model=0C86,type=N,pv=2,cpv=2,cpv_minor=00,mid=NA,humd=0,s_humd=0,acled=0,land=0,elec=0,temp=1,temp_rng=0,m_dtct=1,ac_dst=–,disp_dry=0,dmnd=0,en_scdltmr=1,en_frate=1,en_fdir=1,s_fdir=3,en_rtemp_a=0,en_spmode=0,en_ipw_sep=0,en_mompow=0,en_patrol=0,en_fdir2=0,en_filter_sign=0~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.91/aircon/get_price”
ret=OK,price_int=27,price_dec=0~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.91/aircon/get_sensor_info”
ret=OK,htemp=26.0,hhum=-,otemp=22.0,err=0,cmpfreq=0~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.91/aircon/get_target”
ret=OK,target=0~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.91/aircon/get_week_power”
ret=OK,today_runtime=9,datas=300/600/800/500/300/700/0~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.91/aircon/get_year_power”
ret=OK,previous_year=0/0/0/0/0/0/0/0/0/0/38/72,this_year=45/43/30/12~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.91/common/basic_info”
ret=OK,type=aircon,reg=th,dst=0,ver=1_13_7,rev=4335040,pow=0,err=0,location=0,name=%52%79%61%6e%73%20%42%65%64%72%6f%6f%6d,icon=4,method=home only,lpw_flag=0,adp_kind=3,pv=2,cpv=2,cpv_minor=00,led=0,en_setzone=1,mac=DCF505XXXXXX,ssid=DaikinAP35747,adp_mode=ap_run,en_hol=0,enlver=1.00,grp_name=,en_grp=0,en_secure=1,port=30050,id=,pw=~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.91/common/get_holiday”
ret=OK,en_hol=0~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.91/common/get_notify”
ret=OK,auto_off_flg=0,auto_off_tm=- -~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.91/common/get_remote_method”
ret=OK,method=home only,notice_ip_int=3600,notice_sync_int=60~ $ curl --insecure -H “X-Daikin-uuid: cd29a1e50d914913a3ba22496e3b01ca” “https://192.168.10.91/aircon/get_control_info”
ret=OK,pow=0,mode=0,adv=,stemp=24.0,shum=0,dt1=24.0,dt2=M,dt3=25.0,dt4=25.0,dt5=25.0,dt7=24.0,dh1=0,dh2=50,dh3=0,dh4=0,dh5=0,dh7=0,dhh=50,b_mode=0,b_stemp=24.0,b_shum=0,alert=255,f_rate=A,b_f_rate=A,dfr1=A,dfr2=A,dfr3=A,dfr4=A,dfr5=A,dfr6=A,dfr7=A,dfrh=A,f_dir=0,b_f_dir=0,dfd1=0,dfd2=0,dfd3=0,dfd4=0,dfd5=0,dfd6=0,dfd7=0,dfdh=0~ $
I would think for the integration to work in HA you need to be able to either set the UUID or be able to pull it from HA somewhere. I found mine in the /config/.uuid hidden file.
Next you need to be able to register HA with the daikin units by entering the key that is on the side of the Wi-Fi units. Once this is complete you should be able to pull all of the info you want and hopefully have full control in the future.
2 Likes
That .uuid file is used to identify your HA installation during upgrades (I don’t dare to touch that).
There is not much we can do with the exposed features, I’ve got the same type unit as you (but with different wifi module, and 2.5kW), FTXZ25NV1B and can only do the most basic controls via the app (the year after i bought mine the same model was upgraded with new firmware that allows more features).
Yes, I’m the maintainer of pyDaikin and the HA integration…
I’ve patched the pyDaikin package and the daikin integration in HA. Would love to get it merged into HA but it needs testing first: Daikin BRP072C42 WIFI custom component - #36 by fredrike
Hi!
I don’t know that particular model. Which version of the Daikin mobile app are you supposed to use with it? I don’t think it will allow separate temperatures in each room, the Airbase units just shows zones that can be toggled on or off.
My units are CORA ones, they are separate wall units coming off a single outside one. Each unit has to have its own wifi module and work as separate devices on the network so offer different temperatures and settings in each room - the only catch is you cannot heat one room and cool another at the same time.
As a note the UUID can be anything, its just an identifier for that client and each unit stores which UUID’s can access it. Using the generic HA one could work but if it changes all the units would need to be registered again. Hence why my code was hard coded, I wanted to generate one and store it somewhere, even if it was unique per instance.
1 Like
Hi guys I will buy a daikin controller BRP069A81 for conducts AC the question is ? Its compatible with this integration, the official link dont show up
Supported hardware
- The European versions of the Wifi Controller Unit (BRP069A41, 42, 43, 45), which is powered by the Daikin Online Controllerapplication. The new versions of WiFi Controller Unit (BRP069Bxx) also should work but it have to be confirmed by users. Tested and working devices are the BRP069B41 and BRP069B45.
Thanks !!!
Which app is it using? Which unit would it be used in?
I don’t think we have seen that model before but if it doesn’t work I would be happy to help you debug and add it to the supported hardware, it might take some effort though.
that model is for ducted air conditioners, not for splitter, but I think the API is the same.
Well I don’t read spanish but it looks exactly like the B69 I have. As I said, if it doesn’t work directly we will sort it out.
Hello everyone,
The pydaikin 2.0 release now includes the power consumption feature. The new sensors are about to be integrated in Home Assistant, see https://github.com/home-assistant/core/pull/34391
This feature has only been tested on a BRP069B41 so does anyone with a different AC model could test it too? Running bin/pydaikin $IP -s will tail the measured power consumption if supported by your AC
Have a good day!
1 Like
Hi,
I just got my Wifi modul to my AC unit. It’s BRP069B42, and it’s working well.
What I’m missing is the Powerful and Econo special modes. Well mostly the Powerful. Is there any chance that this will be implemented in the future?
Another thing that I’m missing is the Comfort mode that is on the IR remote, but it looks this feature is missing from the Wifi control. In this mode, the unit controls the horizontal swing automatically. In cooling mode, it directs the air up, and is heating mode it directs it down.
There is also an error I found, when I wanted to make a Scene which switches the unit into Dry mode:
“Failed to call service scene/turn_on. expected float for dictionary value @ data[‘temperature’]”
This is probalby because there is no such thing as target temperature in Dry mode.
There is one more thing I would like to know, but I’m not sure if it’s possible or not.
I want to display the fan and swing paramters directly on the Lovelace UI.
I’m happy to review pull-requests.
I would guess that you need to supply a float for temperature .
You could probably create an attribute sensor for this.
This is the problem, because I can’t do that. In dry mode there is no such thing as target temperature, because in this mode the AC changes the humidity of the room, without modifying the temperature.
It’s not settable nor in HA nor in the Daikin app:
https://www.dropbox.com/s/f7kbj4skztjn2lb/daikin1.jpg?dl=0
Never done this, but I’ll try to look into it.
Create a new topic with the yaml from your scene and I’ll investigate what’s going on.
Hi @Smanny,
Did you manage to make it work? I’m also going to install a multi duct model and I’m really willing to know how is the experience with HA for multi duct models.
Thanks for your help,
If it is a unit mentioned in the docs it will work. Otherwise we have to do some debugging to make it work 
.
1 Like
Thanks for your fest reply @fredrike!
Sorry to ask that before doing a deep research on each and every unit, but by any chance, do you know which unit/s work with duct models?
If an already supported unit works with these kind of models, it may be easier to stick to that working unit 
If not, count with me to provide all help needed to increase the units that the integration can work with.
You are doing an awesome job!
Best,