[weewx-user] Re: Datenbank zusammen legen.

2020-04-10 Thread Günther Wrana
Hello,

I would have my .csv file here that I would like to import. How should it 
look like? Do I have to insert the column names listed in the documentation 
in the header?

Time,Temp,Dewpoint,Press,WindDir,WindSpeed,WindGust,Hum,dailyrain,SolarRad

Date and time are in one column, do they also have to have this UNIX date 
format?

Thank you Günther

-- 
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/b6167402-61bb-4d6d-ab0f-d48055d99e6c%40googlegroups.com.
NO.,Zeit,Intervall,Innentemperatur(°C),Innenluftfeuchtigkeit(%),Außentemperatur(°C),Außenluftfeuchtigkeit(%),Relativer Luftdruck(hpa),Absoluter Luftdruck(hpa),Windgeschwindigkeit(km/h),Windböe(km/h),Windrichtung,Taupunkt(°C),Gefühlte Temperatur(°C),24-Stunden-Niederschlag(mm),WöchentlicherNiederschlag(mm),Monatlicher Niederschlag(mm),Jahr Niederschlag(mm),Gesamter Niederschlag(mm),Beleuchtung(fc),UV(uW/m2),UVI
1,01.05.2019  00:02:00, 5 M, 20.9,51, 12.2,74, 985.2, 988.3, 17.3, 20.9,315, 7.7, 7.1, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
2,01.05.2019  00:07:00, 5 M, 20.9,51, 12.2,74, 985.0, 988.1, 17.3, 22.0,315, 7.7, 7.1, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
3,01.05.2019  00:12:00, 5 M, 20.9,51, 12.2,73, 985.0, 988.1, 14.8, 19.4,0, 7.5, 7.9, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
4,01.05.2019  00:17:00, 5 M, 20.9,51, 12.1,73, 985.0, 988.1, 20.9, 25.6,338, 7.4, 6.0, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
5,01.05.2019  00:22:00, 5 M, 20.9,51, 12.1,73, 984.9, 988.0, 19.4, 24.5,315, 7.4, 6.4, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
6,01.05.2019  00:27:00, 5 M, 20.9,51, 12.1,73, 985.1, 988.2, 15.8, 20.9,0, 7.4, 7.4, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
7,01.05.2019  00:32:00, 5 M, 20.9,51, 12.0,74, 985.2, 988.3, 23.4, 29.5,0, 7.5, 5.3, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
8,01.05.2019  00:37:00, 5 M, 20.9,51, 12.0,74, 985.2, 988.3, 20.9, 24.5,338, 7.5, 5.9, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
9,01.05.2019  00:42:00, 5 M, 20.9,51, 11.9,74, 985.1, 988.2, 22.0, 28.1,0, 7.4, 5.5, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
10,01.05.2019  00:47:00, 5 M, 20.9,51, 11.9,75, 985.2, 988.3, 24.5, 30.6,315, 7.6, 5.0, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
11,01.05.2019  00:52:00, 5 M, 20.9,51, 11.8,75, 985.2, 988.3, 17.3, 20.9,0, 7.5, 6.6, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
12,01.05.2019  00:57:00, 5 M, 20.9,51, 11.7,75, 985.1, 988.2, 19.4, 24.5,338, 7.4, 5.9, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
13,01.05.2019  01:02:00, 5 M, 20.9,51, 11.6,76, 985.1, 988.2, 18.4, 22.0,338, 7.5, 6.0, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
14,01.05.2019  01:07:00, 5 M, 20.9,51, 11.6,75, 984.8, 987.9, 18.4, 23.4,315, 7.3, 6.0, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
15,01.05.2019  01:12:00, 5 M, 20.9,51, 11.5,75, 985.2, 988.3, 17.3, 23.4,315, 7.2, 6.2, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
16,01.05.2019  01:17:00, 5 M, 20.9,51, 11.4,75, 985.0, 988.1, 20.9, 24.5,0, 7.1, 5.1, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
17,01.05.2019  01:22:00, 5 M, 20.9,51, 11.3,75, 985.1, 988.2, 18.4, 23.4,0, 7.0, 5.7, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
18,01.05.2019  01:27:00, 5 M, 20.9,51, 11.3,75, 985.0, 988.1, 17.3, 23.4,0, 7.0, 6.0, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
19,01.05.2019  01:32:00, 5 M, 20.9,51, 11.3,74, 984.9, 988.0, 15.8, 18.4,315, 6.8, 6.4, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
20,01.05.2019  01:37:00, 5 M, 20.9,51, 11.2,74, 985.1, 988.2, 18.4, 24.5,338, 6.8, 5.5, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
21,01.05.2019  01:42:00, 5 M, 20.9,51, 11.2,74, 984.9, 988.0, 17.3, 20.9,0, 6.8, 5.8, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
22,01.05.2019  01:47:00, 5 M, 20.9,51, 11.2,73, 984.9, 988.0, 23.4, 30.6,315, 6.6, 4.3, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
23,01.05.2019  01:52:00, 5 M, 20.9,51, 11.2,73, 984.8, 987.9, 20.9, 25.6,315, 6.6, 4.9, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
24,01.05.2019  01:57:00, 5 M, 20.9,51, 11.1,73, 985.0, 988.1, 17.3, 19.4,0, 6.5, 5.7, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
25,01.05.2019  02:02:00, 5 M, 20.8,51, 11.0,73, 985.0, 988.1, 15.8, 20.9,45, 6.4, 6.1, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
26,01.05.2019  02:07:00, 5 M, 20.8,51, 11.0,73, 984.8, 987.9, 22.0, 25.6,315, 6.4, 4.3, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
27,01.05.2019  02:12:00, 5 M, 20.8,51, 10.9,73, 984.9, 988.0, 19.4, 23.4,315, 6.3, 4.8, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
28,01.05.2019  02:17:00, 5 M, 20.8,51, 10.8,73, 985.0, 988.1, 23.4, 29.5,315, 6.2, 3.7, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
29,01.05.2019  02:22:00, 5 M, 20.8,51, 10.8,73, 984.8, 987.9, 17.3, 22.0,0, 6.2, 5.3, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
30,01.05.2019  02:27:00, 5 M, 20.8,51, 10.8,72, 984.9, 988.0, 23.4, 27.0,315, 6.0, 3.7, 0.0, 17.1, 0.0, 369.6, 706.5, 0.0,0,0
31,01.05.2019  02:32:00, 5 M, 20.8,51, 10.7,72, 984.9, 988.0, 22.0, 27.0,270, 5.9, 3.9, 0.0, 17.1, 0.0, 369.6, 706

[weewx-user] Re: Weewx to mqtt

2020-04-10 Thread Wifi75
Yes now work, 
since I send the mqtt data to hassio I also had to create the sensors by 
hand. now everything works perfectly!

I have an ecowit GW1000 weather station with additional sensors WH51 WIFI 
Weather Sensor Series - Soil Moisture Sensor how should I search for them 
in  mqtt or 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6bc69a1e-ab4f-4930-9445-6293ef5b0444%40googlegroups.com.


Re: [weewx-user] wee_import of Weather Underground in Weewx 4.0

2020-04-10 Thread gjr80
Hallo Günther,

What should I watch out for when installing version 4?
>

Probably the biggest thing is that whilst in beta the WeeWX 4.0 install is 
available via setup.py only (no .rpm or .deb) so you need to manually 
download the package, install the pre-requisites and then install WeeWX. 
Also it is not advisable to install a 4.0 beta over an existing 3.x package 
(.deb or .rpm) due to the different locations used; a clean (WeeWX) install 
will be fine though. A WeeWX 4.0 setup.py install is a little more complex 
due to the support for python2 and python 3; choose either python 2 or 3 
and follow the install instructions in the 4.0.0 docs. Not the best (links 
probably won't work) but you can view the 4.0.0 setup.py install 
instructions here 
.
 
Once you have WeeWX 4.0.0 installed on your device you can browse the 4.0.0 
versions of the documents on your device (WeeWX website only shows the 
current release docs which at this time is still 3.9.2).
 

> I would like to try it on another computer, whether importing from WU 
> works with this version.
>

As long as you are using 4.0.0b13 or later the WU import should be fine. 
wee_import shipped with WeeWX 3.x will not work as it only supported the 
old (now retired) WU API. wee_import in WeeWX 4.0.0 supports the new WU 
API. Usual caveats apply to WU; at times their data is patchy so be wary of 
having wee_import derive the interval field from the WU data, best to use a 
fixed interval value in your import config file. I would also tend to avoid 
importing long periods of data in one go, I would do no more than one month 
at a time. Also work from oldest to newest data when importing.

Gary

-- 
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/7038258c-66a4-4671-b1a0-521ff390154e%40googlegroups.com.


[weewx-user] Re: Weewx2aprx does not show rainfall accumulation

2020-04-10 Thread gjr80
I have provided Bill with an updated service file for testing with 
weewx2aprx, if it works (or when it is fixed) I will post details here.

Gary

On Friday, 10 April 2020 03:30:46 UTC+10, Bill Arthur wrote:
>
> I am trying to set up a weather station in an area without internet, it 
> will transmit the data back through ham radio APRS. I've tried a number of 
> programs and extensions with varying degrees of poor reliability. I've 
> finally found a combination that works.
>
> My present setup is WS-2902 > GW1000 > weewx interceptor > weewx > 
> weewx2aprx > aprx > APRS > NWS.  
>
> Weewx2aprx was written by Hamid Misnan and is based on cwxn. It shares a 
> problem that cwxn had, in that it reports the hourly rain but not the 12 
> hour rain and rain since midnight.
> I worked with Hamid to fix a humidity issue, but he no longer uses weewx 
> and cannot help with the rainfall issue.
> Hamid's page is here, the files can be found there:   
> https://9m2tpt.blogspot.com/2015/09/getting-your-fine-offset-wx-on-rf-with.html
> gjr80 was kind to fix the problem with cwxn, any assistance is appreciated.
>

-- 
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/25b7efc6-d0d9-4ddb-befb-428cf96be600%40googlegroups.com.


[weewx-user] Re: Weahterdata from meteohub to weewx convert

2020-04-10 Thread gjr80
Hello,

Is this the csv file you referred to in your earlier post in another thread 
? If 
so wee_import is the tool to use but it cannot import the data in it's 
present format. You would need to merge the date (Datum) and time (Zeit) 
fields into a single field, eg 01.02.2020 and 00:00 would need to be 
01.02.2020 00:00. wee_import is fairly flexible in terms of the format of 
the single date-time field (any format, any order) but it must be a single 
field. Perhaps you can do this relatively easily using a spreadsheet or 
other editor? Another minor point but you will need to delete the second, 
third and fourth lines; wee_import requires the csv file consist of only a 
header line and lines of data to be imported. This is easily taken care of 
though.

Gary

On Friday, 10 April 2020 23:21:28 UTC+10, Meteo Oberwallis wrote:
>
> Hello. 
>
> I have from meteohub the .csv created. here is an example. 
>
> Is it possible to adapt this file so that it can be copied into the SQL table?
>
> Thx for Help
>
>
>
> Am Montag, 30. März 2020 12:50:27 UTC+2 schrieb Meteo Oberwallis:
>>
>> Hi Guys.
>> I used meteohub before using weewx. I have now collected weather data for 
>> years. Since the switch, however, I have now lacked this data. Meteohub 
>> saves the data in a .raw file. Does any of you have that too? Does anyone 
>> have a solution how to convert the data and read it into weewx afterwards? 
>> In the SQLite would be great.
>> I would appreciate your help. The Page Meteohub: 
>> https://wiki.meteohub.de/Main_Page 
>>
>> Thanks 
>> Stefan
>>
>>
>>

-- 
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/04cc71bc-07eb-465d-9bf9-fd6957e6a232%40googlegroups.com.


[weewx-user] Re: I need to change the url for my registered station website

2020-04-10 Thread gjr80
OK, could be something to do with the anti-spam measures in the website map 
scripts, there is some filtering of URLs to reduce spam. Matthew would 
know, my PERL is not that good.

Gary

On Saturday, 11 April 2020 03:16:06 UTC+10, beachboy wrote:
>
> Ok, I think I've got it. my urll did not include http://www. so weewx 
> didn't publish it. Looks like its working now. Thanks for the guidance. 
>
> On Wednesday, March 25, 2020 at 9:14:17 PM UTC-7, beachboy wrote:
>>
>> I had a couple of errors in the station_url in weewx.conf when I 
>> originally setup weewx. I was able to correct the first error (the 
>> directory at the web site) which may have registered a second station (see 
>> below). To correct the second error (the dot after www) I tried changing 
>> station_url again to the correct value and again had weewx reread conf 
>> (kill -HUP ). But this change does not appear on the weewx map.
>>
>> The set up process was not easy as my wmr200 was providing incorrect 
>> historical data and it took some effort to find and change the 
>> erase_archive parameter) And I tried to set up on both a mac and rpi before 
>> I got a valid installation so many methods were tried which also may have 
>> left some residue i.e. that may be where the duplicate stations came from.
>>
>> I am hoping for a less drastic solution than *Reinstall* so any 
>> suggestion are welcome.
>>
>> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c691d115-b66d-4feb-85b0-e6cc5c6b6f56%40googlegroups.com.


[weewx-user] Re: Weewx to mqtt

2020-04-10 Thread Greg from Oz
Is it working now?

On Thursday, 9 April 2020 19:12:59 UTC+10, Greg from Oz wrote:
>
> Is the mosquitto broker IP 192.168.1.60?
>
> If so why do you have this IP in the url 192.168.1.52 
> 
>  ? 
> It should be the IP of the mosquitto broker.
>
>
>
> On Thursday, 9 April 2020 17:53:15 UTC+10, Wifi75 wrote:
>>
>> hello, I have password on my broker and work with aother devices...
>>
>> se the logo of my broker... 192.168.1.60 it is my weewx server:
>>
>> below my configuration... it's ok?
>>
>> [[MQTT]]
>> server_url = mqtt://my_user:mypassw@192.168.1.52:1883 
>> 
>> topic = weewx
>> unit_system = METRIC
>> binding = loop
>>
>>
>>
>> ##
>>
>> #   This section configures the internal weewx engine.
>>
>> [Engine]
>> 
>> [[Services]]
>> # This section specifies the services that should be run. They are
>> # grouped by type, and the order of services within each group
>> # determines the order in which the services will be run.
>> prep_services = weewx.engine.StdTimeSynch
>> data_services = ,
>> process_services = weewx.engine.StdConvert, 
>> weewx.engine.StdCalibrate, weewx.engine.StdQC, 
>> weewx.wxservices.StdWXCalculate
>> archive_services = weewx.engine.StdArchive
>> restful_services = weewx.restx.StdStationRegistry, 
>> weewx.restx.StdWunderground, weewx.restx.StdPWSweather, 
>> weewx.restx.StdCWOP, weewx.restx.StdWOW, weewx.restx.StdAWEKAS, 
>> user.mqtt.MQTT
>> report_services = weewx.engine.StdPrint, weewx.engine.StdReport
>>
>>
>>
>> Il giorno mercoledì 8 aprile 2020 09:19:40 UTC+2, Wifi75 ha scritto:
>>>
>>> Hello I have installdet plugin for sent info to my broker server But I 
>>> have only one question :
>>> what should I write in the engine section? 
>>> it's not clear to me ...
>>>
>>>
>>>

-- 
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/f9b41d10-0d00-4c68-bcc9-c64b58f501f6%40googlegroups.com.


[weewx-user] Re: Datenbank zusammen legen.

2020-04-10 Thread gjr80
Hallo,

Ich entschuldige mich für das Google-Deutsche :)

Abhängig vom Format Ihrer WsWin-CSV-Datei sollte es möglich sein, Ihre 
CSV-Daten mit dem Dienstprogramm wee_import zu importieren. Für einen 
CSV-Import erfordert wee_import, dass die Datei eine Kopfzeile und dann 
einen Datensatz pro Zeile enthält. Es muss auch ein einzelnes Feld 
vorhanden sein, das Datum und Uhrzeit des Datensatzes enthält. Wenn Ihre 
Daten also separate Felder für Datum und Uhrzeit haben, müssen diese 
zusammengeführt werden. Außerdem kann wee_import jeweils nur aus einer 
einzelnen CSV-Datei importieren. Wenn Sie also mehrere CSV-Dateien haben, 
müssen Sie mehrere wee_import-Sitzungen ausführen oder die Dateien auf 
andere Weise zu einer zusammenführen.

Wenn Sie eine Ihrer WsWin-CSV-Dateien veröffentlichen möchten, schaue ich 
sie mir gerne an und prüfe, ob wee_import mit der Datei funktioniert und 
welche Einstellungen / Änderungen möglicherweise erforderlich sind.

In English:

My apologies for the Google-German :)

Depending on the format of your WsWin .csv file it should be possible to 
import your csv data using the wee_import utility. For a csv import 
wee_import requires the file contain a header line and then one record per 
line. There must also be a single field that contains the date and time of 
the record, so if your data has separate fields for date and time these 
would need to be merged. Also, wee_import can only import from a single csv 
file at a time, so if you have multiple csv files you would need to run 
multiple wee_import sessions or otherwise merge the files into one.

If you wish to post one of your WsWin csv files I am happy to look at it 
and see if wee_import will work with the file and what settings/changes may 
be required.

gruß,

Gary

On Friday, 10 April 2020 23:25:40 UTC+10, Meteo Oberwallis wrote:
>
> Hallo Günther.
>
> Darf ich dich fragen, ob du vorher auch mal WsWin benutzt hast? Ich habe 
> wetterdaten seit 2005, welche aber natürlich jetzt in weewx fehlen. Es 
> müsste doch möglich sein, die von WsWin erstellten Monatsdateien, also .csv 
> in die weewx Datenbank zu implementieren? Das wäre natürlich genial. 
> anonsten verliere ich die ganzen jahre.
>
> Gruss und danke für eure Hilfe
>
> Am Freitag, 10. April 2020 08:25:51 UTC+2 schrieb Günther Wrana:
>>
>> Hallo
>>
>> bei mir hat das dann funktioniert nach dem ich die alte Datenbank so wie 
>> oben beschrieben in eine .sql Datenbank umgewandelt habe.
>>
>> *sqlite3 db3.sdb*
>> sqlite> *.output db3.sql*
>> sqlite> *.dump archive*
>> sqlite> *.quit*
>>
>> und danach haben sich die beiden Datenbanken zusammmen legen lassen.
>>
>> Fehlermeldungen sind auch bei mir gekommen nur wenn man am Schluss die 
>> Datenbank mit dem checkt.
>>
>> *sqlite3 db3.sdb*
>> sqlite> *pragma integrity_check;*
>>
>> und es O.K ausgibt dann passt das.
>>
>> Grüße Günther 
>>
>>
>>
>> Am Donnerstag, 9. April 2020 11:14:57 UTC+2 schrieb Meteo Oberwallis:
>>>
>>> Hallo zusammen.
>>>
>>> Ich wollte ebenfalls meine beiden .sdb Datenbanken zusammenlegen. Sie 
>>> stammen beide aus weewx. Nun bekomme ich immer diese Fehlermeldung:
>>>
>>> root@raspberrypi:~# sqlite3 weewx.sdb_new_new
>>> SQLite version 3.16.2 2017-01-06 16:32:41
>>> Enter ".help" for usage hints.
>>> sqlite> .read weewx.sdb_new
>>> Error: cannot open "weewx.sdb_new"
>>> sqlite> .read /home/pi/Desktop/weewx.sdb_new
>>> Error: near line 1: near "SQLite": syntax error
>>> Error: near line 403: unrecognized token: " "
>>> Error: near line 5261: near "@n�": syntax error
>>> Error: near line 5337: unrecognized token: " "
>>> Error: near line 6332: unrecognized token: " "
>>> Error: near line 6793: unrecognized token: " "
>>> Error: near line 7575: near "@rH": syntax error
>>> Error: near line 7831: near "@n�": syntax error
>>> sqlite> 
>>>
>>> Hatte das jemand auch?
>>> Am Samstag, 4. Januar 2020 23:41:23 UTC+1 schrieb gjr80:

 Hallo Günther,

 Ihr Englisch ist wahrscheinlich besser als mein Deutsch, aber lassen 
 Sie uns sehen, wie wir gehen. Ich habe sowohl Englische als auch 
 Google-Deutsche Wörter eingefügt.

 Wenn ich das richtig verstehe, haben Sie zwei WeeWX SQLite-Datenbanken, 
 die Sie zusammenführen möchten. Leider gibt es im Utilities Guide nichts, 
 was Ihnen das leicht machen könnte. Dies ist ein paar Mal vorgekommen und 
 wenn Sie das Forum nach Beiträgen mit "merge sqlite datbase" durchsuchen, 
 werden Sie einige Beiträge finden, die Ihnen helfen werden. Ich würde 
 dieses versuchen (
 https://groups.google.com/d/msg/weewx-user/T2VuiIkcAEM/wZzemNzWknQJ) 
 und das ist das, was ich als Basis für das verwendet habe:

 1. Erstellen Sie eine Sicherungskopie Ihrer beiden Datenbanken

 2. Installieren Sie das Dienstprogramm sqlite3, falls es noch nicht 
 installiert ist:

 $ sudo apt-get install sqlite3

 3. Wählen Sie eine Ihrer Datenbanken als endgültige Datenbank aus und 
 benennen Sie die andere

[weewx-user] Weewx(Interceptor) does not refresh the weather data.

2020-04-10 Thread 'Joerg Strobel' via weewx-user
Hi,

After installation of weewx and intercepter on my RPI weewx get only one 
time the weather data from my froggit weather station (fineOffset).
So the folder /var/www/html/weewx/ has the last timestamp from yesterday. 
So i'm not sure, if the weather station does not sende data to the 
interceptor or where the bug is.

Can someone help me?

Thanks in advance!


Here are some logs.

*sudo tail -f /var/log/syslog:*

Apr 10 23:50:46 pi-ap weewx[625]: interceptor: MainThread: empty queue

Apr 10 23:50:56 pi-ap weewx[625]: interceptor: MainThread: empty queue

Apr 10 23:51:06 pi-ap weewx[625]: interceptor: MainThread: empty queue

Apr 10 23:51:16 pi-ap weewx[625]: interceptor: MainThread: empty queue

Apr 10 23:51:26 pi-ap weewx[625]: interceptor: MainThread: empty queue

Apr 10 23:51:35 pi-ap systemd[1]: Started Session c6 of user pi.

Apr 10 23:51:36 pi-ap weewx[625]: interceptor: MainThread: empty queue

Apr 10 23:51:38 pi-ap kernel: [39100.559341] [UFW BLOCK] IN=eth0 OUT= 
MAC=01:00:5e:00:00:fb:e4:e4:ab:65:4b:f4:08:00 SRC=192.168.123.57 
DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=45376 PROTO=2 

Apr 10 23:51:39 pi-ap kernel: [39101.353125] [UFW BLOCK] IN=eth0 OUT= 
MAC=01:00:5e:00:00:01:cc:ce:1e:a7:33:95:08:00 SRC=192.168.123.1 
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 

Apr 10 23:51:41 pi-ap kernel: [39103.820734] [UFW BLOCK] IN=eth0 OUT= 
MAC=01:00:5e:00:00:fb:e4:e4:ab:65:4b:f4:08:00 SRC=192.168.123.57 
DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=25508 PROTO=2 

Apr 10 23:51:46 pi-ap weewx[625]: interceptor: MainThread: empty queue

Apr 10 23:51:48 pi-ap weewx[625]: interceptor: ServerThread: sniff: 
timestamp=158608.64 pktlen=58 data=dc a6 32 08 9b 98 2c f4 32 4e 34 7c 
08 00 45 00 00 2c e8 92 00 00 80 06 40 d1 c0 a8 7c 0b 2f 64 a5 50 09 f7 00 
50 15 68 f4 b3 00 00 00 00 60 02 16 d0 5b 8b 00 00 02 04 05 b4

Apr 10 23:51:48 pi-ap weewx[625]: interceptor: ServerThread: sniff: skip 02 
04 05 b4

Apr 10 23:51:49 pi-ap weewx[625]: interceptor: ServerThread: sniff: 
timestamp=158609.19 pktlen=624 data=dc a6 32 08 9b 98 2c f4 32 4e 34 7c 
08 00 45 00 02 62 e8 93 00 00 80 06 3e 9a c0 a8 7c 0b 2f 64 a5 50 09 f7 00 
50 15 68 f4 b4 0a 71 0d 8b 50 18 16 d0 d6 5b 00 00 50 4f 53 54 20 2f 64 61 
74 61 2f 72 65 70 6f 72 74 2f 20 48 54 54 50 2f 31 2e 31 0d 0a 48 4f 53 54 
3a 20 72 74 70 64 61 74 65 2e 65 63 6f 77 69 74 74 2e 6e 65 74 0d 0a 43 6f 
6e 74 65 6e 74 2d 54 79 70 65 3a 20 61 70 70 6c 69 63 61 74 69 6f 6e 2f 78 
2d 77 77 77 2d 66 6f 72 6d 2d 75 72 6c 65 6e 63 6f 64 65 64 0d 0a 43 6f 6e 
74 65 6e 74 2d 4c 65 6e 67 74 68 3a 20 34 34 32 0d 0a 0d 0a 50 41 53 53 4b 
45 59 3d 37 41 30 36 44 34 33 32 45 38 41 37 43 36 33 33 43 41 32 41 43 35 
37 35 36 32 32 43 32 39 45 39 26 73 74 61 74 69 6f 6e 74 79 70 65 3d 45 61 
73 79 57 65 61 74 68 65 72 56 31 2e 34 2e 30 26 64 61 74 65 75 74 63 3d 32 
30 32 30 2d 30 34 2d 31 30 2b 32 31 3a 35 31 3a 34 38 26 74 65 6d 70 69 6e 
66 3d 37 30 2e 35 26 68 75 6d 69 64 69 74 79 69 6e 3d 34 35 26 62 61 72 6f 
6d 72 65 6c 69 6e 3d 32 39 2e 39 30 36 26 62 61 72 6f 6d 61 62 73 69 6e 3d 
32 38 2e 35 34 31 26 74 65 6d 70 66 3d 35 33 2e 38 26 68 75 6d 69 64 69 74 
79 3d 35 35 26 77 69 6e 64 64 69 72 3d 33 31 26 77 69 6e 64 73 70 65 65 64 
6d 70 68 3d 32 2e 32 26 77 69 6e 64 67 75 73 74 6d 70 68 3d 33 2e 34 26 6d 
61 78 64 61 69 6c 79 67 75 73 74 3d 39 2e 32 26 72 61 69 6e 72 61 74 65 69 
6e 3d 30 2e 30 30 30 26 65 76 65 6e 74 72 61 69 6e 69 6e 3d 30 2e 30 30 30 
26 68 6f 75 72 6c 79 72 61 69 6e 69 6e 3d 30 2e 30 30 30 26 64 61 69 6c 79 
72 61 69 6e 69 6e 3d 30 2e 30 30 30 26 77 65 65 6b 6c 79 72 61 69 6e 69 6e 
3d 30 2e 30 30 30 26 6d 6f 6e 74 68 6c 79 72 61 69 6e 69 6e 3d 30 2e 30 30 
30 26 74 6f 74 61 6c 72 61 69 6e 69 6e 3d 30 2e 31 36 39 26 73 6f 6c 61 72 
72 61 64 69 61 74 69 6f 6e 3d 30 2e 30 30 26 75 76 3d 30 26 77 68 36 35 62 
61 74 74 3d 30 26 66 72 65 71 3d 38 36 38 4d 26 6d 6f 64 65 6c 3d 57 53 32 
39 30 30 5f 56 32 2e 30 31 2e 30 38

Apr 10 23:51:49 pi-ap weewx[625]: interceptor: ServerThread: sniff: flush 
50 4f 53 54 3f

Apr 10 23:51:49 pi-ap weewx[625]: interceptor: ServerThread: sniff: start 
POST

Apr 10 23:51:49 pi-ap weewx[625]: interceptor: ServerThread: sniff: 
timestamp=158609.59 pktlen=54 data=dc a6 32 08 9b 98 2c f4 32 4e 34 7c 
08 00 45 00 00 28 e8 97 00 00 80 06 40 d0 c0 a8 7c 0b 2f 64 a5 50 09 f7 00 
50 15 68 f6 ee 0a 71 0e 5c 50 11 15 ff 59 01 00 00

Apr 10 23:51:49 pi-ap weewx[625]: interceptor: ServerThread: sniff: append 

Apr 10 23:51:51 pi-ap kernel: [39113.489675] [UFW BLOCK] IN=wlan0 OUT= 
MAC=dc:a6:32:08:9b:98:2c:f4:32:4e:34:7c:08:00 SRC=192.168.124.11 
DST=192.168.124.1 LEN=59 TOS=0x00 PREC=0x00 TTL=128 ID=59546 PROTO=UDP 
SPT=4096 DPT=53 LEN=39 

Apr 10 23:51:56 pi-ap weewx[625]: interceptor: MainThread: empty queue

Apr 10 23:52:06 pi-ap weewx[625]: interceptor: MainThread: empty queue

Apr 10 23:52:15 pi-ap kernel: [39137.927283] [UFW BLOCK] IN=eth0 OUT= 
MAC=01:00:5e:00:00:fb:e4:e4:ab:65:4b:f4:08:00 SRC

[weewx-user] I'm trying to install the weewx-forcast-master

2020-04-10 Thread David Barto
I’m getting the following:

Magrathea:weewx$ wee_extension --install ~/weewx-forecast-master.tgz 
Request to install '/Users/katherinebarto/weewx-forecast-master.tgz'
Extracting from tar archive /Users/katherinebarto/weewx-forecast-master.tgz
Traceback (most recent call last):
  File "/Users/Shared/weewx/bin/wee_extension", line 82, in 
main()
  File "/Users/Shared/weewx/bin/wee_extension", line 74, in main
ext.install_extension(options.install)
  File "/Users/Shared/weewx/bin/weecfg/extension.py", line 114, in 
install_extension
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 
'/Users/katherinebarto/weewx-forecast-master.tgz': no common path (the 
extension archive contains more than a single root directory)

I don’t have any extension_path configured in my weewx.conf file and a search 
of the discussion archive says that the above command should work.

What, again, am I doing incorrectly?

David

-- 
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/E4050DCE-5EBD-40AA-B4B6-4C99082F39E0%40kdbarto.org.


Re: [weewx-user] Re: Forecast 3.3.2

2020-04-10 Thread John Kline
Hi Phil,

I do have some good news.

I locally reverted my change to add the user-agent and duplicated the 403: 
Forbidden.  I then put back the change, and it again works.

As such, I’ll keep that change.  Thanks for making me aware of it.  I’m hoping 
your fresh install on another machine will work better for you tomorrow.

Cheers,
John

> On Apr 10, 2020, at 10:53 AM, Phil Owers  wrote:
> 
> 
> Just getting another SD Card loaded with everything fresh. Then tomorrow will 
> start again on a spare pi3. Will keep you posted.  Phil
> 
>> On Fri, 10 Apr 2020, 18:25 John Kline,  wrote:
>> This is telling me that your issues are not with WeeWX and the forecast 
>> plugin.
>> 
>> Do you have another machine you could try this on?  Running the simulator 
>> driver would be just fine for this excersize.
>> 
 On Apr 10, 2020, at 10:22 AM, Phil Owers  wrote:
 
>>> 
>>> Yes im running the latest buster on an RPI4.  Running host after running 
>>> PYTHONPATH just replied connection timed out , no servers could be reached. 
>>>  Yet my RPI3 works perfectly ok. 
>>> 
 On Fri, 10 Apr 2020, 17:55 John Kline,  wrote:
 My guess is that the Akamai servers that you are being directed to are 
 acting up when you are getting the denied messages.
 
 The temporary name resolution could also be Akamai dns problems.
 
 Immediately after you see the temporary failure, does running ‘host 
 datapoint.metoffice.gov.uk‘ resolve?
 
 Just grasping at straws for these remaining questions:
 What raspberry pi, what version of Raspbian, what version of Py3?  (I’m 
 running an up to date RPi4 with Buster 4.19.97-v7l+ #1294 SMP Thu Jan 30 
 13:21:14 GMT 2020 armv7l GNU/Linux and Python 3.7.3 on my end to try this 
 and all is working fine.)
 
>> On Apr 10, 2020, at 9:28 AM, Phil Owers  wrote:
>> 
> 
> At the cursor
> pi@raspberrypi:/home/weewx $ PYTHONPATH=/home/weewx/bin python3 
> /home/weewx/bin/user/forecast.py --method UKMO --action download --loc 
> 354731 --api-key ----f051
> None
> pi@raspberrypi:/home/weewx $ 
> 
> In the log
> Apr 10 17:17:12 raspberrypi forecast[3785] INFO __main__: MainThread: 
> UKMO: download forecast from 
> 'http://datapoint.metoffice.gov.uk/public/data/val/wxfcs/all/json/354731?res=3hourly&key=f051'
> Apr 10 17:17:32 raspberrypi forecast[3785] ERROR __main__: MainThread: 
> UKMO: failed attempt 1 to download forecast:  Temporary failure in name resolution>
> Apr 10 17:17:52 raspberrypi forecast[3785] ERROR __main__: MainThread: 
> UKMO: failed attempt 2 to download forecast:  Temporary failure in name resolution>
> Apr 10 17:18:01 raspberrypi kernel: [23984.559200] brcmfmac: 
> brcmf_run_escan: error (-110)
> Apr 10 17:18:01 raspberrypi kernel: [23984.559217] brcmfmac: 
> brcmf_cfg80211_scan: scan error (-110)
> Apr 10 17:18:12 raspberrypi forecast[3785] ERROR __main__: MainThread: 
> UKMO: failed attempt 3 to download forecast:  Temporary failure in name resolution>
> Apr 10 17:18:12 raspberrypi forecast[3785] ERROR __main__: MainThread: 
> UKMO: failed to download forecast
> 
> Phil
>> On Wednesday, April 8, 2020 at 3:11:31 PM UTC+1, Phil Owers wrote:
>> Just downloaded the forecast extension which was 3.3.2.which I think is 
>> the latest on to a python 3 only machine (weewx 4.0.0b18) and it fails 
>> forecast.py Line 567 except OSError , e; with an underscore under the ,
>> Just wondered if anybody else has had this.
>> Cheers Phil
> 
> -- 
> 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/21c677cf-99b6-412d-8085-24dfea8e5b7c%40googlegroups.com.
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to weewx-user+unsubscr...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/758FAA47-402E-467A-BB66-681A4E3E8C28%40johnkline.com.
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to weewx-user+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/CALTQ7pP-Zz4b8%2BOWAtawr4%2BEvP%3DKjk-hvZq0LJwmriP36aJd-g%40mail.gmail.com.
>> 
>> -- 
>> You received this message because you are subscribed to the Google G

Re: [weewx-user] Future date/times into database resulting in loss of data

2020-04-10 Thread Ken Waters
Hi Tom,

Thanks for responding.

Problem #2 resolved, that was easy.  :-)

For Problem #1, I don't have ferrite coils available but will look for them
and try this out.  I note the cable is just simple unshielded telephone
phone cable. Perhaps I could try something more shielded, if something like
that exists for phone cables.

Ken

On Thu, Apr 9, 2020 at 5:48 PM Thomas Keffer  wrote:

> Hi, Ken
>
> Problem #1 is almost surely a hardware problem. Have you put ferrite coils
> around the cable from your logger to the computer? A UPS also helps. If you
> are still getting random corruption in the logger memory, then the logger
> may be defective.
>
> Problem #2: a graphic is regenerated only as often as its aggregation
> interval. For example, if a month plot uses a 3 hour aggregation interval,
> then it will be regenerated only after it is 3 hours old. To force
> regeneration, delete the graphic.
>
> -tk
>
> On Thu, Apr 9, 2020 at 11:05 AM Ken Waters  wrote:
>
>> Hello,
>>
>> Sorry if this seems long but I tried to put everything in here that might
>> help explain the situation.
>>
>> Here is my setup:
>>   Weewx version: 3.9.2
>>   Weather station: Davis Vantage Pro 2 connected thru DB9 serial port
>>   Hardware: HP Pro 6000 SFF dual Pentium RAM: 4 GB, WD 1 TB drive
>> (currently only 2% usage)
>>   O/S: Ubuntu 18.04.4 LTS
>>   Website: http://satwatcher.us/satwatcher.us/wxstation/
>>
>> I've been running WeeWx for about 9-10 years and previously used WxView.
>>
>> Here is the problem:
>>
>> Periodically and randomly the SQLite database gets corrupted with the
>> most recent update showing a future day/time. There seems to be no obvious
>> trigger that causes this and it's been happening to me for several years
>> including with other hardware setups. When this happens it basically
>> "locks" up the database so that current observations can no longer be
>> stored and results in a loss of data after the database corruption. In the
>> past I have had to resort to:
>>
>>   a) stopping the service
>>   b) clearing the memory (sudo /usr/share/weewx/wee_device -y
>> --clear-memory)
>>   c) renaming the .sdb
>>   d) restarting the service
>>
>> in effect, starting with a new database.  This has been happening every
>> 2-4 weeks randomly and not as a result of anything done by me to the server.
>>
>> Here is a sample snippet from syslog that shows the issue:
>>   Apr  9 07:38:15 WeewxWeatherServer weewx[28253]: vantage: Getting
>> archive packets since 2020-04-09 07:37:00 MST (1586443020)
>>   Apr  9 07:38:15 WeewxWeatherServer weewx[28253]: vantage: Gentle wake
>> up of console successful
>>   Apr  9 07:38:15 WeewxWeatherServer weewx[28253]: vantage: Retrieving 1
>> page(s); starting index= 0
>>   Apr  9 07:38:16 WeewxWeatherServer weewx[28253]: manager: Added record
>> 2020-04-22 23:06:00 MST (1587621960) to database 'weewx.sdb'
>>   Apr  9 07:38:16 WeewxWeatherServer weewx[28253]: manager: Added record
>> 2020-04-22 23:06:00 MST (1587621960) to daily summary in 'weewx.sdb'
>>   Apr  9 07:38:16 WeewxWeatherServer weewx[28253]: *vantage: DMPAFT
>> complete: page timestamp 2020-04-07 12:59:00 MST (1586289540) less than
>> final timestamp 2020-04-22 23:06:00 MST (1587621960)*
>>   Apr  9 07:38:16 WeewxWeatherServer weewx[28253]: vantage: Catch up
>> complete.
>>   Apr  9 07:38:16 WeewxWeatherServer weewx[28253]: vantage: Requesting
>> 200 LOOP packets.
>>   Apr  9 07:38:16 WeewxWeatherServer weewx[28253]: reportengine: Running
>> reports for latest time in the database.
>>   Apr  9 07:38:16 WeewxWeatherServer weewx[28253]: reportengine: Running
>> report 'SeasonsReport'
>>   Apr  9 07:38:16 WeewxWeatherServer weewx[28253]: reportengine: Found
>> configuration file /etc/weewx/skins/Seasons/skin.conf for report
>> 'SeasonsReport'
>>
>> Here is output captured this morning from a sqlite3 select command that
>> shows the erroneous timestamp in the database:
>>
>>   $ sqlite3 /var/lib/weewx/weewx.sdb "select
>> datetime(dateTime,'unixepoch','localtime') from archive where
>> dateTime>155;"
>>   2020-04-09 07:30:00
>>   2020-04-09 07:31:00
>>   2020-04-09 07:32:00
>>   2020-04-09 07:33:00
>>   2020-04-09 07:34:00
>>   2020-04-09 07:35:00
>>   2020-04-09 07:36:00
>>   2020-04-09 07:37:00
>>   *2020-04-22 23:06:00* <<< erroneous future entry
>>
>> These date/times are local MST (Z-7) and the problem actually occurred at
>> 2306 MST last night resulting in loss of data for about 8 hours.  It seems
>> as if WeeWx is skipping recording the observation because it thinks this is
>> an old observation due to the last entry being "newer".
>>
>> Problem #2:
>> In addition, after stopping, clearing, removing the .sdb, and restarting
>> I now see that the graphics being produced are not current and are
>> time-stamped 4/22/2029 23:06 although the data on the left-side of the page
>> at http://satwatcher.us/satwatcher.us/wxstation/ are current.  Why are
>> the graphics still keying off the erroneous time in the future?
>>
>> T

