Cover status not updated after an open/close action

[mariusz-schimke]

Problem/Motivation

I have a Z-Wave gate controller (Nice IBT4ZWAVE). When I tap a button in HA to open or close the gate, its state does not update until the gate finishes the movement (which takes over 30 seconds).

Expected behavior

When the gate is being opened/closed, I'd expect its status to change right away to opening/closing accordingly.

Actual behavior

I have to wait for over 30 seconds for the state of the gate to update to opened/closed. During that period you don't know whether your tap action was accepted or not. Unless you stand in front of the gate, which is not always the case :).

Steps to reproduce

Have a cover button on the UI. Click it to open or close the cover. You will see the state does not change until the cover fully opens or closes (or is stopped manually).
It doesn't refer to this specific gate controller, but to all controllers of type cover (e.g. window blinds too).

Proposed changes

I performed some investigations to learn whether the state right after an action taken can be devised in any way. In fact, the problem affects not only the Nice gate controller, but also all my window blinds (Fibaro FGR-223). Initially I thought that the transition is undetected by HA because the devices themselves only notify about their final states. But when I analyzed Z-Wave JS logs yesterday, I realized that all necessary information is already there. This might mean they can be made use of in HA if they are accessible programmatically.

What surprising for me is that the transition action is also visible in logs even if the movement was triggered by a step-by-step input of the gate's control panel rather than by the Z-Wave controller.

I found a workaround by attaching an ESP32 module to the gate control panel so that it provides me with the current state of the gate (and a few other things), but if that information is already available directly from the Z-Wave gate controller, the solution seems stupid...

Please tell me what you think. I'll be grateful if you share your thoughts on this with me. Thank you!!

I attached two log files with notes in their initial lines.
zwave_js-gate-closing-triggered-by-z-wave-controller.log
zwave_js-gate-opening-triggered-by-an-external-button.log

Update

I added a feature request here since I wasn't sure if here is the right place, sorry!

[Dites33]

Sorry to disturb inthe middle of your question (with no answer for now :(() but I have the same controler, added but no buttons are working, nothing happen.
How did you add the IBT4ZWAVE ?

zwave-js-ui: 9.21.0
zwave-js: 13.4.0
home id: 3900514980
home hex: 0xe87d22a4

[mariusz-schimke]

Hello @Dites33! I'm using the Z-Wave JS UI add-on for HA version: 3.13.1.

I included the device through the Z-Wave integration in System > Devices (not through the Z-Wave JS UI add-on):

I did it over a year ago, so the versions were different, but it worked without any issues then. I couldn't only establish a secure connection, but it happens among different devices. Maybe my gate is just too far from the controller (IDK exactly what may cause the problem).

Here are the entities I can access in HA through the integration:

And the device info:

I'm not sure if it helps...

By no buttons are working do you mean that you do have them on the UI but the gate doesn't react or that they aren't available as HA entities at all?

[Dites33]

Thanks for your reply

I have the entities but the fate doesn't react

[mariusz-schimke]

OK, that looks the same as in my case. Have you looked at the connections graph in Z-Wave UI? Check the edge colors between the nodes that join your gate controller with the Z-Wave controllers. Are all of them green or yellow, or are there any red ones, making the route unstable?

Oh, there is one more thing that comes to my mind. There are two drop-down menus created by the integration:

• Local protection state,
• RF protection state.

Local protection state in Fibaro devices blocks physical buttons so when you press them, there is no reaction. RF protection, on the other hand, is an option that prevents controlling the device remotely, by Z-Wave commands. If that one is set to NoControl, then any control commands sent to the gate will be ignored.

Please check these two and let me know if any of them was the case, @Dites33.

Update: I'd also open the cover of the gate control unit and press the S button on the IBT4ZWAVE module. Just to check if there is a correct connection between the module and the control unit. Of course, make sure that the Local protection state option is not set to NoOperationPossible ;).

[sirrkitt]

I'm not sure if this is related or not but I noticed that after one of the latest updates, that my ZEN53 had stopped responding to open and close commands. I couldn't figure out why my chicken coop door hadn't been closing at night (or opening when I'd manually close it) and I noticed that the open and close buttons were not responding.

Connection has been fine and this had been working, automated, for a few months until recently.

I can, however, set the door to 100% and 0% to get it to open and close, which I found to be kind of odd.

I just updated to again today and it seems to be back to somewhat working but it takes a while to update and there seems to be a delay with sending the command and the device responding.

I don't see any connection issues with the device.

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[Dites33]

I have the latest version, i already tried to include again and again.
The NICE BITIZWAVE seems to be reconized, but nothing is working on the cover side. I don'"t know how to look or what to try :(

[mariusz-schimke]

@Dites33, have you tried looking at the Z-Wave add-on logs?

[Dites33]

Hello @mariusz-schimke , thanks for your reply

From Zwave.js the devise is see as this

Then i click to start and stop (i tried from the start on the left to the stop from the right) i see api write and send are ok

here are logs from Zwave addon

2024-11-17 164534.956 DEBUG.txt