[weewx-user] weewx stopped logging

[Ed Wilts]

Everything seemed to be working fine with my weewx/Tempest until 
mid-February, but now nothing is logging.
The Tempest works fine and uploads to the Tempest website.
weewx appears to be working
weewx is not getting data via weatherflowudp

/var/log/weewx:

Mar 10 19:42:05 weatherpi weewx[3727]: Starting weewx weather system: weewx.
Mar 10 19:42:05 weatherpi weewx[3742] INFO weewx.restx: StationRegistry: 
Station will not be registered: no station_url specified.
Mar 10 19:42:05 weatherpi weewx[3742] INFO weewx.restx: Wunderground-PWS: 
Data for station KTXCEDAR382 will be posted
Mar 10 19:42:05 weatherpi weewx[3742] INFO weewx.restx: PWSWeather: Data 
for station Tempest57399 will be posted
Mar 10 19:42:05 weatherpi weewx[3742] INFO weewx.restx: CWOP: Data for 
station GW0498 will be posted
Mar 10 19:42:05 weatherpi weewx[3742] INFO weewx.restx: WOW: Posting not 
enabled.
Mar 10 19:42:05 weatherpi weewx[3742] INFO weewx.restx: AWEKAS: Posting not 
enabled.
Mar 10 19:42:05 weatherpi weewx[3742] INFO weewx.engine: 'pyephem' 
detected, extended almanac data is available
Mar 10 19:42:05 weatherpi weewx[3742] INFO __main__: Starting up weewx 
version 4.7.0
Mar 10 19:42:05 weatherpi weewx[3742] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Mar 10 19:42:05 weatherpi weewx[3742] INFO weewx.manager: Starting backfill 
of daily summaries
Mar 10 19:42:05 weatherpi weewx[3742] INFO weewx.manager: Daily summaries 
up to date
Mar 10 19:42:05 weatherpi weewx[3742] INFO weewx.engine: Starting main 
packet loop.
Mar 10 19:50:58 weatherpi weewx[3742] INFO __main__: Received signal TERM 
(15).
Mar 10 19:50:58 weatherpi weewx[3742] INFO weewx.engine: Main loop exiting. 
Shutting engine down.

weewx.conf:

[WeatherFlowUDP]
driver = user.weatherflowudp
log_raw_packets = False
udp_address = 
# udp_address = 0.0.0.0
# udp_address = 255.255.255.255
udp_port = 50222
udp_timeout = 90
share_socket = False

[[sensor_map]]
outTemp = air_temperature.ST-00051784.obs_st
outHumidity = relative_humidity.ST-00051784.obs_st
pressure = station_pressure.ST-00051784.obs_st
lightning_strikes = lightning_strike_count.ST-00051784.obs_st
avg_distance = lightning_strike_avg_distance.ST-00051784.obs_st
outTempBatteryStatus = battery.ST-00051784.obs_st
windSpeed = wind_speed.ST-00051784.rapid_wind
windDir = wind_direction.ST-00051784.rapid_wind
lux = illuminance.ST-00051784.obs_st
UV = uv.ST-00051784.obs_st
rain = rain_accumulated.ST-00051784.obs_st
windBatteryStatus = battery.ST-00051784.obs_st
radiation = solar_radiation.ST-00051784.obs_st
lightningXXX = distance.ST-00051784.evt_strike
lightningYYY = energy.ST-00051784.evt_strike

/var/log/syslog:

