Shame on Daikin… Poor vision.
As Google Home is integrated with Daikin Cloud, would it be possible to use it as a kind of proxy to send commands to the AC units?
A lot dirty but better that no control.
1 Like
I still cannot understand why API from reverse engineered mobile app is not a solution. At least Xiaomi vacuum cleaner integration works in similar way. You need to do some magic tricks getting API key from app, then it all starts working seamlessly.
I totally agree. Shame in Daikin. Before I bought my units I did extensive research on how to integrate them into my home automation. I was perplexed when I discovered my all new Daikin units didn’t support the old interface anymore. The Intesis solution has the advantage for me that no future changes from Daikin (who we now know can’t be trusted) will influence my integration. Although expensive in the long run it will be beneficial (if it works of course).
Like you, I selected Daikin counting on local API. I have now 2 stilish with old interface and 4 perfera with the Cloud API I cannot control from HA.
Question: The Inesis solution is for a single AC unit or it manages multiple units?
I’m in the Netherlands and called Daikin. They don’t want to help, rude and support is shit. Apparently I’m the one with the problem and not Daikin. This was my first but will be my last Daikin. They can’t seem to understand that AP mode is messing with existing networks in the already crowded 2.4Ghz band. I have 4 units. It’s also annoying when they pop up in the list. At least hide the SSID. If you do the setup you have to enter the SSID and key manually anyway or scan the QR anyway.
I found this on their website. It’s a different card but I would not bet on it that they will fix this. I am on 1.12.30. My apologies for the rant but all the tings add up and make this very frustrating.
https://www.daikin.com.sg/wifi-setup
" Can the AP mode be disabled?"
For the D-Mobile Card (BRP072C42), the AP mode cannot be disabled.
The Intesis module is connect via wire to 1 unit. In other words: You need a Intesis module per unit. If you have many units this can become very costly. Had I known this in advance I would not have taken Daikin although I do think the units are pretty good. Integration is important to me.
Can’t you remove the Wifi modules completely?
Do you work for Daikin? Just disable the WiFi entirely was one of their answers. It’s like opening your car with the key and not using the remote.
I just tested the daikin-controller-cloud that I posted earlier.
Seems to work fine, but still far from something to integrate in HA.
Last commit was 3 months ago, so might be a dead end.
So, the super-secret, high-tech, NDA, don’t-tell-anyone API might not be that super-secret, high-tech, NDA, don’t-tell-anyone
It even comes with examples
I believe that is the NA/US API document which is not the one we need unfortunately. The one we need is not publically available.
It’s still very similar to the Apollo77’s work. So combining both might solve this.
I found this guy using it in node-red.
How did you get the daikin-controller-cloud up? Can you make a small doc about it?
There’s a quite good howto in the PROXY.md file.
You basically run a MITM-proxy attack to “steal” the tokens that are transferred between your phone and the Daikin Cloud. Using that tokens, you can send any command and read any info you’d like from the Daikin Cloud.
Getting it to work like Apollo77 is one thing, but integrating this into an HA Integration is at an other level.
For instance, if you check the certificate, it has an expiry date/time which means you’d have to build logic to fetch a new token after expiry.
I myself am a quite experienced programmer, but I have never done anything in Python unfortunately.
@fredrike I’ve been looking into Apollo77’s code for the last few days. It’s amazing how much has been done already and how good it works.
The existing code can:
- Read values
- Set values/modes
- List all supported features/commands for each device
- Detect token expiry and refresh
Only thing that is missing, is a user friendly tool to fetch the initial tokens - but I could help with that.
1 Like
That’s great!
Should we extend pydaikin for this support too?
The idea is that we have one python library for most Daikin devices.
1 Like
Hi everybody, a couple of weeks ago I have started working on porting Apollo77’s code in python, and to make it become a HomeAssistant custom integration, which I am quite close to release. I currently have something configurable either via YAML or via config flow, entities are being created and the data is correctly read. I am just struggling with sending the commands, which is working but I have difficulties in having the status updated right after that. Will keep you posted when it’s ready.
Bye!
10 Likes
In parallel, I’ve been working on writing docs for MacOS and Windows token-fetching.
@rospogrigio how are you integrating the tokens/refresh_token? Via YAML? Maybe we can fork something dedicated for token-fetching from Apollo’s repository
1 Like
I use the same principle: the file has to be stored in a file called tokenset.json that has to be placed in the config dir (the same where the YAML files are). When the token is refreshed, the file is automatically updated. I think it’s more comfortable in this way for now but we can rethink it in the future and I’m open to suggestions.
1 Like
Ok, so would it be useful to fork some standalone app (from Apollo) to fetch the tokenset? I could help with that. Or do you have that integrated somehow?
Can we see your project on Github?