Releases: Pythm/ad-ClimateCommander
Minor bugfixes
Typos and Logic Fixes
## What's Changed
* Spell correction by @Pythm in https://github.com/Pythm/ad-ClimateCommander/pull/6
**Full Changelog**: https://github.com/Pythm/ad-ClimateCommander/compare/v1.2.3...v1.2.4What the change does
- Corrected a typo in the config key
notify_reciever→notify_receiver. - Minor logic improvements in the HVAC mode selection to reduce unnecessary state changes.
Full Changelog
Compare v1.2.3 → v1.2.4
v1.2.3 Support for fahrenheit and improvements to vacation mode
Release Notes: Climate Commander v1.2.3
Version: v1.2.3
🚀 What's New
🔧 Updated Logic for Cool Mode During Vacation
- Improved logic now ensures HVAC systems correctly enter "cool" mode even when vacation mode is active, based on indoor and outdoor temperature thresholds.
- This resolves previous issues where vacation mode might have inadvertently suppressed cooling functionality.
📡 Default MQTT Namespace Changed to 'mqtt'
- The default MQTT namespace has been updated to
'mqtt', aligning with AppDaemon's documentation defaults for consistency and compatibility. - If you're using a custom namespace, ensure it's explicitly defined in your configuration.
🌡️ Added Fahrenheit Support via Sensor Detection
- The app now automatically detects the temperature unit (Celsius or Fahrenheit) by reading the
unit_of_measurementattribute from either theoutside_temperatureorindoor_sensor_tempsensor. - This eliminates the need for users to manually specify the unit, making the app more user-friendly and adaptable to global sensor setups.
📌 Default Temperature Settings
The app now uses the following default temperature values based on the detected unit:
| Unit | max_vacation_temp |
vacation_temp |
screening_temp |
getting_cold |
target_indoor_temp |
|---|---|---|---|---|---|
| Celsius | 30 | 16 | 8 | 18 | 22.7 |
| Fahrenheit | 86 | 61 | 47 | 65 | 72.8 |
⚠️ These defaults can be customized in your configuration file.
📦 Full Changelog
View the complete list of changes in the GitHub Changelog.
📝 Notes
- Weather Sensor Integration: If using the ad-Weather app, ensure it's configured before ClimateCommander to avoid conflicts.
- Persistent Storage: Changes to fan mode during "silence" periods are now stored persistently for smoother app restarts.
📌 License
🙋 Contributing
Found a bug or want to suggest a feature? Open an issue or submit a PR.
Climate Commander by Pythm
GitHub
Need further assistance? Reach out on GitHub.
v1.2.2
Bug Fix: Climate Temperature Setting Issue
We have addressed an issue where an invalid value could be written to persistent storage, leading to incorrect temperature settings in your climate system.
Manual Intervention Required:
If an invalid value has already been recorded in the JSON file you could either:
- Delete the File: Remove the problematic JSON file to reset storage.
- Identify and Correct:
Search for temperatures that appear 10 times higher than expected, indicating a potential error.
Edit the File: Manually correct or delete the erroneous value within the JSON file.
Weather sensor changes
Release Notes
What's Changed
Notification System Enhancements
- Improved Notifications: The application now sends messages using the following format:
self.notify_app.send_notification( message=f"No Window near {self.ADapi.get_state(self.heater, attribute='friendly_name', namespace=self.namespace)} is open and it is getting hot inside! {in_temp}°", message_title="Window closed", message_recipient=self.recipients, also_if_not_home=False )
Breaking change:
- Recipient List Update: Notifications now send recipients as a list to optimize by making only one call to
send_notification. Note: This change may affect custom notification apps.
Weather Data Integration
- Removed Automatic Weather Sensor Detection: Users can no longer rely on automatic weather sensor detection.
- Integration with ad-Weather App: Utilize the ad-Weather app for weather data. It offers additional features like dual outside temperature sensors and cloud coverage information.
- Custom Weather App Support: Alternatively, create a custom app to send weather data. The app should trigger an event as follows:
self.ADapi.fire_event('WEATHER_CHANGE', temp=self.out_temp, rain=self.rain_amount, wind=self.wind_amount, lux=self.out_lux, cloud_cover=self.cloud_cover )
- Cloud Cover Feature: The weather app now includes cloud cover data to prevent screens from closing if cloud coverage exceeds 70%.
Temperature Sensor Improvements
- Backup Indoor Sensor Temperature: A backup temperature sensor (
backup_indoor_sensor_temp) is added for use when the main indoor sensor is unavailable or stale. - Sensor Staleness Handling: If the indoor temperature sensor remains stale for more than two hours, the application will automatically reload the configuration entry for the sensor.
General Improvements
- Various optimizations and enhancements have been made to improve overall performance and user experience.
More improvements to using persistent data
This release improves the usage of stored data when setting indoor temperature to better stay closer to target.
Use your own notify app
What's Changed:
- Updated logic when setting heater temp with better usage of data from persistent storage.
- Check if persistent storage is configured before trying to open file. Closes #2
- Improvements to notification setup. Now you can use your own notification app with 'notify_app: your_app'. See readme for details.
v1.1.2 Fixed the error on target_indoor_input change
Fixed the error where changing the target_indoor_input would not update until restart.
v1.1.1
What's Changed:
Improvements to logging and recalling temperature when the temperature is far from target.
As an option you can delete the old json file before a restart to have the app create a new json on initialization to get rid of some of those old values that might not be optimal.