Inconsistent State with Fan Mode and Circulate Air

[daswass]

When I turn on circulate air on the thermostat, the fan mode changes from auto to low.
When I turn off circulate air on the thermostat, the fan mode changes from low to auto.

Issue:
When I change the fan mode from low to auto using the integration, the thermostat shows circulate air is off, but the fan continues to blow. Using the thermostat to select circulate air off again does stop the fan.

I have been looking at all the attributes to see is there is some combination that signals to the unit that circulate air is actually on or off, but the only thing that looks like its changing (of the state being pulled into Home Assistant) is fan_mode.

Side Note: Schedule would also be nice to use here, but it doesn't seem to do anything. Selecting it from Home Assistant does make it say Schedule on the thermostat, but I doesn't seem to have any actual affect.

[daswass]

Strange

Additional info regarding requests - I sniffed these from the Daikin iPhone app:

When turning on circulate air, I see two PUT requests 20 seconds apart

1. /deviceData/

2. /deviceData/

[apetrycki]

I can't seem to replicate this problem. I use the integration to set fan to low and it shows always on for circulate air in the app and on the thermostat. Then I use the integration to set it to auto and it says off. The P1P2 stuff shouldn't be relevant, just the fanCirculate.

This is the function:

    def set_fan_mode(self, fan_mode):
        """Set the fan mode.  Valid values are "on", "auto", or "schedule"."""
        if fan_mode in {FAN_ON, FAN_AUTO, FAN_SCHEDULE}:
            self.data.daikinskyport.set_fan_mode(
                self.thermostat_index,
                FAN_TO_DAIKIN_FAN[fan_mode]
            )
            
            self._fan_mode = fan_mode
            self.update_without_throttle = True

            _LOGGER.debug("Setting fan mode to: %s", fan_mode)
        elif fan_mode in {FAN_LOW, FAN_MEDIUM, FAN_HIGH}:
            # Start the fan if it's off.  
            if self._fan_mode == FAN_AUTO:
                self.data.daikinskyport.set_fan_mode(
                    self.thermostat_index,
                    FAN_TO_DAIKIN_FAN[FAN_ON]
                )
                
                self._fan_mode = fan_mode

                _LOGGER.debug("Setting fan mode to: %s", fan_mode)

            self.data.daikinskyport.set_fan_speed(
                self.thermostat_index,
                FAN_TO_DAIKIN_FAN[fan_mode]
            )
            
            self._fan_speed = FAN_TO_DAIKIN_FAN[fan_mode]
            self.update_without_throttle = True

            _LOGGER.debug("Setting fan speed to: %s", self._fan_speed)
        else:
            error = "Invalid fan_mode value:  Valid values are 'on', 'auto', or 'schedule'"
            _LOGGER.error(error)
            return

    def set_fan_mode(self, index, fan_mode):
        ''' Set fan mode. Values: auto (0), schedule (2), on (1) '''
        body = {"fanCirculate": fan_mode}
        log_msg_action = "set fan mode"
        self.thermostats[index]["fanCirculate"] = fan_mode
        return self.make_request(index, body, log_msg_action)

    def set_fan_speed(self, index, fan_speed):
        ''' Set fan speed. Values: low (0), medium (1), high (2) '''
        body = {"fanCirculateSpeed": fan_speed}
        log_msg_action = "set fan speed"
        self.thermostats[index]["fanCirculateSpeed"] = fan_speed
        return self.make_request(index, body, log_msg_action)

If you set it to Auto, On, or Schedule, then all it does is call fanCirculate. If you set it to a speed, it turns the fan on if it's not already on and then sets the fan speed. So for low it calls fanCirculate 1 and then fanCirculateSpeed 0.

Step by step, what are you doing exactly that causes this issue?

[daswass]

Hey @apetrycki thanks for looking into this. Im still playing with it on my end as well.

The core of the issue is a misalignment with the actual blowers and the state reported back.

The hvac_action remains idle regardless of me changing the fan_mode using the integration. The fan does not start blowing when I turn it on and does not turn off when I set to auto, BUT in the Daikin app it does show circulate air on or off aligning with what I set in Home Assistant (this is what makes be believe some of the other parameters and second PUT request are somehow relavent)

[apetrycki]

That's strange. Mine does turn on/off, though it takes about 30 seconds or so. hvac_action is correct on mine. What model system do you have? Do you get any errors in your logs? If you wait a couple minutes, does it eventually work?

[daswass]

Outdoor Unit: model # RXTQ48TAVJU
Indoor Unit: FXSQ24TAVJU

