Add workaround for duration support on sendCommand set

[matejdro]

This is a workaround for zwave-js/node-zwave-js#1321 that allows setting MultiLevelSwitch with duration parameter via sendCommand mqtt topic by specifying second parameter in the set command as duration seconds.

This is not ideal, but it allows us to at least use dimming duration in some way until proper solution is developed (which appears to take a while).

[robertsLando]

@AlCalzone Could this lead to other kind of issues? Or break old sendCommand?

[zwave-js-assistant]

🚧 It seems like this PR has lint errors 🚧

I should be able to fix them for you. If you want me to, just comment
@zwave-js-bot fix lint

[AlCalzone]

Could this lead to other kind of issues?

Not every CC that has a set command accepts a value and duration.
Basic CC doesn't: https://zwave-js.github.io/node-zwave-js/#/api/CCs/Basic
Color Switch CC doesn't: https://zwave-js.github.io/node-zwave-js/#/api/CCs/ColorSwitch?id=set
Door Lock CC doesn't: https://zwave-js.github.io/node-zwave-js/#/api/CCs/DoorLock?id=set
Thermostat Setpoint CC will break if you do this: https://zwave-js.github.io/node-zwave-js/#/api/CCs/ThermostatSetpoint?id=set
Same with User Code CC: https://zwave-js.github.io/node-zwave-js/#/api/CCs/UserCode

Essentially, this is only okay for
https://zwave-js.github.io/node-zwave-js/#/api/CCs/BinarySwitch?id=set
https://zwave-js.github.io/node-zwave-js/#/api/CCs/MultilevelSwitch?id=set
https://zwave-js.github.io/node-zwave-js/#/api/CCs/SceneActivation?id=set

However, I'd prefer if this was done in those methods in the driver that do accept a duration. One way we could represent the duration would be a string like 2m5s or 55s to leave no doubt what the value means.

[matejdro]

Should I add a check for the type of CC?

[matejdro]

@zwave-js-bot fix lint

[zwave-js-bot]

🐌 Please wait for the lint check to complete, then try again.

[robertsLando]

However, I'd prefer if this was done in those methods in the driver that do accept a duration. One way we could represent the duration would be a string like 2m5s or 55s to leave no doubt what the value means.

I'm +1 for this. If so this PR could be closed and this should be handled on zwavejs side

[zwave-js-assistant]

🚧 It seems like this PR has lint errors 🚧

I should be able to fix them for you. If you want me to, just comment
@zwave-js-bot fix lint

[matejdro]

Well the idea was to add quick and dirty workaround until real duration support is ready without the need to change the core zwavejs side. But I guess I can take a stab at editing the zwavejs intead.

[AlCalzone]

Sure but if that change is going to be incompatible with the desired solution we'll end up with a breaking change down the line.

[robertsLando]

I see no reason to merge e temporary (breaking) dirty solution, I prefer to wait the support to be added on zwave-js side to allow back compatibility