[RELEASE] Daikin WiFi Split System v1.4.1

UPDATED 1.4.1 - (11/12/2018) - Implemented fix for B-type adapters (‘Host’ header case). Big thanks to @WGentine

This Device type allows the integration of Daikin Split Systems that have the optional “WiFi module” installed. Most commonly, this is the “BRP072A42” module. This Device Type has only been tested with that module, however other modules (such as the BRP069A42) should be compatible.

It implements the SmartThings “Thermostat” capability, which means it has full compatibility with most thermostat automations and allows integration with platforms such as Google Home.

Note that “P” Series units (FTXMxxP) do not support fan direction or rate controls.

Features

  • Ability to set desired temperature
  • Ability to set desired mode (Auto, Cool, Heat, Dry, Fan)
  • Seperate temperatures for each mode
  • See indoor environment temperature
  • See outdoor environment temperature
  • Adjustment of fan direction (Horizontal, Vertical and “3D”)
  • Adjustment of fan rate (0-5, Auto, Silence)
  • Fahrenheit and Celsius support

To Install

Either copy the device handler directly in to the IDE, or add the repo:

  • Owner: bendews
  • Name: smartthings-daikin-wifi
  • Branch: master

Once the Device Handler has been added, we can then add a virtual device via the IDE:

  • Login to the IDE @ https://account.smartthings.com
  • Click “My Devices”
  • Click the “New Device” Button
  • Enter a “Name” for the device, this can be whatever you want. (I.E “Bedroom Air Conditoner”)
  • Enter a “Label” for the device, this is optional and can be whatever you want.
  • Enter a “Device Network Id” This can be anything, however it must be different from any other device. This ID will change once the device has been configured.
  • “Zigbee” Id should be left blank
  • Select a “Type” from the dropdown, this should be “Daikin WiFi Split System”
  • “Version” should be published
  • “Location” should be your hub location, probably “Home”
  • “Hub” should be your hub name
  • “Group” leave as is
  • Click Create

Once created, we can then open the settings for the device, and fill out the following values:

  • Daikin WiFi IP Address: The IP address of the WiFi unit
  • Daikin WiFi Port: Ensure this is set to 80 if you are not sure
  • Refresh Interval in minutes: The device will refresh automatically when tasks are triggered by SmartThings, however if it is being controlled by other means (I.E a remote), the state will go out of sync. This setting will refresh the device information on a set interval. 10 minutes or higher is strongly recommended.
  • Display Fahrenheit: If toggled temperature values will be displayed in Fahrenheit

See the device type below and visit the Repo for more information:

6 Likes

Hi Ben!

I have just installed your device hanlder. I have encounterd few issues:

  • temeprature seeting is no applied when changed from default values
  • seems that it can’t really work together with daikin app

I’ll do some more tetsing in a few hours when I get back home. In general this is promising!
My firmware version is 3.3.1

Br,
D

1 Like

Also, some control throug webcore would be nice :slight_smile:
Setting AC unit depending on other sensors, date, time, automation…

Thats awesome, thanks for the feedback!

Any chance you could do the following?
Let me know what WiFi module you have installed (I.E BRP072A42)
Link to the Daikin App you are using (App or Play store link)
Output from logging (Live logging in the SmartThings IDE, press some buttons and record the output :slight_smile:)

I’ve found that it doesn’t interfere with my Daikin app (Daikin D-Mobile) at all and they seem to sync up well.

However, I have the latest firmware for my WiFi modules available (BRP072A42), and that is v.2.9.0. So something tells me that there is either regional differences or something else going on.

Let me know how it goes!

And will definitely look in to making sure it works well with WebCoRE, just coming back to SmartThings after over a year of my hub sitting in a box, so still learning my way around some of the new awesome tools that have came out since then.

I’ll get back with requested information in a few hours. No problem!

APP: https://play.google.com/store/apps/details?id=eu.daikin.remoapp
adapter: BRP069A42
V.3.3.1

Problem with updating temperature in any mode is present, other settings are working fine. Default temperature is sent to controller.

