Missing commands for NICE Spa - IBT4ZWAVE - BusT4-Z-Wave interface

[stomko11]

Support for NICE Spa - IBT4ZWAVE - BusT4-Z-Wave interface has been added several months back. However I struggle to be able to control it properly. In Fibaro HC3, I was able to open/close the gate and stop it at any position.
Here, it looks like that only available parameters in multilevel switch are Current and Target value, which allow only values 0 or 99 to close/open the gate. I was not able to find any way to stop the gate in any position, or specify value (similar to when using cover).

Here is the ZwaveJS DB device: https://devices.zwave-js.io/?jumpTo=0x0441:0x2400:0x1000:0.0
PR where device was added: #2525
And here are the commands supported by the device: https://www.niceforyou.com/sites/default/files/upload/manuals/isa00mm.pdf

If I look at "Table 6 - Multilevel Switch Command Class SET" it does not look like there is any command that can be sent to stop the gate.

Any advise would be appreciated.

[kpine]

You could contact the manufacturer and ask how to do it.

If it's anything like normal window covers, you can use the Multilevel Switch Stop Level Change Command. All devices should support this command. There's a CC API method to do this, stopLevelChange.

If you're using the Value API, such as in zwavejs2mqtt or HA, either of these Up or Down values will send the stop command when you use an "Off" (false) value. If you don't have Up/Down, it could be something else like Close/Open.

If not stopLevelChange, then sometimes you have to set the multilevel targetValue based on the direction. If it's opening, send close (0), and if it's closing, send open (99).

[Loic691]

Hi
Yes we can send with zwave-js-ui the Stop command in the 38/0/targetValue/set command to stop it
So ther is a problem in the 38/0/currentValue command wich now get only 0 or 99 (seams closed or opened).
In fact manufactuer says the 254 value is a opening, closing or Stopped status..
Here's the manufacturer data

The duration state is an error too.
When closed we have duration = 0
When opened we have "unknown" instead of 254 (0xFE)

I think there is a bug wich value > 99 in the zwave-js driver

[AlCalzone]

When opened we have "unknown" instead of 254 (0xFE)

Yes because this is the definition of that value from the Z-Wave specification. Your device doesn't seem to have defined intermediate positions, so the current value is unknown in these cases.

[Loic691]

Ok so i will try to use the unknow value of duration to compute the good state.
So I understand that Nice have worse implementation of the zwave protocol. I am right ?

[AlCalzone]

I wouldn't say it's bad, they are using a feature that the protocol provides.

This seems more like a hardware or implementation limitation, other shutters seem to interpolate the current position by moving time instead of just saying the position is unknown.

[Loic691]

ok understand

[arnog23]

Hi,

From what I understand from the Zwave specification (page 100), value 254 is allowed as "Unknown position" for the Multilevel Switch CC.

whereas ZwaveJS is not allowing it as the value is restricted between 0 and 99.

Would it be possible to allow 254 value for the currentValue and targetValue in the Multilevel Switch CC ?

This 254 value was allowed by OpenZwave and it was helpfull to know if the gate is opening, stopped or closing and not only opened (99) or closed (0).

Thanks.

[arnog23]

I need to think about it.

Thanks

On the other hand, "unknown" is much clearer in what it means than 254 to users who don't know the specs.

Not really here. 254 means something else (opening, closing or stopped) than "unknown" based on combination of current and target values, so it have a signification. By the way, the other values are not translated as "open" (for 99) and "close" (for 0) but their numeric values are kept.

The issue under 2. won't be solved by this change, since 254 is still not a valid value for set-type commands.

Ok

[arnog23]

Have you had time to think about it? :-)

[arnog23]

On the other hand, "unknown" is much clearer in what it means than 254 to users who don't know the specs.

Not really here. 254 means something else (opening, closing or stopped) than "unknown" based on combination of current and target values, so it have a signification. By the way, the other values are not translated as "open" (for 99) and "close" (for 0) but their numeric values are kept.

Any thought about it ?

[arnog23]

@AlCalzone, any chance to get improvement about this ?

[arnog23]

@AlCalzone, have you put it on your roadmap ?

[Stephane-80]

Yes 254 status value is very important because without it :
0 -> closed
99 -> open
without opening value (254) the system thinks that the door is fully closed even if it is 99% open in reality (sliding gate for example) but not at the end of its travel
the 0 value change to 99 only when the gate reaches full opening

[Seby9576]

Bonjour,

Il serait bien que le module IBT4 soit bien reconnu et les commandes créées automatiquement afin de recuperer l'etat en mouvement mais aussi l'etat des cellules par exemple

[AlCalzone]

English please 🙏🏻

[tetiti20]

I am also waiting for an update please

[jossalison38]

hello same problem for me, pedestrian opening sliding gate not taken into account.
I hope for progress on the subject
THANKS

[AlCalzone]

This is on my radar for v11. Locking this now since the "ping" spam is annoying.

[AlCalzone]

#5864