-
Notifications
You must be signed in to change notification settings - Fork 590
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AREA_SQUARE_METERS was used from tuya_local, this is a deprecated constant which will be removed in HA Core 2025.12 #2596
Comments
This is new in HA 2024.12, which isn't even released yet, so it is not appropriate to change at this time. |
That's totally right, it's not actionable ATM. |
None of the documentation related to this change has been updated yet, and it is not announced on the Developer blog, but it looks like in addition to replacing the AREA_SQUARE_METERS constant with an enum expanded to cover other units, there is also a new "area" class available for sensor and number entities in 2024.12. |
Logger: homeassistant.const AREA_SQUARE_METERS was used from tuya_local, this is a deprecated constant which will be removed in HA Core 2025.12. Use UnitOfArea.SQUARE_METERS instead, please report it to the author of the 'tuya_local' custom integration |
Description
Found this in my HA logs:
Steps to reproduce
No response
Expected behaviour
No response
Additional context
No response
Confirmation
I am sure this is a bug or improvement, that is well enough described that it can be implemented.
If this is for a specific device, the device config is mentioned above, or diagnostics are included.
Log messages or diagnostics relevant to the issue are included.
This is not requesting addition of a new device.
The text was updated successfully, but these errors were encountered: