Node-RED nodes for hubitat

⚙️ Custom Apps and Drivers Node-RED
4212

Yep, I'm noticing the problem too. It's causing unexpected results when using the Inject node immediately after restarting NR. Please help! :frowning:

4213

I haven't had any issues with inject nodes into the device nodes. They have all been working as expected for me.

I've seen a few other oddities since going to 1.4.0 though that I'm still trying to track down.

EDIT: Never mind, the issue I was referencing was unrelated to the hubitat nodes.

4214

I hope he fixes this soon. :frowning:

4215

You might need to explain further on what your issue is though. Saying you are getting "unexpected results" probably doesn't help francois understand what is broken.

The only thing I see is purely cosmetic - the status text on device nodes. Everything else seems to be working as expected for me (a couple things I thought were broken was something else I messed up that didn't relate to the 1.4.0 update).

1 Like
4216

As you can see, the value is not showing under my Life360 device after NR restart. This inject node runs .1 seconds after reboot, yet it fails on the James path, literally the msg stops after going through the device node. My wife's showing because she was actually driving/ changing the value.

image
image964×333 23.1 KB

4218

.1s after reboot? I'm surprised they don't all fail.

I wait typically no less than 10s reboot before triggering flow updates. It takes a bit of time for the Hubitat nodes to initialize after a node-red (or Hubitat) restart.

1 Like
4219

Just want to call out that this was working before the NR HE release. Also, if I'm simply querying for status shouldn't it pull from the NR HE device cache? I guess the cache is building at startup, maybe that is the problem...

UPDATE: changed inject node to run after 60 seconds, it now works. I think HE NR node was building the cache as I was querying and it was failing.

4220

According your setup/configuration/devices/hub/etc... the cache can be longer to build than before. You can look at the NR log to see the time needed for initialization and set your init offset according the result.
But it should not take more than a few seconds

4221

Fixed in 1.4.1, thank you for reporting :slight_smile:
The diff from 1.4.0 :man_facepalming:

-        node.devicesFetcher();
+        await node.devicesFetcher();
4 Likes
4222

Thank you fblackburn!

2 Likes
4223

Thanks @fblackburn. Confirmed that everything looks normal for me in 1.4.1.

2 Likes
4224

Does anyone know of a good NR thermostat controller / scheduler?

4225

I'm not sure I understand what you're looking for. You can build the equivalent of the Hubitat thermostat scheduler app, or even the new thermostat controller app, using the built-in nodes in conjunction with the hubitat nodes.

4226

I don't use this one, but I know a few of my co-workers do.

4227

small bug fix version 1.4.2

  • device: fix traceback when receiving input or event before initialization
4 Likes
4228

Is there a way to catch the event of opening a smart lock using a pin? What I would like to do is set HSM to intrusion disarm from alarmed away when a smart lock is opened pin.

4229

Typically yes, but it depends on 2 things:

  1. If you are using webhook or websocket connection to hubitat (websocket does not pass pin/all lock info)
  2. The driver you are using on the hubitat side. Some expose the data, some don't.

Best advice I can give is to run the device node into a debug node, lock/unlock with pin, and see what data is in the debug messages.

1 Like
4231

thanks

4232

I posted a while back about my NR GUI being ridiculously slow when doing things like deleting nodes even though automation performance was not affected. I posted similar over at Node Red community and although we couldn't determine a root cause, the suggested solution was to split across multiple machines or even multiple instances on same machine.

Currently NR is running on RPi4 8Gb with 128Gb SSD and I have a 2nd RPi 4 4Gb with 128Gb SSD available.

So my questions are:

  1. How many flows & nodes do you have running in a single instance of NR

  2. Have you noticed slowdown of GUI as you added flows?

  3. How big is your flows' JSON file?

  4. if you have multiple instances on multiple machines, are there any complications I need to look out for?

My instance has over 30 flows usually with multiple sequences in each.

4233

I run mine in docker containers on CHUWI HeroBox nodes (Intel Celeron N4100 based), running Ubuntu desktop.

29, 112 nodes (not sure how many instances of the nodes though - probably a 1000?)

Nope

589K

Too open ended of a question to answer. All depends on your flows. Would need a separate Maker API instance per node-red though.

2 Likes