[weewx-user] Error message with WeeWX-Saratoga extension after weewx 4.6.0 upgrade

[Al]

Immediately after upgrading to weewx 4.6.0 I am getting the following 
errors:


Feb 06 17:00:27 p4-1 weewxd[17341]: weewx[17341] ERROR 
weewx.cheetahgenerator: Evaluation of template 
/opt/weewx/skins/WEEWXtags/WEEWXtags.php.tmpl failed with exception 
''
Feb 06 17:00:27 p4-1 weewxd[17341]: weewx[17341] ERROR 
weewx.cheetahgenerator:  Ignoring template 
/opt/weewx/skins/WEEWXtags/WEEWXtags.php.tmpl
Feb 06 17:00:27 p4-1 weewxd[17341]: weewx[17341] ERROR 
weewx.cheetahgenerator:  Reason: 'trend'
Feb 06 17:00:27 p4-1 weewxd[17341]: weewx[17341] ERROR 
weewx.cheetahgenerator:   Traceback (most recent call last):
Feb 06 17:00:27 p4-1 weewxd[17341]: weewx[17341] ERROR 
weewx.cheetahgenerator: File 
"/opt/weewx/bin/weewx/cheetahgenerator.py", line 344, in generate
Feb 06 17:00:27 p4-1 weewxd[17341]: weewx[17341] ERROR 
weewx.cheetahgenerator:   unicode_string = 
compiled_template.respond()
Feb 06 17:00:27 p4-1 weewxd[17341]: weewx[17341] ERROR 
weewx.cheetahgenerator: File 
"_opt_weewx_skins_WEEWXtags_WEEWXtags_php_tmpl.py", line 669, in respond
Feb 06 17:00:27 p4-1 weewxd[17341]: weewx[17341] ERROR 
weewx.cheetahgenerator: File "/opt/weewx/bin/weewx/tags.py", 
line 65, in trend
Feb 06 17:00:27 p4-1 weewxd[17341]: weewx[17341] ERROR 
weewx.cheetahgenerator:   time_grace = 
to_int(self.option_dict['trend'].get('time_grace', 300))
Feb 06 17:00:27 p4-1 weewxd[17341]: weewx[17341] ERROR 
weewx.cheetahgenerator:   KeyError: 'trend'
Feb 06 17:00:27 p4-1 weewxd[17341]: weewx[17341] INFO 
weewx.cheetahgenerator: Generated 0 files for report WEEWXtagsReport in 
3.30 seconds
Feb 06 17:00:27 p4-1 weewxd[17341]: weewx[17341] ERROR weewx.restx: 
Wunderground-PWS: Failed to publish record 2022-02-06 17:00:00 PST 
(1644195600): Failed upload after 3 tries


WEEWXtags.php.tmpl is the latest version (0.1.2, 25 November 2021)

Any ideas as to a fix?

Thanks,

Al

--
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/a869600c-4d50-ecd9-3834-a2f086d1abd8%40gmail.com.

Re: [weewx-user] Error message with WeeWX-Saratoga extension after weewx 4.6.0 upgrade

[Al]

Thanks Tom and Gary.

For now I'll just go back to the previous weewx version and wait this 
out. I have a full backup from this morning taken just before I upgraded.


For reference, there is no 'since.py' on my installation.

Al

gjr80 wrote:
This will be due to some errant behaviour in one of the WeeWX-Saratoga 
SLEs that most likely has some of the characteristics of the since.py 
issue. I will need to work through and fix and will update 
WeeWX-Saratoga in due course.


Gary

On Monday, 7 February 2022 at 11:39:08 UTC+10 tke...@gmail.com wrote:

Are you using the extension "since"?


--
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/bad09c6c-a157-f884-a8e9-165045084b9c%40gmail.com.

Re: [weewx-user] Error message with WeeWX-Saratoga extension after weewx 4.6.0 upgrade

[Al]

gjr80 wrote:
Turns out I had fixed the 'trend' issue a month ago but never built and 
published the release, my apologies.


I have published v0.1.3 
<https://github.com/gjr80/weewx-saratoga/releases/tag/v0.1.3> which 
fixes this plus one other issue.


Thanks Gary! after updating all is well.

Al

--
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/631e55ba-076f-801b-5663-ddd739f5293a%40gmail.com.

[weewx-user] Belchertown Skin Highchart Rounding Battery Values

[Al P]

I have had weewx installed for a week or so, and loving it.
I've started playing with Belchertown and like the look of it, but I've hit 
a minor problem.

I would like to chart a voltage value to 3 decimal places. Why you ask? 
Because I've recently installed a WeatherFlow Tempest in an overcast 
climate and I really want to see how much/little sunshine it takes for it 
to charge!

I have the sensor value mapped to supplyVoltage, and have created a chart 
in the Seasons skin that shows the precision I'm looking for, but when 
using the same field in the Belchertown charts it only ever shows to 2 
decimal places.
The value definitely has 3 decimal places, I have printed the current value 
to my footer.

Anyone able help me find where it does this?

Cheers,
 Alan

-- 
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/c3df9092-7a04-4d86-9211-da55b57c4484n%40googlegroups.com.

[weewx-user] Re: Belchertown Skin Highchart Rounding Battery Values

[Al P]

Yep, I can see 3 digits in the UDP packets, and as I mentioned I can see 
the 3 digits in the chart in the seasons skin. I've also added the current 
value to my footer and can see the 3 digits there. It's only in the chart 
that it seems to round to 2 digits. The stringformat is already %.3f for 
the rest of it to work.

On Wednesday, 23 December 2020 at 19:51:13 UTC vince wrote:

> On Wednesday, December 23, 2020 at 8:28:11 AM UTC-8 Al P wrote:
>
>> I would like to chart a voltage value to 3 decimal places. Why you ask? 
>> Because I've recently installed a WeatherFlow Tempest in an overcast 
>> climate and I really want to see how much/little sunshine it takes for it 
>> to charge!
>>
>>
> Are you 'sure' the unit reports to three decimal points ?
> My recollection is WF gear only reports to two (but my memory might be 
> hazy).
>
> Remember, an archive record is an average of the data received over that 
> archive period, so the average of a 2-digit actual measurement will seem to 
> be a many-digit value.
>
> But that said, if you look in skin.conf you will see a section called 
> StringFormats where you can set it to any number of digits you want.
>
>

-- 
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/94dc8486-03e4-497f-8083-7547f5d32ff8n%40googlegroups.com.

[weewx-user] Re: Belchertown Skin Highchart Rounding Battery Values

[Al P]

I may have found what was causing this, but I'm not entirely certain.
I think line 2442
usage_round = int(self.skin_dict['Units']['StringFormats'].get(obs_vt[2], 
"2f")[-2]) 
maybe should be
usage_round = int(self.skin_dict['Units']['StringFormats'].get(obs_vt[1], 
"2f")[-2])

because obs_vt[2] appears to show the observation group
and obs_vt[1] the observation type

It's working for me and doesn't seem to have broken anything. 


On Wednesday, 23 December 2020 at 20:08:38 UTC Al P wrote:

> Yep, I can see 3 digits in the UDP packets, and as I mentioned I can see 
> the 3 digits in the chart in the seasons skin. I've also added the current 
> value to my footer and can see the 3 digits there. It's only in the chart 
> that it seems to round to 2 digits. The stringformat is already %.3f for 
> the rest of it to work.
>
> On Wednesday, 23 December 2020 at 19:51:13 UTC vince wrote:
>
>> On Wednesday, December 23, 2020 at 8:28:11 AM UTC-8 Al P wrote:
>>
>>> I would like to chart a voltage value to 3 decimal places. Why you ask? 
>>> Because I've recently installed a WeatherFlow Tempest in an overcast 
>>> climate and I really want to see how much/little sunshine it takes for it 
>>> to charge!
>>>
>>>
>> Are you 'sure' the unit reports to three decimal points ?
>> My recollection is WF gear only reports to two (but my memory might be 
>> hazy).
>>
>> Remember, an archive record is an average of the data received over that 
>> archive period, so the average of a 2-digit actual measurement will seem to 
>> be a many-digit value.
>>
>> But that said, if you look in skin.conf you will see a section called 
>> StringFormats where you can set it to any number of digits you want.
>>
>>

-- 
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/51541257-68fe-4dc1-b100-ee95851c486dn%40googlegroups.com.

[weewx-user] Saratoga extension unhappy with Feb 29th

[Al Barnes]

