# Node-red-contrib-persist nodes not working after Node-RED upgrade

**URL:** <https://discourse.nodered.org/t/node-red-contrib-persist-nodes-not-working-after-node-red-upgrade/56279>\
**Category:** General\
**Created:** [8 January 2022 04:52 UTC](https://discourse.nodered.org/t/node-red-contrib-persist-nodes-not-working-after-node-red-upgrade/56279 "2022-01-08T04:52:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tohox](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tohox/32/14536_2.png) [@tohox](https://discourse.nodered.org/u/tohox)\
**Post date:** [8 January 2022 04:52 UTC](https://discourse.nodered.org/t/node-red-contrib-persist-nodes-not-working-after-node-red-upgrade/56279/1 "2022-01-08T04:52:06Z")

</div>

Hi!

After doing an apt-get-update/upgrade on my RPi all persist nodes in my flows are non functionnal and Node-RED generated warnings upon starting:

[warn] [RED.events] Deprecated use of "nodes-started" event from "/home/pi/.node-red/node\_modules/node-red-contrib-persist/persist.js:164:20". Use "flows:started" instead.

I changed both occurences of nodes-started to flows:started in the persist.js file and no longer got the warning upon starting but my persist stores still didn't work so I deleted them and created new a one.

The persist store appears to have been created successfully but when I write to it and try to restore its content I get nothing. No error message either...

Where can I find these files and can I check if they are indeed getting written to?

Any ideas how to fix this short of performing a clean reinstall of Node-RED?

Thanks!

NOTE: _So I found the location of the persist files (home/pi by default duh!...) and they are indeed getting written to so I guess this means the persist IN nodes are working as expected. I can't however get anything out of the persist OUT nodes it seems. I connected a debug node to my persist OUT node and nothing comes out when I press the restore button._

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [8 January 2022 06:00 UTC](https://discourse.nodered.org/t/node-red-contrib-persist-nodes-not-working-after-node-red-upgrade/56279/2 "2022-01-08T06:00:22Z")

</div>

You could use persistent context. It is easily setup in settings.js (see node-red documentation)

Alternatively, post an issue on the GitHub repository: [Issues · DeanCording/node-red-contrib-persist · GitHub](https://github.com/DeanCording/node-red-contrib-persist/issues) - however the author seems to be unresponsive so you may not get anywhere with that.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [9 March 2022 06:00 UTC](https://discourse.nodered.org/t/node-red-contrib-persist-nodes-not-working-after-node-red-upgrade/56279/3 "2022-03-09T06:00:37Z")

</div>

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