Node-RED nodes for hubitat

stircwazy · July 23, 2020, 2:46pm

Appreciate the feedback.

I've got a volume setup for /data as well with my file path set to /data/alexa/auth.json. When I deploy the change I get "EACCES: permission denied, open '/data/alexa/auth.json'" which is obviously a permission issue, but I'm unclear as to where since my NR container updates /data without issue.

JasonJoel · July 23, 2020, 3:09pm

Could do the nuclear option and do a

sudo chmod -R 777 /data/alexa

To reset permissions wide open on that directory.

Shaneb · July 23, 2020, 3:20pm

I'll see what happens

stircwazy · July 23, 2020, 4:37pm

I could, but would hate myself for giving up so easily.

bdydrp · July 24, 2020, 5:54am

What about a variable for the port?
I run NR on unraid docker. This is a screenshot of my settings:

Shaneb · July 24, 2020, 2:47pm

Has anyone solved anything similar to the below without loads of complex conditions?

I use button controller to also control my lamps in the bedroom.

eibyer · July 24, 2020, 4:38pm

I followed this thread in the beginning but after a few days of not reading I suddenly have hundreds of unread posts lol so I'll just jump to the end and ask.

Anyone seen a significant hub uptime reliability after offloading your webcore/RM rules to node-red?

JasonJoel · July 24, 2020, 4:42pm

Yes

aaiyar · July 24, 2020, 4:46pm

Same observation as @JasonJoel. Hub uptime is now limited by the frequency of platform updates.

erktrek · July 24, 2020, 5:15pm

Yep me too.. on 2 of my 3 production hubs. My third one, a C5 is only for internet/cloud services and has both Zigbee and ZWave turned off. I've never had any issues with that one other than some overheating problems which were my fault.

napalmcsr · July 24, 2020, 5:28pm

Yes, Now my issues are down to my very, very old Z-wave (only) switches that aren't always happy with Maker API.

harold.min · July 24, 2020, 6:24pm

My performance has definitely improved since moving to node-red and deactivating RM. I don't have a lengthy uptime stat for you though since 2.2.2 and resulting hotfixes have been released lately.

Angus_M · July 24, 2020, 8:26pm

Yes, and particularly much faster and more reliable motion lighting with NR than if coded with RM in HE.

cjkeenan · July 24, 2020, 8:40pm

I too would be interested if there is a relatively easy way to move Motion Lighting or Mode Lighting apps over to NR.

Angus_M · July 24, 2020, 8:51pm

It's not a completely straightforward thing to do but in my opinion it's worth the effort for the speed improvement. Here is how I'm doing it...

Shaneb · July 24, 2020, 8:52pm

Motion lighting with modes is easy, it's when you start adding buttons is where It hurts my head...check out the share your nodes post

jason-lane · July 25, 2020, 2:08pm

Can you guys tell me whether RBE nodes are supposed to reset (ie. forget the last msg) across all flows when only re-deploying a single flow? I've just noticed this in the past couple of days. I have a few sequences where an RBE node is set up to block certain Pushover notifications until a change in payload. I'll be working on some things on one flow, and I'll click Deploy, making sure that I've selected "Modified Flows," so I wouldn't expect that to have any impact on the other flows. But every time I re-deploy, I end up receiving notifications from the other flows that should have been suppressed by the RBE nodes.

JasonJoel · July 25, 2020, 2:39pm

Depends on how you are deploying... There are 3 options when deploying - selected with the dropdown on the deploy button:

full deploy
modified flows
modified nodes
(and restart flows, but that isn't technically a "deploy" is it? )

If you are doing a Full Deploy, then yes, they will reset. I typically do Modified Nodes only, unless I know for sure the whole flow needs to be restarted, then I will do Modified Flows.

Full Deploy

This will re-deploy all flows in the workspace regardless of whether or not they have been modified.

This means that currently running flows are interrupted and restarted.

Result

Inject nodes will fire.
Context variables reset
Flow and Global Variables are not reset

Modified Flows

Only flows that contain modified nodes will be redeployed.

Flows that haven’t been modified will continue to run without interruption.

Result

Inject nodes in that flow will fire.
Context variables reset
Flow and Global Variables are not reset

Modified Nodes

Only nodes that have been modified will be redeployed.

Nodes that haven’t been modified will continue to run without interruption.

Result

Inject nodes in that flow will only fire if they have been modified.
Context variables not reset
Flow and Global Variables are not reset

Restart Flows

All deployed flows will be redeployed.

This means that currently running flows are interrupted and restarted.

Result

Inject nodes will fire.
Context variables reset
Flow and Global Variables are not reset

aaiyar · July 25, 2020, 2:46pm

Same here.

jason-lane · July 25, 2020, 3:09pm

Yeah, I've generally been using "Modified Flows," and that's what I was using at the time, so I wouldn't expect the other flows to be affected. That's why I'm surprised that I'm seeing what I'm seeing. I'm going to investigate further tomorrow. Now that I think about it, I don't think it's only the RBE nodes being reset, but also my startup inject nodes on some other other flows being triggered, so it's really as if the flow is being re-deployed, even though I haven't modified it. It doesn't seem to be all other flows, though. I have startup inject nodes on several flows, but only a couple of them seem to be getting triggered. It's too late for me to do more digging tonight, though.