Recent Posts

Pages: [1] 2 3 ... 10
1
Weather Web Site Help / Re: Warning: Undefined variable $curlStatus
« Last post by saratogaWX on Today at 04:30:34 PM »
api.weather.gov is down.  The message is a result of that problem.
2
WiFiLogger/Meteo-Pi / AWEKAS uploading has stopped
« Last post by xmas111 on Today at 04:30:30 PM »
I was checking my AWEKAS webpage and noticed it hasn't received had any new weather data from WifiLogger V2 since Jan. 2024.

The user name and password in WfiLogger are correct. I used them to log into AWEKAS and they work.

Anyone else having issues uploading to AWEKAS?

Thanks,
 John

3
Weather Web Site Help / Warning: Undefined variable $curlStatus
« Last post by yamiacaveman on Today at 04:04:09 PM »
This just showed up: Warning: Undefined variable $curlStatus in /home/hogan2/pennlake.us/advforecast2.php on line 480

I see nothing that indicates I need to update the script, any ideas?

pennlake.us

4
Weather Website PHP/AJAX scripting / api.weather.gov is down
« Last post by Jasiu on Today at 04:00:12 PM »
As noted by Ken within another post, the NWS API is currently down.  I'm getting 502 errors for everything.

Quote
SENIOR DUTY METEOROLOGIST NWS ALERT ADMINISTRATIVE MESSAGE
NWS NCEP CENTRAL OPERATIONS COLLEGE PARK MD
1732Z WED APR 24 2024


...API.WEATHER.GOV DOWN...

Api.weather.gov is currently down. NCO is investigating.


Gerhardt/SDM/NCO/NCEP
5
Thank you, Ken.  I did make the fixes as you advised but a crop of errors is still showing.  The zones had worked up to this time.  But I’ll wait until the api.weather.gov issue is resolved and see if that fixes my problem.
6
So, a couple of issues.  First, the NOAA Forecast Zone you have is incorrect:
Quote
<!-- WARNING: NOAAZone='MNZ049' is not correct.  Will use 'MNZ050' for this point location per NWS. -->
<!-- point forecastURL = 'https://api.weather.gov/gridpoints/MPX/78,102/forecast' -->
<!-- zone  forecastURL = 'https://api.weather.gov/zones/forecast/MNZ050/forecast' -->
<!-- logged 'Fetch fail' to './cache/advforecast2-log-2024-04-24.txt' -->
<!-- curl fetching 'https://api.weather.gov/gridpoints/MPX/78,102/forecast' -->
<!-- HTTP stats:  RC=502 dest=23.220.140.14 port=443 (from sce=192.252.154.18)
      Times: dns=0.001 conn=0.020 pxfer=0.045 get=0.091 total=0.136 secs -->
so change all occurrences of "MNZ049" to "MNZ050" in Settings.php and upload it.

Second, the point forecast is not currently available, so the script tries to use the Zone forecast, but since the zone is incorrect, It just returns null data to the dashboard and wxforecast.php giving you the Undefined errata.

Do the correction to Settings.php, then run wxforecast.php?force=1 to reload the cache.. the Zone forecast should then be displayed if the point forecast isn't available.

Related: the NCEP ops site just posted
Quote
SENIOR DUTY METEOROLOGIST NWS ALERT ADMINISTRATIVE MESSAGE
NWS NCEP CENTRAL OPERATIONS COLLEGE PARK MD
1732Z WED APR 24 2024


...API.WEATHER.GOV DOWN...

Api.weather.gov is currently down. NCO is investigating.


Gerhardt/SDM/NCO/NCEP
so your fix (still needed) may not be available if api.weather.gov is still having issues.
7
Advforecast2.php and ajaxdashboard.php errors suddenly started appearing on my home page this afternoon.  I am current on all updates.  Not sure what is the exact problem, but it appears to be with the forecast scripts. Any help would be most appreciated.  Site was working smoothly until now. 

https://sartelleastweather.com
8
you should have (in the Base-USA distribution) wxnws-alerts-log.php to do just that.
Just change flyout-menu.xml to link to wxnws-alerts-log.php instead of nws-alerts-log.php
9
That is truly an ancient script by Michael of the former relayweather.. the last version I have was from 2011.

I think the issue is your quality data page from gladstone has a missing icon for a check mark about wind data and that causes the script to emit the Notice errata.

You can change cwopstats.php to have
Quote
<?php
error_reporting(E_ALL & ~E_NOTICE);
at the top of of the page (replacing the opening <?php

 
10
The issue where you see "°F" in the result is due to the degree sign being in UTF-8 while the browser is defaulting to ISO-8859-1.

In your meteobridge template, use &deg; instead of a literal degree sign, then it should appear correctly irrespective of what the browser's default character set is.

Also, you might try additionally in using dashboard.txt as the result name since it is really just text w/o any HTML markup.

Thank you for the help. For now I just deleted the degree marks....trying to fig out what areas I need to add the code you said.

Thanks again for the help!
Pages: [1] 2 3 ... 10