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

Fan rate keeps reverting to AUTO after having set it to SILENCE #65

Closed
awarburt opened this issue Apr 13, 2020 · 4 comments
Closed

Fan rate keeps reverting to AUTO after having set it to SILENCE #65

awarburt opened this issue Apr 13, 2020 · 4 comments
Labels
bug Something isn't working due to a problem in the CODE no-issue-activity

Comments

@awarburt
Copy link

Describe the bug
With the fan speed set to AUTO, moving the slider to 5% successfully lowers the fan speed to SILENCE. Later, the fan speed reverts to AUTO without any user inputs. The user observes this reversion by both the change to the louder/faster fan sound/speed as well as the value of the fan slider in Homekit getting changed from the user-set 5% back to 15%.

To Reproduce
Information on your wifi gateway from the daikin app:

  1. Firmware 2.9.0
  2. Wifi adapter BRP072A43 connected to model FTXS

Information on your configuration:

  1. Homebridge version 0.4.53, on a Raspberry Pi 3B+, Raspian Buster OS (fully up-to-date)
  2. node version 10.20.1 (when I upgraded to homebridge-daikin-local 2020.16.3, I saw a warning stating that node >=12.16.1 was required; however, I was unable to upgrade to this version)

Information from the log:

  1. Homebridge log file showing the effect of opening the Home app at 22:08, then changing the fan speed from 15% to 5% at 22:09, then, when relaunching the Home app at 22:10 finding that the fan speed is again back at 15%, which was not desired.

