Skip to content
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

[Bug]: Deprecation Warnings, several constants (2026.1) #459

Closed
2 of 3 tasks
ejpenney opened this issue Jan 6, 2025 · 1 comment
Closed
2 of 3 tasks

[Bug]: Deprecation Warnings, several constants (2026.1) #459

ejpenney opened this issue Jan 6, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@ejpenney
Copy link

ejpenney commented Jan 6, 2025

LocalTuya Version

2024.12.1

Home Assistant Version

2025.1.0

Environment

  • Does the device work using the Home Assistant Tuya Cloud component?
  • Is this device connected to another local integration, including Home Assistant and any other tools?
  • The devices are within the same HA subnet, and they get discovered automatically when I add them

What happened?

Simply a deprecation warning, we've got a year to handle these, all the warnings I see are here:

2025-01-06 04:05:10.246 WARNING (ImportExecutor_0) [homeassistant.components.light] ATTR_COLOR_TEMP was used from localtuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use kelvin equivalent (ATTR_COLOR_TEMP_KELVIN) instead, please report it to the author of the 'localtuya' custom integration
2025-01-06 04:05:10.258 WARNING (ImportExecutor_0) [homeassistant.components.vacuum] STATE_CLEANING was used from localtuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use VacuumActivity.CLEANING instead, please report it to the author of the 'localtuya' custom integration
2025-01-06 04:05:10.261 WARNING (ImportExecutor_0) [homeassistant.components.vacuum] STATE_DOCKED was used from localtuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use VacuumActivity.DOCKED instead, please report it to the author of the 'localtuya' custom integration
2025-01-06 04:05:10.264 WARNING (ImportExecutor_0) [homeassistant.components.vacuum] STATE_ERROR was used from localtuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use VacuumActivity.ERROR instead, please report it to the author of the 'localtuya' custom integration
2025-01-06 04:05:10.267 WARNING (ImportExecutor_0) [homeassistant.components.vacuum] STATE_IDLE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use VacuumActivity.IDLE instead, please report it to the author of the 'localtuya' custom integration
2025-01-06 04:05:10.272 WARNING (ImportExecutor_0) [homeassistant.components.vacuum] STATE_PAUSED was used from localtuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use VacuumActivity.PAUSED instead, please report it to the author of the 'localtuya' custom integration
2025-01-06 04:05:10.276 WARNING (ImportExecutor_0) [homeassistant.components.vacuum] STATE_RETURNING was used from localtuya, this is a deprecated constant which will be removed in HA Core 2026.1. Use VacuumActivity.RETURNING instead, please report it to the author of the 'localtuya' custom integration
Detected that custom integration 'localtuya' is using mireds for warmest light color temperature, when it should be adjusted to use the kelvin attribute `_attr_min_color_temp_kelvin` or override the kelvin property `min_color_temp_kelvin`, possibly with default DEFAULT_MIN_KELVIN (see https://github.com/home-assistant/core/pull/79591). This will stop working in Home Assistant 2026.1, please create a bug report at https://github.com/xZetsubou/hass-localtuya/issues

Steps to reproduce.

  1. Install (this variant) of localTuya alongside Home Assistant 2025.1.0
  2. Check the logs

Relevant log output

No response

Diagnostics information.

No response

@ejpenney ejpenney added the bug Something isn't working label Jan 6, 2025
@xZetsubou
Copy link
Owner

duplicated #442

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants