Daikin Component - no climate entities created - task exception

I also have Daikin BRP069B41 and could not make it work before I found this thread. A few more hints:

  • In my configuration.yaml I have only added “daikin:” with no other arguments. Actually, I don’t really understand how Home Assistant can find the IP addresses to my two Daikin devices.
  • Test with “curl http://daikin_ip/common/basic_info” etc from the command line interface to find out which endpoints that do not work with your configuration
  • I had to remove: aircon/get_timer, aircon/get_program and aircon/get_scdltimer.

Good luck!

Hi all,
I applied the same fix to the sensor/daikin.py
(original here).
Just create sensor subfolder and apply this fix to the original file:
Line12 original: from homeassistant.components.daikin import (
Line12 new: from custom_components.daikin import (

In this way, entities are created:
sensor.inside_temperature_xxxx_inside_temperature
sensor.outside_temperature_xxx_outside_temperature

I noticed today on updating to Hassio 81.0 that there was a breaking change to the daikin component.

hot changed to heat

Cool changed to cool

not a biggie, was able to get around it by re jigging my scripts etc but worth mentinong

The modes are now defined as follows

  • mode (cool, heat, dry, fan only or auto) or off

I have just updated to 0.81 and since the I can’t set Fan_mode or Swing_mode. I amble to set “mode” and temperature. Do anybody else have the same issue?

Hi I’m the one that made the latest breaking change to the Daikin component.

@Sam_Mofrad I just checked and I think I found the issue, I’ll look at it.

@peterho Can I ask you what kind of rejigging you had to do?

I found what probably was wrong with this, I made a PR for that issue.
If you want you can test it setting as a custom component. You can found the code at

My rejigging was merely changing hot to heat Cool to cool etc for operation mode in my scripts and automations. My unit doesn’t support swing mode or fan mode (it’s a ducted in ceiling unit)

Your PR sets the temperature to 22°C when changing the fan_mode!

Edit: I see that you are on the issue on github :slight_smile:

Yes that’s another kind of issue, related to the daikin Python library used to comunicate with the device. Will work on that!

1 Like

Unfortunately, I still need to rely on the custom_components published above.

The new daikin component published with 0.81, not only doesn’t solve the old issues, but introduces new ones.

That is, of course, if I am not the only one with issues here.

I’ve reworked the underlying pydaikin (soon to be v0.7) module for the Daikin component.

This is supposed to fix the issues with temperature reset when changing fan mode. I’ve also taken a decision to make a change that reflect the OEM Daikin app too:

The new changes will set the temperature and humidity to the last setting for that mode. I.e. say that you have 22° for hot and 24° for cold, when you switch from hot to cold the temperature will be set to 24° too. (This is how the Daikin devices and applications works).

This means that when you are controlling from the climate component in Home Assistant, then the temperature will change when you change mode (as you are only able to change one parameter at time there). However, when changing mode from say an automation you can (should) set the operation_mode too.

Please let me know if this change is unacceptable, if it should be an opt out, or if the “previous” setting were better (where the temperature were “persistent” between modes).

1 Like

Can you also please make sure the new units (ending Bxx, instead of Axx) are working?

Sure, what makes them special? I.e. what kind of differences do I need to take into account?

Edit: Make sure that you can run pydaikin · PyPI and report all issues you have and we will try to fix that.

Is it possible to try the temperature fix already now? If yes, which files do I need to add to custom components?

I just updated to 0.82.1 and it broke Daikin integration for me. Previously had Daikin as a climate entry, and a sensor entry. Added it as its own component as per the new docs and it still didn’t work. Removed both the climate and sensor, and only the sensors worked.

I ended up having to add Daikin as its own component, AND as a climate component to get everything working again. Is this expected? Or should adding Daikin as its own component only be enough for sensors and the climate entity?

Apparently, upgrading to 0.82.1 will get you the latest changes.

There are no breaking changes in integration, what was your previous config and version?

This is my Daikin configuration and you are right, it should be enough with just the daikin entry.

climate:                                                                                                                                                                        
  - platform: daikin                                                                                                                                                            
    host: 192.168.1.15                                                                                                                                                          
                                                                                                                                                                                 
daikin:                                                                                                                                                                         
  hosts:                                                                                                                                                                        
  - 192.168.1.15                                                                                                                                                                

I’m going to rewrite the configuration parts (using configuration entities) once people have tested 0.82.1 and are happy with the current functions.

Hi @fredrike ,

I also have the Bxx module instead of Axx (BRP069B41) and with the following config:

daikin:
hosts:
- 192.168.1.133

It doesn’t start:
2018-11-17 18:26:45 ERROR (MainThread) [homeassistant.setup] Error during setup of component daikin
Traceback (most recent call last):
File “/usr/src/app/homeassistant/setup.py”, line 148, in _async_setup_component
component.setup, hass, processed_config) # type: ignore
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/daikin.py”, line 82, in setup
if daikin_api_setup(hass, host) is None:
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

2018-11-17 18:27:05 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/src/app/homeassistant/components/daikin.py”, line 72, in discovery_dispatch
if daikin_api_setup(hass, host) is None:
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

Any logs you need please tell me and I will collect.

Thanks!

I’ll take a look but the “non-OK on response” indicates that there might be something deeper that is not working.

Try to access http://192.168.1.133/common/basic_info

If that is successful we might have other deeper issues…

Can you also download and play with pydaikin from pypi (pip install pydaikin).

Edit: I’ll try to update the code in pydaikin but please try the endpoints listed here so we can track what is going wrong https://bitbucket.org/mustang51/pydaikin/src/bf142f9708a01e673d40b9bba1ad9ada09c5094f/pydaikin/appliance.py?at=master&fileviewer=file-view-default#appliance.py-21

Since we are gathering info from the field I just wanted to chime in and let you all know that I am running three BRP072A43 units and have had no issues since upgrading to 0.82.1.

1 Like

That’s great news! There is one more fix in the main lib that didn’t reach the 0.82.1 release but it will just fix a wired issue going to/from fan only mode.

Perhaps we need a list of models working and models that still are in progress…