Refresh interval is time is time in which device handler polls data from adapter? I’d like to change it to minute or two. :slight_smile:

in WebCore device is visible as pollable and refreshable, nothing else at the moment.

Logging:
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:44:19: debug Executing hubaction on 192.168.178.55:80/aircon/get_sensor_info
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:44:19: debug Delay for '500’
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:44:19: debug Executing hubaction on 192.168.178.55:80/aircon/get_control_info
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:44:19: debug Delay for '500’
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:44:19: debug Executing hubaction on 192.168.178.55:80/aircon/set_control_info?pow=1&mode=4&stemp=18&f_rate=A&f_dir=0&shum=0
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:44:19: debug 0
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:44:19: debug Executing ‘setFanRate’ with Auto
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:44:19: debug Executing 'fanRateAuto’
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:43:36: debug Executing hubaction on 192.168.178.55:80/aircon/get_control_info
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:43:36: debug Delay for '500’
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:43:36: debug Executing hubaction on 192.168.178.55:80/aircon/get_sensor_info
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:43:36: debug Refreshing
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:43:06: debug Executing hubaction on 192.168.178.55:80/aircon/get_sensor_info
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:43:06: debug Delay for '500’
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:43:06: debug Executing hubaction on 192.168.178.55:80/aircon/get_control_info
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:43:06: debug Delay for '500’
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:43:06: debug Executing hubaction on 192.168.178.55:80/aircon/set_control_info?pow=1&mode=4&stemp=18&f_rate=6&f_dir=0&shum=0
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:43:06: debug 0
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:43:06: debug Executing ‘updateEvents’ with heat, 18 and true
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:43:06: debug Executing 'heat’
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:53: debug Executing hubaction on 192.168.178.55:80/aircon/get_sensor_info
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:53: debug Delay for '500’
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:53: debug Executing hubaction on 192.168.178.55:80/aircon/get_control_info
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:53: debug Delay for '500’
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:53: debug Executing hubaction on 192.168.178.55:80/aircon/set_control_info?pow=1&mode=6&stemp=26&f_rate=6&f_dir=0&shum=0
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:53: debug 0
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:53: debug Executing ‘toggleFanDirection’ with Vertical
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:53: debug Executing 'fanDirectionVertical’
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:40: debug Executing hubaction on 192.168.178.55:80/aircon/get_sensor_info
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:40: debug Delay for '500’
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:40: debug Executing hubaction on 192.168.178.55:80/aircon/get_control_info
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:40: debug Delay for '500’
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:40: debug Executing hubaction on 192.168.178.55:80/aircon/set_control_info?pow=1&mode=6&stemp=26&f_rate=6&f_dir=1&shum=0
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:40: debug 1
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:40: debug Executing ‘setFanRate’ with 4
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:33: debug Executing hubaction on 192.168.178.55:80/aircon/get_sensor_info
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:33: debug Delay for '500’
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:33: debug Executing hubaction on 192.168.178.55:80/aircon/get_control_info
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:33: debug Delay for '500’
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:33: debug Executing hubaction on 192.168.178.55:80/aircon/set_control_info?pow=1&mode=6&stemp=26&f_rate=5&f_dir=1&shum=0
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:33: debug 1
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:33: debug Executing ‘setFanRate’ with 3
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:11: debug Executing hubaction on 192.168.178.55:80/aircon/get_sensor_info
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:11: debug Delay for '500’
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:11: debug Executing hubaction on 192.168.178.55:80/aircon/get_control_info
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:11: debug Delay for '500’
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:11: debug Executing hubaction on 192.168.178.55:80/aircon/set_control_info?pow=1&mode=6&stemp=26&f_rate=4&f_dir=1&shum=0
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:11: debug 1
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:41:10: debug Executing ‘setFanRate’ with 2
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:40:56: debug Executing hubaction on 192.168.178.55:80/aircon/get_sensor_info
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:40:56: debug Delay for '500’
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:40:56: debug Executing hubaction on 192.168.178.55:80/aircon/get_control_info
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:40:56: debug Delay for '500’
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:40:56: debug Executing hubaction on 192.168.178.55:80/aircon/set_control_info?pow=1&mode=6&stemp=26&f_rate=A&f_dir=1&shum=0
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:40:56: debug 1
5024d70c-7231-4fe0-b529-a1bb9ac874e9 16:40:56: debug Executing ‘updateEvents’ with fan, null and true

