0.2.83: "subscribe" msg.interval & msg.payload have no effect

[nrok-hpotsirhc]

example.json.zip

If have you once configured the opcuaClient node via UI with action "SUBSCRIBE" you can no more change the interval using msg.payload or msg.interval.

The subscription itself is not affected:
means, for an object like:

msg.action = "subscribe";
//msg.payload = "101"; //min. allowed sample Rate 101ms; interval overwrites payload 
msg.interval = "101"; //Stringified number should work as well; min. 101ms
msg.queueSize = 1; //default in Code is 10;
msg.topic = "ns=5;s=MyLevel;datatype=Double";

From the above object the parameters payload, interval and queueSize have no effect once the opcuaClient was configured via UI.

By the way "unsubscribe" does not work in the same format like "subscribe". Otherwise you get an quiet undefined error.

subscribe = "ns=5;s=MyLevel;datatype=Double";
unsubscribe = "ns=5;s=MyLevel";

example flow attached. rename it to example.json. The server is an online public server. Deploying the flow should instantly work for you.

best regards,
Chris

[mikakaraila]

Ack, I was using Number to check it, changed to parseInt(). Fixed.