Mar 10 19:50:58 weatherpi /weewxd: weatherflowudp: MainThread: sensor map 
is {'outTemp': 'air_temperature.ST-00051784.obs_st', 'outHumidity': 
'relative_humidity.ST-00051784.obs_st', 'pressure': 
'station_pressure.ST-00051784.obs_st', 'lightning_strikes': 
'lightning_strike_count.ST-00051784.obs_st', 'avg_distance': 
'lightning_strike_avg_distance.ST-00051784.obs_st', 'outTempBatteryStatus': 
'battery.ST-00051784.obs_st', 'windSpeed': 
'wind_speed.ST-00051784.rapid_wind', 'windDir': 
'wind_direction.ST-00051784.rapid_wind', 'lux': 
'illuminance.ST-00051784.obs_st', 'UV': 'uv.ST-00051784.obs_st', 'rain': 
'rain_accumulated.ST-00051784.obs_st', 'windBatteryStatus': 
'battery.ST-00051784.obs_st', 'radiation': 
'solar_radiation.ST-00051784.obs_st', 'lightningXXX': 
'distance.ST-00051784.evt_strike', 'lightningYYY': 
'energy.ST-00051784.evt_strike'}
Mar 10 19:50:58 weatherpi /weewxd: weatherflowudp: MainThread: *** Sensor 
names per packet type
Mar 10 19:50:58 weatherpi /weewxd: weatherflowudp: MainThread: packet 
obs_air: ('time_epoch', 'station_pressure', 'air_temperature', 
'relative_humidity', 'lightning_strike_count', 
'lightning_strike_avg_distance', 'battery', 'report_interval')
Mar 10 19:50:58 weatherpi /weewxd: weatherflowudp: MainThread: packet 
obs_sky: ('time_epoch', 'illuminance', 'uv', 'rain_accumulated', 
'wind_lull', 'wind_avg', 'wind_gust', 'wind_direction', 'battery', 
'report_interval', 'solar_radiation', 'local_day_rain_accumulation', 
'precipitation_type', 'wind_sample_interval')
Mar 10 19:50:58 weatherpi /weewxd: weatherflowudp: MainThread: packet 
rapid_wind: ('time_epoch', 'wind_speed', 'wind_direction')
Mar 10 19:50:58 weatherpi /weewxd: weatherflowudp: MainThread: packet 
evt_precip: time_epoch
Mar 10 19:50:58 weatherpi /weewxd: weatherflowudp: MainThread: packet 
evt_strike: ('time_epoch', 'distance', 'energy')
Mar 10 19:50:58 weatherpi /weewxd: weatherflowudp: MainThread: packet 
obs_st: ('time_epoch', 'wind_lull', 'wind_avg', 'wind_gust', 
'wind_direction', 'wind_sample_interval', 'station_pressure', 
'air_temperature', 'relative_humidity', 'illuminance', 'uv', 
'solar_radiation', 'rain_accumulated', 

Re: [weewx-user] $day($data_binding=...).wind.avg not working

[Graham Eddy]

i hasten to clarify that those plot images are generated by the weewx instance 
that owns the gw1000 database. the other weewx instance generates html that 
only points to the existing image, but it does (try to) generate the text 
values via the tags
⊣ Graham Eddy ⊢

> On 11 Mar 2022, at 11:17 am, Graham Eddy  wrote:
> 
> the weewx instance that owns gw1000 database reports $day.wind.avg fine:
> 
> 
> 
> the weewx instance that imports gw1000 database via gw1000_binding reports 
> the ‘unrecognised’ error on $day($data_binding=‘gw1000_binding’).wind.avg. 
> however, it is fine with $day($data_binding=‘gw1000_binding’).windSpeed etc:
> 
> 
> 
> this is the html template code that (successfully) imports scalar wind data 
> and (unsuccessfully) vector wind data:
>   
> 
> 
>   Wind
>   Ave
>   $span($data_binding='gw1000_binding', 
> $day_delta=1).windSpeed.avg
>   
>   Max
>   $span($data_binding='gw1000_binding', 
> $day_delta=1).windSpeed.max
>   $span($data_binding='gw1000_binding', 
> $day_delta=1).windSpeed.maxtime.format('%H:%M %d/%m')
>   Gust
>   
>   
>   
>   Max
>   $span($data_binding='gw1000_binding', 
> $day_delta=1).windGust.max
>   $span($data_binding='gw1000_binding', 
> $day_delta=1).windGust.maxtime.format('%H:%M %d/%m')
> 
>   
>  
>   
> 
> 
>   Spd
>   Ave
>   $day($data_binding='gw1000_binding').wind.avg
>   
>   RMS
>   $day($data_binding='gw1000_binding').wind.rms
>   
>   Vec
>   Ave
>class="value">$day($data_binding='gw1000_binding').wind.vecavg
>   
>   Ave
>class="value">$day($data_binding='gw1000_binding').wind.vecdir
>   
> 
>   
> 
> 
> hopefully i’m just doing something stupid (i can fix that!)
> 
> this is on RPi 64bit bullseye (i gave up on macOS operational environment 
> long ago as too mutant and mutating further…)
> ⊣ Graham Eddy ⊢
> 
>> On 11 Mar 2022, at 2:16 am, Tom Keffer > > wrote:
>> 
>> I just tried it on my Mac and it worked fine. I even added it to the test 
>> suite (commit e907b59 
>> ).
>> 
>> Are you sure that the binding "gw1000_binding" has wind? That is, it needs a 
>> daily summary schema that includes wind.
>> 
>> 
>> On Thu, Mar 10, 2022 at 3:37 AM Graham Eddy > > wrote:
>> under 4.7.0 $day.wind.avg works fine but $day($data_binding=...).wind.avg 
>> does not. is this expected?
>> (i have not tried the latter on earlier versions.)
>> 
>> Mar 10 21:17:42 ironbark wee_reports[3057643] DEBUG weewx.cheetahgenerator: 
>> Unrecognized: $day($data_binding='gw1000_binding').wind.avg
>> 
>> 
>> 
>> -- 
>> 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/540CCCD8-0B87-4942-87EA-1EA2773D0F48%40gmail.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/CAPq0zECYBjR9a4eZgtVkLa8-7N6CMCsQyO87VziJ%2BgB1TLnZLQ%40mail.gmail.com
>>  
>> .
> 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1651A0F3-E147-4ED3-9155-D521CF989F46%40gmail.com.

Re: [weewx-user] Weewx 4.7.0 & Weewx -WD

[Stefanos Kalaitzis]

Hi Gary , 

-- how you have configured the RealtimeClientraw service:
[[RealtimeClientraw]]
   rtcr_path = /home/weewx/public_html/WD
   min_interval = 12 (i have changed this now according to your 
instructions because is my loop period)
the other values are untouched 

-- how you have configured the Saratoga templates:
untouched too now  (ajaxWEEWXwx.js is the original and virgin :P from 
weewx-plugin.zip ) 

-- how are you transferring clientraw.txt to your web server? 
I use this address  
https://northmeteo.gr/weather_stations/tagarades/index.php to post the 
clientraw.txt through remote_server_url under  [[RealtimeClientraw]] 
section 
For the other address http://tagarades-weather.epizy.com/WD/index.php i use 
the ftp report (every archive interval -2,5min) . I was wondering if we can 
put another one   remote_server_url in weewx.conf as the example:

[WeewxSaratoga]

[[RealtimeClientraw]]

   remote_server_url = htttp://one.address.com/post_clientraw.php
   remote_server_url = htttp://second.address.com/post_clientraw.php

I am still having same values for wind speed and gust speed . Have you 
looked at the saratoga WEEWXwx 
 testing page . I noticed the 
same .Sometimes  only when you manually refresh the page probably you will 
see different values  . Ofcourse sometimes are the same indeed in low wind 
conditions.

Greetings from Greece 
Stefanos  
On Thursday, March 10, 2022 at 10:55:22 AM UTC+2 gjr80 wrote:

> Dale,
>
> I am not aware of any means of having WeeWX ingest data via clientraw.txt. 
> I wouldn't be writing off fileparse either, I've never used Weather Display 
> but if I was trying to do what want I would look at using Weather Display's 
> tag system to generate a custom document/report in a format that fileparse 
> can read. The custom document/report should be fairly compact as it only 
> need contain those observations that you wish WeeWX to record. By using 
> fileparse you avoid the need to write any python code and importantly you 
> keep things simple.
>
> Gary
>
> On Thursday, 10 March 2022 at 13:26:46 UTC+10 daleea...@gmail.com wrote:
>
>> Gary, 
>>
>> Pardon me for jumping in on this thread, butseeing Weather Display and 
>> clientraw.txt terms grabbed my attention. 
>>
>> I've read through this message, and it lead me to the WeeWx-WD (end of 
>> life) and the WeeWx-Saratoga portions, which I read, and partially 
>> understand. 
>>
>> My main goal is to find some station code for WeeWx which will take my 
>> WeatherDisplay clientraw file and allow it to drive WeeWx.  I looked at 
>> this a couple years ago and was given a lead to use fileparser, but that 
>> station base code requires a observation name followed by the value; as 
>> you know clientraw.txt is just a string of numbers, which is incredibly 
>> well analyzed in one of the files on Saratoga 
>> (https://saratoga-weather.org/wdparser.php). 
>>
>> As a clarification, you might ask why in the world if I'm running 
>> Weather Display, why would I want it to feed WeeWx?  First, with Weather 
>> Display Brian H. has implemented an amazing number of weather station 
>> interfaces which just plain work.  I have a passion for hardware, and 
>> have at least five stations feeding Weather  Display.  Therefore not 
>> only am I running Weather Display, but it is functioning as an interface 
>> to those stations. I could fiddle with my WeeWx installations and feed 
>> different ones from different stations, especially if there are not 
>> direct drivers native to WeeWx. All I'd need to do is have Weather 
>> Display output through  clientraw.txt, to my WeeWx Raspberry Pi 
>> configurations. 
>>
>> I love WeeWx, and am far from a programmer, but have followed the 
>> discussions and made some modifications to the basic code (all 
>> suggested, I'm not that smart to figure it out but I'm getting better) 
>> and also have selected to run the Belchertown as an output skin also. 
>>
>> So what I'm looking for and haven't apparently found it quite yet, is 
>> some station driver which will take the clientraw. txt and act like a 
>> LOOP feeder for WeeWx.  Fileparser requires a format that is far 
>> different from what WD outputs.  I haven't been able to produce 
>> functioning code which inserts the necessary value identifiers to make 
>> this work.  I see this thread and hope wells up, especially after 
>> looking at the Saratoga examples which seem to look into a URL, analyze 
>> the WeatherDisplay output, and produce such a file.  As far as I can 
>> determine, that whole thing was done just to make the Saratoga work. 
>>
>> Obviously I'm missing something, like why is WeeWx involved in the 
>> conversion at all?  I thought (although never set it up) that WD output 
>> can directly drive Saratoga but I could be all wet on that conclusion. 
>>
>>
>> The last question, straight out, is:  Is there a WeeWx station code that 
>> I can use to 

Re: [weewx-user] Re: weewx-multi performance combined with multiple skins on RPi3/4

[vince]

There is another thread currently talking about using weewx-wd to 
'generate' the file, but Gary is saying there's no way currently he knows 
of to 'ingest' it.  You might want to take a look in the other thread about 
weewx-wd.
On Wednesday, March 9, 2022 at 11:04:45 PM UTC-8 f4n...@gmail.com wrote:

> Could weewx be configured to generate an e.g. realtime.txt / clientraw.txt 
> or something like that, and another weewx system to access and read it live 
> (into its own loop packets/archive records)?
>
> tke...@gmail.com schrieb am Samstag, 5. März 2022 um 18:04:51 UTC+1:
>
>> Nope. Won't work. Unfortunately, the state machine is tangled up in the 
>> archiving service. For example, the decision on when to pause the LOOP 
>> packets and generate archive records is done by StdArchive. Having two 
>> instances would probably result in chaos.
>>
>> They really should be separated, but that's a scary project that could 
>> lead to a lot of subtle bugs.
>>
>> On Sat, Mar 5, 2022 at 8:16 AM matthew wall  wrote:
>>
>>> On Saturday, March 5, 2022 at 10:33:26 AM UTC-5 f4n...@gmail.com wrote:
>>>
 I had an Idea: If I understand the strategies wiki right: can I save to 
 the local sqlite database and to an external mysql database 
 simultaneously? 

>>>
>>> weewx is designed to save to only one database
>>>
>>> i have no idea whether this would work, but you might try putting two 
>>> instances of StdArchive into the service list.  that *might* let you save 
>>> to two different databases.  create your own archiving service by deriving 
>>> from the StdArchive class, and put it in the weewx user directory.  should 
>>> not be necessary to define any methods.  then refer to it in your weewx 
>>> config file:
>>>
>>> archive_services = weewx.engine.StdArchive, user.MyArchive
>>>
>>> If so, I could send it to a mysql database on my webhosting and then 
 access it with another weewx installation on another computer and let the 
 heavier skins run there?  So:

 raspberry Pi A [sqlite local reports] --> webserver [mysql] <--> 
 raspberry Pi B (or other computer) [skin reports]

 Could I access the mysql database simultaneously with weewx on system 
 B? Would it run reports automatically without an attached weather station?

>>>
>>> this is the 'standard' way to do it.  make weewx save to a mysql 
>>> database, either on the computer doing the collection, or on the computer 
>>> doing the aggregated reports.  then make the reporting instance of weewx 
>>> pull data from the mysql database.
>>>  
>>>
>>> -- 
>>> 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/e2c101ac-464c-412d-8daa-e32752e98effn%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/01bdbbcf-495f-4d85-b8a6-3fe34b299a00n%40googlegroups.com.

Re: [weewx-user] Re: Ftp upload

[Rainer Lang]

I doubt that "it" or "everything" works.
Clicking on your link only provides a general page of your web hoster.
Something is still "fishy" - locally, on your web host or with both.

On 10.03.2022 16:19, Kalli Gøtze wrote:

Hi all,
Today i install weewx new and it works. www.kalligotze.org
Thanks for your help :)

