No, there’s more to it than that.
Once the binding identifies the device, it queries the device for its command class versions, configuration parameters, associations, etc. This can sometimes involve quite a bit of back and forth communication between the binding and the device. For some battery devices, it’s not uncommon to have to wake them up multiple times before initialization completes. If initialization is not complete, a binding restart will cause this process to start over (I saw multiple binding restarts in your log). You can tell if initialization compete for a node by the existence of a file in
network_XXXXXXXX__nodeNN.xml, where NN is the node number.