-
-
Notifications
You must be signed in to change notification settings - Fork 96
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
3.1.1 AttributeError: 'NoneType' object has no attribute 'hue' Tapo L530 Series bulbs #746
Comments
Got this too. This currently breaks a lot of things for me. |
Avoid a crash on the hs light check if none is set. Fixes petretiandrea#746
Avoid a crash on the hs light check if none is set. Fixes petretiandrea#746
This issue is stale because it has been open for 30 days with no activity. |
(original comment: #757 (comment), reposting so the issue doesn't go stale) I tried reverting to earlier versions to trace where this issue started: v3.0.0 doesn't have it, but v3.1.0 and above do. #748 fixes this specific issue, since the recently introduced new interface does allow the
Why the L530E (v1.0) doesn't have The python-kasa project has recently merged a fix for this exact model, maybe it'll help with the new interface (but it's not in a release yet): python-kasa/python-kasa#840 |
Version of the integration
3.1.1
Configuration
Tapo L530 (Colour Bulb)
Hardware Version 1.0
Firmware 1.3.0
Home Assistant Green Running:
Core 2024.4.3
Supervisor 2024.04.0
Operating System 12.2
Frontend 20240404.2
Describe the bug
After updating to 3.1.1 some of my Tapo L530 bulbs fail to initialise and others that can be controlled form the dashboard are producing a "Failed to call service light/turn_on. 'NoneType' object has no attribute 'hue'" error which causes automations using these lights to fail.
Debug log
The text was updated successfully, but these errors were encountered: