Function nodes doing different things with different NR versions

Following on from my other question about updating NR from 3.0.2 to 3.1.5....

I made a lump of code in a function node on the 3.1.5 machine.

In the on start tab I have:

// Code added here will be run once
// whenever the node is started.
context.set("counter", 0)
context.set("rounter_status", "unknown")
context.set("pip_status", "unknown")
context.set("modem_status", "unknown")
context.set("internet_status", "unknown")
node.status({ text: "RESET" })

And if I modify the code/node when I DEPLOY it says RESET.

I export it to a machine with 3.0.2 and that doesn't happen.

Is it a version problem or something else?

(off topic: I just saw the typo in the code I posted. But still... It doesn't seem to be done on the second machine. Right or wrong code.)

The status will only be set once the function has received a msg. use debug nodes to confirm a msg was sent to the function.

I think there is confusion with what/how I explained things.

(and now I'm trying to capture it: it is not playing the game.)

Ok, I'll have to fall on my sword again.

Sorry.

I maybe cried Wolf.

Here is an example of what I see happening WRT the on start tab.

A message was received and the status changed.

I edited some of the code in the node.
I press DEPLOY

Now you see that it is doing the on start code.
Which it didn't seem to be happening before when I asked.

The code - again for clarity:

// Code added here will be run once
// whenever the node is started.
context.set("counter", 0)
context.set("router_status", "unknown")
context.set("pip_status", "unknown")
context.set("modem_status", "unknown")
context.set("internet_status", "unknown")
node.status({ text: "RESET" })

Most importantly the last line.

There are no other messages arriving.
This is a controlled environment.