Initializing config screen based on new config node

[BartButenaers]

Hi guys (@dceejay, @knolleary),

@dceejay

Also the serial port config node is an example of a select box that you also type into

That is indeed a good alternative to reduce the communication between the browser and the server (compared to my autocomplete solution). Will keep it in mind !

@knolleary

this is one of those questions that doesn't have a quick response and I haven't had the time to give a proper reply

Until a few days I thought that Nick knew everything, and that he could answer on all my questions immediately. However after reading this post, it seems that he even doesn't know 'all' existing frameworks in detail. I am very shock
Just kidding, I don't expect you to answer all my questions after a couple of seconds ...

@knolleary

they select an existing (known-to-the-runtime) config node, but then edit the config node to change its details. The node in the runtime no longer matches what they have in the editor, so the list will not be correct.

That is indeed so true ... That is a big disadvantage of my autocomplete solution. There goes my short moment of glory

@knolleary

The other is to allow the HTTP Admin end point you create to return the information to accept additional query parameters in place of the config node properties.

That would indeed be the best solution. But not sure how to get started with this... Is there perhaps somewhere a node that I could use as an example?

My config node has 3 fields:

As soon as this config node is deployed, it automatically connects (based on the above 3 settings) to the camera and loads information (e.g. profiles) from the IP camera:

function OnVifConfigNode(config) {
   var options = {};
   options.hostname = config.ipaddress;
   options.username = config.username;
   options.password = config.password;

   // Create a new camera instance ('onvif' node), which will automatically connect to the device (to load configuration data)
   this.cam = new onvif.Cam(options);
}

But it is not clear to me:

• where the 'dirty' config node is stored, when I create a new config node or update an existing config node (until that config node is deployed).
• if I can get hold of that dirty config node data somehow in my code.
• and suppose I could get hold of those dirty config node settings, I would have to create a 'new onvif.Cam(dirtyOptions)' every time a config screen (of a related node) is shown. That Cam instance will send N requests to the camera to load all kind of information. I assume that will become slow, so autocomplete will be impossible.