I've just been going through all the html templates and other foundational files. It appears I can extend the weewx web page-set at will, changing appearance through the css configurations, adding pages, and so on. I'd like to recreate most of the wview presentation pages within reason, for my own consumption only. weewx is GREAT, but its certainly a stripped down version of wview - which I realize helps to make it small and fast.
One of the first things I'd like to do is re-create the wviewmgmt screens, especially the front status page. It'd be a good way to extend my python knowledge and a good winter project overall, assuming I have the necessary grey matter. The only issues I'd have to take account of are my changes would be overwritten with each weewx update/upgrade; and obviously making changes to the weewx package files means I am my own support when problems arise. Am I missing something that would prevent such a project, or make it difficult? Or is this effort already underway by you, Tom, or the weewx user-base? I appreciate expanding the app may not be in the cards, as doing so might make it bigger and slower than your original plan had in mind. On Friday, 17 November 2017 17:17:54 UTC-7, Tom Keffer wrote: > > Go for it! > > WeeWX will add some tables to your wview sqlite database. These are "daily > summaries." It will take a while (how long depends on processing power) to > "backfill" these summaries from the archive database, but it will keep you > informed as to what is going on. I doubt there will be an issue with that, > but you might want to make a copy of the wview database, rather than simply > moving it over. > > -tk > > > On Fri, Nov 17, 2017 at 3:12 PM, Rod in Edm <[email protected] <javascript:>> > wrote: > >> Hey Vince, thanks for the help !! >> >> I've got almost 3 years of archived weather data in my wview files, all >> of it in sql-lite3 databases and I'd like to pull it all into weewx (wth - >> in for a penny, in for a pound). My Davis Vantage Pro 2 wireless station is >> connected to computer via USB cable through Davis' datalogger-dongle. >> wview is currently doing 30sec sensor polling, 60sec data push intervals, >> and 5 min data archiving; html file creation for local browsing; and 5min >> FTP of html files to my ISP website for public viewing. >> >> My uninformed plan before asking for advice was simply to: >> - stop weewx-sim >> - dump the simulated data files completely (essentially return weewx to >> its default install state) >> - as necessary, reconfigure weewx for location, station type, etc etc >> - stop wview live-polling and give it a few seconds to close files and >> clean house before shutting down >> - make sure the weewx interface is set to serial and device to >> /dev/ttyUSB0 >> - import wview data into weewx >> - start up weewx >> - as you say, monitor the crap out of the syslog entries >> >> weewx is already set up to run as a daemon (deb pkg install), so just >> rebooting the machine should tell me if I've covered all the bases or >> bolloxed it up. >> >> I was just concerned that there might be "undocumented" or >> "mis-documented" surprises in the wview->weewx import process. I'll be >> making backups of all the wview data files before doing any importing, as >> well as the default weewx files - so a mistake won't be totally terminal. >> But one small mess leads to another in linux, and before you know it a >> from-scratch-reinstall-of-image to SD card from Etcher starts to become >> appealing. Don't want to go there. >> >> Anything else I should considering before launching? >> Rod >> >> >> On Thursday, 16 November 2017 23:34:29 UTC, vince wrote: >>> >>> On Thursday, November 16, 2017 at 2:34:26 PM UTC-8, Rod in Edm wrote: >>>> >>>> Forgot to ask - once I'm ready to switch from the weewx simulator to >>>> the actual Davis Vantage Pro 2 station, do I need to purge the simulated >>>> data before starting polling with real data? >>>> >>>> >>> yup, almost certainly - there are a zillion threads that have been >>> posted here before re: how to do it, but the 'right way(s)' depend on >>> whether you have pre-existing data you want to keep and the like, as well >>> as whether you're sqlite3 or mysql for your db in weewx. You might get >>> away with something as simple as dropping the summary tables and cleaning >>> out all the archive records after a certain datestamp. We'd need to know >>> more info to provide more help than that I think. >>> >>> You mentioned you have a Davis, which assuming you have their datalogger >>> means you have about a week's worth of data possibly in that. Weewx will >>> catch up gracefully when you switch to the real station. Cool feature. >>> >>> You can certainly import your wview data into weewx. Presumably you've >>> tried that already (using the simulator to append fake 'current' data to >>> whatever starting point you had from wview). If so, you've battled >>> through most of the transition stuff already, so you'd just need to do a >>> little cleanup to get the simulator data out of the archive and let weewx >>> rebuild the NOAA files and summary tables for you. Notionally it's >>> something like: >>> >>> - stop weewx >>> - delete records from the archive newer than some timestamp (to >>> delete your simulated data) >>> - probably drop the summary tables, which would be recreated for you >>> automatically >>> - probably remove the most recent NOAA month+year files, which again >>> should recreate for you >>> - switch to the Vantage driver >>> - start weewx >>> - monitor the heck out of your syslog :-) >>> >>> But the stuff above is just notional. We'd need more info to get you a >>> more solid list. >>> >>> >>> >>> -- >> 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 [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
