Wiz depracation warning for `color`
The problem
Hi,
updated to 2024.3.0b0 and received warning for my Wiz integration.
Here to report. thanks!
Logger: homeassistant.components.light
Source: components/light/__init__.py:914
integration: Light (documentation, issues)
First occurred: 6:31:50 PM (1 occurrences)
Last logged: 6:31:50 PM
light.wiz_rgbw_tunable_a1fc86 (<class 'homeassistant.components.wiz.light.WizBulbEntity'>) does not report a color mode, this will stop working in Home Assistant Core 2025.3, please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+wiz%22
What version of Home Assistant Core has the issue?
2024.3.0b0
What was the last working version of Home Assistant Core?
2024.2.x
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Wiz
Link to integration documentation on our website
https://www.home-assistant.io/integrations/wiz/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
Hey there @sbidy, mind taking a look at this issue as it has been labeled with an integration (wiz) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of wiz can trigger bot actions by commenting:
@home-assistant closeCloses the issue.@home-assistant rename Awesome new titleRenames the issue.@home-assistant reopenReopen the issue.@home-assistant unassign wizRemoves the current integration label and assignees on the issue, add the integration domain after the command.@home-assistant add-label needs-more-informationAdd a label (needs-more-information, problem in dependency, problem in custom component) to the issue.@home-assistant remove-label needs-more-informationRemove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
(message by CodeOwnersMention)
wiz documentation wiz source (message by IssueLinks)
I am seeing this warning too on version 2024.3.0. I noticed this only happens when bulbs are in "effect" mode, e.g. Romance.
min_color_temp_kelvin: 2202 max_color_temp_kelvin: 6535 min_mireds: 153 max_mireds: 454 effect_list: Ocean, Romance, Sunset, Party, Fireplace, Cozy, Forest, Pastel Colors, Wake up, Bedtime, Warm White, Daylight, Cool white, Night light, Focus, Relax, True colors, TV time, Plantgrowth, Spring, Summer, Fall, Deepdive, Jungle, Mojito, Club, Christmas, Halloween, Candlelight, Golden white, Pulse, Steampunk, Rhythm supported_color_modes: color_temp, rgbw effect: Romance color_mode: unknown brightness: null color_temp_kelvin: null color_temp: null hs_color: null rgb_color: null xy_color: null rgbw_color: null friendly_name: Left supported_features: 4
Device info SHRGB1C by WiZ Firmware: 1.31.0 Hardware: ESP01 31
My HA version 2024.3.0 don't like effects or RGB-settings/changes either in the WIZ or Philips Hue integration. HA is not able to save effects- or RGB-settings/changes in HA scenes, etc...
Try to create a scene in HA with a RGB WIZ bulb (or similar) with an effect. Save the scene, close it and open it again - Effect is gone... Maybe it works for you.
Old scenes with WIZ-effects works fine, but causes deprecation warning.
This is related to the same problem as the above posts.
Im also having the same problem. If a light has an effect assigned, HA doesnt return any data for brightness, color_temp etc. Was working find before updating to 2024.3.x
This is pretty infuriating. If a set the scene in the scenes page, it shows the proper effect. But as soon as I save and then try to activate the scene, the wiz lights default back to full brightness and warm white. This has to be any easy fix, no?
Got the same problem. Home Assistant Container; Core v2024.3.3; Frontend v20240307.0 Edit: just tried latest version Core v2024.4.1; Frontend v20240404.1 but still experience the issue. I also deleted all wiz devices in HA and re-added them.
@BlackHawk1912 - I already gave up on setting wiz scenes in home assistant. It's easy to do in node-red.
@dcarpio01 It seems to me, that the bug is new or that there should be some workaround. It was all working for me just yesterday. I had two WiZ bulbs and everything was working fine. I added a third bulb and changes all bulb sockets. Also i recreated the my HA container multiple times (because i was trying to get ZHA/ z2m working) and when trying to update the scene with the new bulb, i noticed that it stopped working.
@BlackHawk1912 - I just moved all my wiz bulbs from Hubitat to HA, so it seems like new wiz scenes are the issue.
https://github.com/home-assistant/core/issues/85731 seems to be releated (also already commented on there)
Inspecting the scenes.yaml shows, that there are several unset properties in the scene with the WiZ lamp:
(...)
supported_color_modes:
- color_temp
- rgbw
effect:
color_mode:
brightness:
color_temp_kelvin:
color_temp:
hs_color:
rgb_color:
xy_color:
rgbw_color:
friendly_name: WiZ RGBW Tunable 1BE560
supported_features: 4
(...)
Unfortunatly, setting the effect attribute manually (and leaving the color empty) does not work. The scene does nothing.
@dCatfish Can you please share the yaml configuration of your old scene that still works? (from scenes.yaml)
@BlackHawk1912 Here is an old scene that still works, but logs a "does not report a color mode" warning. It's a Wiz RGBW E14 bulb "Cozy" effect scene.
- id: '1700632273344' name: Bathroom Wiz over door ON entities: light.wiz_rgbw_tunable_7e0b3c: min_color_temp_kelvin: 2202 max_color_temp_kelvin: 6535 min_mireds: 153 max_mireds: 454 effect_list: - Ocean - Romance - Sunset - Party - Fireplace - Cozy - Forest - Pastel Colors - Wake up - Bedtime - Warm White - Daylight - Cool white - Night light - Focus - Relax - True colors - TV time - Plantgrowth - Spring - Summer - Fall - Deepdive - Jungle - Mojito - Club - Christmas - Halloween - Candlelight - Golden white - Pulse - Steampunk - Rhythm supported_color_modes: - color_temp - rgbw supported_features: 4 friendly_name: Bathroom E14 5 Wiz_LPC09 color_mode: brightness brightness: 255 effect: Cozy state: 'on' icon: mdi:awning-outline metadata: {}
@dCatfish Wow, thank you very much. I ported it to my setup (setting different entities, effects an name) and low and behold IT WORKED!!
The difference between a new (not working) scene and an older, working scene is at follows:
Old:
entities:
light.wiz_rgbw_tunable_1be560:
(...)
supported_features: 4
friendly_name: WiZ RGBW Tunable 1BE560
color_mode: brightness
brightness: 255
effect: Cozy
(...)
New:
entities:
light.wiz_rgbw_tunable_1bf196:
(...)
effect: Forest
color_mode: color_temp
brightness: 255
color_temp_kelvin: 2202
color_temp: 454
hs_color:
- 29.79
- 84.553
rgb_color:
- 255
- 146
- 39
xy_color:
- 0.579
- 0.388
rgbw_color:
friendly_name: WiZ RGBW Tunable 1BF196
supported_features: 4
(...)
The fix above doesn't seem to be working anymore, at least not for me. WiZ lights with effects listed in YAML the 'old' way just turn white for me. Very frustrating as this seems to be a simple fix with no action for months.
Hey, I will take a look into this.
Hey, I will take a look into this.
Thanks! I am also having a similar error:
Logger: homeassistant.components.light Source: components/light/init.py:912 integration: Light (documentation, issues) First occurred: 3:56:22 PM (2 occurrences) Last logged: 3:56:22 PM
light.wiz_rgbw_tunable_391e4d (<class 'homeassistant.components.wiz.light.WizBulbEntity'>) does not report a color mode, this will stop working in Home Assistant Core 2025.3, please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+wiz%22 light.wiz_rgbw_tunable_3ba563 (<class 'homeassistant.components.wiz.light.WizBulbEntity'>) does not report a color mode, this will stop working in Home Assistant Core 2025.3, please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+wiz%22
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
hi, no stale please.
Still getting these warnings in the original post.
yes, even with the latest 2024.10.0 it is giving error messages
The problem is still occurring. Wiz scenes are saving but saving the lighting effect after the scene is not saved.
On Fri, Oct 4, 2024, 8:31 AM Simo Lääveri @.***> wrote:
yes, even with the latest 2024.10.0 it is giving error messages
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/111795#issuecomment-2393601820, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGZ2FVN33HMEPFLWPOUL4IDZZ2DD7AVCNFSM6AAAAABD7HWOX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJTGYYDCOBSGA . You are receiving this because you commented.Message ID: @.***>
I concur. I hand changed the scenes for now back to the old format and they work but cannot use the UI to do any work as that will reformat. Here is the question. Where does the problem exist. In the scene controller or in the Wiz component and how can we help fix this problem. I have had this problem for some time, and it has never worked great. These are foundation features that are important in the system.
I think the problem exists in the scene controller because when I activate the script to change the effect manually it behaves like the changing the scene and doesn't apply the actual effect. I found adding a 500 ms delay to an automation then activating the script achieves the desired effect of scene/effect selection.
On Sat, Oct 19, 2024, 10:37 AM Jeff Basso @.***> wrote:
I concur. I hand changed the scenes for now back to the old format and they work but cannot use the UI to do any work as that will reformat. Here is the question. Where does the problem exist. In the scene controller or in the Wiz component and how can we help fix this problem. I have had this problem for some time, and it has never worked great. These are foundation features that are important in the system.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/111795#issuecomment-2423925877, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGZ2FVNFHKPGIQ3IQJALDG3Z4JVEPAVCNFSM6AAAAABD7HWOX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRTHEZDKOBXG4 . You are receiving this because you commented.Message ID: @.***>
Getting the warning as well on new bulbs.
I'm getting this with my WiZ lights as well, but i'm not using any scenes in HA, just the built in effects. These particular lights are always in effect mode, and I get the error logged at startup of HA even when the lights are unavailable (physically turned off). Not sure if it helps but here's the state info for them
On
min_color_temp_kelvin: 2200
max_color_temp_kelvin: 6500
min_mireds: 153
max_mireds: 454
effect_list: Ocean, Romance, Sunset, Party, Fireplace, Cozy, Forest, Pastel Colors, Wake up, Bedtime, Warm White, Daylight, Cool white, Night light, Focus, Relax, True colors, TV time, Plantgrowth, Spring, Summer, Fall, Deepdive, Jungle, Mojito, Club, Christmas, Halloween, Candlelight, Golden white, Pulse, Steampunk, Rhythm
supported_color_modes: color_temp, rgbw
effect: Party
color_mode: unknown
brightness: null
color_temp_kelvin: null
color_temp: null
hs_color: null
rgb_color: null
xy_color: null
rgbw_color: null
friendly_name: Hallway North South Light
supported_features: 4
Unavailable / Startup
restored: true
min_color_temp_kelvin: 2200
max_color_temp_kelvin: 6500
min_mireds: 153
max_mireds: 454
effect_list: Ocean, Romance, Sunset, Party, Fireplace, Cozy, Forest, Pastel Colors, Wake up, Bedtime, Warm White, Daylight, Cool white, Night light, Focus, Relax, True colors, TV time, Plantgrowth, Spring, Summer, Fall, Deepdive, Jungle, Mojito, Club, Christmas, Halloween, Candlelight, Golden white, Pulse, Steampunk, Rhythm
supported_color_modes: color_temp, rgbw
supported_features: 4
I am also regularly getting the same warning as OP in the Logs as well. I'm still rather new to the back-end elements of Home Assistant and was wondering, is this a Wiz Integration issue or Core Lighting issue? When I initially checked the log, the log indicates that problem is not with Wiz but with "Light"?
Currently running: Core 2024.12.5; Supervisor 2024.12.3; Operating System 14.1; Frontend 20241127.8
Hey, I will take a look into this.
@sbidy
Any update on this? 2025.3 is only a few weeks away.
just updated to 2025.3.0b0, good news is Wiz still works, but the error log is still there when turning on a Wiz light.
I don't think the maintainer is actively supporting this project anymore and I think it needs to be marked as abandoned/stale. There's been no activity in the underlying repo, pywizlight in 9 months and it seems many issues here in HA have received no response.
I could not find the time to take a look into it. But in the next days/weeks I will reserve some time for that. I checked the HASS dev docs, and it is mentioned that "all new integrations" needs to support the color mode. Yes, there are some issues and log entries if this is missing, but the general functionality of the bulbs are still given.
@relic664 we are a community, and we deliver/develop stuff for each other. I'm happy to have more contributors to maintain this. I would assume that the Wiz Hass integration is one of the most complex one because of no vendor documentation/support, UDP connections directly from HASS (no MQTT, HTTP REST etc.) and a lot of different vendors/devices.
Yes I understand the nature of OSS projects and I'm not trying to criticize or otherwise diminish your contribution. I was just noting that it seems that there hasn't been much activity in several months, which happens as maintainers come and go.
I don't doubt the complexities of maintaining the integration, I was simply raising the possibility that it was unmaintained (again just judging solely based on git activity)