Zwave beginner: RGB light can only be toggled via Home Assistant

prankousky · October 7, 2019, 8:14am

Hi everybody,

just yesterday I added zwave components to my Home Assistant via zwave2mqtt. I have two OOMI RGB light bulbs (amazon link). They show up like this in the zwave2mqtt webUI:

3 Multilevel Power Switch Unknown: type=0003, id=0062 (Fantem (Oomi)) Sleep
4 Multilevel Power Switch Unknown: type=0003, id=0062 (Fantem (Oomi)) Alive

In Home Assistant under settings => integrations => mqtt (I have autodiscovery enabled) they show up like this

The light shows up as if the color had been set to red, but it is actually yellow; I did that via the zwave2mqtt webUI, not in Home Assistant. In Home Assistant, the color dial is missing for this light. I can successfully toggle it as well as control brightness, but that’s it. There is no color control.

I am a beginner when it comes to zwave altogether. I have been using zigbee2mqtt exclusively for all my sensors etc. so far, but since I could not find a compatible smoke detector that applies European standards (can’t just use any smoke detector or your insurance might not cover anything in case of fire), I added zwave as well so that I can include smoke detectors as well.

Now, so far I have added these two bulbs as well as an Aeotec Multi-Sensor 6 ZW100-C - Z-Wave Plus multisensor. The multisensors seems to work fine. At least it will display all values I had expected, and then some (like door contact, which it doesn’t even support, but still shows up as an attribute in Home Assistant). I have not yet bought the smoke detectors as they are quite expensive and I wanted to see how well zwave works for me before investing (those light bulbs were only 10 bucks each, so they seemed fit as testing objects).

Question

what do I need to do in order to fully include all controllable options these bulbs offer into my Home Assistant lovelace?

Thank you for your help

Mutt · October 7, 2019, 9:57am

Not sure why you went zwave2mqtt, presumably you have a z_wave stick to communicate.?
Regardless, looking at your lower screenshot : -
You have the binary toggle as you state
You also have the brightness slider
If you were via z-wave I’d say with certainty that if you tap the bulb, a colour wheel will appear so you can choose a colour.
You could also specify the same, when you turn the bulb on from script / automation

joselito1 · October 7, 2019, 10:15am

Go to Zwave integration, for me also no RGB with zwave2mqtt

prankousky · October 7, 2019, 10:15am

I do have a z-wave plus stick and thought zwave2mqtt would be the best solution; I have been using zigbee2mqtt for a long time and it works quite well, so I just assumed that I should go the mqtt way with z-wave as well.

However, I am expecting my Aetonic Z-Wave stick tomorrow, and once it arrives, I’ll try this

prankousky · October 7, 2019, 10:30am

Actually I have just included my old (=current) Z-Wave stick directly via Home Assistant. One of the bulbs was added instantly, but it still does not offer any RGB control.

I went to settings - integrations - z-wave - and can only toggle it, but not set the color. I had previously set the color once via zwave2mqtt, and it worked (so RGB definitely works with that bulb).

Mutt · October 7, 2019, 10:30am

Have you tried tapping the bulb from the UI ?

prankousky · October 7, 2019, 10:33am

What (other?) UI do you mean? I am only able to control it via Home Assistant (webUI) and that’s where I tried controlling it with.

Mutt · October 7, 2019, 10:36am

Yeah you said that and it brings up the lower dialogue.
Have you tried tapping the bulb within that dialogue ?

prankousky · October 7, 2019, 10:40am

UPDATE: seems like the light was too far away. I moved it closer and then was once able to control color. It is stuck at the new color now, but will not turn off or change color when I try to. The other bulb paired, but will only display status, not any controls -.- I will see if I can change anything via config file…

The bulb is not clickable; I can click it, but nothing will happen - and the cursor stays a regular cursor (not the cursor that appears when hovering a link).

It only has these attributes

brightness: 170
node_id: 4
value_index: 0
value_instance: 1
value_id: 72057594109853697
friendly_name: Fantem (Oomi) Unknown: type=0003, id=0062 Level
supported_features: 1

No xy_color, no rgb_color, etc. (but I know that these colors can be set, as I did it before). Really strange.