Hi Greg,

On Wed, May 06, 2020 at 01:01:24PM -0400, Greg Troxel wrote:
> Till Maas <[email protected]> writes:
> 
> > So a PC supports probably several Master Bricks, each master Brick
> > several Outdoor Weather Bricklets (they contain the wireless receiver)
> > or other sensors and each Outdoor Weather Bricklet supports 255 wireless
> > sensors and 255 wireless weather stations. The weather stations provide
> > wind speed, direction, gust, humidity, temperature and rain values. The
> > wireless sensors temperate and humidity.
> 
> I think the big question from the weewx viewpoint is "what is a weather
> station".

yes. If I understand correctly after also looking at Matthews link:

A weewx weather station consists of one driver and possibly multiple
services. It supports multiple temperature/humidity sensors but only one
rain/wind sensor.

> > Since I only have one weather station at the moment, I need to support
> > only one. But since the hardware supports more, I wonder how to do this
> > with weewx. It seems that the database schema does not have an ID for
> > different weather stations. So I guess each weewx instance/config file
> > is meant to accommodate only one weewx station. I guess this logical
> > weewx station could still consist of one Tinkerforge weather station and
> > multiple extra sensors because of fields like
> > "extraHumid1".."extraHumid8" in the schema. Are there some best
> > practices how to map those values in a driver from different sensors?
> 
> I'm not sure about best practice - it really depends on what those
> sensors are measuring and what they mean.
> 
> Let me ask you what you are trying to do with "multiple weather
> stations" in the tinkerforge sense.  Do you want to report them as
> separate logical things?  Average them?

I don't know. I don't have a use case for myself, therefore I was
wondering if it makes sense to support more than one of them. Since
there is no way to store most of it's data in weewx (rain & wind), it
does not seem to make sense. Not sure, if someone might care about wind
speed/direction in different height or points in an area.

> Why does it matter that tinkerforge calls things that also do rain/wind
> "weather station" while they call things that only do
> temperature/humidify "sensor"?  In what fundamental sense are they
> really different?

Since weewx supports several temperature/humidity sensors, it seems it
makes sense to support several of those Tinkerforge sensors in one
driver instance but only one Tinkerforge weather station.

> You could write a driver for tinkerforge stuff with a notion that all of
> the tinkerforge sensors (what they call sensors and what they call
> stations both) are available behind a single interface.
> 
> But, I think the real problem is that weewx's database schema, while of
> course flexible, is (inherited and) designed around the notion of
> storing an analyzing data from a traditional weather station, meaning
> one that captures the traditional in/out temp/humidity, pressure, rain,
> wind and perhaps also extra things like uv and a few more temp sensors.
> It sounds like you have a much grander vision of what you are
> measuring.   It might help to articulate what you see as an example
> system setup that goes beyond what's normal now.

I don't have a vision for myself because I borrowed only one
Tinkerforge weather station and I will probably also buy only one but
maybe some extra sensors, too.

> Hope this helps and wasn't too rambling.

Thank you, it helped me to get some clarity.

Till

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/20200507204836.GA25581%40genius.invalid.

Reply via email to