[weewx-user] Re: Version 4.7.0
Just upgraded my macOS and FreeBSD weather stations to 4.7 and all is good. On Tuesday, March 1, 2022 at 3:57:08 PM UTC-8 tke...@gmail.com wrote: > This version fixes a bunch of minor things, as well as introduces some > minor new features. > > Change log: > > Introduced new option "generate_once". If True, templates will be generated > only on the first run of the reporting engine. Thanks to user Rich! PR #748. > > Added option wee_device --current for vantage. > > Fixed two typos in the Standard skin. > > Fixed spelling mistakes in the Norwegian translations. Thanks to Aslak! > PR#746 > > Supply a sensible default context for group_deltatime when no context has been > specified. > > If windGustDir is missing, extract a value from the accumulators. > > Fixed typo that shows itself if no [Labels]/[[Generic]] section is supplied. > Fixes issue #752. > > Fixed calculation of field "bar_reduction" for Vantage type 2 LOOP packets. > > Fix problem that prevents windSpeed and windDir from being displayed in > the RSS feed. Fixes issue #755. > > -- 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/7f02e897-ca79-4834-8dc0-3fd72524cbb4n%40googlegroups.com.
Re: [weewx-user] Will AC powered Davis transmitter attract lightning?
I don't know what lines you have running to your anemometer, but we have a number of elevated outdoor PoE WiFi APs and we use the Ubiquiti ethernet surge suppressors on the RJ45 / Cat 5e cables. About $12 from Amazon. They are consumables. One time use, then buy another. But it could save your PoE or other power source. On Sunday, April 18, 2021 at 4:44:38 PM UTC-7 etji...@gmail.com wrote: > Nothing specifically attracts lightning. Generally the tallest object in > an area is more prone to be hit. This is regardless of what it is made out > of. That said, if lightning did hit your anemometer, the surge will travel > through whatever it finds that conducts electricity, including data lines > and power lines. It's a good idea to make sure your setup is properly > grounded. That won't 100 percent protect you from a direct hit, but it can > save you in the event of a close strike with "fringe" effects. > > Hope this helps. > > Ernie > > On Sun, Apr 18, 2021 at 4:12 PM Chris Alemany wrote: > >> Hi all, >> Apologies that this is not strictly weewx related but I'm hoping the >> combined experience here will help. >> My solar powered davis transmitter that I use only for my anemometer >> appears to have failed so I am looking at replacing it. It is on my roof >> and the anemometer is the highest point. I do have power available nearby >> now but I'm worried I'll be creating a lightning rod if I go with the AC >> option. >> It is a very exposed spot, the solar transmitter lasted 8 years. >> Thoughts? >> >> Cheers >> Chris >> Sent from my iPad >> >> -- >> 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/5C5931A8-D48E-4472-A2E6-BC54BD6071D5%40gmail.com >> . >> > -- 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/34f09617-bbcb-4188-9c5e-32973e9b3438n%40googlegroups.com.
Re: [weewx-user] Having trouble installing on Mac
What do you see when you run this command from the terminal? └─[$] <> tail -f -n 10 /var/log/weewx.log On Tuesday, February 9, 2021 at 5:05:16 AM UTC-8 PAK wrote: > > Thanks for the link. > > Still trying to get it installed on the Mac. I seem to be close. Not > getting any errors it seems but I don't have the directory: - > *file:///Users/Shared/weewx/public_html/* and the file > *file:///Users/Shared/weewx/public_html/index.html.* > > So I think it's running in the background but I need that folder and file > to see it. Is that right - you type that into the browser and it launches? > > Thanks again, > Peter. > On Monday, February 8, 2021 at 10:02:02 PM UTC+10 mscham...@gmail.com > wrote: > >> >> >> On Feb 5, 2021, at 5:06 AM, Graham Eddy wrote: >> >> did you run bin/weewxd as root, to have needed permissions for creating >> /var/log/weewx.log? >> >> as an aside, you are thinking of moving weewx from mac to rpi. *do it*. >> macos continues to diverge from its linux roots into strange lands opaque >> to mere mortals e.g. i found daemons via launchd becoming impossible >> through successive macos releases without arcane knowledge, and abandoned >> macos 6 months ago. my mac mini now runs ubuntu in a DMZ and weewx runs >> wonderfully on an rpi 4B using raspian os. and i got a gw1000 to run as a >> service in parallel with my vp2 on same weewx instance >> (my macos laptops are still great - i just recommend against macos for >> server) >> >> >> Since when does macOS have Linux roots? macOS is derived from BSD Unix. >> However, Apple has locked system directories down in some annoying ways. >> >> I do have an unofficial MacPorts Portfile for weewx: >> >> https://github.com/Schamschula/macports/tree/master/science/weewx >> >> Not well tested, as I run weewx under FreeBSD. >> >> Marius >> -- >> Marius Schamschula >> >> >> >> >> -- 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/99bbdbd3-1dfc-4fdd-8bb7-e3937a89ce06n%40googlegroups.com.
Re: [weewx-user] yearwindvec calculation problem
Solved. After rebuilding daily, yearwindvec scale is back to normal. Thanks, Tom. On Friday, January 22, 2021 at 6:29:20 PM UTC-8 jerry...@gmail.com wrote: > Tried running rebuild a second time. Finished in 1 second and reported it > was done. > > └─[$] <> sudo ../bin/wee_database --rebuild-daily > Password: > Using configuration file /Users//weewx/weewx.conf > Using database binding 'wx_binding', which is bound to database > 'archive_sqlite' > All daily summaries will be rebuilt. > Proceed (y/n)? y > Rebuilding daily summaries in database 'weewx.sdb' ... > Daily summaries up to date in 'weewx.sdb' > > I'll let it run overnight again and see what happens. > > On Friday, January 22, 2021 at 5:56:48 PM UTC-8 jerry...@gmail.com wrote: > >> Would you recommend trying to run repair first? >> >> On Friday, January 22, 2021 at 5:54:51 PM UTC-8 tke...@gmail.com wrote: >> >>> Can you try it again? >>> >>> I have to confess, I've never tried this under MacOS. >>> >>> On Fri, Jan 22, 2021 at 5:51 PM jerry...@gmail.com >>> wrote: >>> >>>> mmm. --drop-daily ran successfully, but --rebuild-daily ran for 10 min >>>> or so, then hung on 2020-12-02 >>>> ┌─[@weather] - [~/weewx/archive] - [Fri Jan 22, 16:11] >>>> └─[$] <> sudo ../bin/wee_database --drop-daily >>>> Using configuration file /Users//weewx/weewx.conf >>>> Using database binding 'wx_binding', which is bound to database >>>> 'archive_sqlite' >>>> Proceeding will delete all your daily summaries from database >>>> 'weewx.sdb' >>>> Are you sure you want to proceed (y/n)? y >>>> Dropping daily summary tables from 'weewx.sdb' ... >>>> Daily summary tables dropped from database 'weewx.sdb' in 1.43 seconds >>>> ┌─[@weather] - [~/weewx/archive] - [Fri Jan 22, 16:11] >>>> └─[$] <> sudo ../bin/wee_database --rebuild-daily >>>> Using configuration file /Users//weewx/weewx.conf >>>> Using database binding 'wx_binding', which is bound to database >>>> 'archive_sqlite' >>>> All daily summaries will be rebuilt. >>>> Proceed (y/n)? y >>>> Rebuilding daily summaries in database 'weewx.sdb' ... >>>> Records processed: 883000; time: 2020-12-02 07:05:00 PST (1606921500) >>>> >>>> >>>> On Friday, January 22, 2021 at 4:21:48 PM UTC-8 tke...@gmail.com wrote: >>>> >>>>> Thanks. >>>>> >>>>> On Fri, Jan 22, 2021 at 4:04 PM jerry...@gmail.com >>>>> wrote: >>>>> >>>>>> I upgraded from v4.2 and installed v4.3b(final beta) on Jan 2, then >>>>>> upgraded to the v4.3 release on Jan 4 >>>>>> >>>>>> On Friday, January 22, 2021 at 3:34:09 PM UTC-8 tke...@gmail.com >>>>>> wrote: >>>>>> >>>>>>> Jerry, two other questions: >>>>>>> >>>>>>> 1. What version of WeeWX did you use before moving to V4.3? >>>>>>> 2. When did you do the upgrade? >>>>>>> >>>>>>> On Fri, Jan 22, 2021 at 3:24 PM Tom Keffer wrote: >>>>>>> >>>>>>>> I see the problem, but I'm not quite sure what caused it. I'll have >>>>>>>> to do some experimentation. >>>>>>>> >>>>>>>> In the meantime, you can fix things by rebuilding the daily >>>>>>>> summaries. >>>>>>>> >>>>>>>> *sudo wee_database --drop-daily* >>>>>>>> *sudo wee_database --rebuild-daily* >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Jan 22, 2021 at 3:13 PM jerry...@gmail.com < >>>>>>>> jerry...@gmail.com> wrote: >>>>>>>> >>>>>>>>> python 3.9.1 issues corrected. No effect on yearwindvec. Here's >>>>>>>>> sql dump >>>>>>>>> └─[$] <> sqlite3 weewx.sdb >>>>>>>>> SQLite version 3.32.3 2020-06-18 14:16:19 >>>>>>>>> Enter ".help" for usage hints. >>>>>>>>> sqlite> select dateTime, >>>>>>>>> datetime(dateTime,'unixepoch','localtime'), xsum, ysum, dirsumtime >>>>>>>>> from >>>>>
Re: [weewx-user] yearwindvec calculation problem
Tried running rebuild a second time. Finished in 1 second and reported it was done. └─[$] <> sudo ../bin/wee_database --rebuild-daily Password: Using configuration file /Users//weewx/weewx.conf Using database binding 'wx_binding', which is bound to database 'archive_sqlite' All daily summaries will be rebuilt. Proceed (y/n)? y Rebuilding daily summaries in database 'weewx.sdb' ... Daily summaries up to date in 'weewx.sdb' I'll let it run overnight again and see what happens. On Friday, January 22, 2021 at 5:56:48 PM UTC-8 jerry...@gmail.com wrote: > Would you recommend trying to run repair first? > > On Friday, January 22, 2021 at 5:54:51 PM UTC-8 tke...@gmail.com wrote: > >> Can you try it again? >> >> I have to confess, I've never tried this under MacOS. >> >> On Fri, Jan 22, 2021 at 5:51 PM jerry...@gmail.com >> wrote: >> >>> mmm. --drop-daily ran successfully, but --rebuild-daily ran for 10 min >>> or so, then hung on 2020-12-02 >>> ┌─[@weather] - [~/weewx/archive] - [Fri Jan 22, 16:11] >>> └─[$] <> sudo ../bin/wee_database --drop-daily >>> Using configuration file /Users//weewx/weewx.conf >>> Using database binding 'wx_binding', which is bound to database >>> 'archive_sqlite' >>> Proceeding will delete all your daily summaries from database 'weewx.sdb' >>> Are you sure you want to proceed (y/n)? y >>> Dropping daily summary tables from 'weewx.sdb' ... >>> Daily summary tables dropped from database 'weewx.sdb' in 1.43 seconds >>> ┌─[@weather] - [~/weewx/archive] - [Fri Jan 22, 16:11] >>> └─[$] <> sudo ../bin/wee_database --rebuild-daily >>> Using configuration file /Users//weewx/weewx.conf >>> Using database binding 'wx_binding', which is bound to database >>> 'archive_sqlite' >>> All daily summaries will be rebuilt. >>> Proceed (y/n)? y >>> Rebuilding daily summaries in database 'weewx.sdb' ... >>> Records processed: 883000; time: 2020-12-02 07:05:00 PST (1606921500) >>> >>> >>> On Friday, January 22, 2021 at 4:21:48 PM UTC-8 tke...@gmail.com wrote: >>> >>>> Thanks. >>>> >>>> On Fri, Jan 22, 2021 at 4:04 PM jerry...@gmail.com >>>> wrote: >>>> >>>>> I upgraded from v4.2 and installed v4.3b(final beta) on Jan 2, then >>>>> upgraded to the v4.3 release on Jan 4 >>>>> >>>>> On Friday, January 22, 2021 at 3:34:09 PM UTC-8 tke...@gmail.com >>>>> wrote: >>>>> >>>>>> Jerry, two other questions: >>>>>> >>>>>> 1. What version of WeeWX did you use before moving to V4.3? >>>>>> 2. When did you do the upgrade? >>>>>> >>>>>> On Fri, Jan 22, 2021 at 3:24 PM Tom Keffer wrote: >>>>>> >>>>>>> I see the problem, but I'm not quite sure what caused it. I'll have >>>>>>> to do some experimentation. >>>>>>> >>>>>>> In the meantime, you can fix things by rebuilding the daily >>>>>>> summaries. >>>>>>> >>>>>>> *sudo wee_database --drop-daily* >>>>>>> *sudo wee_database --rebuild-daily* >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Fri, Jan 22, 2021 at 3:13 PM jerry...@gmail.com < >>>>>>> jerry...@gmail.com> wrote: >>>>>>> >>>>>>>> python 3.9.1 issues corrected. No effect on yearwindvec. Here's >>>>>>>> sql dump >>>>>>>> └─[$] <> sqlite3 weewx.sdb >>>>>>>> SQLite version 3.32.3 2020-06-18 14:16:19 >>>>>>>> Enter ".help" for usage hints. >>>>>>>> sqlite> select dateTime, >>>>>>>> datetime(dateTime,'unixepoch','localtime'), xsum, ysum, dirsumtime >>>>>>>> from >>>>>>>> archive_day_wind where dateTime>1606780800; >>>>>>>> 1606809600|2020-12-01 >>>>>>>> 00:00:00|-130203.553519314|151249.611011778|288 >>>>>>>> 1606896000|2020-12-02 >>>>>>>> 00:00:00|-52187.9947583369|334558.809337536|288 >>>>>>>> 1606982400|2020-12-03 >>>>>>>> 00:00:00|-153080.843814849|234123.104596637|288 >>>>>>>> 1607068800|2020-12-04 >>>>>>>> 00:00
Re: [weewx-user] yearwindvec calculation problem
Would you recommend trying to run repair first? On Friday, January 22, 2021 at 5:54:51 PM UTC-8 tke...@gmail.com wrote: > Can you try it again? > > I have to confess, I've never tried this under MacOS. > > On Fri, Jan 22, 2021 at 5:51 PM jerry...@gmail.com > wrote: > >> mmm. --drop-daily ran successfully, but --rebuild-daily ran for 10 min >> or so, then hung on 2020-12-02 >> ┌─[@weather] - [~/weewx/archive] - [Fri Jan 22, 16:11] >> └─[$] <> sudo ../bin/wee_database --drop-daily >> Using configuration file /Users//weewx/weewx.conf >> Using database binding 'wx_binding', which is bound to database >> 'archive_sqlite' >> Proceeding will delete all your daily summaries from database 'weewx.sdb' >> Are you sure you want to proceed (y/n)? y >> Dropping daily summary tables from 'weewx.sdb' ... >> Daily summary tables dropped from database 'weewx.sdb' in 1.43 seconds >> ┌─[@weather] - [~/weewx/archive] - [Fri Jan 22, 16:11] >> └─[$] <> sudo ../bin/wee_database --rebuild-daily >> Using configuration file /Users//weewx/weewx.conf >> Using database binding 'wx_binding', which is bound to database >> 'archive_sqlite' >> All daily summaries will be rebuilt. >> Proceed (y/n)? y >> Rebuilding daily summaries in database 'weewx.sdb' ... >> Records processed: 883000; time: 2020-12-02 07:05:00 PST (1606921500) >> >> >> On Friday, January 22, 2021 at 4:21:48 PM UTC-8 tke...@gmail.com wrote: >> >>> Thanks. >>> >>> On Fri, Jan 22, 2021 at 4:04 PM jerry...@gmail.com >>> wrote: >>> >>>> I upgraded from v4.2 and installed v4.3b(final beta) on Jan 2, then >>>> upgraded to the v4.3 release on Jan 4 >>>> >>>> On Friday, January 22, 2021 at 3:34:09 PM UTC-8 tke...@gmail.com wrote: >>>> >>>>> Jerry, two other questions: >>>>> >>>>> 1. What version of WeeWX did you use before moving to V4.3? >>>>> 2. When did you do the upgrade? >>>>> >>>>> On Fri, Jan 22, 2021 at 3:24 PM Tom Keffer wrote: >>>>> >>>>>> I see the problem, but I'm not quite sure what caused it. I'll have >>>>>> to do some experimentation. >>>>>> >>>>>> In the meantime, you can fix things by rebuilding the daily summaries. >>>>>> >>>>>> *sudo wee_database --drop-daily* >>>>>> *sudo wee_database --rebuild-daily* >>>>>> >>>>>> >>>>>> >>>>>> On Fri, Jan 22, 2021 at 3:13 PM jerry...@gmail.com < >>>>>> jerry...@gmail.com> wrote: >>>>>> >>>>>>> python 3.9.1 issues corrected. No effect on yearwindvec. Here's >>>>>>> sql dump >>>>>>> └─[$] <> sqlite3 weewx.sdb >>>>>>> SQLite version 3.32.3 2020-06-18 14:16:19 >>>>>>> Enter ".help" for usage hints. >>>>>>> sqlite> select dateTime, datetime(dateTime,'unixepoch','localtime'), >>>>>>> xsum, ysum, dirsumtime from archive_day_wind where dateTime>1606780800; >>>>>>> 1606809600|2020-12-01 00:00:00|-130203.553519314|151249.611011778|288 >>>>>>> 1606896000|2020-12-02 00:00:00|-52187.9947583369|334558.809337536|288 >>>>>>> 1606982400|2020-12-03 00:00:00|-153080.843814849|234123.104596637|288 >>>>>>> 1607068800|2020-12-04 00:00:00|-99420.8960079433|191113.904386128|288 >>>>>>> 1607155200|2020-12-05 >>>>>>> 00:00:00|-190256.166535543|-63997.1159412606|288 >>>>>>> 1607241600|2020-12-06 00:00:00|-34666.8634217707 <(863)%20421-7707> >>>>>>> |-2021.71578460231|288 >>>>>>> 1607328000|2020-12-07 00:00:00|30124.3625862335|579428.027105184|288 >>>>>>> 1607414400|2020-12-08 00:00:00|-190910.758642127|109709.290467476|288 >>>>>>> 1607500800|2020-12-09 00:00:00|117876.621596901|360564.616051966|288 >>>>>>> 1607587200|2020-12-10 00:00:00|-110801.296843873|-95429.4246456933 >>>>>>> <(424)%20645-6933>|288 >>>>>>> 1607673600|2020-12-11 00:00:00|-43729.9472371972 <(947)%20237-1972> >>>>>>> |-309888.485094482|288 >>>>>>> 160776|2020-12-12 00:00:00|220205.009420536|41034.5716043916 >>>>>>> <(571)%20604-3916>|288 >>>>>>> 1607846400|2020-12-
Re: [weewx-user] yearwindvec calculation problem
mmm. --drop-daily ran successfully, but --rebuild-daily ran for 10 min or so, then hung on 2020-12-02 ┌─[@weather] - [~/weewx/archive] - [Fri Jan 22, 16:11] └─[$] <> sudo ../bin/wee_database --drop-daily Using configuration file /Users//weewx/weewx.conf Using database binding 'wx_binding', which is bound to database 'archive_sqlite' Proceeding will delete all your daily summaries from database 'weewx.sdb' Are you sure you want to proceed (y/n)? y Dropping daily summary tables from 'weewx.sdb' ... Daily summary tables dropped from database 'weewx.sdb' in 1.43 seconds ┌─[@weather] - [~/weewx/archive] - [Fri Jan 22, 16:11] └─[$] <> sudo ../bin/wee_database --rebuild-daily Using configuration file /Users//weewx/weewx.conf Using database binding 'wx_binding', which is bound to database 'archive_sqlite' All daily summaries will be rebuilt. Proceed (y/n)? y Rebuilding daily summaries in database 'weewx.sdb' ... Records processed: 883000; time: 2020-12-02 07:05:00 PST (1606921500) On Friday, January 22, 2021 at 4:21:48 PM UTC-8 tke...@gmail.com wrote: > Thanks. > > On Fri, Jan 22, 2021 at 4:04 PM jerry...@gmail.com > wrote: > >> I upgraded from v4.2 and installed v4.3b(final beta) on Jan 2, then >> upgraded to the v4.3 release on Jan 4 >> >> On Friday, January 22, 2021 at 3:34:09 PM UTC-8 tke...@gmail.com wrote: >> >>> Jerry, two other questions: >>> >>> 1. What version of WeeWX did you use before moving to V4.3? >>> 2. When did you do the upgrade? >>> >>> On Fri, Jan 22, 2021 at 3:24 PM Tom Keffer wrote: >>> >>>> I see the problem, but I'm not quite sure what caused it. I'll have to >>>> do some experimentation. >>>> >>>> In the meantime, you can fix things by rebuilding the daily summaries. >>>> >>>> *sudo wee_database --drop-daily* >>>> *sudo wee_database --rebuild-daily* >>>> >>>> >>>> >>>> On Fri, Jan 22, 2021 at 3:13 PM jerry...@gmail.com >>>> wrote: >>>> >>>>> python 3.9.1 issues corrected. No effect on yearwindvec. Here's sql >>>>> dump >>>>> └─[$] <> sqlite3 weewx.sdb >>>>> SQLite version 3.32.3 2020-06-18 14:16:19 >>>>> Enter ".help" for usage hints. >>>>> sqlite> select dateTime, datetime(dateTime,'unixepoch','localtime'), >>>>> xsum, ysum, dirsumtime from archive_day_wind where dateTime>1606780800; >>>>> 1606809600|2020-12-01 00:00:00|-130203.553519314|151249.611011778|288 >>>>> 1606896000|2020-12-02 00:00:00|-52187.9947583369|334558.809337536|288 >>>>> 1606982400|2020-12-03 00:00:00|-153080.843814849|234123.104596637|288 >>>>> 1607068800|2020-12-04 00:00:00|-99420.8960079433|191113.904386128|288 >>>>> 1607155200|2020-12-05 00:00:00|-190256.166535543|-63997.1159412606|288 >>>>> 1607241600|2020-12-06 00:00:00|-34666.8634217707 <(863)%20421-7707> >>>>> |-2021.71578460231|288 >>>>> 1607328000|2020-12-07 00:00:00|30124.3625862335|579428.027105184|288 >>>>> 1607414400|2020-12-08 00:00:00|-190910.758642127|109709.290467476|288 >>>>> 1607500800|2020-12-09 00:00:00|117876.621596901|360564.616051966|288 >>>>> 1607587200|2020-12-10 00:00:00|-110801.296843873|-95429.4246456933 >>>>> <(424)%20645-6933>|288 >>>>> 1607673600|2020-12-11 00:00:00|-43729.9472371972 <(947)%20237-1972> >>>>> |-309888.485094482|288 >>>>> 160776|2020-12-12 00:00:00|220205.009420536|41034.5716043916 >>>>> <(571)%20604-3916>|288 >>>>> 1607846400|2020-12-13 00:00:00|-244171.679762325|-169645.365425769|288 >>>>> 1607932800|2020-12-14 00:00:00|-102395.07323691|169918.397158235|288 >>>>> 1608019200|2020-12-15 00:00:00|-22417.9273202652|19293.1247338471|288 >>>>> 1608105600|2020-12-16 00:00:00|-139024.644156649|78612.9897242719 >>>>> <(989)%20724-2719>|288 >>>>> 1608192000|2020-12-17 00:00:00|-568165.92865951|130159.284577316|288 >>>>> 1608278400|2020-12-18 00:00:00|-27478.8703463201 <(870)%20346-3201> >>>>> |104361.205410177|288 >>>>> 1608364800|2020-12-19 00:00:00|36037.438769948|378529.578694131|288 >>>>> 1608451200|2020-12-20 00:00:00|60841.5285463173|560381.729354686|288 >>>>> 1608537600|2020-12-21 00:00:00|-69829.7825072144 <(782)%20507-2144> >>>>> |451146.231629289|288 >>>>> 1608624000|2020-12-22 00:00:00|12361.5448934334 <
Re: [weewx-user] yearwindvec calculation problem
I upgraded from v4.2 and installed v4.3b(final beta) on Jan 2, then upgraded to the v4.3 release on Jan 4 On Friday, January 22, 2021 at 3:34:09 PM UTC-8 tke...@gmail.com wrote: > Jerry, two other questions: > > 1. What version of WeeWX did you use before moving to V4.3? > 2. When did you do the upgrade? > > On Fri, Jan 22, 2021 at 3:24 PM Tom Keffer wrote: > >> I see the problem, but I'm not quite sure what caused it. I'll have to do >> some experimentation. >> >> In the meantime, you can fix things by rebuilding the daily summaries. >> >> *sudo wee_database --drop-daily* >> *sudo wee_database --rebuild-daily* >> >> >> >> On Fri, Jan 22, 2021 at 3:13 PM jerry...@gmail.com >> wrote: >> >>> python 3.9.1 issues corrected. No effect on yearwindvec. Here's sql >>> dump >>> └─[$] <> sqlite3 weewx.sdb >>> SQLite version 3.32.3 2020-06-18 14:16:19 >>> Enter ".help" for usage hints. >>> sqlite> select dateTime, datetime(dateTime,'unixepoch','localtime'), >>> xsum, ysum, dirsumtime from archive_day_wind where dateTime>1606780800; >>> 1606809600|2020-12-01 00:00:00|-130203.553519314|151249.611011778|288 >>> 1606896000|2020-12-02 00:00:00|-52187.9947583369|334558.809337536|288 >>> 1606982400|2020-12-03 00:00:00|-153080.843814849|234123.104596637|288 >>> 1607068800|2020-12-04 00:00:00|-99420.8960079433|191113.904386128|288 >>> 1607155200|2020-12-05 00:00:00|-190256.166535543|-63997.1159412606|288 >>> 1607241600|2020-12-06 00:00:00|-34666.8634217707 <(863)%20421-7707> >>> |-2021.71578460231|288 >>> 1607328000|2020-12-07 00:00:00|30124.3625862335|579428.027105184|288 >>> 1607414400|2020-12-08 00:00:00|-190910.758642127|109709.290467476|288 >>> 1607500800|2020-12-09 00:00:00|117876.621596901|360564.616051966|288 >>> 1607587200|2020-12-10 00:00:00|-110801.296843873|-95429.4246456933 >>> <(424)%20645-6933>|288 >>> 1607673600|2020-12-11 00:00:00|-43729.9472371972 <(947)%20237-1972> >>> |-309888.485094482|288 >>> 160776|2020-12-12 00:00:00|220205.009420536|41034.5716043916 >>> <(571)%20604-3916>|288 >>> 1607846400|2020-12-13 00:00:00|-244171.679762325|-169645.365425769|288 >>> 1607932800|2020-12-14 00:00:00|-102395.07323691|169918.397158235|288 >>> 1608019200|2020-12-15 00:00:00|-22417.9273202652|19293.1247338471|288 >>> 1608105600|2020-12-16 00:00:00|-139024.644156649|78612.9897242719 >>> <(989)%20724-2719>|288 >>> 1608192000|2020-12-17 00:00:00|-568165.92865951|130159.284577316|288 >>> 1608278400|2020-12-18 00:00:00|-27478.8703463201 <(870)%20346-3201> >>> |104361.205410177|288 >>> 1608364800|2020-12-19 00:00:00|36037.438769948|378529.578694131|288 >>> 1608451200|2020-12-20 00:00:00|60841.5285463173|560381.729354686|288 >>> 1608537600|2020-12-21 00:00:00|-69829.7825072144 <(782)%20507-2144> >>> |451146.231629289|288 >>> 1608624000|2020-12-22 00:00:00|12361.5448934334 <(544)%20893-4334> >>> |195530.536831909|288 >>> 1608710400|2020-12-23 00:00:00|308287.862067983|318022.906362218|288 >>> 1608796800|2020-12-24 00:00:00|38007.7631483106|282472.618348279|288 >>> 1608883200|2020-12-25 00:00:00|-17230.6374395907|-595796.408608539|288 >>> 1608969600|2020-12-26 00:00:00|-415239.498049725|-162860.386849611|288 >>> 1609056000|2020-12-27 00:00:00|171270.10413|240892.576970562|288 >>> 1609142400|2020-12-28 00:00:00|151298.874931467|336150.260498979|288 >>> 1609228800|2020-12-29 00:00:00|-44868.0593009285|72292.1745354697|288 >>> 1609315200|2020-12-30 00:00:00|-61615.9919150173|-370520.144783963|288 >>> 1609401600|2020-12-31 00:00:00|-124311.997370602|240223.949666045|288 >>> 1609488000|2021-01-01 00:00:00|-122534.326989786|-205708.575737604|288 >>> 1609574400|2021-01-02 00:00:00|21010.6867484957|-24099.0447729012|35271 >>> 1609660800|2021-01-03 00:00:00|-2516.97333745751|-176446.187437961|86400 >>> 1609747200|2021-01-04 00:00:00|-294785.350809428|-581263.937648814|86400 >>> 1609833600|2021-01-05 00:00:00|7324.35652411998|286084.756333686|86400 >>> 160992|2021-01-06 00:00:00|23910.1472753193|114969.099078222|86400 >>> 1610006400|2021-01-07 00:00:00|50945.657891678|228090.123829009|86400 >>> 1610092800|2021-01-08 00:00:00|-27376.7331763921|86157.7738906022 >>> <(773)%20890-6022>|86400 >>> 1610179200|2021-01-09 00:00:00|-85804.0547954349|85044.0362438775|86400 >>> 1610265600|2021-01-10 00:00:00|154585.773517962|153764.91
Re: [weewx-user] yearwindvec calculation problem
outTemp dewpoint [[[yeartempfeel]]] windchill heatindex [[[yeartempin]]] inTemp [[[yeartemp]]] yscale = None, None, 0.5 extraTemp1 extraTemp2 extraTemp3 [[[yearhum]]] outHumidity [[[yearrain]]] yscale = None, None, 0.02 plot_type = bar rain aggregate_type = sum # aggregate_interval = 2629800 # the length of a nominal month aggregate_interval = 604800# one week label = Rain (weekly total) [[[yearwind]]] windSpeed windGust aggregate_type = max [[[yearwinddir]]] yscale = 0.0, 360.0, 45.0 line_type = None marker_type = box marker_size = 2 windDir [[[yearwindvec]]] windvec plot_type = vector [[[yearradiation]]] radiation [[[yearuv]]] #yscale = 0, 16, 1 UV [[[yearrx]]] yscale = 0.0, 100.0, 25.0 rxCheckPercent [[[yearvolt]]] consBatteryVoltage heatingVoltage supplyVoltage referenceVoltage # Plot of high/low temperatures [[[yearhilow]]] hi data_type = outTemp aggregate_type = max label = High low data_type = outTemp aggregate_type = min label = Low Temperature # A progressive vector plot of daily gust vectors overlayed # with the daily wind average would look something like this: #[[[yeargustvec]]] #windvec #plot_type = vector #aggregate_type = avg #windgustvec #plot_type = vector #aggregate_type = max ### [Generators] # The list of generators that are to be run: generator_list = weewx.cheetahgenerator.CheetahGenerator, weewx.imagegenerator.ImageGenerator, weewx.reportengine.CopyGenerator On Thursday, January 21, 2021 at 2:36:48 PM UTC-8 jerry...@gmail.com wrote: > I just realized the python 3.9.1 path was wrong for pip and configobj > leading to mismatched versions. I corrected and will let it run overnight > and check the yearwindvec tomorrow. > > On Thursday, January 21, 2021 at 4:48:05 AM UTC-8 tke...@gmail.com wrote: > >> Hello, Jerry >> >> Two questions: >> >> 1. Can we see skin.conf for the plots? In particular, the section >> [ImageGenerator] in skins/Seasons/skin.conf. >> 2. Let's check the database. Assuming you are using sqlite, use the tool >> sqlite3 to take a look. You may have to install first. I don't know how to >> do that on macOS, but I presume homebrew can do it. Then >> >> cd /Users/Shared/weewx/archive >> sqlite3 weewx.sdb >> select dateTime, datetime(dateTime,'unixepoch','localtime'), xsum, ysum, >> dirsumtime from archive_day_wind where dateTime>1606780800; >> >> This will give us the ingredients to the plot for dates after 1-Dec-2020 >> >> >> >> >> >> On Wed, Jan 20, 2021 at 5:14 PM jerry...@gmail.com >> wrote: >> >>> I noticed that something recently has gone wrong with my year wind >>> vector graphic. The y axis is broken. This seems to have happened around >>> the transition to 4.3 >>> The monthwindvec graphic is ok >>> >>> [image: monthwindvec.png] >>> but the yearwindvec y axis is scaled about 100 times too large >>> [image: yearwindvec.png] >>> Going back to V 4.2 on Dec 31, everything was normal >>> [image: dec31yearwindvec.png] >>> This is running on macOS 10.15.7 (Catalina) with Python 3.9.1 >>> Any ideas where to look for fixes? >>> >>> -- >>> 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/9aa6d4a4-8d32-4709-b1e5-b11e24a9048fn%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/weewx-user/9
Re: [weewx-user] yearwindvec calculation problem
I just realized the python 3.9.1 path was wrong for pip and configobj leading to mismatched versions. I corrected and will let it run overnight and check the yearwindvec tomorrow. On Thursday, January 21, 2021 at 4:48:05 AM UTC-8 tke...@gmail.com wrote: > Hello, Jerry > > Two questions: > > 1. Can we see skin.conf for the plots? In particular, the section > [ImageGenerator] in skins/Seasons/skin.conf. > 2. Let's check the database. Assuming you are using sqlite, use the tool > sqlite3 to take a look. You may have to install first. I don't know how to > do that on macOS, but I presume homebrew can do it. Then > > cd /Users/Shared/weewx/archive > sqlite3 weewx.sdb > select dateTime, datetime(dateTime,'unixepoch','localtime'), xsum, ysum, > dirsumtime from archive_day_wind where dateTime>1606780800; > > This will give us the ingredients to the plot for dates after 1-Dec-2020 > > > > > > On Wed, Jan 20, 2021 at 5:14 PM jerry...@gmail.com > wrote: > >> I noticed that something recently has gone wrong with my year wind vector >> graphic. The y axis is broken. This seems to have happened around the >> transition to 4.3 >> The monthwindvec graphic is ok >> >> [image: monthwindvec.png] >> but the yearwindvec y axis is scaled about 100 times too large >> [image: yearwindvec.png] >> Going back to V 4.2 on Dec 31, everything was normal >> [image: dec31yearwindvec.png] >> This is running on macOS 10.15.7 (Catalina) with Python 3.9.1 >> Any ideas where to look for fixes? >> >> -- >> 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/9aa6d4a4-8d32-4709-b1e5-b11e24a9048fn%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/9aa6d4a4-8d32-4709-b1e5-b11e24a9048fn%40googlegroups.com?utm_medium=email_source=footer> >> . >> > -- 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/7296d4ef-6664-4ec6-a883-8c34746b6be6n%40googlegroups.com.
[weewx-user] yearwindvec calculation problem
I noticed that something recently has gone wrong with my year wind vector graphic. The y axis is broken. This seems to have happened around the transition to 4.3 The monthwindvec graphic is ok [image: monthwindvec.png] but the yearwindvec y axis is scaled about 100 times too large [image: yearwindvec.png] Going back to V 4.2 on Dec 31, everything was normal [image: dec31yearwindvec.png] This is running on macOS 10.15.7 (Catalina) with Python 3.9.1 Any ideas where to look for fixes? -- 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/9aa6d4a4-8d32-4709-b1e5-b11e24a9048fn%40googlegroups.com.
[weewx-user] Re: Upgrade PWS- WLL or WiFiLogger2?
Doh! Didn't work on macOS because I forgot the -u username:password argument. Safari used the login keychain so didn't need it. Much better solution for a shell script. On Wednesday, October 7, 2020 at 4:45:18 AM UTC-7 mh081...@gmail.com wrote: > Yes, works with the script from my above reply with curl on raspberry > pi4 debian 10 > > > > > > > jerry...@gmail.com schrieb am Dienstag, 6. Oktober 2020 um 21:01:31 UTC+2: > >> I'm curious if the curl command works to restart WiFiLogger2. I first >> tried using the lynx command line browser and it did not resolve the page >> correctly and didn't restart. I assumed that was because the restart page >> contains some javascript and lynx doesn't support javascript. I then >> switched to Safari, which has the downside of needing a GUI. >> >> So does curl work in the terminal script? That's a better solution if it >> works. >> >> On Tuesday, October 6, 2020 at 6:37:57 AM UTC-7 gary@gmail.com wrote: >> >>> Thanks for the Linux version of the script. >>> >>> On Tuesday, October 6, 2020 at 4:33:35 AM UTC-4 mh081...@gmail.com >>> wrote: >>> >>>> Thanks for the script. I changed it to be runnable from raspberry pi >>>> (Debian 10.4) >>>> >>>> #!/bin/sh >>>> # Shell script to restart the weatherLogger wifi device in the Davis >>>> Vantage Pro 2 in the Harbormaster Building >>>> # The weather logger tends to disconnect from network every 4 days >>>> causing weewx to crash in a waiting state >>>> # Currently set to run by rycweather as a cron job once a day at 8:07 >>>> am. >>>> # check to see if weatherLogger is connected on Harbormaster vlan >>>> /bin/ping -c 1 WiFiLogger.fritz.box >>>> if [ "$?" = "0" ]; then >>>> weatherLoggerStatus="weatherLogger is online" >>>> # Using curl >>>> curl --connect-timeout 5 --fail >>>> http://WiFiLogger.fritz.box/admin/restart >>>> # wait to launch and load javascript function of URL >>>> sleep 30 >>>> else >>>> weatherLoggerStatus="weatherLogger is OFFLINE" >>>> fi >>>> # Check weatherLogger is connected again >>>> /bin/ping -c 1 WiFiLogger.fritz.box >>>> if [ "$?" = "0" ]; then >>>> newWeatherLoggerStatus="weatherlogger is back online" >>>> else >>>> newWeatherLoggerStatus="weatherLogger is OFFLINE after restart" >>>> fi >>>> echo "$weatherLoggerStatus and after restart $newWeatherLoggerStatus" | >>>> sendemail -f mailadr...@mail.com -t mailad...@mail.com -u "WifiLogger >>>> Restart" -s mailserver.mail.com -xu "username" -xp "password" -o >>>> tls=yes -o message-content-type=auto >>>> exit >>>> >>>> >>>> jerry...@gmail.com schrieb am Dienstag, 6. Oktober 2020 um 09:36:22 >>>> UTC+2: >>>> >>>>> WifiLogger2 doesn't have an ssh port open, but it does respond on port >>>>> 80 to a restart command from http. Under macOS I use the shell script >>>>> command to open the Safair browser to the restart javascript command. >>>>> #!/bin/sh >>>>> # Shell script to restart the weatherLogger wifi device in the Davis >>>>> Vantage Pro 2 in the Harbormaster Building >>>>> # The weather logger tends to disconnect from network every 4 days >>>>> causing weewx to crash in a waiting state >>>>> # Currently set to run by rycweather as a cron job once a day at 8:07 >>>>> am. >>>>> # check to see if weatherLogger is connected on Harbormaster vlan >>>>> /sbin/ping -c 1 192.168.145.106 >>>>> if [[ "$?" == "0" ]]; then >>>>> weatherLoggerStatus="weatherLogger is online" >>>>> # Using Safari browser >>>>> open -a Safari http://192.168.145.106/admin/restart >>>>> # wait for Safari to launch and load javascript function of URL >>>>> sleep 60 >>>>> # close Safari >>>>> killall Safari >>>>> else >>>>> weatherLoggerStatus="weatherLogger is OFFLINE" >>>>> fi >>>>> # Check weatherLogger is connected again >>>>> /sbin/ping -c 1 192.168.145.106 >&
[weewx-user] Re: Upgrade PWS- WLL or WiFiLogger2?
I'm curious if the curl command works to restart WiFiLogger2. I first tried using the lynx command line browser and it did not resolve the page correctly and didn't restart. I assumed that was because the restart page contains some javascript and lynx doesn't support javascript. I then switched to Safari, which has the downside of needing a GUI. So does curl work in the terminal script? That's a better solution if it works. On Tuesday, October 6, 2020 at 6:37:57 AM UTC-7 gary@gmail.com wrote: > Thanks for the Linux version of the script. > > On Tuesday, October 6, 2020 at 4:33:35 AM UTC-4 mh081...@gmail.com wrote: > >> Thanks for the script. I changed it to be runnable from raspberry pi >> (Debian 10.4) >> >> #!/bin/sh >> # Shell script to restart the weatherLogger wifi device in the Davis >> Vantage Pro 2 in the Harbormaster Building >> # The weather logger tends to disconnect from network every 4 days >> causing weewx to crash in a waiting state >> # Currently set to run by rycweather as a cron job once a day at 8:07 am. >> # check to see if weatherLogger is connected on Harbormaster vlan >> /bin/ping -c 1 WiFiLogger.fritz.box >> if [ "$?" = "0" ]; then >> weatherLoggerStatus="weatherLogger is online" >> # Using curl >> curl --connect-timeout 5 --fail >> http://WiFiLogger.fritz.box/admin/restart >> # wait to launch and load javascript function of URL >> sleep 30 >> else >> weatherLoggerStatus="weatherLogger is OFFLINE" >> fi >> # Check weatherLogger is connected again >> /bin/ping -c 1 WiFiLogger.fritz.box >> if [ "$?" = "0" ]; then >> newWeatherLoggerStatus="weatherlogger is back online" >> else >> newWeatherLoggerStatus="weatherLogger is OFFLINE after restart" >> fi >> echo "$weatherLoggerStatus and after restart $newWeatherLoggerStatus" | >> sendemail -f mailadr...@mail.com -t mailad...@mail.com -u "WifiLogger >> Restart" -s mailserver.mail.com -xu "username" -xp "password" -o tls=yes >> -o message-content-type=auto >> exit >> >> >> jerry...@gmail.com schrieb am Dienstag, 6. Oktober 2020 um 09:36:22 >> UTC+2: >> >>> WifiLogger2 doesn't have an ssh port open, but it does respond on port >>> 80 to a restart command from http. Under macOS I use the shell script >>> command to open the Safair browser to the restart javascript command. >>> #!/bin/sh >>> # Shell script to restart the weatherLogger wifi device in the Davis >>> Vantage Pro 2 in the Harbormaster Building >>> # The weather logger tends to disconnect from network every 4 days >>> causing weewx to crash in a waiting state >>> # Currently set to run by rycweather as a cron job once a day at 8:07 am. >>> # check to see if weatherLogger is connected on Harbormaster vlan >>> /sbin/ping -c 1 192.168.145.106 >>> if [[ "$?" == "0" ]]; then >>> weatherLoggerStatus="weatherLogger is online" >>> # Using Safari browser >>> open -a Safari http://192.168.145.106/admin/restart >>> # wait for Safari to launch and load javascript function of URL >>> sleep 60 >>> # close Safari >>> killall Safari >>> else >>> weatherLoggerStatus="weatherLogger is OFFLINE" >>> fi >>> # Check weatherLogger is connected again >>> /sbin/ping -c 1 192.168.145.106 >>> if [[ "$?" == "0" ]]; then >>> newWeatherLoggerStatus="weatherlogger is back online" >>> else >>> newWeatherLoggerStatus="weatherLogger is OFFLINE after restart" >>> fi >>> echo "$weatherLoggerStatus and after restart $newWeatherLoggerStatus" | >>> mail -s "weatherLogger restart" xxx >>> exit >>> >>> >>> On Tuesday, October 6, 2020 at 12:23:03 AM UTC-7 mh081...@gmail.com >>> wrote: >>> >>>> Hi, >>>> >>>> can you provide me this shell script to restart WifiLogger2 by cron? >>>> How did you connect to WifiLogger2 remotely? I have the same problem that >>>> WifiLogger2 disconnects from wlan after several days. >>>> >>>> jerry...@gmail.com schrieb am Dienstag, 6. Oktober 2020 um 09:15:11 >>>> UTC+2: >>>> >>>>> I recently switched from a 3 hop retransmit across 1000 ft by multiple >>>>> Davis Vantage Pro2 li
[weewx-user] Re: Upgrade PWS- WLL or WiFiLogger2?
WifiLogger2 doesn't have an ssh port open, but it does respond on port 80 to a restart command from http. Under macOS I use the shell script command to open the Safair browser to the restart javascript command. #!/bin/sh # Shell script to restart the weatherLogger wifi device in the Davis Vantage Pro 2 in the Harbormaster Building # The weather logger tends to disconnect from network every 4 days causing weewx to crash in a waiting state # Currently set to run by rycweather as a cron job once a day at 8:07 am. # check to see if weatherLogger is connected on Harbormaster vlan /sbin/ping -c 1 192.168.145.106 if [[ "$?" == "0" ]]; then weatherLoggerStatus="weatherLogger is online" # Using Safari browser open -a Safari http://192.168.145.106/admin/restart # wait for Safari to launch and load javascript function of URL sleep 60 # close Safari killall Safari else weatherLoggerStatus="weatherLogger is OFFLINE" fi # Check weatherLogger is connected again /sbin/ping -c 1 192.168.145.106 if [[ "$?" == "0" ]]; then newWeatherLoggerStatus="weatherlogger is back online" else newWeatherLoggerStatus="weatherLogger is OFFLINE after restart" fi echo "$weatherLoggerStatus and after restart $newWeatherLoggerStatus" | mail -s "weatherLogger restart" xxx exit On Tuesday, October 6, 2020 at 12:23:03 AM UTC-7 mh081...@gmail.com wrote: > Hi, > > can you provide me this shell script to restart WifiLogger2 by cron? How > did you connect to WifiLogger2 remotely? I have the same problem that > WifiLogger2 disconnects from wlan after several days. > > jerry...@gmail.com schrieb am Dienstag, 6. Oktober 2020 um 09:15:11 UTC+2: > >> I recently switched from a 3 hop retransmit across 1000 ft by multiple >> Davis Vantage Pro2 links to WiFiLogger2 across an AirMax backhaul and the >> weewx server has been running well for several months. I had one problem >> with the WiFiLogger2. It seemed to disconnect from its vLAN network every >> 4 days or so, which caused weewx to going into a waiting mode and not >> reconnect. WiFiLogger2 eventually reconnects after about 2 hours, but >> weewx needs to be restarted after that. I fixed this problem by running a >> short shell script as a cron job once a day to restart WiFiLogger2. >> WifiLogger2 has been stable if restarted once a day. >> >> WifiLogger2 replaced a Davis Weather Envoy 6316 with a USB interface. I >> found the 6316 would freeze every 8 days (running 5 minute update >> intervals). This was the case under WeatherLink for Windows, WeatherLink >> for Mac, and Weewx. Must be the USB driver. Again, a cron job to restart >> weewx (or the other programs) every 7 days fixed the problem. >> Wojtek at WiFiLogger2 has been very responsive in helping to trouble >> shoot the disconnect issues. I am happy with WiFiLogger2. >> >> >> >> On Monday, October 5, 2020 at 12:58:45 PM UTC-7 gary@gmail.com wrote: >> >>> I am thinking of upgrading my PWS to a Davis 6163. >>> To get the data into WeeWX, I am looking at two devices. >>> The Davis 6100 (WLL) or the WiFiLogger2 >>> >>> I can find no real information about the WLL an local LAN. >>> I see a couple of user created drivers for the WLL and WeeWX, but they >>> seem to have issues. >>> >>> The WiFiLogger2 has the ability to be used as a data logger via WiFi or >>> it can provide a MQTT feed. >>> >>> Why the WLL or WiFiLogger? I don't wish to have my console located with >>> my WeeWX server. >>> >>> Any feedback on either device? >>> I'd like to move forward, but if I can't get my data into WeeWX, then >>> it's a non-starter. >>> >>> >>> -- 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/713078f4-5231-446d-9959-e13e5d8d9cf0n%40googlegroups.com.
[weewx-user] Re: Upgrade PWS- WLL or WiFiLogger2?
I recently switched from a 3 hop retransmit across 1000 ft by multiple Davis Vantage Pro2 links to WiFiLogger2 across an AirMax backhaul and the weewx server has been running well for several months. I had one problem with the WiFiLogger2. It seemed to disconnect from its vLAN network every 4 days or so, which caused weewx to going into a waiting mode and not reconnect. WiFiLogger2 eventually reconnects after about 2 hours, but weewx needs to be restarted after that. I fixed this problem by running a short shell script as a cron job once a day to restart WiFiLogger2. WifiLogger2 has been stable if restarted once a day. WifiLogger2 replaced a Davis Weather Envoy 6316 with a USB interface. I found the 6316 would freeze every 8 days (running 5 minute update intervals). This was the case under WeatherLink for Windows, WeatherLink for Mac, and Weewx. Must be the USB driver. Again, a cron job to restart weewx (or the other programs) every 7 days fixed the problem. Wojtek at WiFiLogger2 has been very responsive in helping to trouble shoot the disconnect issues. I am happy with WiFiLogger2. On Monday, October 5, 2020 at 12:58:45 PM UTC-7 gary@gmail.com wrote: > I am thinking of upgrading my PWS to a Davis 6163. > To get the data into WeeWX, I am looking at two devices. > The Davis 6100 (WLL) or the WiFiLogger2 > > I can find no real information about the WLL an local LAN. > I see a couple of user created drivers for the WLL and WeeWX, but they > seem to have issues. > > The WiFiLogger2 has the ability to be used as a data logger via WiFi or it > can provide a MQTT feed. > > Why the WLL or WiFiLogger? I don't wish to have my console located with my > WeeWX server. > > Any feedback on either device? > I'd like to move forward, but if I can't get my data into WeeWX, then it's > a non-starter. > > > -- 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/c62b81d9-3f29-4c2a-bbce-c8fb0f690137n%40googlegroups.com.
Re: [weewx-user] Python 3.7.3 to 3.8.5 upgrade problem
Wow. It never even occurred to me that PIL shouldn't be there at all. The files were there from early May when I cut over to 4.1 and saw some graphics issues with an extension. It could be even older. I probably ran uninstall / reinstall on the Python dependencies from ~/weewx. The native macOS Python doesn't change often, so it didn't matter. But I just switched over to the HomeBrew version when graphics generation broke. Is that worth a caveat on the macOS installation page? Thanks for your help On Saturday, August 1, 2020 at 5:28:54 AM UTC-7 tke...@gmail.com wrote: > Ah! So, it looks like the problem was caused by installing Pillow from the > weewx home directory at some point. > > I can't tell you how many times that has happened to me. > > -tk > > > On Fri, Jul 31, 2020 at 7:23 PM jerry...@gmail.com > wrote: > >> Solved. There were residual py*37 files in PIL, so >> rm -rf ~/weewx/bin/PIL/* >> followed by a python3 setup.py install (I'm not sure that was needed) >> and it's all good. >> On Friday, July 31, 2020 at 6:15:27 PM UTC-7 tke...@gmail.com wrote: >> >>> You've got me stumped. I would try the uninstall/install. Make sure you >>> don't do it from the weewx home directory. >>> >>> But, before you do, how about seeing what's in that home directory? >>> >>> *ls -l /Users/rycweather/weewx/* >>> >>> Then try the uninstall/install: >>> >>> *cd ~* >>> >>> >>> *pip3 uninstall PILpip3 uninstall Pillowpip3 install Pillow* >>> >>> On Fri, Jul 31, 2020 at 5:27 PM jerry...@gmail.com >>> wrote: >>> >>>> That looks ok also. >>>> └─[$] <> python3 -c "from PIL import _imaging; print(_imaging.__file__)" >>>> /usr/local/lib/python3.8/site-packages/PIL/_ >>>> imaging.cpython-38-darwin.so >>>> >>>> On Friday, July 31, 2020 at 3:32:19 PM UTC-7 tke...@gmail.com wrote: >>>> >>>>> Looking back at your original post, I'm wondering if you're missing >>>>> the C library _imaging. Try this: >>>>> >>>>> *python3 -c "from PIL import _imaging; print(_imaging.__file__)"* >>>>> >>>>> You should get something like >>>>> >>>>> /usr/local/lib/python3.8/site-packages/PIL/_ >>>>> imaging.cpython-37m-darwin.so >>>>> >>>>> If you get an exception, then try uninstalling both PIL (in case it is >>>>> present; it shouldn't be), and Pillow, then reinstalling just Pillow: >>>>> >>>>> >>>>> >>>>> >>>>> *pip3 uninstall PILpip3 uninstall Pillowpip3 install Pillow* >>>>> >>>>> See if that helps. >>>>> >>>>> -tk >>>>> >>>>> >>>>> >>>>> On Fri, Jul 31, 2020 at 2:12 PM jerry...@gmail.com >>>>> wrote: >>>>> >>>>>> Seems OK. >>>>>> └─[$] <> pip3 list -v >>>>>> PackageVersion Location Installer >>>>>> -- --- -- - >>>>>> Cheetah3 3.2.5 /usr/local/lib/python3.8/site-packages pip >>>>>> configobj 5.0.6 /usr/local/lib/python3.8/site-packages pip >>>>>> ephem 3.7.7.0 /usr/local/lib/python3.8/site-packages pip >>>>>> Pillow 7.2.0 /usr/local/lib/python3.8/site-packages pip >>>>>> pip20.2/usr/local/lib/python3.8/site-packages pip >>>>>> pyephem3.7.7.0 /usr/local/lib/python3.8/site-packages pip >>>>>> pyserial 3.4 /usr/local/lib/python3.8/site-packages pip >>>>>> pyusb 1.0.2 /usr/local/lib/python3.8/site-packages pip >>>>>> setuptools 49.2.0 /usr/local/lib/python3.8/site-packages >>>>>> six1.15.0 /usr/local/lib/python3.8/site-packages pip >>>>>> wheel 0.34.2 /usr/local/lib/python3.8/site-packages >>>>>> >>>>>> >>>>>> -- >>>>>> 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 >
Re: [weewx-user] Python 3.7.3 to 3.8.5 upgrade problem
Solved. There were residual py*37 files in PIL, so rm -rf ~/weewx/bin/PIL/* followed by a python3 setup.py install (I'm not sure that was needed) and it's all good. On Friday, July 31, 2020 at 6:15:27 PM UTC-7 tke...@gmail.com wrote: > You've got me stumped. I would try the uninstall/install. Make sure you > don't do it from the weewx home directory. > > But, before you do, how about seeing what's in that home directory? > > *ls -l /Users/rycweather/weewx/* > > Then try the uninstall/install: > > *cd ~* > > > *pip3 uninstall PILpip3 uninstall Pillowpip3 install Pillow* > > On Fri, Jul 31, 2020 at 5:27 PM jerry...@gmail.com > wrote: > >> That looks ok also. >> └─[$] <> python3 -c "from PIL import _imaging; print(_imaging.__file__)" >> /usr/local/lib/python3.8/site-packages/PIL/_imaging.cpython-38-darwin.so >> >> On Friday, July 31, 2020 at 3:32:19 PM UTC-7 tke...@gmail.com wrote: >> >>> Looking back at your original post, I'm wondering if you're missing the >>> C library _imaging. Try this: >>> >>> *python3 -c "from PIL import _imaging; print(_imaging.__file__)"* >>> >>> You should get something like >>> >>> /usr/local/lib/python3.8/site-packages/PIL/_ >>> imaging.cpython-37m-darwin.so >>> >>> If you get an exception, then try uninstalling both PIL (in case it is >>> present; it shouldn't be), and Pillow, then reinstalling just Pillow: >>> >>> >>> >>> >>> *pip3 uninstall PILpip3 uninstall Pillowpip3 install Pillow* >>> >>> See if that helps. >>> >>> -tk >>> >>> >>> >>> On Fri, Jul 31, 2020 at 2:12 PM jerry...@gmail.com >>> wrote: >>> >>>> Seems OK. >>>> └─[$] <> pip3 list -v >>>> PackageVersion Location Installer >>>> -- --- -- - >>>> Cheetah3 3.2.5 /usr/local/lib/python3.8/site-packages pip >>>> configobj 5.0.6 /usr/local/lib/python3.8/site-packages pip >>>> ephem 3.7.7.0 /usr/local/lib/python3.8/site-packages pip >>>> Pillow 7.2.0 /usr/local/lib/python3.8/site-packages pip >>>> pip20.2/usr/local/lib/python3.8/site-packages pip >>>> pyephem3.7.7.0 /usr/local/lib/python3.8/site-packages pip >>>> pyserial 3.4 /usr/local/lib/python3.8/site-packages pip >>>> pyusb 1.0.2 /usr/local/lib/python3.8/site-packages pip >>>> setuptools 49.2.0 /usr/local/lib/python3.8/site-packages >>>> six1.15.0 /usr/local/lib/python3.8/site-packages pip >>>> wheel 0.34.2 /usr/local/lib/python3.8/site-packages >>>> >>>> >>>> -- >>>> 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/2ee63fd4-d60e-4ebe-85bd-adf2ae3e36adn%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/weewx-user/2ee63fd4-d60e-4ebe-85bd-adf2ae3e36adn%40googlegroups.com?utm_medium=email_source=footer> >>>> . >>>> >>> -- >> 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/f220ff59-7d20-43c8-a024-8b860bada7ffn%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/f220ff59-7d20-43c8-a024-8b860bada7ffn%40googlegroups.com?utm_medium=email_source=footer> >> . >> > -- 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/df2bbe7c-f403-4cb9-9a57-dfc717b7365bn%40googlegroups.com.
Re: [weewx-user] Python 3.7.3 to 3.8.5 upgrade problem
That looks ok also. └─[$] <> python3 -c "from PIL import _imaging; print(_imaging.__file__)" /usr/local/lib/python3.8/site-packages/PIL/_imaging.cpython-38-darwin.so On Friday, July 31, 2020 at 3:32:19 PM UTC-7 tke...@gmail.com wrote: > Looking back at your original post, I'm wondering if you're missing the C > library _imaging. Try this: > > *python3 -c "from PIL import _imaging; print(_imaging.__file__)"* > > You should get something like > > /usr/local/lib/python3.8/site-packages/PIL/_imaging.cpython-37m-darwin.so > > If you get an exception, then try uninstalling both PIL (in case it is > present; it shouldn't be), and Pillow, then reinstalling just Pillow: > > > > > *pip3 uninstall PILpip3 uninstall Pillowpip3 install Pillow* > > See if that helps. > > -tk > > > > On Fri, Jul 31, 2020 at 2:12 PM jerry...@gmail.com > wrote: > >> Seems OK. >> └─[$] <> pip3 list -v >> PackageVersion Location Installer >> -- --- -- - >> Cheetah3 3.2.5 /usr/local/lib/python3.8/site-packages pip >> configobj 5.0.6 /usr/local/lib/python3.8/site-packages pip >> ephem 3.7.7.0 /usr/local/lib/python3.8/site-packages pip >> Pillow 7.2.0 /usr/local/lib/python3.8/site-packages pip >> pip20.2/usr/local/lib/python3.8/site-packages pip >> pyephem3.7.7.0 /usr/local/lib/python3.8/site-packages pip >> pyserial 3.4 /usr/local/lib/python3.8/site-packages pip >> pyusb 1.0.2 /usr/local/lib/python3.8/site-packages pip >> setuptools 49.2.0 /usr/local/lib/python3.8/site-packages >> six1.15.0 /usr/local/lib/python3.8/site-packages pip >> wheel 0.34.2 /usr/local/lib/python3.8/site-packages >> >> >> -- >> 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/2ee63fd4-d60e-4ebe-85bd-adf2ae3e36adn%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/2ee63fd4-d60e-4ebe-85bd-adf2ae3e36adn%40googlegroups.com?utm_medium=email_source=footer> >> . >> > -- 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/f220ff59-7d20-43c8-a024-8b860bada7ffn%40googlegroups.com.
Re: [weewx-user] Python 3.7.3 to 3.8.5 upgrade problem
Seems OK. └─[$] <> pip3 list -v PackageVersion Location Installer -- --- -- - Cheetah3 3.2.5 /usr/local/lib/python3.8/site-packages pip configobj 5.0.6 /usr/local/lib/python3.8/site-packages pip ephem 3.7.7.0 /usr/local/lib/python3.8/site-packages pip Pillow 7.2.0 /usr/local/lib/python3.8/site-packages pip pip20.2/usr/local/lib/python3.8/site-packages pip pyephem3.7.7.0 /usr/local/lib/python3.8/site-packages pip pyserial 3.4 /usr/local/lib/python3.8/site-packages pip pyusb 1.0.2 /usr/local/lib/python3.8/site-packages pip setuptools 49.2.0 /usr/local/lib/python3.8/site-packages six1.15.0 /usr/local/lib/python3.8/site-packages pip wheel 0.34.2 /usr/local/lib/python3.8/site-packages -- 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/2ee63fd4-d60e-4ebe-85bd-adf2ae3e36adn%40googlegroups.com.
[weewx-user] Python 3.7.3 to 3.8.5 upgrade problem
I upgraded Python to 3.8.5, reinstalled Weewx. Python -V is OK. Davis loop
data is ok, but now seeing errors in image generation. Pillow and other
dependencies were reinstalled. What am I missing? Or was Python 3.8.5 a
mistake. I have dumped and cleared memory on the Vantage Pro.
weewx[89452] INFO __main__: Initializing weewx version 4.1.1
weewx[89452] INFO __main__: Using Python 3.8.5 (default, Jul 21 2020,
10:48:26)
[Clang 11.0.3 (clang-1103.0.32.62)]
weewx[89452] INFO __main__: Platform macOS-10.15.6-x86_64-i386-64bit
weewx[89452] INFO __main__: Locale is 'C/UTF-8/C/C/C/C'
weewx[89452] INFO __main__: Using configuration file
/Users/rycweather/weewx/weewx.conf
weewx[89452] INFO __main__: Debug is 1
weewx[89452] DEBUG __main__: Initializing engine
weewx[89452] INFO weewx.engine: Loading station type Vantage
(weewx.drivers.vantage)
weewx[89452] DEBUG weewx.drivers.vantage: Driver version is 3.2.1
weewx[89452] DEBUG weewx.drivers.vantage: Opened up ethernet host
192.168.145.106 on port 2. timeout=4.0, tcp_send_delay=0.5
weewx[89452] DEBUG weewx.drivers.vantage: Gentle wake up of console
successful
weewx[89452] DEBUG weewx.drivers.vantage: Hardware type is 16
weewx[89452] DEBUG weewx.drivers.vantage: ISS ID is 3
weewx[89452] DEBUG weewx.drivers.vantage: Hardware name: Vantage Pro2
weewx[89452] DEBUG weewx.engine: Loading service weewx.engine.StdTimeSynch
weewx[89452] DEBUG weewx.engine: Finished loading service
weewx.engine.StdTimeSynch
weewx[89452] DEBUG weewx.engine: Loading service weewx.engine.StdConvert
weewx[89452] INFO weewx.engine: StdConvert target unit is 0x1
weewx[89452] DEBUG weewx.engine: Finished loading service
weewx.engine.StdConvert
weewx[89452] DEBUG weewx.engine: Loading service weewx.engine.StdCalibrate
weewx[89452] DEBUG weewx.engine: Finished loading service
weewx.engine.StdCalibrate
weewx[89452] DEBUG weewx.engine: Loading service weewx.engine.StdQC
weewx[89452] DEBUG weewx.engine: Finished loading service weewx.engine.StdQC
weewx[89452] DEBUG weewx.engine: Loading service
weewx.wxservices.StdWXCalculate
weewx[89452] DEBUG weewx.manager: Daily summary version is 2.0
weewx[89452] INFO weewx.wxservices: The following values will be
calculated: pressure=prefer_hardware, barometer=prefer_hardware,
altimeter=prefer_hardware, windchill=prefer_hardware,
heatindex=prefer_hardware, dewpoint=prefer_hardware,
inDewpoint=prefer_hardware, rainRate=prefer_hardware,
maxSolarRad=prefer_hardware, cloudbase=prefer_hardware,
humidex=prefer_hardware, appTemp=prefer_hardware, ET=prefer_hardware,
windrun=prefer_hardware
weewx[89452] INFO weewx.wxservices: The following algorithms will be used
for calculations: altimeter=aaASOS, maxSolarRad=RS
weewx[89452] DEBUG weewx.engine: Finished loading service
weewx.wxservices.StdWXCalculate
weewx[89452] DEBUG weewx.engine: Loading service weewx.engine.StdArchive
weewx[89452] INFO weewx.engine: Archive will use data binding wx_binding
weewx[89452] INFO weewx.engine: Record generation will be attempted in
'hardware'
weewx[89452] INFO weewx.engine: Using archive interval of 300 seconds
(specified by hardware)
weewx[89452] DEBUG weewx.engine: Use LOOP data in hi/low calculations: 1
weewx[89452] DEBUG weewx.engine: Finished loading service
weewx.engine.StdArchive
weewx[89452] DEBUG weewx.engine: Loading service
weewx.restx.StdStationRegistry
weewx[89452] INFO weewx.restx: StationRegistry: Station will be registered.
weewx[89452] DEBUG weewx.engine: Finished loading service
weewx.restx.StdStationRegistry
weewx[89452] DEBUG weewx.engine: Loading service weewx.restx.StdWunderground
weewx[89452] DEBUG weewx.restx: WU essentials: {}
weewx[89452] INFO weewx.restx: Wunderground-PWS: Data for station
KCACALIF93 will be posted
weewx[89452] DEBUG weewx.engine: Finished loading service
weewx.restx.StdWunderground
weewx[89452] DEBUG weewx.engine: Loading service weewx.restx.StdPWSweather
weewx[89452] INFO weewx.restx: PWSweather: Posting not enabled.
weewx[89452] DEBUG weewx.engine: Finished loading service
weewx.restx.StdPWSweather
weewx[89452] DEBUG weewx.engine: Loading service weewx.restx.StdCWOP
weewx[89452] INFO weewx.restx: CWOP: Posting not enabled.
weewx[89452] DEBUG weewx.engine: Finished loading service
weewx.restx.StdCWOP
weewx[89452] DEBUG weewx.engine: Loading service weewx.restx.StdWOW
weewx[89452] INFO weewx.restx: WOW: Posting not enabled.
weewx[89452] DEBUG weewx.engine: Finished loading service weewx.restx.StdWOW
weewx[89452] DEBUG weewx.engine: Loading service weewx.restx.StdAWEKAS
weewx[89452] INFO weewx.restx: AWEKAS: Posting not enabled.
weewx[89452] DEBUG weewx.engine: Finished loading service
weewx.restx.StdAWEKAS
weewx[89452] DEBUG weewx.engine: Loading service user.windy.Windy
weewx[89452] DEBUG weewx.manager: Daily summary version is 2.0
weewx[89452] INFO user.windy: version is 0.7
weewx[89452] INFO user.windy: Data will be uploaded to
https://stations.windy.com/pws/update
weewx[89452] DEBUG weewx.engine:
