Daikin WIFI controller BRP084Cxx firmware update from 1.19.0 to 2.8.0 breaks local API

[epajfl00]

The problem

Recently, there was an update to the Daikin mobile app, when this was updated, it showed that a firmware update was available for the wifi controller which was running at 1.19.0, and all good.
The update was ver 2.8.0 so that was done. The mobile app is fine and controls as expected, all good.

However, HA latest on version 2023.8.3, failed to connect, so all entities are now unavailable.
Tried to communicate directly with the API commands on the host address, “page not found”, was the result for any commands. So I can no longer communicate with it directly, as before.

A firmware roll-back of the update is not possible.

BTW, for information I’ve found that my controller must be a “BRP084C44”.
See below link.
Daikin (daikinthai.com) 2

Any thoughts?

What version of Home Assistant Core has the issue?

2023.8.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Daikin AC

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @fredrike, mind taking a look at this issue as it has been labeled with an integration (daikin) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of daikin can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign daikin Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

daikin documentation
daikin source
_{^{(message by IssueLinks)}}

[starryalley]

I have 2 split systems (FTXM20WVMA and 35 one) installed today which both use BRP084C44. Both come with v1.1.30 firmware and I updated 1 of them to the latest 2.8.0 without knowing anything yet. And then I tried to configure both in Daikin Mobile Controller (I'm in Australia) and only the one with 2.8.0 can be controlled successfully. Weird thing is only in iOS can I see the "update firmware" choice. In Android I just see "adapter does not respond" error. Nothing I can do there in Android.

And now that I tried to configure them in HA, both can't be connected. When I tried to configure using Daikin AC integration and manually entered the IP, it just said Unexpected Error:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/daikin/config_flow.py", line 74, in _create_device
    device = await Appliance.factory(
             ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/pydaikin/daikin_base.py", line 86, in factory
    await appl.init()
  File "/usr/local/lib/python3.11/site-packages/pydaikin/daikin_airbase.py", line 68, in init
    raise Exception("Empty values.")
Exception: Empty values.

Not sure if this is related, but just sharing what I had.

[fredrike]

There is a big warning on the integration page: https://www.home-assistant.io/integrations/daikin/

This is probably the same issue with your BRP084C44.

Only solution as I see it is to use https://github.com/revk/ESP32-Faikin.

[hank418]

same issue with @epajfl00

[Zepherman]

Same here, have lost connection in HA, was working perfectly prior to updating the daikin wifi module from 1.19.0 to 2.8.0
Daikin mobile controller app is working.
Now getting Unexpected Error when trying to add to HA.

[DKSUSHI]

Same issue. Is it possible to downgrade the firmware version 1.9.0 of the AC ?"

[fredrike]

This is not a forum nor a support channel. Please open a discussion in the forum section of Home Assistant and file a complaint against Daikin that they have broken local integration.

[fredrike]

@home-assistant rename Daikin WIFI controller BRP084Cxx firmware update from 1.19.0 to 2.8.0 breaks local API

[fredrike]

@home-assistant close

[chrisp250]

The local API must still work, as the app can still access the aircon locally without going to the cloud. Maybe it was changed to require encryption or some other breaking change.

[starryalley]

Yes the local API still works over http. I captured some using mitproxy from a iOS Daikin Mobile Controller just to take a quick look:

Unfortunately I can't figure out anything at all about the payload. For example this PUT payload is sent to adjust temperature from 19 to 18 in heat mode:

{
    "requests": [
        {
            "op": 3,
            "pc": {
                "pch": [
                    {
                        "pch": [
                            {
                                "pch": [
                                    {
                                        "pn": "p_01",
                                        "pv": "0100"
                                    },
                                    {
                                        "pn": "p_08",
                                        "pv": "000000"
                                    },
                                    {
                                        "pn": "p_03",
                                        "pv": "24"
                                    },
                                    {
                                        "pn": "p_07",
                                        "pv": "0F0000"
                                    },
                                    {
                                        "pn": "p_0A",
                                        "pv": "0A00"
                                    }
                                ],
                                "pn": "e_3001"
                            },
                            {
                                "pch": [
                                    {
                                        "pn": "p_01",
                                        "pv": "01"
                                    }
                                ],
                                "pn": "e_A002"
                            },
                            {
                                "pch": [
                                    {
                                        "pn": "p_2D",
                                        "pv": "02"
                                    }
                                ],
                                "pn": "e_3003"
                            }
                        ],
                        "pn": "e_1002"
                    }
                ],
                "pn": "dgc_status"
            },
            "to": "/dsiot/edge/adr_0100.dgc_status"
        }
    ]
}

And adjusting air flow direction also goes to the same endpoint for example. This is from vertical to off.

{
    "requests": [
        {
            "op": 3,
            "pc": {
                "pch": [
                    {
                        "pch": [
                            {
                                "pch": [
                                    {
                                        "pn": "p_2D",
                                        "pv": "02"
                                    }
                                ],
                                "pn": "e_3003"
                            },
                            {
                                "pch": [
                                    {
                                        "pn": "p_03",
                                        "pv": "24"
                                    },
                                    {
                                        "pn": "p_01",
                                        "pv": "0100"
                                    },
                                    {
                                        "pn": "p_07",
                                        "pv": "000000"
                                    },
                                    {
                                        "pn": "p_0A",
                                        "pv": "0A00"
                                    },
                                    {
                                        "pn": "p_08",
                                        "pv": "000000"
                                    }
                                ],
                                "pn": "e_3001"
                            },
                            {
                                "pch": [
                                    {
                                        "pn": "p_01",
                                        "pv": "01"
                                    }
                                ],
                                "pn": "e_A002"
                            }
                        ],
                        "pn": "e_1002"
                    }
                ],
                "pn": "dgc_status"
            },
            "to": "/dsiot/edge/adr_0100.dgc_status"
        }
    ]
}

[chrisp250]

Thanks for that @starryalley. I had a look but the two captures are not enough to reverse engineer the protocol. However it seems that register p_07 is where the key is. I've extracted the elements from e_3001 of the two captures, and put them in order. Only one register changed between the two commands, see below.

#Temperature from 19 to 18 in Heat mode
pn	:	p_01 #Same value as below
pv	:	0100

pn	:	p_03 #Same value as below
pv	:	24

pn	:	p_07 #This is different, I would guess this where the temperature is encoded
pv	:	0F0000

pn	:	p_08 #Same value as below
pv	:	000000

pn	:	p_0A #Same value as below
pv	:	0A00



#Direction from vertical to off
pn	:	p_01
pv	:	0100

pn	:	p_03
pv	:	24

pn	:	p_07
pv	:	000000

pn	:	p_08
pv	:	000000

pn	:	p_0A
pv	:	0A00