There is already an issue reported on Github. Just wanted to prove that I have the same problem and that manual healing (by waking up the node) works. Maybe some people can discover something in the logfile that may lead to the solution.
3 Likes
Guys,
may I ask you to understand better the issue? I mean, in my setup (last snapshot, 2.5.0~S1733-1 (Build #1733)) I see all my zwave devices successfully healed at 2.30 AM as expected. And it seems everythingâs working correctly.
What is the symptom I need to look at?
thanks again for your patience
Andrea
Do you have âbattery poweredâ and ânon listeningâ nodes? You can see it in HABmin, select a node â properties (down to the bottom), where could see: last heal, routing, beaming, frequently listening, listening, last wake up, neighbors. If your nodes are neither âfrequently listeningâ nor âlisteningâ then you could have also this issue.
This doesnât look like the issue I reported in #1195, and with additional documentation in #1174.
The issue I reported in #1195 has a very specific log file signature as shown in this log file snippet. I donât see that signature in the log file you posted.
Ok, thanks. 
It seems to be different, but the result is the same. The nodes werenât healed.
Iâve never had this before, but after update from 1486 (02 Jan 2019) to 1731 (20 October 2019).
I have 5 Danfoss Thermostat valves ⊠battery powered, not listening and even not frequent listening. But those valves are working correctly, I mean no errors/issues in my logs. Last heal is always as expected
What is the issue?
Then you donât have any.
Did you make an update from xxxx to 1733 or an installation from scratch?
Last updates:
- from 1657 yo 1712
- from 1712 to 1731
- from 1731 to 1733
Then I donât know, why I have the problem since updating from 1486 to 1731. Maybe because 1486 was before reintegrating ESH into OH-Core and 1731 is after reintegrating ESH into OH-Core? Maybe the step is too big?
1 Like
I remember I had some issues upgrading from 1502 to 1524:
But a soft reset did the trick.
On the other hand, sometimes in the past I had issues with my Danfoss valves ⊠
unfortunately.
Now itâs quite stable. Do you have a chance to rollback, backup, install from scratch the 1733, then recover the backup?
1 Like
Iâve read your topic now.
I also get REQUEST_NIF (from time to time).
I also did a soft reset, and I also removed things from PaperUI and readded them. But I gave them the same thingID. Did you take a different thingID?
better to remove from PaperUI and verify that also the file in zwave folder is removed.
Then rediscovering the thing, youâll have a new thingID, if I well remember.
Consider that was my first approach ⊠then in some cases I did also a hard reset (removing the thing from openHAB and also from the USB key, then including again)
Yes, thatâs right, but Iâve overwrote it with the old thingID, because I didnât want to change my .items file.
item file? you are not using PaperUI to link items to thing?
anyway I would try with a new thingID and see what happens ⊠you did a very long jump from my perspective
1 Like
No, I use .items file.
Ok. Iâm going to try it, but not today. Iâll keep you informed.
1 Like
this is another difference between our implementations ⊠I use items only with Binding like HTTP ⊠with Zwave I use generic items, then I link the items to thing in PaperUI
I link ALL items via .items file.
Here is my neighbor map, according to last heal (see above):
It is very strange!
node1=controller, node2=repeater
node3 und node7 are downstairs.
GREEN = sees neighbor
RED = DOES NOT see neighbor
node 8,9,10 are the âproblem nodesâ!
Did you delete the OH Things (except the controller) and re-add? They will keep the same IDs but get new binding information.
1 Like