best regards Karl

tke...@gmail.com schrieb am Donnerstag, 10. März 2022 um 14:49:42 UTC+1:

In a private email, Kalli noted that the value for "path" is

[[FTP]]
   ...
   path = /home/weewx/public_html
   ...

Two things to note:

  * "path" is the /destination/ directory. This is usually
something like "/var/www/html" or "/weewx".
  * "HTML_ROOT" is the /source/ directory, usually set to
"/home/weewx/public_html" if you used the setup.py install
method (which you did).

You did not say what destination directory you expect, but it is
probably not "/home/weewx/public_html". Think about where you want
the files to go, and set "path" to that. Whatever it is set to,
you must have write permission for the user name you supplied.
Another complication is that for some FTP servers the path must be
an absolute path, for others it is relative to the home directory
of the supplied user. Experiment.

On the other hand, maybe you did want "/home/weewx/public_html".
If so, let us know and we'll go to the next step.

-tk



On Wed, Mar 9, 2022 at 12:23 PM Tom Keffer  wrote:

We have seen this error before and it's very misleading.
Despite the message, it can be caused by problems either
locally or remotely.

1. Make sure the FTP username has write permissions on the
server for the path you specified.
2. Make sure the password is correct. Does it include special
characters? If so, be sure to quote the password.
3. Does your server require FTPS?
4. Try different variations for the path option for [FTP].