Re: [weewx-user] wee_import of Weather Underground in Weewx 4.0

2020-04-10 Thread Günther Wrana
Hi

What should I watch out for when installing version 4?
>
> I would like to try it on another computer, whether importing from WU 
works with this version.

Günther

-- 
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/f2ad68f2-39f0-4a75-a1ab-6ae1cb95d5c9%40googlegroups.com.


[weewx-user] Re: Datenbank zusammen legen.

2020-04-10 Thread Günther Wrana
Hallo Meteo

ich habe das Problem auch meine Wetterdaten von 2014 bis zum Mai 2019 als 
.csv Dateien.
Mit dem weewx_import funktioniert das irgend wie. Ich Versuche das auch 
gerade aber angeblich soll das dann bei weewx 4.0 dann einfacher oder 
überhaupt funktionieren.

Ich bin auch erst seit voriges Jahr im Mai mit dem Programm so ein wenig 
vertraut.
Aber es sind hier alle sehr hilfsbereit bei Fragen.
Nur ist es besser wenn du in Englisch die Fragen stellst dann bekommst du 
schneller Antworten.

Ich mache das immer mit dem Google Übersetzer denn in Englisch bin ich 
nicht so versiert.

Aber lies dir die Dokumentation von weewx durch dort findest du oft Hilfen 
bei manchen Rätseln dieses Programmes.

Sonst funktioniert es sehr gut und ich bin zufrieden den nun kann ich meine 
Wetterdaten von allen meinen Geräten im Netzwerk zuhause und im Internet 
ansehen.

Grüße Günther  

Am Freitag, 10. April 2020 15:25:40 UTC+2 schrieb Meteo Oberwallis:
>
> Hallo Günther.
>
> Darf ich dich fragen, ob du vorher auch mal WsWin benutzt hast? Ich habe 
> wetterdaten seit 2005, welche aber natürlich jetzt in weewx fehlen. Es 
> müsste doch möglich sein, die von WsWin erstellten Monatsdateien, also .csv 
> in die weewx Datenbank zu implementieren? Das wäre natürlich genial. 
> anonsten verliere ich die ganzen jahre.
>
> Gruss und danke für eure Hilfe
>
> Am Freitag, 10. April 2020 08:25:51 UTC+2 schrieb Günther Wrana:
>>
>> Hallo
>>
>> bei mir hat das dann funktioniert nach dem ich die alte Datenbank so wie 
>> oben beschrieben in eine .sql Datenbank umgewandelt habe.
>>
>> *sqlite3 db3.sdb*
>> sqlite> *.output db3.sql*
>> sqlite> *.dump archive*
>> sqlite> *.quit*
>>
>> und danach haben sich die beiden Datenbanken zusammmen legen lassen.
>>
>> Fehlermeldungen sind auch bei mir gekommen nur wenn man am Schluss die 
>> Datenbank mit dem checkt.
>>
>> *sqlite3 db3.sdb*
>> sqlite> *pragma integrity_check;*
>>
>> und es O.K ausgibt dann passt das.
>>
>> Grüße Günther 
>>
>>
>>
>> Am Donnerstag, 9. April 2020 11:14:57 UTC+2 schrieb Meteo Oberwallis:
>>>
>>> Hallo zusammen.
>>>
>>> Ich wollte ebenfalls meine beiden .sdb Datenbanken zusammenlegen. Sie 
>>> stammen beide aus weewx. Nun bekomme ich immer diese Fehlermeldung:
>>>
>>> root@raspberrypi:~# sqlite3 weewx.sdb_new_new
>>> SQLite version 3.16.2 2017-01-06 16:32:41
>>> Enter ".help" for usage hints.
>>> sqlite> .read weewx.sdb_new
>>> Error: cannot open "weewx.sdb_new"
>>> sqlite> .read /home/pi/Desktop/weewx.sdb_new
>>> Error: near line 1: near "SQLite": syntax error
>>> Error: near line 403: unrecognized token: " "
>>> Error: near line 5261: near "@n�": syntax error
>>> Error: near line 5337: unrecognized token: " "
>>> Error: near line 6332: unrecognized token: " "
>>> Error: near line 6793: unrecognized token: " "
>>> Error: near line 7575: near "@rH": syntax error
>>> Error: near line 7831: near "@n�": syntax error
>>> sqlite> 
>>>
>>> Hatte das jemand auch?
>>> Am Samstag, 4. Januar 2020 23:41:23 UTC+1 schrieb gjr80:

 Hallo Günther,

 Ihr Englisch ist wahrscheinlich besser als mein Deutsch, aber lassen 
 Sie uns sehen, wie wir gehen. Ich habe sowohl Englische als auch 
 Google-Deutsche Wörter eingefügt.

 Wenn ich das richtig verstehe, haben Sie zwei WeeWX SQLite-Datenbanken, 
 die Sie zusammenführen möchten. Leider gibt es im Utilities Guide nichts, 
 was Ihnen das leicht machen könnte. Dies ist ein paar Mal vorgekommen und 
 wenn Sie das Forum nach Beiträgen mit "merge sqlite datbase" durchsuchen, 
 werden Sie einige Beiträge finden, die Ihnen helfen werden. Ich würde 
 dieses versuchen (
 https://groups.google.com/d/msg/weewx-user/T2VuiIkcAEM/wZzemNzWknQJ) 
 und das ist das, was ich als Basis für das verwendet habe:

 1. Erstellen Sie eine Sicherungskopie Ihrer beiden Datenbanken

 2. Installieren Sie das Dienstprogramm sqlite3, falls es noch nicht 
 installiert ist:

 $ sudo apt-get install sqlite3

 3. Wählen Sie eine Ihrer Datenbanken als endgültige Datenbank aus und 
 benennen Sie die andere in db1.sdb um. Sie sollten jetzt zwei Datenbanken 
 haben, eine mit dem Namen weewx.sdb und eine andere mit dem Namen db1.sdb. 
 Um die Dinge später zu vereinfachen, stellen Sie sicher, dass sich 
 weewx.sdb in dem Verzeichnis befindet, in dem Sie Ihre WeeWX-Datenbank 
 dauerhaft speichern möchten (die Standardverzeichnisse sind 
 /home/weewx/archive für eine setup.py-Installation oder /var/lib/weewx für 
 alle andere installiert). Ich werde /home/weewx/archive in dieser 
 Anleitung 
 verwenden

 4. Kopieren Sie die Datenbank db1.sdb in eine Datei:

 $ sqlite3 /path/to/db1.sdb
 sqlite> .output /var/tmp/db1.dump
 sqlite> .dump
 sqlite> .quit

 5. Importieren Sie nun die gedumpten Daten in die endgültige Datenbank 
 weewx.sdb:

 $ sqlite3 /home/weewx/archive/weewx.sdb
 sqlite> .read /var/tmp/

Re: [weewx-user] Re: Forecast 3.3.2

2020-04-10 Thread Phil Owers
Just getting another SD Card loaded with everything fresh. Then tomorrow
will start again on a spare pi3. Will keep you posted.  Phil

On Fri, 10 Apr 2020, 18:25 John Kline,  wrote:

> This is telling me that your issues are not with WeeWX and the forecast
> plugin.
>
> Do you have another machine you could try this on?  Running the simulator
> driver would be just fine for this excersize.
>
> On Apr 10, 2020, at 10:22 AM, Phil Owers  wrote:
>
> 
> Yes im running the latest buster on an RPI4.  Running host after running
> PYTHONPATH just replied connection timed out , no servers could be
> reached.  Yet my RPI3 works perfectly ok.
>
> On Fri, 10 Apr 2020, 17:55 John Kline,  wrote:
>
>> My guess is that the Akamai servers that you are being directed to are
>> acting up when you are getting the denied messages.
>>
>> The temporary name resolution could also be Akamai dns problems.
>>
>> Immediately after you see the temporary failure, does running ‘host
>> datapoint.metoffice.gov.uk‘ resolve?
>>
>> Just grasping at straws for these remaining questions:
>> What raspberry pi, what version of Raspbian, what version of Py3?  (I’m
>> running an up to date RPi4 with Buster 4.19.97-v7l+ #1294 SMP Thu Jan 30
>> 13:21:14 GMT 2020 armv7l GNU/Linux and Python 3.7.3 on my end to try this
>> and all is working fine.)
>>
>> On Apr 10, 2020, at 9:28 AM, Phil Owers  wrote:
>>
>> 
>> At the cursor
>> pi@raspberrypi:/home/weewx $ PYTHONPATH=/home/weewx/bin python3
>> /home/weewx/bin/user/forecast.py --method UKMO --action download --loc
>> 354731 --api-key ----f051
>> None
>> pi@raspberrypi:/home/weewx $
>>
>> In the log
>> Apr 10 17:17:12 raspberrypi forecast[3785] INFO __main__: MainThread:
>> UKMO: download forecast from '
>> http://datapoint.metoffice.gov.uk/public/data/val/wxfcs/all/json/354731?res=3hourly&key=f051
>> '
>> Apr 10 17:17:32 raspberrypi forecast[3785] ERROR __main__: MainThread:
>> UKMO: failed attempt 1 to download forecast: > Temporary failure in name resolution>
>> Apr 10 17:17:52 raspberrypi forecast[3785] ERROR __main__: MainThread:
>> UKMO: failed attempt 2 to download forecast: > Temporary failure in name resolution>
>> Apr 10 17:18:01 raspberrypi kernel: [23984.559200] brcmfmac:
>> brcmf_run_escan: error (-110)
>> Apr 10 17:18:01 raspberrypi kernel: [23984.559217] brcmfmac:
>> brcmf_cfg80211_scan: scan error (-110)
>> Apr 10 17:18:12 raspberrypi forecast[3785] ERROR __main__: MainThread:
>> UKMO: failed attempt 3 to download forecast: > Temporary failure in name resolution>
>> Apr 10 17:18:12 raspberrypi forecast[3785] ERROR __main__: MainThread:
>> UKMO: failed to download forecast
>>
>> Phil
>> On Wednesday, April 8, 2020 at 3:11:31 PM UTC+1, Phil Owers wrote:
>>>
>>> Just downloaded the forecast extension which was 3.3.2.which I think is
>>> the latest on to a python 3 only machine (weewx 4.0.0b18) and it fails
>>> forecast.py Line 567 except OSError , e; with an underscore under the ,
>>> Just wondered if anybody else has had this.
>>> Cheers Phil
>>>
>> --
>> 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/21c677cf-99b6-412d-8085-24dfea8e5b7c%40googlegroups.com
>> 
>> .
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/758FAA47-402E-467A-BB66-681A4E3E8C28%40johnkline.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CALTQ7pP-Zz4b8%2BOWAtawr4%2BEvP%3DKjk-hvZq0LJwmriP36aJd-g%40mail.gmail.com
> 
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.c

Re: [weewx-user] Re: Forecast 3.3.2

2020-04-10 Thread John Kline
This is telling me that your issues are not with WeeWX and the forecast plugin.

Do you have another machine you could try this on?  Running the simulator 
driver would be just fine for this excersize.

> On Apr 10, 2020, at 10:22 AM, Phil Owers  wrote:
> 
> 
> Yes im running the latest buster on an RPI4.  Running host after running 
> PYTHONPATH just replied connection timed out , no servers could be reached.  
> Yet my RPI3 works perfectly ok. 
> 
>> On Fri, 10 Apr 2020, 17:55 John Kline,  wrote:
>> My guess is that the Akamai servers that you are being directed to are 
>> acting up when you are getting the denied messages.
>> 
>> The temporary name resolution could also be Akamai dns problems.
>> 
>> Immediately after you see the temporary failure, does running ‘host 
>> datapoint.metoffice.gov.uk‘ resolve?
>> 
>> Just grasping at straws for these remaining questions:
>> What raspberry pi, what version of Raspbian, what version of Py3?  (I’m 
>> running an up to date RPi4 with Buster 4.19.97-v7l+ #1294 SMP Thu Jan 30 
>> 13:21:14 GMT 2020 armv7l GNU/Linux and Python 3.7.3 on my end to try this 
>> and all is working fine.)
>> 
 On Apr 10, 2020, at 9:28 AM, Phil Owers  wrote:
 
>>> 
>>> At the cursor
>>> pi@raspberrypi:/home/weewx $ PYTHONPATH=/home/weewx/bin python3 
>>> /home/weewx/bin/user/forecast.py --method UKMO --action download --loc 
>>> 354731 --api-key ----f051
>>> None
>>> pi@raspberrypi:/home/weewx $ 
>>> 
>>> In the log
>>> Apr 10 17:17:12 raspberrypi forecast[3785] INFO __main__: MainThread: UKMO: 
>>> download forecast from 
>>> 'http://datapoint.metoffice.gov.uk/public/data/val/wxfcs/all/json/354731?res=3hourly&key=f051'
>>> Apr 10 17:17:32 raspberrypi forecast[3785] ERROR __main__: MainThread: 
>>> UKMO: failed attempt 1 to download forecast: >> Temporary failure in name resolution>
>>> Apr 10 17:17:52 raspberrypi forecast[3785] ERROR __main__: MainThread: 
>>> UKMO: failed attempt 2 to download forecast: >> Temporary failure in name resolution>
>>> Apr 10 17:18:01 raspberrypi kernel: [23984.559200] brcmfmac: 
>>> brcmf_run_escan: error (-110)
>>> Apr 10 17:18:01 raspberrypi kernel: [23984.559217] brcmfmac: 
>>> brcmf_cfg80211_scan: scan error (-110)
>>> Apr 10 17:18:12 raspberrypi forecast[3785] ERROR __main__: MainThread: 
>>> UKMO: failed attempt 3 to download forecast: >> Temporary failure in name resolution>
>>> Apr 10 17:18:12 raspberrypi forecast[3785] ERROR __main__: MainThread: 
>>> UKMO: failed to download forecast
>>> 
>>> Phil
 On Wednesday, April 8, 2020 at 3:11:31 PM UTC+1, Phil Owers wrote:
 Just downloaded the forecast extension which was 3.3.2.which I think is 
 the latest on to a python 3 only machine (weewx 4.0.0b18) and it fails 
 forecast.py Line 567 except OSError , e; with an underscore under the ,
 Just wondered if anybody else has had this.
 Cheers Phil
>>> 
>>> -- 
>>> 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/21c677cf-99b6-412d-8085-24dfea8e5b7c%40googlegroups.com.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/758FAA47-402E-467A-BB66-681A4E3E8C28%40johnkline.com.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/CALTQ7pP-Zz4b8%2BOWAtawr4%2BEvP%3DKjk-hvZq0LJwmriP36aJd-g%40mail.gmail.com.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/BD112A63-F30F-4147-9037-E1B8AD7E9CE7%40johnkline.com.


Re: [weewx-user] Re: Forecast 3.3.2

2020-04-10 Thread Phil Owers
Yes im running the latest buster on an RPI4.  Running host after running
PYTHONPATH just replied connection timed out , no servers could be
reached.  Yet my RPI3 works perfectly ok.

On Fri, 10 Apr 2020, 17:55 John Kline,  wrote:

> My guess is that the Akamai servers that you are being directed to are
> acting up when you are getting the denied messages.
>
> The temporary name resolution could also be Akamai dns problems.
>
> Immediately after you see the temporary failure, does running ‘host
> datapoint.metoffice.gov.uk‘ resolve?
>
> Just grasping at straws for these remaining questions:
> What raspberry pi, what version of Raspbian, what version of Py3?  (I’m
> running an up to date RPi4 with Buster 4.19.97-v7l+ #1294 SMP Thu Jan 30
> 13:21:14 GMT 2020 armv7l GNU/Linux and Python 3.7.3 on my end to try this
> and all is working fine.)
>
> On Apr 10, 2020, at 9:28 AM, Phil Owers  wrote:
>
> 
> At the cursor
> pi@raspberrypi:/home/weewx $ PYTHONPATH=/home/weewx/bin python3
> /home/weewx/bin/user/forecast.py --method UKMO --action download --loc
> 354731 --api-key ----f051
> None
> pi@raspberrypi:/home/weewx $
>
> In the log
> Apr 10 17:17:12 raspberrypi forecast[3785] INFO __main__: MainThread:
> UKMO: download forecast from '
> http://datapoint.metoffice.gov.uk/public/data/val/wxfcs/all/json/354731?res=3hourly&key=f051
> '
> Apr 10 17:17:32 raspberrypi forecast[3785] ERROR __main__: MainThread:
> UKMO: failed attempt 1 to download forecast:  Temporary failure in name resolution>
> Apr 10 17:17:52 raspberrypi forecast[3785] ERROR __main__: MainThread:
> UKMO: failed attempt 2 to download forecast:  Temporary failure in name resolution>
> Apr 10 17:18:01 raspberrypi kernel: [23984.559200] brcmfmac:
> brcmf_run_escan: error (-110)
> Apr 10 17:18:01 raspberrypi kernel: [23984.559217] brcmfmac:
> brcmf_cfg80211_scan: scan error (-110)
> Apr 10 17:18:12 raspberrypi forecast[3785] ERROR __main__: MainThread:
> UKMO: failed attempt 3 to download forecast:  Temporary failure in name resolution>
> Apr 10 17:18:12 raspberrypi forecast[3785] ERROR __main__: MainThread:
> UKMO: failed to download forecast
>
> Phil
> On Wednesday, April 8, 2020 at 3:11:31 PM UTC+1, Phil Owers wrote:
>>
>> Just downloaded the forecast extension which was 3.3.2.which I think is
>> the latest on to a python 3 only machine (weewx 4.0.0b18) and it fails
>> forecast.py Line 567 except OSError , e; with an underscore under the ,
>> Just wondered if anybody else has had this.
>> Cheers Phil
>>
> --
> 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/21c677cf-99b6-412d-8085-24dfea8e5b7c%40googlegroups.com
> 
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/758FAA47-402E-467A-BB66-681A4E3E8C28%40johnkline.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CALTQ7pP-Zz4b8%2BOWAtawr4%2BEvP%3DKjk-hvZq0LJwmriP36aJd-g%40mail.gmail.com.


[weewx-user] Re: I need to change the url for my registered station website

2020-04-10 Thread beachboy
Ok, I think I've got it. my urll did not include http://www. so weewx 
didn't publish it. Looks like its working now. Thanks for the guidance. 

On Wednesday, March 25, 2020 at 9:14:17 PM UTC-7, beachboy wrote:
>
> I had a couple of errors in the station_url in weewx.conf when I 
> originally setup weewx. I was able to correct the first error (the 
> directory at the web site) which may have registered a second station (see 
> below). To correct the second error (the dot after www) I tried changing 
> station_url again to the correct value and again had weewx reread conf 
> (kill -HUP ). But this change does not appear on the weewx map.
>
> The set up process was not easy as my wmr200 was providing incorrect 
> historical data and it took some effort to find and change the 
> erase_archive parameter) And I tried to set up on both a mac and rpi before 
> I got a valid installation so many methods were tried which also may have 
> left some residue i.e. that may be where the duplicate stations came from.
>
> I am hoping for a less drastic solution than *Reinstall* so any suggestion 
> are welcome.
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/635a02bd-478d-4704-801e-1d45c68be99d%40googlegroups.com.


Re: [weewx-user] Re: Forecast 3.3.2

2020-04-10 Thread John Kline
My guess is that the Akamai servers that you are being directed to are acting 
up when you are getting the denied messages.

The temporary name resolution could also be Akamai dns problems.

Immediately after you see the temporary failure, does running ‘host 
datapoint.metoffice.gov.uk‘ resolve?

