What entry urls do you have for those temps?
Thanks for the reply, it was something weird with my mesh setup. I can ping it now, so now Iāll wait for you guys to finish the magic. Many thanks.
I am using the Daikin Airbase BRP15B61. Iāve noticed when operating via Home Assistant the fan speed on my ducted system is getting changed from high to low?
It doesnāt do that if I use the Daikin Airbase app.
Any ideas? I literally set up my Home Assistant yesterday so on a steep learning curb 
1 Like
> debug mode of wall controller does show a few temps are available.
What entry urls do you have for those temps?
@fredrike - no URLās - it is a key sequence i found for the wall controllerā¦
1 Like
I guess it might be quite hard to find that entrypoint thenā¦
So should this work now in 91.3?
Woohoo, I got it working by deleting it from integrations and adding it again. Thanks guys
Hi Fredrike, Thanks for your work in getting this integrated into the Daikin component. I did some background work on the airbase when it was first released looking into the URLs etc, The seems to be the Airbase only had 3 fan speeds. When you use the get_control_info URL, the f_rate=1 for low, =3 for mid and =5 for high.
I believe in the pydaikin - in the appliance.py the translations for the āf_rateā should be something like this, in addition there arenāt any Auto or Slience mode for the fans.
'f_rate': {
'1': 'low',
'3': 'mid',
'5': 'high',
},
However, when using the current and trying to set the rates to 3 and 5 it doesnāt seem to work. It does read the rates as 3 and 5 if I set them from my iOS Airbase app to Mid and High though.
Great find!
When developing support for Airbase I was in contact @jurgenweber and according to him only Low and High was available. Hence I mapped fan speed as everything not high as low in https://bitbucket.org/mustang51/pydaikin/src/3f3cedd54ff415dd7953d753f69ab8c2025fbead/pydaikin/appliance.py?at=master&fileviewer=file-view-default#appliance.py-293
Iāll revise and change the pydaikin and update the HA code accordingly. But I am not available in the next few days so it might take some weeks before it reaches a new version in HA.
Same here from our testing, only have Low and High.
I only have low and high too
I guess we need to reach some consensus in this. How can we detect (via the API) which fan_modes that are supported?
Suppose maybe we need from more sample data to see if there is anything relevant in the various api results from those with high-low vs high-med-low
I know we saw High which was Fan mode=3 gives a f_rate=5
I know we saw Low which was Fan mode=1 gives a f_rate=1
Ok maybe there are different rates depending on the Units?
As a survey I have
Airbase App = 3 modes - low, mid, high
Daikin Physical controller = 3 modes - low, mid, high
In my current I have the unit - Set to Cooling mode 22 deg but off
Fan speed ālowā returns:
ret=OK,pow=0,mode=2,stemp=22,dt1=22,dt2=22,dt3=22,f_rate=1,dfr0=3,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
Fan speed āmidā returns:
ret=OK,pow=0,mode=2,stemp=22,dt1=22,dt2=22,dt3=22,f_rate=3,dfr0=3,dfr1=1,dfr2=3,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
Fan speed āhighā returns:
ret=OK,pow=0,mode=2,stemp=22,dt1=22,dt2=22,dt3=22,f_rate=5,dfr0=3,dfr1=1,dfr2=5,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
Just some more info - if I use get_model_info I get the following. I wonder if the āfrate_stepsā below tells us the difference between 2 step fan modes and 3 step fan modes?
ret=OK,err=0,model=NOTSUPPORT,type=N,humd=0,s_humd=7,en_zone=0,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=0,en_dry=1,en_common_zone=0,cool_l=16,cool_h=32,heat_l=16,heat_h=32,frate_steps=3,en_frate_auto=0
1 Like
for my Airbase with only Low and High -
ret=OK,err=0,model=NOTSUPPORT,type=N,humd=0,s_humd=7,en_zone=0,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=0,en_dry=1,en_common_zone=0,cool_l=16,cool_h=32,heat_l=16,heat_h=32,frate_steps=2,en_frate_auto=0
So the f_rate is different to ones with 3 speedsā¦ But looks promising as a way to determine the difference and how to map it.! well done.
1 Like
Ok, so Iāve build temporary support for modular fan-rates (reading the supported settings from get_model_info) in https://github.com/fredrike/home-assistant/blob/daikin_fan-mode/homeassistant/components/daikin/climate.py and https://bitbucket.org/mustang51/pydaikin/src/fan_mode/pydaikin/appliance.py it would be great if some of you could test the changes.
Also, does the AirBase units support Holiday mode and how does it work? It seems to be fairly easy to implement it. Below is a screenshot of how it looks in the Daikin Online Controller app for my unit.
Hi Fredrike, and thanks for all your efforts.
I have the airbase app (1.0.4) on an android and have recently updated the firmware to 1.1.1 on the airbase module. The app main page provides support for:
MODE: cool, fan, heat, dry
TARGET TEMPERATURE: 16-32
FAN SPEED: this toggles Lo or Hi for me (though there are 3 bars on the icon suggesting med is possible where supported)
POWER: on/off
TEMPERATURE: this seems to be the duct temperature no matter what I do with the daikin field settings.
There is no āHOLIDAYā mode that I can find.
If I check the model info I get exactly the same response string that borgy has. This fits with the two fan steps.
I have no zone controller, but the daikin component loads 8 switches - does the airbase app allow zone control for those with zone controllers? If so the airbase app seems to be able to exclude them for me.
I have only one temperature, but the daikin component loads 2 thermometer sensors for me. The airbase app only shows one temperature. Maybe it is excluding one based on the response below (see htemp=/otemp=)
The following responses occur for me (no zone controller installed):
http://192.168.1.191/skyfi/aircon/get_zone_setting?lpw=
ret=OK,zone_name=%2d%3b%2d%3b%2d%3b%2d%3b%2d%3b%2d%3b%2d%3b%2d,zone_onoff=0%3b0%3b0%3b0%3b0%3b0%3b0%3b0
http://192.168.1.191/skyfi/aircon/get_sensor_info?lpw=
ret=OK,err=0,htemp=11,otemp=-
Finally, with the recent files you have suggested I get the below error. The 2 thermometer sensors and 8 switches still load but there is no climate component. I am running hassio, and have implemented this as a custom component and substituted your 2 recommended files where appropriate. It is possible I have done this incorrectly (my experience is very limited).
Error while setting up platform daikin
Traceback (most recent call last):
File ā/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.pyā, line 126, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File ā/usr/local/lib/python3.7/asyncio/tasks.pyā, line 416, in wait_for
return fut.result()
File ā/config/custom_components/daikin/climate.pyā, line 69, in async_setup_entry
async_add_entities([DaikinClimate(daikin_api)])
File ā/config/custom_components/daikin/climate.pyā, line 82, in init
ATTR_FAN_MODE: self._api.device.fan_modes,
AttributeError: āApplianceā object has no attribute āfan_modesā
I hope this helps
Thank you @racsa for your extensive description of your AirBase setting.
I hope the current settings with Auto could be ok. When it comes to Temperature the current supported values are: 7-35 (Iām not planning to change that as an incorrect value will reset to the closest correct value).
Ok, Iāll hide it for ALL AirBase units then.
I did try to remove the Zones switches here, but apparently is it not working, could you please add a debug string to L26 like this _LOGGER.info(zones) so we can see what is going on.
Yes, the old Daikin devices (non AirBase units) reports otemp as outside temperature but only when the device is on. So I need to add the sensor for outside temperature even if it is not supported by your unit (you just have to live with a sensor wo value).
edit: Iāve added a fix for that here: AirBase units does not support outside temp Ā· home-assistant/core@300e5cf Ā· GitHub (requires the f1d5067 version of appliance.py)
You need to replace the appliance.py file in pydaikin (typically located at /usr/local/lib/python3.7/site-packages/pydaikin/applicance.py) to support the latest changes to pyDaikin.
Fredrike
Sorry for the delay. Busy week here.
switch.py edit:
ā¦ā¦
zones = daikin_api.device.zones
_LOGGER.info(zones)
if zones:
ā¦ā¦
log output:
019-05-09 21:31:46 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for daikin which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-05-09 21:31:55 ERROR (MainThread) [.] Error connecting to the Hue bridge at 192.168.1.234
2019-05-09 21:31:55 WARNING (MainThread) [homeassistant.config_entries] Config entry for hue not ready yet. Retrying in 5 seconds.
2019-05-09 21:31:58 WARNING (MainThread) [homeassistant.config_entries] Config entry for daikin not ready yet. Retrying in 5 seconds
The climate, 2 temp sensors and 8 switches are still loading. So it appears there is nothing for .info(zones) to report. I did incorrectly edit the switch.py file initially and it broke the switch loading - so home assistant looks to be using this file.
HASSIO and I are proving to be not very compatible when it comes to file access and replacement. I will try and put together a docker or hassbian version when I get a chance. Hopefully this weekend.
Thanks again