Node-RED nodes for hubitat

erktrek · May 17, 2020, 1:47pm

You should report it to @fblackburn - post the issue on Github. Easier for them to track.

JasonJoel · May 17, 2020, 1:57pm

Not here. I have 6 presence nodes, and they are all showing correct status. I just checked as the wife is at the store - it shows her as not present as expected.

Is it possible that your device changed states while node-red was down? Remember if there is a loss of communication between node-red and Hubitat, the nodes do not do anything to get back in sync... They stay as-is until the next event is received.

Try rebooting Node-RED and see if the state becomes correct, If so, it likely is not a node issue at all, and it just missed the event for some reason.
Verify that MakerAPI post events are making it to Node-RED correctly. AKA verify states change in node-red post reboot.

The only time the cache is rebuilt from scratch is:

Reboot of node-red
Reboot of Hubitat, but only if you have enabled the new systemStart rebuild option in the node-red config node:

image1601×206 20.8 KB

april.brandt · May 17, 2020, 4:17pm

Anyone have a few minutes to help me with a flow? I've been fighting with it for a few weeks now, and it's rather erratic behavior. I had some services break on my pi, which I fixed and things seem to be running better now, but this flow feels like it should work and it's not. So I need some input on it
The whole picture
When either motion sensor is triggered and the lights are off, then I need the lights at 100%
when the tv (ps4, roku, cable) is turned on with harmony then I need the lights to dim to 25% and stay there for the duration. Until the tv goes back off. Then return to 100%.
when the room is again inactive and the tv is off, then the lights should turn off.
Everything works except for the lights turning off. I'm sure it's how I have the flow written, but I've tried so many different things that I can't remember what I have and haven't done yet.
So I need someone to set me straight before I go nutz!

jason-lane · May 17, 2020, 4:31pm

I just had a quick look at your flow after importing into my server, and one thing I noticed straight away is that you seem to have "Send events" enabled on each one of your device nodes, even when you're just checking a value/status. Is that intentional, or an oversight? We usually only want that option ticked on the nodes whose events we want to trigger our flows. I believe that having that enabled on other nodes within the flow can lead to unexpected bahavior. I don't know if this is where your problem is, but it's the first thing I noticed while going through your flow.

april.brandt · May 17, 2020, 4:34pm

I'll change it. Thank you for looking

leeonestop · May 17, 2020, 7:37pm

@JasonJoel Thanks for the info. I took your advises and restarted my Node Red and Hubitat Hub and I think maybe that was the problem and didn't realize or think about sync. I also did as you suggested so If I did a reboot it would rebuild the cache. Again, thanks for the help.

MRobi · May 18, 2020, 6:29pm

Were you ever able to get this going in the HASSIO version of NodeRED or was the only solution to install NR on another device??

I'm experiencing the same thing you were where I can control devices and retrieve info on devices when deploying or a manual inject, but not getting anything on an event.

kevin · May 18, 2020, 8:43pm

Yes I am running node-red in the HASSIO plugin. I can't remember just what solved my initial problem though.

JasonJoel · May 18, 2020, 8:46pm

How do the POST events from Hubitat make it to the node-red container (as opposed to going to the HA container for instance)? I would think that would have taken an extra config step?

morningz · May 18, 2020, 9:04pm

I'm having the damnedest of times trying to get Hubitat + Home Assistant + Node Red all working together.

There seems to be two different approaches and both equally suck

putch · May 20, 2020, 10:05pm

I've gone from using NR stand-alone to using it in HA docker as an addon (and back to stand-alone). I have run it successfully in both scenarios. One thing (and I don't remember if it was during my initial stand-alone or when I switched to HA addon) was the that the NR version installed was < 1.x. This caused my all sort of problems where some messages would come, but then they'd die the as soon as they hit any other HE node. So for @mrobi can you double check the version of NR you are running?

As for @morningz can you be more specific as to what issue you are seeing.

MRobi · May 20, 2020, 11:40pm

Think hard!! LOL Did you setup MakerAPI with the HA port or the NR port?
I'm assuming it's got something to do with my webhook settings. I've tried with and without the login info for NR. I've tried both ports.

v1.0.5

kevin · May 20, 2020, 11:46pm

Does this help ?? I do not expose this nodered to the outside world and have removed SSL and DuckDNS access - and maybe that last line 'leave back door open' I changed...

credential_secret: xxxxxxxx
dark_mode: false
http_node:
  username: ''
  password: ''
http_static:
  username: ''
  password: ''
ssl: false
certfile: fullchain.pem
keyfile: privkey.pem
require_ssl: false
system_packages: []
npm_packages: []
init_commands: []
log_level: info
port: 1880
leave_front_door_open: true

It's likely very vulnerable now and I should add some bits back into that config but I'm pretty sure it's protected on my Intranet. Change that last entry at your own risk.

Just to confirm my nodered is locally accessible on
http://192.168.1.150:1880
and that IP is the host NUC on which hassio is installed - it is not the docker container IP address 172.x.x.x

MRobi · May 21, 2020, 12:00am

I added the leave front door open to my config for testing.
I assume 33737 is your HA port.
I wonder if it's because I'm using the HA integration that's using MakerAPI already?
So I essentially have 1 instance going to http://HAIPADDY:8123 and another going to http://HAIPADDY:8123/hubitat/webhook/

kevin · May 21, 2020, 12:05am

You will need to create two separte Maker API applications and setup the 'URL to send device events to by POST' to be different in each one - one pointing to the HA Hubitat integration and one to the nodered one.

TBH that 33737 may relate to another integration .. I forget now.. it's probably this..

http://192.168.1.150:1880/hubitat/webhook

morningz · May 21, 2020, 12:15am

So I installed HA via the image method detailed here

I love the idea of the clickable floorplan of HA as well as the remote access through their Nabu Casa service. Plus once I get rolling it looks like it's relatively easy to pull in camera feeds into the dashboard as well. I'm super intrigued by the Telegram bot integration as well

My hope was to somehow leverage Node-RED to have this setup:

Hubitat to add/manage the 70 or so devices (because HE appears to be way easier to manage devices than HA)
MakerAPI / Node-RED / and the Hubitat palette from this thread to funnel/expose my devices to HA as entities

That second point seems to have two ways to do it:

Custom app/drivers here on HE to leverage MQTT to bridge the two. Sorry, I wasn't a fan of the setup, a lot of it just didn't make sense: like for instance, do I need to worry about "homie" at all or not? It also seems to be way too chatty on the network for my personal taste. Ah well, that code may work for others, but not for me as in the end I'm trying to run stuff on the HE as little as possible (as it stands right now, I have MakerAPI installed and that's it).
Trying to go the other way with this custom HA/Node-RED code that has nodes to create entities from other Node-RED nodes. I've actually got this kind of working as shown in the screen shot below as an example: I can actually control my blinds from either HE or HA. Issues with this route include: limited entity types (sensor, binary sensor and switch) and an annoying ghost event that fires closing of the blinds every time I restart HA, which to be honest hasn't been very often, but it has been annoying when I tinker with it.

I kind of got fed up with both those routes and thought I'd get my GoControl Z-Wave/Zigbee stick up and running to see about streamlining things. I've got it plugged into the Pi, HA sees it just fine and I have both the ZHA integration and Z-Wave integrations installed and working with a few devices paired to each radio. But: paired a Sengled dimmer to it, HA had no idea what that was. Paired a Zooz ZEN31 LED dimmer to it, no idea what it was (some custom editing of the Z-Wave config file fixed this, but that is not something I want to be doing on a consistent basis). This isn't the route to go if that is the pain of pairing devices to it.

I was actually trading Twitter messages from Rob at "The Hook Up" today as he was intrigued by a comment I made on his video today talking about blinds. we seem to have the common goal of using HE as the conduit for devices in NR and HA

Maybe I just can't decide what I want in the end, maybe I'm just overthinking things. But I do like to tinker around and I am a huge fan of the concept of MQTT, so I'm still hoping I can get my setup of HE > NR > HA all straightened out.

Here is that custom HA Node-RED palette in action that takes my three IKEA blinds paired to HE and turns them into entities for use in my Lovelace dashboard.

zq3bWsqU

And as you can see here I can see and can control them from either platform which is kind of neat

Thanks for reading!

MRobi · May 21, 2020, 12:19am

Just for fun changed my port to 33737 and I'm getting somewhere. I'm now getting events which is something I wasn't getting before so thank you!

I'm still not getting mode change events though even though I have the location events switch turned on.

JasonJoel · May 21, 2020, 12:27am

You do know that there is a HE --> HA integration as well, right? You didn't list that as an option, so thought I would double check...

You could just go HE --> HA and not mess with Node-RED at all.

morningz · May 21, 2020, 12:28am

I for sure want NR in the mix.. dragging and dropping nodes = better than writing YAML (yuck!)

JasonJoel · May 21, 2020, 12:29am

OK... But if you use the linked integration everything shows up in HA with no yaml written at all... But whatever makes the most sense to you.

Just seems to me if you want all HE in HA, then that integration is EXACTLY what you want?

But if you want to do your logic in Node-RED, then yeah I guess it may make more sense to go to Node-RED first, instead of HE --> HA --> Node-RED --> HA ...