Re: [weewx-user] WeatherUnderground Not Publishing

[Pete Geenhuizen]

Mine is back also as of 13:10:25 EDT

On 9/22/22 13:17, Tom Keffer wrote:

Mine is back online as well. Wonder what that was all about?

On Thu, Sep 22, 2022 at 10:15 AM Dave Webb KB1PVH  
wrote:


Mine is back online as of 13:14 EDT.

Dave - KB1PVH




Sent from my Galaxy S21

On Thu, Sep 22, 2022, 12:43 PM Del Merritt 
wrote:

I am seeing no errors publishing (rapid fire) to wunderground,
e.g.:
Sep 22 12:38:49 weewx[15535] INFO weewx.restx:
Wunderground-RF: Published record 2022-09-22 12:38:50 EDT
(1663864730)
Sep 22 12:38:51 weewx[15535] INFO weewx.restx:
Wunderground-RF: Published record 2022-09-22 12:38:52 EDT
(1663864732)
Sep 22 12:38:53 weewx[15535] INFO weewx.restx:
Wunderground-RF: Published record 2022-09-22 12:38:54 EDT
(1663864734)
Sep 22 12:38:55 weewx[15535] INFO weewx.restx:
Wunderground-RF: Published record 2022-09-22 12:38:56 EDT
(1663864736)
Sep 22 12:38:57 weewx[15535] INFO weewx.restx:
Wunderground-RF: Published record 2022-09-22 12:38:58 EDT
(1663864738)
Sep 22 12:38:59 weewx[15535] INFO weewx.restx:
Wunderground-RF: Published record 2022-09-22 12:39:00 EDT
(1663864740)
Sep 22 12:39:01 weewx[15535] INFO weewx.restx:
Wunderground-RF: Published record 2022-09-22 12:39:02 EDT
(1663864742)

WeeWX 4.8.0, Davis Vantage Pro2. Running on a RaspberryPI.

Cheers,
-Del


On Thu, Sep 22, 2022 at 12:36 PM Pete Geenhuizen
 wrote:

Seeing the same thing since 1300 Sept 21.

On 9/22/22 11:49, Tom Stewart wrote:

Nothing since 9/21 @ 10:55 a.m. ET. :-(

getting errors like the following in the log:

Sep 22 09:50:39 woodypi weewx[575] ERROR weewx.restx:
Wunderground-PWS: Failed to publish record 2022-09-22
09:50:00 EDT (1663854600): Failed upload after 3 tries

similar to Tyler's


On Thursday, September 22, 2022 at 11:44:45 AM UTC-4 TomR
wrote:

I’m seeing the same thing.

Tom


On Sep 22, 2022, at 10:35 AM, Tyler Johnson
 wrote:

Hello,

I was wondering if anyone else is having issues
publishing records to WeatherUnderground starting
yesterday around 11:52PM EST? Both standard and
rapid updates seem to be failing but I've validated
the API is working and reachable from my server.

Sep 22 13:11:25 homeserver python3[25207]:
weewx[25207] INFO weewx.engine: Starting main packet
loop.
Sep 22 13:11:27 homeserver python3[25207]:
weewx[25207] ERROR weewx.restx: Wunderground-RF:
Failed to publish record 2022-09-22 13:11:27 UTC
(1663852287): Failed upload after 1 tries
Sep 22 13:11:27 homeserver python3[25207]:
weewx[25207] ERROR weewx.restx: Wunderground-RF:
Failed to publish record 2022-09-22 13:11:27 UTC
(1663852287): Failed upload after 1 tries
Sep 22 13:11:29 homeserver python3[25207]:
weewx[25207] ERROR weewx.restx: Wunderground-RF:
Failed to publish record 2022-09-22 13:11:29 UTC
(1663852289): Failed upload after 1 tries

Curl works:
curl

https://api.weather.com/v2/pws/observations/current\?stationId\=KMABOSTO365\\=json\\=e\\=

<https://api.weather.com/v2/pws/observations/current%5C?stationId%5C=KMABOSTO365%5C%5C=json%5C%5C=e%5C%5C=>

{"observations":[{"stationID":"KMABOSTO365","obsTimeUtc":"2022-09-22T15:34:19Z","obsTimeLocal":"2022-09-22
11:34:19","neighborhood":"Beacon
Hill","softwareType":"Maximum

Inc","country":"US","solarRadiation":null,"lon":-71.069,"realtimeFrequency":null,"epoch":1663860859,"lat":42.357,"uv":null,"winddir":315,"humidity":0,"qcStatus":1,"imperial":{"temp":68,"heatIndex":68,"dewpt":null,"windChill":68,"windSpeed":0,"windGust":9,"pressure":null,"precipRate":0.00,"precipTotal":0.00,"elev":56}}]}

Any help would be greatly appreciated.

Thanks,
Tyler

-- 
You received this message because you are subscribed

to the Google Groups "weewx-user" group.
T

Re: [weewx-user] WeatherUnderground Not Publishing

[Pete Geenhuizen]

Seeing the same thing since 1300 Sept 21.

On 9/22/22 11:49, Tom Stewart wrote:

Nothing since 9/21 @ 10:55 a.m. ET. :-(

getting errors like the following in the log:

Sep 22 09:50:39 woodypi weewx[575] ERROR weewx.restx: 
Wunderground-PWS: Failed to publish record 2022-09-22 09:50:00 EDT 
(1663854600): Failed upload after 3 tries


similar to Tyler's


On Thursday, September 22, 2022 at 11:44:45 AM UTC-4 TomR wrote:

I’m seeing the same thing.

Tom


On Sep 22, 2022, at 10:35 AM, Tyler Johnson
 wrote:

Hello,

I was wondering if anyone else is having issues publishing
records to WeatherUnderground starting yesterday around 11:52PM
EST? Both standard and rapid updates seem to be failing but I've
validated the API is working and reachable from my server.

Sep 22 13:11:25 homeserver python3[25207]: weewx[25207] INFO
weewx.engine: Starting main packet loop.
Sep 22 13:11:27 homeserver python3[25207]: weewx[25207] ERROR
weewx.restx: Wunderground-RF: Failed to publish record 2022-09-22
13:11:27 UTC (1663852287): Failed upload after 1 tries
Sep 22 13:11:27 homeserver python3[25207]: weewx[25207] ERROR
weewx.restx: Wunderground-RF: Failed to publish record 2022-09-22
13:11:27 UTC (1663852287): Failed upload after 1 tries
Sep 22 13:11:29 homeserver python3[25207]: weewx[25207] ERROR
weewx.restx: Wunderground-RF: Failed to publish record 2022-09-22
13:11:29 UTC (1663852289): Failed upload after 1 tries

Curl works:
curl

https://api.weather.com/v2/pws/observations/current\?stationId\=KMABOSTO365\\=json\\=e\\=



{"observations":[{"stationID":"KMABOSTO365","obsTimeUtc":"2022-09-22T15:34:19Z","obsTimeLocal":"2022-09-22
11:34:19","neighborhood":"Beacon Hill","softwareType":"Maximum

Inc","country":"US","solarRadiation":null,"lon":-71.069,"realtimeFrequency":null,"epoch":1663860859,"lat":42.357,"uv":null,"winddir":315,"humidity":0,"qcStatus":1,"imperial":{"temp":68,"heatIndex":68,"dewpt":null,"windChill":68,"windSpeed":0,"windGust":9,"pressure":null,"precipRate":0.00,"precipTotal":0.00,"elev":56}}]}

Any help would be greatly appreciated.

Thanks,
Tyler

-- 
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+...@googlegroups.com.
To view this discussion on the web visit

https://groups.google.com/d/msgid/weewx-user/5ea7428b-3d55-4413-97fb-84b6b6a8fc23n%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/6e430b50-549f-434a-97ba-d5e6655b6b56n%40googlegroups.com 
.


--
This message has been scanned for viruses and
dangerous content by *MailScanner* , and is
believed to be clean. 


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers

--
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/276495ce-4e65-ac24-473f-0ab10f1b285f%40geenhuizen.net.

[weewx-user] Vantage Battery Alarm mail not working

[Pete Geenhuizen]

I recently moved weewx 4.7.0 from CentOS 7 to  Rocky 8 and now I notice 
that I'm not getting any mail regarding low battery.

The log file reports that the battery is low
May 19 18:17:46 opus journal[1137920]: weewx[1137920] DEBUG 
weewx.engine: Loading service user.lowBattery.BatteryAlarm
May 19 18:17:46 opus journal[1137920]: weewx[1137920] INFO 
user.lowBattery: LowBattery alarm enabled. Count threshold is 10
May 19 18:17:46 opus journal[1137920]: weewx[1137920] DEBUG 
weewx.engine: Finished loading service user.lowBattery.BatteryAlarm
May 19 18:18:03 opus journal[1137920]: weewx[1137920] INFO 
user.lowBattery: Low battery status sounded at 2022-05-19 18:18:04 EDT 
(1652998684): {'txBatteryStatus': 1}


I've modified weewx.conf to include the battery alarm

report_services = weewx.engine.StdPrint, weewx.engine.StdReport, 
user.lowBattery.BatteryAlarm


[Alarm]
    time_wait = 3600
    count_threshold = 10
    smtp_host = mailbox.sunny.beach
    # smtp_user = myusername
    # smtp_password = mypassword
    from = ws@
    mailto = ##
    subject = Time to change the battery!

This all worked in CentOS 7 but alas not in Rocky 8.

I looked at  the host mail log, but I don't see any attempt by weewx to 
send mail

I've set debug in weewx.conf to 1.
So how do I go about trouble shooting this problem?

Other than this mail problem all other mail from this host works just fine.

Thanks
Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers

--
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/b5278dc3-100f-db55-f64b-9d5d5d9de08a%40geenhuizen.net.

Re: [weewx-user] Belchertown Forecast Interval

[Pete Geenhuizen]

Well that explains a lot.  I thought I had the latest version.
Thanks

On 4/21/21 8:50 AM, 'Steve Woodford' via weewx-user wrote:
On 21 Apr 2021, at 13:23, Pete Geenhuizen <mailto:pgeenhui...@gmail.com>> wrote:


I've just recently started looking into changing my weewx skin to 
Belchertown.
I've been able to figure out most of what I want, however no matter 
how much tinkering I do the one thing that totally escapes me is the 
Forecast interval option.  No matter what I've tried


It’s a new feature, available in the as-yet unreleased 
Belchertown-v1.3b. You’ll need to install from latest GitHub master to 
get it.


Steve

--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean. --
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 
<mailto:weewx-user+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/C4672CDC-4DBB-4AC7-B35E-2B63D7C1EA2E%40mctavish.co.uk 
<https://groups.google.com/d/msgid/weewx-user/C4672CDC-4DBB-4AC7-B35E-2B63D7C1EA2E%40mctavish.co.uk?utm_medium=email_source=footer>.


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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/a2388e67-38c2-30ac-97e2-ed624ba9ee3d%40geenhuizen.net.

[weewx-user] Belchertown Forecast Interval

[Pete Geenhuizen]

I've just recently started looking into changing my weewx skin to 
Belchertown.
I've been able to figure out most of what I want, however no matter how 
much tinkering I do the one thing that totally escapes me is the 
Forecast interval option.  No matter what I've tried
I can't get the option to show up as you can see here 
http://geenhuizen.net/weewx.


This is what I have in skins.conf, and I've tried setting forecast 
interval hours to all the possible values yet the option never shows up.



   # Forecast defaults
    forecast_enabled = 1
    forecast_provider = "aeris"
    forecast_api_id = " "
    forecast_api_secret = " "
    forecast_units = "us"
    forecast_lang = "en"
    forecast_stale = 3540
    forecast_aeris_use_metar = 1
    forecast_alert_enabled = 0
    forecast_alert_limit = 1
    forecast_show_daily_forecast_link = 0
    forecast_daily_forecast_link = ""
    #

   forecast_interval_hours = 24


Any help in getting this to work would be greatly appreciated.

Thanks
Pete
--

Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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/80b83f3b-2d72-84ac-c671-355a144b54ad%40geenhuizen.net.

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

[Pete Geenhuizen]

OK I guess I'll have to give it a shot and hope like hell that it works.

Thanks

On 2020-05-02 13:36, Tom Keffer wrote:

It should. I'm not sure how thoroughly it as been tested under Python 3.

On Sat, May 2, 2020 at 9:17 AM Pete Geenhuizen <mailto:p...@geenhuizen.net>> wrote:


Oops my bad i got confused by the similar driver name, I'm using
the wx23xx driver which is working just fine under V3 so will it
work in V4?

On 5/2/20 11:47 AM, Tom Keffer wrote:

wh23xx is not a supported weather station under WeeWX V3 or V4.
No plans to change that.

However, I will see what I can do about getting the wh23xx 3rd
party extension updated.

-tk

On Sat, May 2, 2020 at 8:42 AM Pete Geenhuizen
mailto:p...@geenhuizen.net>> wrote:
-- 
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
<mailto:weewx-user+unsubscr...@googlegroups.com>.
To view this discussion on the web visit

https://groups.google.com/d/msgid/weewx-user/CAPq0zEDvXyyw-Le12K8mWVqGRsNkEXgfcd%2Behyji7xYv2ew9Dw%40mail.gmail.com

<https://groups.google.com/d/msgid/weewx-user/CAPq0zEDvXyyw-Le12K8mWVqGRsNkEXgfcd%2Behyji7xYv2ew9Dw%40mail.gmail.com?utm_medium=email_source=footer>.

-- 
This message has been scanned for viruses and

dangerous content by *MailScanner*
<http://www.mailscanner.info/>, and is
believed to be clean. 


-- 
Unencumbered by the thought process.

  -- Click and Clack the Tappet brothers


-- 
This message has been scanned for viruses and

dangerous content by *MailScanner* <http://www.mailscanner.info/>,
and is
believed to be clean.

--
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 
<mailto:weewx-user+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEB2YtYHWcGUcKXCAr2%3DTDkXNTaQe1Z%3D1NmrZYn9bFy8ng%40mail.gmail.com 
<https://groups.google.com/d/msgid/weewx-user/CAPq0zEB2YtYHWcGUcKXCAr2%3DTDkXNTaQe1Z%3D1NmrZYn9bFy8ng%40mail.gmail.com?utm_medium=email_source=footer>.


--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean. 


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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/733f185a-8d2d-874e-ee58-f42e09e6e772%40geenhuizen.net.

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

[Pete Geenhuizen]

Oops my bad i got confused by the similar driver name, I'm using the 
wx23xx driver which is working just fine under V3 so will it work in V4?


On 5/2/20 11:47 AM, Tom Keffer wrote:
wh23xx is not a supported weather station under WeeWX V3 or V4. No 
plans to change that.


However, I will see what I can do about getting the wh23xx 3rd party 
extension updated.


-tk

On Sat, May 2, 2020 at 8:42 AM Pete Geenhuizen <mailto:p...@geenhuizen.net>> wrote:

--
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 
<mailto:weewx-user+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEDvXyyw-Le12K8mWVqGRsNkEXgfcd%2Behyji7xYv2ew9Dw%40mail.gmail.com 
<https://groups.google.com/d/msgid/weewx-user/CAPq0zEDvXyyw-Le12K8mWVqGRsNkEXgfcd%2Behyji7xYv2ew9Dw%40mail.gmail.com?utm_medium=email_source=footer>.


--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean. 


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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/a554794f-6025-9fca-b898-f9b9a1d25a03%40geenhuizen.net.

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

[Pete Geenhuizen]

OK so now I'm a little confused, is/will V4 support WH23xx?  I'm using 
it now and if it won't work under V4 then I should forgo my planned 
upgrade to V4 right?


On 2020-05-02 11:30, Tom Keffer wrote:
Believe me, I'm mighty tempted to trim the list of supported weather 
stations!


On Sat, May 2, 2020 at 7:29 AM Jever Hägen > wrote:


Thanks for thinking about of doing that work.

yes, there are not very much wh23xx stations registered beside mine.
But overall they are on rank 9 ;-)
1   Vantage 537
2   FineOffsetUSB   274
3   AcuRite 147
4   Interceptor 87
5   TE923   67
6   WMR100  40
7   SDR 33
8   WMR200  29
*9* *WH23xx**26*
10  WS23xx  24
11  WS28xx  24
12  netatmo 17
13  Ultimeter   15
14  WeatherFlowUDP  14
15  WMR300  14
16  FileParse   11
17  Simulator   11


Am Samstag, 2. Mai 2020 16:01:39 UTC+2 schrieb Tom Keffer:

The weewx usage map  shows 26
installations (out of 1471 registered stations), or less than
2%. That's not enough usage to justify the work. Get your
friends to use it!

Still, I'll see what I can do...

-tk

On Sat, May 2, 2020 at 5:30 AM Jever Hägen
 wrote:

Hi Tom,

yes I know, but wouldn't it be possible for you or some of
the guys out there to integrate the driver into weewx v4?

Am Freitag, 1. Mai 2020 23:54:16 UTC+2 schrieb Tom Keffer:

It looks like the wh23xx driver has not been ported to
Python 3 and weewx V4 (it's not actually part of weewx).

On Fri, May 1, 2020 at 9:57 AM Богдан Пилюгин
 wrote:

I had the same problem today, when weewx updated
to 4. The station is WH2310. I made a little
analyze of problem and found that import of
log_traceback in the ws23xx driver no more valid,
because of changings in weewx.
Try to replace
the string in the file wh23xx.py:
|
fromweeutil.weeutil
importtimestamp_to_string,log_traceback
|

to:
|
fromweeutil.weeutil importtimestamp_to_string
fromweeutil.log log_traceback
|

This is solved my problem.
I made pull request to the sources of this driver,
hope that it will be accepted.
-- 
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...@googlegroups.com.
To view this discussion on the web visit

https://groups.google.com/d/msgid/weewx-user/2e71df79-aa5c-40be-9d91-0231c192d70e%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...@googlegroups.com.
To view this discussion on the web visit

https://groups.google.com/d/msgid/weewx-user/e19dd0d2-f97f-4a3a-a7a9-d14b020b1dab%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/7a79fd32-daf7-4965-9af4-cb5b9160d2b4%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 

[weewx-user] Battery Alarm warnings

[Pete Geenhuizen]

At 06:20 yesterday I got my first email advising me that my VantageVue 
transmitter battery was low.


Around 1600 yesterday I replaced the battery

Since the first email I've been intermittently getting multiple emails 
like 7 emails at once for a total of 25 at various times advising that 
the battery is low.


The console stopped reporting low battery at midnight, yet I continued 
to get emails until 0544 this morning.


This is my Alarm stanza


[Alarm]
    time_wait = 3600
    count_threshold = 50
    smtp_host = mailbox
    from = xxx@
    mailto = 
    subject = Time to change the battery!

This is what is in the weewx.log

Feb  8 00:06:52 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 00:06:53 EST (1549602413): {'txBatteryStatus': 1}
Feb  8 01:06:53 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 01:06:53 EST (1549606013): {'txBatteryStatus': 1}
Feb  8 02:06:55 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 02:06:55 EST (1549609615): {'txBatteryStatus': 1}
Feb  8 03:06:55 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 03:06:55 EST (1549613215): {'txBatteryStatus': 1}
Feb  8 03:56:53 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 03:56:53 EST (1549616213): {'txBatteryStatus': 1}
Feb  8 04:56:55 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 04:56:55 EST (1549619815): {'txBatteryStatus': 1}
Feb  8 05:56:55 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 05:56:55 EST (1549623415): {'txBatteryStatus': 1}
Feb  8 06:56:55 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 06:56:56 EST (1549627016): {'txBatteryStatus': 1}
Feb  8 07:56:57 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 07:56:58 EST (1549630618): {'txBatteryStatus': 1}
Feb  8 08:56:57 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 08:56:58 EST (1549634218): {'txBatteryStatus': 1}
Feb  8 09:56:57 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 09:56:58 EST (1549637818): {'txBatteryStatus': 1}
Feb  8 10:56:58 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 10:56:58 EST (1549641418): {'txBatteryStatus': 1}
Feb  8 11:57:00 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 11:57:00 EST (1549645020): {'txBatteryStatus': 1}
Feb  8 12:57:00 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 12:57:00 EST (1549648620): {'txBatteryStatus': 1}
Feb  8 13:57:00 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 13:57:00 EST (1549652220): {'txBatteryStatus': 1}
Feb  8 14:57:02 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 14:57:02 EST (1549655822): {'txBatteryStatus': 1}
Feb  8 15:57:02 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 15:57:02 EST (1549659422): {'txBatteryStatus': 1}
Feb  8 16:57:02 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 16:57:03 EST (1549663023): {'txBatteryStatus': 1}
Feb  8 17:57:04 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 17:57:05 EST (154925): {'txBatteryStatus': 1}
Feb  8 18:57:04 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 18:57:05 EST (1549670225): {'txBatteryStatus': 1}
Feb  8 19:57:04 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 19:57:05 EST (1549673825): {'txBatteryStatus': 1}
Feb  8 20:57:06 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 20:57:07 EST (1549677427): {'txBatteryStatus': 1}
Feb  8 21:57:06 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 21:57:07 EST (1549681027): {'txBatteryStatus': 1}
Feb  8 22:57:07 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 22:57:07 EST (1549684627): {'txBatteryStatus': 1}
Feb  8 23:57:09 X weewx[4326]: lowBattery: Low battery status 
sounded at 2019-02-08 23:57:09 EST (1549688229): {'txBatteryStatus': 1}

By my figuring I shouldn't have gotten any more emails after midnight.

So is this an extremely minor bug or have I configured something 
incorrectly?


This is weewx 3.8 running on Centos 7.5

Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx-multi on RHEL

[Pete Geenhuizen]

Hmm that is much more complicated than my setup which consists of a 
computer running C7 which has a Davis VantageVue and a LaCross WS 
attached and sends the info via rsync to my web server.


Wouldn't you have the same problem with the weewx-multi script? I just 
never could get all the parameters worked out and merely split the 
weewx-multi into 2 separate start scripts.



On 05/25/2018 02:50 PM, bdf0506 wrote:

Bummer. But thanks for sharing.

I haven't tried this yet with two separate scripts. I think I am going 
to have issues when I do this because of the interceptor driver I am 
using for the Acurite smarthub. I have it set to listed on 8080 
(traffic is redirected from port 80). I'll be able to start the first 
instance just fine (to listen on 8080), but when I start the second, I 
will have a problem since the second will say that something is 
already listening on port 8080. I'll mess with that this weekend, but 
perhaps someone else here has experience with this.


On Friday, May 25, 2018 at 2:46:59 PM UTC-4, pgeenhuizen wrote:


On 05/25/2018 12:57 PM, bdf0506 wrote:

Once you change the paths, comment out some of the files that
aren't found, still fails as suchclearly you can't comment
out some of the files and expect it to work since it has
refrences later in the script to the commented out files.

[root@server01 init.d]$ service weewx stop
/etc/init.d/weewx: line 176: log_daemon_msg: command not found
/etc/init.d/weewx: line 179: log_end_msg: command not found
/etc/init.d/weewx: line 176: log_daemon_msg: command not found
/etc/init.d/weewx: line 179: log_end_msg: command not found

On Friday, May 25, 2018 at 12:51:31 PM UTC-4, bdf0506 wrote:

If you go through the setup here:
http://www.weewx.com/docs/redhat.htm


Then weewx-multi simply will not work (though weewx in single
mode will work just fine).

Anyone know the trick to make it work? I have modified the
weewx-multi script a bit to modify the locations of the
paths, but I still fail to find things like /var/lib/vars.sh
and don't even have those files available. Any ideas?

-- 


I tried and gave up on the multi start up and just created 2 init
scripts and now have 2 systemd scripts.
Pete

-- 
Unencumbered by the thought process.

  -- Click and Clack the Tappet brothers


-- 
This message has been scanned for viruses and

dangerous content by *MailScanner* ,
and is
believed to be clean.

--
You received this message because you are subscribed to the Google 
Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to weewx-user+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.

--
This message has been scanned for viruses and
dangerous content by *MailScanner* , and is
believed to be clean. 


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx-multi on RHEL

[Pete Geenhuizen]

On 05/25/2018 12:57 PM, bdf0506 wrote:
Once you change the paths, comment out some of the files that aren't 
found, still fails as suchclearly you can't comment out some of 
the files and expect it to work since it has refrences later in the 
script to the commented out files.


[root@server01 init.d]$ service weewx stop
/etc/init.d/weewx: line 176: log_daemon_msg: command not found
/etc/init.d/weewx: line 179: log_end_msg: command not found
/etc/init.d/weewx: line 176: log_daemon_msg: command not found
/etc/init.d/weewx: line 179: log_end_msg: command not found

On Friday, May 25, 2018 at 12:51:31 PM UTC-4, bdf0506 wrote:

If you go through the setup here:
http://www.weewx.com/docs/redhat.htm


Then weewx-multi simply will not work (though weewx in single mode
will work just fine).

Anyone know the trick to make it work? I have modified the
weewx-multi script a bit to modify the locations of the paths, but
I still fail to find things like /var/lib/vars.sh and don't even
have those files available. Any ideas?

--


I tried and gave up on the multi start up and just created 2 init 
scripts and now have 2 systemd scripts.

Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Error reading lock file /etc/weewx/.weewx.conf.swp: Not enough data read

[Pete Geenhuizen]

When you edit a file with  vi, which is actually a link to vim, it 
creates a backup file in your case .weewx.conf.swp. because it has a dot 
in front of the name the best way to see it is by using ls -la


When you save the file and exit vi the .filename.swpis removed, if 
however you kill the vi session or exit it any other abnormal way the 
.filename.swp file won't be removed.


You have 2 options simply remove the file or if you have some changes in 
the file that you want to recover then the best option is to recover the 
file which will have all the changes that you made in your last edit.  
To recover the last edits use vi -r save the file exit vi and then 
remove the .filename.swp file.


Like I said, to avoid this from happening always properly end the vi 
session.


Other than that it sounds like you are dealing with permission/ownership 
error, in that case check both the original file and the .filename.swp 
ownership.


I hope that this helps

Pete

On 04/07/18 15:44, Kimberly Olsen wrote:
and when I look for weewx.conf.swp, it doesn't exist...no nothing 
strange here ;-)




On Saturday, 7 April 2018 12:48:18 UTC+10, Kimberly Olsen wrote:

I've been attempting to get ftp working this morning and suddenly
when attempting to edit weewx.conf, I get the message below

This is when I am ssh-ing in from my Mac.
When I attempt to edit the file directly on the pi, I cannot save it

Any ideas ?

Error reading lock file /etc/weewx/.weewx.conf.swp: Not enough
data read

--
You received this message because you are subscribed to the Google 
Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to weewx-user+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.

--
This message has been scanned for viruses and
dangerous content by *MailScanner* , and is
believed to be clean. 


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Serial connection problem

[Pete Geenhuizen]

Thanks for the info, I've ordered a couple of cables from Monoprice and 
hopefully one of them will work, but I sure would prefer to get the 
serial cards working.


Pete


On 02/03/18 16:23, mwall wrote:

On Monday, January 29, 2018 at 7:46:47 AM UTC-5, pgeenhuizen wrote:


If I can't resolve this issue I'll have to look at alternatives,
and one
thing that comes to mind is to use a serial to USB converter.
Question
is does anyone have a recommendation as to which ones work?


the have been reliable for me:

https://www.amazon.com/IOGEAR-Serial-RS-232-Adapter-GUC232A/dp/B67VB7/

i have used these as well, but they have not worked with every device:

https://www.amazon.com/dp/B00J4N9T9C/

m
--
You received this message because you are subscribed to the Google 
Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to weewx-user+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.

--
This message has been scanned for viruses and
dangerous content by *MailScanner* , and is
believed to be clean. 


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Serial connection problem

[Pete Geenhuizen]

I'm in the process of upgrading from Centos 6 to Centos 7 with an add-on 
dual port PCI card.


Centos 7 recognizes and creates all the appropriate devices.  If I 
connect to ttyS0 which is on the motherboard, all works as advertised, 
however if I connect to either ttyS1 or ttyS2 which are on the add-on 
PCI serial card nothing happens.


Over the years I've suffered several near miss lightening strikes which 
have taken out the serial card which is preferable to taking out the 
mother board.


If I can't resolve this issue I'll have to look at alternatives, and one 
thing that comes to mind is to use a serial to USB converter. Question 
is does anyone have a recommendation as to which ones work?


As a last resort I suppose I could get a USB data logger, but I'd rather 
not have to buy a new logger if I can possibly avoid it.


Thanks
Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Exfoliation errors

[Pete Geenhuizen]

On 01/27/18 11:18, mwall wrote:

On Saturday, January 27, 2018 at 11:05:37 AM UTC-5, pgeenhuizen wrote:


Well now I have a new error
an 27 10:48:52 host weewx[26967]: cheetahgenerator:  Ignoring
template /etc/weewx/skins/forecast/single-strip-vertical.html.tmpl
Jan 27 10:48:52 host weewx[26967]: cheetahgenerator:  Ignoring
template /etc/weewx/skins/forecast/iconic-horizontal.html.tmpl
Jan 27 10:48:52host weewx[26967]: cheetahgenerator:  Ignoring
template /etc/weewx/skins/forecast/tides-graphic.html.tmpl


and now i remember why i did not publicize the forecast 3.2.18 release :)

forecast 3.2.19 has the single-strip-vertical and iconic-horizontal 
pages (3.2.18 has them, but they were not in the install.py 
configuration).


iconic works.  vertical strip still has css issues.  the graphic tide 
display is not ready yet, so i have excluded that from the 3.2.19 
release, but the generator should not fail now.


m


Matt,
That did it.
I see that you changed the strip from horizontal to vertical.  I'm not 
sure which I prefer, the vertical is easier to read, but the horizontal 
was more compact, and doesn't require scrolling.  Could you make 
orientation an option on the strip page?


Not sure about this one.  Right now when I look at the Weather 
Underground iconic view it shows Sat, Sun and Mon and nothing for Wed, 
Thurs and Fri.  When I look at the Table and the strip they both show a 
forecast for Sat - Thurs


Lastly and this might my foul up on the main page under the FORECAST 
heading, I only see the forecast for the current day and only for 
Weather Underground.


None of the above is a show stopper and are merely my observations, my 
main concern were the errors which are now fixed.


Once again thanks for your help and quick response.
Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Exfoliation errors

[Pete Geenhuizen]

On 01/27/18 09:44, mwall wrote:



On Saturday, January 27, 2018 at 9:36:55 AM UTC-5, pgeenhuizen wrote:

Speaking of updating extensions, I've often wonder what is the
best procedure/practice?
remove the existing extension and then install the new one?
Install the new extension then remove the old one?
Install the new extension and nothing more?


just install the new version.  the extension installer will snapshot 
the older version, which is nice if you want to roll back (rollback 
requires manual intervention.  pull requests to make rollback and 
revision-listing part of the wee_extension command-line options would 
be welcome!)


thank you for the 'wee_extension --list'

that is exactly what i was going for, and it makes clear what you have 
installed


m


You're welcome to the list and I'll let you know how it goes.
Thanks for your quick response and help.
Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Exfoliation errors

[Pete Geenhuizen]

On 01/27/18 09:28, mwall wrote:



On Saturday, January 27, 2018 at 9:21:37 AM UTC-5, pgeenhuizen wrote:


Matt,
No apologies needed, these things happen, I'm only too happy to
get a timely response.
This is a test setup, so I'm willing to go either way, what would
you prefer that I do?
Pete


go ahead an update to the latest versions

Speaking of updating extensions, I've often wonder what is the best 
procedure/practice?

remove the existing extension and then install the new one?
Install the new extension then remove the old one?
Install the new extension and nothing more?

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Exfoliation errors

[Pete Geenhuizen]

On 01/27/18 09:12, mwall wrote:

pete,

i seem to have gotten undisciplined in my releases.  i did apply a fix 
for this, but it is un an unpublished release.  my apologies!


the behavior you see happens only when the *remaining* daily high and 
low are the same (often at the end of the day)


you can patch by doing this in forecast_iconic.inc:

at line 97 insert a line to change this:

#set $range_width = 0

#if $summary.tempMin.raw is not None and $summary.tempMax.raw is not None


to this:

#set $range_width = 0

#set $trailing_width = 0

#if $summary.tempMin.raw is not None and $summary.tempMax.raw is not None


and around line 155 insert a line to change this:

#set $range_height = 0

#if $summary.tempMin.raw is not None and $summary.tempMax.raw is not None


to this:

#set $range_height = 0

#set $trailing_height = 0

#if $summary.tempMin.raw is not None and $summary.tempMax.raw is not None


or you can install exfoliation 0.44 and forecast 3.2.18

(i have been battling some css quirks in the vertical orientation of 
the 'strip' forecast display, and so far i am losing that battle)


m


Matt,
No apologies needed, these things happen, I'm only too happy to get a 
timely response.
This is a test setup, so I'm willing to go either way, what would you 
prefer that I do?

Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Exfoliation errors

[Pete Geenhuizen]

On 01/27/18 08:51, mwall wrote:
sorry, i see that you posted the versions.  i thought this was fixed 
some time ago.  can we confirm that you are actually running 0.43 
exfoliation?

--


Is this what you need?

/usr/bin/wee_extension --list
Extension Name    Version   Description
lastrain  0.1   SLE for last rain information for weewx reports
StackedWindRose   2.1.0 Stacked windrose image generator for weeWX.
forecast  3.2.17    Generate and display weather and tide forecasts.
exfoliation   0.43  A minimalist layout with lots of data.

And this from the web page

weewx: 0 days, 15 hours, 15 minutes
server: 0 days, 21 hours, 19 minutes
weewx 3.8.0 with LaCrosse WS23xx and exfoliation 0.43

Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Exfoliation errors

[Pete Geenhuizen]

I guess that this is a question for Matt.

I am in the process of upgrading my weewx installation from

Centos 6 to Centos 7

weewx    3.6.2-1 to 3.8.0-1

forecast  3.2.13 to 3.2.17

exfoliation   0.39 to 0.43

So far everything is working as expected however I see these errors in 
the log


cheetahgenerator:  Reason: cannot find 'trailing_height'

cheetahgenerator:  Reason: cannot find 'trailing_width'

The errors tend to show up late at night around 10 pm Eastern and cease 
around 6 am.


I've attached a snippet from the log.

Any one else seeing these errors and if so what do I need to do to 
eliminate them?


Thanks

Pete


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


weewx-errs.gz
Description: application/gzip

Re: [weewx-user] Re: forecast extension NWS error

[Pete Geenhuizen]

Matt,
Thanks for the quick fix, worked like a charm, appreciate it.
Pete


On 02/09/17 19:50, mwall wrote:

pete,

please update to forecast 3.2.13

there must have been something about the forecast on 7 feb, because 
the current forecast for RAH/NCZ041 is not causing the problem.


i did some minor refactoring and added some logging, so if it happens 
again you'll get a log message and the forecast service will not crap out.


the log message is "NWS: mode unset for label 'xxx'" where xxx is the 
label in the nws forecast that is causing the problem.


m


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: forecast extension NWS error

[Pete Geenhuizen]

   [[NWS]]
lid = NCZ041
foid = RAH

The first failure was Feb 7 @ 07:14


On 02/09/17 18:00, mwall wrote:

On Thursday, February 9, 2017 at 4:37:15 PM UTC-5, pgeenhuizen wrote:

Here's a snippet from the log which hopefully is sufficient, if
not let
me know what else you need.


what is your location identifier?

--
You received this message because you are subscribed to the Google 
Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to weewx-user+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] forecast extension NWS error

[Pete Geenhuizen]

Oops my bad I upgraded to forecast-3.2.12.


On 02/09/17 16:37, Pete Geenhuizen wrote:

Matt,

For the past few days I've been getting an error downloading forecasts 
from NWS.  I just upgraded to forecast 0.40 to see if that solved the 
problem but alas it doesn't.


Here's a snippet from the log which hopefully is sufficient, if not 
let me know what else you need.


Feb  9 16:30:16 host weewx[562]: forecast: NWSThread: NWS: downloading 
forecast from 
'http://forecast.weather.gov/product.php?site=NWS=PFM=txt=RAH'
Feb  9 16:30:16 host weewx[562]: forecast: NWSThread: NWS: forecast 
failure: local variable 'mode' referenced before assignment

Feb  9 16:30:16 host weewx[562]: Traceback (most recent call last):
Feb  9 16:30:16 host weewx[562]:   File 
"/usr/share/weewx/user/forecast.py", line 1177, in do_forecast

Feb  9 16:30:16 host weewx[562]: self.config_dict['DataBindings'],
Feb  9 16:30:16 host weewx[562]:   File 
"/usr/share/weewx/user/forecast.py", line 1679, in get_forecast
Feb  9 16:30:16 host weewx[562]: logerr('%s: no PFM found for %s 
in forecast from %s' %
Feb  9 16:30:16 host weewx[562]:   File 
"/usr/share/weewx/user/forecast.py", line 1790, in NWSParseForecast

Feb  9 16:30:16 host weewx[562]: mode = 3
Feb  9 16:30:16 host weewx[562]: UnboundLocalError: local variable 
'mode' referenced before assignment


Thanks

Pete




--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Version 3.6.0 failure

[Pete Geenhuizen]

Thanks Matt, that did it.

I did a diff of the 2 conf files, but missed that one.

With that in mind is there a way to make changes like this to the 2 
config files when upgrading weewx?



Pete


On 10/08/16 12:53, mwall wrote:

On Saturday, October 8, 2016 at 12:48:05 PM UTC-4, pgeenhuizen wrote:

 in the config file for the lacross, change this:

[StdWXCalculate]
pressure = prefer_hardware
...

to this:

[StdWXCalculate]
[[Calculations]]
pressure = prefer_hardware
...

the upgrade process does not know about multiple weewx configuration 
files, so it probably did this to your vantage config (is it called 
weewx.conf?) but did not do it to your lacross config (what is it called?)


m


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Windrose with weewx

[Pete Geenhuizen]

I installed it on Centos 6 without any issues.


Pete


On 08/09/16 03:43, gjr80 wrote:
Hmm, seems the the extension installer is having conniptions for some 
reason. I am confident the extension itself is good, I know of at 
least one other person who has had no problems installing with 
wee_extension. I have had it install correctly, but on two occassions 
(including just now) I have had the same error. Let me look into the 
error, if I cannot figure it out this evening it might be best for you 
to do a manual install. If possible it is worthwhile installing 
extensions with the extension installer - it makes their management 
much easier.


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 
.

For more options, visit https://groups.google.com/d/optout.


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers

--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.