Apr 13 22:08:47 rpi3bp homebridge[1103]: [4/13/2020, 10:08:47 PM] [Daikin406] getTemperatureDisplayUnits: Temperature unit is 0. 0=Celsius, 1=Fahrenheit. Apr 13 22:09:11 rpi3bp homebridge[1103]: [4/13/2020, 10:09:11 PM] [Daikin406] setTargetHeaterCoolerState: received new state 1 Apr 13 22:09:11 rpi3bp homebridge[1103]: [4/13/2020, 10:09:11 PM] [Daikin406] setTargetHeaterCoolerState: query: ret=OK&pow=1&mode=4&adv=&stemp=16.0&shum=0&dt1=25.0&dt2=M&dt3=25.0&dt4=16.0&dt5=16.0&dt7=25.0&dh1=AUTO&dh2=50&dh3=0&dh4=0&dh5=0&dh7=AUTO&dhh=50&b_mode=4&b_stemp=16.0&b_shum=0&alert=255&f_rate=A&f_dir=2&b_f_rate=A&b_f_dir=2&dfr1=5&dfr2=5&dfr3=5&dfr4=A&dfr5=A&dfr6=5&dfr7=5&dfrh=5&dfd1=0&dfd2=0&dfd3=0&dfd4=2&dfd5=2&dfd6=0&dfd7=0&dfdh=0 Apr 13 22:09:12 rpi3bp homebridge[1103]: [4/13/2020, 10:09:12 PM] [Daikin406] setActive: Power is 1, Mode is 4. Going to change power to 1. Apr 13 22:09:29 rpi3bp homebridge[1103]: [4/13/2020, 10:09:29 PM] [Daikin406] setFanSatus received value: true Apr 13 22:09:30 rpi3bp homebridge[1103]: [4/13/2020, 10:09:30 PM] [Daikin406] setFanSatus: new value: 1 Apr 13 22:09:30 rpi3bp homebridge[1103]: [4/13/2020, 10:09:30 PM] [Daikin406] setFanSatus: Power is: 1 Apr 13 22:09:30 rpi3bp homebridge[1103]: [4/13/2020, 10:09:30 PM] [Daikin406] setFanSatus: Mode is: 4 Apr 13 22:09:31 rpi3bp homebridge[1103]: [4/13/2020, 10:09:31 PM] [Daikin406] setFanSatus received value: true Apr 13 22:09:32 rpi3bp homebridge[1103]: [4/13/2020, 10:09:32 PM] [Daikin406] setFanSatus: new value: 1 Apr 13 22:09:32 rpi3bp homebridge[1103]: [4/13/2020, 10:09:32 PM] [Daikin406] setFanSatus: Power is: 1 Apr 13 22:09:32 rpi3bp homebridge[1103]: [4/13/2020, 10:09:32 PM] [Daikin406] setFanSatus: Mode is: 4 Apr 13 22:09:32 rpi3bp homebridge[1103]: [4/13/2020, 10:09:32 PM] [Daikin406] setFanSatus received value: true Apr 13 22:09:33 rpi3bp homebridge[1103]: [4/13/2020, 10:09:33 PM] [Daikin406] setFanSatus: new value: 1 Apr 13 22:09:33 rpi3bp homebridge[1103]: [4/13/2020, 10:09:33 PM] [Daikin406] setFanSatus: Power is: 1 Apr 13 22:09:33 rpi3bp homebridge[1103]: [4/13/2020, 10:09:33 PM] [Daikin406] setFanSatus: Mode is: 4 Apr 13 22:10:23 rpi3bp homebridge[1103]: [4/13/2020, 10:10:23 PM] [Daikin406] getTemperatureDisplayUnits: Temperature unit is 0. 0=Celsius, 1=Fahrenheit. Apr 13 22:10:54 rpi3bp homebridge[1103]: [4/13/2020, 10:10:54 PM] [Daikin406] setTargetHeaterCoolerState: received new state 1 Apr 13 22:10:54 rpi3bp homebridge[1103]: [4/13/2020, 10:10:54 PM] [Daikin406] setTargetHeaterCoolerState: query: ret=OK&pow=1&mode=4&adv=&stemp=16.0&shum=0&dt1=25.0&dt2=M&dt3=25.0&dt4=16.0&dt5=16.0&dt7=25.0&dh1=AUTO&dh2=50&dh3=0&dh4=0&dh5=0&dh7=AUTO&dhh=50&b_mode=4&b_stemp=16.0&b_shum=0&alert=255&f_rate=A&f_dir=2&b_f_rate=B&b_f_dir=2&dfr1=5&dfr2=5&dfr3=5&dfr4=B&dfr5=B&dfr6=5&dfr7=5&dfrh=5&dfd1=0&dfd2=0&dfd3=0&dfd4=2&dfd5=2&dfd6=0&dfd7=0&dfdh=0 Apr 13 22:10:55 rpi3bp homebridge[1103]: [4/13/2020, 10:10:55 PM] [Daikin406] setActive: Power is 1, Mode is 4. Going to change power to 1.

Expected behavior
The expected behaviour was to have the fan speed, after having been set to SILENCE (5%) by the user, remain at 5% until the user requests that it be changed.

This may be an issue with the handling of the "f_rate" parameter or the related memorized fan rate state parameters. I noted this from the info at the URL https://github.com/ael-code/daikin-control/blob/master/README.md. Also, there may be some issue with confusing A (AUTO) with B (SILENCE) [followed by 3,4,5,6,7 speeds] in the indexing sequence. I attach below a screenshot from the above URL.

Screenshots
Screen Shot 2020-04-13 at 6 23 55 PM

Additional context
Thanks for putting together a great plugin that I am finding immensely useful!

@awarburt awarburt added the bug Something isn't working due to a problem in the CODE label Apr 13, 2020
@github-actions
Copy link

Stale issue message

@awarburt
Copy link
Author

Not stale.

@awarburt
Copy link
Author

May I inquire why this issue has been given low priority?

@MichelRabozee
Copy link

I concur. At least it should be a defaultFANSpeed configuration so it is possible to always start at the rate the user wants (personally I always use SILENCE initially and increase afterwards if needed). Currently, as the Daikin units always report "A" (AUTO) as default rate, it always starts in AUTO unless you force it in setActive method.

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 no-issue-activity
Projects
None yet
Development

No branches or pull requests

2 participants