RED.nodes.getNode fails to find node

General
2

Hi Chris,

I'm not very sure why this happens, but I 'think' the OccupancyTrigger node is at this stage not available entirely in the runtime yet. But I might be wrong!

I had a question recently, that was a bit similar to yours. At the end I found that I was calling the RED.nodes.getNode a bit too soon, because the node was at the particular moment not fully loaded yet.

Can't you workaround it like this:

node.schedule.setupStatusReporting(this);

and this:

node.setNodeActiveStatus = function(nodeToSet) {
    nodeToSet.status({fill: "green", shape: "dot", text: "active"});
};

Good luck with it!
Bart