search

zwave-js / zwave-js-ui

Full featured Z-Wave Control Panel UI and MQTT gateway. Built using Nodejs, and Vue/Vuetify
https://zwave-js.github.io/zwave-js-ui
MIT License
982 stars 202 forks source link

[bug] Fibaro RGBW v1 controller (FGRGBWM-441) module shows up as switch and dimmers (no color control) in HASS using MQTT. #351

Closed scyto closed 3 years ago

scyto commented 3 years ago

Before submitting a bug please read: https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/bug_report

Version

1.0.0-rc.1 Build/Run method

zwavejs2mqtt version: 1.0.0 zwavejs version: 6.0.0

Describe the bug

I added a Fibaro RGBW Dimmer It was propogated to HAAS like this:

image

this doesn't seem to be seen as an RGBW capable device by HAAS

However it is seen as color capable by zwavejs2mqtt

image

Additional context

Add any other context about the problem here.

scyto commented 3 years ago

logs and config fwiw zwavejs2mqtt-store (1).zip

robertsLando commented 3 years ago

@scyto Could you set the loglevel to debug?

scyto commented 3 years ago

Ok set logs to debug. Didn't delete anything Did a rediscover in control panel Checked MQTT explorer and I can see topic 51 is published into MQTT in the topic with the area name - this is the color state topic (11-51-0) .

In light and sensors there is nothing representing the color device (i assume it should be in light section?)

I do note in the Home Assistant Tab there is no corresponding ID, the 5 dimmers seem to refer to the multilevel switch 11-38-1 through 11-38-5. Entire store attached, i have left logging on debug incase you want to see it over longer period of time zwavejs2mqtt-store.zip

Let me know what else you need.

image image image

not sure if it matters, this is how it appears in HA. image

robertsLando commented 3 years ago

@scyto RGB color discovery has been added only recently, could you try to use dev tag?

scyto commented 3 years ago

i used dev tag from 48 hours ago, does it need to be more recent than that? either way, yes i will try this tonight my time and repull the dev container image

robertsLando commented 3 years ago

It's strange no rgb light is created since it's supported. The valueid is there

scyto commented 3 years ago

Yes, my assumption is that for HASS i would expect to see an rgbw device in \/light/wetbar-rgbw/\.

(this forced me to learn what an MQTT topic is and principles of hass discovery work last night :-) hopefuly i got that right)

Does this matter if the future direction is to use the wbesocket server? Do you envisage both paths into HASS being continued in parallel?

robertsLando commented 3 years ago

@scyto websocket server has been integrated on zwavejs2mqtt and will be the main way to use hass with zwave, my mqtt discovery will be still there for users that needs more customizations, it will be an alternative :)

Anyway there was a user that had an rgbw light working. @jcam It was you right?

jcam commented 3 years ago

image I deleted the device from HA, deleted all record of it from both the zwave and homeassistant topics in MQTT explorer, then re-ran discovery, and this is how it comes up (well, this but with a less useful name)

scyto commented 3 years ago

Just pulled the latest dev image from docker hub (seem image was updated 9m hours ago) No difference.

The symptom continues to be the rgbw device doesn't get created in the gateway topic in MQTT and is not shown here.

Looking at the node json nothing in the node 11, class 51 section that is being added to the hass discovery info in zwavejs2mqtt and i assume that is why it never appears in MQTT gateway discovery topi.? It appears in the regular MQTT topic just fine.

Lemme know what else you need.

node_11 (1).zip zwavejs2mqtt-store (1).zip

image

scyto commented 3 years ago

I deleted the device from HA, deleted all record of it from both the zwave and homeassistant topics in MQTT explorer, then re-ran discovery, and this is how it comes up (well, this but with a less useful name)

I have tried deleting every topic in MQTT several times over the last 2 days and that didn't fix it. I eventually realized this is because in MQTT there is no device topic in the discovery topic for this class of the device. Every other command class is propagated into the discovery topics, just not this one.

robertsLando commented 3 years ago

@scyto Could you please try to set log level to debug? Also delete the zwavejs2mqtt log file, it is almost 30MB now

scyto commented 3 years ago

@scyto Could you please try to set log level to debug? Also delete the zwavejs2mqtt log file, it is almost 30MB now

Every log setting in the UI is already has bee set to debug since you first asked, are you not seeing something you expect to? Is there a setting i missed?

Yes will delete that log file.

These are the settings that were set for the last couple of days:

image

scyto commented 3 years ago

Here is what i did to generate this zip file (with settings show in last post), if you need me to do something else just let me know.

joselito11 commented 3 years ago

I have problem with Zipato bulb not showing color picker in HA, I have zwaveJS2mqtt addon and and via zwaveJS integration. I can only on off and dim:

{
  "type": "light",
  "object_id": "dimmer",
  "discovery_payload": {
    "command_topic": "zwave/nodeID_24/38/0/targetValue/set",
    "state_topic": "zwave/nodeID_24/38/0/currentValue",
    "state_value_template": "{{ \"OFF\" if value_json.value == 0 else \"ON\" }}",
    "brightness_command_topic": "zwave/nodeID_24/38/0/targetValue/set",
    "brightness_scale": 99,
    "brightness_state_topic": "zwave/nodeID_24/38/0/currentValue",
    "brightness_value_template": "{{ value_json.value }}",
    "on_command_type": "brightness",
    "device": {
      "identifiers": [
        "zwavejs2mqtt_0xcf1381e2_node24"
      ],
      "manufacturer": "Zipato",
      "model": "RGBW Bulb V2 (RGBWE2)",
      "name": "nodeID_24",
      "sw_version": "2.0"
    },
    "name": "nodeID_24_dimmer",
    "unique_id": "zwavejs2mqtt_0xcf1381e2_24-38-0-currentValue"
  },
  "discoveryTopic": "light/nodeID_24/dimmer/config",
  "values": [
    "38-0-currentValue",
    "38-0-targetValue"
  ],
  "persistent": true,
  "ignoreDiscovery": false,
  "id": "light_dimmer"
}

No color in HA: https://imgur.com/a/H82UOxV Color switch in addon: https://imgur.com/a/8eL97dM

One more problem: the light is associated with Zwave.Me wall controller, and when I toggle light with controller, then the light state wont refresh.

The light is working with colors on zwave2mqtt addon.

robertsLando commented 3 years ago

@joselito11 Version?

joselito11 commented 3 years ago

Hmm Ha addon zwaveJS2mqtt is 0.2.1 or 1.0.1

robertsLando commented 3 years ago

@joselito11 Do you see the hexColor value in control panel?

joselito11 commented 3 years ago

No

robertsLando commented 3 years ago

@joselito11 I need some logs and/or a node export to check

joselito11 commented 3 years ago

2021-02-01 16:56:38.274 INFO ZWAVE: Node 24 is alive 2021-02-01 16:56:38.298 INFO ZWAVE: Node 24: value added 24-38-0-targetValue => 255 2021-02-01 16:56:38.302 INFO ZWAVE: Node 24: value added 24-38-0-duration => [Duration: undefinedseconds] 2021-02-01 16:56:38.315 INFO ZWAVE: Node 24: value added 24-38-0-currentValue => 0 2021-02-01 16:56:38.317 INFO ZWAVE: Node 24: value added 24-38-0-Up => undefined 2021-02-01 16:56:38.320 INFO ZWAVE: Node 24: value added 24-38-0-Down => undefined 2021-02-01 16:56:38.322 INFO ZWAVE: Node 24: value added 24-51-0-duration => [Duration: undefinedseconds] 2021-02-01 16:56:38.339 INFO ZWAVE: Node 24: value added 24-51-0-currentColor-0 => 0 2021-02-01 16:56:38.361 INFO ZWAVE: Node 24: value added 24-51-0-currentColor-1 => 0 2021-02-01 16:56:38.389 INFO ZWAVE: Node 24: value added 24-51-0-currentColor-2 => 255 2021-02-01 16:56:38.400 INFO ZWAVE: Node 24: value added 24-51-0-currentColor-3 => 159 2021-02-01 16:56:38.404 INFO ZWAVE: Node 24: value added 24-51-0-targetColor-0 => undefined 2021-02-01 16:56:38.407 INFO ZWAVE: Node 24: value added 24-51-0-targetColor-1 => undefined 2021-02-01 16:56:38.408 INFO MQTT: Subscribing to zwave/+/+/+/+/+/set 2021-02-01 16:56:38.410 INFO ZWAVE: Node 24: value added 24-51-0-targetColor-2 => undefined 2021-02-01 16:56:38.413 INFO ZWAVE: Node 24: value added 24-51-0-targetColor-3 => undefined 2021-02-01 16:56:38.416 INFO ZWAVE: Node 24: value added 24-112-0-1 => 31 2021-02-01 16:56:38.419 INFO ZWAVE: Node 24: value added 24-112-0-3 => 80 2021-02-01 16:56:38.422 INFO ZWAVE: Node 24: value added 24-112-0-2 => undefined 2021-02-01 16:56:38.424 INFO ZWAVE: Node 24: value added 24-112-0-4 => undefined 2021-02-01 16:56:38.428 INFO ZWAVE: Node 24: value added 24-112-0-255 => undefined 2021-02-01 16:56:38.431 INFO ZWAVE: Node 24: value added 24-114-0-manufacturerId => 305 2021-02-01 16:56:38.433 INFO ZWAVE: Node 24: value added 24-114-0-productType => 2 2021-02-01 16:56:38.435 INFO ZWAVE: Node 24: value added 24-114-0-productId => 3 2021-02-01 16:56:38.437 INFO ZWAVE: Node 24: value added 24-134-0-libraryType => 3 2021-02-01 16:56:38.440 INFO ZWAVE: Node 24: value added 24-134-0-protocolVersion => 4.38 2021-02-01 16:56:38.442 INFO ZWAVE: Node 24: value added 24-134-0-firmwareVersions => 2.0 2021-02-01 16:56:38.444 INFO ZWAVE: Node 24: value added 24-134-0-hardwareVersion => undefined 2021-02-01 16:56:38.450 INFO ZWAVE: Node 24 ready: Zipato - RGBWE2 (RGBW Bulb V2)

scyto commented 3 years ago

@joselito11 could i ask you to open another bug as: 1) you don't have a fibaro 2) your issue / symptom is utterly different as in your case you seem to have a color switch node being created in hass discovery information

I would like to keep this issue focused on the fibaro color switch node not being created in hass discovery on zwavejs2mqtt.

thanks.

scyto commented 3 years ago

@robertsLando what do you need from me for progressing with this issue about the color switch in the fibaro not being created within zwavejs2mqtt hass discovery information?

joselito11 commented 3 years ago

@scyto sorry

scyto commented 3 years ago

@scyto sorry

no worries :-)

robertsLando commented 3 years ago

@joselito11 I think you are running an old version of zwavejs2mqtt or zwavejs because I don't see that value

joselito11 commented 3 years ago

@robertsLando I updated the addon now:

2021-02-02 11:35:28.511 INFO ZWAVE: Node 24: value updated: 38-0-currentValue 255 => 99
2021-02-02 11:35:49.535 INFO ZWAVE: Node 24: value updated: 38-0-currentValue 99 => 0
2021-02-02 11:35:50.512 INFO ZWAVE: Node 24: value updated: 38-0-currentValue 0 => 255
2021-02-02 11:35:54.685 INFO ZWAVE: Node 24: value updated: 38-0-currentValue 255 => 99

app version 1.0.2 zwavejs version 6.1.1 https://imgur.com/UYPCxcc

On Off is now working fine-no more weird chgange with lag, but still no colors: https://imgur.com/a/MqYg3fo

What is about light not report-change state when toggled in association with Zwave.Me wall controller?

Upgraded to 1.0.3

2021-02-02 17:33:10.783 INFO ZWAVE: Node 24: value updated: 38-0-currentValue 99 => 0
2021-02-02 17:33:14.058 INFO ZWAVE: Node 24: value updated: 38-0-currentValue 0 => 255
2021-02-02 17:33:15.946 INFO ZWAVE: Node 24: value updated: 38-0-currentValue 255 => 99
scyto commented 3 years ago

I just pulled the latest :dev container.

I now seem to have 3 extra kwh sensors (all device 11-50-1) which is actually correct. Still no color switch in the home assistant discovery json despite it being listed in the node info.

image

robertsLando commented 3 years ago

@scyto @joselito11 I really have no clue about what's wrong here. Did you also give a try to the new zwavejs addon on hass? Just enable the zwavejs server on zwavejs settings and it will create entities for you. That will become the primary tool for hass, mqtt discovery will be there as an alternative to it when users would like some more customization :)

joselito11 commented 3 years ago

Have install the ZwaveJs addon and ZwaveJS integration and is all same as with ZwaveJs2mqtt addon. For info I hade same problem on Zwave2Mqtt and you have fixed it there: https://github.com/OpenZWave/Zwave2Mqtt/issues/68, for test I had it installed few day ago and color was working.

robertsLando commented 3 years ago

@joselito11 Could you send me some logs?

joselito11 commented 3 years ago

The addon log dont show nothing when I toggle light, the mqtt addon had showed it I could only find dump of network, this is from the light-nodeid 24

{"nodeId": 24, "index": 0, "installerIcon": 1536, "userIcon": 1536, "status": 4, "ready": true, "deviceClass": {"basic": "Routing Slave", "generic": "Multilevel Switch", "specific": "Multilevel Power Switch", "mandatorySupportedCCs": ["Basic", "Multilevel Switch", "All Switch"], "mandatoryControlCCs": []}, "isListening": true, "isFrequentListening": false, "isRouting": true, "maxBaudRate": 40000, "isSecure": false, "version": 4, "isBeaming": true, "manufacturerId": 305, "productId": 3, "productType": 2, "firmwareVersion": "2.0", "zwavePlusVersion": 1, "nodeType": 0, "roleType": 5, "deviceConfig": {"manufacturerId": 305, "manufacturer": "Zipato", "label": "RGBWE2", "description": "RGBW Bulb V2", "devices": [{"productType": "0x0002", "productId": "0x0003"}], "firmwareVersion": {"min": "0.0", "max": "255.255"}, "paramInformation": {"_map": {}}}, "label": "RGBWE2", "neighbors": [4, 16, 27, 28, 29, 32, 33, 39, 49, 54, 55, 56], "interviewAttempts": 1, "endpoints": [{"nodeId": 24, "index": 0, "installerIcon": 1536, "userIcon": 1536}], "values": [{"endpoint": 0, "commandClass": 38, "commandClassName": "Multilevel Switch", "property": "targetValue", "propertyName": "targetValue", "ccVersion": 2, "metadata": {"type": "number", "readable": true, "writeable": true, "min": 0, "max": 99, "label": "Target value"}, "value": 99}, {"endpoint": 0, "commandClass": 38, "commandClassName": "Multilevel Switch", "property": "duration", "propertyName": "duration", "ccVersion": 2, "metadata": {"type": "duration", "readable": true, "writeable": true, "label": "Transition duration"}}, {"endpoint": 0, "commandClass": 38, "commandClassName": "Multilevel Switch", "property": "currentValue", "propertyName": "currentValue", "ccVersion": 2, "metadata": {"type": "number", "readable": true, "writeable": false, "min": 0, "max": 99, "label": "Current value"}, "value": 99}, {"endpoint": 0, "commandClass": 38, "commandClassName": "Multilevel Switch", "property": "Up", "propertyName": "Up", "ccVersion": 2, "metadata": {"type": "boolean", "readable": true, "writeable": true, "label": "Perform a level change (Up)", "ccSpecific": {"switchType": 2}}}, {"endpoint": 0, "commandClass": 38, "commandClassName": "Multilevel Switch", "property": "Down", "propertyName": "Down", "ccVersion": 2, "metadata": {"type": "boolean", "readable": true, "writeable": true, "label": "Perform a level change (Down)", "ccSpecific": {"switchType": 2}}}, {"endpoint": 0, "commandClass": 134, "commandClassName": "Version", "property": "libraryType", "propertyName": "libraryType", "ccVersion": 2, "metadata": {"type": "any", "readable": true, "writeable": false, "label": "Library type"}, "value": 3}, {"endpoint": 0, "commandClass": 134, "commandClassName": "Version", "property": "protocolVersion", "propertyName": "protocolVersion", "ccVersion": 2, "metadata": {"type": "any", "readable": true, "writeable": false, "label": "Z-Wave protocol version"}, "value": "4.38"}, {"endpoint": 0, "commandClass": 134, "commandClassName": "Version", "property": "firmwareVersions", "propertyName": "firmwareVersions", "ccVersion": 2, "metadata": {"type": "any", "readable": true, "writeable": false, "label": "Z-Wave chip firmware versions"}, "value": ["2.0"]}, {"endpoint": 0, "commandClass": 134, "commandClassName": "Version", "property": "hardwareVersion", "propertyName": "hardwareVersion", "ccVersion": 2, "metadata": {"type": "any", "readable": true, "writeable": false, "label": "Z-Wave chip hardware version"}}, {"endpoint": 0, "commandClass": 114, "commandClassName": "Manufacturer Specific", "property": "manufacturerId", "propertyName": "manufacturerId", "ccVersion": 2, "metadata": {"type": "number", "readable": true, "writeable": false, "min": 0, "max": 65535, "label": "Manufacturer ID"}, "value": 305}, {"endpoint": 0, "commandClass": 114, "commandClassName": "Manufacturer Specific", "property": "productType", "propertyName": "productType", "ccVersion": 2, "metadata": {"type": "number", "readable": true, "writeable": false, "min": 0, "max": 65535, "label": "Product type"}, "value": 2}, {"endpoint": 0, "commandClass": 114, "commandClassName": "Manufacturer Specific", "property": "productId", "propertyName": "productId", "ccVersion": 2, "metadata": {"type": "number", "readable": true, "writeable": false, "min": 0, "max": 65535, "label": "Product ID"}, "value": 3}, {"endpoint": 0, "commandClass": 51, "commandClassName": "Color Switch", "property": "duration", "propertyName": "duration", "ccVersion": 1, "metadata": {"type": "duration", "readable": true, "writeable": true, "label": "Remaining duration"}}, {"endpoint": 0, "commandClass": 51, "commandClassName": "Color Switch", "property": "currentColor", "propertyName": "currentColor", "propertyKeyName": "Warm White", "ccVersion": 1, "metadata": {"type": "number", "readable": true, "writeable": false, "min": 0, "max": 255, "label": "Current value (Warm White)", "description": "The current value of the Warm White color."}, "value": 0}, {"endpoint": 0, "commandClass": 51, "commandClassName": "Color Switch", "property": "currentColor", "propertyName": "currentColor", "propertyKeyName": "Cold White", "ccVersion": 1, "metadata": {"type": "number", "readable": true, "writeable": false, "min": 0, "max": 255, "label": "Current value (Cold White)", "description": "The current value of the Cold White color."}, "value": 0}, {"endpoint": 0, "commandClass": 51, "commandClassName": "Color Switch", "property": "currentColor", "propertyName": "currentColor", "propertyKeyName": "Red", "ccVersion": 1, "metadata": {"type": "number", "readable": true, "writeable": false, "min": 0, "max": 255, "label": "Current value (Red)", "description": "The current value of the Red color."}, "value": 255}, {"endpoint": 0, "commandClass": 51, "commandClassName": "Color Switch", "property": "currentColor", "propertyName": "currentColor", "propertyKeyName": "Green", "ccVersion": 1, "metadata": {"type": "number", "readable": true, "writeable": false, "min": 0, "max": 255, "label": "Current value (Green)", "description": "The current value of the Green color."}, "value": 159}, {"endpoint": 0, "commandClass": 51, "commandClassName": "Color Switch", "property": "targetColor", "propertyName": "targetColor", "propertyKeyName": "Warm White", "ccVersion": 1, "metadata": {"type": "number", "readable": true, "writeable": true, "min": 0, "max": 255, "label": "Target value (Warm White)", "description": "The target value of the Warm White color."}}, {"endpoint": 0, "commandClass": 51, "commandClassName": "Color Switch", "property": "targetColor", "propertyName": "targetColor", "propertyKeyName": "Cold White", "ccVersion": 1, "metadata": {"type": "number", "readable": true, "writeable": true, "min": 0, "max": 255, "label": "Target value (Cold White)", "description": "The target value of the Cold White color."}}, {"endpoint": 0, "commandClass": 51, "commandClassName": "Color Switch", "property": "targetColor", "propertyName": "targetColor", "propertyKeyName": "Red", "ccVersion": 1, "metadata": {"type": "number", "readable": true, "writeable": true, "min": 0, "max": 255, "label": "Target value (Red)", "description": "The target value of the Red color."}}, {"endpoint": 0, "commandClass": 51, "commandClassName": "Color Switch", "property": "targetColor", "propertyName": "targetColor", "propertyKeyName": "Green", "ccVersion": 1, "metadata": {"type": "number", "readable": true, "writeable": true, "min": 0, "max": 255, "label": "Target value (Green)", "description": "The target value of the Green color."}}, {"endpoint": 0, "commandClass": 112, "commandClassName": "Configuration", "property": 1, "propertyName": "Internal bulb temperature", "ccVersion": 1, "metadata": {"type": "number", "readable": true, "writeable": false, "valueSize": 1, "min": 0, "max": 0, "default": 0, "format": 0, "allowManualEntry": true, "label": "Internal bulb temperature", "isFromConfig": true}, "value": 30}, {"endpoint": 0, "commandClass": 112, "commandClassName": "Configuration", "property": 3, "propertyName": "Strobe light pulse count", "ccVersion": 1, "metadata": {"type": "number", "readable": true, "writeable": true, "valueSize": 1, "min": 0, "max": 127, "default": 0, "format": 0, "allowManualEntry": true, "label": "Strobe light pulse count", "description": "Strobe light pulse count", "isFromConfig": true}, "value": 80}, {"endpoint": 0, "commandClass": 112, "commandClassName": "Configuration", "property": 2, "propertyName": "Strobe light interval", "ccVersion": 1, "metadata": {"type": "number", "readable": true, "writeable": true, "valueSize": 1, "min": 0, "max": 25, "default": 0, "format": 0, "allowManualEntry": true, "label": "Strobe light interval", "description": "Strobe light interval", "isFromConfig": true}}, {"endpoint": 0, "commandClass": 112, "commandClassName": "Configuration", "property": 4, "propertyName": "Random strobe pulse colors", "ccVersion": 1, "metadata": {"type": "number", "readable": true, "writeable": true, "valueSize": 1, "min": 0, "max": 1, "default": 0, "format": 0, "allowManualEntry": false, "states": {"0": "Random strobe pulse colors OFF", "1": "Random strobe pulse colors ON"}, "label": "Random strobe pulse colors", "description": "Random strobe pulse colors", "isFromConfig": true}}, {"endpoint": 0, "commandClass": 112, "commandClassName": "Configuration", "property": 255, "propertyName": "Reset bulb to factory settings", "ccVersion": 1, "metadata": {"type": "number", "readable": false, "writeable": true, "valueSize": 4, "min": 1, "max": 255, "default": 1, "format": 0, "allowManualEntry": true, "label": "Reset bulb to factory settings", "description": "Reset bulb to factory settings", "isFromConfig": true}}]},
robertsLando commented 3 years ago

