Feature Request

[karlch...@googlemail.com]

1. Native support of meteotemplate.

I guess many Users are using meteotemplate because its donationware and a really nice piece of software. Is there any plan or possibility to implent native support in weewx?

2. Debug Screen with data from the weather station

Maybe i am dumb - but can’t find any possibility to view the „raw“ data from my weather station in the console - especially during the first setup or recovery after some major changes it could help to find my own mistakes ;)

3. Graphical installer (Terminal and GUI based)

For the most users its really a little bit to hard to change things here and there in some python scripts - but the most users don’t need that much to change. So i guess a simple and a pro config with a setup wizard could improve the user experience and also the installations around the globe. 

 

4. Easy support of different other sources

We want to add some additional sensors to weewx - but not directly connected to the raspberry pi - we want to use some wifi connected arduinos. But we don’t know how to setup these in weewx so that this data will be stored in the database and forwarded to some cloud services...

 

[vince]

On Wednesday, September 23, 2020 at 7:20:46 AM UTC-7, karlch...@googlemail.com wrote:

3. Graphical installer (Terminal and GUI based)

For the most users its really a little bit to hard to change things here and there in some python scripts - but the most users don’t need that much to change. So i guess a simple and a pro config with a setup wizard could improve the user experience and also the installations around the globe. 

 

 

If you install the packaged version of weewx it asks all the right questions already.  Why require a GUI ?   That opens up a lot of complexity and potential security risk to get the GUI the permissions to write the output file(s) out.

Each extension or driver could potentially require different customization (example - Belchertown skin and WeatherFlow UDP driver tend to require a lot of editing in weewx.conf).   There is probably no reasonable way to handle this generically that I can think of.  Ultimately the user needs to be able to edit a simple text file.  That's not much to ask.

4. Easy support of different other sources

We want to add some additional sensors to weewx - but not directly connected to the raspberry pi - we want to use some wifi connected arduinos. But we don’t know how to setup these in weewx so that this data will be stored in the database and forwarded to some cloud services...

 

There have been many posts for how to get data into and out of weewx from a variety of sensors.  Look around in the wiki and group archive a bit.  Typically people import a flat file (csv perhaps) or use MQTT for this.

 

[Tom Keffer]

1. Not sure what you mean by "native support." There is an uploader extension.

2. What are you thinking that would be different from running weewx directly from the command line? This prints out the raw data coming off the driver, albeit after running through the engine's pipeline.

3. While this would be nice, it also complicates the porting problem, and can use a huge amount of personpower. I'd rather focus on improving reliability, and, especially, adaptability of WeeWX. It's goal has always been to support the hobbyist / enthusiast who wants to try new stuff. It was never intended as a consumer-grade piece of software, although it has become that.

4. Usually this is done using an MQTT broker. There are many examples of this in the Wiki and user forums.

-tk

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e913164a-231b-4f90-ac07-294f3b135a48n%40googlegroups.com.