Node-RED co-creator and project lead here. Happy to answer any questions you have.
Node-RED: Low-code programming for event-driven applications
81–90 of 93 posts
Re: Node-RED: Low-code programming for event-driven applications
#82I have just been going through a HELL of a time building a web-based app ("PWA" in progressive lingo) that needs to auto-discover certain devices on the user's LAN. This is a rebuild of an existing AIR-based app that's been in use in a corporate setting for 10 years and needs to be replaced because "death of flash". The AIR app I wrote back then handled discovering the local devices fantastically well. The problem no…
Re: Node-RED: Low-code programming for event-driven applications
#83What do people automate at home? I genuinely have never thought to have the need to buy a home assistant but apparently lots of people in this thread do
Unfortunately automating normal curtain opening is pretty tricky mechanically. It was easy to get as far as "Ok Google, open the curtains" -> stepper motor moves. But connecting the stepper motor to the curtains is tricky. I think that's why smart blinds are way more common.
Re: Node-RED: Low-code programming for event-driven applications
#84Node-RED co-creator and project lead here. Happy to answer any questions you have.
I'm not an NR user yet but I've implemented my basic Home Assistant set up and plan to begin using NR extensively as I evolve my home automation beyond "Hello World".
Re: Node-RED: Low-code programming for event-driven applications
#85Earlier quoted context omitted.
This is the thing that’s kept me from pursuing home automation: the advantage of automating lighting (or anything else) is completely negated the moment something goes wrong, because you’ll spend more time debugging than you ever did flicking the light switches in the first place.
The only thing that's tempted me when it comes to automation is whole-house light dimming past a certain hour. But AFAIK that would require buying a whole bunch of really expensive bulbs (or, otherwise, re-wiring a bunch of stuff), so I've passed on it for now. If you get used to candle or other low-power nighttime lighting, typical house lighting seems obnoxiously bright. I'm convinced it's a major contributor to th…
Re: Node-RED: Low-code programming for event-driven applications
#86What do people automate at home? I genuinely have never thought to have the need to buy a home assistant but apparently lots of people in this thread do
Lights come up automatically based on time of day and motion in rooms.
Our family channel in Telegram gets notifications if the house is too hot/cold dry/humid, maybe a humidifier gets turned on automatically.
Re: Node-RED: Low-code programming for event-driven applications
#87Earlier quoted context omitted.
How do you feel Node-RED stacks up against products like Boomi, MuleSoft, SnapLogic, etc., and is competing with those iPaaS vendors something you want to do?
(Node-RED project lead here) Node-RED is an open-source project and part of the OpenJS Foundation. We'd certainly aspire Node-RED to be comparable at a technical level with other offerings. But as an OSS project, we aren't looking to create a hosted SaaS offering - the core project isn't trying to compete commercially with those vendors. But there are companies looking to create commercial services around Node-RED th…
Re: Node-RED: Low-code programming for event-driven applications
#88Node-RED co-creator and project lead here. Happy to answer any questions you have.
Suggestion: when I last used it, loops was a third party add on, you should look at getting that into the core, maybe hire the dev of the add on?
Re: Node-RED: Low-code programming for event-driven applications
#89Earlier quoted context omitted.
We're a industrial-control company whose traditional UI has been standard win32 applications - we've slowing converting our stack over to a web interface but as our UI needs to talk to lots of local devices, we've hit the problems you described. Our solution has been to basically mandate that the user install either a small embedded device (ie. RPI or equiv) or manually launch a container. These essentially just serv…
That's cool. I guess our problem could be described as allowing non-technical users to control the in-shop devices from an app on their phone (both android and iOS) without knowing the local IP at all. Like, how do we determine the shifting dynamic IP of our in local routing system from an app served from the cloud ...and the answer unfortunately is we can't. We have to serve the app locally in each facility.
* Local RPI / Container connects to message queue in cloud * Web User inputs request to Web UI (cloud) * Local RPI / Container retrieves request via queue and access final device * Reports status back to queue which is then reported by Web UI
Basically the local device is your router using whatever message queue you want.
Re: Node-RED: Low-code programming for event-driven applications
#90Earlier quoted context omitted.
I've been following Enso since it was Luna. Can you be a bit more explicit about 'in-dev'? Not to be used yet in production? Thanks.
Hm, honestly, this was kinda precautiously overly-defensive statement from my side. I mean, I'm also following Luna/Enso with huge interest, but it's kinda on-and-off for me; it seemed to me to still have some rough edges in the GUI last time I checked, but also it was quite long ago already - somewhere right around their 2.0 public announcement, in January 2021. No slightest idea at what state the GUI is now, or the…