cbrandlehner / homebridge-daikin-local

Supports Daikin Air Conditioners on HomeBridge

homebridge-daikin-local

Supports Daikin Air Conditioners on HomeBridge by connecting to the optional Daikin Wifi Controller.

WARNING

Daikin has removed their local API in newer products. They offer a cloud API accessible only under NDA, which is incompatible with open source. This affects units fitted with the BRP069C4x wifi adapter.

The Daikin App will most likely ask you to update the devices firmware. If you want to continue to use this plugin, DO NOT UPDATE THE FIRMWARE.

About this plugin

This plugin retrieves sensor and mode data from a Daikin WIFI controller in your local network and allows you to set operation modes and target temperatures. As it is a plugin for HomeBridge you will have access to these features using Apple Home.

It is recommended to configure your DHCP server to reserve a fixed IP for the wifi controller. This plugin can be installed using Homebridge Config UI X.

Configuration

This screenshot shows the configuration in Homebridge Config UI X:

Features

The FAN: The FAN allows you to turn on the fan of your Daikin AC. You can also set the speed of the fan. Apple HomeKit allows you to set a speed percentage from 0% to 100%. This plugin translates this percentage value as follows: 0% to 9%: SILENT mode 10% to 20%: AUTO mode 21% to 30%: Level 3 31% to 40%: Level 4 41% to 60%: Level 5 61% to 80%: Level 6 81% to 100%: Level 7 (max)

The AC: Apple HomeKit settings allow you to enable or disable the swing aka oscillation mode. As HomeKit is limited to a true or false value, the plugin's configuration allows you to configure the type of swing mode. Available modes are "horizontal swing", "vertical swing" and "3D".

Technical background information on the API used

The apiroute is used for two main calls: Get info such as current activity and sensor readings from the thermostat and set the target temperature and modes. The Aircon LAN adapter provides two directories for these settings and data:

1. /common uses the GET method for control and system information about the Aircon (e.g software version, MAC address, Reboot System, Region)

2. /aircon uses the GET method to set Aircon related information (e.g Target Temperature, Modes like Heat and Cool, Temperature Sensor Readings, Timers)

Supported devices

Currently, this plugin supports Daikin wifi controllers supporting the "aircon" URLs (System: Default) and "skyfi" URLs (System: Skyfi).

To test http connectivity, use your browser to connect to your device using one of these URLs:

http://192.168.1.88/aircon/get_model_info
http://192.168.1.88/skyfi/aircon/get_model_info

replace the IP (192.168.1.88) with the IP of your device.

Your browser should return a line like this:

ret=OK,model=0AB9,type=N,pv=2,cpv=2,cpv_minor=00,mid=NA,humd=0,s_humd=0,acled=0,land=0,elec=0,temp=1,temp_rng=0,m_dtct=1,ac_dst=--,disp_dry=0,dmnd=0,en_scdltmr=1,en_frate=1,en_fdir=1,s_fdir=3,en_rtemp_a=0,en_spmode=0,en_ipw_sep=0,en_mompow=0

If it does not, your device is not yet supported.

To test https connectivity see HTTPS/Registered client support

The response of an unsupported device will look like this:

ret=PARAM NG,msg=404 Not Found

Tested devices are documented here: (https://github.com/cbrandlehner/homebridge-daikin-local/wiki/Tested-devices,-reported-to-work)

If you have other devices or firmware versions working, please update the wiki.

HTTPS/Registered client support

Some models require requests via https containing a registered client token.

It is necessary to register a client token with each device. The same token may be registered with multiple devices.

These instructions are based on comments in GitHub Project ael-code/daikin-control Issue #27

1. Generate a UUID4 (https://www.uuidgenerator.net can be used), e.g. 7b9c9a47-c9c6-4ee1-9063-848e67cc7edd
2. Strip the - from the UUID, i.e. 7b9c9a47c9c64ee19063848e67cc7edd
3. Grab the 13-digit key from the sticker on the back of the controller. e.g. 0123456789012
4. Register the UUID as a client token

curl --insecure -H "X-Daikin-uuid: 7b9c9a47c9c64ee19063848e67cc7edd" -v "https://<controller-ip>/common/register_terminal?key=0123456789012"

This UUID must be used in client requests to the device.

Test your registered token using the above requests but using https instead of http, e.g.

curl --insecure -H "X-Daikin-uuid: 7b9c9a47c9c64ee19063848e67cc7edd" -v "https://192.168.1.88/aircon/get_model_info"
curl --insecure -H "X-Daikin-uuid: 7b9c9a47c9c64ee19063848e67cc7edd" -v "https://192.168.1.88/skifi/aircon/get_model_info"

In the configuration file, make sure you specify https in the apiroute option and add the registered token as the value of uuid in the configuration for each device, e.g.

        "accessories": [
            {
                "accessory": "Daikin-Local",
                "name": "Living room",
                "apiroute": "https://192.168.1.50",
                "uuid": "7b9c9a47c9c64ee19063848e67cc7edd",
                "system": "Default",
                "swingMode": "2",
                "defaultMode": "0",
                "fanMode": "FAN",
                "fanName": "Living room FAN"
            }
        ],

Make sure to use the correct token if a different token has been registered with each device.

Debugging and Testing

The code of this plugins generates debug output. Normally, this debug output is not visible on the homebridge console.

Before reporting any issue or bug, enable debugging and restart.

homebridge-daikin-local's Issues

Fan rate keeps reverting to AUTO after having set it to SILENCE

Describe the bug
With the fan speed set to AUTO, moving the slider to 5% successfully lowers the fan speed to SILENCE. Later, the fan speed reverts to AUTO without any user inputs. The user observes this reversion by both the change to the louder/faster fan sound/speed as well as the value of the fan slider in Homekit getting changed from the user-set 5% back to 15%.

To Reproduce
Information on your wifi gateway from the daikin app:

1. Firmware 2.9.0
2. Wifi adapter BRP072A43 connected to model FTXS

Information on your configuration:

1. Homebridge version 0.4.53, on a Raspberry Pi 3B+, Raspian Buster OS (fully up-to-date)
2. node version 10.20.1 (when I upgraded to homebridge-daikin-local 2020.16.3, I saw a warning stating that node >=12.16.1 was required; however, I was unable to upgrade to this version)

Information from the log:

1. Homebridge log file showing the effect of opening the Home app at 22:08, then changing the fan speed from 15% to 5% at 22:09, then, when relaunching the Home app at 22:10 finding that the fan speed is again back at 15%, which was not desired.

Apr 13 22:08:47 rpi3bp homebridge[1103]: [4/13/2020, 10:08:47 PM] [Daikin406] getTemperatureDisplayUnits: Temperature unit is 0. 0=Celsius, 1=Fahrenheit. Apr 13 22:09:11 rpi3bp homebridge[1103]: [4/13/2020, 10:09:11 PM] [Daikin406] setTargetHeaterCoolerState: received new state 1 Apr 13 22:09:11 rpi3bp homebridge[1103]: [4/13/2020, 10:09:11 PM] [Daikin406] setTargetHeaterCoolerState: query: ret=OK&pow=1&mode=4&adv=&stemp=16.0&shum=0&dt1=25.0&dt2=M&dt3=25.0&dt4=16.0&dt5=16.0&dt7=25.0&dh1=AUTO&dh2=50&dh3=0&dh4=0&dh5=0&dh7=AUTO&dhh=50&b_mode=4&b_stemp=16.0&b_shum=0&alert=255&f_rate=A&f_dir=2&b_f_rate=A&b_f_dir=2&dfr1=5&dfr2=5&dfr3=5&dfr4=A&dfr5=A&dfr6=5&dfr7=5&dfrh=5&dfd1=0&dfd2=0&dfd3=0&dfd4=2&dfd5=2&dfd6=0&dfd7=0&dfdh=0 Apr 13 22:09:12 rpi3bp homebridge[1103]: [4/13/2020, 10:09:12 PM] [Daikin406] setActive: Power is 1, Mode is 4. Going to change power to 1. Apr 13 22:09:29 rpi3bp homebridge[1103]: [4/13/2020, 10:09:29 PM] [Daikin406] setFanSatus received value: true Apr 13 22:09:30 rpi3bp homebridge[1103]: [4/13/2020, 10:09:30 PM] [Daikin406] setFanSatus: new value: 1 Apr 13 22:09:30 rpi3bp homebridge[1103]: [4/13/2020, 10:09:30 PM] [Daikin406] setFanSatus: Power is: 1 Apr 13 22:09:30 rpi3bp homebridge[1103]: [4/13/2020, 10:09:30 PM] [Daikin406] setFanSatus: Mode is: 4 Apr 13 22:09:31 rpi3bp homebridge[1103]: [4/13/2020, 10:09:31 PM] [Daikin406] setFanSatus received value: true Apr 13 22:09:32 rpi3bp homebridge[1103]: [4/13/2020, 10:09:32 PM] [Daikin406] setFanSatus: new value: 1 Apr 13 22:09:32 rpi3bp homebridge[1103]: [4/13/2020, 10:09:32 PM] [Daikin406] setFanSatus: Power is: 1 Apr 13 22:09:32 rpi3bp homebridge[1103]: [4/13/2020, 10:09:32 PM] [Daikin406] setFanSatus: Mode is: 4 Apr 13 22:09:32 rpi3bp homebridge[1103]: [4/13/2020, 10:09:32 PM] [Daikin406] setFanSatus received value: true Apr 13 22:09:33 rpi3bp homebridge[1103]: [4/13/2020, 10:09:33 PM] [Daikin406] setFanSatus: new value: 1 Apr 13 22:09:33 rpi3bp homebridge[1103]: [4/13/2020, 10:09:33 PM] [Daikin406] setFanSatus: Power is: 1 Apr 13 22:09:33 rpi3bp homebridge[1103]: [4/13/2020, 10:09:33 PM] [Daikin406] setFanSatus: Mode is: 4 Apr 13 22:10:23 rpi3bp homebridge[1103]: [4/13/2020, 10:10:23 PM] [Daikin406] getTemperatureDisplayUnits: Temperature unit is 0. 0=Celsius, 1=Fahrenheit. Apr 13 22:10:54 rpi3bp homebridge[1103]: [4/13/2020, 10:10:54 PM] [Daikin406] setTargetHeaterCoolerState: received new state 1 Apr 13 22:10:54 rpi3bp homebridge[1103]: [4/13/2020, 10:10:54 PM] [Daikin406] setTargetHeaterCoolerState: query: ret=OK&pow=1&mode=4&adv=&stemp=16.0&shum=0&dt1=25.0&dt2=M&dt3=25.0&dt4=16.0&dt5=16.0&dt7=25.0&dh1=AUTO&dh2=50&dh3=0&dh4=0&dh5=0&dh7=AUTO&dhh=50&b_mode=4&b_stemp=16.0&b_shum=0&alert=255&f_rate=A&f_dir=2&b_f_rate=B&b_f_dir=2&dfr1=5&dfr2=5&dfr3=5&dfr4=B&dfr5=B&dfr6=5&dfr7=5&dfrh=5&dfd1=0&dfd2=0&dfd3=0&dfd4=2&dfd5=2&dfd6=0&dfd7=0&dfdh=0 Apr 13 22:10:55 rpi3bp homebridge[1103]: [4/13/2020, 10:10:55 PM] [Daikin406] setActive: Power is 1, Mode is 4. Going to change power to 1.

Expected behavior
The expected behaviour was to have the fan speed, after having been set to SILENCE (5%) by the user, remain at 5% until the user requests that it be changed.

This may be an issue with the handling of the "f_rate" parameter or the related memorized fan rate state parameters. I noted this from the info at the URL https://github.com/ael-code/daikin-control/blob/master/README.md. Also, there may be some issue with confusing A (AUTO) with B (SILENCE) [followed by 3,4,5,6,7 speeds] in the indexing sequence. I attach below a screenshot from the above URL.

Screenshots

Additional context
Thanks for putting together a great plugin that I am finding immensely useful!

FAN control in mode?

Hi,

i dont have a FAN option in mode (homekit). Is it possible to add FAN to mode in homekit?
(I have only OFF, HEAT, COOL, AUTO).

Thank you for your response

Can't Fetch Data (Error getting state: null)

I currently have this plugin installed on my Raspberry Pi. Upon launching homebridge everything starts correctly. In the home app on my iPhone the aircon is present but reads 10 degrees and has no data. In homebridge, the logs read:

[6/12/2019, 7:48:58 PM] [AC] getTargetHeatingCoolingState: 3 [6/12/2019, 7:48:58 PM] [AC] Temperature unit is 0. 0=Celsius, 1=Fahrenheit. [6/12/2019, 7:48:59 PM] [AC] Error reading temperature: null [6/12/2019, 7:48:59 PM] [AC] Error getting operation mode: null [6/12/2019, 7:48:59 PM] [AC] Error reading target temperature: null

I imagine this could have something to do with the router giving the wrong HTTP returns.

In the browser, typing http://192.168.1.228/skyfi/aircon/get_sensor_info/ returns:
ret=OK,err=0,htemp=22,otemp=18

Removing /skyfi returns:
ret=PARAM NG,msg=404 Not Found

My config is as follows:
{ "bridge": { "name": "Homebridge", "pin": "987-65-432", "username": "B8:27:EB:AF:6F:89" }, "accessories": [{ "accessory": "PiTemperature", "name": "PiTemp" }, { "accessory": "Daikin-Local", "name": "AC", "apiroute": "http://192.168.1.228/skyfi" } ], etc (my JSON is verified and homebridge launches fine - I have just excluded the platforms section of the JSON, let me know if you need it)

Vera conflict?

Didn’t seem to work for me. Seems to be something that is in conflict with Vera.....
Not figured out what’s happening yet.

(by the way, thanks for keeping this going. Great to control the ac via HomeKit....thanks)

Compability with online controller BRP069A45

Hi! Please, add supporting BRP069A45 series Wi-Fi controller, it did not work with full functionality. It has only FAN mode in Homeridge Accessories, but other AC functions (such as Silent Mode, Comfort Mode, Econo, Swing, Cool, Dry & Heat) are not supported. I have two ACs (ATX35KV / ARX35K and ATX20KV / ARX20K) with the same Wi-Fi modules, and this is true for both devices.

Information from ATX35KV / ARX35K
basic_info: ret=OK,type=aircon,reg=eu,dst=1,ver=1_2_51,rev=D3A0C9F,pow=0,err=0,location=0,name=%44%61%69%6b%69%6e%41%50%35%32%36%36%31,icon=4,method=home only,port=30050,id=,pw=,lpw_flag=0,adp_kind=3,pv=2,cpv=2,cpv_minor=00,led=1,en_setzone=1,mac=409F38728A7F,adp_mode=run,en_hol=0,grp_name=,en_grp=0

get_model_info: ret=OK,model=0000,type=N,pv=2,cpv=2,cpv_minor=00,mid=NA,humd=0,s_humd=0,acled=0,land=0,elec=0,temp=1,temp_rng=0,m_dtct=0,ac_dst=--,disp_dry=0,dmnd=0,en_scdltmr=1,en_frate=1,en_fdir=1,s_fdir=1,en_rtemp_a=0,en_spmode=0,en_ipw_sep=0,en_mompow=0

Information from ATX20KV / ARX20K
basic_info: ret=OK,type=aircon,reg=eu,dst=1,ver=1_2_51,rev=D3A0C9F,pow=0,err=0,location=0,name=%44%61%69%6b%69%6e%41%50%32%36%35%36%39,icon=0,method=home only,port=30050,id=,pw=,lpw_flag=0,adp_kind=3,pv=2,cpv=2,cpv_minor=00,led=1,en_setzone=1,mac=409F38727104,adp_mode=run,en_hol=0,grp_name=,en_grp=0

get_model_info:
ret=OK,model=0000,type=N,pv=2,cpv=2,cpv_minor=00,mid=NA,humd=0,s_humd=0,acled=0,land=0,elec=0,temp=1,temp_rng=0,m_dtct=0,ac_dst=--,disp_dry=0,dmnd=0,en_scdltmr=1,en_frate=1,en_fdir=1,s_fdir=1,en_rtemp_a=0,en_spmode=0,en_ipw_sep=0,en_mompow=0

Error: connect ECONNREFUSED 192.168.0.31:80

I have a BRP072C42 and I am getting this error could you suggest if this plugin support this model.

I can connect by passing "X-Daikin-uuid" and I had to register using the Key that came with the wifi controller

Temperature Unit

I get the message:

getTemperatureDisplayUnits: Temperature unit is 0. 0=Celsius, 1=Fahrenheit

In the log, and I want to set it to Fahrenheit. How do I do that? Also Home appears to be using Fahrenheit when I control it!

Two devices, two different views

In HomeBridge my two identical Daikin controllers are displayed differently, see screenshot. Can I configure this somewhere?

Logfile below the picture.

[8/6/2019, 7:46:20 PM] [Daikin Anna] getTemperatureDisplayUnits: Temperature unit is undefined. 0=Celsius, 1=Fahrenheit.
[8/6/2019, 7:46:20 PM] [Daikin Maximilian] getTemperatureDisplayUnits: Temperature unit is undefined. 0=Celsius, 1=Fahrenheit.
[8/6/2019, 7:46:20 PM] [Daikin Anna] getFanSpeed: f_rate is A
[8/6/2019, 7:46:20 PM] [Daikin Anna] getFanSpeed: The current speed is 15
[8/6/2019, 7:46:21 PM] [Daikin Maximilian] getFanSpeed: f_rate is A
[8/6/2019, 7:46:21 PM] [Daikin Maximilian] getFanSpeed: The current speed is 15

Nix geht mehr

Nach dem Update hängt die ganze Homebridge was an einem Daikin Controller zu liegen scheint. Vor dem Update hat alles Funktioniert.

Not possible to switch back to cool mode from fan mode

It's not possible to turn on cool mode when it was in vent mode in those situations (It's seems possible to change it in HomeKit, but with no effect):
iOS 12.4

• when ventilation mode is on (fan shows correctly in HomeKit & works and I turn on the cooling mode, it DOES NOT turn on cooling, but stays in ventilation mode.
• when ventilation mode is off (but had it on before), it's the same as above.
  Basically it's the same for iOS 13 beta, without the second button.

It seems, that if once ventilation (fan) is, or has been active, it's not possible to go back to Cooling/Heating/Auto mode.

To Reproduce
Information on your wifi gateway from the daikin app:
1_2_51
BRP069B41

Information on your configuration:

1. Homebridge 0450

Information from the log:

Expected behavior
When i press Fan mode, it should be Fan. If i press cool mode when the fan is active or had been active before, it should switch to cool mode.

Thanks a lot for your work

The FDXM-F3 update affects only the first Unit

Hello, the FDXM-F3 update affects only my first Unit

the output of the second OFF command is this:
[2019-6-23 07:56:24] [Zona Notte] Setting POWER to OFF, MODE to OFF and TARGET TEMPERATURE to 23

another problem is that the 0 mode on this model is wrong, the AUTO mode is 1

not compare acessorie

I have installed plugin but can't see whenstart homebridge.
Device supported:
ret=OK,model=FBA60A2VEB9,type=N,pv=0,cpv=0,mid=89E1,s_fdir=0,frate_steps=3,en_frate_silent=0,en_frate_auto=1,en_scdltmr=1,hmlmt_l=16.0,hmlmt_h=32.0,cmlmt_l=16.0,cmlmt_h=32.0

This is part in json:
Homebridge config
"accessories": [
{
"accessory": "Daikin-Local",
"name": "Living room",
"apiroute": "http://my device ip",
"system": "Default",
"swingMode": "2",
"defaultMode": "0",
"fanMode": "FAN",
"fanName": "Living room FAN"
}
],

why this?

DKN Cloud Wifi

I have a major remodel under way and am installing Daikin AC that are only supported by the new DKN Cloud Wifi modules. None of the existing wifi thermostats are supported by my model. It may be because the model is mostly installed in commercial applications

This looks like the most mature HomeBridge module for a Daikin product. I am hoping it can be modified to support the new controller. I am prepared to fork and do this myself if it's feasible, but obviously it would be easier for me if the new model were supported by this project. I've done a little JS coding, but not much. I can handle it though if necessary.

The API information is here: https://cms.daikincomfort.com/docs/default-source/professional-documents/residential/manuals/daikin-dkn-cloud-wi-fi-adaptor.pdf

'Daikin-Local' was not registered

Hi,

I've been using Daikin-local with homebeidge for over a year now, infact it was the first plugin I used with Homebridge.
After several different builds, I settled on Hoobs using thin client with Debian Buster.
Daikin-local installed without issue months ago, but now after I upgraded the plugin through Hoobs, it failes and prevents the Homebridge service from starting.

Below is the current log where Daikin-local falls over.
Please help - I love being able to control my a/c with Siri.

Jamie

[Homebridge] [3/28/2020, 8:27:44 AM] Error: The requested accessory 'Daikin-Local' was not registered by any plugin.
at API.accessory (/home/hoobs/.hoobs/node_modules/@hoobs/homebridge/lib/api.js:45:19)
at Server._loadAccessories (/home/hoobs/.hoobs/node_modules/@hoobs/homebridge/lib/server.js:258:48)
at Server.run (/home/hoobs/.hoobs/node_modules/@hoobs/homebridge/lib/server.js:78:14)
at module.exports (/home/hoobs/.hoobs/node_modules/@hoobs/homebridge/lib/cli.js:90:12)
at Object. (/home/hoobs/.hoobs/node_modules/@hoobs/homebridge/bin/homebridge:10:63)
at Module._compile (internal/modules/cjs/loader.js:959:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
at Module.load (internal/modules/cjs/loader.js:815:32)
at Function.Module._load (internal/modules/cjs/loader.js:727:14)
at Function.Module.runMain (internal/modules/cjs/loader.js:1047:10)[Homebridge] [3/28/2020, 8:27:44 AM] Got SIGTERM, shutting down service...

switch with other plugin?

I'm sorry about my English.

I don't know much about Linux. Currently I have the DirtyDevWork/homebridge-daikin plugin, but since the firmware update it no longer works with homebridge. Can I replace the homebridge-daikin plugin with yours? I just need to uninstall and install your plugin?
Many thanks in advance,
C

Typo in Excample config

typo in the excample config fanName <-> nameFan

Expose more configurations

Hi, can you expose more configurations:
I have an aircon that has heating temperatures from 10 to 30 celsius and cooling from 18 to 32 celsius but in the plugin for example heating it is maxed at 25, can we set the mins and max from configuration?

Also it would be nice to have if possible a (toggle) mode that just turns on and off with current settings

Thank you

Homebridge detects but cannot update the status

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=1,ac_dst=--,disp_dry=0,dmnd=1,en_scdltmr=1,en_frate=1,en_fdir=1,s_fdir=3,en_rtemp_a=0,en_spmode=7,en_ipw_sep=1,en_mompow=1,hmlmt_l=10.0

Hi!
Above is a copy of what /aircon/get_model_info returns for me. It seems to be detecting it but I'm puzzled by the model being 0000..?
Could this be the reason Homebridge isn't picking anything up (just showing a fan and temperature block in the Home app)?
Thanks!!

One click turn on/off creates issues with iOS 13

In iOS 12 there are two accessories visible in the room: the fan and the airco. When you click on the fan it turns it on or off. Holding the fan allows to change the speed of the fan..
With iOS 13 there is only 1 accessory anymore but it has two cards that open when you click on it. You can not hold anymore so the feature that turns the fan off/on with a single click does not play nice with iOS 13. When the fan is on you are unable to change anything without turning it off first because you need to click on the accessory first.

Default Values are 10C when (re)starting homebridge

@cbrandlehner first off much respect and many thanks for fixing the connection issue and publishing a new package. Really saved a great plugin of going to waste.

Would there be any way to set the default values after a start or restart to a safer value because now it defaults to 10C. Would be great if that default would be 21 or soto avoid accidental cooling down. I know the unit is off by default anyway but just on the safe side.

I know the thermostat also support min max temp ranges in homekit so not sure if that would be an option.

Many thanks again

nameFan and fanName mixup?

Thanks for building this great functionality. See below for a possible small bug:

Describe the bug
In order to avoid an error when I use "fanName" in my accessory definition in the config.json file, I find that I need to use "nameFan" instead. This is contrary to what is provided in sample-config.json, and may be a situation in which a change of the name was not fixed everywhere. I saw there was a change made back in, I think, August 2019.

To Reproduce
Information on your wifi gateway from the daikin app:

1. 2.9.0
2. Daikin BRP072A43 adapter

Information on your configuration:

1. Homebridge 0.4.50

Option to disable fan control

My AC unit doesn't support fan control via wireless. It's just mode (cool/heat/auto/off) and temperature. Is it possible to disable the fan functionality so I can't see the fan control? The fan speed at the moment is defaulting to 0 and if I accidentally touch it, it turns my AC off.

For your information, get_model_info returns this:
ret=OK,model=NOTSUPPORT,type=N,pv=0,cpv=0,mid=NA,s_fdir=0,en_scdltmr=1
Despite the "NOTSUPPORT", controlling it works fine. It's just the fan speed stuff I need to remove.

Issue with apiroute

Hello, nice job with this project, thanks for keeping alive this! I tried homebridge-daikin of DirtyDevWork and yours homebridge-daikin-local. With homebridge-daikin zero problem while with yours seems i cant pass apiroute correctly. Here the error:

[3/15/2019, 8:00:06 PM] Loaded config.json with 3 accessories and 0 platforms.
[3/15/2019, 8:00:06 PM] ---
[3/15/2019, 8:00:07 PM] Loaded plugin: homebridge-bme280
[3/15/2019, 8:00:07 PM] Registering accessory 'homebridge-bme280.BME280'
[3/15/2019, 8:00:07 PM] ---
[3/15/2019, 8:00:08 PM] Loaded plugin: homebridge-daikin-local
[3/15/2019, 8:00:08 PM] Registering accessory 'homebridge-daikin-local.Daikin-Local'
[3/15/2019, 8:00:08 PM] ---
[3/15/2019, 8:00:09 PM] Loaded plugin: homebridge-sonoff-tasmota-http
[3/15/2019, 8:00:09 PM] Registering accessory 'homebridge-sonoff-tasmota-http.SonoffTasmotaHTTP'
[3/15/2019, 8:00:09 PM] ---
[3/15/2019, 8:00:09 PM] Loading 0 platforms...
[3/15/2019, 8:00:09 PM] Loading 3 accessories...
[3/15/2019, 8:00:09 PM] [Daikin] Initializing Daikin-Local accessory...
/usr/local/lib/node_modules/homebridge-daikin-local/index.js:16
const myURL = new URL(config.apiroute);
^

ReferenceError: URL is not defined
at Object.Daikin (/usr/local/lib/node_modules/homebridge-daikin-local/index.js:16:27)
at Server._loadAccessories (/usr/local/lib/node_modules/homebridge/lib/server.js:297:29)
at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:87:38)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:45:10)
at Object. (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (module.js:577:32)
at Object.Module._extensions..js (module.js:586:10)
at Module.load (module.js:494:32)
at tryModuleLoad (module.js:453:12)
at Function.Module._load (module.js:445:3)

And this is my config.json:

"accessories":[
{
"accessory":"Daikin-Local",
"name":"Daikin",
"apiroute":"http://192.168.0.8"
}

Working Devices

The following Model/Device combinations are working for various Daikin Cora models in Australia:

Daikin BRP072A42, Model 0C87, Firmware 3.4.3
Daikin BRP072A42, Model 0C89, Firmware 3.4.3
Daikin BRP072A42, Model 0C8A, Firmware 3.4.3
Daikin BRP072A42, Model 0C8B, Firmware 3.4.3
Daikin BRP072A42, Model 0EB0, Firmware 3.4.3

switch the AC on and off with a tap

Is it possible to redesign the plugin so that you can switch the AC on and off with a tap in the home app?

AC in Fan mode after changing the fan intensity

Hello,

First of all congrats for what you have done.

Describe the bug
When turn the AC ON just using the "modes" all goes well but if I change the FAN intensity just force the FAN mode (turning off the "Heat mode")
To Reproduce
Information on your wifi gateway from the daikin app:

1. Firmware version 1.2.51
2. If known: It's the built in wifi adapter of Daikin Stylish - FTXA-AW

Information on your configuration:

1. Homebridge config

        "name": "AC Escritório",
        "apiroute": "http://192.168.1.70",
        "system": "Default",
        "swingMode": "3",
        "defaultMode": "null",
        "accessory": "Daikin-Local"
   

Information from the log:

As you can see in the last line is changing the mode to 6 after I change the fan.

[11/28/2019, 10:19:51 AM] [AC Escritório] setActive: Power is 0, Mode is 4. Going to change power to 1.
[11/28/2019, 10:20:24 AM] [AC Quarto dos Pais] getTemperatureDisplayUnits: Temperature unit is 0. 0=Celsius, 1=Fahrenheit.
[11/28/2019, 10:20:24 AM] [AC Escritório] getTemperatureDisplayUnits: Temperature unit is 0. 0=Celsius, 1=Fahrenheit.
[11/28/2019, 10:20:24 AM] [AC Quarto do Joaquim] getTemperatureDisplayUnits: Temperature unit is 0. 0=Celsius, 1=Fahrenheit.
[11/28/2019, 10:20:24 AM] [AC Sala] getTemperatureDisplayUnits: Temperature unit is 0. 0=Celsius, 1=Fahrenheit.
[11/28/2019, 10:20:26 AM] [AC Escritório] setTargetHeaterCoolerState: received new state 1
[11/28/2019, 10:20:26 AM] [AC Escritório] setTargetHeaterCoolerState: query: ret=OK&pow=1&mode=4&adv=&stemp=23.0&shum=0&dt1=23.0&dt2=M&dt3=25.0&dt4=23.0&dt5=23.0&dt7=23.0&dh1=0&dh2=50&dh3=0&dh4=0&dh5=0&dh7=0&dhh=50&b_mode=4&b_stemp=23.0&b_shum=0&alert=255&f_rate=A&f_dir=0&b_f_rate=A&b_f_dir=0&dfr1=A&dfr2=A&dfr3=5&dfr4=A&dfr5=A&dfr6=A&dfr7=A&dfrh=5&dfd1=0&dfd2=2&dfd3=0&dfd4=0&dfd5=0&dfd6=3&dfd7=0&dfdh=0&dmnd_run=0&en_demand=0
[11/28/2019, 10:20:26 AM] [AC Escritório] setActive: Power is 1, Mode is 4. Going to change power to 1.
[11/28/2019, 10:20:36 AM] [AC Escritório] setFanSatus received value: true
[11/28/2019, 10:20:37 AM] [AC Escritório] setFanSatus: new value: 1
[11/28/2019, 10:20:37 AM] [AC Escritório] setFanSatus: Power is: 1
[11/28/2019, 10:20:37 AM] [AC Escritório] setFanSatus: Mode is: 4
[11/28/2019, 10:20:37 AM] [AC Escritório] setFanSatus received value: true
[11/28/2019, 10:20:37 AM] [AC Escritório] setFanSatus: new value: 1
[11/28/2019, 10:20:37 AM] [AC Escritório] setFanSatus: Power is: 1
[11/28/2019, 10:20:37 AM] [AC Escritório] setFanSatus: Mode is: 6

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Request for other Aircon Controllers

This probably isn’t the best place to post this, but wondering if you would be able to work on the E-zone Controller by Ambience/Advantage Air (uses E-zone app)? I would love to get a Homebridge plug-in for this but don’t have the know how.

Another person who contacted me has created individual switches for each function of the AC through HTTP commands

Compability with online controller BRP069A81

Hello everyone.
I'm gonna buy soon five FDXM-F9 units for my new house and on internet I saw that the correct online unit is the BRP069A81.

I wanna understand if I have good chance that this plugin will work with this unit.

Thank you so much.

Sometimes ECONNRESET

Describe the bug
Sometimes I get this error. Especially if I go to homekit screen on my phone multiple times.
After I get this error, all homebridge devices hangs. It returns to normal after a couple of tries.

ERROR: The URL http://192.168.1.65/aircon/get_control_info returned error Error: socket hang up
    at connResetException (internal/errors.js:608:14)
    at Socket.socketOnEnd (_http_client.js:460:23)
    at Socket.emit (events.js:322:22)
    at endReadableNT (_stream_readable.js:1187:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  code: 'ECONNRESET',
  response: undefined,
  retries: 5
}

To Reproduce
Information on your wifi gateway from the daikin app:

1. Firmware version: 1.2.51
2. If known: BRP069B43

Information on your configuration:

1. Homebridge config

        {
            "name": "AC",
            "apiroute": "http://192.168.1.65",
            "system": "Default",
            "swingMode": "1",
            "fanMode": "FAN",
            "fanName": "AC Fan",
            "defaultMode": "0",
            "accessory": "Daikin-Local"
        }

Information from the log:

1. Homebridge log file showing relevant information.

ERROR: The URL http://192.168.1.65/aircon/get_control_info returned error Error: socket hang up
    at connResetException (internal/errors.js:608:14)
    at Socket.socketOnEnd (_http_client.js:460:23)
    at Socket.emit (events.js:322:22)
    at endReadableNT (_stream_readable.js:1187:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  code: 'ECONNRESET',
  response: undefined,
  retries: 5
}

Expected behavior
There should not be any connection problem. The adapter is located in a good wifi spot with solid connection.

Can't switch off BRP069A81

Hi, the plugin can't turn the AC off (BRP069A81 wifi working with FDXM35F unit).
However, turning on by choosing the mode (cool/warm) and changing the temperature do work. Can this be solved somehow?

No request: just try to tell you my Daikin is working...

Daikin Siesta ATXP-K3
Daikin Wifi Controller
FW 3.3.6

plugin crashes if configuration is wrong

If a mandatory configuration option is missing, the plugin crashes at start - causing homebridge to terminate as well.

BRP072C42 support

Would be great to add support for the BRP072C42 controller (Daikin iSmile units).

Getting this error when adding:

(node:651) UnhandledPromiseRejectionWarning: RequestError: Error: Invalid URI "192.168.1.116/aircon/get_model_info" at new RequestError (/homebridge/node_modules/homebridge-daikin-unofficial/node_modules/request-promise-core/lib/errors.js:14:15) at Request.plumbing.callback (/homebridge/node_modules/homebridge-daikin-unofficial/node_modules/request-promise-core/lib/plumbing.js:87:29) at Request.RP$callback [as _callback] (/homebridge/node_modules/homebridge-daikin-unofficial/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/homebridge/node_modules/homebridge-daikin-unofficial/node_modules/request/request.js:185:22) at Request.emit (events.js:310:20) at Request.init (/homebridge/node_modules/homebridge-daikin-unofficial/node_modules/request/request.js:273:17) at Request.RP$initInterceptor [as init] (/homebridge/node_modules/homebridge-daikin-unofficial/node_modules/request-promise-core/configure/request2.js:45:29) at new Request (/homebridge/node_modules/homebridge-daikin-unofficial/node_modules/request/request.js:127:8) at request (/homebridge/node_modules/homebridge-daikin-unofficial/node_modules/request/index.js:53:10) at DaikinApi.getModelInfo (/homebridge/node_modules/homebridge-daikin-unofficial/dist/index.js:88:32) at DaikinAccessory.getModelInfo (/homebridge/node_modules/homebridge-daikin-unofficial/dist/index.js:274:42) at new DaikinAccessory (/homebridge/node_modules/homebridge-daikin-unofficial/dist/index.js:266:14) at Server._loadAccessories (/usr/local/lib/node_modules/homebridge/lib/server.js:308:29) at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:91:38) at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:59:10) at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22) at Module._compile (internal/modules/cjs/loader.js:1156:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1176:10) at Module.load (internal/modules/cjs/loader.js:1000:32) at Function.Module._load (internal/modules/cjs/loader.js:899:14) at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:74:12) at internal/main/run_main_module.js:18:47 (node:651) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:651) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Temperature changing automatically when triggered from scene

