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

[bonhomme 4]

Hi 

 

For a while I have been using the excellent QuickApp

Please login or register to see this link.

 to control my Daikin split system ACs. 

However, a recent firmware update (which I thoughtlessly installed without first checking 😢) completely changes the API and breaks this QuickApp. 

 

The Home Assistant community have a github thread which explains the issue and makes some progress to reverse-engineer the new API. 

Please login or register to see this link.

That thread links to a teardown blog post of the new API: 

Please login or register to see this link.

 (but it's in Japanese)

 

Is anyone else in a similar position? Does anyone have plans to update this QA to the new API (or develop anything new against the new API)?

 

(Also, for anyone running the older firmware - don't update! Although you won't be able to use the native app to control those units until you do). 

[tinman 1,070]

12 hours ago, bonhomme said:

Does anyone have plans to update this QA to the new API (or develop anything new against the new API)?

...

(Also, for anyone running the older firmware - don't update! Although you won't be able to use the native app to control those units until you do). 

 

even if, that will be till next update. Did you tested if your Daikin is compatible with Intesis INWMPUNI001I000 or INWMPDAI001I000, INWMPDAI001R000 or Aidoo AZAI6ZWEDA0 or AZAI6ZWEDA1?

 

[bonhomme 4]

On 1/17/2024 at 11:16 PM, tinman said:

 

even if, that will be till next update. Did you tested if your Daikin is compatible with Intesis INWMPUNI001I000 or INWMPDAI001I000, INWMPDAI001R000 or Aidoo AZAI6ZWEDA0 or AZAI6ZWEDA1?

 

Good suggestions. The trouble is those Intesis units are in the vicinity of $400 (AUD) which is more than 20% of the cost of the original air conditioners. And I have two AC units so this would be a significant extra cost, just to get back to where I was before the update (integration had been working well for over a year). 

 

I've also heard that Sensibo has similar units that might be a bit cheaper and work with Fibaro, but that none of the IR-based solutions is that reliable and they often get out of sync (as some commands are dropped and there's no feedback from the AC back to the remote to read the state). Dunno how true that is, I've never personally used the IR blaster approach.

 

Hence I'm trying to work out if there's a way to solve the problem without spending significant extra cash first.

 

EDIT: I was referring above to INWMPUNI001I000, I do note that Intesis has also got other units that connect to a wired remote output that don't have the reliability problem e.g. INWMPDAI001I000 (these are brand-specific). That costs about an extra AUD100, and requires a component from Daikin (KRP067A41 - some kind of wired remote terminal) that a quick online search says is about USD200). 

 

Edited January 20, 2024 by bonhomme

[tinman 1,070]

On 1/20/2024 at 3:44 AM, bonhomme said:

I've also heard that ... and work with Fibaro, but that none of the IR-based solutions is that reliable and they often get out of sync (as some commands are dropped and there's no feedback from the AC back to the remote to read the state). Dunno how true that is, I've never personally used the IR blaster approach

 

 

right, there are others IR based, like MCO Home 

Please login or register to see this link.

 or Remotec ZXT-600 AC, they are not bad as well, but as you said IR. 

[bonhomme 4]

I've contacted Daikin tech support - let's see what they say. They are due to get back to me today. 

[JJSNED 1]

is there any news?

[JJSNED 1]

Does anyone have any ideas on how I enter the ONECTA Cloud API? This is listed as an example at Daikin:

 

  

Please login or register to see this link.

  response_type=code
  &client_id=[YOUR_CLIENT_ID]
  &redirect_uri=[YOUR_REDIRECT_URI]
  &scope=openid%20onecta:basic.integration

 

The following does not work:

 

function QuickApp:onInit()

self:debug("Daikin - onInit")

self.http = net.HTTPClient()

ClientID = self:getVariable("ClientID")

Clientsecret = self:getVariable("Clientsecret")

RedirectURI = self:getVariable("RedirectURI")

Scope = "openid onecta:basic.integration"

 

local function loop()

setTimeout(loop,600000)

end

loop()

end

 

function QuickApp:SessionIDbutton()

local DaikinURLlogin = "https://idp.onecta.daikineurope.com/v1/oidc/authorize?"

local DataDaikinURLlogin = '{"client_id": "' .. ClientID .. '"}'

self:debug("Get session_id")

self:debug(DataDaikinURLlogin)

 

self.http:request(DaikinURLlogin, {

options = {

method = 'GET',

headers = {

['Content-Type'] = Scope,

},

data = DataDaikinURLlogin,

timeout = 10000

},

 

success = function(response)

if (response.status == 200 or response.status == 201) and type(response.data) == "string" and response.data ~= "" then

SessionID = json.decode(response.data)

SessionID = SessionID.session_id

self:debug("Session_id = " .. SessionID)

self:setVariable("SessionID", SessionID)

end

end

})

end

 

etc. etc.

[bonhomme 4]

Initially I got a call from an L2 (or above) support person, who promised to look into a resolution and said to give him a week.

 

However, multiple weeks went by with no contact, and then I got a pretty nastily-worded email from the General Counsel for Daikin Australia basically telling me to get stuffed. 

 

ONECTA isn't available in my region, but I have had some success with using Google Home integration with Daikin (which is officially supported by their app), then using Home Assistant's

Please login or register to see this link.

 integration (not to be confused with the Google Assistant integration which goes the other way) to create scripts that control the ACs via Google. The last step (pulling in HA devices into Fibaro), I haven't done yet, but should be straightforward. 

 

Ridiculous restrictions call for ridiculous hacks