Daikin Airbase Binding

Hi Jim

See below:

ret=OK,type=aircon,reg=au,dst=1,ver=1_1_3,rev=17,pow=1,err=0,location=0,name=%44%61%69%6b%69%6e%41%50%36%35%32%37%39,icon=0,method=home only,port=30050,id=,pw=,lpw_flag=0,adp_kind=3,led=1,en_setzone=1,mac=D0C5D39D01A1,adp_mode=run,ssid=DaikinAP65279,err_type=0,err_code=0,en_ch=1
ret=OK,err=0,model=NOTSUPPORT,type=N,humd=0,s_humd=7,en_zone=8,en_filter_sign=1,acled=1,land=0,elec=0,temp=1,m_dtct=0,ac_dst=au,dmnd=0,en_temp_setting=1,en_frate=1,en_fdir=0,en_rtemp_a=0,en_spmode=0,en_ipw_sep=0,en_scdltmr=0,en_mompow=0,en_patrol=0,en_airside=0,en_quick_timer=1,en_auto=1,en_dry=1,en_common_zone=1,cool_l=16,cool_h=32,heat_l=16,heat_h=32,frate_steps=3,en_frate_auto=1
ret=OK,zone_name=%46%72%6f%6e%74%20%52%6f%6f%6d%3b%53%74%75%64%79%3b%42%65%64%72%6f%6f%6d%3b%4c%69%76%69%6e%67%3b%20%20%20%20%20%20%20%5a%6f%6e%65%35%3b%20%20%20%20%20%20%20%5a%6f%6e%65%36%3b%20%20%20%20%20%20%20%5a%6f%6e%65%37%3b%20%20%20%20%20%20%20%5a%6f%6e%65%38,zone_onoff=0%3b1%3b0%3b1%3b0%3b0%3b0%3b0
ret=OK,err=0,htemp=23,otemp=-
ret=OK,pow=1,mode=2,stemp=24,dt1=21,dt2=24,dt3=21,f_rate=1,dfr0=1,dfr1=1,dfr2=1,dfr3=1,f_airside=0,airside0=0,airside1=0,airside2=0,airside3=0,f_auto=0,auto0=0,auto1=0,auto2=0,auto3=0,f_dir=0,dfd0=0,dfd1=0,dfd2=0,dfd3=0,dfd7=0,filter_sign_info=0,cent=0,en_cent=0,remo=2

Thanks! Interesting that your get_model_info says en_airside=0. What fan settings does your phone app allow you to set? Does it include “Airside”?

Could you please set your ac fan to just “Auto” (not auto low/med/high), and then send me another output from http://192.168.1.xx/skyfi/aircon/get_control_info

Interesting… I see more possible config options now:
frate_steps=3 - ie 3 fan speeds - possible to support mode?
en_frate_auto=1 - I wonder if this is the auto-level1, auto-level2, auto-level3 stuff?
en_auto=1 - ‘Auto’ mode supported y/n
en_airside=0 - is airside support y/n

My model string is:

ret=OK,err=0,model=NOTSUPPORT,type=N,humd=0,s_humd=7,en_zone=5,en_filter_sign=1,acled=1,land=0,elec=0,temp=1,m_dtct=0,ac_dst=au,dmnd=0,en_temp_setting=1,en_frate=1,en_fdir=0,en_rtemp_a=0,en_spmode=0,en_ipw_sep=0,en_scdltmr=0,en_mompow=0,en_patrol=0,en_airside=0,en_quick_timer=1,en_auto=1,en_dry=1,en_common_zone=1,cool_l=16,cool_h=32,heat_l=16,heat_h=32,frate_steps=3,en_frate_auto=1

So… Paul’s opinion…

For fan modes, we should be checking model info to check what is supported by the unit, and dynamically building the available states, and only showing the ones that are supported. It would be great to get some more data from other systems - I’ll post a request on whirlpool too. Once we see some other options in model info, we can ask more questions about what shows in the airbase app to understand what the options really mean and test our theories.

I’ll be pretty time poor for the next couple of weeks, but on the positive side, will have data on another daikin system hopefully by the 16th when I install my airbase at our holiday house :slight_smile:

Cheers,

Paul

On COOL, I only get Auto, 1 bar actually

ret=OK,pow=1,mode=2,stemp=24,dt1=21,dt2=24,dt3=24,f_rate=1,dfr0=1,dfr1=1,dfr2=1,dfr3=1,f_airside=0,airside0=0,airside1=0,airside2=0,airside3=0,f_auto=1,auto0=0,auto1=0,auto2=1,auto3=1,f_dir=0,dfd0=0,dfd1=0,dfd2=0,dfd3=0,dfd7=0,filter_sign_info=0,cent=0,en_cent=0,remo=2

Yep I’m working on this.

