Releases: dlarrick/hass-kumo
v0.2.3
Release 0.2.3. No changes since 0.2.3-beta2:
Two fixes:
New logic for set_temperature that conforms to new service definition.
Now it sets the mode (heat, etc.) if provided, and has better input
checking.
Better behavior when one or all units are unreachable.
If no units are reachable at startup after 10 tries, it gives up. This behavior
is designed to accommodate users who power down their units seasonally.
If a unit that was properly set up becomes unreachable, it will retry only
once (instead of for each attribute) on the next update. Such units will show
as "unavailable" in HA and will reappear if they become reachable again.
Update to pykumo 0.1.10 for #2 above.
v0.2.3-beta
Two fixes:
- New logic for set_temperature that conforms to new service definition.
Now it sets the mode (heat, etc.) if provided, and has better input
checking. - Better behavior when one or all units are unreachable.
If no units are reachable at startup after 10 tries, it gives up. This behavior
is designed to accommodate users who power down their units seasonally.
If a unit that was properly set up becomes unreachable, it will retry only
once (instead of for each attribute) on the next update. Such units will show
as "unavailable" in HA and will reappear if they become reachable again.
Update to pykumo 0.1.10 for #2 above.
v0.2.2
Fix setup error if user doesn't interact with the "prefer cache" checkbox
v0.2.1
Restore ability to configure via configuration.yaml
v0.2.0
Config Flow (GUI config) is out of beta
Bump pykumo version to pick up 'vertical' swing setting
v0.2.0-beta
Config Flow (GUI setup) courtesy of @omriasta
v0.1.6
Fix "Auto" aka heat/cool mode. Thanks @FrancisLab !
v0.1.5
Fix fetching state at startup so entities are ready for use sooner
Fix one more async violation in fetching kumo_cache.json
Bump pykumo to 0.1.7, fixes flakiness in reporting just-set states
v0.1.4
Compatibility changes for HA 0.110
Squash more async warnings
Increase default connect timeout to 1.2 seconds