It does take effect, and it doesn’t result in any device leaving from what I can tell.
In the log I can see that the Node 20 is still pinged but it always says Node not awake. So how do I remove it from the network?
I can only repeat what I said earlier on how to exclude devices - I’m not sure what else I can suggest as that’s the standard way to remove devices.
I tried again and got the same result. Node 20 is still pinged in the log and the device is still in the list of things in HABmin. Does these log entries tell you anything about what might be wrong?
2017-04-27 21:25:18.049 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 459: Transaction Start type RemoveNodeFromNetwork
2017-04-27 21:25:18.050 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2017-04-27 21:25:18.051 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 459: [WAIT_REQUEST] requiresResponse=true callback: 107
2017-04-27 21:25:18.051 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2017-04-27 21:25:18.053 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2017-04-27 21:25:18.053 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: expected cmd class: null
2017-04-27 21:25:18.054 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start
2017-04-27 21:25:18.056 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: expected cmd: null
2017-04-27 21:25:18.059 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage Transactions outstanding: 1
2017-04-27 21:25:18.061 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Start transaction timer to Thu Apr 27 21:25:23 CEST 2017 - 5000ms
2017-04-27 21:25:18.063 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage lastTransaction: TID 459: [WAIT_REQUEST] requiresResponse=true callback: 107
2017-04-27 21:25:18.065 [DEBUG] [nal.protocol.ZWaveTransactionManager] - STOP transaction timer
2017-04-27 21:25:18.065 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction lastTransaction outstanding...
2017-04-27 21:25:18.067 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Start transaction timer to Thu Apr 27 21:25:23 CEST 2017 - 4994ms
2017-04-27 21:25:18.069 [DEBUG] [nal.protocol.ZWaveTransactionManager] - STOP transaction timer
2017-04-27 21:25:18.069 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave controller end exclusion
2017-04-27 21:25:18.071 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Start transaction timer to Thu Apr 27 21:25:23 CEST 2017 - 4991ms
2017-04-27 21:25:23.062 [DEBUG] [sactionManager$ZWaveTransactionTimer] - XXXXXXXXX Timeout.......... 1 outstanding transactions
2017-04-27 21:25:23.063 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 255: TID 459: Timeout at state WAIT_REQUEST. 3 retries remaining.
2017-04-27 21:25:23.066 [DEBUG] [sactionManager$ZWaveTransactionTimer] - TID 459: Transaction is current transaction, so clearing!!!!!
2017-04-27 21:25:23.067 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 459: Transaction CANCELLED
2017-04-27 21:25:23.069 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2017-04-27 21:25:23.070 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: notifyTransactionResponse TID:459 CANCELLED
2017-04-27 21:25:23.084 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at startHello again. Now I finally got the damed device recognised by openHAB. I had to take out the batteries for 10 minutes or so and add it to the network again. Though now I have the good old Node 20 still there, but a new Node 31 showed up and got identified as a ZP3102 Motion/Temperature sensor. So now I have the Node 22 Unknown and Online. What do I do with that one? Set it as failed?
I have the same thing with an Aeotech Motion sensor that generated two nodes. One identified and the other Unknown.
I just bought one of these Vision Pir´s (with temperature), model ZP3102-5.
I had at hell including it. Afterwards I had at hell removing it again, to try again. After at few time I did a final attempt.
The first two times I placed the Pir aproc 50cm from the controller.
This last Try, I placed it aproc 3-4cm from the controller. The Pir was included, but as an Unknown device. I followed the decription of what to do in this case. Opened the case, let it wake up a coupple of times… And the, I´ll of a sudden, everything go included. The Unknow Node changed to Vision Pir, and even association worked.
Bottom line, I guess this device if highly sensitive of beeing closed enough to your controller. My controller is the UZB1 connected to my Rpi3.
But… It seems like the database has not beeing updated. My Pir is having firmware 8.2. According to the printed manual I have, there are 4 Parameter options, but OpenHab doesn´t give me the 4. option which is manually calibrate the temperature sensor. Maybe @chris needs to look at this.
I can´t find this manual online anywhere, so I wonder if this is w a new one.
I also had huge problems to include my second ZP3102-5… I finally managed to include it to my ZWave Controller with High Power Inclusion (ZMEEUZB1) by covering the ZP3102 and the Controller within silver foil to reduce as much as possible external signals. 
Not relly sure if the silver foil really did the trick but it worked.