It seems that your model doesn’t support airside either.

1 Like

I noticed a quirk and I think its the lack of refresh. if the temp is 24, and you ask Alexa to set the temp to 23 by linking the V3 Alexa skill to the Temp channel, it says Air temperature is set to 24.

Presumably this is because it sets it to 23 and immediately back to 24. Despite the Daikin app showing it correctly.

Won’t it then go to 23 after a few seconds? I will take a look and see if this can be fixed.

Unfortunately not

changing the fan or any setting does the same thing. Zones/Power dont though

Paul said it was a refresh issue? Do you not see the same issue, even without Alexa? I created a Habpanel slider and dragging the temp does it also

12:48:18.664 [INFO ] [arthome.event.ItemStatePredictedEvent] - DaikinACUnit_Mode predicted to become HEAT
12:48:18.665 [INFO ] [smarthome.event.ItemStateChangedEvent] - DaikinACUnit_Mode changed from FAN to HEAT
12:48:19.051 [INFO ] [smarthome.event.ItemStateChangedEvent] - DaikinACUnit_Mode changed from HEAT to FAN

When I changed the temp, or fan speed on BasicUI, say 24 to 25, it went back to 24, then after a few seconds, it will then show 25. However, on the wall controller it went straight to 25.

I’ve got the dynamic state option for the Airbase Fan working now. Thanks for the tip, @rossko57! If en_airside=0, it won’t show the Airside as an option, and if en_frate_auto=0, it won’t show the “Auto Low/Medium/High”.

I’ve added an enumset into AirbaseModelInfo to keep track of these en_xxx feature set of the aircon, to keep track of it.

As for frate_steps, I’d need to gather some more “samples” to understand it. Are there systems out there in existence with frate_steps other than 3?

I’m planning to add a channel called “filtersign”. I haven’t yet seen this on my system but it is suppposed to remind you to clean the filter when it’s on. Has anyone seen it pop up on their controller?

Hi Jim I’m using Habpanel as I have a widget written for it. Yes the controller updates correctly. I just tested this more. The UI does update but takes around 15 seconds. Alexa still gets it wrong though as the update isn’t fast enough. I assume due to the refresh

Heres a video

1 Like

Great news on the dynamic fan speed! Thanks for picking this up!

re: frate_steps - see https://whrl.pl/RfYzlE where there are only 2x rates, and no auto fan. This particular model has en_auto=0 which I suspect means it won’t have an AUTO mode either. I’ve asked more questions over in whirlpool

I’ve never seen filter warnings pop up here…

I love your habpanel! Care to share?

What is your aircon thing refresh set to?

Great data collecting, thank you! So with frate_steps = 2 they only have f_rate=1 for low and f_rate=5 for high. Sweet, just hide “Medium” for them. So far I’m the only one with airside feature it seems.

I can also make the aircon mode dynamic and hide the Auto mode, and possibly the “Dry” mode (en_dry).

On further thought, this frate_steps isn’t as simple as it may first seem. I think the ideal scenario is like this:

for frate_steps=2, they have the choice of LEVEL_1 (f_rate=1) and LEVEL_2 (f_rate=5)
for frate_steps=3, they have the choice of LEVEL_1 (f_rate=1), LEVEL_2 (f_rate=3) and LEVEL_3 (f_rate=5)
and I am guessing a system exists somewhere out there with f_rate=5, in which case,
for frate_steps=5, they have the choice of LEVEL_1 (f_rate=1), LEVEL_2 (f_rate=2) … LEVEL_5 (f_rate=5)

Notice the translation of LEVEL_N to f_rate is not constant.

Sure!

See attached, it assumes you’re using the Matrix theme, it’s not a widget though because there is alot of other stuff in here specific to my system

AirconDaikin.txt (5.8 KB)

the thing is:

daikin:airbase_ac_unit:ducted_ac [ host="192.168.0.84" ]

I submitted an issue to keep track of this https://github.com/openhab/openhab2-addons/issues/6524

I don’t quite understand the Alexa part though. Can you elaborate how Alexa is linked? I don’t have Alexa so can’t experiment with it.

If I understood you correctly, when you asked Alexa to change the temp from 24 to 23, the daikin wall controller would change to 23 as expected; OpenHAB after the cycle of 24->23, 23->24, 24->23, eventually settled on 23; but Alexa would still think it’s 24? How do you know what value Alexa knows? Does it display it on a screen?

Hi Jim I might be confusing you, the alexa part is kinda irrelevant. The reason Alexa announces the temperature as effectively not changing, is because of the delay. She reads it back as soon as its sent.

And yes, thats exactly what happens, 24 to 23, 23 to 24 then finally to 23.

Alexa just reads back something along the lines of ‘temperature set to 24’ despite me sending 23 :slight_smile: