Closed SkyDev125 closed 1 year ago
Which entity (id) is the problematic one?
wiz_rgbww_tunable_f36281
You should check the logs for errors after switching the light. Looking at the logs this is only just after startup, I don't see any issues there.
2023-03-19 08:27:28.312 DEBUG (MainThread) [custom_components.powercalc.sensors.power] light.wiz_rgbww_tunable_f36281: State changed to "off". Power:0.33
This indicates the light was initially off after startup and powercalc set the power sensor to 0.33 Watt.
You should see a similar line after turning the light on / changing brightness.
Logger: custom_components.powercalc.strategy.lut Source: custom_components/powercalc/strategy/lut.py:124 Integration: Powercalc (documentation, issues) First occurred: 4:34:01 PM (1 occurrences) Last logged: 4:34:01 PM
light.wiz_rgbww_tunable_f36281: Lookup table not found (model: SHRGBW, color_mode: brightness
Could you check supported_color_modes
attribute for your light in developer tools?
well, I changed the light's colour, and now it reports a wattage. Then changed it back to daylight and it seems to be working now? this is very weird
Definitely a problem with the wiz integration. supported_color_modes: color_temp color_mode: brightness
It indicates that the only supported color_mode color_temp
, but somehow it sets the light color_mode to brightness
.
Not much I can do in powercalc for this as the wiz integration messes things up.
Would be a good idea to report this at HA issues tracker when you are able to reproduce this again.
I'll keep an eye out, Thank you for helping me troubleshoot this.
Closing this issue. Hopefully for you the color mode stays at color_temp now and does not return to brightness each time.
System Health details
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.31.0 Stage | running Available Repositories | 1249 Downloaded Repositories | 4Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Debian GNU/Linux 11 (bullseye) -- | -- update_channel | stable supervisor_version | supervisor-2023.03.1 agent_version | 1.4.1 docker_version | 23.0.1 disk_total | 116.9 GB disk_used | 19.1 GB healthy | failed to load: Unhealthy supported | failed to load: Unsupported supervisor_api | ok version_api | ok installed_addons | Studio Code Server (5.5.4), Terminal & SSH (9.6.1), Mosquitto broker (6.1.3), Vaultwarden (Bitwarden) (0.19.0), Home Assistant Google Drive Backup (0.110.1)Dashboards
dashboards | 1 -- | -- resources | 0 mode | auto-genRecorder
oldest_recorder_run | March 9, 2023 at 6:09 PM -- | -- current_recorder_run | March 19, 2023 at 7:56 AM estimated_db_size | 105.89 MiB database_engine | sqlite database_version | 3.38.5Checklist
Describe the issue
I have 3 Wiz bulbs. All of them are being captured properly, except this one specific bulbs which has a slightly different model. WiZ Bulb A67 E27 SHRGBW
Everytime that I turn the bulb on, the power estimate just goes to unavailable. When I turn it back off, it then starts recording its "sleep power consumption".
So I think probably something is either wrong on my installation/bulb. or something is wrong with the power estimate calculations for the SHRGBW bulb
Reproduction steps
...
Debug logs
Diagnostics dump or YAML config
No response