Must restart Nod-RED to get some Node value changes to be accepted

[Jon Murphy]

Hoping you can point me in the right direction.  I am not sure if this is a cockpit issue (my error), or a Node-RED issue or a Node issue.

On the Node-Red browser user interface I’ll make a change to the Nest Request Node (node-red-contrib-nest 0.1.8) and flip Streaming from True to False, then click the Node-RED Deploy button and “boom” nothing changes.  The Streaming states False, but the output keeps coming and is viewed in the Debug area (just like if the Streaming was set to True).  In the Streaming = False mode I should only have output when triggered (e.g., with Inject node).  The only way to stop the streaming mode is to restart Node-RED.

Last night I ran into a similar situation with the just downloaded Edimax Smartplug Node (node-red-contrib-smartplug 0.0.5).  When I change the Interval(ms) from the default of 1000 (or any other number) to the new number of 300000 the change does not happen after a Deploy.  Again to get the change to “set” or “take” I must stop & start Node-RED.

Is stopping & starting Node-RED just part of the Deploy process when a change to a value is made?

Details: The Node-RED is running on an Open Energy Monitor <http://openenergymonitor.org/emon/> emonPi box with Jessie Minibian (v 2015-11-12).  emonCMS version low-write 9.3 on 2015.12.30.  Node-RED version: v0.12.5 and Node.js version: v0.12.9.  The Node-RED and node.js were part of Jessie build (or OEM build) and were not added by me.

Thank you!   Jon

[Nicholas O'Leary]

Hi Jon,

no, you should not need to restart node-red when you deploy a new configuration.

I've had a quick look at the nest node and it is a bug with the node - it doesn't have any code in it to tidy up when it gets redeployed. So when you switch from streaming to not-streaming, the streaming code is still happily running sending messages.

The smartplug node does have code to handle the redeploy, so would need to dig deeper to see what's happening with that one .

Nick

--
http://nodered.org
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Julian Knight]

I'm using the smartplug node and I think that it needs a full deploy not just a changed node or changed flows deploy, don't know if that helps.

[Nicholas O'Leary]

Julian - that would certainly be a bug. If the node's configuration has been changed then it should get redeployed no matter which deploy type you've selected. If you can confirm that behaviour then please let me know.

Nick

[Julian Knight]

OK, I'm due to update it, just haven't had any time I'm afraid. I'll try and test again with the latest. As you know there were some early bugs in that code and it needs a patch if using it on older versions of node.js to get promises working.

[Jon Murphy]

JK - When you do update, be aware I stumbled across another odd item.  I was cleaning up my EdiPlug flow (Edimax SmartPlug SP-2101W) and I was deleting all of the flows and nodes on Sheet 2.  Sheet 2 is now blank. I clicked the Node-RED Deploy and the EdiPlug node kept running.  The debug info was something similar to EHOSTUNREACH error (sorry I cannot locate the exact statement in my logs).  So I did a Node-RED stop & start.  And the EHOSTUNREACH error did not go away. In the hamburger menu in the Config Menu and the EdiPlug was a greyed out (i.e., EdiPlug 0).  I deleted it but the errors kept coming.  I ended up having to reboot the Pi box to get rid of the EHOSTUNREACH errors and the EdiPlug node.  I am assuming like the above items, this is not normal.

Is this something I should let the Maintainer / Author know about?  Or? 

Best regards!

Jon

[Julian Knight]

Strange. I did do an update and apart from having to put a reference to bluebird back into the repeating function because I'm running an old version of node.js, I'm not getting any issues at the moment. Though I haven't had that much time to test other than some quick manual and simple flow tests.

Certainly my standard switch flows are working as is controlling from UI. I didn't have to reboot.

Yes, I would report to the author.

[Jochen Scheib]

Hey.

I tried to reproduce your problem with the smartplug node but removing and changing interval worked fine for me. Can you provide more information to reproduce the problem? Which version of the smartplug node you are using?

Thanks.

[Jochen Scheib]

PS: Please use github https://github.com/mapero/node-red-contrib-smartplug/issues to discuss the problem.

Am Samstag, 16. Januar 2016 22:16:18 UTC+1 schrieb Jon Murphy: