[weewx-user] UPGRADE and " you must use the same upgrade technique ". How to know?
OK guys I installed WEEWX a couple of years ago and its due for an upgrade. I Have NO idea what 'method' I used to install Weewx. How do I know? -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: UPGRADE and " you must use the same upgrade technique ". How to know?
Hmm Ok I will try that. Also, I see a weewx_3.1.0-1_all.deb in the root directory. Myabe that means I installed the .deb with the command line. On Wednesday, April 5, 2017 at 3:07:01 PM UTC-5, Joe wrote: > > OK guys I installed WEEWX a couple of years ago and its due for an upgrade. > > I Have NO idea what 'method' I used to install Weewx. > > How do I know? > -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: UPGRADE and " you must use the same upgrade technique ". How to know?
Thanks! It's the DEB package! Appreciate the fast reply. On Wednesday, April 5, 2017 at 3:07:01 PM UTC-5, Joe wrote: > > OK guys I installed WEEWX a couple of years ago and its due for an upgrade. > > I Have NO idea what 'method' I used to install Weewx. > > How do I know? > -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: UPGRADE and " you must use the same upgrade technique ". How to know?
Update went ok. Everything still working. I kept my previous .conf file. Is there any negative to 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. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Re: UPGRADE and " you must use the same upgrade technique ". How to know?
I've been very impressed with weeWX. I'm a user for life. I noticed some changes to the weewx.conf file were made since my 3.1 version ( I was a bit behind ). Is there any manual editing I need to do? On Wednesday, April 5, 2017 at 3:41:21 PM UTC-5, Tom Keffer wrote: > > We've worked hard to make sure upgrades go smoothly, so if it's working, > it's working! > > -tk > > On Wed, Apr 5, 2017 at 1:36 PM, Joe > > wrote: > >> Update went ok. Everything still working. >> >> I kept my previous .conf file. >> >> Is there any negative to 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+...@googlegroups.com . >> 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Re: UPGRADE and " you must use the same upgrade technique ". How to know?
I looked through there, and did not see anything that appeared to be critical for use of weewx. It still functions as it did before with version 3.1 On Wednesday, April 5, 2017 at 4:14:37 PM UTC-5, Tom Keffer wrote: > > If there is, it will be noted in the Upgrade Guide > <http://weewx.com/docs/upgrading.htm>. > > -tk > > On Wed, Apr 5, 2017 at 1:47 PM, Joe > > wrote: > >> I've been very impressed with weeWX. I'm a user for life. >> >> I noticed some changes to the weewx.conf file were made since my 3.1 >> version ( I was a bit behind ). Is there any manual editing I need to do? >> >> On Wednesday, April 5, 2017 at 3:41:21 PM UTC-5, Tom Keffer wrote: >>> >>> We've worked hard to make sure upgrades go smoothly, so if it's working, >>> it's working! >>> >>> -tk >>> >>> On Wed, Apr 5, 2017 at 1:36 PM, Joe wrote: >>> >>>> Update went ok. Everything still working. >>>> >>>> I kept my previous .conf file. >>>> >>>> Is there any negative to 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+...@googlegroups.com. >>>> 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 weewx-user+...@googlegroups.com . >> 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] dayhumidity.png not displayed in index.html
The .png is being created by the software, but its not being displayed on index.html I checked the skin.conf and it shows the dayhumidity string. Is there something I am missing? Or possibly, does the software not create this change in the html more than once a day in the index.html? -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] ET Calculations always show Zero on HTML but correct on console.
My Davis 2 console shows the E.T. data on the console for the day or the month. However Weewx is always showing zero for ET in the displayed HTML data or a .02 or real low number. I have both sensors UV and Solar installed and those graphs are displaying their data correctly. -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: ET Calculations always show Zero on HTML but correct on console.
High UV Low UV 8.3 at 10-03-2017 13:36 0.0 at 10-01-2017 00:00 High ET Low ET 0.02 in at 10-01-2017 14:00 0.00 in at 10-01-2017 00:05 High Radiation Low Radiation 1060 W/m² at 10-04-2017 13:41 0 W/m² at 10-01-2017 00:00 This is the MONTHLY totals. And it always shows .02 for ET for the High ET -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Re: ET Calculations always show Zero on HTML but correct on console.
I didn't change the default settings for ET.. i will look at data and try to see. The reason I think something is wrong is because its always the same even after it rains. But on the console its being displayed. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Re: ET Calculations always show Zero on HTML but correct on console.
StdArchive field i record_generation is HARDWARE On Sunday, November 5, 2017 at 5:04:40 AM UTC-6, Tom Keffer wrote: > > Are you using hardware record generation? Or, software? Look in weewx.conf > in the [StdArchive] section, option record_generation. > > -tk > > On Sat, Nov 4, 2017 at 7:30 PM, Joe > > wrote: > >> I didn't change the default settings for ET.. i will look at data and >> try to see. >> >> The reason I think something is wrong is because its always the same even >> after it rains. >> >> But on the console its being displayed. >> >> -- >> 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 . >> 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Three days and no outside temperature graph updates...
I don't normally post questions like this, however I have rebooted the PI computer a few times, and manually stopped/started the weewx software via command line a couple of times. However, suddenly the updating on the website stopped on the 5th of this month . I noticed it today. After I rebooted the PI Computer, it began to update HTML Again and showed current within the last 5 minutes that I have the interval set at. However, after several hours of running, it still has not updated the CURRENT TEMP graph and I cant figure out where to look for an error message. I Am running looking at the log as it happens via putty but I Dont see any errors. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Three days and no outside temperature graph updates...
I missed that, sorry. On Wednesday, November 8, 2017 at 10:00:03 AM UTC-6, Tom Keffer wrote: > > See the User's Guide, section *Weewx generates HTML pages, but does not > update them > <http://weewx.com/docs/usersguide.htm#html_generated_but_not_updated>*. > > -tk > > On Wed, Nov 8, 2017 at 7:57 AM, Joe > > wrote: > >> I don't normally post questions like this, however I have rebooted the PI >> computer a few times, and manually stopped/started the weewx software via >> command line a couple of times. >> >> However, suddenly the updating on the website stopped on the 5th of this >> month . I noticed it today. After I rebooted the PI Computer, it began to >> update HTML Again and showed current within the last 5 minutes that I have >> the interval set at. >> >> However, after several hours of running, it still has not updated the >> CURRENT TEMP graph and I cant figure out where to look for an error >> message. I Am running looking at the log as it happens via putty but I >> Dont see any errors. >> >> -- >> 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 . >> 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Three days and no outside temperature graph updates...
As a follow up to this. I tried powering down the Vantage2 console and re started weewx. Same problem. I did the --DUMP command after stopping weewx of course, restarted weewx. Same Problem! Loaded a different browser and went to the HTML site and it's fine! I went to google chrome and dumped all the image cache for the website and suddenly it appeared correctly. So I don't know which action was the problem after all. It may have been the WHOLE TIME Google chrome refusing to update the images. It may have been the console power-cycle that fixed it, or it may have been the DUMP command fixed it. I will never know this time. NEXT TIME I will immediately use a different browser. When looking at the debug output, It all looks the same after I powered down the whole RPI computer from the start of this when I noticed none of the HTML was being updated. THe way I noticed was, I went to my cell phone browser and noticed the graphs were displaying fine! IT does not look like I lost any data through all of this. UGH! But I greatly appreciate as usual this forum and the quick responses we get on questions. I really like weewx, but the support is great and why I continue to use weewx. >> -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Re: ET Calculations always show Zero on HTML but correct on console.
Ok So I was assuming it would always show a field here at any given point like what it does on the Vanage Console. Is there not a 'graph' that can be displayed along with the rest of them in the HTML ? On Wednesday, November 8, 2017 at 7:51:37 AM UTC-6, Tom Keffer wrote: > > If record generation is hardware, then weewx is just reporting what was > calculated by the Vantage console. > > The algorithm they use is rather complicated and is described here > <http://www.davisnet.com/product_documents/weather/app_notes/AN_28-derived-weather-variables.pdf> > (see > page 28-15). The main variables they depend on are actual and saturation > water pressures, which are functions of humidity. So, rainfall is not taken > into account, except in so far as it might affect relative humidity. > > -tk > > On Wed, Nov 8, 2017 at 5:01 AM, Joe > > wrote: > >> StdArchive field i record_generation is HARDWARE >> >> >> >> >> >> >> >> On Sunday, November 5, 2017 at 5:04:40 AM UTC-6, Tom Keffer wrote: >>> >>> Are you using hardware record generation? Or, software? Look in >>> weewx.conf in the [StdArchive] section, option record_generation. >>> >>> -tk >>> >>> On Sat, Nov 4, 2017 at 7:30 PM, Joe wrote: >>> >>>> I didn't change the default settings for ET.. i will look at data and >>>> try to see. >>>> >>>> The reason I think something is wrong is because its always the same >>>> even after it rains. >>>> >>>> But on the console its being displayed. >>>> >>>> -- >>>> 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. >>>> 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 weewx-user+...@googlegroups.com . >> 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Re: ET Calculations always show Zero on HTML but correct on console.
Ok I will look for the string to add to the conf file. On Wednesday, November 8, 2017 at 12:30:25 PM UTC-6, Tom Keffer wrote: > > Sure, there is no reason you can't plot ET. You just need to make sure you > have an aggregation period of at least an hour. > > -tk > > Fat-fingered from my Android > > On Nov 8, 2017 9:34 AM, "Joe" > > wrote: > > Ok So I was assuming it would always show a field here at any given point > like what it does on the Vanage Console. > > > Is there not a 'graph' that can be displayed along with the rest of them > in the HTML ? > > > > On Wednesday, November 8, 2017 at 7:51:37 AM UTC-6, Tom Keffer wrote: > >> If record generation is hardware, then weewx is just reporting what was >> calculated by the Vantage console. >> >> The algorithm they use is rather complicated and is described here >> <http://www.davisnet.com/product_documents/weather/app_notes/AN_28-derived-weather-variables.pdf> >> (see >> page 28-15). The main variables they depend on are actual and saturation >> water pressures, which are functions of humidity. So, rainfall is not taken >> into account, except in so far as it might affect relative humidity. >> >> -tk >> >> On Wed, Nov 8, 2017 at 5:01 AM, Joe wrote: >> >>> StdArchive field i record_generation is HARDWARE >>> >>> >>> >>> >>> >>> >>> >>> On Sunday, November 5, 2017 at 5:04:40 AM UTC-6, Tom Keffer wrote: >>>> >>>> Are you using hardware record generation? Or, software? Look in >>>> weewx.conf in the [StdArchive] section, option record_generation. >>>> >>>> -tk >>>> >>>> On Sat, Nov 4, 2017 at 7:30 PM, Joe wrote: >>>> >>>>> I didn't change the default settings for ET.. i will look at data and >>>>> try to see. >>>>> >>>>> The reason I think something is wrong is because its always the same >>>>> even after it rains. >>>>> >>>>> But on the console its being displayed. >>>>> >>>>> -- >>>>> 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. >>>>> 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 weewx-user+...@googlegroups.com. >>> 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 weewx-user+...@googlegroups.com . > 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Yearly Summary Data from previous years prior to 2019 is gone.
The requested URL /wx/NOAA/NOAA-2016.txt was not found on this server. I tried recently, today in fact, to look at some WX data from a previous year and it is gone. Nothing prior to 2019 is on my website. Can anyone tell me why it removed all this data? I assume the database still has the data And for reference it involves the bottom button on the main index page where you click YEARLY SUMMARY. It shows all the years the data should be there, but there are no files with the data to display. -- 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/fae0d080-fa27-4f1d-aad1-c4bbf40e0fd5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Yearly Summary Data from previous years prior to 2019 is gone.
Sorry If I needed to provide more info. All of the NOAA Files are on the local box as they should be, They are just suddenly not on the website. I Am using FTP. So I assume I should delete the FTP.LAST. On Monday, July 8, 2019 at 7:47:25 PM UTC-5, Thomas Keffer wrote: > > You're not giving us much to go by. > > Are the files missing on the machine running weewx? Or, just the website? > > If they are missing on the weewx machine, they are easy enough to > recreate: just delete the subdirectory NOAA and all will be regenerated. > > If they are just missing from the website, what are you using to transfer > files? FTP? rsync? Something else? If FTP, delete the file "#FTP.last". > This contains the history of which files were transferred and when. > Deleting it will cause all the files to be retransferred. > > If these suggestions don't help, you'll have to give us more information. > > -tk > > > On Mon, Jul 8, 2019 at 5:35 PM Joe > > wrote: > >> The requested URL /wx/NOAA/NOAA-2016.txt was not found on this server. >> >> I tried recently, today in fact, to look at some WX data from a previous >> year and it is gone. Nothing prior to 2019 is on my website. >> >> Can anyone tell me why it removed all this data? I assume the database >> still has the data >> >> And for reference it involves the bottom button on the main index page >> where you click YEARLY SUMMARY. It shows all the years the data should be >> there, but there are no files with the data to display. >> >> >> -- >> 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...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/fae0d080-fa27-4f1d-aad1-c4bbf40e0fd5%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/fae0d080-fa27-4f1d-aad1-c4bbf40e0fd5%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/0ac748da-d304-4531-9b72-065f4bde7f19%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Yearly Summary Data from previous years prior to 2019 is gone.
I deleted the #ftp.last file in the NOAA directory and it did not re-send the files via FTP/rsync for some reason. I even re-started weewx. At least I have somewhere to start now I appreciate the reponse. I Will have to resume tomorrow after work. On Monday, July 8, 2019 at 7:58:10 PM UTC-5, Joe wrote: > > Sorry If I needed to provide more info. All of the NOAA Files are on the > local box as they should be, They are just suddenly not on the website. > > I Am using FTP. So I assume I should delete the FTP.LAST. > > > > On Monday, July 8, 2019 at 7:47:25 PM UTC-5, Thomas Keffer wrote: >> >> You're not giving us much to go by. >> >> Are the files missing on the machine running weewx? Or, just the website? >> >> If they are missing on the weewx machine, they are easy enough to >> recreate: just delete the subdirectory NOAA and all will be regenerated. >> >> If they are just missing from the website, what are you using to transfer >> files? FTP? rsync? Something else? If FTP, delete the file "#FTP.last". >> This contains the history of which files were transferred and when. >> Deleting it will cause all the files to be retransferred. >> >> If these suggestions don't help, you'll have to give us more information. >> >> -tk >> >> >> On Mon, Jul 8, 2019 at 5:35 PM Joe wrote: >> >>> The requested URL /wx/NOAA/NOAA-2016.txt was not found on this server. >>> >>> I tried recently, today in fact, to look at some WX data from a previous >>> year and it is gone. Nothing prior to 2019 is on my website. >>> >>> Can anyone tell me why it removed all this data? I assume the database >>> still has the data >>> >>> And for reference it involves the bottom button on the main index page >>> where you click YEARLY SUMMARY. It shows all the years the data should be >>> there, but there are no files with the data to display. >>> >>> >>> -- >>> 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...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-user/fae0d080-fa27-4f1d-aad1-c4bbf40e0fd5%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/weewx-user/fae0d080-fa27-4f1d-aad1-c4bbf40e0fd5%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/18ed5be6-8b11-4bb0-9047-f30c2cdedcd8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Yearly Summary Data from previous years prior to 2019 is gone.
I had TAIL running the last few times the FTP ran and it only tried to upload the last two most recent files, so I sent them up manually to the web server with my FTP program. The debug logfile didn't provide an error message at the time the FTPUPLOAD report ran. On Monday, July 8, 2019 at 8:24:55 PM UTC-5, Thomas Keffer wrote: > > Look in the log. It will give you information about why the ftp upload > failed. > > -tk > > On Mon, Jul 8, 2019 at 6:12 PM Joe > > wrote: > >> I deleted the #ftp.last file in the NOAA directory and it did not re-send >> the files via FTP/rsync for some reason. I even re-started weewx. >> >> At least I have somewhere to start now I appreciate the reponse. I Will >> have to resume tomorrow after work. >> >> On Monday, July 8, 2019 at 7:58:10 PM UTC-5, Joe wrote: >>> >>> Sorry If I needed to provide more info. All of the NOAA Files are on >>> the local box as they should be, They are just suddenly not on the website. >>> >>> I Am using FTP. So I assume I should delete the FTP.LAST. >>> >>> >>> >>> On Monday, July 8, 2019 at 7:47:25 PM UTC-5, Thomas Keffer wrote: >>>> >>>> You're not giving us much to go by. >>>> >>>> Are the files missing on the machine running weewx? Or, just the >>>> website? >>>> >>>> If they are missing on the weewx machine, they are easy enough to >>>> recreate: just delete the subdirectory NOAA and all will be regenerated. >>>> >>>> If they are just missing from the website, what are you using to >>>> transfer files? FTP? rsync? Something else? If FTP, delete the file >>>> "#FTP.last". This contains the history of which files were transferred and >>>> when. Deleting it will cause all the files to be retransferred. >>>> >>>> If these suggestions don't help, you'll have to give us more >>>> information. >>>> >>>> -tk >>>> >>>> >>>> On Mon, Jul 8, 2019 at 5:35 PM Joe wrote: >>>> >>>>> The requested URL /wx/NOAA/NOAA-2016.txt was not found on this server. >>>>> >>>>> I tried recently, today in fact, to look at some WX data from a >>>>> previous year and it is gone. Nothing prior to 2019 is on my website. >>>>> >>>>> Can anyone tell me why it removed all this data? I assume the >>>>> database still has the data >>>>> >>>>> And for reference it involves the bottom button on the main index page >>>>> where you click YEARLY SUMMARY. It shows all the years the data should >>>>> be >>>>> there, but there are no files with the data to display. >>>>> >>>>> >>>>> -- >>>>> 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...@googlegroups.com. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/weewx-user/fae0d080-fa27-4f1d-aad1-c4bbf40e0fd5%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/weewx-user/fae0d080-fa27-4f1d-aad1-c4bbf40e0fd5%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> 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 weewx...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/18ed5be6-8b11-4bb0-9047-f30c2cdedcd8%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/18ed5be6-8b11-4bb0-9047-f30c2cdedcd8%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e4d0d446-7dbf-4471-82f3-a42622785e5e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Yearly Summary Data from previous years prior to 2019 is gone.
What I'm really wondering now is why the files were deleted off the website in the first place.. On Monday, July 8, 2019 at 8:44:39 PM UTC-5, Joe wrote: > > I had TAIL running the last few times the FTP ran and it only tried to > upload the last two most recent files, so I sent them up manually to the > web server with my FTP program. > > The debug logfile didn't provide an error message at the time the > FTPUPLOAD report ran. > > > On Monday, July 8, 2019 at 8:24:55 PM UTC-5, Thomas Keffer wrote: >> >> Look in the log. It will give you information about why the ftp upload >> failed. >> >> -tk >> >> On Mon, Jul 8, 2019 at 6:12 PM Joe wrote: >> >>> I deleted the #ftp.last file in the NOAA directory and it did not >>> re-send the files via FTP/rsync for some reason. I even re-started weewx. >>> >>> At least I have somewhere to start now I appreciate the reponse. I Will >>> have to resume tomorrow after work. >>> >>> On Monday, July 8, 2019 at 7:58:10 PM UTC-5, Joe wrote: >>>> >>>> Sorry If I needed to provide more info. All of the NOAA Files are on >>>> the local box as they should be, They are just suddenly not on the website. >>>> >>>> I Am using FTP. So I assume I should delete the FTP.LAST. >>>> >>>> >>>> >>>> On Monday, July 8, 2019 at 7:47:25 PM UTC-5, Thomas Keffer wrote: >>>>> >>>>> You're not giving us much to go by. >>>>> >>>>> Are the files missing on the machine running weewx? Or, just the >>>>> website? >>>>> >>>>> If they are missing on the weewx machine, they are easy enough to >>>>> recreate: just delete the subdirectory NOAA and all will be regenerated. >>>>> >>>>> If they are just missing from the website, what are you using to >>>>> transfer files? FTP? rsync? Something else? If FTP, delete the file >>>>> "#FTP.last". This contains the history of which files were transferred >>>>> and >>>>> when. Deleting it will cause all the files to be retransferred. >>>>> >>>>> If these suggestions don't help, you'll have to give us more >>>>> information. >>>>> >>>>> -tk >>>>> >>>>> >>>>> On Mon, Jul 8, 2019 at 5:35 PM Joe wrote: >>>>> >>>>>> The requested URL /wx/NOAA/NOAA-2016.txt was not found on this server. >>>>>> >>>>>> I tried recently, today in fact, to look at some WX data from a >>>>>> previous year and it is gone. Nothing prior to 2019 is on my website. >>>>>> >>>>>> Can anyone tell me why it removed all this data? I assume the >>>>>> database still has the data >>>>>> >>>>>> And for reference it involves the bottom button on the main index >>>>>> page where you click YEARLY SUMMARY. It shows all the years the data >>>>>> should be there, but there are no files with the data to display. >>>>>> >>>>>> >>>>>> -- >>>>>> 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...@googlegroups.com. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/weewx-user/fae0d080-fa27-4f1d-aad1-c4bbf40e0fd5%40googlegroups.com >>>>>> >>>>>> <https://groups.google.com/d/msgid/weewx-user/fae0d080-fa27-4f1d-aad1-c4bbf40e0fd5%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> 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 weewx...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-user/18ed5be6-8b11-4bb0-9047-f30c2cdedcd8%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/weewx-user/18ed5be6-8b11-4bb0-9047-f30c2cdedcd8%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/c957e5a7-90d1-4096-b8c1-59bc42fa00bc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Strange activity on Davis2 after changing batteries
The only thing I've done lately is change out old batteries that showed low on the console. I plugged it in and changed it so the console never shut off. Since then I've been getting some errors trying to communicate with the Davis2 console. Odd never had any problems and now getting communication errors. I only notice because WUNDERGROUND emails me because it stops sending them data. So several times since yesterday I've had to restart the program and now its not doing anything. Last night, it ran a report, then tried to request loop packets and failure... Jul 10 21:06:10 raspberrypi weewx[2185]: ftpupload: Uploaded file /RSS/weewx_rss.xml Jul 10 21:06:10 raspberrypi weewx[2185]: ftpupload: Uploaded file /smartphone/radar.html Jul 10 21:06:10 raspberrypi weewx[2185]: ftpupload: Uploaded file /smartphone/barometer.html Jul 10 21:06:11 raspberrypi weewx[2185]: ftpupload: Uploaded file /smartphone/temp_outside.html Jul 10 21:06:11 raspberrypi weewx[2185]: ftpupload: Uploaded file /smartphone/index.html Jul 10 21:06:11 raspberrypi weewx[2185]: ftpupload: Uploaded file /smartphone/rain.html Jul 10 21:06:12 raspberrypi weewx[2185]: ftpupload: Uploaded file /smartphone/wind.html Jul 10 21:06:12 raspberrypi weewx[2185]: reportengine: Running report 'RSYNC' Jul 10 21:06:12 raspberrypi weewx[2185]: reportengine: Found configuration file /etc/weewx/skins/Rsync/skin.conf for report 'RSYNC' Jul 10 21:06:12 raspberrypi weewx[2185]: rsyncgenerator: rsync upload not requested. Skipped. Jul 10 21:06:20 raspberrypi weewx[2185]: vantage: Requesting 200 LOOP packets. Jul 10 21:06:25 raspberrypi weewx[2185]: vantage: Retry #0 failed Jul 10 21:06:30 raspberrypi weewx[2185]: vantage: Retry #1 failed Jul 10 21:06:35 raspberrypi weewx[2185]: vantage: Retry #2 failed Jul 10 21:06:40 raspberrypi weewx[2185]: vantage: Retry #3 failed Jul 10 21:06:40 raspberrypi weewx[2185]: vantage: Requesting 200 LOOP packets. Jul 10 21:06:45 raspberrypi weewx[2185]: vantage: Retry #0 failed Jul 10 21:06:50 raspberrypi weewx[2185]: vantage: Retry #1 failed Jul 10 21:06:55 raspberrypi weewx[2185]: vantage: Retry #2 failed Jul 10 21:07:00 raspberrypi weewx[2185]: vantage: Retry #3 failed Jul 10 21:07:00 raspberrypi weewx[2185]: vantage: Requesting 200 LOOP packets. Jul 10 21:07:05 raspberrypi weewx[2185]: vantage: Retry #0 failed Jul 10 21:07:10 raspberrypi weewx[2185]: vantage: Retry #1 failed Jul 10 21:07:15 raspberrypi weewx[2185]: vantage: Retry #2 failed Jul 10 21:07:20 raspberrypi weewx[2185]: vantage: Retry #3 failed Jul 10 21:07:20 raspberrypi weewx[2185]: engine: StdReport thread has been terminated Jul 10 21:07:20 raspberrypi weewx[2185]: restx: Shut down PWSWeather thread. Jul 10 21:07:20 raspberrypi weewx[2185]: restx: Shut down Wunderground-RF thread. Jul 10 21:07:20 raspberrypi weewx[2185]: restx: Shut down StationRegistry thread. Jul 10 21:08:20 raspberrypi weewx[2185]: engine: Debug is 1 Jul 10 21:08:20 raspberrypi weewx[2185]: engine: Initializing engine Jul 10 21:08:20 raspberrypi weewx[2185]: vantage: Driver version is 3.1.1 Jul 11 06:09:31 raspberrypi weewx[3217]: engine: Debug is 1 Jul 11 06:09:31 raspberrypi weewx[3217]: engine: Initializing engine Jul 11 06:09:31 raspberrypi weewx[3217]: vantage: Driver version is 3.1.1 ^C Here where it says JUL 11, I've restarted the program several times, root@raspberrypi:/var/log# tail -f debug Jul 10 21:07:20 raspberrypi weewx[2185]: engine: StdReport thread has been terminated Jul 10 21:07:20 raspberrypi weewx[2185]: restx: Shut down PWSWeather thread. Jul 10 21:07:20 raspberrypi weewx[2185]: restx: Shut down Wunderground-RF thread. Jul 10 21:07:20 raspberrypi weewx[2185]: restx: Shut down StationRegistry thread. Jul 10 21:08:20 raspberrypi weewx[2185]: engine: Debug is 1 Jul 10 21:08:20 raspberrypi weewx[2185]: engine: Initializing engine Jul 10 21:08:20 raspberrypi weewx[2185]: vantage: Driver version is 3.1.1 Jul 11 06:09:31 raspberrypi weewx[3217]: engine: Debug is 1 Jul 11 06:09:31 raspberrypi weewx[3217]: engine: Initializing engine Jul 11 06:09:31 raspberrypi weewx[3217]: vantage: Driver version is 3.1.1 Jul 11 06:13:55 raspberrypi weewx[3260]: engine: Debug is 1 Jul 11 06:13:55 raspberrypi weewx[3260]: engine: Initializing engine Jul 11 06:13:55 raspberrypi weewx[3260]: vantage: Driver version is 3.1.1 Jul 11 06:14:42 raspberrypi weewx[3328]: engine: Debug is 1 Jul 11 06:14:42 raspberrypi weewx[3328]: engine: Initializing engine Jul 11 06:14:42 raspberrypi weewx[3328]: vantage: Driver version is 3.1.1 ... And here below, I did a reboot of the PI computer and the whole thing is just stopped... Linux raspberrypi 3.18.7+ #755 PREEMPT Thu Feb 12 17:14:31 GMT 2015 armv6l The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY
[weewx-user] Re: Strange activity on Davis2 after changing batteries
It's still sitting at the VANTAGE DRIVER VERSION 3.1.1 too -- 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/7534db35-cf18-498a-8a5a-178b0618c8ff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Re: Strange activity on Davis2 after changing batteries
Odd because when I do a PS -A and list the processes I dont see any instances of WEEWX running at all. On Thursday, July 11, 2019 at 8:58:02 AM UTC-5, Thomas Keffer wrote: > > It looks like you have two instances of weewx running at the same time. > Make sure you stop all instances, then try again. > > On Thu, Jul 11, 2019 at 5:05 AM Joe > > wrote: > >> >> It's still sitting at the VANTAGE DRIVER VERSION 3.1.1 >> too >> >> -- >> 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...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/7534db35-cf18-498a-8a5a-178b0618c8ff%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/7534db35-cf18-498a-8a5a-178b0618c8ff%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/d7f01eb6-79ed-4424-a53a-ca2bc50281a8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Strange activity on Davis2 after changing batteries
root12 0.0 0.0 0 0 ?S< 10:31 0:00 [netns] root13 0.0 0.0 0 0 ?S< 10:31 0:00 [perf] root14 0.0 0.0 0 0 ?S10:31 0:00 [khungtaskd] root15 0.0 0.0 0 0 ?S< 10:31 0:00 [writeback] root16 0.0 0.0 0 0 ?S< 10:31 0:00 [crypto] root17 0.0 0.0 0 0 ?S< 10:31 0:00 [bioset] root18 0.0 0.0 0 0 ?S< 10:31 0:00 [kblockd] root19 0.1 0.0 0 0 ?S10:31 0:00 [kworker/0:1] root20 0.0 0.0 0 0 ?S< 10:31 0:00 [rpciod] root21 0.0 0.0 0 0 ?S10:31 0:00 [kswapd0] root22 0.0 0.0 0 0 ?S10:31 0:00 [fsnotify_mark] root23 0.0 0.0 0 0 ?S< 10:31 0:00 [nfsiod] root29 0.0 0.0 0 0 ?S< 10:31 0:00 [kthrotld] root30 0.0 0.0 0 0 ?S< 10:31 0:00 [VCHIQ-0] root31 0.0 0.0 0 0 ?S< 10:31 0:00 [VCHIQr-0] root32 0.0 0.0 0 0 ?S< 10:31 0:00 [VCHIQs-0] root33 0.0 0.0 0 0 ?S< 10:31 0:00 [iscsi_eh] root34 0.0 0.0 0 0 ?S< 10:31 0:00 [dwc_otg] root35 0.0 0.0 0 0 ?S< 10:31 0:00 [DWC Notificatio] root36 0.0 0.0 0 0 ?S10:31 0:00 [kworker/u2:1] root37 0.0 0.0 0 0 ?S10:31 0:00 [VCHIQka-0] root38 0.0 0.0 0 0 ?S< 10:31 0:00 [SMIO] root39 0.0 0.0 0 0 ?S< 10:31 0:00 [deferwq] root40 0.0 0.0 0 0 ?S10:31 0:00 [kworker/u2:2] root41 0.0 0.0 0 0 ?S10:31 0:00 [mmcqd/0] root42 0.0 0.0 0 0 ?S10:31 0:00 [kworker/0:2] root43 0.0 0.0 0 0 ?S10:31 0:00 [jbd2/mmcblk0p2-] root44 0.0 0.0 0 0 ?S< 10:31 0:00 [ext4-rsv-conver] root 159 0.0 0.4 2892 2204 ?Ss 10:31 0:00 udevd --daemon root 278 0.0 0.4 2888 1976 ?S10:31 0:00 udevd --daemon root 292 0.0 0.4 2888 1968 ?S10:31 0:00 udevd --daemon root 1528 0.0 0.2 1756 984 ?S10:31 0:00 /usr/sbin/ifplugd -i lo -q -f -u0 -d10 -w -I root 1554 0.0 0.2 1756 1236 ?S10:31 0:00 /usr/sbin/ifplugd -i eth0 -q -f -u0 -d10 -w -I root 1812 0.0 0.7 4904 3132 ?Ss 10:31 0:00 dhclient -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0 root 1919 0.0 0.5 28004 2640 ?Sl 10:31 0:00 /usr/sbin/rsyslogd -c5 root 1966 0.0 2.7 24348 12456 ?Ss 10:31 0:00 /usr/sbin/apache2 -k start www-data 2004 0.0 1.1 24372 5264 ?S10:31 0:00 /usr/sbin/apache2 -k start www-data 2006 0.0 1.1 24372 5264 ?S10:31 0:00 /usr/sbin/apache2 -k start www-data 2007 0.0 1.1 24372 5264 ?S10:31 0:00 /usr/sbin/apache2 -k start www-data 2009 0.0 1.1 24372 5264 ?S10:31 0:00 /usr/sbin/apache2 -k start www-data 2010 0.0 1.1 24372 5264 ?S10:31 0:00 /usr/sbin/apache2 -k start root 2026 0.0 0.4 3832 1820 ?Ss 10:31 0:00 /usr/sbin/cron 104 2033 0.0 0.3 3184 1592 ?Ss 10:31 0:00 /usr/bin/dbus-daemon --system ntp 2090 0.0 0.7 5524 3204 ?Ss 10:31 0:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 102:104 root 2125 0.0 0.6 6224 2868 ?Ss 10:31 0:00 /usr/sbin/sshd nobody2138 0.0 0.3 2024 1400 ?Ss 10:31 0:00 /usr/sbin/thd --daemon --triggers /etc/triggerhappy/triggers.d/ --socket /var/run/thd.socket --pidfile /var/run/thd.pid --user nobody /dev/input/event* root 2219 0.0 0.3 3752 1708 tty1 Ss+ 10:31 0:00 /sbin/getty --noclear 38400 tty1 root 2220 0.0 0.3 3752 1644 tty2 Ss+ 10:31 0:00 /sbin/getty 38400 tty2 root 2221 0.0 0.3 3752 1644 tty3 Ss+ 10:31 0:00 /sbin/getty 38400 tty3 root 0.0 0.3 3752 1700 tty4 Ss+ 10:31 0:00 /sbin/getty 38400 tty4 root 2223 0.0 0.3 3752 1708 tty5 Ss+ 10:31 0:00 /sbin/getty 38400 tty5 root 2224 0.0 0.3 3752 1644 tty6 Ss+ 10:31 0:00 /sbin/getty 38400 tty6 root 2225 0.0 0.3 2072 1588 ttyAMA0 Ss+ 10:31 0:00 /sbin/getty -L ttyAMA0 115200 vt100 root 2226 0.1 1.0 9268 4496 ?Ss 10:36 0:00 sshd: root@pts/0 root 2230 0.4 0.9 5652 4028 pts/0Ss 10:36 0:00 -bash root 2243 0.0 0.3 3392 1480 pts/0S+ 10:37 0:00 tail -f debug root 2244 0.2 1.0 9268 4540 ?Ss 10:38 0:00 sshd: root@pts/1 root 2248 0.5
[weewx-user] Re: Strange activity on Davis2 after changing batteries
DISREGARD: root 2385 0.0 0.0 0 0 ?S10:47 0:00 [kworker/0:0] root 2420 59.1 6.9 69264 31064 ?Sl 10:48 2:25 python /usr/bin/weewxd --daemon --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf root 2442 0.0 0.3 3392 1508 pts/0S+ 10:48 0:00 tail -f syslog root 2449 0.0 0.0 0 0 ?S10:50 0:00 [kworker/u2:0] root 2450 0.0 0.4 4464 2080 pts/1R+ 10:52 0:00 ps -aux My USB connection was not working for some reason. I looked at the SYSLOG and it said there was a USB connection error so I unplugged/plugged in the USB cord to the console and it started back up. This error was preventing weewx from loading properly. I had no idea, so I know what to look for later if the USB cord is not cutting it. Thanks for the replies. -- 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/9eec69bc-9c39-4ecd-b093-369c10f2cfee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] vantagepro2 - Import of driver failed: [errno 2] could not open port /dev/ttyUSB0
root@weewx:/etc/weewx# tail -f /var/log/syslog Oct 8 04:58:34 weewx weewx[1739]: Starting weewx weather system: weewx. Oct 8 04:58:34 weewx systemd[1]: Started LSB: weewx weather system. Oct 8 04:58:34 weewx weewx[1756]: engine: Using configuration file /etc/weewx/weewx.conf Oct 8 04:58:34 weewx weewx[1756]: engine: Debug is 1 Oct 8 04:58:34 weewx weewx[1756]: engine: Initializing engine Oct 8 04:58:34 weewx weewx[1756]: engine: Loading station type Vantage (weewx.drivers.vantage) Oct 8 04:58:34 weewx weewx[1756]: vantage: Driver version is 3.1.1 Oct 8 04:58:34 weewx weewx[1756]: import of driver failed: [Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0' () Oct 8 04:58:34 weewx weewx[1756]: engine: Unable to load driver: [Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0' Oct 8 04:58:34 weewx weewx[1756]: Exiting... I'm installing a second davis2 with weewx and this error appeared after successfully accessing the davis2 dongle for a period of time, then began this error and it wont continue to load. Is this related to the hardware connection to the davis dongle or USB cable/connection or is this a software error? I have a choke on the USB cable. I'm wondering if it does not 'like' the USB cable. -- 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/a79bcd16-ce46-4f6f-a28c-528124e3a5f8%40googlegroups.com.
[weewx-user] New Davis2 weewx install............no data from last year from the dongle
I just installed weewx on a davis2 in a remote location that has been online for 10 years with the DONGLE attached. I started weewx and it only has the last three months of data in the history. Does anyone know why it is not displaying all the previous data on the dongle? Does weewx pull that data by default if it was there, and possibly this means the data has been deleted somehow? THe station owner stated they havent touched anything related to the data. -- 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/582021d5-ea42-4ae8-aae2-d9f0abed0bb6%40googlegroups.com.
[weewx-user] Re: New Davis2 weewx install............no data from last year from the dongle
Correct. The data logger. I was assuming that the logger would store more than the two months of data. So it is storing exactly what it should it seems. Well then, I guess it is doing what it is supposed to. Well dangit, I figured it would store at least a year of data or two. On Tuesday, October 8, 2019 at 8:31:01 PM UTC-5, gjr80 wrote: > > Hi, > > By 'dongle' I presume you mean one of the Davis data loggers. If so the > logger has a fixed memory and stores archive records in a round robin > fashion (ie once memory is full the oldest record is overwritten with the > newest). How long a history you can store depends on your archive interval; > the logger can store 2560 records so at one minute that is a little over 42 > hours, at five minutes just under nine days and at 120 minutes about seven > months. The default 30 minute archive period gives about two months of > recorded history. Sounds like you may have a 60 minute archive period? > > And yes on startup WeeWX will download any (previously unseen) history > from a Davis station. > > Gary > > On Wednesday, 9 October 2019 11:13:08 UTC+10, Joe wrote: >> >> I just installed weewx on a davis2 in a remote location that has been >> online for 10 years with the DONGLE attached. >> >> I started weewx and it only has the last three months of data in the >> history. >> >> Does anyone know why it is not displaying all the previous data on the >> dongle? >> >> Does weewx pull that data by default if it was there, and possibly this >> means the data has been deleted somehow? THe station owner stated they >> havent touched anything related to the data. >> >> >> -- 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/df901be6-8e43-457f-bfa2-bc6df3ca2368%40googlegroups.com.
[weewx-user] Re: Weather station recommendations?
I would never buy anything but a Davis2 Pro. On Wednesday, October 9, 2019 at 6:55:38 PM UTC-5, Timothy Buchanan wrote: > > I have a spare Raspberry Pi3 to run WeeWx, but no weather station yet, and > would like recommendations. Reliability and accuracy are top priorities, > and I'd prefer one of the models marked as tested. I am considering a Davis > Vantage Vue, but would I need to buy their pricey USB interface, or could > it be interfaced another way? What other stations should I consider? Thanks > for all suggestions. > -- 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/cb389902-f2a2-43b0-ae9b-5cd4ac7f01bc%40googlegroups.com.
[weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?
Looks like its all working and accessing the davis OK. Only problem Im having now is the dates and times on the generated HTML are all over the place. Some of it is from a couple days ago, some of it is last night and the mobile and smartphone HTML is not current. On Friday, December 25, 2020 at 8:35:05 PM UTC-6 Joe wrote: > Reimaged it finally and got the database conf file and such transferred > over. > > Now its catching up with all the data its been storing the past few days > in the Davis and publishing the records for last few days. > > I guess it has been a few years since I have done this so its not too bad > I guess. > > Hopefully I dont loose much data. I'm still miffed why I lost 6mo of data > when I restored a backup from 6 months ago but I probably just dont > understand how the database is written is all. > > Such is life! I Do appreciate, as I always do the responses from the > group. > > On Friday, December 25, 2020 at 7:31:09 PM UTC-6 vince wrote: > >> You can get old versions of weewx .deb packages at >> http://weewx.com/downloads/released_versions/ if you know what version >> you used to use. Check your weewx.conf file for the version identifier >> near the top.You could alternately use the 'setup.py' method to install >> current weewx on your ancient os, likely using python2 that your old os >> probably has as its default. >> >> But your preferred path is reflash to a current os and install current >> weewx and then you're good for a long time. You're talking 15 minutes of >> work to do that. >> >> I would suggest not bothering trying a dist-upgrade from debian-7 to >> debian-10, as it's going to take forever and likely will not work anyway. >> Just reimage clean to current RaspiOS which is based on current debian and >> get caught up once and for all. >> >> On Friday, December 25, 2020 at 4:53:02 PM UTC-8 Joe wrote: >> >>> Really sucks I gotta completely re-image and re-set my whole PI board >>> for this. I get used to set-forget . I downloaded the files it needs. >>> Database. conf files etc as the online site says. >>> >>> I was hoping this program would be more backward compatible with the RPI >>> OS. >>> >>> On Friday, December 25, 2020 at 1:06:21 PM UTC-6 vince wrote: >>> >>>> Yup - your os is far too ancient for the libraries the weewx dpkg is >>>> built against. That version went end-of-life in May-2018. >>>> >>>> I'd suggest you reimage with the current RaspiOS from >>>> https://www.raspberrypi.org/software/operating-systems and then you'll >>>> be up to date and supportable. The weewx package works just fine in the >>>> current os. >>>> >>>> On Friday, December 25, 2020 at 2:35:04 AM UTC-8 Joe wrote: >>>> >>>>> That worked. 7.8 >>>>> >>>>> >>>>> PRETTY_NAME="Raspbian GNU/Linux 7 (wheezy)" >>>>> NAME="Raspbian GNU/Linux" >>>>> VERSION_ID="7" >>>>> VERSION="7 (wheezy)" >>>>> ID=raspbian >>>>> ID_LIKE=debian >>>>> ANSI_COLOR="1;31" >>>>> HOME_URL="http://www.raspbian.org/"; >>>>> SUPPORT_URL="http://www.raspbian.org/RaspbianForums"; >>>>> BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"; >>>>> root@raspberrypi:/etc# >>>>> >>>>> On Thursday, December 24, 2020 at 11:44:26 PM UTC-6 vince wrote: >>>>> >>>>>> The current kernel version is 5.4.79 according to the release notes >>>>>> at https://www.raspberrypi.org/software/operating-systems >>>>>> >>>>>> My suspicion is that you are running an ancient os version that is >>>>>> too old for the current packaged version of weewx. >>>>>> >>>>>> Again, please run the following commands and provide the results. >>>>>> >>>>>>- cat /etc/debian_version >>>>>>- cat /etc/os-release >>>>>> >>>>>> >>>>>> On Thursday, December 24, 2020 at 6:26:16 PM UTC-8 Joe wrote: >>>>>> >>>>>>> Neither of those directories exist. >>>>>>> >>>>>>> Its raspberrypi 3.18.7 >>>>>>> >>>>>>> On Thursday, December 24, 2020
Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?
I''m watching with TAIL and I dont see any errors. It's making the images and using FTP to send as needed but the dates and times on the published HTML is all over. Some says 2am, some says last night at 830pm. The FTP files date/time are mostly Dec 26 now, but some are 25th. On Saturday, December 26, 2020 at 5:09:58 AM UTC-6 graha...@gmail.com wrote: > sounds like some files might not be generating. are the timestamps on the > generated files current? errors in log? > > On 26 Dec 2020, at 9:56 pm, Joe wrote: > > Looks like its all working and accessing the davis OK. > > Only problem Im having now is the dates and times on the generated HTML > are all over the place. Some of it is from a couple days ago, some of it > is last night and the mobile and smartphone HTML is not current. > > On Friday, December 25, 2020 at 8:35:05 PM UTC-6 Joe wrote: > >> Reimaged it finally and got the database conf file and such transferred >> over. >> >> Now its catching up with all the data its been storing the past few days >> in the Davis and publishing the records for last few days. >> >> I guess it has been a few years since I have done this so its not too bad >> I guess. >> >> Hopefully I dont loose much data. I'm still miffed why I lost 6mo of >> data when I restored a backup from 6 months ago but I probably just dont >> understand how the database is written is all. >> >> Such is life! I Do appreciate, as I always do the responses from the >> group. >> >> On Friday, December 25, 2020 at 7:31:09 PM UTC-6 vince wrote: >> >>> You can get old versions of weewx .deb packages at >>> http://weewx.com/downloads/released_versions/ if you know what version >>> you used to use. Check your weewx.conf file for the version identifier >>> near the top.You could alternately use the 'setup.py' method to install >>> current weewx on your ancient os, likely using python2 that your old os >>> probably has as its default. >>> >>> But your preferred path is reflash to a current os and install current >>> weewx and then you're good for a long time. You're talking 15 minutes of >>> work to do that. >>> >>> I would suggest not bothering trying a dist-upgrade from debian-7 to >>> debian-10, as it's going to take forever and likely will not work anyway. >>> Just reimage clean to current RaspiOS which is based on current debian and >>> get caught up once and for all. >>> >>> On Friday, December 25, 2020 at 4:53:02 PM UTC-8 Joe wrote: >>> >>>> Really sucks I gotta completely re-image and re-set my whole PI board >>>> for this. I get used to set-forget . I downloaded the files it needs. >>>> Database. conf files etc as the online site says. >>>> >>>> I was hoping this program would be more backward compatible with the >>>> RPI OS. >>>> >>>> On Friday, December 25, 2020 at 1:06:21 PM UTC-6 vince wrote: >>>> >>>>> Yup - your os is far too ancient for the libraries the weewx dpkg is >>>>> built against. That version went end-of-life in May-2018. >>>>> >>>>> I'd suggest you reimage with the current RaspiOS from >>>>> https://www.raspberrypi.org/software/operating-systems and then >>>>> you'll be up to date and supportable. The weewx package works just fine >>>>> in >>>>> the current os. >>>>> >>>>> On Friday, December 25, 2020 at 2:35:04 AM UTC-8 Joe wrote: >>>>> >>>>>> That worked. 7.8 >>>>>> >>>>>> >>>>>> PRETTY_NAME="Raspbian GNU/Linux 7 (wheezy)" >>>>>> NAME="Raspbian GNU/Linux" >>>>>> VERSION_ID="7" >>>>>> VERSION="7 (wheezy)" >>>>>> ID=raspbian >>>>>> ID_LIKE=debian >>>>>> ANSI_COLOR="1;31" >>>>>> HOME_URL="http://www.raspbian.org/"; >>>>>> SUPPORT_URL="http://www.raspbian.org/RaspbianForums"; >>>>>> BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"; >>>>>> root@raspberrypi:/etc# >>>>>> >>>>>> On Thursday, December 24, 2020 at 11:44:26 PM UTC-6 vince wrote: >>>>>> >>>>>>> The current kernel version is 5.4.79 according to the release notes >>>>&
Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?
g -rw-r--r-- 1 root root 9988 Dec 25 20:51 yeartempdew.png -rw-r--r-- 1 root root 8794 Dec 25 20:53 yeartempfeel.png -rw-r--r-- 1 root root 7840 Dec 25 20:53 yeartempin.png -rw-r--r-- 1 root root 7638 Dec 25 20:53 yeartemp.png -rw-r--r-- 1 root root 6920 Dec 25 20:52 yearuv.png -rw-r--r-- 1 root root 11815 Dec 25 20:53 yearvolt.png -rw-r--r-- 1 root root 7589 Dec 25 20:51 yearwinddir.png -rw-r--r-- 1 root root 8958 Dec 25 20:51 yearwind.png -rw-r--r-- 1 root root 7648 Dec 25 20:51 yearwindvec.png On Saturday, December 26, 2020 at 5:54:00 AM UTC-6 graha...@gmail.com wrote: > to reduce the problem space, maybe ignore FTP for now - just look at the > generated files locally. if timestamps are all over the place, either new > ones are not being attempted (skin config error) or they are failing > (template content failure) > > watching tail, sometimes many screenfulls of log are generated at once and > you can miss big chunks. i suggest using an editor to look at the log, line > by line, to confirm (a) it has found the report definition; (b) it is > enabled and will attempt generating all its files; (c) any errors; (d) > completion of report generation > > On 26 Dec 2020, at 10:13 pm, Joe wrote: > > I''m watching with TAIL and I dont see any errors. It's making the images > and using FTP to send as needed but the dates and times on the published > HTML is all over. Some says 2am, some says last night at 830pm. > > The FTP files date/time are mostly Dec 26 now, but some are 25th. > > > -- 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/285c4371-572a-42bc-85e7-c4c3648a2463n%40googlegroups.com.
Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?
Ok I will get a look at it in about a week after a needed vacation. On Sunday, December 27, 2020 at 8:38:26 PM UTC-6 graha...@gmail.com wrote: > the .html timestamps are all current (assuming Dec 27 19:50 is current). > the .png timestamps are current until middle of the month images, then all > old → stopping part way through image generation. > some of the .png timestamps are very late in the 5 minute reporting period > → maybe not finishing one report before starting the next. > you will need to look at (post here) the detailed log showing from before > the start of report generation until past the end of completion of report > generation to see if there is overlap. > or maybe the image generator is crashing part-way → ditto for need to see > detailed logs > > On 28 Dec 2020, at 12:54 pm, Joe wrote: > > -rw-r--r-- 1 root root 7357 Dec 27 19:51 daywind.png > -rw-r--r-- 1 root root 6148 Dec 27 19:51 daywindvec.png > -rw-r--r-- 1 root root 1150 Dec 27 19:46 favicon.ico > drwxr-xr-x 2 root root 4096 Dec 25 20:53 font > -rw-r--r-- 1 root root 7315 Dec 27 19:51 '#FTP.last' > -rw-r--r-- 1 root root 25919 Dec 27 19:50 index.html > -rw-r--r-- 1 root root 564 Dec 27 19:46 mobile.css > -rw-r--r-- 1 root root 2413 Dec 27 19:50 mobile.html > -rw-r--r-- 1 root root 7606 Dec 25 20:48 monthbarometer.png > -rw-r--r-- 1 root root 11985 Dec 27 19:50 month.html > -rw-r--r-- 1 root root 7135 Dec 25 20:48 monthhumidity.png > -rw-r--r-- 1 root root 6519 Dec 25 20:53 monthhum.png > -rw-r--r-- 1 root root 8204 Dec 25 20:51 monthinside.png > -rw-r--r-- 1 root root 5436 Dec 25 20:51 monthpond.png > -rw-r--r-- 1 root root 7674 Dec 25 20:51 monthradiation.png > -rw-r--r-- 1 root root 6976 Dec 25 20:48 monthrain.png > -rw-r--r-- 1 root root 7324 Dec 25 20:51 monthrx.png > -rw-r--r-- 1 root root 9045 Dec 25 20:48 monthtempchill.png > -rw-r--r-- 1 root root 9280 Dec 25 20:48 monthtempdew.png > > > -- 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/e7a08812-2cfd-4413-8cf0-da040a7bfec0n%40googlegroups.com.
Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?
Sandisk extreme with the red and brown two tone color. Unfortuantely, I did not have one of these in the PI at the time. Though I do now. I've never had one fail . On Monday, December 28, 2020 at 7:23:04 PM UTC-6 robcr...@gmail.com wrote: > With all this talk about "good quality" SD cards, can anyone share a > recommendation? > > I have an SSD that I run my main WeeWX/HomeAssistant server on, but I have > several others that I play around with, and need to get some new SD cards > for that purpose, so I figure I may as well get some "good" ones. > > Thanks for any suggestions. > > > On Monday, December 28, 2020 at 4:36:23 AM UTC-8 Joe wrote: > >> Ok I will get a look at it in about a week after a needed vacation. >> >> On Sunday, December 27, 2020 at 8:38:26 PM UTC-6 graha...@gmail.com >> wrote: >> >>> the .html timestamps are all current (assuming Dec 27 19:50 is current). >>> the .png timestamps are current until middle of the month images, then >>> all old → stopping part way through image generation. >>> some of the .png timestamps are very late in the 5 minute reporting >>> period → maybe not finishing one report before starting the next. >>> you will need to look at (post here) the detailed log showing from >>> before the start of report generation until past the end of completion of >>> report generation to see if there is overlap. >>> or maybe the image generator is crashing part-way → ditto for need to >>> see detailed logs >>> >>> On 28 Dec 2020, at 12:54 pm, Joe wrote: >>> >>> -rw-r--r-- 1 root root 7357 Dec 27 19:51 daywind.png >>> -rw-r--r-- 1 root root 6148 Dec 27 19:51 daywindvec.png >>> -rw-r--r-- 1 root root 1150 Dec 27 19:46 favicon.ico >>> drwxr-xr-x 2 root root 4096 Dec 25 20:53 font >>> -rw-r--r-- 1 root root 7315 Dec 27 19:51 '#FTP.last' >>> -rw-r--r-- 1 root root 25919 Dec 27 19:50 index.html >>> -rw-r--r-- 1 root root 564 Dec 27 19:46 mobile.css >>> -rw-r--r-- 1 root root 2413 Dec 27 19:50 mobile.html >>> -rw-r--r-- 1 root root 7606 Dec 25 20:48 monthbarometer.png >>> -rw-r--r-- 1 root root 11985 Dec 27 19:50 month.html >>> -rw-r--r-- 1 root root 7135 Dec 25 20:48 monthhumidity.png >>> -rw-r--r-- 1 root root 6519 Dec 25 20:53 monthhum.png >>> -rw-r--r-- 1 root root 8204 Dec 25 20:51 monthinside.png >>> -rw-r--r-- 1 root root 5436 Dec 25 20:51 monthpond.png >>> -rw-r--r-- 1 root root 7674 Dec 25 20:51 monthradiation.png >>> -rw-r--r-- 1 root root 6976 Dec 25 20:48 monthrain.png >>> -rw-r--r-- 1 root root 7324 Dec 25 20:51 monthrx.png >>> -rw-r--r-- 1 root root 9045 Dec 25 20:48 monthtempchill.png >>> -rw-r--r-- 1 root root 9280 Dec 25 20:48 monthtempdew.png >>> >>> >>> -- 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/3efb56ad-5b36-4530-a492-d22f8ae0e1e1n%40googlegroups.com.
Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?
Yep. But I am away from the house on vacation. I'm still confused why im having trouble drawing graphs and posting current wx data via weewx. On Friday, January 1, 2021 at 12:56:50 PM UTC-6 kk44...@gmail.com wrote: > In german people say (translated word by word): "Who buys cheap, buys > twice." > > weatherl...@gmail.com schrieb am Freitag, 1. Januar 2021 um 18:32:21 > UTC+1: > >> The Meteobridge builder requires a high endurance microSD card for their >> NANO SD unit; I haven’t investigated to see if they come in higher >> capacities though it seems likely they would. >> >> *Choice of microSD Card * >> >> To avoid lots of system fails caused by worn out consumer microSD cards >> we restrict microSD cards that can be used in the NANO to 1GB and 2GB >> industrial SLC cards. These are world-wide available from Mouser and other >> electronic distributors. We decided to enforce use of these high endurance >> cards to avoid having tons of unnecessary support requests and not to harm >> the reputation of the NANO SD by failed cards. Please trust in our >> experience with flash storage issues that there is simply no reasonable way >> to avoid buying of high-price, high-endurance SLC storage. These are the >> currently supported microSD cards: >> >> swissbit SFSD1024N1BM1TO-I-DF-221-STD (microSD Card, 1 GB, SLC Flash, >> -40°C - 85°C) >> swissbit SFSD2048N1BM1MT-I-ME-221-STD (microSD Card, 2 GB, SLC Flash, >> -40°C - 85°C) >> >> swissbit SFSD2048N1BM1MT-E-ME-221-STD (microSD Card, 2 GB, SLC Flash, >> -25°C - 85°C) >> ATP AF2GUDI (microSD Card, 2 GB, SLC Flash, -40°C – 80°C) >> Cactus KS2GRIT-803M (microSD Card, 2 GB, SLC Flash, -45°C – 90°C) >> >> Panasonic SMSC02DA1 (microSD Card, 2 GB, SLC Flash, -40°C - 85°C) >> >> Apacer MSD02GIDI-T (microSD Card, 2 GB, SLC Flash) >> >> >> On 1 Jan, 2021, at 08:52, Joe wrote: >> >> Sandisk extreme with the red and brown two tone color. Unfortuantely, I >> did not have one of these in the PI at the time. Though I do now. I've >> never had one fail . >> >> On Monday, December 28, 2020 at 7:23:04 PM UTC-6 robcr...@gmail.com >> wrote: >> >>> With all this talk about "good quality" SD cards, can anyone share a >>> recommendation? >>> >>> I have an SSD that I run my main WeeWX/HomeAssistant server on, but I >>> have several others that I play around with, and need to get some new SD >>> cards for that purpose, so I figure I may as well get some "good" ones. >>> >>> Thanks for any suggestions. >>> >>> >>> On Monday, December 28, 2020 at 4:36:23 AM UTC-8 Joe wrote: >>> >>>> Ok I will get a look at it in about a week after a needed vacation. >>>> >>>> On Sunday, December 27, 2020 at 8:38:26 PM UTC-6 graha...@gmail.com >>>> wrote: >>>> >>>>> the .html timestamps are all current (assuming Dec 27 19:50 is >>>>> current). >>>>> the .png timestamps are current until middle of the month images, then >>>>> all old → stopping part way through image generation. >>>>> some of the .png timestamps are very late in the 5 minute reporting >>>>> period → maybe not finishing one report before starting the next. >>>>> you will need to look at (post here) the detailed log showing from >>>>> before the start of report generation until past the end of completion of >>>>> report generation to see if there is overlap. >>>>> or maybe the image generator is crashing part-way → ditto for need to >>>>> see detailed logs >>>>> >>>>> On 28 Dec 2020, at 12:54 pm, Joe wrote: >>>>> >>>>> -rw-r--r-- 1 root root 7357 Dec 27 19:51 daywind.png >>>>> -rw-r--r-- 1 root root 6148 Dec 27 19:51 daywindvec.png >>>>> -rw-r--r-- 1 root root 1150 Dec 27 19:46 favicon.ico >>>>> drwxr-xr-x 2 root root 4096 Dec 25 20:53 font >>>>> -rw-r--r-- 1 root root 7315 Dec 27 19:51 '#FTP.last' >>>>> -rw-r--r-- 1 root root 25919 Dec 27 19:50 index.html >>>>> -rw-r--r-- 1 root root 564 Dec 27 19:46 mobile.css >>>>> -rw-r--r-- 1 root root 2413 Dec 27 19:50 mobile.html >>>>> -rw-r--r-- 1 root root 7606 Dec 25 20:48 monthbarometer.png >>>>> -rw-r--r-- 1 root root 11985 Dec 27 19:50 month.html >>>>> -rw-r--r-- 1 root root 7135 Dec 25 20:48 monthhumid
Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?
file /var/www/weewx/RSS/weewx_rss.xml to /RSS/weewx_rss.xml Jan 4 00:26:16 raspberrypi weewx[677] INFO weewx.reportengine: ftpgenerator: Ftp'd 37 files in 11.63 seconds Jan 4 00:26:16 raspberrypi weewx[677] DEBUG weewx.reportengine: Running report 'RSYNC' Jan 4 00:26:16 raspberrypi weewx[677] DEBUG weewx.reportengine: Found configuration file /etc/weewx/skins/Rsync/skin.conf for report 'RSYNC' Jan 4 00:26:16 raspberrypi weewx[677] DEBUG weewx.reportengine: rsyncgenerator: Rsync upload not requested. Skipped. On Sunday, January 3, 2021 at 4:29:38 AM UTC-6 mi...@cougar.eu.com wrote: > This was on of my main concerns when I first moved my WeeWX station to a > Raspberry Pi, so I have added a nightly backup to AWS S3 for the database > and as S3 now has versioning that will be my next addition so I have more > than one backup . > > I haven't gotten around to writing this up yet, but it has been working > uninterrupted for 213 days. > > If you want to know how I did it just reach out, the process is very > similar to my solution for publishing to S3 which I have just finished > writing up this week > > On Friday, January 1, 2021 at 8:35:37 PM UTC lang@googlemail.com > wrote: > >> @ (not only) weatherlist >> >> If you had copied the list completely, 😉 >> >> See below - bold by me. >> >> (but possibly a SSD comes cheaper than the higher capacity SLC micro SD >> cards - still may need an enclosure with USB (best 3) interface; not too >> expensive either) >> >> . >> >> Meteobridge enforces the use of one of the following industrial SLC cards: >> >> .. >> >>- Western Digital/SanDisk SDSDQED-00*8G*-XI, SDSDQED-0*16G*-XI, >>SDSDQED-0*32G*-XI, SDSDQED-064G-XI (microSD Card, 8-*64* GB, SLC >>Flash) >>- Greenliant GLS93MP008G1-I-BZ801 (microSD Card, *8 GB*, SLC Flash) >> >> On 01.01.2021 20:44, Michael Form wrote: >> >> As someone has previously suggested, you can boot and run a Raspberry Pi >> off of a SSD. These are a lot more reliable than most SD cards and are >> available with huge capacities. Unless you are buying a 1 TB or 2 TB SSD, >> they are also relatively inexpensive. I am running several Pis, both models >> 3 and 4, on some 500 GB and 250 GB SSDs with no problems. You can also use >> a MSATA or M2 drive as well. >> >> Although there are off the shelf solutions to do this (check out >> Geekworm), the easiest way is to buy an inexpensive SATA, MSATA or M2 to >> USB external interface and plug it into the Pi's USB port. If you use a >> Pi4, then you can run it as a USB3 device, which is faster. >> >> Mike >> >> On 1/1/2021 2:21 PM, steep...@gmail.com wrote: >> >> There are more SLC cards available from Mouser and other distributors >> with much lager capacities. Those quoted below would struggle to contain an >> operating system, WeeWX and data. >> >> >> >> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for >> Windows 10 >> >> >> >> *From: *weather list >> *Sent: *01 January 2021 17:32 >> *To: *weewx...@googlegroups.com >> *Subject: *Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 >> months of data? >> >> >> >> The Meteobridge builder requires a high endurance microSD card for their >> NANO SD unit; I haven’t investigated to see if they come in higher >> capacities though it seems likely they would. >> >> >> >> *Choice of microSD Card * >> >> To avoid lots of system fails caused by worn out consumer microSD cards >> we restrict microSD cards that can be used in the NANO to 1GB and 2GB >> industrial SLC cards. These are world-wide available from Mouser and other >> electronic distributors. We decided to enforce use of these high endurance >> cards to avoid having tons of unnecessary support requests and not to harm >> the reputation of the NANO SD by failed cards. Please trust in our >> experience with flash storage issues that there is simply no reasonable way >> to avoid buying of high-price, high-endurance SLC storage. These are the >> currently supported microSD cards: >> >> swissbit SFSD1024N1BM1TO-I-DF-221-STD (microSD Card, 1 GB, SLC Flash, >> -40°C - 85°C) >> swissbit SFSD2048N1BM1MT-I-ME-221-STD (microSD Card, 2 GB, SLC Flash, >> -40°C - 85°C) >> >> swissbit SFSD2048N1BM1MT-E-ME-221-STD (microSD Card, 2 GB, SLC Flash, >> -25°C - 85°C) >> ATP AF2GUDI (microSD Card, 2 GB, SLC Flash, -40°C – 80°C) >> Cac
Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?
Log give any clues ? On Monday, January 4, 2021 at 1:36:42 PM UTC-6 sali...@gmail.com wrote: > hi > > happy new year at all > > I had already this issue, now I used a disk ssd for my RPi3b. > > bye > > Patrick > Le 04/01/2021 à 20:18, Xant a écrit : > > > I recently also had a corrupted SD card. Tried many alternatives to > recover data, including trying to mount at a Linux machine (at no prevail). > > The only (Windows) solution that actually worked was, where I was able to > read and retrieve data, was the freeware "DiskInternals Linux Reader": > > https://www.diskinternals.com/linux-reader/ > > > Xant > > On Monday, January 4, 2021 at 6:19:41 AM UTC-5 Joe wrote: > >> GNU nano 3.2 >> syslog >> >> >> >> >> Here is the log >> >> >> Jan 4 00:25:33 raspberrypi weewx[677] INFO weewx.restx: Wunderground-RF: >> Published record 2021-01-04 00:25:33 CST (1609741533) >> Jan 4 00:25:35 raspberrypi weewx[677] INFO weewx.restx: Wunderground-RF: >> Published record 2021-01-04 00:25:35 CST (1609741535) >> Jan 4 00:25:36 raspberrypi weewx[677] INFO weewx.imagegenerator: >> Generated 13 images for report StandardReport in 8.04 seconds >> Jan 4 00:25:36 raspberrypi weewx[677] INFO weewx.reportengine: Copied 0 >> files to /var/www/weewx >> Jan 4 00:25:36 raspberrypi weewx[677] DEBUG weewx.reportengine: Running >> report 'SeasonsReport' >> Jan 4 00:25:36 raspberrypi weewx[677] DEBUG weewx.reportengine: Found >> configuration file /etc/weewx/skins/Seasons/skin.conf for report >> 'SeasonsReport' >> Jan 4 00:25:37 raspberrypi weewx[677] DEBUG weewx.cheetahgenerator: >> Using search list ['weewx.cheetahgenerator.Almanac', >> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', >> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahg$ >> Jan 4 00:25:37 raspberrypi weewx[677] DEBUG weewx.manager: Daily summary >> version is 2 >> Jan 4 00:25:49 raspberrypi weewx[677] INFO weewx.restx: Wunderground-RF: >> Published record 2021-01-04 00:25:49 CST (1609741549) >> Jan 4 00:25:49 raspberrypi weewx[677] INFO weewx.cheetahgenerator: >> Generated 8 files for report SeasonsReport in 12.96 seconds >> Jan 4 00:25:49 raspberrypi weewx[677] DEBUG weewx.manager: Daily summary >> version is 2 >> Jan 4 00:25:57 raspberrypi weewx[677] INFO weewx.imagegenerator: >> Generated 14 images for report SeasonsReport in 7.65 seconds >> Jan 4 00:25:57 raspberrypi weewx[677] INFO weewx.reportengine: Copied 0 >> files to /var/www/weewx >> Jan 4 00:25:57 raspberrypi weewx[677] DEBUG weewx.reportengine: Running >> report 'SmartphoneReport' >> Jan 4 00:25:57 raspberrypi weewx[677] DEBUG weewx.reportengine: Found >> configuration file /etc/weewx/skins/Smartphone/skin.conf for report >> 'SmartphoneReport' >> Jan 4 00:25:58 raspberrypi weewx[677] DEBUG weewx.cheetahgenerator: >> Using search list ['weewx.cheetahgenerator.Almanac', >> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', >> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahg$ >> Jan 4 00:25:58 raspberrypi weewx[677] DEBUG weewx.manager: Daily summary >> version is 2 >> Jan 4 00:25:58 raspberrypi weewx[677] INFO weewx.cheetahgenerator: >> Generated 6 files for report SmartphoneReport in 0.75 seconds >> Jan 4 00:25:58 raspberrypi weewx[677] DEBUG weewx.manager: Daily summary >> version is 2Jan 4 00:26:01 raspberrypi weewx[677] INFO weewx.restx: >> Wunderground-RF: Published record 2021-01-04 00:26:01 CST (1609741561) >> Jan 4 00:26:01 raspberrypi weewx[677] INFO weewx.imagegenerator: >> Generated 6 images for report SmartphoneReport in 3.04 seconds >> Jan 4 00:26:01 raspberrypi weewx[677] INFO weewx.reportengine: Copied 0 >> files to /smartphone >> Jan 4 00:26:01 raspberrypi weewx[677] DEBUG weewx.reportengine: Running >> report 'MobileReport' >> Jan 4 00:26:01 raspberrypi weewx[677] DEBUG weewx.reportengine: Found >> configuration file /etc/weewx/skins/Mobile/skin.conf for report >> 'MobileReport' >> Jan 4 00:26:02 raspberrypi weewx[677] DEBUG weewx.cheetahgenerator: >> Using search list ['weewx.cheetahgenerator.Almanac', >> 'weewx.cheetahgenerator.Station&#
Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?
I upgraded to the most recent release, and it is reporting, generating new graphs on schedule. Not sure why that had any bearing on it, but it's working 100% now. On Tuesday, January 5, 2021 at 5:34:42 PM UTC-6 Joe wrote: > Log give any clues ? > > On Monday, January 4, 2021 at 1:36:42 PM UTC-6 sali...@gmail.com wrote: > >> hi >> >> happy new year at all >> >> I had already this issue, now I used a disk ssd for my RPi3b. >> >> bye >> >> Patrick >> Le 04/01/2021 à 20:18, Xant a écrit : >> >> >> I recently also had a corrupted SD card. Tried many alternatives to >> recover data, including trying to mount at a Linux machine (at no prevail). >> >> The only (Windows) solution that actually worked was, where I was able to >> read and retrieve data, was the freeware "DiskInternals Linux Reader": >> >> https://www.diskinternals.com/linux-reader/ >> >> >> Xant >> >> On Monday, January 4, 2021 at 6:19:41 AM UTC-5 Joe wrote: >> >>> GNU nano 3.2 >>> syslog >>> >>> >>> >>> >>> Here is the log >>> >>> >>> Jan 4 00:25:33 raspberrypi weewx[677] INFO weewx.restx: >>> Wunderground-RF: Published record 2021-01-04 00:25:33 CST (1609741533) >>> Jan 4 00:25:35 raspberrypi weewx[677] INFO weewx.restx: >>> Wunderground-RF: Published record 2021-01-04 00:25:35 CST (1609741535) >>> Jan 4 00:25:36 raspberrypi weewx[677] INFO weewx.imagegenerator: >>> Generated 13 images for report StandardReport in 8.04 seconds >>> Jan 4 00:25:36 raspberrypi weewx[677] INFO weewx.reportengine: Copied 0 >>> files to /var/www/weewx >>> Jan 4 00:25:36 raspberrypi weewx[677] DEBUG weewx.reportengine: Running >>> report 'SeasonsReport' >>> Jan 4 00:25:36 raspberrypi weewx[677] DEBUG weewx.reportengine: Found >>> configuration file /etc/weewx/skins/Seasons/skin.conf for report >>> 'SeasonsReport' >>> Jan 4 00:25:37 raspberrypi weewx[677] DEBUG weewx.cheetahgenerator: >>> Using search list ['weewx.cheetahgenerator.Almanac', >>> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', >>> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahg$ >>> Jan 4 00:25:37 raspberrypi weewx[677] DEBUG weewx.manager: Daily >>> summary version is 2 >>> Jan 4 00:25:49 raspberrypi weewx[677] INFO weewx.restx: >>> Wunderground-RF: Published record 2021-01-04 00:25:49 CST (1609741549) >>> Jan 4 00:25:49 raspberrypi weewx[677] INFO weewx.cheetahgenerator: >>> Generated 8 files for report SeasonsReport in 12.96 seconds >>> Jan 4 00:25:49 raspberrypi weewx[677] DEBUG weewx.manager: Daily >>> summary version is 2 >>> Jan 4 00:25:57 raspberrypi weewx[677] INFO weewx.imagegenerator: >>> Generated 14 images for report SeasonsReport in 7.65 seconds >>> Jan 4 00:25:57 raspberrypi weewx[677] INFO weewx.reportengine: Copied 0 >>> files to /var/www/weewx >>> Jan 4 00:25:57 raspberrypi weewx[677] DEBUG weewx.reportengine: Running >>> report 'SmartphoneReport' >>> Jan 4 00:25:57 raspberrypi weewx[677] DEBUG weewx.reportengine: Found >>> configuration file /etc/weewx/skins/Smartphone/skin.conf for report >>> 'SmartphoneReport' >>> Jan 4 00:25:58 raspberrypi weewx[677] DEBUG weewx.cheetahgenerator: >>> Using search list ['weewx.cheetahgenerator.Almanac', >>> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', >>> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahg$ >>> Jan 4 00:25:58 raspberrypi weewx[677] DEBUG weewx.manager: Daily >>> summary version is 2 >>> Jan 4 00:25:58 raspberrypi weewx[677] INFO weewx.cheetahgenerator: >>> Generated 6 files for report SmartphoneReport in 0.75 seconds >>> Jan 4 00:25:58 raspberrypi weewx[677] DEBUG weewx.manager: Daily >>> summary version is 2Jan 4 00:26:01 raspberrypi weewx[677] INFO >>> weewx.restx: Wunderground-RF: Published record 2021-01-04 00:26:01 CST >>> (1609741561) >>> Jan 4 00:26:01 raspberrypi weewx[677] INFO weewx.imagegenerator: >>> Generated 6 images for report SmartphoneReport in 3.04 seconds >>> Jan 4 00:26:01 raspberryp
[weewx-user] copied 0 files to /var/www/html/weewx
The HTML Files are from OCT 7, for some reason its not copying the generated files to the HTML directory and its uploading the same old files every time. Should I delete the old files? Oct 15 18:15:41 weewx weewx[24814]: reportengine: Report 'RSYNC' not enabled. Skipping. Oct 15 18:17:01 weewx CRON[29196]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 15 18:20:14 weewx weewx[24814]: vantage: Getting archive packets since 2020-10-07 17:50:00 EDT (1602107400) Oct 15 18:20:14 weewx weewx[24814]: vantage: Gentle wake up of console successful Oct 15 18:20:16 weewx weewx[24814]: vantage: Retrieving 462 page(s); starting index= 0 Oct 15 18:20:16 weewx weewx[24814]: vantage: DMPAFT complete: page timestamp 2020-10-07 14:40:00 EDT (1602096000) less than final timestamp 2020-10-07 17:50:00 EDT (1602107400) Oct 15 18:20:16 weewx weewx[24814]: vantage: Catch up complete. Oct 15 18:20:16 weewx weewx[24814]: reportengine: Running reports for latest time in the database. Oct 15 18:20:16 weewx weewx[24814]: vantage: Requesting 200 LOOP packets. Oct 15 18:20:16 weewx weewx[24814]: reportengine: Running report 'SeasonsReport' Oct 15 18:20:16 weewx weewx[24814]: vantage: Gentle wake up of console successful Oct 15 18:20:16 weewx weewx[24814]: reportengine: Found configuration file /etc/weewx/skins/Seasons/skin.conf for report 'SeasonsReport' Oct 15 18:20:16 weewx weewx[24814]: cheetahgenerator: using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras'] Oct 15 18:20:16 weewx weewx[24814]: manager: Daily summary version is 2.0 Oct 15 18:20:18 weewx weewx[24814]: cheetahgenerator: Generated 8 files for report SeasonsReport in 2.13 seconds Oct 15 18:20:19 weewx weewx[24814]: manager: Daily summary version is 2.0 Oct 15 18:20:20 weewx weewx[24814]: imagegenerator: Generated 14 images for SeasonsReport in 1.10 seconds Oct 15 18:20:20 weewx weewx[24814]: copygenerator: copied 0 files to /var/www/html/weewx Oct 15 18:20:20 weewx weewx[24814]: reportengine: Running report 'SmartphoneReport' Oct 15 18:20:20 weewx weewx[24814]: reportengine: Found configuration file /etc/weewx/skins/Smartphone/skin.conf for report 'SmartphoneReport' Oct 15 18:20:20 weewx weewx[24814]: cheetahgenerator: using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras'] Oct 15 18:20:20 weewx weewx[24814]: manager: Daily summary version is 2.0 Oct 15 18:20:20 weewx weewx[24814]: cheetahgenerator: Generated 6 files for report SmartphoneReport in 0.11 seconds Oct 15 18:20:20 weewx weewx[24814]: manager: Daily summary version is 2.0 Oct 15 18:20:20 weewx weewx[24814]: imagegenerator: Generated 6 images for SmartphoneReport in 0.42 seconds Oct 15 18:20:20 weewx weewx[24814]: copygenerator: copied 0 files to /var/www/html/weewx Oct 15 18:20:20 weewx weewx[24814]: reportengine: Running report 'MobileReport' Oct 15 18:20:20 weewx weewx[24814]: reportengine: Found configuration file /etc/weewx/skins/Mobile/skin.conf for report 'MobileReport' Oct 15 18:20:20 weewx weewx[24814]: cheetahgenerator: using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras'] Oct 15 18:20:20 weewx weewx[24814]: manager: Daily summary version is 2.0 Oct 15 18:20:20 weewx weewx[24814]: cheetahgenerator: Generated 1 files for report MobileReport in 0.04 seconds Oct 15 18:20:20 weewx weewx[24814]: manager: Daily summary version is 2.0 Oct 15 18:20:21 weewx weewx[24814]: imagegenerator: Generated 4 images for MobileReport in 0.29 seconds Oct 15 18:20:21 weewx weewx[24814]: copygenerator: copied 0 files to /var/www/html/weewx Oct 15 18:20:21 weewx weewx[24814]: reportengine: Running report 'StandardReport' Oct 15 18:20:21 weewx weewx[24814]: reportengine: Found configuration file /etc/weewx/skins/Standard/skin.conf for report 'StandardReport' Oct 15 18:20:21 weewx weewx[24814]: cheetahgenerator: using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras'] Oct 15 18:20:21 weewx weewx[24814]: manager: Daily summary version is 2.0 Oct 15 18:20:23 weewx weewx[24814]: cheetahgenerator: Generated 14 files for report StandardReport in 1.97 seconds Oct 15 18:20:23 weewx weewx[24814]: manager: Daily summary version is 2.0 Oct 15 18:20:23 weewx weewx[24814]: imagegenerator: Generated 12 images for StandardReport in 0.85 seconds Oct 15 18:20:23 weewx weewx[24814]: copygenerator: copied 0 files to /var/www/htm
[weewx-user] Re: copied 0 files to /var/www/html/weewx
Curious then why if its normal you think there is a corrupt station memory? On Thursday, October 15, 2020 at 6:24:56 PM UTC-5 gjr80 wrote: > Hi, > > WeeWX is not receiving any archive records from your station, hence > nothing is saved to archive and your generated reports are unchanged. It's > possible you have corrupt station memory. I recommend you work through the > Corrupt > station memory > <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory> > > section of the Troubleshooting Davis stations > <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station> > > wiki entry. > > By the way, seeing 0 files copied in copygenerator log entry lines like: > > Oct 15 18:20:23 weewx weewx[24814]: copygenerator: copied 0 files to > /var/www/html/weewx > > is quite normal. > > Gary > > On Friday, 16 October 2020 at 08:23:27 UTC+10 Joe wrote: > >> The HTML Files are from OCT 7, for some reason its not copying the >> generated files to the HTML directory and its uploading the same old files >> every time. >> >> Should I delete the old files? >> >> >> >> >> >> >> >> >> Oct 15 18:15:41 weewx weewx[24814]: reportengine: Report 'RSYNC' not >> enabled. Skipping. >> Oct 15 18:17:01 weewx CRON[29196]: (root) CMD ( cd / && run-parts >> --report /etc/cron.hourly) >> Oct 15 18:20:14 weewx weewx[24814]: vantage: Getting archive packets >> since 2020-10-07 17:50:00 EDT (1602107400) >> Oct 15 18:20:14 weewx weewx[24814]: vantage: Gentle wake up of console >> successful >> Oct 15 18:20:16 weewx weewx[24814]: vantage: Retrieving 462 page(s); >> starting index= 0 >> Oct 15 18:20:16 weewx weewx[24814]: vantage: DMPAFT complete: page >> timestamp 2020-10-07 14:40:00 EDT (1602096000) less than final timestamp >> 2020-10-07 17:50:00 EDT (1602107400) >> Oct 15 18:20:16 weewx weewx[24814]: vantage: Catch up complete. >> Oct 15 18:20:16 weewx weewx[24814]: reportengine: Running reports for >> latest time in the database. >> Oct 15 18:20:16 weewx weewx[24814]: vantage: Requesting 200 LOOP packets. >> Oct 15 18:20:16 weewx weewx[24814]: reportengine: Running report >> 'SeasonsReport' >> Oct 15 18:20:16 weewx weewx[24814]: vantage: Gentle wake up of console >> successful >> Oct 15 18:20:16 weewx weewx[24814]: reportengine: Found configuration >> file /etc/weewx/skins/Seasons/skin.conf for report 'SeasonsReport' >> Oct 15 18:20:16 weewx weewx[24814]: cheetahgenerator: using search list >> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', >> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', >> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras'] >> Oct 15 18:20:16 weewx weewx[24814]: manager: Daily summary version is 2.0 >> Oct 15 18:20:18 weewx weewx[24814]: cheetahgenerator: Generated 8 files >> for report SeasonsReport in 2.13 seconds >> Oct 15 18:20:19 weewx weewx[24814]: manager: Daily summary version is 2.0 >> Oct 15 18:20:20 weewx weewx[24814]: imagegenerator: Generated 14 images >> for SeasonsReport in 1.10 seconds >> Oct 15 18:20:20 weewx weewx[24814]: copygenerator: copied 0 files to >> /var/www/html/weewx >> Oct 15 18:20:20 weewx weewx[24814]: reportengine: Running report >> 'SmartphoneReport' >> Oct 15 18:20:20 weewx weewx[24814]: reportengine: Found configuration >> file /etc/weewx/skins/Smartphone/skin.conf for report 'SmartphoneReport' >> Oct 15 18:20:20 weewx weewx[24814]: cheetahgenerator: using search list >> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', >> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', >> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras'] >> Oct 15 18:20:20 weewx weewx[24814]: manager: Daily summary version is 2.0 >> Oct 15 18:20:20 weewx weewx[24814]: cheetahgenerator: Generated 6 files >> for report SmartphoneReport in 0.11 seconds >> Oct 15 18:20:20 weewx weewx[24814]: manager: Daily summary version is 2.0 >> Oct 15 18:20:20 weewx weewx[24814]: imagegenerator: Generated 6 images >> for SmartphoneReport in 0.42 seconds >> Oct 15 18:20:20 weewx weewx[24814]: copygenerator: copied 0 files to >> /var/www/html/weewx >> Oct 15 18:20:20 weewx weewx[24814]: reportengine: Running report >> 'MobileReport' >> Oct 15 18:20:20 wee
[weewx-user] Re: copied 0 files to /var/www/html/weewx
I had to do the DUMP and CLEAR command unfortunately. It's working again. On Thursday, October 15, 2020 at 7:31:44 PM UTC-5 gjr80 wrote: > Deleting files will not force the copy generator to copy them again on the > next report cycle. Copy once is executed once on the first report cycle > after WeeWX startup. Copy always is executed on every report cycle. In both > cases the copy generator is executed irrespective of whether the > destination files exist or not. > > Gary > > On Friday, 16 October 2020 at 09:59:47 UTC+10 Greg from Oz wrote: > >> Delete the files and see if they are regenerated. >> >> On Friday, 16 October 2020 at 10:42:35 UTC+11 Joe wrote: >> >>> Curious then why if its normal you think there is a corrupt station >>> memory? >>> >>> On Thursday, October 15, 2020 at 6:24:56 PM UTC-5 gjr80 wrote: >>> >>>> Hi, >>>> >>>> WeeWX is not receiving any archive records from your station, hence >>>> nothing is saved to archive and your generated reports are unchanged. It's >>>> possible you have corrupt station memory. I recommend you work through the >>>> Corrupt >>>> station memory >>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory> >>>> >>>> section of the Troubleshooting Davis stations >>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station> >>>> >>>> wiki entry. >>>> >>>> By the way, seeing 0 files copied in copygenerator log entry lines like: >>>> >>>> Oct 15 18:20:23 weewx weewx[24814]: copygenerator: copied 0 files to >>>> /var/www/html/weewx >>>> >>>> is quite normal. >>>> >>>> Gary >>>> >>>> On Friday, 16 October 2020 at 08:23:27 UTC+10 Joe wrote: >>>> >>>>> The HTML Files are from OCT 7, for some reason its not copying the >>>>> generated files to the HTML directory and its uploading the same old >>>>> files >>>>> every time. >>>>> >>>>> Should I delete the old files? >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Oct 15 18:15:41 weewx weewx[24814]: reportengine: Report 'RSYNC' not >>>>> enabled. Skipping. >>>>> Oct 15 18:17:01 weewx CRON[29196]: (root) CMD ( cd / && run-parts >>>>> --report /etc/cron.hourly) >>>>> Oct 15 18:20:14 weewx weewx[24814]: vantage: Getting archive packets >>>>> since 2020-10-07 17:50:00 EDT (1602107400) >>>>> Oct 15 18:20:14 weewx weewx[24814]: vantage: Gentle wake up of console >>>>> successful >>>>> Oct 15 18:20:16 weewx weewx[24814]: vantage: Retrieving 462 page(s); >>>>> starting index= 0 >>>>> Oct 15 18:20:16 weewx weewx[24814]: vantage: DMPAFT complete: page >>>>> timestamp 2020-10-07 14:40:00 EDT (1602096000) less than final timestamp >>>>> 2020-10-07 17:50:00 EDT (1602107400) >>>>> Oct 15 18:20:16 weewx weewx[24814]: vantage: Catch up complete. >>>>> Oct 15 18:20:16 weewx weewx[24814]: reportengine: Running reports for >>>>> latest time in the database. >>>>> Oct 15 18:20:16 weewx weewx[24814]: vantage: Requesting 200 LOOP >>>>> packets. >>>>> Oct 15 18:20:16 weewx weewx[24814]: reportengine: Running report >>>>> 'SeasonsReport' >>>>> Oct 15 18:20:16 weewx weewx[24814]: vantage: Gentle wake up of console >>>>> successful >>>>> Oct 15 18:20:16 weewx weewx[24814]: reportengine: Found configuration >>>>> file /etc/weewx/skins/Seasons/skin.conf for report 'SeasonsReport' >>>>> Oct 15 18:20:16 weewx weewx[24814]: cheetahgenerator: using search >>>>> list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', >>>>> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', >>>>> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras'] >>>>> Oct 15 18:20:16 weewx weewx[24814]: manager: Daily summary version is >>>>> 2.0 >>>>> Oct 15 18:20:18 weewx weewx[24814]: cheetahgenerator: Generated 8 >>>>> files for report
[weewx-user] Re: copied 0 files to /var/www/html/weewx
I had to do the CLEAR / DUMP again today. It took about three days for it to happen again where it was failing to update online. Is there a way to test/look at the dongle memory chip to determine if it is " bad " ? On Friday, October 16, 2020 at 4:47:54 AM UTC-5 Joe wrote: > I had to do the DUMP and CLEAR command unfortunately. > > It's working again. > > On Thursday, October 15, 2020 at 7:31:44 PM UTC-5 gjr80 wrote: > >> Deleting files will not force the copy generator to copy them again on >> the next report cycle. Copy once is executed once on the first report cycle >> after WeeWX startup. Copy always is executed on every report cycle. In both >> cases the copy generator is executed irrespective of whether the >> destination files exist or not. >> >> Gary >> >> On Friday, 16 October 2020 at 09:59:47 UTC+10 Greg from Oz wrote: >> >>> Delete the files and see if they are regenerated. >>> >>> On Friday, 16 October 2020 at 10:42:35 UTC+11 Joe wrote: >>> >>>> Curious then why if its normal you think there is a corrupt station >>>> memory? >>>> >>>> On Thursday, October 15, 2020 at 6:24:56 PM UTC-5 gjr80 wrote: >>>> >>>>> Hi, >>>>> >>>>> WeeWX is not receiving any archive records from your station, hence >>>>> nothing is saved to archive and your generated reports are unchanged. >>>>> It's >>>>> possible you have corrupt station memory. I recommend you work through >>>>> the Corrupt >>>>> station memory >>>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory> >>>>> >>>>> section of the Troubleshooting Davis stations >>>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station> >>>>> >>>>> wiki entry. >>>>> >>>>> By the way, seeing 0 files copied in copygenerator log entry lines >>>>> like: >>>>> >>>>> Oct 15 18:20:23 weewx weewx[24814]: copygenerator: copied 0 files to >>>>> /var/www/html/weewx >>>>> >>>>> is quite normal. >>>>> >>>>> Gary >>>>> >>>>> On Friday, 16 October 2020 at 08:23:27 UTC+10 Joe wrote: >>>>> >>>>>> The HTML Files are from OCT 7, for some reason its not copying the >>>>>> generated files to the HTML directory and its uploading the same old >>>>>> files >>>>>> every time. >>>>>> >>>>>> Should I delete the old files? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Oct 15 18:15:41 weewx weewx[24814]: reportengine: Report 'RSYNC' not >>>>>> enabled. Skipping. >>>>>> Oct 15 18:17:01 weewx CRON[29196]: (root) CMD ( cd / && run-parts >>>>>> --report /etc/cron.hourly) >>>>>> Oct 15 18:20:14 weewx weewx[24814]: vantage: Getting archive packets >>>>>> since 2020-10-07 17:50:00 EDT (1602107400) >>>>>> Oct 15 18:20:14 weewx weewx[24814]: vantage: Gentle wake up of >>>>>> console successful >>>>>> Oct 15 18:20:16 weewx weewx[24814]: vantage: Retrieving 462 page(s); >>>>>> starting index= 0 >>>>>> Oct 15 18:20:16 weewx weewx[24814]: vantage: DMPAFT complete: page >>>>>> timestamp 2020-10-07 14:40:00 EDT (1602096000) less than final timestamp >>>>>> 2020-10-07 17:50:00 EDT (1602107400) >>>>>> Oct 15 18:20:16 weewx weewx[24814]: vantage: Catch up complete. >>>>>> Oct 15 18:20:16 weewx weewx[24814]: reportengine: Running reports for >>>>>> latest time in the database. >>>>>> Oct 15 18:20:16 weewx weewx[24814]: vantage: Requesting 200 LOOP >>>>>> packets. >>>>>> Oct 15 18:20:16 weewx weewx[24814]: reportengine: Running report >>>>>> 'SeasonsReport' >>>>>> Oct 15 18:20:16 weewx weewx[24814]: vantage: Gentle wake up of >>>>>> console successful >>>>>> Oct 15 18:20:16 weewx weewx[24814]: reportengine: Found configuration >>>>>> file /etc/weewx/skins/Seasons/skin.conf for repor
[weewx-user] Corrupted Memory card. Now I lost 6 months of data?
I'm curious if anyone has any suggestions on this. I had to revert back to a WEEWX backup from June of this year. I re imaged the SD card and booted it up. It began doing its thing. I loaded the HTML and, the graph has 6 months of data not listed on the graphs. Is there something I should be doing when I revert to a backup? Thanks again guys. -- 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/218c77f0-6736-4c7a-b5b4-ebf2aa8d38f6n%40googlegroups.com.
Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?
I appreciate the responses. I'm having trouble updating to the newest version now so I'm not sure what went wrong overall. On Monday, December 21, 2020 at 3:08:42 PM UTC-6 vince wrote: > (sigh - sqlite3 db in my previous post, of course...) > -- 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/d3cca3aa-689c-45a4-a9f7-eb2937e9e44dn%40googlegroups.com.
Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?
It says the package is not understood. I don't get this one. root@raspberrypi:~# sudo apt-get install weewx Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: sqlite ftp python-dev python-pip The following packages will be upgraded: weewx 1 upgraded, 0 newly installed, 0 to remove and 207 not upgraded. Need to get 0 B/1,207 kB of archives. After this operation, 645 kB disk space will be freed. E: /var/cache/apt/archives/weewx_4.2.0-1_all.deb not a valid DEB package. E: Prior errors apply to /var/cache/apt/archives/weewx_4.2.0-1_all.deb debconf: apt-extracttemplates failed: No such file or directory dpkg-deb: error: archive '/var/cache/apt/archives/weewx_4.2.0-1_all.deb' contains not understood data member control.tar.xz, giving up dpkg: error processing /var/cache/apt/archives/weewx_4.2.0-1_all.deb (--unpack): subprocess dpkg-deb --control returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/weewx_4.2.0-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) root@raspberrypi:~# On Wednesday, December 23, 2020 at 9:49:43 AM UTC-6 vince wrote: > On Wednesday, December 23, 2020 at 7:42:49 AM UTC-8 Joe wrote: > >> I'm having trouble updating to the newest version now so I'm not sure >> what went wrong overall. >> > > In the absence of seeing any logs we don't either. > > -- 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/4a2e130e-7701-4511-bad6-26a0faa94864n%40googlegroups.com.
[weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?
Right it was from July this year. I don't have the 'current' one because the memory card suddenly died and was not accessable. I assumed the online portion would be retained . On Monday, December 21, 2020 at 2:33:25 AM UTC-6 michael.k...@gmx.at wrote: > If you didn't put the caurrent database, holding the values up until now, > on the card, after reverting, that's exactly the expected behaviour. > > Joe schrieb am Montag, 21. Dezember 2020 um 03:22:33 UTC+1: > >> I'm curious if anyone has any suggestions on this. >> >> I had to revert back to a WEEWX backup from June of this year. >> >> I re imaged the SD card and booted it up. It began doing its thing. >> >> I loaded the HTML and, the graph has 6 months of data not listed on the >> graphs. >> >> Is there something I should be doing when I revert to a backup? >> >> Thanks again guys. >> > -- 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/ec74ff14-2bc6-44e9-8501-8d2e914d6c86n%40googlegroups.com.
[weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?
You mean to say running on the SD-CARD is bad idea? I do get the inherent nature of SD-CARDS being unpredictible. But I buy high quality cards. The one I had been using was not unfortunately, but I switched to a red label super fast sandisk. using an SSD would definitely be a good idea in my case. On Monday, December 21, 2020 at 10:31:18 AM UTC-6 wes...@gmail.com wrote: > running an RPI on an SSD is a bad idea as kk44 point out. run your RPI on > an SSD and life will be way better. > > -- 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/c3449e5e-359a-44c2-a09e-7325904fc104n%40googlegroups.com.
[weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?
Neither of those directories exist. Its raspberrypi 3.18.7 On Thursday, December 24, 2020 at 9:53:49 AM UTC-6 vince wrote: > On Thursday, December 24, 2020 at 4:33:57 AM UTC-8 Joe wrote: > >> You mean to say running on the SD-CARD is bad idea? > > > Not bad, but not great if the card and power aren't quality. But yes I > misstyped my original reply. > > Re: your previous message containing " *d**pkg-deb: error: archive > '/var/cache/apt/archives/weewx_4.2.0-1_all.deb' contains not understood > data member control.tar.xz, giving up*", that's an unusual message. > > What version of raspi os are you running ? > Can we see the contents of /etc/os-release and /etc/debian_version please ? > > > -- 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/342d1470-c9ce-48dc-b9ae-884c589d9dddn%40googlegroups.com.
[weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?
That worked. 7.8 PRETTY_NAME="Raspbian GNU/Linux 7 (wheezy)" NAME="Raspbian GNU/Linux" VERSION_ID="7" VERSION="7 (wheezy)" ID=raspbian ID_LIKE=debian ANSI_COLOR="1;31" HOME_URL="http://www.raspbian.org/"; SUPPORT_URL="http://www.raspbian.org/RaspbianForums"; BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"; root@raspberrypi:/etc# On Thursday, December 24, 2020 at 11:44:26 PM UTC-6 vince wrote: > The current kernel version is 5.4.79 according to the release notes at > https://www.raspberrypi.org/software/operating-systems > > My suspicion is that you are running an ancient os version that is too old > for the current packaged version of weewx. > > Again, please run the following commands and provide the results. > >- cat /etc/debian_version >- cat /etc/os-release > > > On Thursday, December 24, 2020 at 6:26:16 PM UTC-8 Joe wrote: > >> Neither of those directories exist. >> >> Its raspberrypi 3.18.7 >> >> On Thursday, December 24, 2020 at 9:53:49 AM UTC-6 vince wrote: >> >>> On Thursday, December 24, 2020 at 4:33:57 AM UTC-8 Joe wrote: >>> >>>> You mean to say running on the SD-CARD is bad idea? >>> >>> >>> Not bad, but not great if the card and power aren't quality. But yes I >>> misstyped my original reply. >>> >>> Re: your previous message containing " *d**pkg-deb: error: archive >>> '/var/cache/apt/archives/weewx_4.2.0-1_all.deb' contains not understood >>> data member control.tar.xz, giving up*", that's an unusual message. >>> >>> What version of raspi os are you running ? >>> Can we see the contents of /etc/os-release and /etc/debian_version >>> please ? >>> >>> >>> -- 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/8f5b6acc-68a8-45f2-9006-3769a3458aa0n%40googlegroups.com.
[weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?
Well then. That explains that. Any suggestions on how to save my database data? On Friday, December 25, 2020 at 1:06:21 PM UTC-6 vince wrote: > Yup - your os is far too ancient for the libraries the weewx dpkg is built > against. That version went end-of-life in May-2018. > > I'd suggest you reimage with the current RaspiOS from > https://www.raspberrypi.org/software/operating-systems and then you'll be > up to date and supportable. The weewx package works just fine in the > current os. > > On Friday, December 25, 2020 at 2:35:04 AM UTC-8 Joe wrote: > >> That worked. 7.8 >> >> >> PRETTY_NAME="Raspbian GNU/Linux 7 (wheezy)" >> NAME="Raspbian GNU/Linux" >> VERSION_ID="7" >> VERSION="7 (wheezy)" >> ID=raspbian >> ID_LIKE=debian >> ANSI_COLOR="1;31" >> HOME_URL="http://www.raspbian.org/"; >> SUPPORT_URL="http://www.raspbian.org/RaspbianForums"; >> BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"; >> root@raspberrypi:/etc# >> >> On Thursday, December 24, 2020 at 11:44:26 PM UTC-6 vince wrote: >> >>> The current kernel version is 5.4.79 according to the release notes at >>> https://www.raspberrypi.org/software/operating-systems >>> >>> My suspicion is that you are running an ancient os version that is too >>> old for the current packaged version of weewx. >>> >>> Again, please run the following commands and provide the results. >>> >>>- cat /etc/debian_version >>> - cat /etc/os-release >>> >>> >>> On Thursday, December 24, 2020 at 6:26:16 PM UTC-8 Joe wrote: >>> >>>> Neither of those directories exist. >>>> >>>> Its raspberrypi 3.18.7 >>>> >>>> On Thursday, December 24, 2020 at 9:53:49 AM UTC-6 vince wrote: >>>> >>>>> On Thursday, December 24, 2020 at 4:33:57 AM UTC-8 Joe wrote: >>>>> >>>>>> You mean to say running on the SD-CARD is bad idea? >>>>> >>>>> >>>>> Not bad, but not great if the card and power aren't quality. But yes >>>>> I misstyped my original reply. >>>>> >>>>> Re: your previous message containing " *d**pkg-deb: error: archive >>>>> '/var/cache/apt/archives/weewx_4.2.0-1_all.deb' contains not understood >>>>> data member control.tar.xz, giving up*", that's an unusual message. >>>>> >>>>> What version of raspi os are you running ? >>>>> Can we see the contents of /etc/os-release and /etc/debian_version >>>>> please ? >>>>> >>>>> >>>>> -- 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/49a7b36b-13cb-4114-bb3f-ebfb5c285570n%40googlegroups.com.
[weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?
Really sucks I gotta completely re-image and re-set my whole PI board for this. I get used to set-forget . I downloaded the files it needs. Database. conf files etc as the online site says. I was hoping this program would be more backward compatible with the RPI OS. On Friday, December 25, 2020 at 1:06:21 PM UTC-6 vince wrote: > Yup - your os is far too ancient for the libraries the weewx dpkg is built > against. That version went end-of-life in May-2018. > > I'd suggest you reimage with the current RaspiOS from > https://www.raspberrypi.org/software/operating-systems and then you'll be > up to date and supportable. The weewx package works just fine in the > current os. > > On Friday, December 25, 2020 at 2:35:04 AM UTC-8 Joe wrote: > >> That worked. 7.8 >> >> >> PRETTY_NAME="Raspbian GNU/Linux 7 (wheezy)" >> NAME="Raspbian GNU/Linux" >> VERSION_ID="7" >> VERSION="7 (wheezy)" >> ID=raspbian >> ID_LIKE=debian >> ANSI_COLOR="1;31" >> HOME_URL="http://www.raspbian.org/"; >> SUPPORT_URL="http://www.raspbian.org/RaspbianForums"; >> BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"; >> root@raspberrypi:/etc# >> >> On Thursday, December 24, 2020 at 11:44:26 PM UTC-6 vince wrote: >> >>> The current kernel version is 5.4.79 according to the release notes at >>> https://www.raspberrypi.org/software/operating-systems >>> >>> My suspicion is that you are running an ancient os version that is too >>> old for the current packaged version of weewx. >>> >>> Again, please run the following commands and provide the results. >>> >>>- cat /etc/debian_version >>> - cat /etc/os-release >>> >>> >>> On Thursday, December 24, 2020 at 6:26:16 PM UTC-8 Joe wrote: >>> >>>> Neither of those directories exist. >>>> >>>> Its raspberrypi 3.18.7 >>>> >>>> On Thursday, December 24, 2020 at 9:53:49 AM UTC-6 vince wrote: >>>> >>>>> On Thursday, December 24, 2020 at 4:33:57 AM UTC-8 Joe wrote: >>>>> >>>>>> You mean to say running on the SD-CARD is bad idea? >>>>> >>>>> >>>>> Not bad, but not great if the card and power aren't quality. But yes >>>>> I misstyped my original reply. >>>>> >>>>> Re: your previous message containing " *d**pkg-deb: error: archive >>>>> '/var/cache/apt/archives/weewx_4.2.0-1_all.deb' contains not understood >>>>> data member control.tar.xz, giving up*", that's an unusual message. >>>>> >>>>> What version of raspi os are you running ? >>>>> Can we see the contents of /etc/os-release and /etc/debian_version >>>>> please ? >>>>> >>>>> >>>>> -- 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/2dfc7a65-53b1-47e4-88a4-290c54b7d6a3n%40googlegroups.com.
[weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?
Reimaged it finally and got the database conf file and such transferred over. Now its catching up with all the data its been storing the past few days in the Davis and publishing the records for last few days. I guess it has been a few years since I have done this so its not too bad I guess. Hopefully I dont loose much data. I'm still miffed why I lost 6mo of data when I restored a backup from 6 months ago but I probably just dont understand how the database is written is all. Such is life! I Do appreciate, as I always do the responses from the group. On Friday, December 25, 2020 at 7:31:09 PM UTC-6 vince wrote: > You can get old versions of weewx .deb packages at > http://weewx.com/downloads/released_versions/ if you know what version > you used to use. Check your weewx.conf file for the version identifier > near the top.You could alternately use the 'setup.py' method to install > current weewx on your ancient os, likely using python2 that your old os > probably has as its default. > > But your preferred path is reflash to a current os and install current > weewx and then you're good for a long time. You're talking 15 minutes of > work to do that. > > I would suggest not bothering trying a dist-upgrade from debian-7 to > debian-10, as it's going to take forever and likely will not work anyway. > Just reimage clean to current RaspiOS which is based on current debian and > get caught up once and for all. > > On Friday, December 25, 2020 at 4:53:02 PM UTC-8 Joe wrote: > >> Really sucks I gotta completely re-image and re-set my whole PI board for >> this. I get used to set-forget . I downloaded the files it needs. >> Database. conf files etc as the online site says. >> >> I was hoping this program would be more backward compatible with the RPI >> OS. >> >> On Friday, December 25, 2020 at 1:06:21 PM UTC-6 vince wrote: >> >>> Yup - your os is far too ancient for the libraries the weewx dpkg is >>> built against. That version went end-of-life in May-2018. >>> >>> I'd suggest you reimage with the current RaspiOS from >>> https://www.raspberrypi.org/software/operating-systems and then you'll >>> be up to date and supportable. The weewx package works just fine in the >>> current os. >>> >>> On Friday, December 25, 2020 at 2:35:04 AM UTC-8 Joe wrote: >>> >>>> That worked. 7.8 >>>> >>>> >>>> PRETTY_NAME="Raspbian GNU/Linux 7 (wheezy)" >>>> NAME="Raspbian GNU/Linux" >>>> VERSION_ID="7" >>>> VERSION="7 (wheezy)" >>>> ID=raspbian >>>> ID_LIKE=debian >>>> ANSI_COLOR="1;31" >>>> HOME_URL="http://www.raspbian.org/"; >>>> SUPPORT_URL="http://www.raspbian.org/RaspbianForums"; >>>> BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"; >>>> root@raspberrypi:/etc# >>>> >>>> On Thursday, December 24, 2020 at 11:44:26 PM UTC-6 vince wrote: >>>> >>>>> The current kernel version is 5.4.79 according to the release notes at >>>>> https://www.raspberrypi.org/software/operating-systems >>>>> >>>>> My suspicion is that you are running an ancient os version that is too >>>>> old for the current packaged version of weewx. >>>>> >>>>> Again, please run the following commands and provide the results. >>>>> >>>>>- cat /etc/debian_version >>>>>- cat /etc/os-release >>>>> >>>>> >>>>> On Thursday, December 24, 2020 at 6:26:16 PM UTC-8 Joe wrote: >>>>> >>>>>> Neither of those directories exist. >>>>>> >>>>>> Its raspberrypi 3.18.7 >>>>>> >>>>>> On Thursday, December 24, 2020 at 9:53:49 AM UTC-6 vince wrote: >>>>>> >>>>>>> On Thursday, December 24, 2020 at 4:33:57 AM UTC-8 Joe wrote: >>>>>>> >>>>>>>> You mean to say running on the SD-CARD is bad idea? >>>>>>> >>>>>>> >>>>>>> Not bad, but not great if the card and power aren't quality. But >>>>>>> yes I misstyped my original reply. >>>>>>> >>>>>>> Re: your previous message containing " *d**pkg-deb: error: archive >>>>>>> '/var/cache/apt/archives/weewx_4.2.0-1_all.deb' contains not understood >>>>>>> data member control.tar.xz, giving up*", that's an unusual message. >>>>>>> >>>>>>> What version of raspi os are you running ? >>>>>>> Can we see the contents of /etc/os-release and /etc/debian_version >>>>>>> please ? >>>>>>> >>>>>>> >>>>>>> -- 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/d59e3a07-e710-4dcd-b1ee-fd9642b50ceen%40googlegroups.com.
[weewx-user] Vantage Console wakeup failing again....
So this has starting being a problem again. Its not really related to version 5. But it is still happening. This is a PI4 using the wifi option and a decent power connection and USB cord . It seems to be a USB detection / conversion problem. I've tried restarting the vantage a few times, and the PI computer pull the USB plug, and it restarts the USB device, attempts to begin pulling data and gets an error. Very frustrating after working for such a long time. Feb 2 19:30:56 raspberrypi weewxd[920]: INFO __main__: Starting up weewx version 5.0.0 Feb 2 19:30:57 raspberrypi weewxd[920]: INFO weewx.engine: Clock error is -197.26 seconds (positive is fast) Feb 2 19:30:57 raspberrypi weewxd[920]: INFO weewx.drivers.vantage: Clock set to 2024-02-02 19:30:58 CST (1706923858) Feb 2 19:30:57 raspberrypi weewxd[920]: INFO weewx.engine: Using binding 'wx_binding' to database 'weewx.sdb' Feb 2 19:30:57 raspberrypi weewxd[920]: INFO weewx.manager: Starting backfill of daily summaries Feb 2 19:30:57 raspberrypi weewxd[920]: INFO weewx.manager: Daily summaries up to date Feb 2 19:30:59 raspberrypi kernel: [ 1426.892512] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32 Feb 2 19:30:59 raspberrypi kernel: [ 1426.892962] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32 Feb 2 19:30:59 raspberrypi kernel: [ 1426.983918] usb 1-1.3: USB disconnect, device number 7 Feb 2 19:30:59 raspberrypi kernel: [ 1426.984264] cp210x ttyUSB0: failed set request 0x7 status: -19 Feb 2 19:30:59 raspberrypi kernel: [ 1426.984298] cp210x ttyUSB0: failed set request 0x12 status: -19 Feb 2 19:30:59 raspberrypi kernel: [ 1426.984316] cp210x ttyUSB0: failed set request 0x0 status: -19 Feb 2 19:30:59 raspberrypi kernel: [ 1426.985025] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 Feb 2 19:30:59 raspberrypi kernel: [ 1426.985139] cp210x 1-1.3:1.0: device disconnected Feb 2 19:30:59 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: SerialException on read. Feb 2 19:30:59 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: device reports readiness to read but returned no data (device disconnected or multiple access on port?) Feb 2 19:30:59 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: Is there a competing process running?? Feb 2 19:31:03 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: Unable to wake up Vantage console Feb 2 19:31:03 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: DMPAFT try #1; error: Unable to wake up Vantage console Feb 2 19:31:08 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: Unable to wake up Vantage console Feb 2 19:31:08 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: DMPAFT try #2; error: Unable to wake up Vantage console Feb 2 19:31:13 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: Unable to wake up Vantage console Feb 2 19:31:13 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: DMPAFT try #3; error: Unable to wake up Vantage console Feb 2 19:31:18 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: Unable to wake up Vantage console Feb 2 19:31:18 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: DMPAFT try #4; error: Unable to wake up Vantage console Feb 2 19:31:18 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: DMPAFT max tries (4) exceeded. Feb 2 19:31:18 raspberrypi weewxd[920]: INFO weewx.engine: Main loop exiting. Shutting engine down. Feb 2 19:31:18 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: SerialException on write. Feb 2 19:31:18 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: write failed: [Errno 5] Input/output error Feb 2 19:31:18 raspberrypi weewxd[920]: CRITICAL __main__: Caught WeeWxIOError: Max tries exceeded while getting archive data. Feb 2 19:31:18 raspberrypi weewxd[920]: CRITICAL __main__: Waiting 60.0 seconds then retrying... Feb 2 19:32:18 raspberrypi weewxd[920]: INFO __main__: retrying... Feb 2 19:32:18 raspberrypi weewxd[920]: INFO weewx.engine: Loading station type Vantage (weewx.drivers.vantage) Feb 2 19:32:18 raspberrypi weewxd[920]: ERROR weewx.engine: Import of driver failed: [Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0' () Feb 2 19:32:18 raspberrypi weewxd[920]: CRITICAL weewx.engine: Traceback (most recent call last): Feb 2 19:32:18 raspberrypi weewxd[920]: CRITICAL weewx.engine: File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 322, in open Feb 2 19:32:18 raspberrypi weewxd[920]: CRITICAL weewx.engine: self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK) Feb 2 19:32:18 raspberrypi weewxd[920]: CRITICAL weewx.engine: FileNotFoundError: [Errno 2] No such file or directory: '/dev/ttyUSB0' Feb 2 19:32:18 raspberrypi weewxd[920]: CRITICAL weewx.engine: Feb 2 19:32:18 raspberrypi weewxd[920]
Re: [weewx-user] Vantage Console wakeup failing again....
Its a standard PI4. No external USB devices are connected except for the Vantage data logger. There are coils on both ends of the cable, too. I'm going to try to find another power supply though. On Friday, February 2, 2024 at 7:53:40 PM UTC-6 Tom Keffer wrote: > Is this a serial logger with a serial-to-USB converter? Or, a USB logger? > If the former, try another converter. > > A couple of ferrite coils might help. See the wiki article on troubleshooting > Davis stations > <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station> > . > > It's also possible that the power supply of the RPi is failing and can't > deliver enough power. Try another power supply, or a powered USB hub. > > > > On Fri, Feb 2, 2024 at 5:36 PM Joe wrote: > >> So this has starting being a problem again. Its not really related to >> version 5. But it is still happening. >> >> This is a PI4 using the wifi option and a decent power connection and USB >> cord . >> >> It seems to be a USB detection / conversion problem. >> >> I've tried restarting the vantage a few times, and the PI computer pull >> the USB plug, and it restarts the USB device, attempts to begin pulling >> data and gets an error. >> >> Very frustrating after working for such a long time. >> >> >> >> >> >> >> Feb 2 19:30:56 raspberrypi weewxd[920]: INFO __main__: Starting up weewx >> version 5.0.0 >> Feb 2 19:30:57 raspberrypi weewxd[920]: INFO weewx.engine: Clock error >> is -197.26 seconds (positive is fast) >> Feb 2 19:30:57 raspberrypi weewxd[920]: INFO weewx.drivers.vantage: >> Clock set to 2024-02-02 19:30:58 CST (1706923858) >> Feb 2 19:30:57 raspberrypi weewxd[920]: INFO weewx.engine: Using binding >> 'wx_binding' to database 'weewx.sdb' >> Feb 2 19:30:57 raspberrypi weewxd[920]: INFO weewx.manager: Starting >> backfill of daily summaries >> Feb 2 19:30:57 raspberrypi weewxd[920]: INFO weewx.manager: Daily >> summaries up to date >> Feb 2 19:30:59 raspberrypi kernel: [ 1426.892512] cp210x ttyUSB0: >> usb_serial_generic_read_bulk_callback - urb stopped: -32 >> Feb 2 19:30:59 raspberrypi kernel: [ 1426.892962] cp210x ttyUSB0: >> usb_serial_generic_read_bulk_callback - urb stopped: -32 >> Feb 2 19:30:59 raspberrypi kernel: [ 1426.983918] usb 1-1.3: USB >> disconnect, device number 7 >> Feb 2 19:30:59 raspberrypi kernel: [ 1426.984264] cp210x ttyUSB0: failed >> set request 0x7 status: -19 >> Feb 2 19:30:59 raspberrypi kernel: [ 1426.984298] cp210x ttyUSB0: failed >> set request 0x12 status: -19 >> Feb 2 19:30:59 raspberrypi kernel: [ 1426.984316] cp210x ttyUSB0: failed >> set request 0x0 status: -19 >> Feb 2 19:30:59 raspberrypi kernel: [ 1426.985025] cp210x ttyUSB0: cp210x >> converter now disconnected from ttyUSB0 >> Feb 2 19:30:59 raspberrypi kernel: [ 1426.985139] cp210x 1-1.3:1.0: >> device disconnected >> Feb 2 19:30:59 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: >> SerialException on read. >> Feb 2 19:30:59 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: >> device reports readiness to read but returned no data (device >> disconnected or multiple access on port?) >> Feb 2 19:30:59 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: >> Is there a competing process running?? >> Feb 2 19:31:03 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: >> Unable to wake up Vantage console >> Feb 2 19:31:03 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: >> DMPAFT try #1; error: Unable to wake up Vantage console >> Feb 2 19:31:08 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: >> Unable to wake up Vantage console >> Feb 2 19:31:08 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: >> DMPAFT try #2; error: Unable to wake up Vantage console >> Feb 2 19:31:13 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: >> Unable to wake up Vantage console >> Feb 2 19:31:13 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: >> DMPAFT try #3; error: Unable to wake up Vantage console >> Feb 2 19:31:18 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: >> Unable to wake up Vantage console >> Feb 2 19:31:18 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: >> DMPAFT try #4; error: Unable to wake up Vantage console >> Feb 2 19:31:18 raspberrypi weewxd[920]: ERROR weewx.drivers.vantage: >> DMPAFT max tries (4) exceeded. >> Feb 2 19:31:18 raspberrypi weewxd[920]: INFO weewx.engine: Main loop >> exiting. Shutti
Re: [weewx-user] Vantage Console wakeup failing again....
r 37
Feb 5 05:50:34 raspberrypi kernel: [206471.268765] cp210x ttyUSB0: failed
set request 0x7 status: -19
Feb 5 05:50:34 raspberrypi kernel: [206471.268797] cp210x ttyUSB0: failed
set request 0x12 status: -19
Feb 5 05:50:34 raspberrypi kernel: [206471.268814] cp210x ttyUSB0: failed
set request 0x0 status: -19
Feb 5 05:50:34 raspberrypi kernel: [206471.269465] cp210x ttyUSB0: cp210x
converter now disconnected from ttyUSB0
Feb 5 05:50:34 raspberrypi kernel: [206471.269578] cp210x 1-1.2:1.0:
device disconnected
Feb 5 05:50:39 raspberrypi weewxd[4471]: ERROR weewx.drivers.vantage:
Unable to wake up Vantage console
Feb 5 05:50:39 raspberrypi weewxd[4471]: ERROR weewx.engine: Import of
driver failed: Unable to wake up Vantage console ()
Feb 5 05:50:39 raspberrypi weewxd[4471]: CRITICAL weewx.engine:
Traceback (most recent call last):
Feb 5 05:50:39 raspberrypi weewxd[4471]: CRITICAL weewx.engine:
File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
Feb 5 05:50:39 raspberrypi weewxd[4471]: CRITICAL weewx.engine:
self.console = loader_function(config_dict, self)
Feb 5 05:50:39 raspberrypi weewxd[4471]: CRITICAL weewx.engine:
File "/usr/share/weewx/weewx/drivers/vantage.py", line 32, in loader
Feb 5 05:50:39 raspberrypi weewxd[4471]: CRITICAL weewx.engine:
return VantageService(engine, config_dict)
Feb 5 05:50:39 raspberrypi weewxd[4471]: CRITICAL weewx.engine:
File "/usr/share/weewx/weewx/drivers/vantage.py", line 2046, in __init__
Feb 5 05:50:39 raspberrypi weewxd[4471]: CRITICAL weewx.engine:
Vantage.__init__(self, **config_dict[DRIVER_NAME])
Feb 5 05:50:39 raspberrypi weewxd[4471]: CRITICAL weewx.engine:
File "/usr/share/weewx/weewx/drivers/vantage.py", line 539, in __init__
Feb 5 05:50:39 raspberrypi weewxd[4471]: CRITICAL weewx.engine:
self._setup()
Feb 5 05:50:39 raspberrypi weewxd[4471]: CRITICAL weewx.engine:
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1440, in _setup
Feb 5 05:50:39 raspberrypi weewxd[4471]: CRITICAL weewx.engine:
self.port.wakeup_console(max_tries=self.max_tries)
Feb 5 05:50:39 raspberrypi weewxd[4471]: CRITICAL weewx.engine:
File "/usr/share/weewx/weewx/drivers/vantage.py", line 113, in
wakeup_console
Feb 5 05:50:39 raspberrypi weewxd[4471]: CRITICAL weewx.engine:
raise weewx.WakeupError("Unable to wake up Vantage console")
Feb 5 05:50:39 raspberrypi weewxd[4471]: CRITICAL weewx.engine:
weewx.WakeupError: Unable to wake up Vantage console
Feb 5 05:50:39 raspberrypi weewxd[4471]: CRITICAL __main__: Unable to load
driver: Unable to wake up Vantage console
Feb 5 05:50:39 raspberrypi weewxd[4471]: CRITICAL __main__:
Exiting...
Feb 5 05:50:39 raspberrypi systemd[1]: weewx.service: Main process exited,
code=exited, status=4/NOPERMISSION
Feb 5 05:50:39 raspberrypi systemd[1]: weewx.service: Failed with result
'exit-code'.
Feb 5 05:51:15 raspberrypi kernel: [206512.559257] usb 1-1.2: new
full-speed USB device number 38 using xhci_hcd
Feb 5 05:51:15 raspberrypi kernel: [206512.664702] usb 1-1.2: New USB
device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
Feb 5 05:51:15 raspberrypi kernel: [206512.664736] usb 1-1.2: New USB
device strings: Mfr=1, Product=2, SerialNumber=3
Feb 5 05:51:15 raspberrypi kernel: [206512.664754] usb 1-1.2: Product:
CP2102 USB to UART Bridge Controller
Feb 5 05:51:15 raspberrypi kernel: [206512.664769] usb 1-1.2:
Manufacturer: Silicon Labs
Feb 5 05:51:15 raspberrypi kernel: [206512.664782] usb 1-1.2:
SerialNumber: 0001
Feb 5 05:51:15 raspberrypi kernel: [206512.670692] cp210x 1-1.2:1.0:
cp210x converter detected
Feb 5 05:51:15 raspberrypi kernel: [206512.676544] usb 1-1.2: cp210x
converter now attached to ttyUSB0
Feb 5 05:51:15 raspberrypi mtp-probe: checking bus 1, device 38:
"/sys/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb1/1-1/1-1.2"
Feb 5 05:51:15 raspberrypi mtp-probe: bus: 1, device: 38 was not an MTP
device
Feb 5 05:51:16 raspberrypi mtp-probe: checking bus 1, device 38:
"/sys/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb1/1-1/1-1.2"
Feb 5 05:51:16 raspberrypi mtp-probe: bus: 1, device: 38 was not an MTP
device
Feb 5 05:51:18 raspberrypi ModemManager[453]: [base-manager]
couldn't check support for device
'/sys/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb1/1-1/1-1.2':
not supported by any plugin
On Saturday, February 3, 2024 at 2:37:15 PM UTC-6 Peter Fletcher wrote:
> It is very unlikely to be the Pi power supply if the Pi itself is not
> flagging up power problems.
>
> On Friday, February 2, 2024 at 9:23:04 PM UTC-5 Joe wrote:
>
>> Its a st
Re: [weewx-user] Vantage Console wakeup failing again....
I replaced the USB cable, and it works now. I dont have the ferrite cores on it yet though. Trying it without them. On Monday, February 5, 2024 at 7:04:52 AM UTC-6 Tom Keffer wrote: > Try removing modemmanager: > > *sudo apt purge modemmanager* > > > > On Mon, Feb 5, 2024 at 3:53 AM Joe wrote: > >> >> Even tried a new port # on the PI computer. It sees the davis but hates >> it >> >> >> Feb 5 05:48:15 raspberrypi weewxd[4416]: CRITICAL __main__: >> Exiting... >> Feb 5 05:48:15 raspberrypi systemd[1]: weewx.service: Main process >> exited, code=exited, status=4/NOPERMISSION >> Feb 5 05:48:15 raspberrypi systemd[1]: weewx.service: Failed with result >> 'exit-code'. >> Feb 5 05:48:47 raspberrypi kernel: [206364.060056] usb 1-1.3: USB >> disconnect, device number 32 >> Feb 5 05:48:47 raspberrypi kernel: [206364.060992] cp210x ttyUSB0: >> cp210x converter now disconnected from ttyUSB0 >> Feb 5 05:48:47 raspberrypi kernel: [206364.061124] cp210x 1-1.3:1.0: >> device disconnected >> Feb 5 05:48:51 raspberrypi kernel: [206368.742960] usb 1-1.2: new >> full-speed USB device number 33 using xhci_hcd >> Feb 5 05:48:52 raspberrypi kernel: [206368.823208] usb 1-1.2: device >> descriptor read/64, error -32 >> Feb 5 05:48:52 raspberrypi kernel: [206369.011191] usb 1-1.2: device >> descriptor read/64, error -32 >> Feb 5 05:48:52 raspberrypi kernel: [206369.198959] usb 1-1.2: new >> full-speed USB device number 34 using xhci_hcd >> Feb 5 05:48:52 raspberrypi kernel: [206369.279207] usb 1-1.2: device >> descriptor read/64, error -32 >> Feb 5 05:48:52 raspberrypi kernel: [206369.467193] usb 1-1.2: device >> descriptor read/64, error -32 >> Feb 5 05:48:52 raspberrypi kernel: [206369.575606] usb 1-1-port2: >> attempt power cycle >> Feb 5 05:48:53 raspberrypi kernel: [206370.178963] usb 1-1.2: new >> full-speed USB device number 35 using xhci_hcd >> Feb 5 05:48:53 raspberrypi kernel: [206370.179245] usb 1-1.2: Device not >> responding to setup address. >> Feb 5 05:48:53 raspberrypi kernel: [206370.387214] usb 1-1.2: Device not >> responding to setup address. >> Feb 5 05:48:53 raspberrypi kernel: [206370.594992] usb 1-1.2: device not >> accepting address 35, error -71 >> Feb 5 05:49:14 raspberrypi kernel: [206391.719029] usb 1-1.2: new >> full-speed USB device number 37 using xhci_hcd >> Feb 5 05:49:15 raspberrypi kernel: [206391.824466] usb 1-1.2: New USB >> device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 >> Feb 5 05:49:15 raspberrypi kernel: [206391.824500] usb 1-1.2: New USB >> device strings: Mfr=1, Product=2, SerialNumber=3 >> Feb 5 05:49:15 raspberrypi kernel: [206391.824518] usb 1-1.2: Product: >> CP2102 USB to UART Bridge Controller >> Feb 5 05:49:15 raspberrypi kernel: [206391.824532] usb 1-1.2: >> Manufacturer: Silicon Labs >> Feb 5 05:49:15 raspberrypi kernel: [206391.824545] usb 1-1.2: >> SerialNumber: 0001 >> Feb 5 05:49:15 raspberrypi kernel: [206391.830290] cp210x 1-1.2:1.0: >> cp210x converter detected >> Feb 5 05:49:15 raspberrypi kernel: [206391.836351] usb 1-1.2: cp210x >> converter now attached to ttyUSB0 >> Feb 5 05:49:15 raspberrypi mtp-probe: checking bus 1, device 37: >> "/sys/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb1/1-1/1-1.2" >> Feb 5 05:49:15 raspberrypi mtp-probe: bus: 1, device: 37 was not an MTP >> device >> Feb 5 05:49:15 raspberrypi mtp-probe: checking bus 1, device 37: >> "/sys/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb1/1-1/1-1.2" >> Feb 5 05:49:15 raspberrypi mtp-probe: bus: 1, device: 37 was not an MTP >> device >> Feb 5 05:49:17 raspberrypi ModemManager[453]: [base-manager] >> couldn't check support for device >> '/sys/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb1/1-1/1-1.2': >> >> not supported by any plugin >> Feb 5 05:50:33 raspberrypi systemd[1]: Started WeeWX. >> Feb 5 05:50:34 raspberrypi weewxd[4471]: INFO __main__: Initializing >> weewxd version 5.0.0 >> Feb 5 05:50:34 raspberrypi weewxd[4471]: INFO __main__: Command line: >> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf >> Feb 5 05:50:34 raspberrypi weewxd[4471]: INFO __main__: Using Python >> 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110] >> Feb 5 05:50:34 raspberrypi weewxd[4471]: INFO __main__: Located at >> /usr/bin/python3 >> Feb 5 05:50:34 raspberrypi weewxd[4471]: INFO __ma
Re: [weewx-user] Vantage Console wakeup failing again....
CRITICAL __main__: Exiting... Feb 9 12:57:02 raspberrypi systemd[1]: weewx.service: Main process exited, code=exited, status=4/NOPERMISSION Feb 9 12:57:02 raspberrypi systemd[1]: weewx.service: Failed with result 'exit-code'. However prior to that, this error was seen Feb 8 14:45:56 raspberrypi kernel: [497794.276168] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32 Feb 8 14:46:02 raspberrypi kernel: [497800.099892] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32 Feb 8 14:46:06 raspberrypi weewxd[5015]: ERROR weewx.drivers.vantage: LOOP batch try #1; error: Expected to read 99 chars; got 0 instead Feb 8 14:46:33 raspberrypi weewxd[5015]: ERROR weewx.drivers.vantage: Unable to wake up Vantage console Feb 8 14:46:33 raspberrypi weewxd[5015]: ERROR weewx.drivers.vantage: LOOP batch try #2; error: Unable to wake up Vantage console Feb 8 14:46:59 raspberrypi weewxd[5015]: ERROR weewx.drivers.vantage: Unable to wake up Vantage console Feb 8 14:46:59 raspberrypi weewxd[5015]: ERROR weewx.drivers.vantage: LOOP batch try #3; error: Unable to wake up Vantage console Feb 8 14:46:59 raspberrypi weewxd[5015]: ERROR weewx.drivers.vantage: LOOP max batch errors (3) exceeded. Feb 8 14:46:59 raspberrypi weewxd[5015]: INFO weewx.engine: Main loop exiting. Shutting engine down. Feb 8 14:46:59 raspberrypi weewxd[5015]: INFO weewx.engine: Shutting down StdReport thread Feb 8 14:46:59 raspberrypi weewxd[5015]: CRITICAL __main__: Caught WeeWxIOError: LOOP max batch errors (3) exceeded. Feb 8 14:46:59 raspberrypi weewxd[5015]: CRITICAL __main__: Waiting 60.0 seconds then retrying... On Monday, February 5, 2024 at 5:37:30 PM UTC-6 Joe wrote: > I replaced the USB cable, and it works now. > > I dont have the ferrite cores on it yet though. Trying it without them. > > > > > On Monday, February 5, 2024 at 7:04:52 AM UTC-6 Tom Keffer wrote: > >> Try removing modemmanager: >> >> *sudo apt purge modemmanager* >> >> >> >> On Mon, Feb 5, 2024 at 3:53 AM Joe wrote: >> >>> >>> Even tried a new port # on the PI computer. It sees the davis but hates >>> it >>> >>> >>> Feb 5 05:48:15 raspberrypi weewxd[4416]: CRITICAL __main__: >>> Exiting... >>> Feb 5 05:48:15 raspberrypi systemd[1]: weewx.service: Main process >>> exited, code=exited, status=4/NOPERMISSION >>> Feb 5 05:48:15 raspberrypi systemd[1]: weewx.service: Failed with >>> result 'exit-code'. >>> Feb 5 05:48:47 raspberrypi kernel: [206364.060056] usb 1-1.3: USB >>> disconnect, device number 32 >>> Feb 5 05:48:47 raspberrypi kernel: [206364.060992] cp210x ttyUSB0: >>> cp210x converter now disconnected from ttyUSB0 >>> Feb 5 05:48:47 raspberrypi kernel: [206364.061124] cp210x 1-1.3:1.0: >>> device disconnected >>> Feb 5 05:48:51 raspberrypi kernel: [206368.742960] usb 1-1.2: new >>> full-speed USB device number 33 using xhci_hcd >>> Feb 5 05:48:52 raspberrypi kernel: [206368.823208] usb 1-1.2: device >>> descriptor read/64, error -32 >>> Feb 5 05:48:52 raspberrypi kernel: [206369.011191] usb 1-1.2: device >>> descriptor read/64, error -32 >>> Feb 5 05:48:52 raspberrypi kernel: [206369.198959] usb 1-1.2: new >>> full-speed USB device number 34 using xhci_hcd >>> Feb 5 05:48:52 raspberrypi kernel: [206369.279207] usb 1-1.2: device >>> descriptor read/64, error -32 >>> Feb 5 05:48:52 raspberrypi kernel: [206369.467193] usb 1-1.2: device >>> descriptor read/64, error -32 >>> Feb 5 05:48:52 raspberrypi kernel: [206369.575606] usb 1-1-port2: >>> attempt power cycle >>> Feb 5 05:48:53 raspberrypi kernel: [206370.178963] usb 1-1.2: new >>> full-speed USB device number 35 using xhci_hcd >>> Feb 5 05:48:53 raspberrypi kernel: [206370.179245] usb 1-1.2: Device >>> not responding to setup address. >>> Feb 5 05:48:53 raspberrypi kernel: [206370.387214] usb 1-1.2: Device >>> not responding to setup address. >>> Feb 5 05:48:53 raspberrypi kernel: [206370.594992] usb 1-1.2: device >>> not accepting address 35, error -71 >>> Feb 5 05:49:14 raspberrypi kernel: [206391.719029] usb 1-1.2: new >>> full-speed USB device number 37 using xhci_hcd >>> Feb 5 05:49:15 raspberrypi kernel: [206391.824466] usb 1-1.2: New USB >>> device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 >>> Feb 5 05:49:15 raspberrypi kernel: [206391.824500] usb 1-1.2: New USB >>> device strings: Mfr=1, Product=2, SerialNumber=3 >>> Feb 5 05:49:15 raspberrypi kernel: [206391.82451
Re: [weewx-user] Vantage Console wakeup failing again....
Plug in the replacement cable with ferrite cores, and I get this error eb 9 13:03:58 raspberrypi kernel: [578076.357712] usb 1-1.4: USB disconnect, device number 42 Feb 9 13:03:58 raspberrypi kernel: [578076.358554] cp210x ttyUSB1: cp210x converter now disconnected from ttyUSB1 Feb 9 13:03:58 raspberrypi kernel: [578076.358689] cp210x 1-1.4:1.0: device disconnected Feb 9 13:06:10 raspberrypi kernel: [578208.959876] usb 1-1.4: new full-speed USB device number 43 using xhci_hcd Feb 9 13:06:11 raspberrypi kernel: [578209.065310] usb 1-1.4: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 Feb 9 13:06:11 raspberrypi kernel: [578209.065345] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Feb 9 13:06:11 raspberrypi kernel: [578209.065362] usb 1-1.4: Product: CP2102 USB to UART Bridge Controller Feb 9 13:06:11 raspberrypi kernel: [578209.065377] usb 1-1.4: Manufacturer: Silicon Labs Feb 9 13:06:11 raspberrypi kernel: [578209.065390] usb 1-1.4: SerialNumber: 0001 Feb 9 13:06:11 raspberrypi kernel: [578209.071129] cp210x 1-1.4:1.0: cp210x converter detected Feb 9 13:06:11 raspberrypi kernel: [578209.077119] usb 1-1.4: cp210x converter now attached to ttyUSB0 Feb 9 13:06:11 raspberrypi mtp-probe: checking bus 1, device 43: "/sys/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb1/1-1/1-1.4" Feb 9 13:06:11 raspberrypi mtp-probe: bus: 1, device: 43 was not an MTP device Feb 9 13:06:11 raspberrypi mtp-probe: checking bus 1, device 43: "/sys/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb1/1-1/1-1.4" Feb 9 13:06:11 raspberrypi mtp-probe: bus: 1, device: 43 was not an MTP device Feb 9 13:06:13 raspberrypi ModemManager[453]: [base-manager] couldn't check support for device '/sys/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb1/1-1/1-1.4': not supported by any plugin On Friday, February 9, 2024 at 1:00:36 PM UTC-6 Joe wrote: > > Weewx failed to start or run again. > > Feb 9 12:57:01 raspberrypi systemd[1]: Started WeeWX. > Feb 9 12:57:02 raspberrypi weewxd[12139]: INFO __main__: Initializing > weewxd version 5.0.0 > Feb 9 12:57:02 raspberrypi weewxd[12139]: INFO __main__: Command line: > /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf > Feb 9 12:57:02 raspberrypi weewxd[12139]: INFO __main__: Using Python > 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110] > Feb 9 12:57:02 raspberrypi weewxd[12139]: INFO __main__: Located at > /usr/bin/python3 > Feb 9 12:57:02 raspberrypi weewxd[12139]: INFO __main__: Platform > Linux-6.1.21-v8+-aarch64-with-glibc2.31 > Feb 9 12:57:02 raspberrypi weewxd[12139]: INFO __main__: Locale: > 'en_US.UTF-8' > Feb 9 12:57:02 raspberrypi weewxd[12139]: INFO __main__: Entry path: > /usr/share/weewx/weewxd.py > Feb 9 12:57:02 raspberrypi weewxd[12139]: INFO __main__: WEEWX_ROOT: / > Feb 9 12:57:02 raspberrypi weewxd[12139]: INFO __main__: Configuration > file: /etc/weewx/weewx.conf > Feb 9 12:57:02 raspberrypi weewxd[12139]: INFO __main__: User module: > /etc/weewx/bin/user > Feb 9 12:57:02 raspberrypi weewxd[12139]: INFO __main__: Debug: 0 > Feb 9 12:57:02 raspberrypi weewxd[12139]: INFO weewx.engine: Loading > station type Vantage (weewx.drivers.vantage) > Feb 9 12:57:02 raspberrypi weewxd[12139]: ERROR weewx.engine: Import of > driver failed: [Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No > such file or directory: '/dev/ttyUSB0' ( 'serial.serialutil.SerialException'>) > Feb 9 12:57:02 raspberrypi weewxd[12139]: CRITICAL weewx.engine: > Traceback (most recent call last): > Feb 9 12:57:02 raspberrypi weewxd[12139]: CRITICAL weewx.engine: >File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 322, > in open > Feb 9 12:57:02 raspberrypi weewxd[12139]: CRITICAL weewx.engine: > self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | > os.O_NONBLOCK) > Feb 9 12:57:02 raspberrypi weewxd[12139]: CRITICAL weewx.engine: > FileNotFoundError: [Errno 2] No such file or directory: '/dev/ttyUSB0' > Feb 9 12:57:02 raspberrypi weewxd[12139]: CRITICAL weewx.engine: > > Feb 9 12:57:02 raspberrypi weewxd[12139]: CRITICAL weewx.engine: > During handling of the above exception, another exception occurred: > Feb 9 12:57:02 raspberrypi weewxd[12139]: CRITICAL weewx.engine: > > Feb 9 12:57:02 raspberrypi weewxd[12139]: CRITICAL weewx.engine: > Traceback (most recent call last): > Feb 9 12:57:02 raspberrypi weewxd[12139]: CRITICAL weewx.engine: >File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation > Feb 9 12:57:02 raspberry
Re: [weewx-user] Vantage Console wakeup failing again....
START weewx, and it begins publishing records again from the console. -- 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/38055abe-fc46-421c-a1f9-1aa9dce59e56n%40googlegroups.com.
Re: [weewx-user] Vantage Console wakeup failing again....
Feb 9 13:07:55 raspberrypi systemd[1]: Started WeeWX. Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Initializing weewxd version 5.0.0 Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Command line: /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Using Python 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110] Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Located at /usr/bin/python3 Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Platform Linux-6.1.21-v8+-aarch64-with-glibc2.31 Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Locale: 'en_US.UTF-8' Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Entry path: /usr/share/weewx/weewxd.py Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: WEEWX_ROOT: / Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Configuration file: /etc/weewx/weewx.conf Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: User module: /etc/weewx/bin/user Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Debug: 0 Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO weewx.engine: Loading station type Vantage (weewx.drivers.vantage) Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: StdConvert target unit is 0x1 Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.wxservices: StdWXCalculate will use data binding wx_binding Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: Archive will use data binding wx_binding Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: Record generation will be attempted in 'hardware' Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: Using archive interval of 300 seconds (specified by hardware) Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.restx: StationRegistry: Station will not be registered: no station_url specified. Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.restx: Wunderground: Posting not enabled. Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.restx: PWSWeather: Data for station JTX99 will be posted Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.restx: CWOP: Posting not enabled. Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.restx: WOW: Posting not enabled. Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.restx: AWEKAS: Posting not enabled. Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: 'pyephem' detected, extended almanac data is available Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO __main__: Starting up weewx version 5.0.0 Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: Clock error is 4.14 seconds (positive is fast) Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: Using binding 'wx_binding' to database 'weewx.sdb' Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.manager: Starting backfill of daily summaries Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.manager: Daily summaries up to date On Friday, February 9, 2024 at 1:08:35 PM UTC-6 Joe wrote: > > START weewx, and it begins publishing records again from the > console. -- 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/d79d92ab-01cd-41b6-bd88-f2b540f6724fn%40googlegroups.com.
Re: [weewx-user] Vantage Console wakeup failing again....
Well, it failed with a USB error is the problem. I put the ferrite core on the cable and plugged it back in and it started normally. Didnt see there was an update, I will do that, and remove the modemmanger On Friday, February 9, 2024 at 3:58:05 PM UTC-6 Tom Keffer wrote: > The log in that last email looked pretty normal. Is there a problem? > > You should upgrade to v5.0.1. > > Be sure to get rid of ModemManager. It competes with weewxd for the port. > > *sudo apt purge modemmanager* > > > -tk > > > On Fri, Feb 9, 2024 at 11:12 AM Joe wrote: > >> Feb 9 13:07:55 raspberrypi systemd[1]: Started WeeWX. >> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Initializing >> weewxd version 5.0.0 >> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Command line: >> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf >> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Using Python >> 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110] >> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Located at >> /usr/bin/python3 >> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Platform >> Linux-6.1.21-v8+-aarch64-with-glibc2.31 >> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Locale: >> 'en_US.UTF-8' >> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Entry path: >> /usr/share/weewx/weewxd.py >> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: WEEWX_ROOT: / >> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Configuration >> file: /etc/weewx/weewx.conf >> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: User module: >> /etc/weewx/bin/user >> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Debug: 0 >> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO weewx.engine: Loading >> station type Vantage (weewx.drivers.vantage) >> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: StdConvert >> target unit is 0x1 >> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.wxservices: >> StdWXCalculate will use data binding wx_binding >> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: Archive >> will use data binding wx_binding >> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: Record >> generation will be attempted in 'hardware' >> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: Using >> archive interval of 300 seconds (specified by hardware) >> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.restx: >> StationRegistry: Station will not be registered: no station_url specified. >> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.restx: >> Wunderground: Posting not enabled. >> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.restx: PWSWeather: >> Data for station JTX99 will be posted >> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.restx: CWOP: >> Posting not enabled. >> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.restx: WOW: Posting >> not enabled. >> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.restx: AWEKAS: >> Posting not enabled. >> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: 'pyephem' >> detected, extended almanac data is available >> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO __main__: Starting up >> weewx version 5.0.0 >> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: Clock error >> is 4.14 seconds (positive is fast) >> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: Using >> binding 'wx_binding' to database 'weewx.sdb' >> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.manager: Starting >> backfill of daily summaries >> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.manager: Daily >> summaries up to date >> >> On Friday, February 9, 2024 at 1:08:35 PM UTC-6 Joe wrote: >> >>> >>> START weewx, and it begins publishing records again from the >>> console. >> >> -- >> > 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/d79d92ab-01cd-41b6-bd88-f2b540f6724fn%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/d79d92ab-01cd-41b6-bd88-f2b540f6724fn%40googlegroups.com?utm_medium=email&utm_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/f09eacb1-84c4-4688-8689-1df3df836686n%40googlegroups.com.
Re: [weewx-user] Vantage Console wakeup failing again....
md[1]: weewx.service: Main process exited, code=exited, status=4/NOPERMISSION Feb 10 07:45:52 raspberrypi systemd[1]: weewx.service: Failed with result 'exit-code'. On Friday, February 9, 2024 at 4:29:22 PM UTC-6 Joe wrote: > Well, it failed with a USB error is the problem. I put the ferrite core on > the cable and plugged it back in and it started normally. > Didnt see there was an update, I will do that, and remove the modemmanger > > > On Friday, February 9, 2024 at 3:58:05 PM UTC-6 Tom Keffer wrote: > >> The log in that last email looked pretty normal. Is there a problem? >> >> You should upgrade to v5.0.1. >> >> Be sure to get rid of ModemManager. It competes with weewxd for the port. >> >> *sudo apt purge modemmanager* >> >> >> -tk >> >> >> On Fri, Feb 9, 2024 at 11:12 AM Joe wrote: >> >>> Feb 9 13:07:55 raspberrypi systemd[1]: Started WeeWX. >>> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Initializing >>> weewxd version 5.0.0 >>> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Command line: >>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf >>> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Using Python >>> 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110] >>> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Located at >>> /usr/bin/python3 >>> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Platform >>> Linux-6.1.21-v8+-aarch64-with-glibc2.31 >>> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Locale: >>> 'en_US.UTF-8' >>> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Entry path: >>> /usr/share/weewx/weewxd.py >>> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: WEEWX_ROOT: / >>> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Configuration >>> file: /etc/weewx/weewx.conf >>> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: User module: >>> /etc/weewx/bin/user >>> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO __main__: Debug: 0 >>> Feb 9 13:07:56 raspberrypi weewxd[12185]: INFO weewx.engine: Loading >>> station type Vantage (weewx.drivers.vantage) >>> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: StdConvert >>> target unit is 0x1 >>> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.wxservices: >>> StdWXCalculate will use data binding wx_binding >>> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: Archive >>> will use data binding wx_binding >>> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: Record >>> generation will be attempted in 'hardware' >>> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: Using >>> archive interval of 300 seconds (specified by hardware) >>> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.restx: >>> StationRegistry: Station will not be registered: no station_url specified. >>> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.restx: >>> Wunderground: Posting not enabled. >>> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.restx: PWSWeather: >>> Data for station JTX99 will be posted >>> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.restx: CWOP: >>> Posting not enabled. >>> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.restx: WOW: >>> Posting not enabled. >>> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.restx: AWEKAS: >>> Posting not enabled. >>> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: 'pyephem' >>> detected, extended almanac data is available >>> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO __main__: Starting up >>> weewx version 5.0.0 >>> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: Clock >>> error is 4.14 seconds (positive is fast) >>> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.engine: Using >>> binding 'wx_binding' to database 'weewx.sdb' >>> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.manager: Starting >>> backfill of daily summaries >>> Feb 9 13:07:57 raspberrypi weewxd[12185]: INFO weewx.manager: Daily >>> summaries up to date >>> >>> On Friday, February 9, 2024 at 1:08:35 PM UTC-6 Joe wrote: >>> >>>> >>>> START weewx, and it begins publishing records again from the >>>> console. >>> &
Re: [weewx-user] Vantage Console wakeup failing again....
Not sure why its doing this. I will need to check my pi hole to make sure its not stoppiing the inquiry. Get:1 http://weewx.com/apt/python3 buster InRelease [4,252 B] Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease Err:1 http://weewx.com/apt/python3 buster InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E788768B9CB16E10 Fetched 4,252 B in 2s (2,129 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://weewx.com/apt/python3 buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E788768B9CB16E10 W: Failed to fetch http://weewx.com/apt/python3/dists/buster/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E788768B9CB16E10 W: Some index files failed to download. They have been ignored, or old ones used instead. On Saturday, February 10, 2024 at 7:52:03 AM UTC-6 Tom Keffer wrote: > Something is causing the usb adapter to release /dev/ttyUSB0. Try the > kernel message "dmesg". It may give you some information. > > Also you should update to v5.0.2 > > *sudo apt update* > *sudo apt upgrade* > > -tk > > On Sat, Feb 10, 2024 at 5:47 AM Joe wrote: > >> Back with the USB error again now.. >> >> Feb 10 07:45:51 raspberrypi systemd[1]: Started WeeWX. >> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Initializing >> weewxd version 5.0.0 >> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Command line: >> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf >> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Using Python >> 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110] >> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Located at >> /usr/bin/python3 >> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Platform >> Linux-6.1.21-v8+-aarch64-with-glibc2.31 >> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Locale: >> 'en_US.UTF-8' >> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Entry path: >> /usr/share/weewx/weewxd.py >> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: WEEWX_ROOT: / >> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Configuration >> file: /etc/weewx/weewx.conf >> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: User module: >> /etc/weewx/bin/user >> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Debug: 0 >> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO weewx.engine: Loading >> station type Vantage (weewx.drivers.vantage) >> Feb 10 07:45:51 raspberrypi weewxd[797]: ERROR weewx.engine: Import of >> driver failed: [Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No >> such file or directory: '/dev/ttyUSB0' (> 'serial.serialutil.SerialException'>) >> Feb 10 07:45:51 raspberrypi weewxd[797]: CRITICAL weewx.engine: >> Traceback (most recent call last): >> Feb 10 07:45:51 raspberrypi weewxd[797]: CRITICAL weewx.engine: >>File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 322, >> in open >> Feb 10 07:45:51 raspberrypi weewxd[797]: CRITICAL weewx.engine: >> self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | >> os.O_NONBLOCK) >> Feb 10 07:45:51 raspberrypi weewxd[797]: CRITICAL weewx.engine: >> FileNotFoundError: [Errno 2] No such file or directory: '/dev/ttyUSB0' >> Feb 10 07:45:51 raspberrypi weewxd[797]: CRITICAL weewx.engine: >> Feb 10 07:45:51 raspberrypi weewxd[797]: CRITICAL weewx.engine: >> During handling of the above exception, another exception occurred: >> Feb 10 07:45:51 raspberrypi weewxd[797]: CRITICAL weewx.engine: >> Feb 10 07:45:51 raspberrypi weewxd[797]: CRITICAL weewx.engine: >> Traceback (most recent call last): >> Feb 10 07:45:51 raspberrypi weewxd[797]: CRITICAL weewx.engine: >>File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation >> Feb 10 07:45:51 raspberrypi weewxd[797]: CRITICAL weewx.engine: >> self.console = loader_function(config_dict, self) >> Feb 10 07:45:51 raspberrypi weewxd[797]: CRITICAL weewx.engine: >>File "/usr/share/weewx/weewx/drivers/vantage.py",
Re: [weewx-user] Vantage Console wakeup failing again....
Thank you for the url about apt keys. Success. I'm running updates and its done, and i restarted weewx and it seems to be doing it however it is getting loop batch errors now I will see if it resolves... On Saturday, February 10, 2024 at 12:01:18 PM UTC-6 vince wrote: > Update your apt keys first per the configure apt section at the top of > https://weewx.com/docs/5.0/quickstarts/debian/ > > Then do Tom’s two commands. > > On Saturday, February 10, 2024 at 8:12:07 AM UTC-8 Joe wrote: > >> Not sure why its doing this. I will need to check my pi hole to make >> sure its not stoppiing the inquiry. >> >> >> >> Get:1 http://weewx.com/apt/python3 buster InRelease [4,252 B] >> Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease >> >> Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease >> Err:1 http://weewx.com/apt/python3 buster InRelease >> The following signatures couldn't be verified because the public key is >> not available: NO_PUBKEY E788768B9CB16E10 >> Fetched 4,252 B in 2s (2,129 B/s) >> Reading package lists... Done >> Building dependency tree... Done >> Reading state information... Done >> All packages are up to date. >> W: An error occurred during the signature verification. The repository is >> not updated and the previous index files will be used. GPG error: >> http://weewx.com/apt/python3 buster InRelease: The following signatures >> couldn't be verified because the public key is not available: NO_PUBKEY >> E788768B9CB16E10 >> W: Failed to fetch http://weewx.com/apt/python3/dists/buster/InRelease >> The following signatures couldn't be verified because the public key is >> not available: NO_PUBKEY E788768B9CB16E10 >> W: Some index files failed to download. They have been ignored, or old >> ones used instead. >> >> On Saturday, February 10, 2024 at 7:52:03 AM UTC-6 Tom Keffer wrote: >> >>> Something is causing the usb adapter to release /dev/ttyUSB0. Try the >>> kernel message "dmesg". It may give you some information. >>> >>> Also you should update to v5.0.2 >>> >>> *sudo apt update* >>> *sudo apt upgrade* >>> >>> -tk >>> >>> On Sat, Feb 10, 2024 at 5:47 AM Joe wrote: >>> >>>> Back with the USB error again now.. >>>> >>>> Feb 10 07:45:51 raspberrypi systemd[1]: Started WeeWX. >>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Initializing >>>> weewxd version 5.0.0 >>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Command line: >>>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf >>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Using Python >>>> 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110] >>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Located at >>>> /usr/bin/python3 >>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Platform >>>> Linux-6.1.21-v8+-aarch64-with-glibc2.31 >>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Locale: >>>> 'en_US.UTF-8' >>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Entry path: >>>> /usr/share/weewx/weewxd.py >>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: WEEWX_ROOT: / >>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Configuration >>>> file: /etc/weewx/weewx.conf >>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: User module: >>>> /etc/weewx/bin/user >>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Debug: 0 >>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO weewx.engine: Loading >>>> station type Vantage (weewx.drivers.vantage) >>>> Feb 10 07:45:51 raspberrypi weewxd[797]: ERROR weewx.engine: Import of >>>> driver failed: [Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No >>>> such file or directory: '/dev/ttyUSB0' (>>> 'serial.serialutil.SerialException'>) >>>> Feb 10 07:45:51 raspberrypi weewxd[797]: CRITICAL weewx.engine: >>>> Traceback (most recent call last): >>>> Feb 10 07:45:51 raspberrypi weewxd[797]: CRITICAL weewx.engine: >>>> File "/usr/lib/python3/dist-packages/serial/serialposix.py", line >>>> 322, in open >>>> Feb 10 07:45:51 raspberrypi weewxd[797]: CRITICAL weewx.engine: >>>> self.fd = os.op
Re: [weewx-user] Vantage Console wakeup failing again....
The loopback errors have stopped for now. Not sure why... Thanks for the suggestions I hope it helped! On Saturday, February 10, 2024 at 3:36:09 PM UTC-6 Joe wrote: > Thank you for the url about apt keys. Success. I'm running updates and its > done, and i restarted weewx and it seems to be doing it however it is > getting loop batch errors now I will see if it resolves... > > On Saturday, February 10, 2024 at 12:01:18 PM UTC-6 vince wrote: > >> Update your apt keys first per the configure apt section at the top of >> https://weewx.com/docs/5.0/quickstarts/debian/ >> >> Then do Tom’s two commands. >> >> On Saturday, February 10, 2024 at 8:12:07 AM UTC-8 Joe wrote: >> >>> Not sure why its doing this. I will need to check my pi hole to make >>> sure its not stoppiing the inquiry. >>> >>> >>> >>> Get:1 http://weewx.com/apt/python3 buster InRelease [4,252 B] >>> Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease >>> >>> Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease >>> Err:1 http://weewx.com/apt/python3 buster InRelease >>> The following signatures couldn't be verified because the public key >>> is not available: NO_PUBKEY E788768B9CB16E10 >>> Fetched 4,252 B in 2s (2,129 B/s) >>> Reading package lists... Done >>> Building dependency tree... Done >>> Reading state information... Done >>> All packages are up to date. >>> W: An error occurred during the signature verification. The repository >>> is not updated and the previous index files will be used. GPG error: >>> http://weewx.com/apt/python3 buster InRelease: The following signatures >>> couldn't be verified because the public key is not available: NO_PUBKEY >>> E788768B9CB16E10 >>> W: Failed to fetch http://weewx.com/apt/python3/dists/buster/InRelease >>> The following signatures couldn't be verified because the public key is >>> not available: NO_PUBKEY E788768B9CB16E10 >>> W: Some index files failed to download. They have been ignored, or old >>> ones used instead. >>> >>> On Saturday, February 10, 2024 at 7:52:03 AM UTC-6 Tom Keffer wrote: >>> >>>> Something is causing the usb adapter to release /dev/ttyUSB0. Try the >>>> kernel message "dmesg". It may give you some information. >>>> >>>> Also you should update to v5.0.2 >>>> >>>> *sudo apt update* >>>> *sudo apt upgrade* >>>> >>>> -tk >>>> >>>> On Sat, Feb 10, 2024 at 5:47 AM Joe wrote: >>>> >>>>> Back with the USB error again now.. >>>>> >>>>> Feb 10 07:45:51 raspberrypi systemd[1]: Started WeeWX. >>>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Initializing >>>>> weewxd version 5.0.0 >>>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Command line: >>>>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf >>>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Using Python >>>>> 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110] >>>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Located at >>>>> /usr/bin/python3 >>>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Platform >>>>> Linux-6.1.21-v8+-aarch64-with-glibc2.31 >>>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Locale: >>>>> 'en_US.UTF-8' >>>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Entry path: >>>>> /usr/share/weewx/weewxd.py >>>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: WEEWX_ROOT: / >>>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Configuration >>>>> file: /etc/weewx/weewx.conf >>>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: User module: >>>>> /etc/weewx/bin/user >>>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO __main__: Debug: 0 >>>>> Feb 10 07:45:51 raspberrypi weewxd[797]: INFO weewx.engine: Loading >>>>> station type Vantage (weewx.drivers.vantage) >>>>> Feb 10 07:45:51 raspberrypi weewxd[797]: ERROR weewx.engine: Import of >>>>> driver failed: [Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No >>>>> such file or directory: '/dev/ttyUSB0' (>>>> 'serial.serialutil.Se
[weewx-user] YEAR Tab shows graph with much lower actual temperatures than were recorded. Same with Heat Index.......
I'm having trouble with graphs I believe and I'm not sure why. Maybe it is my configuration. https://wx-data.site/satx/ If I click the YEAR tab, I'm seeing last June July August with much lower temps, under 90F than were actually recorded by the weather station. If you go to August 2019, it clearly shows 100+. Is there something I'm doing wrong in the configurations for the graphs on my setup? Also if you look at the heat-index, it shows much lower than were actually recorded. Heat Index here in Texas are 110F or higher in the summer. Not the mid 90s or upper 90s that is displayed. Thanks for looking! -- 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/ed0bb26c-0784-467c-8e84-3a901ee80716%40googlegroups.com.
Re: [weewx-user] YEAR Tab shows graph with much lower actual temperatures than were recorded. Same with Heat Index.......
I was not aware the graphs were averaging. I thought it showed actual temps in the graph. I noticed in my graph list that it does not show the HIGH and LOW temp graphs in the skin I am using. I need to figure out how to include that graph as well. I will check the customizing guide and see what it does for me. A moire accurate graph would be nice on outside temp in any case. On Tuesday, May 19, 2020 at 7:00:31 PM UTC-5, Tom Keffer wrote: > > Remember, for year plots, the plots are *aggregates.* The default is to > average over 24 hours, so it will smear out the highs and lows. If you want > to see the real highs and lows, take a look in the Customizing Guide, > section *Including a type more than once in a plot > <http://www.weewx.com/docs/customizing.htm#including_same_sql_type_2x>*. > > > > > On Tue, May 19, 2020 at 4:21 PM Joe > > wrote: > >> I'm having trouble with graphs I believe and I'm not sure why. Maybe it >> is my configuration. >> >> https://wx-data.site/satx/ >> >> If I click the YEAR tab, I'm seeing last June July August with much lower >> temps, under 90F than were actually recorded by the weather station. If you >> go to August 2019, it clearly shows 100+. >> >> Is there something I'm doing wrong in the configurations for the graphs >> on my setup? >> >> Also if you look at the heat-index, it shows much lower than were >> actually recorded. Heat Index here in Texas are 110F or higher in the >> summer. Not the mid 90s or upper 90s that is displayed. >> >> Thanks for looking! >> >> -- >> 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...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/ed0bb26c-0784-467c-8e84-3a901ee80716%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/ed0bb26c-0784-467c-8e84-3a901ee80716%40googlegroups.com?utm_medium=email&utm_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/4ff3dc2d-86ad-42b7-9bc2-29d396280d5d%40googlegroups.com.
[weewx-user] 3.9.1 reports
I am getting the following error when running reports. Any suggestions? pi@weewx:/etc/weewx $ wee_reports Using configuration file /etc/weewx/weewx.conf Generating for all time Traceback (most recent call last): File "/usr/share/weewx/weewx/reportengine.py", line 204, in run obj.start() File "/usr/share/weewx/weewx/reportengine.py", line 300, in start self.run() File "/usr/share/weewx/weewx/reportengine.py", line 460, in run shutil.copy(_file, dest_dir) File "/usr/lib/python2.7/shutil.py", line 120, in copy copymode(src, dst) File "/usr/lib/python2.7/shutil.py", line 91, in copymode os.chmod(dst, mode) OSError: [Errno 1] Operation not permitted: '/var/www/html/weewx/seasons.css' -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] 3.9.1 reports
Thanks. My bad for not catching that. On Tuesday, February 12, 2019 at 9:29:22 AM UTC-5, Thomas Keffer wrote: > > Hello, Joe > > The user does not have the necessary permissions to write into the > subdirectory /var/www/html/weewx. > > Either run as superuser, or change the permissions of the directory. For > example, > > *sudo wee_reports* > > -tk > > On Tue, Feb 12, 2019 at 5:29 AM Joe Spears > wrote: > >> I am getting the following error when running reports. Any suggestions? >> >> pi@weewx:/etc/weewx $ wee_reports >> Using configuration file /etc/weewx/weewx.conf >> Generating for all time >> Traceback (most recent call last): >> File "/usr/share/weewx/weewx/reportengine.py", line 204, in run >> obj.start() >> File "/usr/share/weewx/weewx/reportengine.py", line 300, in start >> self.run() >> File "/usr/share/weewx/weewx/reportengine.py", line 460, in run >> shutil.copy(_file, dest_dir) >> File "/usr/lib/python2.7/shutil.py", line 120, in copy >> copymode(src, dst) >> File "/usr/lib/python2.7/shutil.py", line 91, in copymode >> os.chmod(dst, mode) >> OSError: [Errno 1] Operation not permitted: >> '/var/www/html/weewx/seasons.css' >> >> >> -- >> 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 . >> 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Belchertown Skin 0.8.2 Released
I installed the Belchertown skin and I get none of the graphs. The weather data and report data show just fine. Looking at my log I see that Highcharts runs but nothing is being copied for every instance of Highcharts. Any suggestions? Thanks. Joe Feb 15 17:11:05 weewx wee_reports[1236]: cheetahgenerator: Generated 4 files for report Highcharts_Belchertown in 25.87 seconds Feb 15 17:11:05 weewx wee_reports[1236]: copygenerator: copied 0 files to /var/www/html/weewx/belchertown > -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] 1st Installer Attempt
Here is what I am planning to use for the installer for a custom service
I'm adding.
I would appreciate any feedback you can give but there is one obvious
question... for both the 'snow' standard report and the 'FTP3' ftp report
should the HTML_ROOT be the same, ie 'public_html/snow'?
This was (obviously) adapted from the mem service example.
Thank you!
from setup import ExtensionInstaller
def loader():
return SnowDepthInstaller()
class SnowDepthInstaller(ExtensionInstaller):
def __init__(self):
super(SnowDepthInstaller, self).__init__(
version="0.2",
name='snow',
description='Collect and display snow depth.',
author="Joe Percival",
author_email="m...@mysite.com",
process_services='user.snow.SnowDepth',
config={
'SnowDepth': {
'data_binding': 'snow_binding',
'address = 192.168.1.xxx',
'username = theuser',
'password = thepassword',
'max_mm = 5000',
'app_name = snowpy.py',
'DataBindings': {
'snow_binding': {
'database': 'snow_sqlite',
'table_name': 'archive',
'manager': 'weewx.manager.DaySummaryManager',
'schema': 'user.snow.schema'}},
'Databases': {
'snow_sqlite': {
'database_name': 'snow.sdb',
'driver': 'weedb.sqlite'}},
'StdReport': {
'snow': {
'skin': 'snow',
'HTML_ROOT': 'snow'}
'FTP3': {
'skin': 'Ftp'
'HTML_ROOT': 'public_html/snow'
'user': 'ftpu...@mytsite.com'
'password': 'myftppw'
'server': 'ftp.mysite.com'
'path': '/path/to/where/it/goes'
'passive': '1'}},
files=[('bin/user', ['bin/user/snow.py']),
('skins/snow', ['skins/snow/skin.conf',
'skins/snow/index.html.tmpl',
'skins/snow/weewx.css'])]
)
--
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.
For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: 1st Installer Attempt
The intent is that the "snow" report be put in the public_html/snow
directory and that the FTP3 report grabs the contents of that directory and
FTPs them to my webserver. So, should I change the HTML_ROOT for either
the snow report or FTP3?
On Friday, January 12, 2018 at 2:04:12 PM UTC-8, Joe Percival wrote:
>
> Here is what I am planning to use for the installer for a custom service
> I'm adding.
> I would appreciate any feedback you can give but there is one obvious
> question... for both the 'snow' standard report and the 'FTP3' ftp report
> should the HTML_ROOT be the same, ie 'public_html/snow'?
> This was (obviously) adapted from the mem service example.
> Thank you!
>
> from setup import ExtensionInstaller
>
> def loader():
> return SnowDepthInstaller()
>
> class SnowDepthInstaller(ExtensionInstaller):
> def __init__(self):
> super(SnowDepthInstaller, self).__init__(
> version="0.2",
> name='snow',
> description='Collect and display snow depth.',
> author="Joe Percival",
> author_email="m...@mysite.com",
> process_services='user.snow.SnowDepth',
> config={
> 'SnowDepth': {
> 'data_binding': 'snow_binding',
> 'address = 192.168.1.xxx',
> 'username = theuser',
> 'password = thepassword',
> 'max_mm = 5000',
> 'app_name = snowpy.py',
> 'DataBindings': {
> 'snow_binding': {
> 'database': 'snow_sqlite',
> 'table_name': 'archive',
> 'manager': 'weewx.manager.DaySummaryManager',
> 'schema': 'user.snow.schema'}},
> 'Databases': {
> 'snow_sqlite': {
> 'database_name': 'snow.sdb',
> 'driver': 'weedb.sqlite'}},
> 'StdReport': {
> 'snow': {
> 'skin': 'snow',
> 'HTML_ROOT': 'snow'}
> 'FTP3': {
> 'skin': 'Ftp'
> 'HTML_ROOT': 'public_html/snow'
> 'user': 'ftpu...@mytsite.com'
> 'password': 'myftppw'
> 'server': 'ftp.mysite.com'
> 'path': '/path/to/where/it/goes'
> 'passive': '1'}},
> files=[('bin/user', ['bin/user/snow.py']),
>('skins/snow', ['skins/snow/skin.conf',
>'skins/snow/index.html.tmpl',
>'skins/snow/weewx.css'])]
> )
>
>
--
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.
For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: 1st Installer Attempt
I want to send it to a different location on my webserver, or at least have
the flexibility to do so.
Currently I have 3 ftp reports for that very purpose. I send an XML file
to one location, snapshots to another, and the standard weewx report to a
third. I want to start out, until I have completed troubleshooting, with
the snow report going to it's own location on the server. Later, once
everything is working smoothly I may actually integrate the snow data into
the standard report.
On Friday, January 12, 2018 at 2:04:12 PM UTC-8, Joe Percival wrote:
>
> Here is what I am planning to use for the installer for a custom service
> I'm adding.
> I would appreciate any feedback you can give but there is one obvious
> question... for both the 'snow' standard report and the 'FTP3' ftp report
> should the HTML_ROOT be the same, ie 'public_html/snow'?
> This was (obviously) adapted from the mem service example.
> Thank you!
>
> from setup import ExtensionInstaller
>
> def loader():
> return SnowDepthInstaller()
>
> class SnowDepthInstaller(ExtensionInstaller):
> def __init__(self):
> super(SnowDepthInstaller, self).__init__(
> version="0.2",
> name='snow',
> description='Collect and display snow depth.',
> author="Joe Percival",
> author_email="m...@mysite.com",
> process_services='user.snow.SnowDepth',
> config={
> 'SnowDepth': {
> 'data_binding': 'snow_binding',
> 'address = 192.168.1.xxx',
> 'username = theuser',
> 'password = thepassword',
> 'max_mm = 5000',
> 'app_name = snowpy.py',
> 'DataBindings': {
> 'snow_binding': {
> 'database': 'snow_sqlite',
> 'table_name': 'archive',
> 'manager': 'weewx.manager.DaySummaryManager',
> 'schema': 'user.snow.schema'}},
> 'Databases': {
> 'snow_sqlite': {
> 'database_name': 'snow.sdb',
> 'driver': 'weedb.sqlite'}},
> 'StdReport': {
> 'snow': {
> 'skin': 'snow',
> 'HTML_ROOT': 'snow'}
> 'FTP3': {
> 'skin': 'Ftp'
> 'HTML_ROOT': 'public_html/snow'
> 'user': 'ftpu...@mytsite.com'
> 'password': 'myftppw'
> 'server': 'ftp.mysite.com'
> 'path': '/path/to/where/it/goes'
> 'passive': '1'}},
> files=[('bin/user', ['bin/user/snow.py']),
>('skins/snow', ['skins/snow/skin.conf',
>'skins/snow/index.html.tmpl',
>'skins/snow/weewx.css'])]
> )
>
>
--
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.
For more options, visit https://groups.google.com/d/optout.
[weewx-user] Extension Installer Error
I have tried using the extension installer following the guidance from the
github wiki on an extension package created by modifying the mem extension
example. I do not understand the error message I am getting. Can someone
please explain where I've gone wrong?
My extension package is a zipped directory named weewx_snow which contains
install.py, a bin directory and a skins directory.
here is the error message I am getting:
raise InstallError("Unable to install from '%s': no common path (the
extension archive contains more than a single root directory)" %
extension_path)
weecfg.extension.InstallError: Unable to install from
'/home/pi/Downloads/weewx_snow.zip': no common path (the extension archive
contains more than a single root directory)
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Extension Installer Error
yes. though I have taken out the readme and changelog for the time being. I have found the problem. I created the zip on a Mac and it created a second directory inside the archive called _MACOS. That was confusing the installer. Deleting that directory allowed the installer to proceed (and churn up the next layer of bugs). Thanks, joe > On Jan 13, 2018, at 2:40 PM, gjr80 wrote: > > I know you outlined your zip structure but it wasn't 100% clear to me. I > package in tgz format not zip but the structure I have in my tgz file is: > > name > | > -- install.py > | > -- readme.txt > | > -- changelog > | > -- bin > | | > | -- directories/files to go in $BIN directory > | > -- skins > | > -- directories/files to go in skin directory > > where name is the common name of the extension/driver etc > > Alternatively, post your zip. > > Gary > > -- > You received this message because you are subscribed to a topic in the Google > Groups "weewx-user" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/weewx-user/WI_RccEFDNM/unsubscribe > <https://groups.google.com/d/topic/weewx-user/WI_RccEFDNM/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > weewx-user+unsubscr...@googlegroups.com > <mailto:weewx-user+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout > <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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Extension Installer Syntax Error
Though this section is almost an exact duplicate of the mem extension
install.py file, I am getting a syntax error on the last section of the
file.
File "/var/tmp/weewx_snow/install.py", line 48
files=[('bin/user', ['bin/user/snow.py']),
^
SyntaxError: invalid syntax
here is the exact text in that section of my install.py:
files=[('bin/user', ['bin/user/snow.py']),
('skins/snow', ['skins/snow/skin.conf',
'skins/snow/index.html.tmpl',
'skins/snow/weewx.css'])]
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Extension Installer Syntax Error
I think I found the problem here also… I found one section in the earlier
configuration section where I had not used a closing brace.
> On Jan 13, 2018, at 3:12 PM, Joe Percival wrote:
>
> Though this section is almost an exact duplicate of the mem extension
> install.py file, I am getting a syntax error on the last section of the file.
>
> File "/var/tmp/weewx_snow/install.py", line 48
> files=[('bin/user', ['bin/user/snow.py']),
> ^
> SyntaxError: invalid syntax
>
>
> here is the exact text in that section of my install.py:
>
> files=[('bin/user', ['bin/user/snow.py']),
> ('skins/snow', ['skins/snow/skin.conf',
> 'skins/snow/index.html.tmpl',
> 'skins/snow/weewx.css'])]
>
>
>
> --
> You received this message because you are subscribed to a topic in the Google
> Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/hqwdXDu55eM/unsubscribe
> <https://groups.google.com/d/topic/weewx-user/hqwdXDu55eM/unsubscribe>.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout
> <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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Extension Installer Syntax Error
Yay!
"Finished installing extension '/home/pi/Downloads/weewx_snow.zip’"
> On Jan 13, 2018, at 3:24 PM, Joe Percival wrote:
>
> I think I found the problem here also… I found one section in the earlier
> configuration section where I had not used a closing brace.
>
>> On Jan 13, 2018, at 3:12 PM, Joe Percival > <mailto:j...@bigtreestech.com>> wrote:
>>
>> Though this section is almost an exact duplicate of the mem extension
>> install.py file, I am getting a syntax error on the last section of the file.
>>
>> File "/var/tmp/weewx_snow/install.py", line 48
>> files=[('bin/user', ['bin/user/snow.py']),
>> ^
>> SyntaxError: invalid syntax
>>
>>
>> here is the exact text in that section of my install.py:
>>
>> files=[('bin/user', ['bin/user/snow.py']),
>> ('skins/snow', ['skins/snow/skin.conf',
>> 'skins/snow/index.html.tmpl',
>> 'skins/snow/weewx.css'])]
>>
>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/weewx-user/hqwdXDu55eM/unsubscribe
>> <https://groups.google.com/d/topic/weewx-user/hqwdXDu55eM/unsubscribe>.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx-user+unsubscr...@googlegroups.com
>> <mailto:weewx-user+unsubscr...@googlegroups.com>.
>> For more options, visit https://groups.google.com/d/optout
>> <https://groups.google.com/d/optout>.
>
>
> --
> You received this message because you are subscribed to a topic in the Google
> Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/hqwdXDu55eM/unsubscribe
> <https://groups.google.com/d/topic/weewx-user/hqwdXDu55eM/unsubscribe>.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout
> <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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[weewx-user] SSH Known Hosts issue
The new service I've written uses pysftp which in turn uses SSH. when I run a test script it works. When the service runs I'm getting an SSH exception: SSHException: No hostkey for host 192.168.1.175 found I thought that the problem might be that there was no .ssh/known_hosts file under /home/weewx so I copied the the file from my ~/.ssh directory into /home/weewx/.ssh/. I got the same error. Any ideas as to how to get SSH to recognize the known hosts key when running as weewx? Thanks! -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] SSH Known Hosts issue
Thanks! I ended up solving the problem by specifying the path to the file using pysftp.CnOpts. The service seems to be working now but we won’t know for sure until we get some snow here in the DRY Sierra Nevada mountains. > On Jan 14, 2018, at 1:06 PM, gjr80 wrote: > > The issue is most likely related to which user account is running your code. > When you run your code outside of weeWX what account is being used? Is that > the same account as that which runs weeWX (commonly root)? If they are > different you will need to make sure you known hosts file is in ~/.ssh for > root. No need for anything in the weeWX tree. Or to take a different > approach, try and get your code running outside weeWX when logged in as the > account that runs weeWX, once it works it should work under weeWX (well at > least the ssh part should work). > > You run into similar issues getting rsync to work under weeWX, it's all about > the account that runs weeWX not the account you normally login with. > > Gary > > -- > You received this message because you are subscribed to a topic in the Google > Groups "weewx-user" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/weewx-user/WQdXpSrKyEs/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > weewx-user+unsubscr...@googlegroups.com. > 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Change Database Content
The new service I added saves snow depth measurements to its own sqlite database in archive format with measurements in mm. However, so far (since yesterday) the field usUnits has been posted as weewx.METRIC. I suspect that it should be set to weewx.METRICWX. 1) does it really matter what the usUnits field is set to? 2) if it does matter, how can I either revise all the existing database entries or remove all the entries? Fortunately, all the measurements are 0 so far so no worries about unit conversion. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Change Database Content
Thank you! On Monday, January 15, 2018 at 6:57:04 AM UTC-8, Tom Keffer wrote: > > The difference between METRIC and METRICWX is described in the Customizing > Guide <http://weewx.com/docs/customizing.htm#units>. Briefly, they are > identical except for rain (group_rain and group_rainrate) and wind speed > (group_speed and group_speed2). > > It seems that I cannot emphasize enough, it should not matter what unit > system is used in the database. If an observation type is properly > implemented, it will get converted to the correct, final target unit in the > reports. > > However, if you decide you want to convert from METRIC to METRICWX, you > can use the utility wee_database with the --reconfigure > <http://weewx.com/docs/utilities.htm#Action_--reconfigure11> option. > > -tk > > On Mon, Jan 15, 2018 at 7:40 AM, Joe Percival > wrote: > >> The new service I added saves snow depth measurements to its own sqlite >> database in archive format with measurements in mm. However, so far (since >> yesterday) the field usUnits has been posted as weewx.METRIC. I suspect >> that it should be set to weewx.METRICWX. >> 1) does it really matter what the usUnits field is set to? >> 2) if it does matter, how can I either revise all the existing database >> entries or remove all the entries? >> >> Fortunately, all the measurements are 0 so far so no worries about unit >> conversion. >> >> -- >> 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 . >> 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Problem with Unit Conversion
I know I was assured that no matter the units of the data in the database, I could convert them to what ever I want later. While I suspect that this is true inside the text elements of the template, since Chetah apparently provides nearly full access to python capabilities, I have not found any means by which to convert data for images. Specifically, I have a depth measurement that is stored in the database in mm. I want my graphs / images to display the data in inches or feet. Since this is a custom data type, weewx has no idea that it is in mm and how it is to convert to inches or feet. I’ve read and re-read the user guide and customization guide and have not found a solution. Have I missed something or do I need to revise my custom service to store data in the units I want displayed in the images? Thanks, Joe -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Problem with Unit Conversion
The images I’m talking about are the graphics produced by weewx. A good example is the mem extension example. However, in that example I believe that the “mem” values were captured in the database as the author wished them to be displayed in the end. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Problem with Unit Conversion
The data is in a separate dB as snow_depth. It is measured and archived in mm. The usUnits in each record is METRIC. If I am not mistaken, weewx has no idea how to convert snow_depth to anything else. Hence, if I am not mistaken, I will either need to convert the data before graphs are generated or change the way I store the data so it is stored in the units that I want displayed in the end. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Problem with Unit Conversion
Thanks. It is sounding like my best, if not only, option is to trash the current database and to start over after modifying my service to record snow depth in inches and change the. usUnits to US. Fortunately this is a very new service and we have had zero snow. Unfortunately I am not able to make any changes for a week or so and we are due for some snow this week. Everything will work out I’m sure. -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Cheetah
It has been years since I was involved with Weewx and I have a steep climb to get back up to speed. While Weewx has been running faithfully for those years, recently my webhost made some changes that have broken a number of things on my site so I need to redesign pretty much everything. I am also embarking on providing my community with much more robust weather content. Long ago, when Weewx was fairly young, I did quite a bit of customization work for my site. Rather than attempting to port that to my new architecture I am planning on starting from scratch with the latest version of Weewx. Question(s) of the day: It seems that most / all the links to Cheetah documentation within Weewx documentation are broken. 1) Is Cheetah still supported? 2) If so, where is a good place to go to learn more about it? 3) Is Cheetah still used in Weewx? 4) If Cheetah is not still being supported, are there any alternatives to use within Weewx? Thanks very much! joe -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Cheetah
The problem is not with attempting to upgrade weewx. There are a few things that have happened that have motivated me to upgrade, hardware, software, and how I go about using weewx. These include unreliable recovery from periodic power outages, webhost interference in how page and image caching are managed, and my desire to completely revamp how I display weather data on my site. I've therefore decided that the least miserable path is to start from scratch. FWIW the version of weewx that I am running is from the very first set of releases, maybe even a pre-release version (reliable nonetheless). A few years back when I was thinking of upgrading I was warned that it would not be a smooth transition due to architectural changes that had been made. Even if that were not the case, I would still want to start from scratch this time around. Thanks, joe On Sunday, March 5, 2017 at 12:50:42 PM UTC-8, mwall wrote: > > On Sunday, March 5, 2017 at 1:44:01 PM UTC-5, Joe Percival wrote: >> >> Question(s) of the day: >> It seems that most / all the links to Cheetah documentation within Weewx >> documentation are broken. >> 1) Is Cheetah still supported? >> 2) If so, where is a good place to go to learn more about it? >> 3) Is Cheetah still used in Weewx? >> 4) If Cheetah is not still being supported, are there any alternatives >> to use within Weewx? >> > > cheetah is still used in weewx > > since the cheetah documentation has been unavailable for awhile now (since > late 2016, i think?) we probably should host it at weewx.com. i created > a ticket to track this task. > > https://github.com/weewx/weewx/issues/223 > > unless you wrote some python code or modified weewx itself, your existing > skins and templates should work with the latest weewx. > > what happened when you tried to upgrade? > > m > -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Python Version
The new box I'm configuring for WeeWx has ubuntu 16.04 and Python 2.7.12 installed. Is it worth the trouble to install the latest Python 2.7.13? Thanks, joe -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Ownership
Do I have to leave all the weewx files under root ownership? With my Ubuntu install, while I am a super user, I am not root, and do not know what root's password might be. So far, I changed ownership of /home so that I could move the weex tar.gz file into it and weex.conf so that I could edit it. I have seen mention of using sudo password root which may allow me to log in as root??? sorry for all the newbie questions, joe -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Ownership
thank you! On Sunday, March 5, 2017 at 6:00:09 PM UTC-8, Joe Percival wrote: > > Do I have to leave all the weewx files under root ownership? > With my Ubuntu install, while I am a super user, I am not root, and do not > know what root's password might be. > So far, I changed ownership of /home so that I could move the weex tar.gz > file into it and weex.conf so that I could edit it. > > I have seen mention of using sudo password root which may allow me to log > in as root??? > sorry for all the newbie questions, > joe > > -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Pillow vs PIL
I followed the setup.py installation instructions. One of those instructions is to execute: sudo apt-get install python-imaging >From what I have read, under Ubuntu, this may install Pillow instead of the older PIL, and I have seen suggestions that this may result in the need to install more support packages to handle different image formats. Is this "old news" that I don't need to be concerned about or ??? FYI, not only will I be generating Weewx graphics, but I will also be "doctoring" images downloaded from some webcams. Thanks, joe -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] start problem
I have tried sudo weewxd weewx.conf but I get an error message saying there there is no command weewxd. I installed using setup.py on ubuntu 16.04 I have since upgraded to ubuntu 16.10 in an attempt to fix a bluetooth keyboard problem (unsuccessfully). I put /home/weewx/bin on the PATH and have verified it using sudo $PATH. I temporarily changed ownership of the weewx directory so that I could run the reconfiguration utility but have since changed ownership back to root. What might I have done wrong? Thanks, joe -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Cache Problem
Recently my webhost (bluehost) started adding scripts, without notice or permission, that institute both page and browser caching which has resulted in users being presented with old images unless the image name is changed somehow. I was wondering if there might be a way to do the following: 1) Have weewx create a unique image name for all the images each time a report is generated. 2) Have a method in the template that knows the correct new image names and creates the appropriate html. 3) Have a method in FTP that deletes old content before loading new content to avoid accumulation of old, unused images. regarding #1, if I put cheetah commands inside the configuration file for image names, will they be executed when reports are generated? Just hypothetically, like changing [[[monthrain]]] plot_type = bar yscale = None, None, 0.02 rain aggregate_type = sum aggregate_interval = 86400 label = Rain (daily total) to something like [[[monthrain$timestamp]]] plot_type = bar yscale = None, None, 0.02 rain aggregate_type = sum aggregate_interval = 86400 label = Rain (daily total) Regarding 3), it seems that RSYNC might do the trick but I have to look into it more and also determine if bluehost supports it. thanks, joe -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Cache Problem
It may be. I had not thought of using a parameter on the image src. It'll be interesting to see if it works. Thank you! On Thursday, March 16, 2017 at 8:24:02 AM UTC-7, Tom Keffer wrote: > > Is this thread > <https://groups.google.com/d/msg/weewx-user/CwRLAERrRW0/bAF12-WDDwAJ> > helpful? > > -tk > > On Thu, Mar 16, 2017 at 7:59 AM, Joe Percival > wrote: > >> Recently my webhost (bluehost) started adding scripts, without notice or >> permission, that institute both page and browser caching which has resulted >> in users being presented with old images unless the image name is changed >> somehow. >> I was wondering if there might be a way to do the following: >> 1) Have weewx create a unique image name for all the images each time a >> report is generated. >> 2) Have a method in the template that knows the correct new image names >> and creates the appropriate html. >> 3) Have a method in FTP that deletes old content before loading new >> content to avoid accumulation of old, unused images. >> >> regarding #1, if I put cheetah commands inside the configuration file for >> image names, will they be executed when reports are generated? Just >> hypothetically, like changing >> >> [[[monthrain]]] >> plot_type = bar >> yscale = None, None, 0.02 >> rain >> aggregate_type = sum >> aggregate_interval = 86400 >> label = Rain (daily total) >> >> to something like >> >> [[[monthrain$timestamp]]] >> plot_type = bar >> yscale = None, None, 0.02 >> rain >> aggregate_type = sum >> aggregate_interval = 86400 >> label = Rain (daily total) >> >> >> >> Regarding 3), it seems that RSYNC might do the trick but I have to look >> into it more and also determine if bluehost supports it. >> thanks, >> joe >> >> -- >> 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 . >> 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] No /dev/ttyUSB0
Trying to check connection to vantage pro 2 USB but I have no file /dev/ttyUSB0, nor anything similar. I'm running ubuntu 16.04 LTS on an Azulle Byte Plus. Station is on and plugged into the USB 2.0 port and some other things are plugged into a hub on one of the USB 3.0 ports. Any idea what I may have done wrong? -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] No /dev/ttyUSB0
I don't see anything like that. Could this be a clue? When I did a lsusb the vantage connection indicates that it is a cp210x UART bridge. When I do a osmosis, cp210x is not listed. Usbserial is also missing. Does this mean that the build that came with my machine is incompatible? -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] No /dev/ttyUSB0
I'm about ready to give up on this box and go with the well known rasberry pi 3. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] No /dev/ttyUSB0
Not osmosis... lsmod 😜 -- 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. For more options, visit https://groups.google.com/d/optout.
