Skip to content
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

Plugin no longer in Sync with physical panel #389

Open
SimonPPickard opened this issue Jan 15, 2025 · 1 comment
Open

Plugin no longer in Sync with physical panel #389

SimonPPickard opened this issue Jan 15, 2025 · 1 comment
Labels
bug Something isn't working due to a problem in the CODE

Comments

@SimonPPickard
Copy link

SimonPPickard commented Jan 15, 2025

Hi all,

I've been using this app for a while now with no issues (thank you so much Dev(s)!).

Recently I'm finding that everything works in sync between HomeKit and the physical Daikin panel if driven from from the Home App..

I turn Aircon on, the panel lights up green I turn Aircon off, the panel switches off.

However if I turn on Aircon from the physical panel HomeBirdge / Home App doesn't pick this up. It's making my automation of.. if Aircon is turned on.. turn off after x mins fail.

I've checked google, made sure background refresh is on for the Daikin App, etc. Used to all work fine, anything I'm missing?

Log:

[15/01/2025, 17:42:28] [Daikin Livingroom] The firmware version is 1_2_1
[15/01/2025, 20:58:23] [Daikin Livingroom] setTargetHeaterCoolerState: received new state 2
[15/01/2025, 20:58:23] [Daikin Livingroom] HomeKit requested the AC to operate in COOL mode.
[15/01/2025, 20:58:23] [Daikin Livingroom] setTargetHeaterCoolerState: query: ret=OK&pow=0&mode=3&operate=2&bk_auto=2&stemp=22&dt1=19&dt2=22&f_rate=1&dfr1=1&dfr2=1&f_airside=0&airside1=0&airside2=0&f_auto=0&auto1=0&auto2=0&f_dir=0&dfd1=0&dfd2=0&filter_sign_info=1&cent=0&en_cent=0&remo=2
[15/01/2025, 20:58:24] [Daikin Livingroom] setActive: Power is 0, Mode is 2. Going to change power to 1.

Regards,
Simon

@SimonPPickard SimonPPickard added the bug Something isn't working due to a problem in the CODE label Jan 15, 2025
@cbrandlehner
Copy link
Owner

Some Daikin ACs seem to operate slightly different. For me it is almost impossible to debug.

If you turn on DEBUG you should see the URLs used to communicate with the unit. You can try yourself too by using these URLs in a terminal with curl.

like this:
curl http://192.168.71.135/aircon/get_model_info
it will give an output like this:

ret=OK,model=0AB9,type=N,pv=2,cpv=2,cpv_minor=00,mid=NA,humd=0,s_humd=0,acled=0,land=0,elec=0,temp=1,temp_rng=0,m_dtct=1,ac_dst=--,disp_dry=0,dmnd=0,en_scdltmr=1,en_frate=1,en_fdir=1,s_fdir=3,en_rtemp_a=0,en_spmode=0,en_ipw_sep=0,en_mompow=0%

What the plugin does is:
a) read the current status from the AC to get the current state. I the data you provided the string "pow=0" says the device is turned OFF. The string "mode=3" is the mode, like HEAT or COOL.
b) next the plugin replaces parts of the response. To turn it on it will replace "pow=0" with "pow=1".
c) finally it sends the string back to the AC.

As said, you can perform all these commands using curl (or a browser) manually.

Due to caching, HomeKit and the Daikin App may be out of sync. We found that the Daikin adapter hangs up and gets unresponsive if you poll the status too often so we reduced the number of requests sent.

The manual remote can only send, it will no update with anything from either HomeKit or the Daikin App.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working due to a problem in the CODE
Projects
None yet
Development

No branches or pull requests

2 participants