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". I think the answer at the high level is "a collection of sensors that are more or less in one place", and this is what is reflected in a single database. In this high level view, sensors that are not in the same package or from the same vendor can still be aggregated. >From the driver viewpoint, a weather station is a thing you can talk to that provides some number of sensors. It may or may not have multiple pieces and wireless -- the point is that there is a common protocol to talk to it. And, from the weewx viewpoint, there is "driver" which is the main thing, and "service" which are extra things. I would suggest that the driver/service distinction is arbitrary and becoming less important. The world used to be "buy a weather station (collection of sensors with an interface)" and "hook it up to weewx to manage it". Now, gluing together a system of a bunch of sensors that did not necesssily come together is more common. You are using "weather station" to mean "a thing that has some number of sensors that sends data to a bricklet", which is not quite the same as the weewx view. As an extreme example, I have a Davis Vantage Pro2 and ingest that into weewx, entirely normally. I have a friend with a Pro2, some 10s of km away, and he runs weewx (also normally) and publishes data to mqtt. I have a home assistant instance that shows both of these (no weewx involved, other than that both weewx instances publish). Now, I could use a mqtt service to put the other station's temps/etc. into my weewx database so that I would have "two weather stations" in my weewx instance. But this really seems contrary to the weewx way of managing a single logical "weather station" which may include some extra sensors, perhaps more temps, perhaps things like PM2.5 not included in the base system. > 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? 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? 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. Hope this helps and wasn't too rambling. -- 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/rmiimh9knff.fsf%40s1.lexort.com.