Describe the bug
Temperature gets set to 21ºC when triggered twice from a Home Scene and AC does not turn on every time as expected.

To Reproduce
Hi have a scene that sets my Daikin to "Cold" mode at 25ºC. It does not work as expected since a lot of times the AC does not turn ON and, if it is already on and the scene gets triggered, the temperature gets lowered to 21/22ºC.

1. Firmware version: 3.3.6
2. If known: Model information of the wifi gateway (unknown, but Daikin Original)

Information on your configuration:

1. Homebridge config
   Nothing special, just the name and the local IP of the accessory

"accessories": [
        {
            "name": "Camera da letto",
            "apiroute": "http://192.168.1.173",
            "accessory": "Daikin-Local"
        }
]

Information from the log:

1. Homebridge log file showing relevant information.

[7/12/2019, 2:56:41 PM] [Camera da letto] set fan status
[7/12/2019, 2:56:41 PM] [Camera da letto] true
[7/12/2019, 2:56:41 PM] [Camera da letto] Setting POWER to OFF, MODE to OFF and TARGET TEMPERATURE to 25 (0000)
[7/12/2019, 2:56:41 PM] [Camera da letto] DaikinMode: URL is: http://192.168.1.173/aircon/set_control_info?pow=0&mode=0&stemp=25&shum=0&f_rate=
[7/12/2019, 2:56:41 PM] [Camera da letto] set Threshold Temp: 23
[7/12/2019, 2:56:41 PM] [Camera da letto] Setting POWER to OFF, MODE to OFF and TARGET TEMPERATURE to 23 (0000)
[7/12/2019, 2:56:41 PM] [Camera da letto] DaikinMode: URL is: http://192.168.1.173/aircon/set_control_info?pow=0&mode=0&stemp=23&shum=0&f_rate=
[7/12/2019, 2:56:41 PM] [Camera da letto] set fan speed
[7/12/2019, 2:56:41 PM] [Camera da letto] 5
[7/12/2019, 2:56:41 PM] [Camera da letto] Setting POWER to OFF, MODE to OFF and TARGET TEMPERATURE to 23 (0000)
[7/12/2019, 2:56:41 PM] [Camera da letto] DaikinMode: URL is: http://192.168.1.173/aircon/set_control_info?pow=0&mode=0&stemp=23&shum=0&f_rate=B
[7/12/2019, 2:56:41 PM] [Camera da letto] Setting target temperature to 25 degrees
[7/12/2019, 2:56:41 PM] [Camera da letto] Setting POWER to OFF, MODE to OFF and TARGET TEMPERATURE to 25 (0000)
[7/12/2019, 2:56:41 PM] [Camera da letto] DaikinMode: URL is: http://192.168.1.173/aircon/set_control_info?pow=0&mode=0&stemp=25&shum=0&f_rate=B
[7/12/2019, 2:56:41 PM] [Camera da letto] Changing operation mode from 0 to 2
[7/12/2019, 2:56:41 PM] [Camera da letto] Setting POWER to ON, MODE to COOL and TARGET TEMPERATURE to 25 (0000)
[7/12/2019, 2:56:41 PM] [Camera da letto] DaikinMode: URL is: http://192.168.1.173/aircon/set_control_info?pow=1&mode=3&stemp=25&shum=0&f_rate=B
[7/12/2019, 2:56:41 PM] [Camera da letto] set Threshold Temp: 22
[7/12/2019, 2:56:41 PM] [Camera da letto] Setting POWER to ON, MODE to COOL and TARGET TEMPERATURE to 22 (0000)
[7/12/2019, 2:56:41 PM] [Camera da letto] DaikinMode: URL is: http://192.168.1.173/aircon/set_control_info?pow=1&mode=3&stemp=22&shum=0&f_rate=B

Expected behavior
The AC should turn on if turned off and should be set on cold, 25ºC.

Screenshots

Turning on/off Daikin with Apple Siri always switches air condition to 'AUTO'

When I turn off or on the Aircon with Apple Siri it always switches to AUTO-mode.
It should leave the state as it is.

I am using the Daikin WIFI controller.

This is what I find in the Homebridge log:

[6/21/2019, 7:30:54 PM] [Frosty] Setting POWER to ON, MODE to AUTO and TARGET TEMPERATURE to 21

Then I switch manually with the Apple Home App to : COOL

Log:
[6/21/2019, 7:31:52 PM] [Frosty] Setting POWER to ON, MODE to COOL and TARGET TEMPERATURE to 21

THEN I turn it OFF with Apple Siri:

[6/21/2019, 7:32:41 PM] [Frosty] Setting POWER to OFF, MODE to OFF and TARGET TEMPERATURE to 21

THEN I turn it on again with Apple Siri:

[6/21/2019, 7:33:24 PM] [Frosty] Setting POWER to ON, MODE to AUTO and TARGET TEMPERATURE to 21

I think the last mode should not be changed.

Latest Daikin Firmware 3.3.6

FTXM95PVMA Works

Again like a previous post, this is not an issue but a report that my Daikin is also working with this plugin, details are below:

Daikin P-Series FTXM95PVMA
Daikin BRP072A42 wireless LAN adaptor
Firmware 3.4.3

Working as expected although when testing the http://x.x.x.x/aircon/get_model_info I get, which compared to what others have posted is unusual and not an expected return log:

ret=OK,model=NOTSUPPORT,type=N,pv=0,cpv=0,mid=NA,s_fdir=0,en_scdltmr=1

Don't see swing mode?

Describe the bug
I don't see swing mode. I selected vertical swing mode (default) for my daikin FKXS20 unit. I use the BRP069A43 wifi controller. Firmware is 1.2.51.

I get this answer from the browser.

ret=OK,model=NOTSUPPORT,type=N,pv=0,cpv=0,mid=NA,s_fdir=1,en_scdltmr=1

Everything works despite the swing mode. I can not select swing mode anywhere.

Grtz

Info about configuration tag "system"

Hi, I saw there is a tag called "system" in the example configuration and reports "Default" as value.
What are the other values we can use in this tag and what is the purpose?

Thanks

When the Daikin is down homebridge hang

Hello, it's normal that if the Daikin is not connected to the wireless, the homebridge platform completely stop to work?

mode DRY causing problem as no target temperature is set

Describe the bug
If you use the daikin app to enable DRY mode, homebridge-daikin.local has a problem as no target temp is set.