Just grasping at straws for these remaining questions:
What raspberry pi, what version of Raspbian, what version of Py3?  (I’m running 
an up to date RPi4 with Buster 4.19.97-v7l+ #1294 SMP Thu Jan 30 13:21:14 GMT 
2020 armv7l GNU/Linux and Python 3.7.3 on my end to try this and all is working 
fine.)

>> On Apr 10, 2020, at 9:28 AM, Phil Owers  wrote:
> 
> At the cursor
> pi@raspberrypi:/home/weewx $ PYTHONPATH=/home/weewx/bin python3 
> /home/weewx/bin/user/forecast.py --method UKMO --action download --loc 354731 
> --api-key ----f051
> None
> pi@raspberrypi:/home/weewx $ 
> 
> In the log
> Apr 10 17:17:12 raspberrypi forecast[3785] INFO __main__: MainThread: UKMO: 
> download forecast from 
> 'http://datapoint.metoffice.gov.uk/public/data/val/wxfcs/all/json/354731?res=3hourly&key=f051'
> Apr 10 17:17:32 raspberrypi forecast[3785] ERROR __main__: MainThread: UKMO: 
> failed attempt 1 to download forecast:  failure in name resolution>
> Apr 10 17:17:52 raspberrypi forecast[3785] ERROR __main__: MainThread: UKMO: 
> failed attempt 2 to download forecast:  failure in name resolution>
> Apr 10 17:18:01 raspberrypi kernel: [23984.559200] brcmfmac: brcmf_run_escan: 
> error (-110)
> Apr 10 17:18:01 raspberrypi kernel: [23984.559217] brcmfmac: 
> brcmf_cfg80211_scan: scan error (-110)
> Apr 10 17:18:12 raspberrypi forecast[3785] ERROR __main__: MainThread: UKMO: 
> failed attempt 3 to download forecast:  failure in name resolution>
> Apr 10 17:18:12 raspberrypi forecast[3785] ERROR __main__: MainThread: UKMO: 
> failed to download forecast
> 
> Phil
>> On Wednesday, April 8, 2020 at 3:11:31 PM UTC+1, Phil Owers wrote:
>> Just downloaded the forecast extension which was 3.3.2.which I think is the 
>> latest on to a python 3 only machine (weewx 4.0.0b18) and it fails 
>> forecast.py Line 567 except OSError , e; with an underscore under the ,
>> Just wondered if anybody else has had this.
>> Cheers Phil
> 
> -- 
> 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/21c677cf-99b6-412d-8085-24dfea8e5b7c%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/758FAA47-402E-467A-BB66-681A4E3E8C28%40johnkline.com.


[weewx-user] Re: Forecast 3.3.2

2020-04-10 Thread Phil Owers
At the cursor
pi@raspberrypi:/home/weewx $ PYTHONPATH=/home/weewx/bin python3 
/home/weewx/bin/user/forecast.py --method UKMO --action download --loc 
354731 --api-key ----f051
None
pi@raspberrypi:/home/weewx $ 

In the log
Apr 10 17:17:12 raspberrypi forecast[3785] INFO __main__: MainThread: UKMO: 
download forecast from 
'http://datapoint.metoffice.gov.uk/public/data/val/wxfcs/all/json/354731?res=3hourly&key=f051'
Apr 10 17:17:32 raspberrypi forecast[3785] ERROR __main__: MainThread: 
UKMO: failed attempt 1 to download forecast: 
Apr 10 17:17:52 raspberrypi forecast[3785] ERROR __main__: MainThread: 
UKMO: failed attempt 2 to download forecast: 
Apr 10 17:18:01 raspberrypi kernel: [23984.559200] brcmfmac: 
brcmf_run_escan: error (-110)
Apr 10 17:18:01 raspberrypi kernel: [23984.559217] brcmfmac: 
brcmf_cfg80211_scan: scan error (-110)
Apr 10 17:18:12 raspberrypi forecast[3785] ERROR __main__: MainThread: 
UKMO: failed attempt 3 to download forecast: 
Apr 10 17:18:12 raspberrypi forecast[3785] ERROR __main__: MainThread: 
UKMO: failed to download forecast

Phil
On Wednesday, April 8, 2020 at 3:11:31 PM UTC+1, Phil Owers wrote:
>
> Just downloaded the forecast extension which was 3.3.2.which I think is 
> the latest on to a python 3 only machine (weewx 4.0.0b18) and it fails 
> forecast.py Line 567 except OSError , e; with an underscore under the ,
> Just wondered if anybody else has had this.
> Cheers Phil
>

-- 
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/21c677cf-99b6-412d-8085-24dfea8e5b7c%40googlegroups.com.


Re: [weewx-user] Re: Forecast 3.3.2

2020-04-10 Thread John Kline
Hi Phil,

OK, from the machine in question running WeeWX 4.0b18, please run:

PYTHONPATH=/home/weewx/bin python3 /home/weewx/bin/user/forecast.py --method 
UKMO --action download --loc 354731 --api-key 

Fill in your api-key and adjust ‘/home/weewx’ to your weewx install location.

Cheers,
John