It doesnt work after any amount of time. Ive got 3 zones and am playing with all of them. Another variable might be the way the zones are setup. Ive got 2 outdoor units, but 3 zones. I turned on debug logging and nothing out of the ordinary. I am able to make it work as expected in Postman following the same pattern i see from the app:

curl --location --request PUT 'https://api.daikinskyport.com/deviceData/UUID' \
--header 'User-Agent: DOH/9 CFNetwork/3826.500.131 Darwin/24.5.0' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer TOKEN' \
--data '{
    "P1P2SuperSecretFieldSettingModeNumber": 0,
    "P1P2NonPublicFieldSettingModeNumber": 0,
    "P1P2FieldSettingModeNumber": 12,
    "P1P2FieldSettingUnitNum": 0,
    "P1P2FieldSettingUnitNumChangeRequest": true,
    "P1P2SuperSecretSentFieldSettingSW0": 0,
    "P1P2SuperSecretSentFieldSettingSW1": 0,
    "P1P2SuperSecretSentFieldSettingSW2": 0,
    "P1P2SuperSecretSentFieldSettingSW3": 0,
    "P1P2SuperSecretSentFieldSettingSW4": 0,
    "P1P2SuperSecretSentFieldSettingSW5": 0,
    "P1P2SuperSecretSentFieldSettingSW6": 0,
    "P1P2SuperSecretSentFieldSettingSW7": 0,
    "P1P2SuperSecretSentFieldSettingSW8": 0,
    "P1P2SuperSecretSentFieldSettingSW9": 0,
    "P1P2SuperSecretSentFieldSettingSWa": 0,
    "P1P2SuperSecretSentFieldSettingSWb": 0,
    "P1P2SuperSecretSentFieldSettingSWc": 0,
    "P1P2SuperSecretSentFieldSettingSWd": 0,
    "P1P2SuperSecretSentFieldSettingSWe": 0,
    "P1P2SuperSecretSentFieldSettingSWf": 0,
    "P1P2NonPublicSentFieldSettingSW0": 0,
    "P1P2NonPublicSentFieldSettingSW1": 0,
    "P1P2NonPublicSentFieldSettingSW2": 0,
    "P1P2NonPublicSentFieldSettingSW3": 0,
    "P1P2NonPublicSentFieldSettingSW4": 0,
    "P1P2NonPublicSentFieldSettingSW5": 0,
    "P1P2NonPublicSentFieldSettingSW6": 0,
    "P1P2NonPublicSentFieldSettingSW7": 0,
    "P1P2NonPublicSentFieldSettingSW8": 0,
    "P1P2NonPublicSentFieldSettingSW9": 0,
    "P1P2NonPublicSentFieldSettingSWa": 0,
    "P1P2NonPublicSentFieldSettingSWb": 0,
    "P1P2NonPublicSentFieldSettingSWc": 0,
    "P1P2NonPublicSentFieldSettingSWd": 0,
    "P1P2NonPublicSentFieldSettingSWe": 0,
    "P1P2NonPublicSentFieldSettingSWf": 0,
    "P1P2SentFieldSettingSW0": 15,
    "P1P2SentFieldSettingSW1": 15,
    "P1P2SentFieldSettingSW2": 15,
    "P1P2SentFieldSettingSW3": 1,
    "P1P2SentFieldSettingSW4": 15,
    "P1P2SentFieldSettingSW5": 15,
    "P1P2SentFieldSettingSW6": 1,
    "P1P2SentFieldSettingSW7": 15,
    "P1P2SentFieldSettingSW8": 15,
    "P1P2SentFieldSettingSW9": 15,
    "P1P2SentFieldSettingSWa": 15,
    "P1P2SentFieldSettingSWb": 15,
    "P1P2SentFieldSettingSWc": 15,
    "P1P2SentFieldSettingSWd": 15,
    "P1P2SentFieldSettingSWe": 15,
    "P1P2SentFieldSettingSWf": 15,
    "fanCirculate": 1
}'

