-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
HA ghcr.io/home-assistant/home-assistant:2025.1 causes the 530L light to not show up as an identity. Rolling back to ghcr.io/home-assistant/home-assistant:2024.12.5 fixes it #823
Comments
Having the same issue with L530's, rolling back to Dec24 HA to resolve. |
Having the same issue. Restored 2024.12 and everything is working. Hopefully this can be resolved soon. |
Having the same issue for both L630 and L530 after upgraded to 2025.01, rolling back to core 2024.12.5 resolved the issue. |
Defect 822 also related. Confirmed that issue also occurs for L510, and is resolved by rolling back to 2024.12. |
Note: The error below may have been raised because the component still supports deprecated features and may not be the origin of the defect - I haven't read the code through yet! Logger: homeassistant.components.light Entity None (<class 'custom_components.tapo.light.TapoLightEntity'>) 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/petretiandrea/home-assistant-tapo-p100/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation |
I confirm this is working for my L530 bulb |
Confirmed works for me too |
This brought back online the L530, L630 and L535 bulbs that had gone 'unavailable' in the integration. But the light groups they were in didn't work. |
Does this also fix it for TL135? Edit: I can confirm that this also fixes it for TL135. (That is the model shown in the Tapo app, but it is the L535) |
This issue is stale because it has been open for 30 days with no activity. |
Version of the integration
Configuration
Add your logs here.
Describe the bug
A clear and concise description of what the bug is.
Debug log
The text was updated successfully, but these errors were encountered: