Rule condition shows TRUE in UI but Rule never transitions to SET — survives full restart

[d868]

Hi, has anyone got a Fibaro FGD212 dimmer working with Home Assistant and MSR? I have moved one of these devices from my Vera controller to my Home assistant controller and MSR isn't displaying any of the dimming capability. When it was on the Vera it showed the dimming capability in MSR and all the associated actions, but now it's on the Home assistant controller I can't see those in MSR.

In Home assistant I can see and use the dimming OK, so I'm wondering does MSR just need to have the mapping/capability added to the HASS configuration, or is there something more that needs to be done?

[d868]

Hi @toggledbits, do you have any thoughts on this? I was going to have a look at the mapping myself to see if it's just additional capabilities that need to be updated, but I wanted to check with you first. I'm running MSR as a docker container so if that's what needs to be done are the devices and capabilities YAML files within the docker image, or the configuration volume? I see in the documentation you mention that we can create our own mappings and capabilities by creating configuration files in the local subdirectory of the Reactor installation. Is that within the config volume, or do they need to be within the container? If that's what's required I was hoping to have a look at the system config ones to check the formatting required.

[toggledbits]

Open a ticket in Mantis for the device on HomeAssistant, and post your hass_states.json file (from your logs subdirectory) on the PR. The Fibaro devices identify very strangely and are a consistent source of agony (for Vera as well). I can give you custom config and instructions from that, and also address it in the core device files if it doesn't create a conflict with other devices.

[d868]

Thanks. TIcket has been logged in Mantis.

[toggledbits]

I see it. I will be looking at it shortly.

Which device is it? (name) And can you control dimming for it on the Hass UI (Lovelace)?

[toggledbits]

For the benefit of readers, PR 0000223 was opened for this, and it was determined that (a) ZWave-JS component is not completely/correctly setting the supported_features attribute (a bit mask) for the device in question, and (b) perhaps related, Hass is moving away from using supported_features for the description of color and dimming capabilities on light domain devices. They are moving to a new supported_color_modes attribute, which is an array containing keys such as: onoff, brightness, rgb, rgbw, rgbww, hs, xy, etc. In the case of the subject device (Fibaro FGD212), the ZWave-JS component was giving supported_features as 32, so missing the bit 0 flag to indicate a dimming-capable device (should be 33), but is providing brightness as a mode in supported_color_modes.

I've made new Docker images with an updated capabilities file for HomeAssistant that uses both the old supported_features bitmask and the newer supported_color_modes array, and as expected, the device now has dimming capability. The new docker images carry the datestamp 21175 and can be pulled now from DockerHub. I have not planned on making a generic downloadable package for this, but if any HomeAssistant user needs it, just let me know and I'll roll a full release early and update the download link in Mantis.

[d868]

Thanks for the super quick resolution on this PR!