@joselito11 Enable logs to file on both general and zwave section, set loglevel to debug on both, go to store select those files and press on the bottom right button to export them in a zip

(remember to disable log to file then, they becomes huge files in low time)

joselito11 commented 3 years ago

All data: zwavejs2mqtt-store (4).zip

robertsLando commented 3 years ago

@AlCalzone Any clue why the hexColor value isn't created here?

AlCalzone commented 3 years ago 
{"k":"{\"nodeId\":24,\"commandClass\":51,\"endpoint\":0,\"property\":\"supportedColorComponents\"}","v":[0,1,2,3]}

According to the device, it supports Warm White (0), Cold White (1), Red (2) and Green (3), but not Blue (4).

@joselito11, please re-interview the node (refreshNode) and post me a log of that.

AlCalzone commented 3 years ago

https://community.zipato.com/topic/no-blue-channel-for-rgbw-bulb-2 --> Might be a firmware issue

joselito11 commented 3 years ago

New logs: zwavejs2mqtt-store (5).zip

AlCalzone commented 3 years ago

Definitely a device bug:

13:27:55.101 DRIVER « [Node 024] [REQ] [ApplicationCommand]
                      └─[ColorSwitchCCSupportedReport]
                          supported color components:
                          · Warm White
                          · Cold White
                          · Red
                          · Green