To Reproduce
Information on your wifi gateway from the daikin app:

1. Firmware version: 1.2.51
2. If known: Model information of the wifi gateway: 0AB9

Information on your configuration:

1. Homebridge config

"accessories": [
        {
            "accessory": "Daikin-Local",
            "name": "Living room",
            "apiroute": "http://192.168.1.50"
        },
        {
            "accessory": "Daikin-Local",
            "name": "Master bedroom",
            "apiroute": "http://192.168.1.51"
        }
    ],

Information from the log:

1. Homebridge log file showing relevant information.

[6/20/2019, 9:06:15 AM] [Master bedroom] Target temperature is NaN degrees

Expected behavior
Proper handling.

Screenshots
n/a

Additional context
nothing to add.

Fan in A/C Mode

Hi There

loving the new upates, keep up the great work !

one thing though that may be a quirk or an issue im finding is the fan
as you can only set to fan or dry, if i have the AC on cool and want to slow down the fan speed, by using the fan control it changes the mode to Fan or Dry

is there a possibility so that when using the fan it stays on the mode that its currently on such as heat, cool or auto?

cheers

BRP072C42 support

I reopen a feature request re compatibility with the controller BRP072C42.
It’s fairly simple to add: the request you send to the controller must have a header “X-Daikin-uuid: {uuid}” and must use https.
The uuid can be added in the config.json file.

