I fixed it by commenting out $solars = array();.
On Monday, October 24, 2016 at 9:47:54 PM UTC-5, john hutchison wrote:
>
> I am running weewx 3.5.0 and everything was working properly while running
> the simulator. weewx,weewxDB, and meteotemplate were populating the db's.
> Today
I am running weewx 3.5.0 and everything was working properly while running
the simulator. weewx,weewxDB, and meteotemplate were populating the db's.
Today I installed an Acurite 5-in-1 and enabled the driver. weewx and
weexDB are updating properly, and the live values in meteotemplate are
Woke up this morning and it's back to not publishing to WOW, WU, and PWS,
while CWOP, AWEKAS, and WeatherCloud still work. Meteotemplate posting
still works too using the API extension.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To
>
> This is what I get:
>
wget
https://weatherstation.wunderground.com/weatherstation/updateweatherstation.php?ID=KCASANFR5=XX=2000-01-01+10
%3A32%3A35=230=12=12=70=0=29.1=68.2=90===vws%20versionxx=update
raw
[15] 32074
[16] 32075
[17] 32076
[18] 32077
[19] 32078
[20] 32079
[21] 32080
[22]
Well it's working again and has been for the past 3 days. I have made no
changes to either the program or router. FWIW the router is a custom
pfSense box running Snort, pfBlocker, Squid/SquidGuard, etc.. but none of
them were reporting any blocking happening regarding the machine running
Well, after two days I started weewx in debug lvl 3 and now it's updating
to WOW, WU, and PWS... I am trying to remember how to re-enable saving logs
to syslog, as several months ago I installed loganaylzer and syslog-ng and
disabled local syslogs. But it's working somehow now. Going to leave
This is also a DEB install.
--
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
I have been using weewx for almost a year now with few issues. Publishing
has always worked for WU, WOW, PWS, CWOP, AWEKAS, & WeatherCloud. All of a
sudden, two days ago WU, PWS, & WOW started throwing the following messages
while running the archive interval:
restx: Wunderground-PWS: Failed
I fixed it. Was using the publish url from the syslog
http://api.openweathermap.org/data/3.0/measurements?appid=
instead of the registration url
http://api.openweathermap.org/data/3.0/stations?appid=
--
You received this message because you are subscribed to the Google Groups
"weewx-user"
Chotechai Piyavongsiri,
I get the following message when using postman:
{
> "code": 41,
> "message": "unmarshal type error:
> expected=[]types.MeasurementRequest, got=object, offset=1"
> }
>
>
>
Other than my appid and body, your screenshots match my postman entries.
Here is my
In order for me to get it working, I had to set it to true and overwrite,
delete the file and restart weewx. The documentation states that true is
default but that wasn't the case in my experience. When it created the file
again it had the headers. I let it go for a couple archive intervals
In the POST field for postman, do you have
http://api.openweathermap.org/data/3.0/stations?appid=
--
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
In Postman, you should have a button that says "code" under the save
button. Can you copy the output of that and post it here, removing your
appid and personal info of course?
Here is mine:
POST /data/3.0/stations?appid=myAppID HTTP/1.1
Host: api.openweathermap.org
Content-Type:
Server updated to 3.8.2 last week and caused the following:
Aug 23 11:50:02 john-PS583AA-ABA-a1020n weewx[19269]: 'outTemp'
Aug 23 11:50:02 john-PS583AA-ABA-a1020n weewx[19269]: Traceback
(most recent call last):
Aug 23 11:50:02 john-PS583AA-ABA-a1020n weewx[19269]:
It is a deb installation, the server is configured for unattended updates.
In troubleshooting the issues briefly last week I noticed weewx was a newer
version than I recalled, and matched the current version on the website.
The backup conf date also matched the last day weewx was posting
I am receiving the following errors:
john@john-PS583AA-ABA-a1020n ~ $ wd_database -h
Traceback (most recent call last):
File "/usr/local/bin/wd_database", line 44, in
import user.wdSearchX3
ImportError: No module named wdSearchX3
&&
Feb 7 13:56:16 john-PS583AA-ABA-a1020n weewx[29003]:
:13 AM UTC-6, john hutchison wrote:
>
> OK, thanks for looking into it. Further info is I had made NO changes to
> weewx AFIAK, and it has been happening since mid last year. The cheetah
> errors are the only errors shown when debug=1, and happen every archive
> interval.
>
t; Gary
>
> On Friday, 8 February 2019 06:31:41 UTC+10, john hutchison wrote:
>>
>> I am receiving the following errors:
>>
>> john@john-PS583AA-ABA-a1020n ~ $ wd_database -h
>> Traceback (most recent call last):
>> File "/usr/local/bin/wd_database
18 matches
Mail list logo
