🎉 Node-RED 1.2.2 released

News
21

With free new installation, if i install node-red-contrib-s7 for first it work, and all other modules installed before have this issue.
In this case i have installed first node-red-dashboard and all other modules make this issue.

I will use v12.19.0 for now...

Thanks

22

If you still have the 15 version... can you share the package.json it creates in that dir ?
and ideally the package-lock.json

23

package.json

{
    "name": "node-red-project",
    "description": "A Node-RED Project",
    "version": "0.0.1",
    "private": true,
    "dependencies": {
        "node-red-contrib-influxdb": "~0.4.1",
        "node-red-contrib-s7": "~2.2.1",
        "node-red-dashboard": "\"~\"2.23.4"
    }
}

First package installed node-red-dashboard with v15, all other with v12.
then
reinstalled v15 then, from this moment I can't install any packages with v15

24

yeah - edit that package.json to have just "~2.23.4" instead of those extra slashes and quotes

25

package.json

{
    "name": "node-red-project",
    "description": "A Node-RED Project",
    "version": "0.0.1",
    "private": true,
    "dependencies": {
        "node-red-contrib-influxdb": "~0.4.1",
        "node-red-contrib-s7": "~2.2.1",
        "node-red-contrib-s7comm": "\"~\"1.1.6",
        "node-red-dashboard": "~2.23.4"
    }
}

to try i use v15 now.

it work for the first package installed node-red-contrib-s7comm installed correctly, but in package.json it will add always "\"~\ before version. i have tried to install another package and will not work.

Ok, found problem... Thanks, i will continue use v12 for now ... or I will fix the file every time before installing a package.

Thanks a lot

26

Side note, I did notice that upgrading to 1.2.2 broke the restart persistence on the node-red-contrib-stoptimer-varidelay node (at least for me). Rolling back to 1.1.3 fixed it. I run my instances in docker containers, in case it matters.

I submitted an issue to the author, but thought I would mention it here as it certainly seems 1.2.x related since the only thing I did to make it work again was roll back to 1.1.3.

EDIT: Put the container back to 1.2.2 and confirmed that the node does not continue after restart, as mentioned. Rolled back to 1.1.3 and it is working as expected again after a NR restart. Definitely seems NR 1.2.x related...

27

I've faced this issue multiple times;

Restarting node red and all of my flows have disappeared.

It's quite tragic after you've put in a couple of hours of work.

Hope there's a fix for it

28

@liiontamer without more information its going to be hard to help.

How are you running Node-RED? How do you upgrade? What does the startup log say about the location of your flows file?

29

Hi Nick,

Thanks for your response.

Running it on my laptop - accessing via localhost. This isn't related to an upgrade however just in general, sometimes if I restart the instance; I login to find my flows missing. It's happened 3 or 4 times in the past 2 months since I've started using Node-RED again. Startup log doesn't mention anything right now but everything's working at the moment.

I want to use Node-RED in commercial environments but not sure if my clients may restart their systems and find that the flows are gone

30

That certainly should not happen unless something has changed on your system. Does it recover by itself or do you have to restore the flows from your backup?

As Nick asked, start node-red in a terminal and post the log here as that may give us a clue. When pasting the text in then use the </> button at the top of the forum text entry window and paste the log in.

31

Actually, since this isn't about an upgrade or about the new release of node-red it would be better to start a new thread for your issue. Please post the additional information there. Thanks.

32

By default it uses the hostname as part of the flow file name. If that changes then it will pick up a different flow.

You can fix the flow file name in your settings.js file so it won't be affected.

33

I think that Nick is the only full-time Node-RED (core) developer. Some folk here use it professionally though. The rest of us vary in our day-jobs and, like Batman, inhabit the forum at night :rofl:

1 Like
34

Thanks for your support.

I've just created a new topic "Node-RED Flows Disappearing"

I've also posted the startup log over there

Thanks in advance

35

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.