search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.81k stars 30.51k forks source link

Unable to control white colors on ZW098 (vera) #37118

Closed ackstorm23 closed 3 years ago

ackstorm23 commented 4 years ago

The problem

I am unable to control the white channels on my Aeontec ZW098.

It appears as if it is not even detecting the white channels, as the widget only shows brightness and RGB color wheel.

Manually trying to affect white_color or color _temp has no effect.

Changing the colors to 255, 255, 255 does not provide white light but instead causes low brightness blue color.

Currently any attempt to control the device through HA turns off the two white color channels and only allows for direct RGB colors. The result is a bulb which is very dark and cannot be used to light a room normally.

Environment

arch | x86_64 dev | false docker | true docker_version | 19.03.11-ce hassio | true host_os | Manjaro Linux installation_type | Home Assistant Supervised os_name | Linux os_version | 5.4.44-rt27-MANJARO python_version | 3.7.7 supervisor | 227 timezone | America/Chicago version | 0.111.4 virtualenv | false

These are the only attributes listed for the entity in HA. 

brightness: 255
hs_color: 300, 99.216
rgb_color: 255, 1, 255
xy_color: 0.385, 0.155
Vera Device Id: 4
friendly_name: Colored Light Bulb
supported_features: 17

Traceback/Error logs

No error logs that I have seen indicating any problem with controlling or detecting the device.

Additional information

I suspect HA is incorrectly detecting the device, resulting in HA not believing it has white channels to control.

It appears to have mutually exclusive settings where it can either fulfill RGB colors, a Warm White color, or a Cool White color.
Because HA does not know how to control the two white channels, any attempt to control the device in HA only results in RGB results.

I am able to control both white channels without issue inside of my Vera Plus.

Supported Colors for the device in Vera show as: W,D,R,G,B

With Current Color showing: 0=0,1=247,2=255,3=2,4=255

I have also tried installing the "RGB controller device" plugin in Vera, which works equally well on the Vera, but only detects as a on/off switch in HA.

I will provide any information requested.

frenck commented 4 years ago

Please supply the integration used. We have multiple integrations that matches your description. Thanks 👍

ackstorm23 commented 4 years ago

Edited to include url to integration.

probot-home-assistant[bot] commented 4 years ago

Hey there @vangorra, mind taking a look at this issue as its been labeled with an integration (vera) you are listed as a codeowner for? Thanks! (message by CodeOwnersMention)

vangorra commented 4 years ago

If it's being detected as a switch, this means you need to provide the device ID in the light_ids config list. This is ensure it is treated as a light.

ackstorm23 commented 4 years ago
  1. The light itself identifies as a light, and I can control the colors.
  1. The secondary entity which comes from the 'RGB Controller' app within the Vera Plus, only detects as a switch.

So should light.colored_light_bulb_4 entity be detecting it as a RGBW device, or is this meant to work using the rgb_controller_devic entity which would then need light_ids?

ackstorm23 commented 4 years ago

If it's being detected as a switch, this means you need to provide the device ID in the light_ids config list. This is ensure it is treated as a light.

I can't see to find documentation on how to force set light_ids. Can you guide me on that?

vangorra commented 4 years ago

I'm confused about the issue you're reporting. Does vera recognize the light and provide the light warm controls? Does home assistant identify the device as a light or a switch?

Forcing a vera light can be done on the integration page. The vera integration has an options button that allows you to specify with vera device IDs will be treated this way.

I had an issue where vera could not get the features of an Inovelli RGB light. I had to add it through home assistant's build in zwave support to get it working correctly.

ackstorm23 commented 4 years ago

The native light device in Vera Plus:

  1. Home Assistant recognizes is as a light, but it only recognizes the RGB channels. The light widget allows me to pick colors and brightness, but only that.

  2. The light also has two separate White channels (Warm, and Cool). HA does NOT recognize those and they cannot be controlled via HA.

As a result of the above, the light cannot be used to provide white light. It can only display colors, and attempting to emulate white light by providing 255,255,255 results in a very dim white light no brighter than a night light.

The RGB controller device in Vera Plus, which compliments the above device and is provided as an 'app' within Vera.

  1. Home Assistant recognizes it as a switch, and it can only power the light on and off.

I will add the device ID for this entity into the integration and see if i get any different results from that.

EDIT: This caused the "RGB Controller Device" to show as a light, but only as basic dimmer. No color control.

ackstorm23 commented 4 years ago

Pictures in Vera UI and HA

vangorra commented 4 years ago

Looks like neither the Home Assistant of downstream pyvera code support this.Could you open a issue for pyvera and include the output of your device? That will help a lot in adding the missing code. Here's the vera controller URL to get the device data. http://<ip address>:3480/data_request?id=status&output_format=json&DeviceNum=<device number>

ackstorm23 commented 4 years ago

https://github.com/pavoni/pyvera/issues/135

stale[bot] commented 4 years ago

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 now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ackstorm23 commented 4 years ago

.

github-actions[bot] commented 3 years ago

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.