> On Apr 10, 2020, at 7:32 AM, Phil Owers  wrote:
> 
> 
> I raised a second API to see if that was the problem hence why you got 2 
> different ones.  The following is from the key ending in f051.   Both keys 
> acted the same.
> 
> pi@raspberrypi:~ $ curl --user-agent 'foo' 
> "http://datapoint.metoffice.gov.uk/public/data/val/wxfcs/all/json/354731?res=3hourly&key=----f051";
> {"SiteRep":{"Wx":{"Param":[{"name":"F","units":"C","$":"Feels Like 
> Temperature"},{"name":"G","units":"mph","$":"Wind 
> Gust"},{"name":"H","units":"%","$":"Screen Relative 
> Humidity"},{"name":"T","units":"C","$":"Temperature"},{"name":"V","units":"","$":"Visibility"},{"name":"D","units":"compass","$":"Wind
>  Direction"},{"name":"S","units":"mph","$":"Wind 
> Speed"},{"name":"U","units":"","$":"Max UV 
> Index"},{"name":"W","units":"","$":"Weather 
> Type"},{"name":"Pp","units":"%","$":"Precipitation 
> Probability"}]},"DV":{"dataDate":"2020-04-10T09:00:00Z","type":"Forecast","Location":{"i":"354731","lat":"52.9456","lon":"1.212","name":"SHERINGHAM
>  
> (BEACH)","country":"ENGLAND","continent":"EUROPE","elevation":"0.0","Period":[{"type":"Day","value":"2020-04-10Z","Rep":[{"D":"ESE","F":"6","G":"13","H":"87","Pp":"5","S":"11","T":"8","V":"GO","W":"7","U":"1","$":"360"},{"D":"ESE","F":"9","G":"18","H":"79","Pp":"4","S":"9","T":"11","V":"GO","W":"7","U":"3","$":"540"},{"D":"ESE","F":"10","G":"18","H":"68","Pp":"4","S":"16","T":"13","V":"GO","W":"7","U":"4","$":"720"},{"D":"ESE","F":"12","G":"18","H":"60","Pp":"4","S":"13","T":"15","V":"GO","W":"7","U":"2","$":"900"},{"D":"ESE","F":"10","G":"13","H":"73","Pp":"4","S":"9","T":"11","V":"GO","W":"7","U":"1","$":"1080"},{"D":"SE","F":"7","G":"20","H":"78","Pp":"3","S":"9","T":"9","V":"GO","W":"7","U":"0","$":"1260"}]},{"type":"Day","value":"2020-04-11Z","Rep":[{"D":"SE","F":"7","G":"20","H":"79","Pp":"4","S":"9","T":"9","V":"GO","W":"7","U":"0","$":"0"},{"D":"SSE","F":"6","G":"22","H":"82","Pp":"4","S":"9","T":"9","V":"GO","W":"7","U":"0","$":"180"},{"D":"SSE","F":"6","G":"22","H":"81","Pp":"0","S":"9","T":"9","V":"GO","W":"1","U":"1","$":"360"},{"D":"S","F":"13","G":"18","H":"62","Pp":"0","S":"11","T":"15","V":"VG","W":"1","U":"3","$":"540"},{"D":"S","F":"17","G":"18","H":"50","Pp":"0","S":"11","T":"19","V":"VG","W":"1","U":"5","$":"720"},{"D":"SSW","F":"18","G":"16","H":"49","Pp":"7","S":"9","T":"20","V":"VG","W":"3","U":"2","$":"900"},{"D":"S","F":"16","G":"16","H":"61","Pp":"36","S":"9","T":"17","V":"GO","W":"3","U":"1","$":"1080"},{"D":"SW","F":"13","G":"13","H":"77","Pp":"8","S":"7","T":"14","V":"VG","W":"7","U":"0","$":"1260"}]},{"type":"Day","value":"2020-04-12Z","Rep":[{"D":"WSW","F":"11","G":"11","H":"84","Pp":"10","S":"7","T":"12","V":"VG","W":
> 
> Download failures are every time, hence why the forecast.sdb is empty.
> Im using a Python 3 only machine with your forecast.py file from your link 
> you gave me the other day. The weewx version is V4.0.0.b18 and always fails.
> My main machine runs weewx Version 3.9.2 and downloads from the met office 
> and uses forecast 3.3.2 forecast.py that was modified to use mozilla5.0 to 
> work and works fine.
> About a couple of months ago UKMO started to fail and via email they 
> suggested to use mozilla5.0. There were others around the UK who also had 
> problems it wasn't just me. 
> It failed HTTP Error 403: Forbidden which is the same as your forecast.py 
> hence why I think it is the same problem.
>  I cant remember the person name, its on this forum somewhere, who changed 
> his code form
> try:
> response = urllib2.urlopen(u)
> return response.read()
> to 
> try:
> req = urllib2.Request(u)
> req.add_header('User-Agent', 'Mozilla/5.0')
> 
> response = urllib2.urlopen(req)
> return response.read()
> This changed worked and we have been using it ever since.
> Phil
> 
> 
>> On Wednesday, April 8, 2020 at 3:11:31 PM UTC+1, Phil Owers wrote:
>> Just downloaded the forecast extension which was 3.3.2.which I think is the 
>> latest on to a python 3 only machine (weewx 4.0.0b18) and it fails 
>> forecast.py Line 567 except OSError , e; with an underscore under the ,
>> Just wondered if anybody else has had this.
>> Cheers Phil
> 
> -- 
> 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/d4bbeec7-b162-46de-b0c9-65f8ec4ea221%40googlegro

[weewx-user] Re: Forecast 3.3.2

2020-04-10 Thread Phil Owers
I raised a second API to see if that was the problem hence why you got 2 
different ones.  The following is from the key ending in f051.   Both keys 
acted the same.

pi@raspberrypi:~ $ curl --user-agent 'foo' 
"http://datapoint.metoffice.gov.uk/public/data/val/wxfcs/all/json/354731?res=3hourly&key=----f051";
{"SiteRep":{"Wx":{"Param":[{"name":"F","units":"C","$":"Feels Like 
Temperature"},{"name":"G","units":"mph","$":"Wind 
Gust"},{"name":"H","units":"%","$":"Screen Relative 
Humidity"},{"name":"T","units":"C","$":"Temperature"},{"name":"V","units":"","$":"Visibility"},{"name":"D","units":"compass","$":"Wind
 
Direction"},{"name":"S","units":"mph","$":"Wind 
Speed"},{"name":"U","units":"","$":"Max UV 
Index"},{"name":"W","units":"","$":"Weather 
Type"},{"name":"Pp","units":"%","$":"Precipitation 
Probability"}]},"DV":{"dataDate":"2020-04-10T09:00:00Z","type":"Forecast","Location":{"i":"354731","lat":"52.9456","lon":"1.212","name":"SHERINGHAM
 
(BEACH)","country":"ENGLAND","continent":"EUROPE","elevation":"0.0","Period":[{"type":"Day","value":"2020-04-10Z","Rep":[{"D":"ESE","F":"6","G":"13","H":"87","Pp":"5","S":"11","T":"8","V":"GO","W":"7","U":"1","$":"360"},{"D":"ESE","F":"9","G":"18","H":"79","Pp":"4","S":"9","T":"11","V":"GO","W":"7","U":"3","$":"540"},{"D":"ESE","F":"10","G":"18","H":"68","Pp":"4","S":"16","T":"13","V":"GO","W":"7","U":"4","$":"720"},{"D":"ESE","F":"12","G":"18","H":"60","Pp":"4","S":"13","T":"15","V":"GO","W":"7","U":"2","$":"900"},{"D":"ESE","F":"10","G":"13","H":"73","Pp":"4","S":"9","T":"11","V":"GO","W":"7","U":"1","$":"1080"},{"D":"SE","F":"7","G":"20","H":"78","Pp":"3","S":"9","T":"9","V":"GO","W":"7","U":"0","$":"1260"}]},{"type":"Day","value":"2020-04-11Z","Rep":[{"D":"SE","F":"7","G":"20","H":"79","Pp":"4","S":"9","T":"9","V":"GO","W":"7","U":"0","$":"0"},{"D":"SSE","F":"6","G":"22","H":"82","Pp":"4","S":"9","T":"9","V":"GO","W":"7","U":"0","$":"180"},{"D":"SSE","F":"6","G":"22","H":"81","Pp":"0","S":"9","T":"9","V":"GO","W":"1","U":"1","$":"360"},{"D":"S","F":"13","G":"18","H":"62","Pp":"0","S":"11","T":"15","V":"VG","W":"1","U":"3","$":"540"},{"D":"S","F":"17","G":"18","H":"50","Pp":"0","S":"11","T":"19","V":"VG","W":"1","U":"5","$":"720"},{"D":"SSW","F":"18","G":"16","H":"49","Pp":"7","S":"9","T":"20","V":"VG","W":"3","U":"2","$":"900"},{"D":"S","F":"16","G":"16","H":"61","Pp":"36","S":"9","T":"17","V":"GO","W":"3","U":"1","$":"1080"},{"D":"SW","F":"13","G":"13","H":"77","Pp":"8","S":"7","T":"14","V":"VG","W":"7","U":"0","$":"1260"}]},{"type":"Day","value":"2020-04-12Z","Rep":[{"D":"WSW","F":"11","G":"11","H":"84","Pp":"10","S":"7","T":"12","V":"VG","W":

Download failures are every time, hence why the forecast.sdb is empty.
Im using a Python 3 only machine with your forecast.py file from your link 
you gave me the other day. The weewx version is V4.0.0.b18 and always fails.
My main machine runs weewx Version 3.9.2 and downloads from the met office 
and uses forecast 3.3.2 forecast.py that was modified to use mozilla5.0 to 
work and works fine.
About a couple of months ago UKMO started to fail and via email they 
suggested to use mozilla5.0. There were others around the UK who also had 
problems it wasn't just me. 
It failed HTTP Error 403: Forbidden which is the same as your forecast.py 
hence why I think it is the same problem.
 I cant remember the person name, its on this forum somewhere, who changed 
his code form
try:
response = urllib2.urlopen(u)
return response.read()
to 
try:
req = urllib2.Request(u)
req.add_header('User-Agent', 'Mozilla/5.0')

response = urllib2.urlopen(req)
return response.read()
This changed worked and we have been using it ever since.
Phil


On Wednesday, April 8, 2020 at 3:11:31 PM UTC+1, Phil Owers wrote:
>
> Just downloaded the forecast extension which was 3.3.2.which I think is 
> the latest on to a python 3 only machine (weewx 4.0.0b18) and it fails 
> forecast.py Line 567 except OSError , e; with an underscore under the ,
> Just wondered if anybody else has had this.
> Cheers Phil
>

-- 
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/d4bbeec7-b162-46de-b0c9-65f8ec4ea221%40googlegroups.com.


Re: [weewx-user] Re: Forecast 3.3.2

2020-04-10 Thread John Kline
Hi Phil,

Are you absolutely certain that the key you used for the command you ran below 
is the same as what is in your weewx.conf file?  I ask because the forbidden 
error is what I see when I don’t use a valid key.

If they keys agree, please try again for the command line, but use your 
location instead of the one I gave you.  That is, use 354731.

Do you see the download failures in log every time or just some times?

Would you point me to the information about changing the User-agent?

Are you running with Python 2 or 3?

On my end, I switched to your location and its running fine.  I’ll leave it 
running.


> On Apr 10, 2020, at 2:52 AM, Phil Owers  wrote:
> 
> 
> But looking in the log a little late I see this
> Apr 10 10:39:24 raspberrypi weewx[626] INFO user.forecast: UKMOThread: UKMO: 
> download forecast from 
> 'http://datapoint.metoffice.gov.uk/public/data/val/wxfcs/all/json/354731?res=3hourly&key=f051'
> Apr 10 10:39:24 raspberrypi weewx[626] INFO weewx.manager: Added record 
> 2020-04-10 10:30:00 BST (1586511000) to daily summary in 'weewx.sdb'
> Apr 10 10:39:24 raspberrypi weewx[626] ERROR user.forecast: UKMOThread: UKMO: 
> failed attempt 1 to download forecast: HTTP Error 403: Forbidden
> Apr 10 10:39:24 raspberrypi weewx[626] ERROR user.forecast: UKMOThread: UKMO: 
> failed attempt 2 to download forecast: HTTP Error 403: Forbidden
> Apr 10 10:39:24 raspberrypi weewx[626] ERROR user.forecast: UKMOThread: UKMO: 
> failed attempt 3 to download forecast: HTTP Error 403: Forbidden
> Apr 10 10:39:24 raspberrypi weewx[626] ERROR user.forecast: UKMOThread: UKMO: 
> failed to download forecast
> Apr 10 10:39:24 raspberrypi weewx[626] ERROR user.forecast: UKMOThread: UKMO: 
> no forecast data for 354731 from 
> http://datapoint.metoffice.gov.uk/public/data/val/wxfcs/all/json/
> Apr 10 10:39:24 raspberrypi weewx[626] INFO user.forecast: UKMOThread: UKMO: 
> download forecast from 
> 'http://datapoint.metoffice.gov.uk/public/data/val/wxfcs/all/json/354731?res=3hourly&key=f051'
> 
>> On Wednesday, April 8, 2020 at 3:11:31 PM UTC+1, Phil Owers wrote:
>> Just downloaded the forecast extension which was 3.3.2.which I think is the 
>> latest on to a python 3 only machine (weewx 4.0.0b18) and it fails 
>> forecast.py Line 567 except OSError , e; with an underscore under the ,
>> Just wondered if anybody else has had this.
>> Cheers Phil
> 
> -- 
> 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/755d97de-cac8-4c97-85ea-9fb98a453d17%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5C31F8E3-99C2-4DED-B152-D0E342E81F83%40johnkline.com.


[weewx-user] Re: Datenbank zusammen legen.

2020-04-10 Thread Meteo Oberwallis
Hallo Günther.

Darf ich dich fragen, ob du vorher auch mal WsWin benutzt hast? Ich habe 
wetterdaten seit 2005, welche aber natürlich jetzt in weewx fehlen. Es 
müsste doch möglich sein, die von WsWin erstellten Monatsdateien, also .csv 
in die weewx Datenbank zu implementieren? Das wäre natürlich genial. 
anonsten verliere ich die ganzen jahre.

Gruss und danke für eure Hilfe

Am Freitag, 10. April 2020 08:25:51 UTC+2 schrieb Günther Wrana:
>
> Hallo
>
> bei mir hat das dann funktioniert nach dem ich die alte Datenbank so wie 
> oben beschrieben in eine .sql Datenbank umgewandelt habe.
>
> *sqlite3 db3.sdb*
> sqlite> *.output db3.sql*
> sqlite> *.dump archive*
> sqlite> *.quit*
>
> und danach haben sich die beiden Datenbanken zusammmen legen lassen.
>
> Fehlermeldungen sind auch bei mir gekommen nur wenn man am Schluss die 
> Datenbank mit dem checkt.
>
> *sqlite3 db3.sdb*
> sqlite> *pragma integrity_check;*
>
> und es O.K ausgibt dann passt das.
>
> Grüße Günther 
>
>
>
> Am Donnerstag, 9. April 2020 11:14:57 UTC+2 schrieb Meteo Oberwallis:
>>
>> Hallo zusammen.
>>
>> Ich wollte ebenfalls meine beiden .sdb Datenbanken zusammenlegen. Sie 
>> stammen beide aus weewx. Nun bekomme ich immer diese Fehlermeldung:
>>
>> root@raspberrypi:~# sqlite3 weewx.sdb_new_new
>> SQLite version 3.16.2 2017-01-06 16:32:41
>> Enter ".help" for usage hints.
>> sqlite> .read weewx.sdb_new
>> Error: cannot open "weewx.sdb_new"
>> sqlite> .read /home/pi/Desktop/weewx.sdb_new
>> Error: near line 1: near "SQLite": syntax error
>> Error: near line 403: unrecognized token: " "
>> Error: near line 5261: near "@n�": syntax error
>> Error: near line 5337: unrecognized token: " "
>> Error: near line 6332: unrecognized token: " "
>> Error: near line 6793: unrecognized token: " "
>> Error: near line 7575: near "@rH": syntax error
>> Error: near line 7831: near "@n�": syntax error
>> sqlite> 
>>
>> Hatte das jemand auch?
>> Am Samstag, 4. Januar 2020 23:41:23 UTC+1 schrieb gjr80:
>>>
>>> Hallo Günther,
>>>
>>> Ihr Englisch ist wahrscheinlich besser als mein Deutsch, aber lassen Sie 
>>> uns sehen, wie wir gehen. Ich habe sowohl Englische als auch 
>>> Google-Deutsche Wörter eingefügt.
>>>
>>> Wenn ich das richtig verstehe, haben Sie zwei WeeWX SQLite-Datenbanken, 
>>> die Sie zusammenführen möchten. Leider gibt es im Utilities Guide nichts, 
>>> was Ihnen das leicht machen könnte. Dies ist ein paar Mal vorgekommen und 
>>> wenn Sie das Forum nach Beiträgen mit "merge sqlite datbase" durchsuchen, 
>>> werden Sie einige Beiträge finden, die Ihnen helfen werden. Ich würde 
>>> dieses versuchen (
>>> https://groups.google.com/d/msg/weewx-user/T2VuiIkcAEM/wZzemNzWknQJ) 
>>> und das ist das, was ich als Basis für das verwendet habe:
>>>
>>> 1. Erstellen Sie eine Sicherungskopie Ihrer beiden Datenbanken
>>>
>>> 2. Installieren Sie das Dienstprogramm sqlite3, falls es noch nicht 
>>> installiert ist:
>>>
>>> $ sudo apt-get install sqlite3
>>>
>>> 3. Wählen Sie eine Ihrer Datenbanken als endgültige Datenbank aus und 
>>> benennen Sie die andere in db1.sdb um. Sie sollten jetzt zwei Datenbanken 
>>> haben, eine mit dem Namen weewx.sdb und eine andere mit dem Namen db1.sdb. 
>>> Um die Dinge später zu vereinfachen, stellen Sie sicher, dass sich 
>>> weewx.sdb in dem Verzeichnis befindet, in dem Sie Ihre WeeWX-Datenbank 
>>> dauerhaft speichern möchten (die Standardverzeichnisse sind 
>>> /home/weewx/archive für eine setup.py-Installation oder /var/lib/weewx für 
>>> alle andere installiert). Ich werde /home/weewx/archive in dieser Anleitung 
>>> verwenden
>>>
>>> 4. Kopieren Sie die Datenbank db1.sdb in eine Datei:
>>>
>>> $ sqlite3 /path/to/db1.sdb
>>> sqlite> .output /var/tmp/db1.dump
>>> sqlite> .dump
>>> sqlite> .quit
>>>
>>> 5. Importieren Sie nun die gedumpten Daten in die endgültige Datenbank 
>>> weewx.sdb:
>>>
>>> $ sqlite3 /home/weewx/archive/weewx.sdb
>>> sqlite> .read /var/tmp/db1.dump
>>>
>>> Sie werden wahrscheinlich Beschwerden über 'existing tables' oder 
>>> 'unique constraint failed' sehen. Diese können ignoriert werden. Es muss 
>>> jedoch etwas Ernsthafteres betrachtet werden.
>>>
>>> sqlite> .quit
>>>
>>> 6. Der nächste Schritt besteht darin, die täglichen Zusammenfassungen 
>>> neu zu erstellen. Dies erfolgt mit dem Dienstprogramm wee_database und 
>>> erfordert, dass Sie eine WeeWX-Datenbindung konfigurieren, um die jetzt 
>>> konsolidierte Datenbank weewx.sdb zu verwenden. Bearbeiten Sie die Datei 
>>> weewx.conf und suchen Sie die Zeilengruppe [Databases]. Überprüfen Sie, ob 
>>> Sie einen Datenbankeintrag für weewx.sdb haben. Dieser sollte ungefähr so 
>>> ​​aussehen:
>>>
>>> [Databases]
>>>
>>> # A SQLite database is simply a single file
>>> [[archive_sqlite]]
>>> database_name = weewx.sdb
>>> database_type = SQLite
>>>
>>> Wenn sich weewx.sdb in den Verzeichnissen home/weewx/archive oder 
>>> /var/lib/weewx befindet, ist das oben Genannte in Ordnung. Beachten Sie den 
>>> Eintrag in [[ ]], in diese

[weewx-user] Re: Forecast 3.3.2

2020-04-10 Thread Phil Owers
But looking in the log a little late I see this
Apr 10 10:39:24 raspberrypi weewx[626] INFO user.forecast: UKMOThread: 
UKMO: download forecast from 
'http://datapoint.metoffice.gov.uk/public/data/val/wxfcs/all/json/354731?res=3hourly&key=f051'
Apr 10 10:39:24 raspberrypi weewx[626] INFO weewx.manager: Added record 
2020-04-10 10:30:00 BST (1586511000) to daily summary in 'weewx.sdb'
Apr 10 10:39:24 raspberrypi weewx[626] ERROR user.forecast: UKMOThread: 
UKMO: failed attempt 1 to download forecast: HTTP Error 403: Forbidden
Apr 10 10:39:24 raspberrypi weewx[626] ERROR user.forecast: UKMOThread: 
UKMO: failed attempt 2 to download forecast: HTTP Error 403: Forbidden
Apr 10 10:39:24 raspberrypi weewx[626] ERROR user.forecast: UKMOThread: 
UKMO: failed attempt 3 to download forecast: HTTP Error 403: Forbidden
Apr 10 10:39:24 raspberrypi weewx[626] ERROR user.forecast: UKMOThread: 
UKMO: failed to download forecast
Apr 10 10:39:24 raspberrypi weewx[626] ERROR user.forecast: UKMOThread: 
UKMO: no forecast data for 354731 from 
http://datapoint.metoffice.gov.uk/public/data/val/wxfcs/all/json/
Apr 10 10:39:24 raspberrypi weewx[626] INFO user.forecast: UKMOThread: 
UKMO: download forecast from 
'http://datapoint.metoffice.gov.uk/public/data/val/wxfcs/all/json/354731?res=3hourly&key=f051'

On Wednesday, April 8, 2020 at 3:11:31 PM UTC+1, Phil Owers wrote:
>
> Just downloaded the forecast extension which was 3.3.2.which I think is 
> the latest on to a python 3 only machine (weewx 4.0.0b18) and it fails 
> forecast.py Line 567 except OSError , e; with an underscore under the ,
> Just wondered if anybody else has had this.
> Cheers Phil
>

-- 
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/755d97de-cac8-4c97-85ea-9fb98a453d17%40googlegroups.com.


[weewx-user] Re: Forecast 3.3.2

2020-04-10 Thread Phil Owers
pi@raspberrypi:~ $ host datapoint.metoffice.gov.uk
datapoint.metoffice.gov.uk is an alias for 
datapoint.metoffice.gov.uk.edgesuite.net.
datapoint.metoffice.gov.uk.edgesuite.net is an alias for a978.r.akamai.net.
a978.r.akamai.net has address 213.123.252.58
a978.r.akamai.net has address 213.123.252.56
pi@raspberrypi:~ $
{"SiteRep":{"Wx":{"Param":[{"name":"F","units":"C","$":"Feels Like 
Temperature"},{"name":"G","units":"mph","$":"Wind 
Gust"},{"name":"H","units":"%","$":"Screen Relative 
Humidity"},{"name":"T","units":"C","$":"Temperature"},{"name":"V","units":"","$":"Visibility"},{"name":"D","units":"compass","$":"Wind
 
Direction"},{"name":"S","units":"mph","$":"Wind 
Speed"},{"name":"U","units":"","$":"Max UV 
Index"},{"name":"W","units":"","$":"Weather 
Type"},{"name":"Pp","units":"%","$":"Precipitation 
Probability"}]},"DV":{"dataDate":"2020-04-10T07:00:00Z","type":"Forecast","Location":{"i":"3772","lat":"51.479","lon":"-0.449","name":"HEATHROW","country":"ENGLAND","continent":"EUROPE","elevation":"25.0","Period":[{"type":"Day","value":"2020-04-10Z","Rep":[{"D":"NE","F":"9","G":"13","H":"78","Pp":"0","S":"4","T":"10","V":"MO","W":"2","U":"0","$":"180"},{"D":"NE","F":"8","G":"18","H":"87","Pp":"0","S":"4","T":"9","V":"MO","W":"1","U":"1","$":"360"},{"D":"E","F":"12","G":"11","H":"71","Pp":"0","S":"9","T":"14","V":"MO","W":"1","U":"3","$":"540"},{"D":"ESE","F":"19","G":"13","H":"51","Pp":"0","S":"9","T":"21","V":"GO","W":"1","U":"5","$":"720"},{"D":"ESE","F":"21","G":"16","H":"44","Pp":"0","S":"11","T":"23","V":"GO","W":"1","U":"2","$":"900"},{"D":"ESE","F":"18","G":"18","H":"50","Pp":"0","S":"11","T":"20","V":"GO","W":"1","U":"1","$":"1080"},{"D":"E","F":"14","G":"13","H":"65","Pp":"0","S":"7","T":"15","V":"GO","W":"0","U":"0","$":"1260"}]},{"type":"Day","value":"2020-04-11Z","Rep":[{"D":"E","F":"12","G":"11","H":"76","Pp":"0","S":"4","T":"12","V":"GO","W":"0","U":"0","$":"0"},{"D":"E","F":"11

There is more but it only copied what was on the screen I then usedmy 
location and got 
i@raspberrypi:~ $ curl --user-agent 'foo' 
"http://datapoint.metoffice.gov.uk/public/data/val/wxfcs/all/json/354731?res=3hourly&key=8f916e8d-7477-4198-8ecc-ae764ff7bb84";
{"SiteRep":{"Wx":{"Param":[{"name":"F","units":"C","$":"Feels Like 
Temperature"},{"name":"G","units":"mph","$":"Wind 
Gust"},{"name":"H","units":"%","$":"Screen Relative 
Humidity"},{"name":"T","units":"C","$":"Temperature"},{"name":"V","units":"","$":"Visibility"},{"name":"D","units":"compass","$":"Wind
 
Direction"},{"name":"S","units":"mph","$":"Wind 
Speed"},{"name":"U","units":"","$":"Max UV 
Index"},{"name":"W","units":"","$":"Weather 
Type"},{"name":"Pp","units":"%","$":"Precipitation 
Probability"}]},"DV":{"dataDate":"2020-04-10T07:00:00Z","type":"Forecast","Location":{"i":"354731","lat":"52.9456","lon":"1.212","name":"SHERINGHAM
 
(BEACH)","country":"ENGLAND","continent":"EUROPE","elevation":"0.0","Period":[{"type":"Day","value":"2020-04-10Z","Rep":[{"D":"ESE","F":"5","G":"13","H":"90","Pp":"5","S":"11","T":"8","V":"MO","W":"7","U":"0","$":"180"},{"D":"ESE","F":"6","G":"13","H":"87","Pp":"5","S":"11","T":"8","V":"GO","W":"7","U":"1","$":"360"},{"D":"ESE","F":"7","G":"16","H":"84","Pp":"4","S":"11","T":"9","V":"GO","W":"7","U":"3","$":"540"},{"D":"ESE","F":"10","G":"18","H":"66","Pp":"4","S":"16","T":"13","V":"GO","W":"7","U":"4","$":"720"},{"D":"ESE","F":"11","G":"20","H":"61","Pp":"5","S":"16","T":"14","V":"GO","W":"7","U":"2","$":"900"},{"D":"SE","F":"10","G":"16","H":"72","Pp":"4","S":"9","T":"12","V":"GO","W":"7","U":"1","$":"1080"},{"D":"SE","F":"7","G":"20","H":"77","Pp":"4","S":"9","T":"9","V":"GO","W":"7","U":"0","$":"1260"}]},{"type":"Day","value":"2020-04-11Z","Rep":[{"D":"SSE","F":"7",
Again there is more
Phil


On Wednesday, April 8, 2020 at 3:11:31 PM UTC+1, Phil Owers wrote:
>
> Just downloaded the forecast extension which was 3.3.2.which I think is 
> the latest on to a python 3 only machine (weewx 4.0.0b18) and it fails 
> forecast.py Line 567 except OSError , e; with an underscore under the ,
> Just wondered if anybody else has had this.
> Cheers Phil
>

-- 
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/956e76a2-776e-46ba-8fd9-1bff76e9654a%40googlegroups.com.


Re: [weewx-user] Re: Forecast 3.3.2

2020-04-10 Thread Phil Owers
That gives me a display of siterep and then the list of param name units
feels like etc and then the info. So works.  Its also the same on my
working pi.  So that looks good
Phil

On Fri, 10 Apr 2020, 05:34 John Kline,  wrote:

> Hi Phil,
>
> Please run the following command (it is a single line), substituting your
> API key, and reply with the output you receive.
>
> curl --user-agent 'foo' "
> http://datapoint.metoffice.gov.uk/public/data/val/wxfcs/all/json/3772?res=3hourly&key=X
> "
>
> For me, with —user-agent not specified, with —user-agent ‘foo’ specified,
> or with any other user-agent specified, the command works.
>
> Web searches do show that, from time to time, UKMO has issues and there is
> anecdotal evidence that changing the user-agent sometimes helps.  I wonder
> if your original problem, where you needed to change the user-agent, was
> one of those times.
>
> It will also be interested to see if you can resolve
> datapoint.metoffice.gov.uk.  In addition to that above, please also
> include the output of:
>
> host datapoint.metoffice.gov.uk
>
> I will revert the change I made to specify a user-agent if it turns out it
> is not needed (which currently appears to be the case).
>
> John
>
> On Apr 9, 2020, at 6:05 PM, John Kline  wrote:
>
> 
> Hi Phil,
>
> I committed the change.  Please pull again.
>
> None of the code is going to help you with name resolution; but it doesn’t
> hurt to try anyway.
>
> Afterwards, try resolving the machine name in the UKMO url on the same
> machine that WeeWX is running (with host or nslookup).
>
> On Apr 9, 2020, at 4:49 PM, Phil Owers  wrote:
>
> 
> John
> Mine keeps saying temp temporary failure in name. Could you send me your
> forecast.py file please
> Phil
>
> On Wednesday, April 8, 2020 at 3:11:31 PM UTC+1, Phil Owers wrote:
>>
>> Just downloaded the forecast extension which was 3.3.2.which I think is
>> the latest on to a python 3 only machine (weewx 4.0.0b18) and it fails
>> forecast.py Line 567 except OSError , e; with an underscore under the ,
>> Just wondered if anybody else has had this.
>> Cheers Phil
>>
> --
> 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/88ea690b-da8c-49f2-8b62-53b275ee31e7%40googlegroups.com
> 
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/9EE1E277-3441-4AA8-ADCF-BC0E78B28F06%40johnkline.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CALTQ7pM1OnEg1ia%2BNose1qfZhiox%2BPMV40X5N516zH5%2BjegPNg%40mail.gmail.com.