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

"property "targetColor" requires a property key" when changing RGB or CCWW light. #45924

Closed DelusionalAI closed 3 years ago

DelusionalAI commented 3 years ago

The problem

When trying to change the color (RGB or CCWW) of a zwave bulb (Inovelli LZW42) nothing happens and the following shows up in the zwave logs:

2021-02-03 21:30:22.219 INFO ZWAVE: Controller status: Driver: Color Switch: property "targetColor" requires a property key, but none was given.

The integration is talking to the zwavejs/zwavejs2mqtt:1.0.4 docker image with MQTT disabled.

Attached network dump. On off and brightness work as expected.

What is version of Home Assistant Core has the issue?

2021.2.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

zwave-js

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zwave_js/

Example YAML snippet

# Put your YAML below this line

Anything in the logs that might be useful for us?

# Put your logs below this line

zwave_js_dump.jsonl.zip

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

Hey there @home-assistant/z-wave, mind taking a look at this issue as its been labeled with an integration (zwave_js) you are listed as a codeowner for? Thanks! (message by CodeOwnersMention)

marcelveldt commented 3 years ago

This issue will be fixed with a new release of the Z-Wave server addon. For users running on zwavejs2mqtt I'll ask them to release a new version too.

nickroberts commented 3 years ago

Awesome! I was wondering what was going on with this.

I'm already loving everything about the z-wave-js integration. So much faster!

Speaking of faster, I am going to piggy-back on this issue, and just mention that when turning the LZW42 lights on / off through Home Assistant, the changes are immediate. When modifying the values in zwavejs2mqtt, the light takes around 3 seconds to transition (just like OZW).

I'm just wondering what could be causing this, as from what I know, the Inovelli firmware for the LZW42 doesn't support changing the default transition speed, like they do in their switches.

Thanks!

Keep up the great work!

marcelveldt commented 3 years ago

That's strange, at this point we do not send any transition at all (it is literally commented out in the code)....

DelusionalAI commented 3 years ago

I can confirm that the zwavejs2mqtt docker image v1.0.5 has the updated server and now the lights are working as expected!

nickroberts commented 3 years ago

Looks good! Definitely weird about the on / off transition! It's weird, because the Inovelli bulbs immediately change state, whereas the Inovelli dimmer switches transition smoothly (although they have a config property for the transition duration).

Thanks, again!

jprates commented 3 years ago

I was here to report the same issue on an Aeotec LED Bulb 6, glad someone had already mentioned it. The latest available version I can see of the Z-Wave JS to MQTT add-on is v0.2.3 and it still is not working. @DelusionalAI you mentioned the docker image v1.0.5, any correlation to the standard supervisor add-on? Trying to get an ETA here...

Thank you all for your great work.