Re: [weewx-user] Re: Belchertown skin 1.1 released!

hello PAT I just upgrade in skin 1.1 before I was in 1.1b9 that works fine . http://jurassikpat.ddns.net/weewx/belchertown/ good Job pay attention to health, and congratulations on the baby. Patrick Le 09/04/2020 à 16:50, G Hammer a écrit : Upgraded from a previous 1.1 beta fine here. --

[weewx-user] MQTTSubscribe 1.5.2

Release 1.5.2 can be found here, https://github.com/bellrichm/WeeWX-MQTTSubscribe/releases/tag/v1.5.2 Here is a summary of some of the improvements made in recent releases: - Support for data that is cumulative (for example rain totals). - Allow date/time formats other than Unix epoch.

[weewx-user] Re: Forecast 3.3.2

Hi John Just need to tweek the forecast.py so it can download from the UK Met Office. They changed a few weeks ago to only excepting 'User-Agent', 'Mozilla/5.0 In the forecast.py you sent me it had response = six.moves.urllib.request.urlopen(u) return response.read().decode('utf-8') My

Re: [weewx-user] Re: Forecast 3.3.2

Hi Phil, Would you please try the following: user_agent = {'User-Agent': 'Mozilla/5.0'} requester = six.moves.urllib.request.Request(u, headers=user_agent) response = request.urlopen(requester) return response.read().decode('utf-8')

Re: [weewx-user] Re: Changes with Belchertown skin & DarkSky

Alerts come from DarkSky's internal AI aggregation with direct links to the source. This works for multiple countries and not just weather.gov. OWM does not have this type of setup or service. So alerts will be removed in Belchertown skin v1.2 On Thursday, April 9, 2020 at 3:39:49 PM UTC-4,

Re: [weewx-user] Re: Changes with Belchertown skin & DarkSky

Pat Just curious how Alerts works, and how it may depend on DarkSky. Got alert today regarding Wind Advisory in effect until 10 April 2020 00:00 . Which has

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

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

[weewx-user] Re: Forecast 3.3.2

John That was quick It failed in the syslog NameError : name 'request' is not defined I will put log.info(u) before the first line if that helps and thanks for helping Phil On Wednesday, April 8, 2020 at 3:11:31 PM UTC+1, Phil Owers wrote: > > Just downloaded the forecast extension which was

[weewx-user] Weewx2aprx does not show rainfall accumulation

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

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

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

[weewx-user] Re: Forecast 3.3.2

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

Re: [weewx-user] Re: Forecast 3.3.2

Hi Phil, I signed up for an API key and it it working for me. With the code I sent you (that is, the second code snippet I sent). The temporary failure in name resolution you are seeing is just that, temporary. Here’s my log once I had a real API key: Apr 9 15:25:05 judy weewx[29939] INFO

Re: [weewx-user] Re: Forecast 3.3.2

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,

Re: [weewx-user] Re: Forecast 3.3.2

OK, one more try while I’m waiting for the URL from you. I forgot to prefix request with six.moves.urllib. user_agent = {'User-Agent': 'Mozilla/5.0'} requester = six.moves.urllib.request.Request(u, headers=user_agent) response = six.moves.urllib.request.urlopen(requester) return

Re: [weewx-user] Re: Forecast 3.3.2

OK, the URL I asked you to send will have your API key, so don’t send that. I tried the code I sent with an API key of 123 (i.e., invalid) and a location code of 3772 (which I got from the HEATHROW_1 test in the plugin). The results I get are below. Which obviously didn’t work with an invalid

[weewx-user] Re: Forecast 3.3.2

http://datapoint.metoffice.gov.uk/public/data/val/wxfcs/all/json/ Apr 9 23:11:21 raspberrypi weewx[1898] ERROR user.forecast: UKMOThread: UKMO: failed attempt 3 to download forecast: Hope that's what you need I could set up a temp api / location for UKMO if that would help. But its late

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

I have re-started weewx and see this: After (finally) re-starting I see the re: station registry: restx: StationRegistry: wait interval (840 < 604800) has not passed for record 2020-04-09 21:48:00 PDT (1586494080) On Wednesday, March 25, 2020 at 9:14:17 PM UTC-7, beachboy wrote: > > I had a

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

OK, and what appeared in the log 840 odd seconds earlier? Once WeeWX is running it only updates the station registry every 7 days (or every 604800 seconds). That log entry tells us that the last update occurred 840 seconds ago and it is while yet until WeeWX hits the 7 elapsed days for the next

Re: [weewx-user] Re: Forecast 3.3.2

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=X; For me, with —user-agent

[weewx-user] Re: Datenbank zusammen legen.

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-user] Re: Weewx to mqtt

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

[weewx-user] Re: Belchertown skin 1.1 released!

Thank you for all your hard work Pat! Update works well, had to use my beta configuration after update. Graphs-page, charts and about page works without problems. https://www.vorrath-net.de/wetter/ regards Joachim -- You received this message because you are subscribed to the Google Groups

[weewx-user] Re: Belchertown skin 1.1 released!

Hi Pat I hope you are fine I installed your skin but I always see the default skin like never before. look at my configuration and tell me what am i wrong: [[SeasonsReport]] # The SeasonsReport uses the 'Seasons' skin, which contains the # images, templates and plots

[weewx-user] Re: Belchertown skin 1.1 released!

That's because you have Belchertown being saved to HTML_ROOT = /var/www/html /weewx/belchertown Either browse to your server at /weewx/belchertown or change the HTML_ROOT to something that works for you On Thursday, April 9, 2020 at 6:34:00 AM UTC-4, Wifi75 wrote: > > Hi Pat I hope you are

[weewx-user] Re: Belchertown skin 1.1 released!

Upgraded from a previous 1.1 beta fine here. -- 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