Based on the logging it actually looks like a response is never returned from the A/C.

Is the SmartThings hub and A/C on the same network subnet? (I.E SmartThings hub is on 192.168.178.x)

What happens when you go to 192.168.178.55/aircon/get_sensor_info in your browser?

Thanks heaps for all the info!

ret=OK,htemp=22.5,hhum=-,otemp=-,err=0,cmpfreq=0

Devices are in the same network.

Hi, thanks much bendews for your great work here!!!..
im new to smartthings although I have the daikin wifi AC for quite some time now.
I just added the split systems to smartthings & able to control, mostly.
few things I observed not working:

  1. turning back ON the system (Google indicates mode is not available).
  2. from the smartthings app, set point changes do not take effect into the system (AC).

Daikin mobile controller model = BPP072A42
Firmware version (all 3) = 2.9.0

Appreciate your further assistance & support.

1 Like

Nice! Been waiting for something like this for my Daikin unit as well, been relying on the IFTTT integration so far. But last night it did not trigger for some reason and my house was too cold in the morning. So popped on here and found this! :slight_smile:
But… Having the same issue as Davor is mentioning. Using the same app, have not checked the mobile controller yet.
Have also had a php based controller which I have been running locally on my webserver, to be able to control it from my wall tablet.
If you need any logs from my side as well, I am willing to help out as much as I can.
Awesome work so far!

1 Like

I was looking for this, i will give immediately a try

1 Like

Hi Everyone,
I have updated to v1.2 which should hopefully fix the issues with setting temperature, as well as adding Switch and Temperature Measurement capability. Please update from GitHub and If there are any further issues let me know and we can do our best to troubleshoot and figure them out :slight_smile:

@Artis_Pagsanjan, note the behaviour you are describing with the google home is a limitation of the SmartThings thermostat capability. You have to phrase it with a mode (I.E Hey Google, set the bedroom thermostat to cool/heat/auto). I have added switch capabilities which may enable the behaviour you are describing but I have not had a chance to test it with the Google home yet. See this link for more info: https://support.smartthings.com/hc/en-us/articles/214609826-Google-Assistant-SmartThings-FAQ#Thermostats
Note that only the generic thermostat modes are available via Google (cool/heat/auto), unfortunately Dry and Fan-Only can not be set via external systems at all :frowning_face:

Perfect! Seems to be working. :star:

Awesome! Thats great to hear, thanks for the feedback :smiley:

Also, @Davor_Dooley, I’ve been testing with WebCoRE and it looks like all functionality is available now :slight_smile: Including Dry and Fan-only mode (The first two custom actions in the list)

So now since it’s seems to be working, can I put a small request? :slight_smile:
Can you pull the outside temperature as well so it could be used?
Just added this to an Actiontiles panel and it would be nice to see the outside temp as well.

ret=OK,htemp=20.0,hhum=-,otemp=-2.0,err=0,cmpfreq=72

Sure can, it’s on the planned future feature list and the value is already getting gathered by the Device Handler, I’m just running into trouble figuring out the best way to advertise the value to the user. The SmartThings temperature measurement capability only allows 1 value.

Do you have any suggestions? :slight_smile:

I just updated with support for the outside temperature value as a custom attribute “outsideTemp”, let me know if this provides what you’re looking for :slight_smile:

No value is returned for the outside temp.

ret=OK,htemp=21.0,hhum=-,otemp=-1.0,err=0,cmpfreq=74

Have you tried clicking the refresh button? If so and it still isn’t working, send me a PM and we can go through the logs. :slight_smile:

Nice workshop there! Just looken for somethings like this and find this Thread. I Will start testning imidiatly butik im pretty new to all of this with automation, so my First Step is to figure Outlook Which ip my Daikin device has.