Remove / delete old nodes

[Jon Evans]

I have openHAB 1.7.0 set up on a Mac Mini, with a USB Aeon Z-Stick S2 controller. Over the months I've set up the system, there are quite a few nodes which have stopped responding, and I've ended up having to re-add. I now seem to have a problem which is that sometimes commands don't go through. Looking in HABmin, I see lots of nodes with a yellow icon. See attached screenshot.

I enabled the automated 2am Heal process a few days ago in an attempt to make some progress with this issue.

I've tried all sorts of things to remove the "dead" nodes but can't work out how to do it. No "delete" option ever shows up in HABmin. I've installed HABmin 2 and found the "Delete failed node" item in the Device Tools menu, but that doesn't work either. Here's a sample log:

2015-06-16 14:02:38.668 [DEBUG] [.z.i.config.ZWaveConfiguration:975 ]- NODE 41: Delete node

2015-06-16 14:02:38.669 [DEBUG] [s.RemoveFailedNodeMessageClass:42  ]- NODE 41: Marking node as having failed.

2015-06-16 14:02:38.669 [DEBUG] [o.b.z.i.protocol.SerialMessage:109 ]- NODE 255: Creating empty message of class = RemoveFailedNodeID (0x61), type = Request (0x00)

2015-06-16 14:02:38.669 [DEBUG] [b.z.i.protocol.ZWaveController:667 ]- Enqueueing message. Queue length = 1

2015-06-16 14:02:38.669 [DEBUG] [WaveController$ZWaveSendThread:1258]- Took message from queue for sending. Queue length = 0

2015-06-16 14:02:38.670 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 05 00 61 29 FE 4C 

2015-06-16 14:02:38.670 [DEBUG] [WaveController$ZWaveSendThread:1315]- NODE 255: Sending REQUEST Message = 01 05 00 61 29 FE 4C 

2015-06-16 14:02:38.672 [DEBUG] [eController$ZWaveReceiveThread:1528]- Receive Message = 01 04 01 61 18 83 

2015-06-16 14:02:38.673 [DEBUG] [eController$ZWaveReceiveThread:1452]- Receive queue ADD: Length=1

2015-06-16 14:02:38.673 [DEBUG] [b.z.i.protocol.ZWaveController:1210]- Receive queue TAKE: Length=0

2015-06-16 14:02:38.673 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 04 01 61 18 83 

2015-06-16 14:02:38.673 [DEBUG] [b.z.i.protocol.ZWaveController:1211]- Process Message = 01 04 01 61 18 83 

2015-06-16 14:02:38.673 [DEBUG] [b.z.i.protocol.ZWaveController:190 ]- Message: class = RemoveFailedNodeID (0x61), type = Response (0x01), payload = 18 

2015-06-16 14:02:38.674 [DEBUG] [s.RemoveFailedNodeMessageClass:53  ]- Got RemoveFailedNode response.

2015-06-16 14:02:38.674 [ERROR] [s.RemoveFailedNodeMessageClass:81  ]- NODE 41: Remove failed node not placed on stack due to error 0x18.

2015-06-16 14:02:38.674 [DEBUG] [b.z.i.protocol.ZWaveController:682 ]- Notifying event listeners: ZWaveTransactionCompletedEvent

2015-06-16 14:02:38.674 [DEBUG] [.z.internal.ZWaveActiveBinding:433 ]- ZwaveIncomingEvent

2015-06-16 14:02:38.674 [DEBUG] [WaveController$ZWaveSendThread:1374]- NODE 255: Response processed after 4ms/4978ms.

Does anyone know how to get rid of the dead entries and get my house working well again?

By the way, the main culprit seems to be a Fibaro door sensor (node 41, 42, 43 - it's all the same device). It takes ages to get openHAB to recognise the device and get it configured OK, then if you restart openHAB it seems to never work again. That's why I ended up with 3 devices before I gave up and left it dead.

Cheers,

Jon

[wolffromthenorth]

hi,

 

You could use the zwave tool to delete nodes or use the exclude function in openhab.

 

for exclude --> push exclude in habmin --> triple click the node for exclusion till openhab reacts correct.

then reboot openhab server.

redo this step until your ghostnodes are gone. maybe refreshing the page a few time sin habmin will do no harm.

else use the zwave tool.

 

kind regards

[Jon Evans]

Hi

On Monday, 22 June 2015 10:03:13 UTC+1, wolffromthenorth wrote:

You could use the zwave tool to delete nodes or use the exclude function in openhab.

What is "the zwave tool"? I can't use the exclude function in openhab because these are mostly nodes which are already re-included. For example the front door switch is nodes 41, 42 and 43. Even if I manage to get it to talk to openHAB again, it will only remove node 43.

I'm assuming - perhaps incorrectly? - that the list of nodes is contained within the Aeon Z-Stick, and I somehow need to purge the invalid nodes from there.

Thanks

Jon

[Chris Jackson]

Unfortuntely the zwave stick only allows you to delete nodes when the controller (ie the stick) thinks they are dead! So, unless they are in the controllers 'dead nodes list' the 'delete node' function doesn't work.

Normally, mains powered nodes will go into this list reasonably quickly once they fail - battery devices aren't quick at all, and may neve end up there :(  I don't know of a way to force devices into the list...

Chris

[Christophe Van Vossel]

Search for how to reset the zstick, i posted today a link to download

Op 22-jun.-2015 11:26 schreef "Jon Evans" <evan...@gmail.com>:

--
You received this message because you are subscribed to a topic in the Google Groups "openhab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab/uFBjpg_O0CM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
To view this discussion on the web visit https://groups.google.com/d/msgid/openhab/d1c82da1-e0df-4223-8b7a-2bd748ef771c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Chris Jackson]

Of course, you can reset the stick, that’s easy, but it’s also quite drastic when all you want to do is remove one node :)