I am developing a node whose config node establishes a connection with a server. When all nodes are disabled, the config node remains active and establishes a connection.
Would it be possible to add an option during deployment that disables the config node if no node is active so as not to establish a connection?
Thanks for your answers.
So, this is my take on it.
A config node, should be self aware of what dependants it has.
As an example:
my config nodes (ZWave V9 - WIP) has 2 methods....
These are used by the child nodes ->
With this, the config nodes has a state of what it is responsible for.
ideally, one could decide to NOT connect to anything, if it has no active dependants.
The moment a child node calls
registerInterest (as an example)
you can then make a connection to some service, and on the flip side, if
deregisterInterest is called, and you remove the state of the last child node, disconnect the service.
I use something similar to show the connection status with my server on each child node. I can consider this idea for my concern but my question is more general (not just for my nodes) would it be smarter to completely disable this node config rather than having to register active child nodes?
The idea may seem stupid but it happens to me during my tests to disable one or more flows and that's where these problems occur.