You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With this change, set_supports_xxxxx_swing is only called when the CONF_CAPABILITIES_xxxxx is True. If the capability is false, set_supports_xxxx_swing is never called.
Following the code, supports_xxxxx_swing_ can now only be true since the initialization value in samsung_ac_device.h is also true (see line 481 in samsung_ac_device.h).
A solution would be to set the initialization values for supports_horizontal_swing_ and supports_vertical_swing_ to false.
The text was updated successfully, but these errors were encountered:
We have prepared a PR to resolve issue #187 regarding the handling of horizontal and vertical swing control. The fix ensures that both true and false values are properly passed from the YAML configuration.
Since the PR #169 horizontal_swing can not be disabled by yaml. The device capabilities do not have any effect any more:
result:
The problem arises from the change in init.py line 286:
With this change,
set_supports_xxxxx_swing
is only called when the CONF_CAPABILITIES_xxxxx isTrue
. If the capability is false,set_supports_xxxx_swing
is never called.Following the code,
supports_xxxxx_swing_
can now only betrue
since the initialization value insamsung_ac_device.h
is alsotrue
(see line 481 in samsung_ac_device.h).A solution would be to set the initialization values for
supports_horizontal_swing_
andsupports_vertical_swing_
tofalse
.The text was updated successfully, but these errors were encountered: