Node-RED nodes for hubitat

Where are you located ?

Perhaps instead of just posting works for me you might post an example? There's obviously something I'm missing. Especially since I've already posted that I've tried every key I can find.
Sorry to sound cranky, but here's yet another node with poor documentation and I'm sorry if this node is beneath you, but the answers in this thread in general are increasingly more frustrating and searching it is almost impossible.

Have you seen these nodes?

1 Like

San Antonio, Texas, USA

Sorry but I don't know what else to tell you

For the pushover config node:

  • the "User" field is the "User Token" listed in your pushover account.
  • the "Token" field is an "Application/API Token" in your pushover account. You may need to go into your account and make one as you should use a different one for each application that sends pushover notifications.


For msgs into a pushover node

  • msg.device (if specified, it's optional) in an incoming msg to the pushover node is the name of a device you have configured, as listed in your pushover account page
1 Like

new version 1.2.0 :tada:


  • add hsm and hsm-setter node to manage Hubitat Safety Monitor (thank you to @dan.t for PR and @JasonJoel for functional review)
  • fix websocket connection to take Hubitat server port into account (thank you @csteele)
  • improve nodes documentation (thank you to @JasonJoel)

Have a look at this.

[{"id":"a1104b2c.c3c4d8","type":"tab","label":"Flow 2","disabled":false,"info":""},{"id":"5a80ff44.23e1f","type":"hubitat device","z":"a1104b2c.c3c4d8","name":"B","server":"be7a24b8.2cc5c8","deviceId":"1058","attribute":"","sendEvent":true,"x":210,"y":120,"wires":[["354e743a.6ca46c"]]},{"id":"188f21c7.2741be","type":"hubitat device","z":"a1104b2c.c3c4d8","name":"B1","server":"be7a24b8.2cc5c8","deviceId":"1059","attribute":"","sendEvent":true,"x":210,"y":260,"wires":[["6d6a094b.2a67b8"]]},{"id":"8b9ba393.9d1c8","type":"hubitat device","z":"a1104b2c.c3c4d8","name":"B2","server":"be7a24b8.2cc5c8","deviceId":"1060","attribute":"","sendEvent":true,"x":210,"y":380,"wires":[["6d6a094b.2a67b8"]]},{"id":"d649f48a.e434e8","type":"hubitat command","z":"a1104b2c.c3c4d8","name":"B1","server":"be7a24b8.2cc5c8","deviceId":"1059","command":"","commandArgs":"","x":570,"y":100,"wires":[[]]},{"id":"dfda43fc.3b3c6","type":"comment","z":"a1104b2c.c3c4d8","name":"Group B control On/Off both B1, B2","info":"","x":420,"y":40,"wires":[]},{"id":"24a2dced.c90a14","type":"hubitat command","z":"a1104b2c.c3c4d8","name":"B2","server":"be7a24b8.2cc5c8","deviceId":"1060","command":"","commandArgs":"","x":570,"y":140,"wires":[[]]},{"id":"354e743a.6ca46c","type":"change","z":"a1104b2c.c3c4d8","name":"","rules":[{"t":"set","p":"command","pt":"msg","to":"payload.value","tot":"msg"}],"action":"","property":"","from":"","to":"","reg":false,"x":390,"y":120,"wires":[["d649f48a.e434e8","24a2dced.c90a14"]]},{"id":"6de2eca6.3f2074","type":"comment","z":"a1104b2c.c3c4d8","name":"B1 : ON - Group B : ON, but B2 still OFF,","info":"","x":440,"y":200,"wires":[]},{"id":"edaa6cbe.d4dcf","type":"hubitat command","z":"a1104b2c.c3c4d8","name":"B","server":"be7a24b8.2cc5c8","deviceId":"1058","command":"","commandArgs":"","x":569,"y":261,"wires":[[]]},{"id":"6d6a094b.2a67b8","type":"change","z":"a1104b2c.c3c4d8","name":"","rules":[{"t":"set","p":"command","pt":"msg","to":"payload.value","tot":"msg"}],"action":"","property":"","from":"","to":"","reg":false,"x":390,"y":260,"wires":[["edaa6cbe.d4dcf"]]},{"id":"fe9743dd.f8aac","type":"comment","z":"a1104b2c.c3c4d8","name":"or B2 : ON - Group B : ON, B1 still OFF","info":"","x":430,"y":320,"wires":[]},{"id":"be7a24b8.2cc5c8","type":"hubitat config","z":"","name":"Node-Red 2","usetls":false,"host":"","port":"80","appId":"1411","nodeRedServer":"","webhookPath":"/hubitat/webhook","autoRefresh":true}]
1 Like

Nice work Francois! I may owe you a beer next time I'm in Quebec (I go to QC for work at least 1x/yr)! :slight_smile:


hehe sure, you are welcome. let's me know :slight_smile:

Quick question? Does the websocket connection have any de-dup code in there? Before I try it out :smiley: :smiley:

No. You would want to use an RBE node after the device node if you want dedupe.

1 Like

Can someone help me figure out what’s wrong with this flow? I want the light to turn on when with motion and when illuminance <= 60. However it never gets past the illuminance node.

Thanks! Going to hold off for now.

1 Like

Can you post the sequence? Or at least the content of the two switch nodes?

This isn't directly pertinent to your question, but are you sure you want "send events" selected for the device node called "Illumination"?


Hmmmmm..... so the illuminance sensor is from another motion sensor on a shared wall. When someone triggered motion I saw the debug message.

You need to use msg.payload.value for your Illuminance switch node.

Also: Deselect "send events" for the Illuminance device node.


It is a bit of a dilemma...

On the one hand he could easily just dedupe everything when using websocket. But some device events need to NOT be deduped - like button presses. And the websocket doesn't include a "state change" attribute, so @fblackburn would have to hard code in exceptions by type (not fun).

So it might always be necessary for the end user to do their own RBE/deduplication on events when using websocket. Not sure how the HubConnect nodejs server does it - if they hard coded exception ion or other.


I agree. Just not what I want to tackle while my hotdog filled gut is soaking up a six-pack of Shiner bock.


Me either. :slight_smile:

1 Like

Download the Hubitat app