Hello all, just wondering if anyone is using the ‘Projects’ feature with node red on HA? Since it doesn’t come configured that way I wondered if it is compatible.
Thanks
I have never heard of HA Projects. A quick google search didn’t help me. Do you have a link to the description of what that is?
Oh ok. Well the settings.js if installed as the standard addon will be in the config folder.
\YOURIP\config\node-red\settings.js
Yes that’s it, so does it work when running node-red with HA? The reason I ask is because it offers some nice versioning capabilities. I just don’t want to screw up what I have already written by enabling projects.
I am using it. It’s a git GUI but the built-in functions are still pretty lacking.
For example, there’s no way to use the GUI to revert to a previous commit. You have to use git from the command line in the projects folder.
It also doesn’t have a built-in way to see and work on forks and merge them together, etc.
For now, it’s basically just a one-way commit to a remote server thing. At least you can see the commits and the comments locally, but that seems to be pretty much the extent of what it can do, as far as I was able to tell.
Thanks for that, doesn’t look like it’s worth doing at present, so, for once, I’ll leave well enough alone.
I was trying this yesterday. I managed to create some different branches and then use the git command line to check out different branches. This way I can check out a new branch make several changes and decide to merge in to main or to revert by checking out main.
But I think there is a bigger problem (see my comment below).
I’ve messed up my node red flows a few times and wanted to start to use Node Red Projects with the idea of having a development node red instance and a production node red instance.
I set up a new node red docker compose instance on my laptop, enabled and created a project, added the node-red-contrib-home-assistant-websocket package. Tested with a call service node and configured the HomeAssistant server node. All ok.
I then exported all my production (HA Yellow) node red flows, and imported them into the new project. There were three hundred HA nodes that needed to be reconfigured to point to the HA Yellow server. - This site helps a bit: Scrubber | node-red-contrib-home-assistant-websocket
All seemed to be going in the right direction but I did not test any further because the live system had some failures!!
I have a number of nodes that create Home Assistant Entities - buttons and switches mainly. These stopped working on the production instance!!
What I think is happening is that both node red instances were trying to create the same instances and HA got confused - in the end I stopped the new node red server and then changed and re-published all the broken entity nodes to get them to start working again.
We need a documented design to show how to manage and test change in HA and in node-red. There should be a process / convention that enables testing and rollback of change (roll back after updates could be clearer too). I personally would love to have two HA instances - production and standby.