I just noticed that today my logs are filled with messages every cycle 
complaining about the date:


 ValueError: day is out of range for month

Full log attached

Al

--
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/2d017b19-7009-4151-a87e-b91515d990eb%40gmail.com.
Feb 29 16:18:55 p5-1 systemd[1]: Started weewx.service - WeeWX weather system.
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO __main__: Initializing weewxd version 
5.0.2
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO __main__: Command line: 
/home/al/venv-weewx/lib/python3.11/site-packages/weewxd.py 
/home/al/weewx-data/weewx.conf
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO __main__: Using Python 3.11.2 (main, 
Mar 13 2023, 12:18:29) [GCC 12.2.0]
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO __main__: Located at 
/home/al/venv-weewx/bin/python3
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO __main__: Platform 
Linux-6.1.0-rpi8-rpi-2712-aarch64-with-glibc2.36
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO __main__: Locale: 'en_US.UTF-8'
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO __main__: Entry path: 
/home/al/venv-weewx/lib/python3.11/site-packages/weewxd.py
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO __main__: WEEWX_ROOT: 
/home/al/weewx-data
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO __main__: Configuration file: 
/home/al/weewx-data/weewx.conf
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO __main__: User module: 
/home/al/weewx-data/bin/user
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO __main__: Debug: 0
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO weewx.engine: Loading station type 
Vantage (weewx.drivers.vantage)
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO weewx.engine: StdConvert target unit is 
0x1
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO weewx.wxservices: StdWXCalculate will 
use data binding wx_binding
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO user.ws: WsWXCalculate version 0.1.8
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO user.ws: WsWXCalculate sunshine 
threshold: 120
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO user.ws: pyephem was detected
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO weewx.engine: Archive will use data 
binding wx_binding
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO weewx.engine: Record generation will be 
attempted in 'hardware'
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO weewx.engine: Using archive interval of 
300 seconds (specified by hardware)
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO user.ws: WsArchive version 0.1.8
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO user.ws: Using binding 'ws_binding' to 
database 'weewxwd.sdb'
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO user.ws: Starting backfill of daily 
summaries
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO weewx.manager: Starting backfill of 
daily summaries
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO weewx.manager: Daily summaries up to 
date
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO user.ws: Daily summaries up to date.
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO weewx.restx: StationRegistry: Station 
will be registered.
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO weewx.restx: Wunderground-PWS: Data for 
station KWASEATT52 will be posted
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO weewx.restx: PWSWeather: Data for 
station CW6259 will be posted
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO weewx.restx: CWOP: Data for station 
CW6259 will be posted
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO weewx.restx: WOW: Data for station 
ff36fec3-c199-e911-80e7-0003ff59889d will be posted
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO weewx.restx: AWEKAS: Data will be 
uploaded for user *
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO user.mqtt: service version is 0.24
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO user.mqtt: binding to archive, loop
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO user.mqtt: data_binding is wx_binding
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO user.mqtt: topic is weather
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO user.mqtt: desired unit system is US
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO user.mqtt: data will be uploaded to 
mqtt://*:xxx@192.81.132.82:1883
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO weewx.engine: 'pyephem' detected, 
extended almanac data is available
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO user.rtcr: RealtimeClientraw version 
0.3.7
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO user.rtcr: RealtimeClientraw will 
generate /home/al/weewx-data/public_html/clientraw.txt
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO user.rtcr: min_interval is 10 seconds
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO user.rtcr: clientraw.txt will be posted 
to https://radiex.com/wx/saratoga/post_clientraw.php by HTTP POST
Feb 29 16:18:56 p5-1 weewxd[5537]: INFO __main__: Starting up weewx version 
5.0.2
Feb 29 16:18:57 p5-1 weewxd[5537]: INFO weewx.engine: Clock error is 1.76 
seconds (positive is fast)

Re: [weewx-user] Re: Saratoga extension unhappy with Feb 29th

[Al Barnes]

Thanks Gary! Now working fine after updating to 0.1.9.

Al


gjr80 wrote:
Was fixed in release 0.1.9 
<https://github.com/gjr80/weewx-saratoga/releases/tag/v0.1.9>.


Gary

On Friday 1 March 2024 at 10:48:13 UTC+10 vanilla...@gmail.com wrote:

I just noticed that today my logs are filled with messages every cycle
complaining about the date:

ValueError: day is out of range for month

Full log attached

Al

--
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/60887087-3954-4072-bbfa-ef78a75eb4cfn%40googlegroups.com <https://groups.google.com/d/msgid/weewx-user/60887087-3954-4072-bbfa-ef78a75eb4cfn%40googlegroups.com?utm_medium=email&utm_source=footer>.


--
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/8763f43f-551a-41bc-a768-144e2f76ecee%40gmail.com.

Re: [weewx-user] Error message with WeeWX-Saratoga extension after weewx 4.6.0 upgrade

[Big Al]

OK, I'll stick with 4.6.0 and await your update.

Al

On Sunday, February 6, 2022 at 7:29:54 PM UTC-8 gjr80 wrote:

> Hang on, gives about 15 minutes and I will have the new version published.
>
> Gary
> On Monday, 7 February 2022 at 13:22:06 UTC+10 vanilla...@gmail.com wrote:
>
>> Thanks Tom and Gary.
>>
>> For now I'll just go back to the previous weewx version and wait this 
>> out. I have a full backup from this morning taken just before I upgraded.
>>
>> For reference, there is no 'since.py' on my installation.
>>
>> Al
>>
>> gjr80 wrote:
>> > This will be due to some errant behaviour in one of the WeeWX-Saratoga 
>> > SLEs that most likely has some of the characteristics of the since.py 
>> > issue. I will need to work through and fix and will update 
>> > WeeWX-Saratoga in due course.
>> > 
>> > Gary
>> > 
>> > On Monday, 7 February 2022 at 11:39:08 UTC+10 tke...@gmail.com wrote:
>> > 
>> > Are you using the extension "since"?
>>
>>

-- 
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/43c8c129-a7a0-4cf7-8eff-639de593c721n%40googlegroups.com.

Re: [weewx-user] Uptime in seconds with v4.10.0?

[Al Barnes]

Tom Keffer wrote:
It's worth reading the Upgrade Guide: /Breaking changes for skins that 
use delta time/ 
<http://www.weewx.com/docs/upgrading.htm#Breaking_changes_for_skins_that_use_delta_times>


Looking at this, the example in the upgrade guide for 
Seasons/celestial.inc shows no difference between the before and after.


Using the latest celestial.inc from git results in Total daylight being 
displayed in seconds.


Al

--
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/98c9400d-3806-328c-eecb-d9711e6f47d6%40gmail.com.

Re: [weewx-user] Uptime in seconds with v4.10.0?

[Al Barnes]

Tom Keffer wrote:

Thanks for catching these!

Fixed in commit b6d8057 
.



That was quick! I copied the updated celestial.inc to my current weewx 
skins/Seasons directory and everything is perfect now.


Thank you!

--
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/502bc863-5bc7-2b4a-4156-e7d19bb2d4bf%40gmail.com.

[weewx-user] Adding alternative source for a sensor data

[Jafar Al-Gharaibeh]

The humidity sensor has failed in my weather station giving 99% reading all the 
time. Is there an easy way to disable that sensor in weewx? Or better, is there 
a way to pull this data from other nearby stations?

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/98b07764-58a6-41b3-9bc3-b9e6c96edc12%40googlegroups.com.

Re: [weewx-user] Adding alternative source for a sensor data

[Jafar Al-Gharaibeh]

Thomas,

Thank you very much. I tested that and it worked. Now I get these 
fields on the generated website:

Heat Index N/A
Dewpoint N/A
Humidity N/A

Is there a way to feed humidity data from another external source so that I 
can get Heat Index and Dewpoint values calculated ? I can easily write a 
script to pull this data from weather.gov fro example and store it in a 
file to be read by weewx. Just want to know what options I have before 
gluing something together.

Thanks,
Jafar

-- 
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/547065cf-c134-4087-982e-440fb06b5d6a%40googlegroups.com.

Re: [weewx-user] Adding alternative source for a sensor data

[Jafar Al-Gharaibeh]

I have AcuRite 02064C, and yes running a Raspberry Pi Zero W.  Generated 
Website: weather.jafaral.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/6f38f100-77e2-4ba9-8262-a645fd90f89f%40googlegroups.com.

Re: [weewx-user] Adding alternative source for a sensor data

[Jafar Al-Gharaibeh]

Rich,

   Thanks for the link. Looks like it is only compatible with the new 
models where they made it easy to swap the sensor. I might still be able to 
solder this myself. I will give it a try.

Thanks again,
Jafar

-- 
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/be5f45c1-7d98-4924-a4a7-b9f6f64c67f7%40googlegroups.com.

Re: [weewx-user] Adding alternative source for a sensor data

[Jafar Al-Gharaibeh]

Rich, 

   Thanks a lot for your suggestion. The new sensor arrived earlier this 
week and I was able to install it to day. Fortunately, the replacement was 
easy. Even though my unit is listed as compatible, it does have a socketed 
sensor inside, so it was an easy plug and play. See image below - adding it 
for reference if other people have the same issue. 

Thanks,
Jafar





On Monday, December 30, 2019 at 12:39:22 PM UTC-6, Jafar Al-Gharaibeh wrote:
>
> Rich,
>
>Thanks for the link. Looks like it is only compatible with the new 
> models where they made it easy to swap the sensor. I might still be able to 
> solder this myself. I will give it a try.
>
> Thanks again,
> Jafar
>

-- 
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/94e7ab0a-aa38-41c1-9267-09c8dd4e92f7%40googlegroups.com.

Re: [weewx-user] Re: Looking for a Weewx running script

[Mohamed Al Futtan]

Thanks for your quick response. I have no fixed IP from my ISP, my DynDNS
IP is checked and updated every 5 minutes

I am running a Davice Vantage Pro with WeatherLink IP

As attached file the log and my conf file

Thanks again

2018-05-24 14:56 GMT+07:00 Andrew Milner :

> Weewx does not crash without a reason.  Believe me - it doesn't.
>
> What does the log have to say around the time of the crashes.  Fixing the
> cause of your crashes is the right way to go about fixing the problem
> rather than trying a sticky plaster approach with automated restarts.
> Automated restarts are just the wrong way to go about this - believe me.
>
> Can you tell us your station type, install method and attach a log and/or
> config file and say what skin(s) or extensions you are using.
>
> Then we can help you sort out your problems.
>
> If you are using a raspberry pi have you also checked the weewx wiki for
> advice on using weewx with a raspberry pi
>
>
> On Thursday, 24 May 2018 09:42:18 UTC+3, Mike wrote:
>>
>> Hi guys,
>>
>> my Weewx is crashing time by time.
>>
>> I am looking for a script which is checking the status of Weewx every
>> hour. In case Weewx was crashing the script is starting Weewx.
>>
>> My Linux knowledge is not the best at all. Looking like something: It
>> does not work.
>>
>> #!/bin/bash
>> #weewx check
>> if ps x | grep -v grep | grep -v checkweewx.sh | grep -c weewx >/dev/null
>> then
>> echo "weewx  ok"
>> else
>> echo ""
>> date >> /etc/weewx/weewx.fail
>> echo "weewx crashed ... restarting now" >> /usr/local/
>> sleep 1
>> /etc/init.d/weewx start
>> fi
>>
>> Thanks
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/c3NEhifi_Ro/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.conf
Description: Binary data


weewy.log
Description: Binary data

Re: [weewx-user] Re: Looking for a Weewx running script

[Mohamed Al Futtan]

Dear Andrew,

my Weewx is not running at this point, see the log file

Right now it is running, If I try to start it I am getting:

* Starting weewx weather system weewx
 *  already running...
   ...done.

which is right.

But before it was not running and it was crahing. I am pretty sure the
Dedicated server with my Domain is getting the right IP.

Any way, I have changed the wait time as you have suggested to 360 and
restarted Weewx.

Pls have a look again into my log file, I have seen 100 times the
entry with the same date/time stamp. I think it is not normal too.

May 24 00:19:11 sd-69780 weewx[1752]: vantage: Retry  #16 failed
May 24 00:19:11 sd-69780 weewx[1752]: vantage: ip-write error: [Errno
32] Broken pipe



2018-05-24 15:54 GMT+07:00 Andrew Milner :

