validation failure if more than one data source about node-red-contrib-mindconnect HOT 4 CLOSED

@ToSa27

Hi

I am having a bit of trouble reproducing this.

Config:

Node-RED Node:

could you include

msg._forceGetConfig=true;

in your message to force the node to refresh the configuration?

I also looked into the code and it enumerates accross all data sources.

    model.dataSources.forEach(function(elem) {
        elem.dataPoints.forEach(function(elem2) {
            dataPointIdArray.push(elem2.id);
            valueArray.push(elem2.type.toString());
        });
    });

Btw, this seems to work too (just 2nd datasource...)

from node-red-contrib-mindconnect.

@ToSa27 One more question :) Are you by any chance using TIMESTAMP or BIG_STRING data points in your configuration?

from node-red-contrib-mindconnect.

@sn0wcat Adding msg._forceGetConfig=true; fixed it. The second data source was definitely created after the NodeRed flow was setup so this makes some sense but even after quite some time it still failed. Without forcing it, will the config ever be pulled again e.g. on a given frequency or is there a way to manually trigger a one-time refresh (other than removing and re-adding the node)?
I'm not using TIMESTAMP or BIG_STRING.

from node-red-contrib-mindconnect.

@ToSa27 the node pulls the data source once from the mindsphere and never again unless you force it. you should remove the msg._forceGetConfig now, to minimize the load on the system.

I am planning to change the node configuration a bit now that the agents actually can get list of assets from Mindsphere (we will provide a dialog where you can select the assets and the agent will automatically create data source config and mappings for them). For that I have to touch that code anyhow, I will see if I can do here a bit more ...

from node-red-contrib-mindconnect.