Closed jacoscaz closed 4 months ago
@jacoscaz can you check and validate homebridge-daikin-cloud@2.4.0-beta0
?
@JeroenVdb I can't test exhaustively right now but I did install 2.4.0-beta0
and the plugin now starts normally without crashing and appears to work normally. Thank you so much!
Ok, get back to me if it would not work.
@JeroenVdb did a few more tests switching back and forth between cooling mode and dry mode, everything works as intended.
@JeroenVdb could you publish the beta version to NPM for easier installation?
Describe The Bug: The plugin breaks with the following error when interrogating a Daikin Perfera unit in
dry
mode:To Reproduce:
dry
mode using the remoteExpected behavior: The plugin should start correctly without breaking, even though
dry
mode is not natively supported by HomeKit and therefore can't be supported by this plugin as the more "normal" modesauto
,heating
andcooling
.Logs:
Plugin Config:
Daikin Environment:
Homebridge Environment:
Additional Info:
The problem seems to be that the object at
climateControl/fanDirection/operationModes/dry
differs from its equivalent within one of the supported modes (auto
,heating
orcooling
) in that it is missing thefanSpeed.modes.fixed
path.This is for dry mode:
This is for auto mode:
This breaks the following lines: https://github.com/JeroenVdb/homebridge-daikin-cloud/blob/e3c321c267b12f964f0003bb498a465e84e9cc94/src/daikinAirConditioningAccessory.ts#L73-L75
because
accessory.context.device.getData('climateControl', 'fanControl', `/operationModes/${this.getCurrentOperationMode()}/fanSpeed/modes/fixed`)
returns
null
due to the non-existent path.A quick'n'dirty workaround for this which I've already verified locally is to change that entire block as follows:
If this is the way to go I can open a PR accordingly, though I suspect there might be better ways to sort this out.