The bridge comes up properly and autodiscovers the node 2 while the second line fails, because the parameter zwave_nodeid is not seen in ZWaveThingHandler.initialize(), resulting in the following errorlog-message:
[ding.zwave.handler.ZWaveThingHandler] - NodeID is not set in zwave:device:controller:mynode2
I must admit, that I am not sure, if the the configuration syntax for the Thing is correct. Therefore I tried alternatively the following Thing definition without success:
if coming from a conf/things/xxx.things-File. The following snippet is from the intitialze() method of ZWaveThingHandler which outputs the above mentioned error:
String nodeParm = this.getThing().getProperties().get(ZWaveBindingConstants.PROPERTY_NODEID);
if (nodeParm == null) {
logger.error("NodeID is not set in {}", this.getThing().getUID());
return;
}
If those parameters are provided from the database (which is the case if the Thing is added with PaperUI) everything works fine. Therefore I conclude, that this could be a runtime problem.
All config files from above seem to comply with the xtext-definition for Things, found in:
Yes, as per the issue linked directly above, manual thing configuration has been implemented, and is available in the development branch of the binding (ie not the main branch) at this time.
The first few messages provide the instructions. Just be aware that it is a large change from the current binding and you’ll need to reconfigure everything. I guess this isn’t a problem if you’re planning on changing the configuration anyway…