From 35afb56cf921eb8375cb4a9b1799eb6608a4e829 Mon Sep 17 00:00:00 2001 From: Raman Gupta <7243222+raman325@users.noreply.github.com> Date: Thu, 1 Feb 2024 03:06:53 -0500 Subject: [PATCH] Add note to ClimateEntityFeature blog post about disable flag (#2068) Co-authored-by: G Johansson --- blog/2024-01-24-climate-climateentityfeatures-expanded.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/blog/2024-01-24-climate-climateentityfeatures-expanded.md b/blog/2024-01-24-climate-climateentityfeatures-expanded.md index 78ebe566..8e227314 100644 --- a/blog/2024-01-24-climate-climateentityfeatures-expanded.md +++ b/blog/2024-01-24-climate-climateentityfeatures-expanded.md @@ -12,3 +12,6 @@ Integrations implementing `turn_off` service call needs to set the `TURN_OFF` fe There will be a 10 month deprecation period (2025.1) where `ClimateEntity` will set these on behalf of the integrations implementing the respective methods and from 2025.1 it will make integrations unable to use the respective methods if entity features has not been set accordingly. Implementing the methods without setting the respective feature flag will create a warning log entry guiding the user to create an issue for the integration. + +Integrations should set the attribute `_enable_turn_on_off_backwards_compatibility` in your `ClimateEntity` subclass instance to `False` once it has been migrated into using or not using the new feature flags. +This will stop the automatic setting of the new feature flags during the deprecation period and can be removed once deprecation has ended.