> since you seem to be using a non-static ip connection which may not be
> known for 5 minutes (30 secs) to the weather station have you tried
> increasing the wait time to say 6 minutes (360 secs) in weewx.conf
> (currently set to 180 secs).  I'm sure this is a question of tweeking the
> timeouts and retries to make weewx cater for the fact that the ip address
> of the station has altered.
>
> Of course, if you can give the station and host addresses on an internal
> network things would improve - but you don't give the hardware / network
> setup.
>
> I'm sure many people are running watchdog scripts of some kind though.
> Your issue does not appear to be a crash from the log segment you posted
> however - since weewx is definitely still trying to establish contact with
> the station - so weewx is doing the right things.
>
> Another VP user will know the answer to this - but it seems to me that
> from a theoretical viewpoint it would be better in your situation to have
> no loop records, hardware created archive records, and only poll the
> station once every archive interval to retrieve the latest rec - and ignore
> loop data.  This would have the effect of minimising the comms with the
> station ….but I do not know if this is possible or not.
>
>
> On Thursday, 24 May 2018 11:35:17 UTC+3, Mike wrote:
>>
>> Thanks for your quick response. I have no fixed IP from my ISP, my DynDNS
>> IP is checked and updated every 5 minutes
>>
>> I am running a Davice Vantage Pro with WeatherLink IP
>>
>> As attached file the log and my conf file
>>
>> Thanks again
>>
>> 2018-05-24 14:56 GMT+07:00 Andrew Milner :
>>
>>> Weewx does not crash without a reason.  Believe me - it doesn't.
>>>
>>> What does the log have to say around the time of the crashes.  Fixing
>>> the cause of your crashes is the right way to go about fixing the problem
>>> rather than trying a sticky plaster approach with automated restarts.
>>> Automated restarts are just the wrong way to go about this - believe me.
>>>
>>> Can you tell us your station type, install method and attach a log
>>> and/or config file and say what skin(s) or extensions you are using.
>>>
>>> Then we can help you sort out your problems.
>>>
>>> If you are using a raspberry pi have you also checked the weewx wiki for
>>> advice on using weewx with a raspberry pi
>>>
>>>
>>> On Thursday, 24 May 2018 09:42:18 UTC+3, Mike wrote:

 Hi guys,

 my Weewx is crashing time by time.

 I am looking for a script which is checking the status of Weewx every
 hour. In case Weewx was crashing the script is starting Weewx.

 My Linux knowledge is not the best at all. Looking like something: It
 does not work.

 #!/bin/bash
 #weewx check
 if ps x | grep -v grep | grep -v checkweewx.sh | grep -c weewx
 >/dev/null
 then
 echo "weewx  ok"
 else
 echo ""
 date >> /etc/weewx/weewx.fail
 echo "weewx crashed ... restarting now" >> /usr/local/
 sleep 1
 /etc/init.d/weewx start
 fi

 Thanks

 --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>>> pic/weewx-user/c3NEhifi_Ro/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> weewx-user+...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/c3NEhifi_Ro/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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: Looking for a Weewx running script

[Mohamed Al Futtan]

Hi Andrew,

in case it would be run I should get this message when I try to start it:
"already running"

/etc/init.d/weewx start

* Starting weewx weather system weewx
 *  already running...
   ...done.

What I am calling a crash and I run

/etc/init.d/weewx start

I am getting, see below, so Weewx is not running and after the website is
getting

updates from the station

* Starting weewx weather system weewx
   ...done.






2018-05-24 16:46 GMT+07:00 Andrew Milner :

> I am sorry - this is NOT a crash.  Weewx is sill running and is trying and
> trying to reach your station.
>
> If you look closely at your log you will see it is logging try #1, try #2,
> try #3, try #4 and so forth.  This is not a crash - this is handling an
> error because it cannot communicate with the station.  Presumably your
> redirection is not yet up-to-date, so weewx cannot communicate with the
> station and must keep retrying.  There is nothi9ng else weewx can do until
> the connection is re-established via your redirection.
>
> Weewx is still running and trying to communicate with the station.  Why do
> you say it has crashed??
>
>
>
>
> On Thursday, 24 May 2018 12:15:09 UTC+3, Mike wrote:
>>
>> Dear Andrew,
>>
>> my Weewx is not running at this point, see the log file
>>
>> Right now it is running, If I try to start it I am getting:
>>
>> * Starting weewx weather system weewx
>>  *  already running...
>>...done.
>>
>> which is right.
>>
>> But before it was not running and it was crahing. I am pretty sure the 
>> Dedicated server with my Domain is getting the right IP.
>>
>> Any way, I have changed the wait time as you have suggested to 360 and 
>> restarted Weewx.
>>
>> Pls have a look again into my log file, I have seen 100 times the entry with 
>> the same date/time stamp. I think it is not normal too.
>>
>> May 24 00:19:11 sd-69780 weewx[1752]: vantage: Retry  #16 failed
>> May 24 00:19:11 sd-69780 weewx[1752]: vantage: ip-write error: [Errno 32] 
>> Broken pipe
>>
>>
>>
>> 2018-05-24 15:54 GMT+07:00 Andrew Milner :
>>
>>> since you seem to be using a non-static ip connection which may not be
>>> known for 5 minutes (30 secs) to the weather station have you tried
>>> increasing the wait time to say 6 minutes (360 secs) in weewx.conf
>>> (currently set to 180 secs).  I'm sure this is a question of tweeking the
>>> timeouts and retries to make weewx cater for the fact that the ip address
>>> of the station has altered.
>>>
>>> Of course, if you can give the station and host addresses on an internal
>>> network things would improve - but you don't give the hardware / network
>>> setup.
>>>
>>> I'm sure many people are running watchdog scripts of some kind though.
>>> Your issue does not appear to be a crash from the log segment you posted
>>> however - since weewx is definitely still trying to establish contact with
>>> the station - so weewx is doing the right things.
>>>
>>> Another VP user will know the answer to this - but it seems to me that
>>> from a theoretical viewpoint it would be better in your situation to have
>>> no loop records, hardware created archive records, and only poll the
>>> station once every archive interval to retrieve the latest rec - and ignore
>>> loop data.  This would have the effect of minimising the comms with the
>>> station ….but I do not know if this is possible or not.
>>>
>>>
>>> On Thursday, 24 May 2018 11:35:17 UTC+3, Mike wrote:

 Thanks for your quick response. I have no fixed IP from my ISP, my
 DynDNS IP is checked and updated every 5 minutes

 I am running a Davice Vantage Pro with WeatherLink IP

 As attached file the log and my conf file

 Thanks again

 2018-05-24 14:56 GMT+07:00 Andrew Milner :

> Weewx does not crash without a reason.  Believe me - it doesn't.
>
> What does the log have to say around the time of the crashes.  Fixing
> the cause of your crashes is the right way to go about fixing the problem
> rather than trying a sticky plaster approach with automated restarts.
> Automated restarts are just the wrong way to go about this - believe me.
>
> Can you tell us your station type, install method and attach a log
> and/or config file and say what skin(s) or extensions you are using.
>
> Then we can help you sort out your problems.
>
> If you are using a raspberry pi have you also checked the weewx wiki
> for advice on using weewx with a raspberry pi
>
>
> On Thursday, 24 May 2018 09:42:18 UTC+3, Mike wrote:
>>
>> Hi guys,
>>
>> my Weewx is crashing time by time.
>>
>> I am looking for a script which is checking the status of Weewx every
>> hour. In case Weewx was crashing the script is starting Weewx.
>>
>> My Linux knowledge is not the best at all. Looking like something: It
>> does not work.
>>
>> #!/bin/bash
>> #weewx check
>> if ps x | grep -v grep | grep -v checkweewx.sh | grep -c weewx
>>>

[weewx-user] I need help viewing the archive of Davis vantage vue + RPi3 + weewx user

[Mohamed Al-Sabri]

Hello!!

I'm completely new to the weewx, and I have been in the past 3 days 
learning and connecting my weather station to the RPi3 via Data logger usb. 
I was able to have it run and showing the current data. However, I have 
struggled in playing with the archive. I have completely no idea how to 
view or run or plot it using the SQLite3. I know there is a data base file 
called weewx.sdb but I don't know how to use it. I'm not even sure whether 
its storing data now or not!

what I know for sure, it's running and I could read the data in the 
terminal using command.. sudo weewxd weewx.conf

Any help please!

Regards,
2.6.0.0

-- 
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] I need help viewing the archive of Davis vantage vue + RPi3 + weewx user

[Mohamed Al-Sabri]

