Closed ChristianMayer closed 3 years ago
Hi The node’s goal is to mantain states. have you set the node, to retain the states after reboot?The option is in the config window.
Yes, this is the full config of one of the nodes where I can see deleting:
Please be sure that the node-red user has permission to write to the filesystem. The folder where the node stores the states, is this: .node-red/booleanlogicultimatepersist Can you check that, please?
Please, unzip the content of the attachment into the .node-red/node_modules/node-red-contrib-boolean-logic-ultimate/boolean-logic-ultimate folder and restart nodered. This will output an error everytime the boolean logic node is unable to write to the filesystem. Then, please paste here the error. Thanks.
Hey @ChristianMayer please let me know. If you run nodered behind redmatic, homeassistant etc... you should assure the write access to the .node-red folder.
That directory seems to work fine, files are there, modification time looks good:
I'm running the official Docker image nodered/node-red:latest
Should I still try the ZIP file?
Hi Christian Nope. If you can open one of these files and tell me the content, it will be helpful. Whenever you deploy, are these files wiped out?
@ChristianMayer Hello Christian have you solved the issue?
@ChristianMayer Hi, the persistent states file is deleted only whenever you open the property window of boolean-logic-ultimate (and only the file belonging to that node). Otherwise they'll never been deleted.
Hi Giovane,
sorry for answering late but I was busy on the one hand and wanted to understand the behavior on the other.
Currently it's behaving correctly, i.e. it's solved. But the path to that is strange, so I'm not sure whether that is really solved:
I have detected that in a different flow I had a problem with the topics, so there was a boolean node, listening for two topics although it was fed with more than that due to a setup mistake from me. But that flow is independent from the flow that I was closely monitoring and that was the base for this issue report. Once I resolved the mistake on the other flow (without touching anything on the monitored flow) the deletion of the persistent states went here away as well. What's even more strange: adding a 2-topic bool with three inject nodes and thus creating such a mistake on purpose again doesn't trigger the observed behavior.
When this description gives you a hint of what to check that's great. If it doesn't I'm also fine with closing this topic in the hope that it's no issue anymore (and when it's coming back I'll report back)
Hi Chris That's very unusual, but i saw a think like that in another my node (KNX-Ultimate) of one user. I struggled to try to help the user, until it sent me their flow. The user had logged to node-red from 2 different browsers, making the bad decision to click "OK" in the "would you like to merge the changes?" popup window of one of the browsers. The result? A mess in the json configuration. I had to manually change all node's IDs in the config file of that user. Another time, i saw a strange things due to a "devil char" in the config Json. You should be fine now. If not, please don't hesitate to contact me again.
Please bear in mind, that each time you enter the boolean logic's ultimate config window, the persistent file of this particular node is automatically deleted.
As I'm currently creating many new flows I have to deploy regularly. But each deploy is deleting my persistent states, which doesn't make sense here.
Is it possible to prevent prevent that?