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. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/0a8ca782-b997-4032-8608-f16ae3b499deo%40googlegroups.com.
