More than one generic HTTP server IP possible?

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
chunter1
Normal user
Posts: 82
Joined: 22 Jan 2016, 22:40

More than one generic HTTP server IP possible?

#1 Post by chunter1 » 26 Sep 2016, 11:14

Is it possible to send the Data to more than one generic HTTP server IP?
The reason i would appreciate that feature is, that i got two FHEM home automation servers running and want to get the data on both servers.

Drum
Normal user
Posts: 300
Joined: 07 Feb 2016, 11:56

Re: More than one generic HTTP server IP possible?

#2 Post by Drum » 27 Sep 2016, 18:05

I don't think so, what is it you want to send?

chunter1
Normal user
Posts: 82
Joined: 22 Jan 2016, 22:40

Re: More than one generic HTTP server IP possible?

#3 Post by chunter1 » 28 Sep 2016, 13:08

It would be mainly temperature data and digital i/o states.

tozett
Normal user
Posts: 734
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: More than one generic HTTP server IP possible?

#4 Post by tozett » 29 Sep 2016, 10:06

consider using node-red as backend, that can distribute than on more...
there is info on this forum for going that way, if you like..

User avatar
moelski
Normal user
Posts: 161
Joined: 31 Aug 2016, 06:33
Location: Germany - NRW
Contact:

Re: More than one generic HTTP server IP possible?

#5 Post by moelski » 29 Sep 2016, 10:50

Could also be possible to write a new Controller which sends data to two destinations ...
regards
Dominik

uhrheber
Normal user
Posts: 22
Joined: 26 Sep 2016, 14:03

Re: More than one generic HTTP server IP possible?

#6 Post by uhrheber » 29 Sep 2016, 10:52

You could either use FHEM2FHEM to connect the two FHEM servers, or send the data to an MQTT broker first.
From there, an unlimited number of clients can get the data.

chunter1
Normal user
Posts: 82
Joined: 22 Jan 2016, 22:40

Re: More than one generic HTTP server IP possible?

#7 Post by chunter1 » 03 Oct 2016, 13:29

i know about MQTT broker and FHEM2FHEM solutions.
i tried both and absolutely don't like them.
either solution in my oppinion means unnecessary overhead, one more point of failure and increased maintainance.
the most simple, least complex and efficient solution would be the espeasy "data-source" sending the date to both servers seperately.
in sourcecode it should basically only be an array and a for-loop to be added?

Post Reply

Who is online

Users browsing this forum: No registered users and 80 guests