The other homebridge plugin (Daikin unofficial) that I wrongly pasted the logs of here doesn’t support different FAN so I would think it would be great to add the https compatibility to this one. It does supper https and uuid though.

For more info you can check this out: https://community.home-assistant.io/t/daikin-brp072c42-wifi-custom-component/126981

Enhancement: Support for Swing Mode

Is your feature request related to a problem? Please describe.
I would like to be able to enable or disable the swing mode.

Describe the solution you'd like
In Apple Home Kit, I expect to see an option to enable or disable swing mode.

Describe alternatives you've considered
Use the native Daikin App.

Looking for ways to pimp this project

I would like to pimp the documentation by adding some cool pictures to the readme.

In case you have pictures of your Daikin AC, the Daikin WIFI controller or your Apple Home App, please share these.
I am looking forward to see if anybody here uses Apple Home workflows, like "switch off AC when nobody is at home" or even better.

If you have ideas on how to improve the readme, please let me know.

Switch the AC on and off with a tap in the home app

Is it possible to redesign the plugin so that you can switch the AC on and off with a tap in the home app?

HomeBridge service start problems after upgrading

Hi,
after upgrading to latest version (2020.10.1), I'm no longer able to start homebridge service with this error:

[Homebridge] [3/10/2020, 19:54:25] Error: The requested accessory 'Daikin-Local' was not registered by any plugin.
    at API.accessory (/home/hoobs/.hoobs/node_modules/@hoobs/homebridge/lib/api.js:45:19)
    at Server._loadAccessories (/home/hoobs/.hoobs/node_modules/@hoobs/homebridge/lib/server.js:258:48)
    at Server.run (/home/hoobs/.hoobs/node_modules/@hoobs/homebridge/lib/server.js:78:14)
    at module.exports (/home/hoobs/.hoobs/node_modules/@hoobs/homebridge/lib/cli.js:90:12)
    at Object.<anonymous> (/home/hoobs/.hoobs/node_modules/@hoobs/homebridge/bin/homebridge:10:63)
    at Module._compile (internal/modules/cjs/loader.js:959:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
    at Module.load (internal/modules/cjs/loader.js:815:32)
    at Function.Module._load (internal/modules/cjs/loader.js:727:14)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1047:10)
