Skip to content

0.2.12
Compare
Choose a tag to compare
@PeteRager PeteRager released this 08 Aug 14:02
· 189 commits to master since this release
0.2.12
187caf8
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Version 0.2.12 - Feature and Maintenance Release

Ventilation enhancements - #187

  • The switch to control ventilation was only created for systems with an External Fresh Air Damper. Now it is also created for systems with 1 or 2 stage HRVs/ERVs. https://github.com/PeteRager/lennoxs30#ventilation

  • For timed (non ASHRAE) ventilators, you can start a timed ventilation action using a new number entity. So running your ventilator for 30 minutes can be done without an automation. Setting to 0 will stop an existing timed ventilation. This is equivalent to setting a timed ventilation from the thermostat panel - and similarly actions taken from the panel are now reflected in Home Assistant. https://github.com/PeteRager/lennoxs30#timed_ventilation

  • The ventilation switch will now be on if a timed ventilation is active. The prior behavior is it would be off. Turning it off will stop whatever ventilation (timed or always on) is active. Attributes added to indicate what type of ventilation action is active.

  • A new Ventilation Device will be created in Home Assistant with the ventilation entities attached.

Thanks to @Paulbhyo for assistance on this feature!

Cloud Connections - Data Quality #142 #148

These improvements are for Cloud Connections, similar capability is already implemented for Local Connection.

One of the main issues was - if your thermostat became disconnected from the Lennox Cloud but the integration was still able to reach the Lennox Cloud, stale data (old temperatures, etc.) would be reported indefinitely with no indication that there was a problem (like your thermostat has become disconnected from your WIFI). Anyways, not a good situation. Specifically:

  • Every 5 minutes the integration will detect if the thermostat is "online" in the Lennox Cloud using the Lennox "Presence" API. If is it not, all the entities will become unavailable; and an error will be logged. When the thermostat goes back "online", the integration will automatically reconnect and entities become available.

  • During startup with multiple M30s, if one was offline, initialization would not complete and no helpful errors were logged. Errors will be logged at startup if a thermostat is offline.

  • A binary sensor has been added to reflect the online / offline status - this can be used to determine if your thermostat has a "wifi dropout". https://github.com/PeteRager/lennoxs30#cloud_connected-cloud-connections-only

What's Changed

Full Changelog: 0.2.11...0.2.12

Contributors

PeteRager and Paulbhyo
Assets 2
Loading