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:
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).
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 ?
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?
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
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.
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.