[Homebridge] [3/10/2020, 19:54:25] Got SIGTERM, shutting down service...

My first try was to uninstall the plugin in order to install it again, but I got this error when uninstalling

npm
 ERR! code EEXIST
npm
 ERR! path /home/hoobs/.hoobs/node_modules/superagent/node_modules/.bin/semver
npm
 ERR! Refusing to delete /home/hoobs/.hoobs/node_modules/superagent/node_modules/.bin/semver: is outside /home/hoobs/.hoobs/node_modules/superagent/node_modules/semver and not a link
npm ERR! File exists: /home/hoobs/.hoobs/node_modules/superagent/node_modules/.bin/semver
npm ERR! Move it away, and try again.
npm ERR! A complete log of this run can be found in:
npm ERR!
     /home/hoobs/.npm/_logs/2020-03-10T18_57_03_099Z-debug.log

Here you have my config.json

"accessories": [
        {
            "name": "Condizionatore Ufficio",
            "apiroute": "http://192.168.1.174",
            "system": "Default",
            "swingMode": "2",
            "defaultMode": "0",
            "accessory": "Daikin-Local",
            "fanMode": "FAN",
            "fanName": "Condizionatore Ufficio FAN"
        },
        {
            "name": "Condizionatore Sala da Pranzo",
            "apiroute": "http://192.168.1.170",
            "system": "Default",
            "swingMode": "2",
            "defaultMode": "0",
            "accessory": "Daikin-Local",
            "fanMode": "FAN",
            "fanName": "Condizionatore Sala da Pranzo FAN"
        },
        {
            "name": "Condizionatore Salotto",
            "apiroute": "http://192.168.1.171",
            "system": "Default",
            "swingMode": "2",
            "defaultMode": "0",
            "accessory": "Daikin-Local",
            "fanMode": "FAN",
            "fanName": "Condizionatore Salotto FAN"
        },
        {
            "name": "Condizionatore Stanzetta",
            "apiroute": "http://192.168.1.172",
            "system": "Default",
            "swingMode": "2",
            "defaultMode": "0",
            "accessory": "Daikin-Local",
            "fanMode": "FAN",
            "fanName": "Condizionatore Stanzetta FAN"
        },
        {
            "name": "Condizionatore Camera da letto",
            "apiroute": "http://192.168.1.173",
            "system": "Default",
            "swingMode": "2",
            "defaultMode": "0",
            "accessory": "Daikin-Local",
            "fanMode": "FAN",
            "fanName": "Condizionatore Camera da letto FAN"
        },

Before updating everything was working as expected

Thank you!

AC not turning off

Describe the bug
Turning off the AC is not working. Maybe related to #7 ?

To Reproduce
Information on your wifi gateway from the daikin app:

1. Firmware version : 3.3.6
2. BRP069A81 wifi controller, for indoor units => FDXM50F3V1B & FBA35A2VEB

Information from the log:

Setting POWER to OFF, MODE to OFF and TARGET TEMPERATURE to 27 (FDXM50F3V1B)
DaikinMode: URL is: http://192.168.1.13/aircon/set_control_info?pow=0&mode=0&stemp=27&shum=0&f_rate=7

Expected behavior
AC should power OFF, but it does not.
Wifi adapter HTTP response is: ret=PARAM NG

How to get this fixed :)
Using the same URL but with removing mode=0 parameter fix the issue. The AC is powering OFF.
Setting mode to the original mode (something different than 0) works too.

Dry Mode

Is your feature request related to a problem? Please describe.
I'd like to set my AC to dry mode

Describe the solution you'd like
I'd like to have a "Dry" button alongsite to "auto", "cold" and "warm"

Describe alternatives you've considered
Using the Daikin App

plugin crashes if HTTP response is not a JSON as expected

Describe the bug
In case you connect to a not supported device, eg by mistaking the IP address, the plugin crashes.

To Reproduce
Information on your wifi gateway from the daikin app:

1. Firmware version: 1.2.51
2. If known: Model information of the wifi gateway: 0AB9

Information on your configuration:

1. Homebridge config

"accessories": [
        {
            "accessory": "Daikin-Local",
            "name": "Living room",
            "apiroute": "http://192.168.1.50"
        },
        {
            "accessory": "Daikin-Local",
            "name": "Master bedroom",
            "apiroute": "http://192.168.1.51"
        }
    ],

Information from the log:

1. Homebridge log file showing relevant information.

6/20/2019, 6:30:53 AM] [Master bedroom] Successfully established connection.
[6/20/2019, 6:30:53 AM] SyntaxError: Unexpected token 
 in JSON at position 8
    at JSON.parse (<anonymous>)
    at Daikin.<anonymous> (/root/.nvm/versions/node/v11.10.0/lib/node_modules/homebridge-daikin-local/index.js:437:21)
    at Request.self.callback (/root/.nvm/versions/node/v11.10.0/lib/node_modules/homebridge-daikin-local/node_modules/request/request.js:185:22)
    at Request.emit (events.js:197:13)
    at Request.<anonymous> (/root/.nvm/versions/node/v11.10.0/lib/node_modules/homebridge-daikin-local/node_modules/request/request.js:1161:10)
    at Request.emit (events.js:197:13)
    at IncomingMessage.<anonymous> (/root/.nvm/versions/node/v11.10.0/lib/node_modules/homebridge-daikin-local/node_modules/request/request.js:1083:12)
    at Object.onceWrapper (events.js:285:13)
    at IncomingMessage.emit (events.js:202:15)
    at endReadableNT (_stream_readable.js:1129:12)
[6/20/2019, 6:30:53 AM] Got SIGTERM, shutting down Homebridge...

Expected behavior
Expecting no crash.

Screenshots
n/a

Additional context
nothing to add.

new version hang homebridge

Hello,
it's me or the new version of the plugin completely hang homebridge?