[weewx-user] Re: NOAA Reports - Heating Degree Days

The simple part of the answer - you want a [Units] [[DegreeDays]] stanza in your skin config file. It's covered in the v5.1 documentation here . The challenge you will now face is where to put your setting(s). The answer is it

[weewx-user] Re: NOAA reports question

Yes, it appears to have been some sort of caching issue. Looks like after midnight the display updated. I can now see all of the monthly NOAA data. I have more archive updates to do and will look at the web server cache after each one. Craig On Monday, October 16, 2023 at 9:23:04 AM UTC+13

[weewx-user] Re: NOAA reports question

I am only using one skin, Seasons. When I delete the files and they get rebuilt they do show the new data on Seasons. In fact, the NOAA yearly report does have the correct numbers for each month. The History reports are all correct and do update with the archive load. It is just the monthly

[weewx-user] Re: NOAA reports question

The Seasons skin loads the respective NOAA format report file via a call to small javascript function. No processing of the file is performed other than reading the posting the content. This html template and this

[weewx-user] Re: NOAA reports question

Can you provide any more details regarding your installation? How many skins do you have installed? Are you sure, the files you have deleted and rebuilt, are the ones, that are shown in Seasons? Craig Young schrieb am Sonntag, 15. Oktober 2023 um 07:24:22 UTC+2: > I have loaded several months o

[weewx-user] Re: NOAA Reports

You have old data in your database from weewx running before your clock was corrected by ntpd or systemd. See the wiki article " https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data" for the procedure to fix things. You want to search for dateTime < 10 which is in 2001 so it s

[weewx-user] Re: NOAA Reports showing back to 1969

Any time you see 1969 it means your VM came up with a time of zero seconds (or close) since the unix epoch of 1/1/1970 midnight UTC. You're seeing 1969 because you are a few hours behind UTC in your timezone. I've never seen this in bringing up many os in VM in VirtualBox/Vagrant on my Ma

[weewx-user] Re: NOAA Reports not corrcet - Belchertown

Olivier, how did you switch to python3? I can't get it to work. oliv...@gmail.com schrieb am Freitag, 5. Juni 2020 um 00:11:41 UTC+2: > I've found the trouble, was because, my Weewx4 was on Python2. Now > launched with python3 there no more issue on my RPI3 and raspbian10. > > > Le jeudi 4 juin

[weewx-user] Re: NOAA Reports not corrcet - Belchertown

I've found the trouble, was because, my Weewx4 was on Python2. Now launched with python3 there no more issue on my RPI3 and raspbian10. Le jeudi 4 juin 2020 13:53:53 UTC+2, Olivier Payrastre a écrit : > > Yes, why not, but before doing that, i'd like to know if you kept an empty > database or im

[weewx-user] Re: NOAA Reports not corrcet - Belchertown

Yes, why not, but before doing that, i'd like to know if you kept an empty database or import it after ? Thanks a lot. Le jeudi 4 juin 2020 12:56:11 UTC+2, Joachim Puttkammer a écrit : > > For Information > > I have completely reinstalled weewx 4.1.1 ( Raspberry , Meteostick, empty > database,

[weewx-user] Re: NOAA Reports not corrcet - Belchertown

For Information I have completely reinstalled weewx 4.1.1 ( Raspberry , Meteostick, empty database, Belchertown skin). NOAA reports are displayed correctly. Am Dienstag, 2. Juni 2020 11:08:38 UTC+2 schrieb Olivier Payrastre: > > > Hello, > > I just tried update to 4.1.1 this morning, but unfor

[weewx-user] Re: NOAA Reports not corrcet - Belchertown

Hello, I just tried update to 4.1.1 this morning, but unfortunatly, I've the same issue than in 4.0 and 4.1. Best regards. Olivier. -- 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

Re: [weewx-user] Re: NOAA Reports not corrcet - Belchertown

