Regarding Node 30 config via Habmin - not sure what is correct TBH. Here’s some screen shots…
Node30 conf.pdf (145.5 KB)
As there is only one association group (lifeline) defined for this device, I’m not sure what would cause the double reporting. And, the config parameters look like they wouldn’t cause such behavior. I’d suggest you try the following:
- exclude device
- perform factory reset
- include device
Node 63 is showing timeouts. There’s not much information in the log to determine what was happening with node 62.
@mhilbush just to confirm, when you say exclude you mean press and hold, flashing yellow on the z-stick to take the module off the network completely, then reset the module and delete from OpenHAB. Finally re-add (press for blue on z-stick) and re-add on OpenHAB, updating the config accordingly. I.e. not just delete and re-add via OpenHAB 
I usually use HABmin to do node inclusion/exclusion, so I’m not sure about the process if using the zstick directly.
That is the currently correct and recommended way when using openHAB. You can also use Paper UI.
But effectively that’s the same process right, just controlled from HABmin or PaperUI - as shown at https://www.cd-jackson.com/index.php/openhab/habmin/10-habmin-zwave-binding-initialisation? Basically using the UI to put the z-stick into inclusion/exclusion mode rather than the button on the stick?
I can do that for nearby modules, but some of them are a bit further away, so doing it from the stick works better for me. Any risks or issues doing it that way?
Yes, secure inclusion only works through the binding.
1 Like
So I presume secure inclusion simply minimizes external threats to the z-wave network or are there other benefits?
Due to the spread of my house most of the modules are probably out of direct range of the z-stick, so it’s easier to walk over, include/exclude, then plug the stick back in.
I guess I could set up WiFi on the pi and move the whole thing closer to the various consumer units, if secure inclusion is a must?
Communications between controller and your devices are encrypted.
Should be possible, yes.
So to exclude via HABmin - do I select the thing and use the Tools menu (top right) to select “Remove device from controller” to enter exclude mode on the z-stick? Then triple click the switch on the module?
Exactly.
Also note that unplugging/plugging a zstick (at least in Linux can cause the USB device to change (e.g. /dev/ttyACM0 to /dev/ttyACM1).
2 Likes
I tend to power down, unplug the stick to include/exclude, then plug it back into the same USB port and re-boot for that reason @mhilbush. Slow old process but seems to have worked for the last few years (I think )
So, I selected to remove node30 and the module flashed to say excluded as I would expect. Also OpenHAB told me the thing was not responding. I deleted the thing and did a factory reset on the module before re-adding it, now as node 78. Reconfigured the thing for the new node and all looks good…
But now I see that node 30 has re-appeared in the inbox. I guess the exclude did not succeed? How do I remove it now that the module has been reset and re-added as node 78?
I believe the process @chris recommends is to discover the Thing, mark it as Failed, Excklude the Thing, and then delete the Thing?
Not sure though. I have used Zensys Tools to delete from the controller.
Yes, this should (or could) work. Restart the binding before doing this - that will hopefully cause the binding to send the NOP command which seems to be what’s needed prior sending the “Remove failed node” command.
If it doesn’t work, then you’re probably stuck with the Zensys tool…
1 Like
That’s what I use. Works every time.
Marking as failed, excluding and deleting does not seem to remove the old node30, even after a reboot. Just following https://aeotec.freshdesk.com/support/solutions/articles/6000226205-z-wave-command-class-configuration-tool-download- to install the Zensys tool… see if I can work that one out
1 Like
When using the Zensys tool, I follow the procedure described in this post.