I have experienced this problem a few times in the last month. Each time my solution has been to restore from snapshot. Yesterday, however, the problem came back just hours after a snapshot restore . So now I realize that this âsolutionâ wonât be working, going forward. I spent many hours searching for someone with a similar problem, but without success.
Setup
Home Assistant (prev. Hassio) running on raspberryPi
None Red running as add-on.
Everything is updated to lastest available versions.
Multiple browsers and operating systems have been tested on client side.
Problem description
Suddenly, when developing in node red, the deploy button cannot be pressed. It is red, but nothing happens when I press it.
This error code appears in the browser console when I press deploy:
TypeError: undefined is not an object (evaluating 'e.id')
These error codes appear when the page is loaded, but Iâm not sure they are connected to this:
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (purify.min.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (gridstack.min.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (gridstack.min.map, line 0)
Some other problems that has occurred roughly at the same time, and may be connected
- Keyboard shortcut stops working (cmd-z brings back the last closed browser window, instead of functioning within node red).
- Some nodes are impossible to select. Nothing happens when I click on them.
Result of troubleshooting so far
When I delete the flows.json-file and start node red, everything works again (but of course without my nodes). My suspicion is therefore that the flow-file is corrupt. However, since the problem comes back time after time after reverting to functioning backup, something is probably causing the corruption.
Way forward
What are my options If I donât find the root cause? I can see these possibilities, but I donât know which is most likely to succeed:
- Uninstall Node red, start a new instance and use the last functioning flow file.
- Uninstall Node red, start a new instance and import the flows one by one so that the flow file is created from scratch.
- Do not uninstall node red, but remove the flow-file and import the flows one by one so that the flow file is created from scratch.
Any help to find the root cause would be extremely appreciated! If I donât find it I would be thankful for your recommendations of what path to take of the ones listed under âWay forwardâ, above.