Tom, thanks for looking into this. I had this reported to my GitHub too and hadn't had a chance to dig into it. Hopefully 4.1.1 fixes it! On Sunday, May 31, 2020 at 4:48:28 PM UTC-4, Tom Keffer wrote: > > I think I may know what the problem is. To make the drop down list work, > the templates ha

Re: [weewx-user] Re: NOAA Reports not corrcet - Belchertown

I think I may know what the problem is. To make the drop down list work, the templates have to be processed in a specific order: the "By month" and "By year" first, *then* the "To date" templates. Unfortunately, with the introduction of Python 3, dictionaries are no longer ordered (they were not gu

[weewx-user] Re: NOAA Reports not corrcet - Belchertown

Le samedi 16 mai 2020 17:29:29 UTC+2, Rolf Zanchettin a écrit : > > Hello, > > i have the same problem. > Any advice? > > Thanks in advance > Best regards > Rolf > > Am Freitag, 15. Mai 2020 17:49:30 UTC+2 schrieb Dirk: >> >> I still have this problem. >> All reports are generated and uploaded to

[weewx-user] Re: NOAA Reports not corrcet - Belchertown

Hello, i have the same problem. Any advice? Thanks in advance Best regards Rolf Am Freitag, 15. Mai 2020 17:49:30 UTC+2 schrieb Dirk: > > I still have this problem. > All reports are generated and uploaded to the Server, but only 2 of them > are to see on the webpage. > Any ideas? -- You rece

[weewx-user] Re: NOAA Reports not corrcet - Belchertown

I still have this problem. All reports are generated and uploaded to the Server, but only 2 of them are to see on the webpage. Any ideas? -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails fro

[weewx-user] Re: NOAA Reports not corrcet - Belchertown

Hi, i have the same problem after i have updatet weewx to 4.0.0, only the year 2020 Jan Feb are showing, any solution? Am Dienstag, 5. Mai 2020 23:30:23 UTC+2 schrieb Joachim Puttkammer: > > Hi, > I have installed weewx (4.0.0) with the skin Belchertown (1.1) on the > local PC (Debian Buster).

[weewx-user] Re: NOAA Reports Blank

The barometer issue was it. I am using an Acurite 5-in-1 over SDR and it doesn't include pressure data. I was able to add pressure data using a BME280 https://gitlab.com/wjcarpenter/bme280wx and now the reports generate great! On Sunday, March 1, 2020 at 1:47:11 AM UTC-5, gjr80 wrote: > > Hi, >

[weewx-user] Re: NOAA Reports Blank

Hi, I'll wager you are using WeeWX 3.x and are (still) having barometer/pressure problems? If so you are likely suffering from this issue . In a nutshell the 3.x and earlier NOAA reports require that a given day or month have barometer data before tha

[weewx-user] Re: NOAA Reports Blank

can you attach your skin file for belchertown and also seasons. which skin should be generating the noaa reports? is the noaa report being generated with no data inside or is it not being generated at all. Check the date and time of the latest noaa file. On Sunday, 1 March 2020 05:58:03

[weewx-user] Re: NOAA Reports Blank

System Log on Archive: https://pastebin.com/zszNY2C3 On Saturday, February 29, 2020 at 10:51:56 PM UTC-5, Kenny Stier wrote: > > WeeWX is generating blank NOAA reports for me. > https://wx.millhousen.com/reports/ > > In the Belchertown Q&A, it says you may have to give it a few archive > interva

[weewx-user] Re: NOAA Reports from imported Data

I'm not sure I have the full picture on exactly what data and NOAA reports you have/do not have over what period but the NOAA monthly reports require there to be at least one non-None barometer value for each day (ie any day with no barometer data will be skipped). For the NOAA yearly reports th

Re: [weewx-user] Re: NOAA Reports from imported Data

Could you do a full select on archive_day_outTemp? select * from archive_day_outTemp; It looks like there is some data in there. -tk On Sun, Mar 3, 2019 at 5:33 AM Michael wrote: > Hello, Thomas, > > my imported data has different origins. The first year only inTemp un > OutTemp, 2 values per

[weewx-user] Re: NOAA Reports from imported Data

Hello, Thomas, my imported data has different origins. The first year only inTemp un OutTemp, 2 values per day (min and max). Then until 2017 the values recorded by the software of my station and from 06/2018 the values of WeeWX. Here is a small example from weewx.archiv MariaDB [weewx]> SELECT

Re: [weewx-user] Re: NOAA Reports from imported Data

Well, you certainly have lots of data that predates 1-Jun-2018! Have you taken a look in the database to see whether the data are valid? Something like: select dateTime, barometer, outTemp, outHumidity, from archive_day_outTemp where dateTime < 1527811200 limit 20; Question: when you say you "can

Re: [weewx-user] Re: NOAA Reports from imported Data

Hi Thomas, I started the data import as follows: wee_import --config=/home/weewx/weewx.conf --import-config=/home/weewx/NexusImport/csv.conf csv.conf ist attached and here is the result of the query: MariaDB [weewx]> select count(dateTime) from archive where dateTime < 1527811200; +---

Re: [weewx-user] Re: NOAA Reports from imported Data

Do you recall how you did wee_import? Are you sure the missing data was actually imported? We can check what is actually in your database, but, first, you will need to locate it. If you used a package installer (apt-get), it will be in /var/lib/weewx/weewx.sdb. If you used setup.py, it will be in

[weewx-user] Re: NOAA Reports from imported Data

Hi Andrew, done as described. The NOAA reports were also rebuilt, but still the imported periods are without data. Michael Am Samstag, 2. März 2019 14:31:31 UTC+1 schrieb Andrew Milner: > > If you are certain the imported data is in the database and it is just the > NOAA reports which are miss

[weewx-user] Re: NOAA Reports from imported Data

If you are certain the imported data is in the database and it is just the NOAA reports which are missing then the easiest way is to force a recreation of all the NOAA reports. Just stop weewx, delete all the NOAA files (monthly and yearly) in the NOAA directory, and restart weewx. On the next

Re: [weewx-user] Re: NOAA reports not available

Thanks for the time you spent on this. I'll try eliminating things until I find it. I may even have to reinstall weewx. Much appreciated for the help. Bob On Monday, February 11, 2019 at 5:59:39 PM UTC-5, mwall wrote: > > On Saturday, February 9, 2019 at 9:19:27 AM UTC-5, bgrattan wrote: >>

Re: [weewx-user] Re: NOAA reports not available

On Saturday, February 9, 2019 at 9:19:27 AM UTC-5, bgrattan wrote: > > Matt, > Here are the three files. ForecastVariables is commented out. I can change > it if you need. NOAA drop down menus now work. Thanks. Bob > i cannot replicate the behavior you are seeing. no matter what i do, the NOA

Re: [weewx-user] Re: NOAA reports not available

Sorry, no date problem... I just read the update info for 3.9.1. Bob On Saturday, February 9, 2019 at 11:32:04 AM UTC-5, bgra...@umw.edu wrote: > > Matt, > One thing I have noticed which may or may not give you a clue is my [Time] > format is not being picked up correctly from skin.conf. I hav

Re: [weewx-user] Re: NOAA reports not available

Matt, One thing I have noticed which may or may not give you a clue is my [Time] format is not being picked up correctly from skin.conf. I have set the following which isn't showing--it seems to have defaulted to something else/ day= %H:%M week = %H:%M on %A

Re: [weewx-user] Re: NOAA reports not available

Matt, Here are the three files. ForecastVariables is commented out. I can change it if you need. NOAA drop down menus now work. Thanks. Bob On Friday, February 8, 2019 at 6:49:29 PM UTC-5, mwall wrote: > > On Friday, February 8, 2019 at 6:43:14 PM UTC-5, bgrattan wrote: >> >> I have removed Fo

Re: [weewx-user] Re: NOAA reports not available

On Friday, February 8, 2019 at 6:43:14 PM UTC-5, bgrattan wrote: > > I have removed ForecastVariables in skin.conf. All of the month/year > selections appear as they should--you can have a look. The forecast items > no longer appear. > please post these files: skins/Standard/index.html.tmpl ski

Re: [weewx-user] Re: NOAA reports not available

Matt, I have removed ForecastVariables in skin.conf. All of the month/year selections appear as they should--you can have a look. The forecast items no longer appear. The [[[DAILYCHARTS]]], [[[MONTHLYCHARTS]]], and [[[YEARLYCHARTS]]] are from trying to install the WX-HWS page which I haven't

Re: [weewx-user] Re: NOAA reports not available

On Friday, February 8, 2019 at 3:03:34 PM UTC-5, Glenn McKechnie wrote: > > > The commented code that you see in Bob's template is not the actual > NOAA generating code. It is a duplicate that I included when we were > troubleshooting this originally. The original #for...#end for code is > st

Re: [weewx-user] Re: NOAA reports not available

Hi Matt, Further to Bob's comment regarding those html comments. The commented code that you see in Bob's template is not the actual NOAA generating code. It is a duplicate that I included when we were troubleshooting this originally. The original #for...#end for code is still contained in the t

Re: [weewx-user] Re: NOAA reports not available

Matt, Thanks for the quick reply. I've been trying to fix things and forgot to clean up some of the test code changes, sorry. However, when I make the corrections the drop down NOAA menus are still missing. I have attached my corrected index.html.tmpl file. No errors are showing up that I see.

Re: [weewx-user] Re: NOAA reports not available

On Friday, February 8, 2019 at 10:04:35 AM UTC-5, bgrattan wrote: > > Any idea what's going on here? You say its working for you but I can't > seem to find the correct setting to have both the forecast and NOAA > summaries. I have attached my Standard/skin.conf > in your index.html.tmpl you ha

Re: [weewx-user] Re: NOAA reports not available

Matt, I have upgraded to weewx 3.9.1 and forecast 3.3.2. I thought all was fine but then found that my NOAA summary drop down menus had disappeared again. I added the forecast_compact to the Standard skin (with your help, thanks) and everything seems good except the NOAA menus. The NOAA *.txt

[weewx-user] Re: NOAA Reports Belchertown Skin

The NOAA files Belchertown skin are using are from the Standard skin. When comparing 3.9.1's Standard skin NOAA files, there are no changes to what Belchertown has now. It appears as though the Belchertown NOAA files already have the same Barometer checks

[weewx-user] Re: NOAA Reports Belchertown Skin

Ah yes, should have remembered there is a check in the NOAA templates to see whether data is to be output for that row (day or month) - the check is whether there is barometer data for that row. No barometer data the row is left blank, have barometer data the row is populated. This has come up

[weewx-user] Re: NOAA Reports Belchertown Skin

Well, it appears that I solved this. I picked up a WH25 to get barometer and inside temp to weewx until I could figure out how to capture the WH32B. Once I started capturing a barometer reading again, it started generating the NOAA reports. Odd, but that was the only thing IO changed. I wil

Re: [weewx-user] Re: NOAA reports not available

another data point: forecast 3.3.2 works fine with the standard skin, as show in the attached screenshot. i included the forecast by adding two lines to index.html.tmpl in the Standard skin: #include "forecast_compact.inc" Current Conditions

Re: [weewx-user] Re: NOAA reports not available

On Tuesday, February 5, 2019 at 4:34:24 PM UTC-5, Glenn McKechnie wrote: > > With hindsight in full, a search on weewx-user returns a couple of > hits, 2 of interest are... > https://groups.google.com/d/topic/weewx-user/k3yy2IK__Ow/discussion > https://groups.google.com/d/topic/weewx-user/p1A

Re: [weewx-user] Re: NOAA reports not available

Indeed! That looks better, the menu is now populated and working. It appears that removing the "search_list_extensions = user.forecast.ForecastVariables" entry has made all the difference. That line is still in the copy I have here but I don't have the forecast extension installed so it had nothi

Re: [weewx-user] Re: NOAA reports not available

Glenn, *I've got it!!!* I checked the original skin.conf under 3.8.2 and noticed that "search_list_extensions = user.forecast.ForecastVariables" didn't exist under [CheetahGenerator]. I commented it out in mine and the summaries worked from drop down lists. I'll have to go back and figure out w

Re: [weewx-user] Re: NOAA reports not available

To get the entries for the dropdown list, the report generator does not scan the NOAA subdirectory. Instead, it watches what goes by in the [[SummaryByMonth]] and [[SummaryByYear]] sections, then saves that result. So, for the dropdown list to populate properly, the [[SummaryByMonth]] and [[Summar

Re: [weewx-user] Re: NOAA reports not available

Glenn, Had a thought that might not mean anything but here it goes. The page is not finding the summaries in /NOAA because I am unable to select a month or year. The box fails to display a drop down list of months or years from which I would select. It seems that it's the actual drop down list

Re: [weewx-user] Re: NOAA reports not available

No insights (to me ) from the files you provided. What's in no.htaccess? I wouldn't have thought there could be anything in there that would prevent weewx from using the contents of NOAA. It's more a webserver control point - but then...? Ownership and permissions seem okay. root.www-data is typ

Re: [weewx-user] Re: NOAA reports not available

Hey Bob, There is no change, but it confirms that 1.) we are working on the same page (the change has propagated to godaddy) 2.) The [[SummaryByMonth]] and [[SummaryByYear]] sections aren't being picked up and filled. If weewx couldn't find them, it would complain with an error - at least it does

Re: [weewx-user] Re: NOAA reports not available

Glenn, Your files are loaded now. Haven't seen any difference. I upgraded from 3.7.0 to 3.8.2 several months ago. Could there be a problem with cheetah? Is it possible to reinstall cheetah without messing up the configuration? I've also been trying to install WX-HWS, with only partial luck, as it

[weewx-user] Re: NOAA Reports Belchertown Skin

Thanks guys, I am travelling and will be away from my pi until Thursday, I will try the suggested changes then and report back. Thanks! On Sunday, February 3, 2019 at 10:47:42 PM UTC-6, gjr80 wrote: > > I agree with Pat that some changes are needed to [StdReport]. I don't > expect the Belcherto

Re: [weewx-user] Re: NOAA reports not available

Bugger - wrong file. Use this one. On 04/02/2019, Glenn McKechnie wrote: > Hi Bob, > > The simplest explanation would be that CheetahGenerator is not finding > the NOAA templates to generate the html links - and that it's not > throwing an error in the process. > > Attached is a version of your

Re: [weewx-user] Re: NOAA reports not available

Hi Bob, The simplest explanation would be that CheetahGenerator is not finding the NOAA templates to generate the html links - and that it's not throwing an error in the process. Attached is a version of your index.html.tmpl that will display the NOAA filenames it finds. If it finds any (I don't

[weewx-user] Re: NOAA Reports Belchertown Skin

I agree with Pat that some changes are needed to [StdReport]. I don't expect the Belchertown extension would be interfering with other skins, but for some reason it appears that a number of settings in [StdReport] have changed from default and would appear to be conflicting (the conflicts may n

Re: [weewx-user] Re: NOAA reports not available

Glenn, See below and attached. Thanks Bob On Sunday, February 3, 2019 at 4:44:22 PM UTC-5, Glenn McKechnie wrote: > > Okay, it seems that we're back to square one. > > Using your template here. It now works. (the utf-8 selection code > within it must be correcting the problem I encountered.)

[weewx-user] Re: NOAA Reports Belchertown Skin

The Belchertown skin shouldn't be altering the skin settings of other skins. The exception is the Highcharts_Belchertown skin (which I refer to as a subskin). However, the Belchertown skin does ship with its own NOAA report templates - which are borrowed from the Standard skin. Exact copy/paste

[weewx-user] Re: NOAA Reports Belchertown Skin

Yup, I noticed that and just commented out the StdReport, same results (no new data in NOAA reports), though it only runs the skin once. On Sunday, February 3, 2019 at 3:41:58 PM UTC-6, gjr80 wrote: > > So WeeWX is generating archive records with data and saving them to > archive. Looking at wee

Re: [weewx-user] Re: NOAA reports not available

Okay, it seems that we're back to square one. Using your template here. It now works. (the utf-8 selection code within it must be correcting the problem I encountered.) Regarding your skin.conf file. If I remove the templates I don't have from it, then it also works. ie: I get an index.html page g

[weewx-user] Re: NOAA Reports Belchertown Skin

So WeeWX is generating archive records with data and saving them to archive. Looking at weewx.conf I notice you are not running the Standard skin: [[StandardReport]] # See the customizing guide to change the units, plot types and line # colors, modify the fonts, display additi

[weewx-user] Re: NOAA Reports Belchertown Skin

weewx is 3.8.2 and I am using sqlite3 v3.7.17 All other data seems to plot well in the standard skin when I was using it and in Belchertown, so the data is being written. I am not currently capture barometric pressure, but I do not even see that in the NOAA reports. . On Sunday, February 3, 201

[weewx-user] Re: NOAA Reports Belchertown Skin

Yeah, I don't think it's the skin either. You do appear to have some data though but it seems to be spotty. Your LOOPs look good and your RECs do too. I'm a bit at a loss too. What version of weewx and what database type are you using (sqlite or mysql)? -- You received this message because y

[weewx-user] Re: NOAA Reports Belchertown Skin

Oh and I am 100% convinced it is not the Belchertown skin. On Sunday, February 3, 2019 at 1:09:56 PM UTC-6, tor...@torrin.org wrote: > > I am running 0.8.2, here are the files: > > cd /var/www/html/weewx/NOAA/ > [root@localhost NOAA]# ls -ltr > total 12 > -rw-r--r--. 1 root root 1037 Feb 2 22:31

[weewx-user] Re: NOAA Reports Belchertown Skin

I am running 0.8.2, here are the files: cd /var/www/html/weewx/NOAA/ [root@localhost NOAA]# ls -ltr total 12 -rw-r--r--. 1 root root 1037 Feb 2 22:31 NOAA-2019-01.txt -rw-r--r--. 1 root root 1788 Feb 3 13:05 NOAA-2019.txt -rw-r--r--. 1 root root 857 Feb 3 13:05 NOAA-2019-02.txt [root@localhost

[weewx-user] Re: NOAA Reports Belchertown Skin

Just curious, what version of Belchertown skin are you running? I don't see it outputting the version number in your log file which tells me you may be a few versions old. I'd say upgrade to the latest release 0.8.2, but I'm finalizing a 0

[weewx-user] Re: NOAA Reports Belchertown Skin

Here is the output to the screen when running weewxd: weewxd /etc/weewx/weewx.conf -n TRACKER /etc/weewx/weewx.conf LOOP: 2019-02-03 11:03:28 CST (1549213408) appTemp: 61.5912522388, cloudbase: 3116.86206104, dateTime: 1549213408, dewpoint: 52.0578069314, heatindex: 62.78, humidex: 66.06463311

[weewx-user] Re: NOAA Reports Belchertown Skin

No modification to the standard skin at all, I checked the file stamps and all are from August of last year (I installed on a few weeks ago) I do indeed have debug = 1 set in my weewx config, I have always felt the info put in the log is light for debug mode being on. I tried removing the spac

Re: [weewx-user] Re: NOAA reports not available

Glenn, Something odd. My index.html.tmpl looks ok (attached) so something is happening when it's used to generate the page. I have also attached the skin.conf file in case that helps in understanding what's going on. Both files are local and the problem is on my local machine as well as the pag

[weewx-user] Re: NOAA Reports Belchertown Skin

Ok, a few things. You appear to be generating archive records and saving them to database. Your log indicates the Standard skin is generating 13 files each report cycle, an unmodified Standard skin should be producing at least 15 files each report cycle. Have you modified the Standard skin at al

[weewx-user] Re: NOAA Reports Belchertown Skin

Here is a full run from journalctl -l: Feb 02 23:55:31 localhost weewx[482]: manager: Added record 2019-02-02 23:55:00 CST (1549173300) to database 'weewx.sdb' Feb 02 23:55:31 localhost weewx[482]: manager: Added record 2019-02-02 23:55:00 CST (1549173300) to daily summary in 'weewx.sdb' Feb 02

[weewx-user] Re: NOAA Reports Belchertown Skin

I am happy to post the logs: Feb 2 23:30:27 localhost weewx[482]: manager: Added record 2019-02-02 23:30:00 CST (1549171800) to database 'weewx.sdb' Feb 2 23:30:27 localhost weewx[482]: manager: Added record 2019-02-02 23:30:00 CST (1549171800) to daily summary in 'weewx.sdb' Feb 2 23:30:30 l

[weewx-user] Re: NOAA Reports Belchertown Skin

So it seems you are not prepared to post your logs? As I said in my previous post not only do we look for errors in the logs but we look to see what is/is not going on. That often gives us a clue to the issue. Gary -- You received this message because you are subscribed to the Google Groups "

[weewx-user] Re: NOAA Reports Belchertown Skin

I have been running debug=1 since I installed, I am also monitoring all weewx activity by tailing /var/log/messages and journalctl -l, there have been no errors on generating reports. Again, a new set of NOAA reports are generated each report run, just no data in them. On Saturday, February 2,

[weewx-user] Re: NOAA Reports Belchertown Skin

There may well be no errors in the logs but sometimes it is not errors that we are looking for rather what is and isn't in the log. I suggest you set debug=1 if you haven't already, restart WeeWX and let it run for 2-3 archive periods then post the log from the restart through until the 2-3 arch

[weewx-user] Re: NOAA Reports Belchertown Skin

Hmmm, the only other variable here is I was using interceptor for a bit, but it was not stable (stopped capturing packets after 1-4 hours), maybe this is SDR vs Interceptor/observer data capture? On Saturday, February 2, 2019 at 10:17:31 PM UTC-6, tor...@torrin.org wrote: > > It is odd, I got

[weewx-user] Re: NOAA Reports Belchertown Skin

It is odd, I got weewx running on 1/30/19 and I have entries for 1/30 and 1/31, nothing for 2/1 or 2/2. I checked the standard skin NOAA reports and they were also missing 2/1 and 2/2. I checked the NOAA templates in the Belchertown skin and diff'd the weewx standard skin and they are identic

[weewx-user] Re: NOAA Reports Belchertown Skin

Hey there. Any errors in syslog when generating the reports? Not sure off top of my head why NOAA reports would fail. They get the info from within weewx itself. Do you have any data in the Reports page? What do you mean by the hourly forecasts extended into Belchertown? I'm using them at https

Re: [weewx-user] Re: NOAA reports not available

Glenn, Thanks! I’ll try the fix tomorrow. Not sure how or when this got messed up. As I haven’t used the summary feature for a while then I haven’t missed it. Much appreciated! Just curious where you are located? Will keep you posted. Bob -- You received this message because you are subscribed

Re: [weewx-user] Re: NOAA reports not available

Hi Bob, Your page at http://grattans.org/wx/ is missing some vital code, which interestingly you have correct in your last post. Is that from your local tmpl version? The navbar code is missing the 6 lines that start with - in the diff below. @@ -451,17 +451,11 @@ Monthly summ

[weewx-user] Re: NOAA Reports Belchertown Skin

Actually, this looks like a weewx issue, since with the old standard skin it was not working past Jan 31. Any help would be appreciated. On Saturday, February 2, 2019 at 3:29:36 PM UTC-6, tor...@torrin.org wrote: > > I installed the Belchertown skin last night (It is quite AWESOME!), my > onl

Re: [weewx-user] Re: NOAA reports not available

Glenn, Here's what I found, so far: two NOAA directories /home/weewx/skins/Standard/NOAA - contains 2 template files for and MM summaries /home/weewx/pub_html/NOAA - contains all the summary files *.txt from 2007-present day I substituted the original index.html.tmpl and an older weewx.co

Re: [weewx-user] Re: NOAA reports not available

Okay, That just confirms your NOAA problem is somewhere else. If wxobs is working for you then I'm assuming that will be on your local computer, as it's not working on your remote (public) side. That should be fixable, but is not your original issue. Your original issue... You mention that the NOA

Re: [weewx-user] Re: NOAA reports not available

Glenn, Still missing the NOAA reports. I moved datepicker.js and it didn't seem to change anything. I have wxobs running fine and removing datepicker.js didn't seem to affect it, or anything else. On Thursday, January 31, 2019 at 7:04:50 PM UTC-5, Glenn McKechnie wrote: > > I've had this happen

Re: [weewx-user] Re: NOAA reports not available

Thanks, Glenn, I’ll check on that tomorrow. Much appreciated for the help. Bob -- 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.

Re: [weewx-user] Re: NOAA reports not available

I've had this happen before and its been a javascript problem , clashing with similarly named code or a missing script. wxobs (https://github.com/glennmckechnie/weewx-wxobs ) uses either one of 2 files, standard.js or seasons.js skins for the generation of the NOAA templates - but only for itself

[weewx-user] Re: NOAA reports not available

It might be missing the NOAA tmpl files. Maybe reinstall the skin and then restart weewx and see if they are back after an interval period -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails fr

[weewx-user] Re: NOAA reports not available

It seems that HTMLPages is coming from the Bootstrap skin so I'll look into that. On Thursday, January 31, 2019 at 5:12:45 PM UTC-5, Pat wrote: > > It looks like you're using 2 skins called "wxobs" and "HTMLPages"? If so, > you might need to check with the developer of those skins to see why. >

[weewx-user] Re: NOAA reports not available

Thanks for the quick reply, Pat. Yes I am using the extension "wxobs" plus the Standard skin but am not sure what "HTMLPages" is connected to. Bob -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving

[weewx-user] Re: NOAA reports not available

It looks like you're using 2 skins called "wxobs" and "HTMLPages"? If so, you might need to check with the developer of those skins to see why. If that's not true then you haven't pasted enough of the logs. On Thursday, January 31, 2019 at 5:07:14 PM UTC-5, bgra...@umw.edu wrote: > > Hello, >

[weewx-user] Re: NOAA reports not showing up

For the life of me, I have no idea where that sigma came from... probably while trying to edit something via VNC. That was exactly the problem...thank you both! On Friday, October 13, 2017 at 10:58:20 PM UTC-4, WxManAJB wrote: > > I'm running the Responsive skin through Weewx and noticed that wh

[weewx-user] Re: NOAA reports not showing up

FWIW Gary - I see the sigma also, and the demo site for responsive skin does not appear to contain the sigma - so I reckon you have got it spot on there - so forget the feeble suggestions I made earlier that were really stabs in the dark!! On Saturday, 14 October 2017 12:53:39 UTC+3, gjr80 wr

[weewx-user] Re: NOAA reports not showing up

I'm no java or css expert, but after getting to the site (your link has a double n when it should be a single) - the only things I can suggest would be a) replace "#" with "#!" b) remove the "#" completely c) 'tweak'/simplify the javascript to build the reference link in a simpler manner - I su