Sorry - it needs to be a debug log. Check out the zwave wiki (toward the bottom of the page I think) - it describes how to configure for debug logging.
It seems like you’ve done most of the things I’d suggest - the only thing you don’t say is how far away from the controller the device is? I would get it a meter or two away (if it’s not already) while you’re testing.
I’m going to check if it’s working tonight - but I’ve noticed that in habmin the node now has info but is grey. Is this more like what you would expect?
I had this type of issue previously and it turned out I was just being impatient and needed to wait for the device to wakeup on it’s own and transmit data. Usually the information is then populated in around 24 hours. Have a look at the Status tab to see when data was last transmitted.
The system should support using routing slaves - no problem at all.
The point to note though is that in order to configure a device, it first needs to be configured in direct range of the controller - this is at least true for battery devices since the wakeup notification that battery devices send is disabled by default, or, it is set to braodcast in some devices and broadcast frames are not routed. Mains devices are likely to be more tollerant, but a battery device really needs to be included into the network, and configured in direct range of the controller.
A grey dot in HABmin means it’s not finished initialisation
