Would anyone here want a cloud-hosted hosted version of node-red? Like a PaaS for node-red?
Node-Red
21–28 of 28 posts
Re: Node-Red
#22The one thing I want added to Node-Red is an editable, sanely git diff-able on-disk text format for its configuration. I want to be able to edit either in GUI or in text, and then view the result in the GUI (and have it work of course!). Does anybody know if there's any plugin for or way of achieving that? When I last looked into it, people were checking in the config files (whatever format they were, perhaps proprie…
Are you aware of the projects feature and how it lets you maintain all your flows in a git repo, complete with "visual" diffing?
Yes, but I can also put MS Word .docx files 'in a git repo', and diff them with MS Word proprietary version control. That's not good enough for use at work, in a software project among software engineers who don't need or necessarily want no/low-code; and it's not what I want in personal 'home automation' use either, which is where I gather it's perhaps most popular and how I discovered it - and probably most of that audience does want no/low-code and doesn't know 'what a git is', but, you know, I'm a SE, I know what git is, I like it, can't bare the idea of having anything like HA outside of its control.
Re: Node-Red
#23Would anyone here want a cloud-hosted hosted version of node-red? Like a PaaS for node-red?
There are a few such services out there today.
It's also what we're working on at https://flowforge.com
(Disclaimer - I'm the co-founder of the Node-RED project, and CTO/Founder at FlowForge)
Re: Node-Red
#24I use NodeRed a lot for my smart home and local network as glue between different pieces. It works really well for “hit this API, apply this transformation, and then return it when I send you a GET at /something” or “listen for MQTT, get this key out of the message, and rebroadcast it”.
Do you use it on it's own, or with other automation software like home assistant or openhab?
I have similar process setup as original poster, instead of MQTT, I use home assistant Node-RED pallete which exposes all home assistant entities to nodered.
Node-RED automation is SO much better than home assistant automation or Huggins, ability to deploy modified flows when nodes on same flow are kept running is AMAZING!, makes dev cycle so much faster.
I use home assistant's builtin zwave, homekit controller, homekit bridge, Sonos, and InfluxDB, everything else is commented out. It's all running on used $50 HP Prodesk G2 with Ubuntu server with HASSOS in VM, VS.Code server in docker. Uses about 7 watts/hr.
Re: Node-Red
#25Earlier quoted context omitted.
Are you aware of the projects feature and how it lets you maintain all your flows in a git repo, complete with "visual" diffing?
Yes, but I can also put MS Word .docx files 'in a git repo', and diff them with MS Word proprietary version control. That's not good enough for use at work, in a software project among software engineers who don't need or necessarily want no/low-code; and it's not what I want in personal 'home automation' use either, which is where I gather it's perhaps most popular and how I discovered it - and probably most of that…
Well, the node representation relies on internal identifiers and is not really human-friendly, so I think you’re out of luck there.
(I do run my home automation and quite a few dashboard and minimal API projects on Node-Red and version then that way, but if I want something with an actual lifecycle, I’ll reach for Python or Go…)
Re: Node-Red
#26Earlier quoted context omitted.
Yes, but I can also put MS Word .docx files 'in a git repo', and diff them with MS Word proprietary version control. That's not good enough for use at work, in a software project among software engineers who don't need or necessarily want no/low-code; and it's not what I want in personal 'home automation' use either, which is where I gather it's perhaps most popular and how I discovered it - and probably most of that…
Well, the node representation relies on internal identifiers and is not really human-friendly, so I think you’re out of luck there. (I do run my home automation and quite a few dashboard and minimal API projects on Node-Red and version then that way, but if I want something with an actual lifecycle, I’ll reach for Python or Go…)
Yes, that's my point! I wish that it weren't.
Re: Node-Red
#27I use NodeRed a lot for my smart home and local network as glue between different pieces. It works really well for “hit this API, apply this transformation, and then return it when I send you a GET at /something” or “listen for MQTT, get this key out of the message, and rebroadcast it”.
Do you use it on it's own, or with other automation software like home assistant or openhab?
I use it with HomeAssistant. I like HA automations for many things, but I really prefer NodeRed for gluing together systems or sketching things.
Re: Node-Red
#28I had worked +/- 5 months ago a lot with nodered. One thing I miss is some kind of benchmark performance for huge projects. Is something new in docs regarding this? This tool is really great.
I agree! what kind of project were you working on that you consider a 'huge project' genuinely curious to learn how other people are applying this to use-cases beyond home automation!