Daikin Component - no climate entities created - task exception

I don’t see outside temperature anywhere. My guess is that current_temperature: is the inside temp. Then temperature: is the target temperature.
Is it possible to edit values for min_temp and max_temp? I’d be quite happy locking people from using temps >30C and <25C.
Also, I have noticed that I cannot access the Daikin app when the AC unit adapter is being used by HA. This won’t be an issue once I make HA accessible from outside the network, but is this normal behavior?

If u open again all the endpoints from the previous time and u see there the min and max teperature in the output response then yes u will also be able to control it from HA.
And no, its not normal that HA blocks your Daikin app and it should be accesible from multiple devices @monkey-house

Ok, I realised I had network issues in the room where my AC is. It’s a remote room so I have to rely on PLCs… That could explain some of the issues. Now that it’s sorted, I can access the AC from both the Daikin app and HA.
Now, for the outdoor sensor, I can access this via the Daikin sensor component as follows:

sensor.outside_temperature_electric_ac_outside_temperature	29.0	unit_of_measurement: °C
friendly_name: Outside Temperature Electric AC outside temperature
icon: mdi:thermometer

It does not show up in the Climate component…

Hi guys,
Is there any further development of the Daikin platform?
Things have been awefuly silent for the past 2 months, and I’ve reported a couple of bugs and no answers :frowning:

1 Like

Any update about this platform? I have a similiar issues with my AC Daikin.

Thank you.

@rofrantz,

Thanks for your fix above — I removed get_timer, get_program, and get_scdltimer from appliance.py and now it works perfectly!

