Send Node-RED information to two HS instances without creating double HS device nodes

[John245]

Is there an easy way to send the information in Node-RED to two HomeSeer instances.

I'm running two instances of HomeSeer 1) QA/Staging 2)Production. For testing it would be helpful if Node-RED will send the status of the devices two both instances. As both instances are using the same configuration I can imagine that it will work if I can send the info to both servers (IP addresses).

spud Is this something that could be implemented easily?

---
John

[spud]

no this would not be very easy, and I don't think it makes much sense. A HS device is tied to one HS instance, even if you copied your configuration from one instance to the other, now you have 2 HS devices that are 2 independent entities, so I think they should be represented as 2 different nodes in Node-Red.

[John245]

no this would not be very easy, and I don't think it makes much sense. A HS device is tied to one HS instance, even if you copied your configuration from one instance to the other, now you have 2 HS devices that are 2 independent entities, so I think they should be represented as 2 different nodes in Node-Red.

thanks.

In my current set-up I did this for a limited number of devices, just for the purpose of testing on QA/staging before moving to production.

---
John

[Eman]

MQTT node out will do, because both instances of HS can SUB to the same topic and the message delivered in real time.
This is the such case where you don't have to use the HS node because the settings in the nodes are single server centric




Eman

[ksum]

I would be running a production and test environment which includes a Node Red server for each. You can export/import your individual flows from the rest to the production server.

[Eman]

I would be running a production and test environment which includes a Node Red server for each. You can export/import your individual flows from the rest to the production server.

That would work well if the two systems are not running at the same time (but even if they did I think they would be able to send data at the exact moment) because given the unknown or the not said John245 is after creating a high availability cluster. So HomeSeer doesn't care which system is sending the data (Just target the same device [ID]) but with 2 webhooks and may be stop the logging...this complains when disconnected.


Eman.

[John245]

I would be running a production and test environment which includes a Node Red server for each. You can export/import your individual flows from the rest to the production server.

That would work for flows not depending on HW (at least I have some HW that will not work) (I tried your suggestion before asking the question).

---
John

[John245]

That would work well if the two systems are not running at the same time (but even if they did I think they would be able to send data at the exact moment) because given the unknown or the not said John245 is after creating a high availability cluster. So HomeSeer doesn't care which system is sending the data (Just target the same device [ID]) but with 2 webhooks and may be stop the logging...this complains when disconnected.


Eman.

These are 2 different things.

1) I'm setting up a HA cluster (ordered HW but waiting for it)
2)I'm running a production environment and a QA/Staging environment

---
John

[Eman]

These are 2 different things.

1) I'm setting up a HA cluster (ordered HW but waiting for it)
2)I'm running a production environment and a QA/Staging environment

---
John

John245, am sorry for poking in too deep but surely it was a kind of the need to know...(Investigative insinuation )

But it's your ball now...


Eman.