I double-checked the data it sends and there is no bit for the Blue channel

joselito11 commented 3 years ago

Thanks. But there is no option to upgrade without zipato hub? Colors were working on old 1.4 and zwave2mqtt.

AlCalzone commented 3 years ago

OZW probably had a workaround for this. You could ask the Zipato support for a firmware file to update and use that to update via zjs2m. The Aeotec support for example gives out updates if you ask.

AlCalzone commented 3 years ago

Also, as a short-term workaround:

  1. Shut down zwavejs2mqtt
  2. open <your-home-id>.values.json, add these two lines at the end: 
    {"k":"{\"nodeId\":24,\"commandClass\":51,\"endpoint\":0,\"property\":\"supportedColorComponents\"}","v":[0,1,2,3,4]}
{"k":"{\"nodeId\":24,\"commandClass\":51,\"endpoint\":0,\"property\":\"supportsHexColor\"}","v":true}
  3. Start zwavejs2mqtt.
  4. Leave your hands off the refreshInfo button!
joselito11 commented 3 years ago

Will try later and report. Have also contacted Zipato for firmware.

robertsLando commented 3 years ago

Also, as a short-term workaround:

@joselito11 YOu can do this from the store explorer UI

AlCalzone commented 3 years ago

Worth a try, but the driver should not be running to avoid inconsistencies in the cache.

robertsLando commented 3 years ago

Worth a try, but the driver should not be running to avoid inconsistencies in the cache.

Humm maybe it's better if he stop zwavejs2mqtt and does the edit manually to be sure

joselito11 commented 3 years ago

Thank you both for help and support! Have problem to change the file, store UI can not open any file, can only download. I have edit file via Portainer console, but can only do this by running addon(if the addon is stopped, portainer in ha wont show it). No change after. Tried also with addon restart. Logs: zwavejs2mqtt-store (6).zip

AlCalzone commented 3 years ago

Hm, that didn't get picked up. The linked cache file is back to false and [0,1,2,3]

joselito11 commented 3 years ago

Yeah, but no option to edit when the addon is stopped.

AlCalzone commented 3 years ago

@robertsLando any more ideas? I didn't see anything in the log where this was overwritten.