From a maker API event standpoint I believe they are equal.
Command nodes setting methods via maker API are almost certainly faster on a virtual device than a real device though. It that wouldn't impact your initialization time.
I will say that in 2.2.4 beta devices/* only takes about 1-2s for 103 devices in Maker API (~80 physical, 20 virtual). I think the platform optimizations they have been doing are really working, as it used to take 10+ seconds.
It's nice to know, thank you !!
Can anyone break it down for us dumb guys in the back. I can't even figure out how to install it.
Do you have node-red installed? What platform are you running node-red on?
Nope, couldn't figure out how. Most likely windows
I have no experience with Windows; if you have a spare RPi, then this image from @csteele would be useful:
Edit: Here are instructions on how to install Node-RED on Windows:
I don't know anyone that runs it on Windows, but that said it is supported and should work.
Here are the official instructions:
https://nodered.org/docs/getting-started/windows
(EDIT: @aaiyar beat me)
Summary:
Correct me if I'm wrong, but isn't this just another rule style machine?
More or less. More info here:
https://nodered.org/
No right or wrong on what to use. I like node-red as it has many integrations with LAN/cloud devices that hubitat doesn't. I also like having my logic in an 'independent' system - probably 90% of my home automation 'intellectual property' is in my logic.
So I like having it in a system I can backup at will, put on faster hardware if needed, or even swap my logic to a completely different hub/home automation system if I needed/wanted to. I have needed to/wanted to 2x already. Nice to not have to redo all my logic from scratch each time.
I integrate at least 3 different systems in node-red, (Home Assistant, hubitat, MQTT) so it is really a great system to glue it all together. I also use it for dashboards since I can then have data from any of those 3 systems on the same dashboard.
And I like the graphical drag/drop connect the dots editor in node-red.
Great explanation.
What do you run out on?
This!!! I second what he said!!!
I am in the middle of migrating my stuff over to a C-7 and my rules (sequences) have stayed the same. The only thing I had to do was edit the HE device nodes they were pointing to. I can add hubs or remove them and my rules stay consistent.
The most common hardware would be a RPi or similar SBC.
I ran it on an Intel NUC for a while, but then repurposed that as a Linux desktop and am currently running it on an Odroid N2.
I've run it on a VM but then switched to an RPi4 which is also what I am also using for my clients. I have an Odroid as well which I may eventually switch over to because it seems a bit more reliable. To be fair the RPi has held up since last July. You can run it directly from the usb drives now which is also something I am looking into.
So if it's browser based, why do not many people run it on a windows computer?
I have 5 node-red instances .. 1 kubernetes, 3 docker containers, 1 ubuntu VM.
It's nice to have it running on a headless (no monitor) server. That way it does not interfere with your desktop system in anyway. Another nice thing is running a VPN with it. Something like WireGuard allows you secure remote access.
If you have a Windows computer running 24x7, there’s no reason you cannot.
I use my Odroid for lots of other things that run headless as well. It is configured to restart all my servers (including the nodejs ones) on startup. And its power consumption is negligible.
Ah, okay. So a BI iris server would be good to run it on.
Sure. Should work. Node-red doesn't take much memory or cpu.
Agree with @JasonJoel. It will be amply powerful. You may consider running it in a VM. Or container (I’m assuming that’s possible under Windows?).
Download the Hubitat app
