Qubino Shutter ZMNHCD1 physical switches synchronization to HA [Solved]

Configuration Z-Wave
1

Hi,

I have an issue about the Qubino Shutter ZMNHCD1.

Everything work like a charm:

  • Up/Down (from HA and from physical Switch)
  • Set/Get Position at a specific value

My issue is when I use the physical wall switches, position is not updated in HA (Even after many hours).

To solve the issue, I can restart HA or manipulate it by HA (That will update the value)

I, of course, already try to reinitialize it and re-integrate it in the zwave network but it doesn’t change anything

Do you have an idea to solve this issue?

FYI, I have also 6x Fibaro FGR-222 “Roller Shutter 2” and absolutly not this bad behavior

Thanks,

2

Nobody have this issue?
So sad :frowning:

3

I’ve had this with the tilt functionality in venetian blind mode, but not for up/down.
What solved it for me was removing the association and adding it again with an instance parameter. So calling the association service twice - first with:

association: "remove"
node_id: <your node id>
group: 1
target_node_id: 1

then with:

association: "add"
node_id: <your node id>
group: 1
target_node_id: 1
instance: 1
4

Have you set the polling interval?

5

Hi,

Thanks for your answer.
I will take a look

Thanks,

6

Hi,

I don’t know if it’s your suggestion but I tried to change this parameter:

image
image1179×1743 161 KB

Is it your suggestion?

FYI, it didn’t change anything

Thanks,

7

Yes, correct. You can set the polling intensity to 1 or 2, that reports the status back on a regular base. It’s not real-time but worked for me (don’t have z-wave anymore).

Here’s the documentation:

8

Seems to work thanks.

I’m wondering if the last time, I had set 10 instead of 1 or 2 and it was probably my issue.

So, seems to work correctly with a polling intensity to 1

Thanks!

9

There’s no need to poll with these devices. They support hail.

10

I agree and I have no problem with Fibaro but there is an issue with the Qubino in HA and nobody knows what happening

11

Hi Xes,
I’m also a user of ZMNHCD1 in HA, since November 2018.
I’ve already sent a message to DudeShemesh to get his feedback over the behavior of these modules, but I have to say that for me, the reliability fully disappeared since a few HA release (estimate after 0.96).
Lots of commands not being executed, and an absolute erratic displayed state in HA.
What is the status from your side ?

12

Did you try my instructions above?

13

I believe I mentioned this several times in the forum - I find these modules very unreliable. First of all, I’ve already had several of them go bad, but even when they’re not defective they have many problems.
I’m mostly seeing out of sync info on the tilt channel, which is partially resolved by my instructions above.
I have not noticed any regression - this was always the case, and I started using them way before 0.96. Given that you mentioned dropped packets, and I know that auto-heal was dropped at some point around that time frame, maybe try to heal your network?

14

What is the status from your side ?

Hi,

The workaround (set polling intensity to 1) seems to work even I didn’t have the oportunity to test a lot because it’s for awning and the weather is not good this week :wink:

I didn’t try to re-associate the device because the device is far from the HA box and normally, to add a new device, I just need to unplug and use the autonomous Aeon Z-Stick to associate new device.

So, it is not properly fixed but it works

15

You don’t need to re-add it. Just run the commands I shared and that’s it. It only takes a couple of seconds, and there’s no need for physical access to the device.