Closed trancefam closed 2 years ago
light documentation light source (message by IssueLinks)
wiz documentation wiz source (message by IssueLinks)
Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (light
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
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!
(message by CodeOwnersMention)
I looked into this. This is not an issue with Wiz but with light profiles.
color_name
. This is converted to rgb_color
in preprocess_turn_on_alternatives
(source)hs_color
in the params. (source)rgb_color
. After the default profile is applied, both rgb_color
and hs_color
are set.
The problem
Hi, I have about 30 wiz bulbs. I recently switched from the custom component to the core version of Wiz. I am having a new issue where when I turn any of the bulbs from
off
toon
, the value I have set inlight_profiles.csv
overrides the desired value. For example, when I activate a scene that is supposed to turn on the bulbsred
, they turn onwhite
(the default inlight_profiles.csv
). If I activate the scene a second time (when the bulbs are already on), it works.I have noticed if I delete
light_profiles.csv
, it works as expected.What version of Home Assistant Core has the issue?
core-2022.3.8
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
wiz
Link to integration documentation on our website
https://www.home-assistant.io/integrations/wiz/
Diagnostics information
Example of a model of bulb I have and the firmware:
ESP01_SHRGB1C_31
1.24.0
Example YAML snippet
According to the light_profiles.csv docs: "If no data is sent, and a default profile exists, the default profile will be applied."
However, the below yml will first turn on the light white. Calling it a second time will set it to the correct color.
Anything in the logs that might be useful for us?
Additional information
All of my bulbs are blocked at the firewall. They cannot reach the internet. This means the firmware of the bulbs aren't up to date. To test if this was a firmware issue, I unblocked one bulb and it updated from
1.24.0
to1.26.0
, then restarted Home Assistant. I experienced the same result -- thelight_profiles.csv
overrode the desired value on the initial bulb turn on.I captured the wiz diagnostics for both pre update (1.24.0) and post update (1.26.0):
1.24.0 Diagnostics
1.26.0 Diagnostics