Feature request: Fibaro dimmers and hidden entities

[Dinth]

Hey. I find the idea of hiding unusable entities in Zwave-over-MQTT really great and helpful. Unfortunately, there's one instance, where unusable entity is not only visible, but a whole new device is created for it - which is Fibaro Dimmers 2. Each of my dimmers have two devices created in the integration - one has all the internal sensor and a functional switch, and the other device has only the none functional switch. It would be great to have the second switch hidden by default in the same way as all other unusable entities are being hidden

[kpine]

How does HA know that the switch is not functional?

[Dinth]

To be honest i dont know, in fact ive been previously told that OZW doesnt have any information about unusable classes, and yet somehow Z-over-MQTT can detect such unusable classes and hide the entities created from them by default. Maybe it could just be hardcoded for those few devices which have unusable switch classes? PS. It seems that Single Switch 2 also have such unusable switch.

[kpine]

I don't have these devices, but I've looked at the manuals before. It provides switches S1 and S2, so I always thought those are the two switches provided.

S2 has functionality but it's not enabled by default. I assume S1 is instance 1 and S2 is instance 2, but like I said, I haven't used these.

[Dinth]

I think you're confusing input and output terminals here @kpine. The output terminal (which actually is controlled through Zwave) is the one with sinusoidal symbol. S1 and S2 are only for wall switches as a mean of additional, manual control of the built in switch and - i believe - are totally unrelated to Zwave classes exposed by the device.

Actually i did contact Fibaro support before to ask about the second switch class on those devices and here's what they have replied (sorry for Google Translate):

Sorry for the long response time, Switch 2 can activate scenes in the Z-Wave controller by sending the scene identifier and the action data attribute using the central Scene command class. By default, scenes are not activated, set parameters 28 and 29 to enable scene activation for selected actions.

The Switch Multilevel command class is also used to create and operate associations. Association (pairing) - direct control of another device in the Z-Wave network, e.g. Dimmer, Switch (ON-OFF), Roller Shutter Controller or stage (only via the Z-Wave controller). This link can be beneficial: https://manuals.fibaro.com/content/manuals/pl/FGS-2×3/FGS-2×3-PL-T-v1.2.pdf

[marcelveldt]

The 2nd instance on these Fibaro dimmers is indeed used for associations. You can for example control an associated light (or group of lights) with the second wall switch.

I own the Fibaro Dimmers myself too so I know exactly what you mean.

There is no way for us to tell in code if that 2nd instance needs to be there or not. So you will have to disable those entities yourself I'm afraid. I will take a quick second look if I see some loophole to detect this is a "fake" instance.

[marcelveldt]

BTW: Just as an FYI, this Instance 2 behaviour also exists in the current Z-wave implementation.