Weird. Tried it on 2 different computers and it both worked fine.
i had to retry a couple of times before it wanted to work. At first i kept getting security errors in the browser, but after closing out my browser, clearing the cache and restarting the script it worked.
Iāve written token-docs for Windows, MacOS and iOS: daikin-controller-cloud/PROXY.md at 1b037133da59316db6de90bffd8c9326d3285724 Ā· Apollon77/daikin-controller-cloud Ā· GitHub
Iām now waiting for the merge of a PR that would make available a .js file solely dedicated to saving the token: Tokensaver by gigatexel Ā· Pull Request #14 Ā· Apollon77/daikin-controller-cloud Ā· GitHub
Iāve also built standalone binaries (win/mac/linux) but still trying to figure out how to auto-generate them in the Appollo repository.
Version above is merged now, so we now check on the auto binary building ā¦ stay tuned
You guys are absolute legends!!! Got it working as well.
Some tips for people running into issues:
- Start the command prompt only after installing node-js. Just like @stefdewilde writes. I started it before and it wouldnāt recognize the npm command.
- Edit the example.js with notepad or notepad++ and change the ip to the ip of your local machine. Not your WAN address but of the specific computer/device you are fetching the tokens on.
- When you import the ca.pem file, the easiest way is to just import it in Chrome. Go to settings in Chrome and search for ācertā then you will find the menu to import the file.
- Go to your proxy settings from Chrome settings as well. I did it the way Apollon describes (through start > search) and it somehow didnāt work and gave me issues in the command prompt having too many listeners. I tried closing all my other browsers and apps, maybe that also helped.
- When installing through HACS (I would recommend this), add the repo. And then donāt forget to install the integration. After adding the line daikin_residential: to my config.yaml the integration immediately worked.
Using localhost instead of the IP address for the proxy worked for me - obviously only if you are logging in from the same machine you run the script on.
Hello,
excuse my english i use the google translator.
I followed the indications of āstefdewildeā and āmalentoā but nothing works I can not get the token my CMD window gives me this as an answer: Daikin-Cloud: SSL-Proxy ERROR for: Error: 4444 : error: 14094416: SSL routines: ssl3_read_bytes: sslv3 alert certificate unknown: c: \ ws \ deps \ openssl \ openssl \ ssl \ record \ rec_layer_s3.c: 1544: SSL alert number 46
ERR_SSL_SSLV3_ALERT_CERTIFICATE_UNKNOWN: Error: 4444: error: 14094416: SSL routines: ssl3_read_bytes: sslv3 alert certificate unknown: c: \ ws \ deps \ openssl \ openssl \ ssl \ record \ rec_layer_s3.c: 1544: SSL alert alert number
Thank you for your help
Seems like you didnāt import the ca.pem file you get after accessing the proxy webpage yourip:8889. Are you sure you imported it?
Hello,
I think so
Quite difficult to troubleshoot without seeing what you are exactly doing.
At what step do the errors show? Are you using Chrome? Did you try a clean chrome ignito session?
Hello I just tried again and it worked by following the stefwilde procedure so I donāt know what happened thank you for your help
Happy it worked eventually. Going to add to my instructions to close your browser and clear your cache.
A big thank you for this Daikin BRP069C4x CA Integration. Excellent job to all contributors it was not easy to do it with the language barrier again bravo for your work
Apollo77, rospogrigio & stefdewilde
1 Like
I donāt need a big thank you.
@Apollon77 @gigatexel and @rospogrigio are the real MVPs here 
1 Like
@fredrike first feedback from users here seems very positive. 
Great how the community has managed to adapt itself so quickly.
Iām another happy user who has succesfully integrated the component.
A big thank you!
1 Like
Yes that is really great news. I would really like to integrate the cloud code to the main pydaikin library but have concerns about the token generation. Wouldnāt it be possible to authenticate without the MiM? Is there signing going on that we have not cracked?
Edit:
My question is more, doesnāt Daikin just use some variant of oauth so we could implement that instead of the proxy.
Another thing I wonder is, how often do we need to refresh this token? Is this known information at this moment?
@Malento token gets refreshed automatically. There is a refresh-token in the initial saved tokenset.json
1 Like
@fredrike there is an OAuth document (docs) but some suggested that this is only applicable to the Daikin North-America servers.
I suspect there is a solution for third party developers using OAuth, but this is part of the āsecret apiā.
@Apollon77 @rospogrigio have you looked into this OAuth document by accident?