-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot add integration, won't start #75
Comments
Well, I think I figured out the issue, I have a multi-headunit system and the data structures provided by the API are much different. I made some changes to the calls here to ensure it wouldn't crash when keys were missing and presto, I'm able to get some details on what I get from daikin's backend:
Needless to say, it's a whole lot more than the Open API spec :) but it also means it's going to be a pain to get this running properly. For example, issuing any commands to this system does not work. I also signed up and set up a quick hack to use Daikin's official API (https://www.daikinone.com/openapi/documentation/index.html) via curl and when I get the list of devices, it's an empty array. If I use the knowledge from this integration and provide the ID, I get "NotAuthorizedError" back which is a bit odd. Nothing in their documentation indicates that my system should be excluded from their API, but who knows. For the record, it's a CTXV07AVJU9 (I also have the FTXV09AVJU9 and FTXV12AVJU9, but they're all the same, just different BTUs). |
Version
0.9.6
Home Assistant Version
Core 2025.1.3, Supervisor 2024.12.3, Operating System 14.1, Frontend 20250109.0
What is the issue?
Created a Daikin One account and added three wall mounted minisplits. I'm able to control them from the app.
Proceeded to add the integration from HACS (by adding custom repo) and restarted HA.
Then I set up the integration and provided the same credentials as in the mobile application, however this fails to work. The integration will not start and I get an saying that a key is missing (ctSystemCapHeat).
Diagnostics
No such option is available since it cannot initialize
Relevant log output
The text was updated successfully, but these errors were encountered: