Multilevel Switch values can get exposed although Window Covering CC is supported

[AlCalzone]

...these will result in errors when used

[AlCalzone]

This seems to happen when devices support both Window Covering CC and Multilevel Switch CC, and report changes of the Window Covering status using Multilevel Switch CC instead, see also https://github.com/zwave-js/node-zwave-js/discussions/7049

[com6056]

👋 any updates on this? I think I'm running into it, happy to provide any debug info needed to get this fixed up! 🙌

[AlCalzone]

I know what needs to be done - it's just a matter of finding the time to actually tackle this. Let's see if we can't kickstart this.

[AlCalzone]

Some device support both the Window Covering CC and Multilevel Switch CC for backwards compatibility. As per the Z-Wave specifications, Multilevel Switch CC must be hidden in favor of Window Covering CC if supported. All controlling of the device should go through Window Covering CC.

However, some device still report their status using Multilevel Switch CC. Even though Z-Wave JS originally filters out those values, the unsolicited reports cause them to get exposed to applications.

@Copilot find where incoming Multilevel Switch CC reports are handled. If Window Covering CC is supported, make sure the Multilevel Switch CC reports are mapped to the corresponding Window Covering CC values instead. This probably requires refactoring the automatic persistence of Multilevel Switch CC values in favor of handling those reports "manually", like we already do for Basic CC for example.