Weather Networks with different weather stations

[Stebi]

I have 3 weather stations (Weatherflow, Ecowitt and Davis Air Link) connected to my Meteobridge. How can I manage the data which is sent to the different weather networks? Is all the data going to the networks or just the primary station?

Greetings from Basel
Thomas

[Gyvate]

as far as I know it's always the data from the the primary station.
@admin: This could be a future feature to make this selectable for each weather service if one has more stations ....

so far the only workaround (which I also use) I see is that you send the data of the other stations via a http request (Services, events).
You will have to figure out what that string to be sent - including the main interface address for the service - would be like.

For your Ecowitt station useful information for the posting strings could be found under
https://loxwiki.atlassian.net/wiki/spac ... ic+version
(in the forwarding to weather services section)

if you have another little (or bigger e.g. a NAS) 24/7 running server like a RaspberryPi or so,
you could even install there the FOSHKplugin, have your console post to it via custom server (Ecowitt station !) and have the FOSHKplugin spread/distribute the data to the different weather services where you want your Ecowitt station data to be sent to.

While Meteobridge is limited to 20 events, FOSHKplugin can use up to 100 events/forwards (if 20 becomes a limitation)

[wvdkuil]

I have 3 weather stations (Weatherflow, Ecowitt and Davis Air Link) connected to my Meteobridge. How can I manage the data which is sent to the different weather networks? Is all the data going to the networks or just the primary station?

Greetings from Basel
Thomas

Normall the primary sensors are used.
F.i. with your 3 stations toy have three temp/hum/pressure sensors, on for each station.
normally the system assumes you want to use the first station as your primary.
But on the Station -> Mapping tab you find a dropdown selecter with all sensors Select one and assign it as your primary sensor.

Wim

[Gyvate]

that's in principle true, but it doesn't solve the issue that only one station at a time can be chosen for all the weather networks - howsoever you match the sensors.
If e.g. you want station 0 (primary) to post to WU and station 1 to post to AWEKAS and station 2 to post to WOW, you cannot do this with matching.

With matching you can only replace one station by another or(, if this is wanted,) mix values from different stations into one post

right now you only can create a http post with the sensors of the station you want to send to the target service, and then, using the example from above, post in separate http posts th1!0temp etc. to AWEKAS and th2!0temp etc. to WOW - and for station 0 (th0!0temp etc.) you choose the service offered in the weather network tab (or do some matching for the standard networks and then cover the other stations with http posts).

A (future) option that you can choose the station data to be used for each service in the Weather Nets tab would solve the issue (as long as you don't want to send more than one station to the same weather service).

[admin]

When I decide to support multiple accounts of a each weather network then to select which station to take the data from will also be on the agenda. However, currently the development effort coming along with this does push the idea a bit more into the future.

[Gyvate]

When I decide to support multiple accounts of a each weather network then to select which station to take the data from will also be on the agenda. However, currently the development effort coming along with this does push the idea a bit more into the future.

I suggest a two-step approach

1. allow the station choice for each weather network (one account only)
example: WU by station 0, AWEKAS by station 1, WOW by station 2 or WU and WOW by station 0, AWEKAS by station 2 ...
(only configured stations selectable)

2. extend it to weather service by selectable station to more than one account
(max account = max # of stations; only configured stations selectable)
example: (step 1 already completed)
station 0 to WU account #1, station 1 to WU account #2 etc.

step 1 would already solve quite a few scenarios and would possibly be not so much work
step 2 would admittedly be more effort to implement