Yes, but not that will be applicable here. There is a totally new standard now, but that will not work at all with the current binding, or with any other current software on the market.
This cannot have changed.
I’m not really sure why you think that? From what I saw in the logs earlier, the controller was being put into inclusion mode, and the controller was responding to say it was going into inclusion mode.
Possible.
It could also be some other systematic issue to do with the way this is being done. It’s strange that the controller only seems to ever allow one device to join, so it’s either something to do with the way that devices are being included, or possibly the controller isn’t working (although this is a very strange failure mode!).
Could it be I’m adding the USB ZWave Serial Controller wrong?
When running OpenHAB on a mac should I set the controller’s Serial Port as:
cu.usbmodem?
or
tty.usbmodem?
Not really - the binding is communicating with it just fine. As per the log above - the binding was putting the controller into inclusion mode, this was being acknowledged, but no devices were found. The inclusion process itself is solely between the controller and the device (once the binding has put it into inclusion mode).
Just looking from here it appears the controller is not always recognizing devices to be included if using our binding but it works with another software package (Domoticz). That is my concern here.
I know they use the latest openzwave for their database. I do not know if that includes the rest of their zwave code too.
Could it be related to the Z-WAVE binding’s installation process?
When I first install the binding under Addons, the spinning wheel doesn’t change to Uninstall untill I refresh the webpage. Can that somehow be related?
I’m confused by what could have made the controller stop discovering the 2+2 switchbox and suddenly start discovering the 4lights. If you remember, initially the controller’s behavior was the opposite – it didn’t discover the 4lights and it did discover the 2+2.
The list of devices is retrieved immediately - it’s nearly the first thing that is retrieved and the information comes directly from the controller. Full information may take longer as it needs to be downloaded from the device, but the addition of the inbox device mentioned here comes from the first information.
Sure - but the point I’m making is that the inbox addition is added when the binding starts and it gets the list of nodes from the controller. This happens as soon as the binding starts and doesn’t take more time.
I’m assuming the binding is s starting if it’s adding a device - unless the device is just stuck in the inbox which should not be the case as this is a fresh install.
Problem found and solved!
OpenHAB didn’t discover the switchboxes after I Hard Reset my USB controller, because, apparently, I didn’t follow the correct Node Exclusion procedure prior to the hard reset.
I went to the store today to check if the USB controller was faulty, and we found that once we performed a proper Node Exclusion with another standalone Philio ZWave controller hub we were able to discover both Switchboxes using my USB controller and OpenHAB.
So… I’m happy to close this topic and change it to SOLVED
Many thanks for all your support and help @chris@Bruce_Osborne. I really appreciate it