[SOLVED] Z-Wave unreliable in 2.5.0.M4

[Bruce_Osborne]

@ariela

he next discover you should find it again

Only if it is not removed from the network on the controller.
I think there are currently issues doing this through the binding. Research & troubleshooting are ongoing.

[ariela (Andrea Riela)]

I usually remove the nodes from the controller without the support of the binding itself. But I agree with you, it’s a try approach

[Bruce_Osborne]

Here is the latest conversation I saw on failed nodes.

Remove a ghost Z-Wave Node from HABmin

@chris I haven’t had as much time as I thought… Spent a little too much time figuring out how to use Wireshark to capture a USB trace. But, I now have a trace of the conversation between the Zensys tool and the ZWave stick when performing the following steps in the Zensys tool. Send NOP Send IsFailed Send RemoveFailed I’ve marked and annotated the packets as best I could. Are you familiar with Wireshark, and, if so, could you take a look at the pcap? If not familiar with Wireshar…

[Celaeno1 (Alex)]

@ariela

no issues at all till now.

Troubles will start after network healing…

[Celaeno1 (Alex)]

@rrgeorge

I am using a Aeotec Z-Stick Gen5

Me, too.

[Andrew_Rowe]

There have been some recent talk about the nightly heal and can on occasion (usually when a node is misbehaving) hang the network and in some cases knocking the network completely offline. Here is one thread where Chris comments on the nightly heal

[SOLVED] Z-Wave Network Heal.. when is it needed? does it always need to happen?

OH S1628 on RPi with UZB So, my Z-Wave network works quite well! The only time it’s sluggish is with battery driven devices after a network heal. And that network heal happens every day at 2 AM. I understand the need for network heal as your network grows. But, once your configuration is stable… if you haven’t added any new devices, does network heal really need to happen? If it does sometimes need to happen even on an unchanging network, certainly it doesn’t have to happen every day? It …

Also please check the thread Bruce linked to for info about the remove node in habmin and using zensys tool. Mark and Chris have been working on getting habmin to function better at getting rid of died/ghost nodes

Robert @rrgeorge
if you consider your issue fixed please mark the thread title as [SOLVED] and put a check mark in the thread that helped you fix the issue
thanks

[Celaeno1 (Alex)]

In my case: I’ve checked all nodes with “zensys tool 4.7” and “Z-Wave PC Controller 5.38” by sending a NOP to all nodes. All were responding. None is failed. And it worked for 10 months without any problems. But since I made update to Snapshot 1731 and after first network heal, the troubles began.

[rrgeorge (Robert George)]

@Andrew_Rowe

There have been some recent talk about the nightly heal and can on occasion (usually when a node is misbehaving) hang the network and in some cases knocking the network completely offline.

That is a new and terrible bug. This was never the case before M3.

@Andrew_Rowe

Robert @rrgeorge
if you consider your issue fixed please mark the thread title as [SOLVED] and put a check mark in the thread that helped you fix the issue

I do not, and I will not know for certain for at least 24 hours.

[Bruce_Osborne]

@rrgeorge

This was never the case before M3.

I know @5iver had some issues related to healing a while ago, before M3 IIRC.

[5iver (Scott Rushworth)]

I reported the same/similar before 2.5M2 as something that should be considered a blocker…

Preparation for 2.5M2

The 2.5M2 release has been held up for several reasons. The main one has been the actual ability to build the release, but this has just been resolved (). However, there’s still the question of whether 2.5M2 is ready to be released. There have been many changes since 2.5M1, so I thought it would be good timing to get a post going with a live list of the current major issues that the testers in the community feel should be addressed before the release, as well as a list of new feat…

[Andrew_Rowe]

@rrgeorge

I will not know for certain for at least 24 hours

thank you for that and let us know. Do you already have you logs set to debug?

if you need to know how check here then

ZWave - Bindings

[rrgeorge (Robert George)]

Thank you. When I had discovered it was broken for me in M3, I tried unsuccessfully to find if someone had a similar issue, but didn’t have time to thoroughly look into it. I have no idea why, but I opted to roll back to M1 instead of M2, so I was unaware if the issue affected M2. So all I knew was the issue existed in M3, but not M1.

[rrgeorge (Robert George)]

@Andrew_Rowe

Do you already have you logs set to debug?

I do now… Thank you for the reminder.

[ariela (Andrea Riela)]

Sorry guys,

I’m not sure to understand what M1-2-3-4 means … I have 2.5.0~S1733-1 (Build #1733) on openhabian and I can say this bug is not visible (at the moment).

No issues so far with zwave

[ariela (Andrea Riela)]

I have the same USB key … and healing at 2 AM … updated yesterday so I’ve already passed this point

[Bruce_Osborne]

@ariela

I’m not sure to understand what M1-2-3-4 means

There are current release versions of OpenHAB.

The stable release, normally released every 6 months, is currently 2.4 released late last year.

The Testing releases, also known ad Milestone releases are released every month. 2.5M4 or 2,5 Milestone 4 is the current version.

The Unstable, or Snapshot releases are built & released every night and are only designed for developers to test all pieces working together. Snapshot releases are not expected to totally work or be stable.

[Andrew_Rowe]

OK folks… before we all grab our pitchforks and start calling this a bug… this is common traits of a failed node. Sometimes when things are working good for a long time and we upgrade and things suddenly break, it is easy to blame the upgrade itself, when in fact, it is a low battery, node slightly out of range or whatever edge case. In a system with a lot of nodes, it could have gone unnoticed previously.

@rrgeorge

This was never the case before M3.

[Celaeno1 (Alex)]

I have not finished my investigations because of time constraints. I’ll post the results here as soon as I find the exact reason.

[Celaeno1 (Alex)]

@5iver

I reported the same/similar before 2.5M2 as something that should be considered a blocker…

The issues (#1195, #1178) you reported on Github are still open.
If it turns out that they still exist in M2, M3, M4 and snapshots, why has not it been resolved so far, or why was it decided to publish the milestones anyway?

[5iver (Scott Rushworth)]

@Celaeno1

The issues (#1195, #1178) you reported on Github are still open .

I did not report the first, and it was a known issue. The second one was mine. My workaround was to disable the daily network heal and restarting OH. I can still heal individual devices, if needed.

@Celaeno1

If it turns out that they still exist in M2, M3, M4 and snapshots, why has not it been resolved so far

It’s a rare issue, possibly related to large networks (>120 devices). Chris is extremely busy, and with all the changes this year, the IDE is not what it was, especially when it comes to debugging.

@Celaeno1

why was it decided to publish the milestones anyway?

I’m not the right person to ask, but the 2.5M2 preparation topic may shed some light on that.