ZWaveJSMQTT: Fibaro RGBW doesn't show color control wheel

Configuration
4

I have the same behaviour as both of you - also getting 5 dimmers of which one acts as the main switch. Appears to be a bug or feature that hasn’t been build in yet? I found this topic which is not exactly the same but similar - https://github.com/zwave-js/zwavejs2mqtt/issues/477 . I checked whether the recommended lines are in the *.values.jsonl, which it is.

{"k":"{\"nodeId\":6,\"commandClass\":51,\"endpoint\":0,\"property\":\"supportedColorComponents\"}","v":[0,2,3,4]}
{"k":"{\"nodeId\":6,\"commandClass\":51,\"endpoint\":0,\"property\":\"supportsHexColor\"}","v":true}

Do any of you know where I to submit this as a bug/feature request?

5

I found the issue being reported here - https://github.com/zwave-js/zwavejs2mqtt/issues/351 doesn’t seem to be a perm. fix yet.

1 Like
6

Something else odd; I looked at the list of entities for the RGBW controller that I had when running OpenZwave (beta), and instead of 5 dimmers, there were actually 6 Light controls:

Node 14:

  • LEDs 1 Woonkamer: Instance 1: Level
    light.multilevel_power_switch_instance_1_level

  • LEDs 1 Woonkamer: Instance 2: Level
    light.multilevel_power_switch_instance_2_level

  • LEDs 1 Woonkamer: Instance 3: Level
    light.multilevel_power_switch_instance_3_level

  • LEDs 1 Woonkamer: Instance 4: Level
    light.multilevel_power_switch_instance_4_level

  • LEDs 1 Woonkamer: Instance 5: Level
    light.multilevel_power_switch_instance_5_level

  • LEDs 1 Woonkamer: Instance 6: Level
    light.multilevel_power_switch_instance_6_level

  • LEDs 1 Woonkamer: Electric - kWh
    sensor.multilevel_power_switch_electric_kwh

  • LEDs 1 Woonkamer: Electric - W
    sensor.multilevel_power_switch_electric_w

  • LEDs 1 Woonkamer: Power
    sensor.multilevel_power_switch_power

7

I see that this issue has now been raised for the core ZWave JS as well:

1 Like
8

I can confirm that on the following versions, the color wheel is working for the FGRGBW-442.

zwavejs2mqtt: 4.2.1
zwave-js: 7.4.0
homeassistant: 2021.5.4

Great!

9

Hmm, I’m still not seeing the color wheel for my FGRGBW-442 here… The color wheel entity is still showing as unavailable:

Home Assistant 40
Home Assistant 40361×1092 65.9 KB

I am running later versions than you are, but I don’t think that there has been a regression here, since at one time I would have been running the same versions as yourself, and I have never seen the color wheel since I moved from OpenZwave (beta) to ZWaveJS…

zwavejs2mqtt: 4.3.0
zwavejs driver: 7.5.0
zwavejs server: 1.5.0
Home Assistant Core: 2021.5.5

10

No, it is not working just by upgrading. I’m on the latest everything. zwavejs2mgtt, zwave-js under the hood, HA.
No color wheel still. What steps did you take to get it working?

11

Nothing specific, just using the latest dockers for HA and ZWJS2MQTT. I enabled the five switches and when I switch on the main switch, I also start the white led with an automation (don’t know if that is still needed, it was required before the wheel started working.

image
image229×924 12.8 KB

The configuration in ZWJS2MQTT is the following:

image
image1313×838 38.9 KB

image
image1307×466 21.9 KB

12

Your config screen in the zwavejsmgtt admin looks entirely different than mine. I re-interviewed, but didn’t help. I actually have a color picker in the admin tool.

image
image1082×960 36.5 KB

13

Strange…version info of the device says this:

image
image1565×99 5 KB

14

image
image1084×153 4.61 KB

15

Are you sure you have the 442?

16

I am not sure, I don’t know to what 442 is referring.
What I will say is it worked on the now deprecated native zwave solution.

17

441 is the Fibaro RGBW Controller, 442 is the successor, the Fibaro RGBW Controller 2. I have the 442, which is shown in both applications. Don’t see that in Geoff’s screenshot, which does show the same FW version you have. So I think you have the 441.

18

Makes sense.

19

All of a sudden my 442 started working. I already had a colorwheel, it just did not do anything when selection colors… I does now… not sure why, only updated regular things as they came out…

442-3
442-3589×1012 83 KB

But now a new question, how do I get the pre-programmed sequences activated ?
442-1
442-11231×534 32.3 KB

I see them and can activate from Z-Wave JS Controlpanel, but not (yet) in HomeAssistant itself.
442-2
442-2782×698 24.2 KB

I would like to use them via NodeRed to activate for example when the doorbell rings…
but the available items in developer options to do seem to do much with regards to the sequences:
442-4

20

Still not working on 441, firmware 25.25

21

Like this… I call it from a script, change your node_id to match

Screenshot 2021-08-16 9.57.43 PM

22

This is great @ThatGreekAaron !

I got it to work from calling the WebUI of MQTT Zwave !!

I have no idea of how to incorporate it into a card or UI … can anyone please point me to some info where I can learn how to do it?

23

Not to worry … got it working here !!