2.5.3 Z-wave - thing receives a command, mostly does it, then goes offline

[chris (Chris Jackson)]

@psyciknz

But isn’t that when it should run through other devices?

Maybe - I have no information about your network. How many devices there are, if they are mains, where they are located etc so I’m just offering ideas.

@psyciknz

And noThing I do with placing smart switches within a few meters changes its routing.

Probably this is correct since routing is generally pretty static, however you probably can’t actually tell this
since there is nothing to tell you the routing (or maybe you have a sniffer?).

@psyciknz

Yes there are walls and even a floor between these controller and switch

What are they made of?

[psyciknz]

@chris

@psyciknz

But isn’t that when it should run through other devices?

Maybe - I have no information about your network. How many devices there are, if they are mains, where they are located etc so I’m just offering ideas.

I think 16 devices. All mains.

All mostly at the controller end of the house, I have started putting devices at the out reaches.

@chris

@psyciknz

And nothing I do with placing smart switches within a few meters changes its routing.

Probably this is correct since routing is generally pretty static, however you probably can’t actually tell this
since there is nothing to tell you the routing (or maybe you have a sniffer?).

No sniffer just the si labs pc controller. Can that tell me routing? I know it can set routes, but the doco is a little sparse on how to do this, and what it should look like.

@chris

@psyciknz

Yes there are walls and even a floor between these controller and switch

What are they made of?

Not brick, Just timber, dry wall ( I think that’s what you call gib board in the us)

I’d posted this similar topic with a node made and floor plan: Zwave node - weird neighbours

Node 19 is on the 2nd floor, Probably close to the node 7 which is in the little room at the bottom of the floor plan.

Generally the zwave has been good, but adding this last node has caused me no end of problems. It was generally working, and responding, but has since stopped.

[psyciknz]

So things kind of stablised. But there were a couple of nodes that would never move off ping or request_nif. So I let it do a heal over night. Most have come back, one was being annoying, so I’ve moved it 1m and it’s now got a signal. But again I’m left with a couple of devices that seem to work, but they are not completing their initialisation.

2020-07-07 07:44:15.639 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 8: Application Command Request (ALIVE:DONE)
2020-07-07 07:44:19.478 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 10: Application Command Request (ALIVE:DONE)
2020-07-07 07:44:20.791 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 13: Application Command Request (ALIVE:UPDATE_NEIGHBORS)
2020-07-07 07:44:33.253 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Application Command Request (ALIVE:DELETE_SUC_ROUTES)
2020-07-07 07:44:33.629 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Application Command Request (ALIVE:DELETE_SUC_ROUTES)
2020-07-07 07:44:33.988 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Application Command Request (ALIVE:DELETE_SUC_ROUTES)
2020-07-07 07:44:34.076 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Application Command Request (ALIVE:DELETE_SUC_ROUTES)
2020-07-07 07:44:34.545 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Application Command Request (ALIVE:DELETE_SUC_ROUTES)
2020-07-07 07:44:35.473 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
2020-07-07 07:44:38.312 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 5: Application Command Request (ALIVE:DONE)
2020-07-07 07:44:38.385 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 5: Application Command Request (ALIVE:DONE)
2020-07-07 07:44:40.553 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 8: Application Command Request (ALIVE:DONE)
2020-07-07 07:44:41.409 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
2020-07-07 07:44:47.478 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 10: Application Command Request (ALIVE:DONE)
2020-07-07 07:44:47.909 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 3: Application Command Request (ALIVE:DONE)
2020-07-07 07:44:48.110 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
2020-07-07 07:44:50.789 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 13: Application Command Request (ALIVE:UPDATE_NEIGHBORS)

These did a heal at 3am, and it’s currently 7am. I know form previous experience, that these will never resolve. Is there anything I can do to help them along? Does sending commands to these devices (on, off, on, off) help it carry on the process?
@chris

[Bruce_Osborne]

Sometimes deleting a Thing from OH (NOT excluding from the network) and then rediscovering, keeping it awake helps.

[psyciknz]

I’ve never had good luck removing and re-adding a device…

[Bruce_Osborne]

I believe the OH threads get hung & orphaned after a while. What else do you suggest?

[psyciknz]

I have no idea, that’s why I’m asking. I’ve been battling some nodes for a number of weeks now. And have a number of threads about it.

[psyciknz]

I did try removing one of the nodes that was sitting in update neighbours. Deleted it in paper ui. Waited a minute or so, then scanned zwave a re-added. Still seems to be in the same state.

Have I done that correctly? Or should I have deleted, and fully restarted openhab before trying to re-add?

Its definitely online, as I can see its power reports coming in every minute or so.