Top 3 most used smart products

💬 Lounge Debate Chamber
41

How complex is if over rule Machine. I like Rule Machine, just find it fiddly

1 Like
42

Hard to answer, depends on the complexity of the rule in question. I find many things easier in node-red, but some things can be harder in node-red too - looping logic, repeating logic for instance.

Without much effort Node-RED is very good at once through flows, including many conditionals/branching on the flow. Loops/repeats and sometimes wait events can be trickier in node-red - possible, but trickier as it requires some thought/workarounds.

1 Like
43

Don't think you will have much problem. I am a noob and after a week of reading and youtubing. I have node red up and running with basic rules.

3 Likes
44

I have a few days off I might do some reading

1 Like
45

I'm a non-developer, and I've moved all my rules (bar a tiny few) to Node Red. It's not without a learning curve, but I really like it.

3 Likes
46

What are the advantages to using NodeRED over RM other than just the different interface?

1 Like
47

Here are some of my reasons for using Node-RED over RM that aren't interface related:

  1. It is easier to use more complex logic in automations if necessary (for eg. a finite state machine).
  2. It supports a superset of devices supported by Hubitat, rendering it possible to create automations that use devices directly paired to Hubitat as well as devices not supported by Hubitat.
  3. It is easy to backup and share automations (sequences/flows).
  4. If necessary, it is easy to move the automation engine to more powerful hardware.
  5. The automation engine is agnostic vis-a-vis the z-wave controller or zigbee coordinator to which devices are paired. I've exchanged automations with people using Home Assistant with a zigbee/z-wave dongle.
  6. Because it can run on more powerful hardware, it is generally more resistant to ignorant user behavior. I've seen poorly written rules slow one of my Hubitat's down to a crawl. By and large, I have not seen badly constructed Node-RED sequences do the same thing.
6 Likes
48

Not to derail the thread any further, but I often wondered if the trade off in lost transit time was made up in the processing power. @aaiyar would you say for rules more than a single action this would be true, or true for even the most basic rule?

1 Like
49

I think there are too many variables - like other drivers/apps that might affect processing efficiency to make a call.

However, in general, if one follows the KISS principles recommended by Hubitat to construct rules, slowdowns are less likely.

3 Likes
50

For me;
0. HE

  1. Lutron
  2. Alexa
  3. Sonos
  1. Samsung Multi-sensor (doors, windows, garage)
  2. Sengled bulbs
  3. Water Sensors

Lots more, but those are the primary for me.

2 Likes
51

For me, exclusively HE

  1. Locks
  2. Motion
  3. Fan Controls
  4. environment sensors (temperature, lux)
2 Likes
52

Another big thing was make sure the nodes are working properly. I spent hours making a rule,that didn’t work, come to find out a node wasn’t configured properly. If the node worked, my 1st automation would have worked

2 Likes
53

Hmm... top 3....

  1. Lutron
  2. Z-Wave
  3. LAN/Wifi
1 Like