thanks Peter for the replay! yes now I do have a more clear idea of how do 
the archiving thing work!
but, still I can't get any use of it >,< What I'm able to do until now is 
just displaying the current data.

On Wednesday, February 20, 2019 at 6:17:35 PM UTC+4, Peter Fletcher wrote:
>
> I hope that you understand that the 'archive' can only go back as far as 
> the current data stored in the logger when you first connected it to weewx. 
> Even if you previously had it connected to Weatherlink, weewx has no way of 
> accessing any older data. How far the logger's data goes back in time 
> depends on the 'sample frequency' you last set. For a 5 minute sample 
> frequency, the logger will save data for a bit over 5 days before the 
> oldest data starts to be overwritten by new data. For higher and lower 
> 'sample frequencies', the time will be correspondingly shorter or longer.
>
> On Wednesday, February 20, 2019 at 1:27:35 AM UTC-6, Mohamed Al-Sabri 
> wrote:
>>
>> unfortunately, No I wasn't able to get the reports. what I'm trying is to 
>> get the archive data into a file for data analysis. maybe the reports 
>> contain some data! how can I get there?
>>
>> here is what I'm able to do til now! Just reading the current data! and I 
>> would love to able to have it in any type of file (+ archive) in a file to 
>> do some analysis using!
>>
>> I really appreciate it!
>>
>> 2.6.0.0
>>
> 2.6.0.0

-- 
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] I need help viewing the archive of Davis vantage vue + RPi3 + weewx user

[Mohamed Al-Sabri]

> 2.  You need to set your vantage archive interval to the same as what you 
> have in weewx.conf - use wee_device to change the console
>
>  

> sudo wee_device --set-interval=5
>
>
>
>
>
>  

> 2.6.0.0

>>> 2.6.0.0
>>
> 2.6.0.0

-- 
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] I need help viewing the archive of Davis vantage vue + RPi3 + weewx user

[Mohamed Al-Sabri]

Ouh OK now I understand the interval thing!
How do I know that I’m running two instances? I’m not sure how to kill one of 
them or which one I kill in order to get the data.


Mohamed,

-- 
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] I need help viewing the archive of Davis vantage vue + RPi3 + weewx user

[Mohamed Al-Sabri]

Thanks for the replay, what I'm trying to do is basically collecting 
accumulated data from the weather station and storing it into an excel file 
(or text file), it doesn't matter the way of creating the data file as long 
as the results contain the basic weather variables (OutTemp, InTemp, OutRH, 
InRH, Wind speed and direction, etc). I hope I could express what I'm 
trying to do.



Regards, 



On Monday, February 25, 2019 at 1:13:03 PM UTC+4, Andrew Milner wrote:
>
> It would help if you were much more specific!!
>
> Yes, a csv file can be created instead of a .html file by adding a new 
> 'report' using a template for example called newreport.csv.tmpl and have 
> cheetah create the file every archive interval.  Note - every archive 
> interval will keep overwriting the previous .csv however!!
>
> The database can be queried whenever you wish to create whatever file you 
> want by using any programming language or exprting the results of a query 
> issued using sqlite3.
>
> It really depends on exactly what you are trying to achive, and you are 
> being extremely vague.  There is more that one way to create files - using 
> weewx is one way, writing additional programs and scripts provide more 
> methods.  Which is more appropriate depends on the real requirement end 
> expectations.
>
>
>
>
> On Monday, 25 February 2019 10:51:49 UTC+2, Mohamed Al-Sabri wrote:
>>
>> Guys you are awesome!! I was able to generate the reports (see 
>> attachments). It was the time interval and the double instances issues! Yes 
>> I have lost data, but it worked eventually!
>>
>> However, is there anyway to store the data into a text file or excel 
>> sheet for analysis directly without going to the website step? 
>>
>>
>> Thank you so much all!!!
>>
>> On Saturday, February 23, 2019 at 12:22:46 PM UTC+4, gjr80 wrote:
>>>
>>> Ok, let's see if we can get that 1st para to make a bit of sense:
>>>
>>> This part of your log extract shows two different processes (1393 and 
>>> 1338) trying to communicate with your station, it happens if you start 
>>> WeeWX again without stopping it first or doing a restart:
>>>
>>> Gary
>>>
>>> 2.6.0.0
>>
> 2.6.0.0

-- 
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.