curl --location --request PUT 'https://api.daikinskyport.com/deviceData/UUID' \
--header 'User-Agent: DOH/9 CFNetwork/3826.500.131 Darwin/24.5.0' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer TOKEN' \
--data '{
    "P1P2SuperSecretFieldSettingModeNumber": 0,
    "P1P2NonPublicFieldSettingModeNumber": 0,
    "P1P2FieldSettingModeNumber": 0,
    "P1P2FieldSettingUnitNum": 0,
    "P1P2FieldSettingUnitNumChangeRequest": false,
    "P1P2SuperSecretSentFieldSettingSW0": 0,
    "P1P2SuperSecretSentFieldSettingSW1": 0,
    "P1P2SuperSecretSentFieldSettingSW2": 0,
    "P1P2SuperSecretSentFieldSettingSW3": 0,
    "P1P2SuperSecretSentFieldSettingSW4": 0,
    "P1P2SuperSecretSentFieldSettingSW5": 0,
    "P1P2SuperSecretSentFieldSettingSW6": 0,
    "P1P2SuperSecretSentFieldSettingSW7": 0,
    "P1P2SuperSecretSentFieldSettingSW8": 0,
    "P1P2SuperSecretSentFieldSettingSW9": 0,
    "P1P2SuperSecretSentFieldSettingSWa": 0,
    "P1P2SuperSecretSentFieldSettingSWb": 0,
    "P1P2SuperSecretSentFieldSettingSWc": 0,
    "P1P2SuperSecretSentFieldSettingSWd": 0,
    "P1P2SuperSecretSentFieldSettingSWe": 0,
    "P1P2SuperSecretSentFieldSettingSWf": 0,
    "P1P2NonPublicSentFieldSettingSW0": 0,
    "P1P2NonPublicSentFieldSettingSW1": 0,
    "P1P2NonPublicSentFieldSettingSW2": 0,
    "P1P2NonPublicSentFieldSettingSW3": 0,
    "P1P2NonPublicSentFieldSettingSW4": 0,
    "P1P2NonPublicSentFieldSettingSW5": 0,
    "P1P2NonPublicSentFieldSettingSW6": 0,
    "P1P2NonPublicSentFieldSettingSW7": 0,
    "P1P2NonPublicSentFieldSettingSW8": 0,
    "P1P2NonPublicSentFieldSettingSW9": 0,
    "P1P2NonPublicSentFieldSettingSWa": 0,
    "P1P2NonPublicSentFieldSettingSWb": 0,
    "P1P2NonPublicSentFieldSettingSWc": 0,
    "P1P2NonPublicSentFieldSettingSWd": 0,
    "P1P2NonPublicSentFieldSettingSWe": 0,
    "P1P2NonPublicSentFieldSettingSWf": 0,
    "P1P2SentFieldSettingSW0": 15,
    "P1P2SentFieldSettingSW1": 15,
    "P1P2SentFieldSettingSW2": 15,
    "P1P2SentFieldSettingSW3": 15,
    "P1P2SentFieldSettingSW4": 15,
    "P1P2SentFieldSettingSW5": 15,
    "P1P2SentFieldSettingSW6": 15,
    "P1P2SentFieldSettingSW7": 15,
    "P1P2SentFieldSettingSW8": 15,
    "P1P2SentFieldSettingSW9": 15,
    "P1P2SentFieldSettingSWa": 15,
    "P1P2SentFieldSettingSWb": 15,
    "P1P2SentFieldSettingSWc": 15,
    "P1P2SentFieldSettingSWd": 15,
    "P1P2SentFieldSettingSWe": 15,
    "P1P2SentFieldSettingSWf": 15
}'

[apetrycki]

Have you tried sending only the ones that change? Do any of the variables change if you control a different unit?

[daswass]

The following works as well (note circulate air off requiring a different value for 2 fields):

Circulate air ON:

{
    "P1P2FieldSettingModeNumber": 12,
    "P1P2FieldSettingUnitNumChangeRequest": true,
    "P1P2SentFieldSettingSW3": 1,
    "P1P2SentFieldSettingSW6": 1,
    "fanCirculate": 1
}

followed by

{
    "P1P2FieldSettingModeNumber": 0,
    "P1P2FieldSettingUnitNumChangeRequest": false,
    "P1P2SentFieldSettingSW3": 15,
    "P1P2SentFieldSettingSW6": 15
}

Circulate air OFF:

{
    "P1P2FieldSettingModeNumber": 12,
    "P1P2FieldSettingUnitNumChangeRequest": true,
    "P1P2SentFieldSettingSW3": 2,
    "P1P2SentFieldSettingSW6": 2,
    "fanCirculate": 0
}

followed by (same as above)

{
    "P1P2FieldSettingModeNumber": 0,
    "P1P2FieldSettingUnitNumChangeRequest": false,
    "P1P2SentFieldSettingSW3": 15,
    "P1P2SentFieldSettingSW6": 15
}

It seems like there is some state being set, then the app waits 20 seconds just to give enough time for the first request to complete, and then sends the "completion/reset" request. I confirmed that the P1P values will not auto-reset after waiting some amount of time, and its unclear what the impact of leaving them in that state is.