Constant deprecation in HA 2024.1 #1484
Comments
make-all
added
maintenance
|
It seems only the 0 values are an issue, as there is not any value defined for them in the enums. |
make-all
added
awaiting confirmation
make-all
added a commit
that referenced
this issue
Jan 7, 2024
HA 2024.1 has deprecated the use of old constants, but even 0 (which does not have a constant, nor an enum value to assign) is caught up in this. Workaround this by casting 0 to the enum type. Issue #1484
make-all
removed
awaiting confirmation
timlaing
pushed a commit
to timlaing/tuya-local
that referenced
this issue
Aug 8, 2024
HA 2024.1 has deprecated the use of old constants, but even 0 (which does not have a constant, nor an enum value to assign) is caught up in this. Workaround this by casting 0 to the enum type. Issue make-all#1484
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Home Assistant 2024.1 has deprecated a number of constants which have been replaced by enum types. Starting in HA 2024.1, this will emit log messages for use of deprecated constants in 2024.1. These constants will be removed completely in 2025.1.
Reference:
To Reproduce
Issue is reproduced on any Home Assistant build > 2024.1
Expected behavior
Integration starts with no warnings in log.
Sample Log messages
Entity None (<class 'custom_components.tuya_local.light.TuyaLocalLight'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature: 0> and color modes, please create a bug report at https://github.com/make-all/tuya-local/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
The text was updated successfully, but these errors were encountered: