Node-RED on AWS

[david.i.tanzer@gmail.com]

I'm running Node-RED on an AWS EC-2 instance. Is there a way to reference my HomeSeer (I'm running HS4 on a HomeTroller Zee S2) as a server in the Node-RED HS Device node?

[Eman]

I'm running Node-RED on an AWS EC-2 instance. Is there a way to reference my HomeSeer (I'm running HS4 on a HomeTroller Zee S2) as a server in the Node-RED HS Device node?

Living dangerously...Are we?...

At your own risk try : https:// {your username}:{password}@myhs2.homeseer.com:{port of your HomeSeer System}

And in HomeSeer custom settings https:// {the access address of your AWS Node-RED}:1880/homeseer/webhook

No guaranties if this will work but...you're the one doing the hacking!


Else, you may need to contact this guy here : https://www.youtube.com/watch?v=n_1wX7kKx7k (Unrelated but he knows his stuff)


Eman.

[david.i.tanzer@gmail.com]

Ha! I have the feeling that I need to go directly to my HomeSeer box, so I don't think myhs.homeseer.com will work for this. I tried port forwarding, but I couldn't get that to work either. Perhaps Node-RED needs to be running on my local network? Or maybe I need to set up a VPN?

[Eman]

It should look like in the image below but I have not tested.... We did that trick with a remote speaker client on a Laptop and it worked!. But what I think it only works on plug-ins






You may need to contact spud or Michael McSharry to secure your mqtt nodes from AWS back to HomeSeer.



There is also this : https://flows.nodered.org/node/node-...ib-aws-iot-hub (Which should be local on a Raspberry pi)

How to start right here : https://nodered.org/docs/getting-started/raspberrypi




Eman

[david.i.tanzer@gmail.com]

So, port forwarding DOES work! I simply created a dummy port (I used 1880 because that's what Node-RED uses) and forwarded it on to the internal IP of my Zee S2 at port 80. Bingo! It works!

[Eman]

So, port forwarding DOES work! I simply created a dummy port (I used 1880 because that's what Node-RED uses) and forwarded it on to the internal IP of my Zee S2 at port 80. Bingo! It works!

You go boy! But secure your network and can also check out those links I posted at # 4

Try this guy again : https://www.youtube.com/watch?v=80vIin4xGp8

Eman.

[drhtmal]

So, port forwarding DOES work! I simply created a dummy port (I used 1880 because that's what Node-RED uses) and forwarded it on to the internal IP of my Zee S2 at port 80. Bingo! It works!

Port forwarding works and is great until your system is hacked.

[david.i.tanzer@gmail.com]

drhtmal, do you have an alternative if Node-RED isn't running on my local network?

[david.i.tanzer@gmail.com]

Eman, thanks for your suggestions. I don't believe using myhs2.homeseer.com will work for Node-RED--I think it needs to talk directly to an IP. And the Raspberry Pi documentation is for installing it on a local device, in this case, of course, a Rapsberry Pi. In my case, I'm running it on an AWS EC2 box. As well, I'm using the HomeSeer-provided Node-RED node: https://flows.nodered.org/node/node-...ntrib-homeseer which I don't believe uses MQTT.

This is very cool, though. Changes to my HomeSeer devices immediately reflect in Node-RED flows, and the Node-RED sourced control of my HomeSeer network is very fast!

[dbrunt]

I'd be considering a VPN or at the very least locking down port 1880 to only accept traffic from AWS IP's...

[Eman]

Eman, thanks for your suggestions. I don't believe using myhs2.homeseer.com will work for Node-RED--I think it needs to talk directly to an IP. And the Raspberry Pi documentation is for installing it on a local device, in this case, of course, a Rapsberry Pi. In my case, I'm running it on an AWS EC2 box. As well, I'm using the HomeSeer-provided Node-RED node: https://flows.nodered.org/node/node-...ntrib-homeseer which I don't believe uses MQTT.

This is very cool, though. Changes to my HomeSeer devices immediately reflect in Node-RED flows, and the Node-RED sourced control of my HomeSeer network is very fast!

You could also have 2 or more (but 2 are enough in my case) instances of Node-RED (Local and the AWS EC2 box) Depending on what you are running, you can have the remote one enable when you are away from home but have the local one deal with the in-house automations (your ball)

I run 2 locally (one on ioBroker and the stand alone which also has an mqtt instance reason being I can't run the Node-RED NEEO nodes on the ioBroker instance and the same goes for the ioBroker Nodes, they come bandied with the server

• As for mqtt nodes, they add more juice to the mix , they add to the alchemy...

Eman.

[John245]

You could also have 2 or more (but 2 are enough in my case) instances of Node-RED (Local and the AWS EC2 box) Depending on what you are running, you can have the remote one enable when you are away from home but have the local one deal with the in-house automations (your ball)

I run 2 locally (one on ioBroker and the stand alone which also has an mqtt instance reason being I can't run the Node-RED NEEO nodes on the ioBroker instance and the same goes for the ioBroker Nodes, they come bandied with the server

• As for mqtt nodes, they add more juice to the mix , they add to the alchemy...

Eman.

Why would people like to life on the edge and and an additional point of failure?

---
John

[Eman]

Why would people like to life on the edge and and an additional point of failure?

---
John

Well,

What he didn't explain about is what he was using the AWS EC2 box for (Why not install Node-RED locally and avoid running it remotely)

Unless I missed something?... https://aws.amazon.com/ec2/instance-types/

• Now like you can see in the above posts everything diverted into security issues
• I explained myself, what I do with my 2 local instances...I guess that clears everything...

So if he is OK with his instance, all he has to deal with is this : https:// {the access address of your AWS Node-RED}:1880/homeseer/webhook

Eman.