If you are still stuck, post your [FTP] section, but be sure
to obfuscate your password first.

-tk

On Wed, Mar 9, 2022 at 11:28 AM vince  wrote:

Possibly, but why would weewx try to upload a file that is
not there on the weewx system ?
Or is that what that #FTPlast file does ?

https://groups.google.com/g/weewx-user/c/XwQqsslGKfA
suggests removing that file which should cause weewx to
upload everything it finds.

On Wednesday, March 9, 2022 at 10:11:51 AM UTC-8
kk44...@gmail.com wrote:

kalli...@gmail.com schrieb am Mittwoch, 9. März 2022
um 18:27:38 UTC+1:

Reason: '550 /home/weewx/public_html/monthhum.png:
No such file or directory'


I would have listened to that error message and guess,
the local file is missing.

-- 
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/70edd677-2765-4bb2-8088-60e0cf5c09a0n%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/5c916353-6bf2-421c-a380-6cf9443831e1n%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/b7b70499-5f42-fe40-443d-6e2e448d1e47%40gmail.com.

Re: [weewx-user] Re: Ftp upload

[Tom Keffer]

Wait, wait! What changed? It would be useful to know for future users. Is
there something different in [[FTP]]?

On Thu, Mar 10, 2022 at 7:19 AM Kalli Gøtze  wrote:

> Hi all,
> Today i install weewx new and it works.  www.kalligotze.org
> Thanks for your help :)
>
> best regards Karl
>
> tke...@gmail.com schrieb am Donnerstag, 10. März 2022 um 14:49:42 UTC+1:
>
>> In a private email, Kalli noted that the value for "path" is
>>
>> [[FTP]]
>>...
>>path = /home/weewx/public_html
>>...
>>
>> Two things to note:
>>
>>- "path" is the *destination* directory. This is usually something
>>like "/var/www/html" or "/weewx".
>>- "HTML_ROOT" is the *source* directory, usually set to
>>"/home/weewx/public_html" if you used the setup.py install method (which
>>you did).
>>
>> You did not say what destination directory you expect, but it is probably
>> not "/home/weewx/public_html". Think about where you want the files to go,
>> and set "path" to that. Whatever it is set to, you must have write
>> permission for the user name you supplied. Another complication is that for
>> some FTP servers the path must be an absolute path, for others it is
>> relative to the home directory of the supplied user. Experiment.
>>
>> On the other hand, maybe you did want "/home/weewx/public_html". If so,
>> let us know and we'll go to the next step.
>>
>> -tk
>>
>>
>>
>> On Wed, Mar 9, 2022 at 12:23 PM Tom Keffer  wrote:
>>
>>> We have seen this error before and it's very misleading. Despite the
>>> message, it can be caused by problems either locally or remotely.
>>>
>>> 1. Make sure the FTP username has write permissions on the server for
>>> the path you specified.
>>> 2. Make sure the password is correct. Does it include special
>>> characters? If so, be sure to quote the password.
>>> 3. Does your server require FTPS?
>>> 4. Try different variations for the path option for [FTP].
>>>
>>> If you are still stuck, post your [FTP] section, but be sure to
>>> obfuscate your password first.
>>>
>>> -tk
>>>
>>> On Wed, Mar 9, 2022 at 11:28 AM vince  wrote:
>>>
 Possibly, but why would weewx try to upload a file that is not there on
 the weewx system ?
 Or is that what that #FTPlast file does ?

 https://groups.google.com/g/weewx-user/c/XwQqsslGKfA suggests removing
 that file which should cause weewx to upload everything it finds.

 On Wednesday, March 9, 2022 at 10:11:51 AM UTC-8 kk44...@gmail.com
 wrote:

> kalli...@gmail.com schrieb am Mittwoch, 9. März 2022 um 18:27:38
> UTC+1:
>
>> Reason: '550 /home/weewx/public_html/monthhum.png: No such file or
>> directory'
>>
>
> I would have listened to that error message and guess, the local file
> is missing.
>
>
 --
 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/70edd677-2765-4bb2-8088-60e0cf5c09a0n%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/5c916353-6bf2-421c-a380-6cf9443831e1n%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/CAPq0zEDppt-fYT9Oe1yV1x1ASunXpc6Aqu_nQfQFW_32%3DtL%2B_A%40mail.gmail.com.

Re: [weewx-user] Re: Ftp upload

[Kalli Gøtze]

Hi all,
Today i install weewx new and it works.  www.kalligotze.org
Thanks for your help :)

best regards Karl

tke...@gmail.com schrieb am Donnerstag, 10. März 2022 um 14:49:42 UTC+1:

> In a private email, Kalli noted that the value for "path" is
>
> [[FTP]]
>...
>path = /home/weewx/public_html
>...
>
> Two things to note:
>
>- "path" is the *destination* directory. This is usually something 
>like "/var/www/html" or "/weewx".
>- "HTML_ROOT" is the *source* directory, usually set to 
>"/home/weewx/public_html" if you used the setup.py install method (which 
>you did).
>
> You did not say what destination directory you expect, but it is probably 
> not "/home/weewx/public_html". Think about where you want the files to go, 
> and set "path" to that. Whatever it is set to, you must have write 
> permission for the user name you supplied. Another complication is that for 
> some FTP servers the path must be an absolute path, for others it is 
> relative to the home directory of the supplied user. Experiment.
>
> On the other hand, maybe you did want "/home/weewx/public_html". If so, 
> let us know and we'll go to the next step.
>
> -tk
>
>
>
> On Wed, Mar 9, 2022 at 12:23 PM Tom Keffer  wrote:
>
>> We have seen this error before and it's very misleading. Despite the 
>> message, it can be caused by problems either locally or remotely.
>>
>> 1. Make sure the FTP username has write permissions on the server for the 
>> path you specified.
>> 2. Make sure the password is correct. Does it include special characters? 
>> If so, be sure to quote the password.
>> 3. Does your server require FTPS?
>> 4. Try different variations for the path option for [FTP].
>>
>> If you are still stuck, post your [FTP] section, but be sure to obfuscate 
>> your password first.
>>
>> -tk
>>
>> On Wed, Mar 9, 2022 at 11:28 AM vince  wrote:
>>
>>> Possibly, but why would weewx try to upload a file that is not there on 
>>> the weewx system ?
>>> Or is that what that #FTPlast file does ?
>>>
>>> https://groups.google.com/g/weewx-user/c/XwQqsslGKfA suggests removing 
>>> that file which should cause weewx to upload everything it finds.
>>>
>>> On Wednesday, March 9, 2022 at 10:11:51 AM UTC-8 kk44...@gmail.com 
>>> wrote:
>>>
 kalli...@gmail.com schrieb am Mittwoch, 9. März 2022 um 18:27:38 UTC+1:

> Reason: '550 /home/weewx/public_html/monthhum.png: No such file or 
> directory'
>

 I would have listened to that error message and guess, the local file 
 is missing.
  

>>> -- 
>>> 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/70edd677-2765-4bb2-8088-60e0cf5c09a0n%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/5c916353-6bf2-421c-a380-6cf9443831e1n%40googlegroups.com.

Re: [weewx-user] $day($data_binding=...).wind.avg not working

[Tom Keffer]

I just tried it on my Mac and it worked fine. I even added it to the test
suite (commit e907b59

).

Are you sure that the binding "gw1000_binding" has wind? That is, it needs
a daily summary schema that includes wind.


On Thu, Mar 10, 2022 at 3:37 AM Graham Eddy  wrote:

> under 4.7.0 $day.wind.avg works fine but $day($data_binding=...).wind.avg
> does not. is this expected?
> (i have not tried the latter on earlier versions.)
>
> Mar 10 21:17:42 ironbark wee_reports[3057643] DEBUG
> weewx.cheetahgenerator: Unrecognized:
> $day($data_binding='gw1000_binding').wind.avg
>
>
>
> --
> 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/540CCCD8-0B87-4942-87EA-1EA2773D0F48%40gmail.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/CAPq0zECYBjR9a4eZgtVkLa8-7N6CMCsQyO87VziJ%2BgB1TLnZLQ%40mail.gmail.com.

Re: [weewx-user] Re: Ftp upload

[Tom Keffer]

In a private email, Kalli noted that the value for "path" is

[[FTP]]
   ...
   path = /home/weewx/public_html
   ...

Two things to note:

   - "path" is the *destination* directory. This is usually something like
   "/var/www/html" or "/weewx".
   - "HTML_ROOT" is the *source* directory, usually set to
   "/home/weewx/public_html" if you used the setup.py install method (which
   you did).

You did not say what destination directory you expect, but it is probably
not "/home/weewx/public_html". Think about where you want the files to go,
and set "path" to that. Whatever it is set to, you must have write
permission for the user name you supplied. Another complication is that for
some FTP servers the path must be an absolute path, for others it is
relative to the home directory of the supplied user. Experiment.

On the other hand, maybe you did want "/home/weewx/public_html". If so, let
us know and we'll go to the next step.

-tk



On Wed, Mar 9, 2022 at 12:23 PM Tom Keffer  wrote:

> We have seen this error before and it's very misleading. Despite the
> message, it can be caused by problems either locally or remotely.
>
> 1. Make sure the FTP username has write permissions on the server for the
> path you specified.
> 2. Make sure the password is correct. Does it include special characters?
> If so, be sure to quote the password.
> 3. Does your server require FTPS?
> 4. Try different variations for the path option for [FTP].
>
> If you are still stuck, post your [FTP] section, but be sure to obfuscate
> your password first.
>
> -tk
>
> On Wed, Mar 9, 2022 at 11:28 AM vince  wrote:
>
>> Possibly, but why would weewx try to upload a file that is not there on
>> the weewx system ?
>> Or is that what that #FTPlast file does ?
>>
>> https://groups.google.com/g/weewx-user/c/XwQqsslGKfA suggests removing
>> that file which should cause weewx to upload everything it finds.
>>
>> On Wednesday, March 9, 2022 at 10:11:51 AM UTC-8 kk44...@gmail.com wrote:
>>
>>> kalli...@gmail.com schrieb am Mittwoch, 9. März 2022 um 18:27:38 UTC+1:
>>>
 Reason: '550 /home/weewx/public_html/monthhum.png: No such file or
 directory'

>>>
>>> I would have listened to that error message and guess, the local file is
>>> missing.
>>>
>>>
>> --
>> 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/70edd677-2765-4bb2-8088-60e0cf5c09a0n%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/CAPq0zEAy5iK3SsQGgT6nL%3D1UM4sPPyjA_vA4LXc-PMcsyi246Q%40mail.gmail.com.

[weewx-user] $day($data_binding=...).wind.avg not working

[Graham Eddy]

under 4.7.0 $day.wind.avg works fine but $day($data_binding=...).wind.avg does 
not. is this expected?
(i have not tried the latter on earlier versions.)

