Daikin Binding support for BRP072C42 controller

Hi All,

Is the support for the BRP072C42 (which is a replacement for BRP072A42) controller on the horizon? What I can see Daikin moved the protocol from HTTP to HTTPS with additional authentication/authorization.

Someone with that controller would need to submit a PR. Alternatively, would you be a tester? Is the difference mainly http vs https?

Hi Jim, I can definitely assist with testing. What I understand the difference is only in switching to HTTPS and token authentication. I got the following reply from the controller (10.100.100.97) using CURL and registering the token:

$ curl --insecure -H "X-Daikin-uuid: 7b9c9a47c9c64eesrfgt848e67cc7edd" -v "https://10.100.100.97/aircon/get_control_info"

Trying 10.100.100.97…
Connected to 10.100.100.97 (10.100.100.97) port 443 (#0)
found 148 certificates in /etc/ssl/certs/ca-certificates.crt
found 592 certificates in /etc/ssl/certs
ALPN, offering http/1.1
SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256
server certificate verification SKIPPED
server certificate status verification SKIPPED
common name: 015F4441494B494E000000430020A0DD.svr (does not match ‘10.100.100.97’)
server certificate expiration date OK
server certificate activation date OK
certificate public key: RSA
certificate version: #3
subject: C=JP,ST=Osaka,O=DAIKIN INDUSTRIES, LTD,CN=015F4441494B494E000000430020A0DD.svr
start date: Sat, 06 Apr 2019 01:56:10 GMT
expire date: Mon, 13 Mar 2119 01:56:10 GMT
issuer: C=JP,ST=Osaka,O=DAIKIN INDUSTRIES, LTD,CN=CA.daikindev.com
compression: NULL
ALPN, server did not agree to a protocol

GET /aircon/get_control_info HTTP/1.1
Host: 10.100.100.97
User-Agent: curl/7.47.0
Accept: /
X-Daikin-uuid: 7b9c9a47c9c64ee19063848e67cc7edd

HTTP 1.0, assume close after body

HTTP/1.0 200 OK
Content-Length: 178
Content-Type: text/plain

Closing connection 0

ret=OK,pow=1,mode=0,adv=,stemp=23.0,shum=0,dt1=23.0,dt2=M,dt3=23.0,dt4=25.0,dt5=25.0,dt7=23.0,dh1=0,dh2=50,dh3=0,dh4=0,dh5=0,dh7=0,dhh=50,b_mode=0,b_stemp=23.0,b_shum=0,alert=255

To register the token I’ve used the following:

$ curl --insecure -H "X-Daikin-uuid: 7b9c9a47c9c64ee19063848e67cc7edd" -v "https://10.100.100.97/common/register_terminal?key=0307222342343"

where “key” = key printed on the device label

With the hope that more people can help, let’s continue here: Daikin wi-fi adapter BRP072C42 not visible or configurable in OH

Please repost your info there, thanks.