I’m using a BRP069B42 adapter with FTXS50KAVMA and FTXS25KVMA heads in Australia, where the ultra expensive (~$500/head), and apparently unreliable (due to app & wifi issues) SkyFi system (BRP15A61) was discontinued at the start of 2017 (per https://www.ozbargain.com.au/node/318865). It’s hard to find documentation online about which modules work with which heads, but I had understood the 20/25 (2/2.5kW) heads required the adapter, but the larger 35/50 (3.5/5.0kW) heads did not… turns out the smaller units have the S21 interface and don’t need the KRP980B1 adapter after all, at least down here. If I understand well:

  • BRP069B41 is just the box, which connects to the cable supplied with the newest heads
  • BRP069B42 is the box with the cable to the S21 connector
  • BRP069B43 is the box with the cable and the KRP980B1 adapter

Daikin now recommend the D-Mobile App with BRP072A42 modules (almost $200/head). “Daikin warrant this product to work with their latest split systems, the new P series. However it should work perfectly with any Daikin split system that has an S21 port on the indoor PCB. This is almost all systems manufactured since 2008.” (per http://server.chowmain.software/Control4/Chowmain%20-%20Daikin%20Wifi%20Driver%20Installation%20Guide.pdf).

Hope this information helps someone else.

Sam

@rofrantz

All been working well for me through to latest .71 version.

For the temp reset during automation i ended up putting a set temp statement in every automation. A little bit cumbersome but works none the less.

Was there ever a fix for the temp reset to 22 deg?

@rofrantz

I’m on Hass.io and use 3 Daikin AC units: 1 x BRP072A42 and 2x BRP072B41.
I am nt sure how I can modify my files from the above explanations.

Can you elaborate a bit more, please?

Had the same issue. Hass.io is a bit tricky as you need to modify the docker-image. Which will have to be done on each update of HA.

I’ve created a PR with @samj’s proposed fix (return empty dictionary in stead of error) but not sure if it will be accepted.

I dont know either since:

  1. I didnt provide those files
  2. I dont use docker or hass.io
    Maybe @samj can give u more details

@nrosier : I’m not sure you need to modify docker-image. Using this tip https://github.com/home-assistant/home-assistant/issues/13111#issuecomment-404500315 I finally manage to get it working with hass.io

Tried the solution but no luck. Also added my modified entities.py to the pydaikin directory but still no luck. So will have to continue with modifying the docker image which really is a hassle. My problem is this:

2018-07-26 11:23:39 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/daikin.py", line 72, in discovery_dispatch
    if daikin_api_setup(hass, host) is None:
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/daikin.py", line 105, in daikin_api_setup
    device = appliance.Appliance(host)
  File "/usr/local/lib/python3.6/site-packages/pydaikin/appliance.py", line 110, in __init__
    self.values.update(self.get_resource(resource))
  File "/usr/local/lib/python3.6/site-packages/pydaikin/appliance.py", line 115, in get_resource
    return self.parse_response(r.text)
  File "/usr/local/lib/python3.6/site-packages/pydaikin/entity.py", line 28, in parse_response
    raise ValueError("non-OK return on response")
ValueError: non-OK return on response
2018-07-26 11:23:39 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/daikin.py", line 72, in discovery_dispatch
    if daikin_api_setup(hass, host) is None:
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/daikin.py", line 105, in daikin_api_setup
    device = appliance.Appliance(host)
  File "/usr/local/lib/python3.6/site-packages/pydaikin/appliance.py", line 110, in __init__
    self.values.update(self.get_resource(resource))
  File "/usr/local/lib/python3.6/site-packages/pydaikin/appliance.py", line 115, in get_resource
    return self.parse_response(r.text)
  File "/usr/local/lib/python3.6/site-packages/pydaikin/entity.py", line 28, in parse_response
    raise ValueError("non-OK return on response")
ValueError: non-OK return on response

If I hack the entity.py do return {} in stead of raise an error all works well.

This is weird. It worked well for me.

This is what I’ve done :

wget https://github.com/home-assistant/home-assistant/files/2188643/daikin.zip
ssh [email protected] mkdir /config/custom_components
scp daikin.zip [email protected]:/tmp
ssh [email protected] unzip /tmp/daikin.zip -d /config/custom_components
ssh [email protected] "mv /config/custom_components/daikin/* /config/custom_components"
ssh [email protected] rmdir /config/custom_components/daikin

Then reboot hassio instance.

Do you still have the error after that ?

I unzipped it directly in the custom_components directory. Didn’t know the top-level directory should not be copied. Will try later and let you know.

@nrosier: Unpacked the zip and moved the files without the top-level directory and got the following warning (which indicates the custom_component was found):

You are using a custom component 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.

However, I’m also receiving the same error you posted above, indicating the “non-OK return on response” in the /usr/local/lib/python3.6/site-packages/pydaikin/entity.py file.

Could you give us the result for the following commands :

curl "http://[DAIKIN_IP_ADDRESS]/common/basic_info" 
curl "http://[DAIKIN_IP_ADDRESS]/common/get_remote_method" 
curl "http://[DAIKIN_IP_ADDRESS]/aircon/get_sensor_info" 
curl "http://[DAIKIN_IP_ADDRESS]/aircon/get_model_info" 
curl "http://[DAIKIN_IP_ADDRESS]/aircon/get_control_info" 
curl "http://[DAIKIN_IP_ADDRESS]/aircon/get_target" 
curl "http://[DAIKIN_IP_ADDRESS]/aircon/get_price" 
curl "http://[DAIKIN_IP_ADDRESS]/common/get_holiday" 
curl "http://[DAIKIN_IP_ADDRESS]/common/get_notify"
curl "http://[DAIKIN_IP_ADDRESS]/aircon/get_week_power"
curl "http://[DAIKIN_IP_ADDRESS]/aircon/get_year_power"

If one of the command fails, try to delete the matching path from HTTP_RESOURCES array in your custom_components/pydaikin/appliance.py file.

I’m having similar issues as @nrosier with a long row of errors when starting my HASS Docker container (v 0.74.2). I can’t get the climate component working and no controls are shown, in gui or dev-state <>. I tried adding it as per the documentation:

climate:
  - platform: daikin
    host: 192.168.1.167

This is on my home server running Ubuntu 18.04. I also have a Raspberry Pi 3 running HASS in Docker for experimental purposes and there the Daikin climate component shows in the gui and dev-state even if I didn’t add it to my configuration.yaml. Is that auto-discovery at work or what’s going on?

The weird thing is that the Daikin wifi adapter IP address is unreachable from within the Docker container on my home server but accessable from the container on my RPi. Both containers are running network_mode=host, HASS being the only one running like that on my home server.

I have yet to try @tchab’s solution with the custom component, I’ll give it a shot this evening.

Thanks for your response. I’ve done the curl requests you suggested and all of them return a proper result I guess. Adapter is a BRP069B45.

curl “http://192.168.0.184/common/basic_info
Response:
ret=OK,type=aircon,reg=eu,dst=1,ver=1_2_48,rev=7A61A5D,pow=0,err=0,location=0,name=%44%61%69%6b%69%6e%41%50%37%30%30%35%33,icon=0,method=home only,port=30050,id=,pw=,lpw_flag=0,adp_kind=3,pv=3.20,cpv=3,cpv_minor=20,led=1,en_setzone=1,mac=XXXXXXXXXXXX,adp_mode=run,en_hol=0,grp_name=,en_grp=0

curl “http://192.168.0.184/common/get_remote_method
Response:
ret=OK,method=home only,notice_ip_int=3600,notice_sync_int=60

curl “http://192.168.0.184/aircon/get_sensor_info
Response:
ret=OK,htemp=29.0,hhum=-,otemp=35.0,err=0,cmpfreq=0,mompow=1

curl “http://192.168.0.184/aircon/get_model_info
Response:
ret=OK,model=0000,type=N,pv=3.20,cpv=3,cpv_minor=20,mid=NA,humd=0,s_humd=0,acled=0,land=0,elec=1,temp=1,temp_rng=0,m_dtct=0,ac_dst=–,disp_dry=0,dmnd=1,en_scdltmr=1,en_frate=1,en_fdir=1,s_fdir=1,en_rtemp_a=0,en_spmode=3,en_ipw_sep=1,en_mompow=1,hmlmt_l=10.0

curl “http://192.168.0.184/aircon/get_control_info
Response:
ret=OK,pow=0,mode=0,adv=,stemp=22.0,shum=AUTO,dt1=22.0,dt2=M,dt3=21.0,dt4=25.0,dt5=25.0,dt7=22.0,dh1=AUTO,dh2=50,dh3=0,dh4=0,dh5=0,dh7=AUTO,dhh=50,b_mode=0,b_stemp=22.0,b_shum=AUTO,alert=255,f_rate=B,f_dir=0,b_f_rate=B,b_f_dir=0,dfr1=B,dfr2=5,dfr3=7,dfr4=5,dfr5=5,dfr6=5,dfr7=B,dfrh=5,dfd1=0,dfd2=0,dfd3=1,dfd4=0,dfd5=0,dfd6=0,dfd7=0,dfdh=0,dmnd_run=0,en_demand=0

curl “http://192.168.0.184/aircon/get_target
Response:
ret=OK,target=0

curl “http://192.168.0.184/aircon/get_price
Response:
ret=OK,price_int=27,price_dec=0

curl “http://192.168.0.184/common/get_holiday
Response:
ret=OK,en_hol=0

curl “http://192.168.0.184/common/get_notify
Response:
ret=OK,auto_off_flg=0,auto_off_tm=- -

curl “http://192.168.0.184/aircon/get_week_power
Response:
ret=OK,today_runtime=0,datas=0/100/100/0/0/100/0

curl “http://192.168.0.184/aircon/get_year_power
Response:
ret=OK,previous_year=0/0/0/0/0/0/0/0/0/0/0/0,this_year=0/0/0/0/0/0/0/0

Another question, even though that the daikin component is loaded as a custom_component, could it be that the wrong appliance.py is called as shown in the errors below? It looks like the error is thrown by a 404 for “aircon/get_timer”, which indicates that the appliance.py in the custom_components is not used, but the default one in /usr/local/lib…

2018-08-01 11:56:05 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up platform daikin
Traceback (most recent call last):
File “/usr/src/app/homeassistant/helpers/entity_platform.py”, line 129, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File “/usr/local/lib/python3.6/asyncio/tasks.py”, line 358, in wait_for
return fut.result()
File “/usr/local/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/src/app/homeassistant/components/sensor/daikin.py”, line 48, in setup_platform
api = daikin_api_setup(hass, host, name)
File “/usr/src/app/homeassistant/components/daikin.py”, line 105, in daikin_api_setup
device = appliance.Appliance(host)
File “/usr/local/lib/python3.6/site-packages/pydaikin/appliance.py”, line 110, in init
self.values.update(self.get_resource(resource))
File “/usr/local/lib/python3.6/site-packages/pydaikin/appliance.py”, line 115, in get_resource
return self.parse_response(r.text)
File “/usr/local/lib/python3.6/site-packages/pydaikin/entity.py”, line 28, in parse_response
raise ValueError(“non-OK return on response”)
ValueError: non-OK return on response

Sorry, I forgot to mention that I had to disable autodiscovery by commenting

#discovery:

component in configuration file, otherwise it didn’t worked.

Just upgraded hass.io and it did not break daikin this time. Thanks.