Mar 10 21:17:42 ironbark wee_reports[3057643] DEBUG weewx.cheetahgenerator: 
Unrecognized: $day($data_binding='gw1000_binding').wind.avg


-- 
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/540CCCD8-0B87-4942-87EA-1EA2773D0F48%40gmail.com.

Re: [weewx-user] Weewx 4.7.0 & Weewx -WD

[gjr80]

Dale,

I am not aware of any means of having WeeWX ingest data via clientraw.txt. 
I wouldn't be writing off fileparse either, I've never used Weather Display 
but if I was trying to do what want I would look at using Weather Display's 
tag system to generate a custom document/report in a format that fileparse 
can read. The custom document/report should be fairly compact as it only 
need contain those observations that you wish WeeWX to record. By using 
fileparse you avoid the need to write any python code and importantly you 
keep things simple.

Gary

On Thursday, 10 March 2022 at 13:26:46 UTC+10 daleea...@gmail.com wrote:

> Gary,
>
> Pardon me for jumping in on this thread, butseeing Weather Display and 
> clientraw.txt terms grabbed my attention.
>
> I've read through this message, and it lead me to the WeeWx-WD (end of 
> life) and the WeeWx-Saratoga portions, which I read, and partially 
> understand.
>
> My main goal is to find some station code for WeeWx which will take my 
> WeatherDisplay clientraw file and allow it to drive WeeWx.  I looked at 
> this a couple years ago and was given a lead to use fileparser, but that 
> station base code requires a observation name followed by the value; as 
> you know clientraw.txt is just a string of numbers, which is incredibly 
> well analyzed in one of the files on Saratoga 
> (https://saratoga-weather.org/wdparser.php).
>
> As a clarification, you might ask why in the world if I'm running 
> Weather Display, why would I want it to feed WeeWx?  First, with Weather 
> Display Brian H. has implemented an amazing number of weather station 
> interfaces which just plain work.  I have a passion for hardware, and 
> have at least five stations feeding Weather  Display.  Therefore not 
> only am I running Weather Display, but it is functioning as an interface 
> to those stations. I could fiddle with my WeeWx installations and feed 
> different ones from different stations, especially if there are not 
> direct drivers native to WeeWx. All I'd need to do is have Weather 
> Display output through  clientraw.txt, to my WeeWx Raspberry Pi 
> configurations.
>
> I love WeeWx, and am far from a programmer, but have followed the 
> discussions and made some modifications to the basic code (all 
> suggested, I'm not that smart to figure it out but I'm getting better) 
> and also have selected to run the Belchertown as an output skin also.
>
> So what I'm looking for and haven't apparently found it quite yet, is 
> some station driver which will take the clientraw. txt and act like a 
> LOOP feeder for WeeWx.  Fileparser requires a format that is far 
> different from what WD outputs.  I haven't been able to produce 
> functioning code which inserts the necessary value identifiers to make 
> this work.  I see this thread and hope wells up, especially after 
> looking at the Saratoga examples which seem to look into a URL, analyze 
> the WeatherDisplay output, and produce such a file.  As far as I can 
> determine, that whole thing was done just to make the Saratoga work.
>
> Obviously I'm missing something, like why is WeeWx involved in the 
> conversion at all?  I thought (although never set it up) that WD output 
> can directly drive Saratoga but I could be all wet on that conclusion.
>
>
> The last question, straight out, is:  Is there a WeeWx station code that 
> I can use to read WD files (not fileparser, since as I noted it needs a 
> different format) and have WeeWx import those Loop-like packets?
>
> If there is not, and my efforts to make something like this work (the 
> data in the clientraw.txt  or customclientraw.txt output is very much 
> enough to make WeeWx's need for data points to work), my old remaining 
> possible solution is to write Brian, who has returned from a  brake, to 
> see if he can implement a custom output driver that will do like his API 
> code does to feed Meteotemplate and CWOS, which work slick but no doubt 
> takes a bit of skill and time to write.
>
>
> Whew, I'm sorry for the long message, but was inspired by the discussion 
> to see if there is something out there, or that a solution is easily 
> implemented, and hope to get guidance from you or others experienced 
> with station driver routines.
>
> Dale
>
> http://ecwx.info/weewx/
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f95285a7-5cc1-4576-998b-4d3773cc07c1n%40googlegroups.com.