POPE012501: zwave database entry isn’t complete. So I did try to include. A new node 9 added to my things. More isn’t possible. No xml-file was written. Log is showing an error: Specific device class 10 not found. I’m not sure but I gues the commentet lines are not correct.
[rialmessage.IdentifyNodeMessageClass] - NODE 9: ProtocolInfo
[rialmessage.IdentifyNodeMessageClass] - NODE 9: Listening = false
[rialmessage.IdentifyNodeMessageClass] - NODE 9: Routing = true
[rialmessage.IdentifyNodeMessageClass] - NODE 9: Beaming = true <— battery powered?
[rialmessage.IdentifyNodeMessageClass] - NODE 9: Version = 4
[rialmessage.IdentifyNodeMessageClass] - NODE 9: FLIRS = true
[rialmessage.IdentifyNodeMessageClass] - NODE 9: Security = false <— secured communication shall be possible
[rialmessage.IdentifyNodeMessageClass] - NODE 9: Max Baud = 40000
[rialmessage.IdentifyNodeMessageClass] - NODE 9: Basic = Routing Slave
[rialmessage.IdentifyNodeMessageClass] - NODE 9: Generic = Entry Control
[rialmessage.IdentifyNodeMessageClass] - NODE 9: Specific device class 10 not found
Thanks. I’ll take a look at this tomorrow hopefully - from the quick look I’ve had I think I know the issue and it shouldn’t be too hard to resolve.
I’m not sure about the re-inclusion question. This might be normal - it’s not something I’ve tried, but I know it’s possible to get the same device showing up twice, so I suspect it’s the same issue… I’d suggest not to do this ;).
You shouldn’t need to keep excluding and re-including it though - once should be enough…
I did try to include. I did press the button 3 times … nothing was shown… i did press agin 3 times … 2 new nodes was shown . I can’t remove the first one now.
To remove the first one, you can try the following (no guarantees though - especially for battery devices where it’s problematic to get rid of such devices)…
In HABmin, select advanced mode - in the thing config screen, click on a thing, then click on the menu in the top right corner.
Add the node that you want to get rid of as a thing - I assume it’s in your inbox at the moment?
Select the Set device as FAILed, then Remove device from controller.
Delete the thing.
Hopefully this will work, but the problem is that if the controller thinks the device might still be alive, then it won’t allow it to be removed. For battery devices, it can be especially problematic…
Hmm - I guess that since this is a lock controller, it needs the security classes which are not currently supported, so the database update won’t help much - sorry. Hopefully security will be added very soon…
Also, the database needs the configuration parameters adding, so it might be good if you can take a look at this?
Unfortunately that means it won’t currently work even with the database update. I’m hoping to get a test version which includes security available in the coming week or so.
I did notice, you did use the holliday to do something. Thats nice. I can check first in some days. I did kill the board while starting the test with the input. So I’ve to wait until I have a new one.
That’s correct - this is not currently possible right now. It is in the development version, which will hopefully be available for widespread testing very soon, but it will likely be a while before it’s in the master branch.