Add compat flag to override values reported by a device

[AlCalzone]

To work around this device firmware (!) issue on the zwave-js side, we need to add a compat flag that allows us to override specific values and avoid querying them from the device (because in this case the supported colors response is simply wrong).

Originally posted by @AlCalzone in zwave-js/zwave-js-ui#477 (comment)

[scyto]

Is this fix required per device definition file or somewhere else?
Is this just new integration specific or would apply to the MQTT hass discovery code path?

[AlCalzone]

This needs to be done in the device config files where necessary to fix wrong device-specific capability reports.

In the mentioned issue, the device does not report that it supports the blue color channel, based on which the channel is not queried by zwave-js and RGB (hex) support is assumed to be false.

[scyto]

thanks, could this be the root cause on the fibaro rgbw v1?
Z-Wave-Me/z-way-issues#163 (comment)

this person has indicate the device has a pretty bad bug on reporting channels....

I can take point on the fibaro rgbw file if someone tells me what to add (folks seem to mentioning difference devices so i assume we will need to edit multiple device files)

[AlCalzone]

That looks different

[joselito11]

Will be some update on version 7 for this rgb bug?

[AlCalzone]

Sorry, that would require a larger rework of the interview process where I'd have to touch every CC implementation in several locations.

[joselito11]

So on HA core-2021.4.0b0 and with zwaveJS addon 0.1.15 the light has color wheel, must click few times to get the color, but it works! Thanks!

[AlCalzone]

I didn't do anything here 😳

[joselito11]

Color picker is gone again, any idea how to get it back? Have deleted zwavejs integration, reinstalled addon