Weewx 4.7.0 & Weewx -WD

[Stefanos Kalaitzis]

Hi everyone...I am running weewx with sdr driver  I decided to update from weewx 4.2.0 to 4.7.0 and i have several errors in Clientraw skin....It doesnt generate the clientraw.txt but all the others clientrawhour,-daily - extra are generated.In the 4.2.0 version evrything was flawless .I also made a clean install of weewx 4.7.0 and the errors are the same ... I kept the log from 4.7.0 and i downgraded again to the old version. If someone knows whats going on i would appreciate it.

 I didnt make any change to weewx.conf after the update .

Thank you in advanced

[Tom Keffer]

See if this thread helps: https://groups.google.com/g/weewx-user/c/rnLNpNoX0U0/m/stFp0t_MEAAJ

--
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/b200d823-4ee6-4e64-8164-b531a227d54bn%40googlegroups.com.

[Stefanos Kalaitzis]

Thanks Tom... Weewx -wd doesnt run in 4.7.0 ... I checked all the necessary conf files and the result is the same .

Also tried the weewx -saratoga  that runs without problem but the clientraw.txt that generated is a little bit different than the weewx-wd as a result the saratoga template gets different values in the appropriate fields and i have to modify the dashboard script file and i dont have much time :p

I thought that clientraw gets standard values in standard place 

Example

Temp, wind ,baro, and rain are correct but dew point is wrong and time of max-min temp is not updated

I can live with the 4.2.0 ... :)

[gjr80]

clientraw.txt is indeed a fixed format, space delimited file that should have the same observation/stat in the same location irrespective of source. If dewpoint and time of max/min outside (?) temperature is not correct then that is a bug and it should be fixed. I have just looked at my own WeeWX-Saratoga generated clientraw.txt and I note that the time of max outside temperature is incorrect but time of min outside temperature is correct. dewpoint is also correct.

I am more than happy to deal with bugs in WeeWX-Saratoga but WeeWX-WD has reached end of life and won't be updated. Can you give me some more information on the errors you are seeing? dewpoint, is it obviously wrong, in F instead of C, close but not quite or not updating? Are both time of max/min outside temperature wrong or just time of max? What station and driver are you using? Is your site publicly accessible? Ideally it would be good to be able to see the erroneous clientraw.txt alongside your current (correct) site but I guess you have probably uninstalled WeeWX-Saratoga.

Gary

[gjr80]

I did some debugging of the WeeWX-Saratoga service that generates clientraw.txt. My test environment running the simulator shows the WeeWX-Saratoga clientraw.txt service is working correctly. The outTemp loop cache was being correctly seeded from the daily summaries at startup and max/min and associated time correctly updated on arrival of loop packets. dewpoint was also being correctly calculated. I also took another look at my live site and day max/min outTemp and associated times are correct; I suspect I was looking at old data this morning.

I am guessing this is your site -  https://tagarades-weather.epizy.com ? I found a WeeWX-Saratoga generated clientraw.txt at this address - https://tagarades-weather.epizy.com/clientraw.txt - the timestamp is 1825 on 6 March. Unfortunately your site graphs have moved on to 7 March so I cannot correlate the day max/min temps and times as they would have been at 1825 on 6 March. However, your NOAA format reports indicate the maximum temperature on 6 March was 8.5C at 1637 - this agrees with the data in clientraw.txt (fields 46 and 174 respectively). According to the NOAA reports the day min outTemp occurred after 1825 so the NOAA format report data cannot be used to verify the clientraw.txt min outTemp and time as it would have been at 1825. Looking at your weekly plot though I see a minimum outTemp before 1825 of 5.5C at 0737 and 0837. The 1825 clientraw.txt has minimum outTemp of 5.2 at 0652. Given the weekly plot only shows data points every hour we can't really draw any conclusion from this other than the clientraw.txt min outTemp is not obviously wrong. dewpoint in the 1825 clientraw.txt is 0.0 and looking at your week plot you had not dewpoint data from (around) 1537 to 1837, the WeeWX-Saratoga clientraw.txt service substitutes 0.0 if a temperature based observation does not exist (it must output something otherwise the clientraw.txt format will be corrupted) so it is quite possible the clientraw.txt dewpoint value of 0.0 was the expected result at the time.

The upshot of this analysis of your site is that I cannot find any obvious issues with the clientraw.txt data. One thing you may consider doing is upgrade to WeeWX v4.5.1. This would allow WeeWX-WD to continue to operate without error (it is changes introduced in v4.6.0 that breaks WeeWX-WD) and it would also allow you to re-install WeeWX-Saratoga (it requires v4.5.0 or later) to allow proper troubleshooting of the clientraw.txt issue.

Gary

[Stefanos Kalaitzis]

Hi Gary... I am imprsessed.... How do you find me...?? :p

Yes thats my site (https://tagarades-weather.epizy.com/WD) but i made it to test things before i upload my data to a weather provider https://northmeteo.gr/weather_stations/tagarades/index.php?lang=en . For the main site i am using the belchertown skin ( is without the /WD).  I am using now the 4.2.0 version with weewx-wd but i kept the clientraw file of weewx saratoga...

Few things that i noticed in weewx -saratoga ...

1. I cant change path of clientraraw.txt (always is saved to puplic_html and i want to public_html/WD) even if i edit the rtcr.py

2. The dewpoint gets value 0 (i attached a screen shot  when i made again the upgrade)

3. When i made a split with python to clinentraw.txt to data[174] for example i get 0 value

4. Sometimes not always the avg_speed gets bigger values than the gust_speed.

Probably when you saw my clientraw.txt that is correct was from the weewx-wd and not from Saratoga

Anyway , thank you for your time and for your support

Maybe i did something wrong but i didnt touch anything when i upgrade to 4.7.0 . I use the sdr driver . After i saw the incorrect values i tried to change the time format (only that)

p.s the saratoga clientraw was from yesterday (compared with the -wd i see that after station location have different values, those with solar radiation percent i think)

[Stefanos Kalaitzis]

Also i didnt mentioned that the issue is maybe the correspondence with the template fields and not the client raw file itself

[Stefanos Kalaitzis]

Hi Gary...I did what you said...

1. I upgraded from 4.2.0 to 4.5.1 with weewx-wd plugin (everything fine)

2. I uninstalled the weewx-wd and installed the saratoga (seems that the dew point is correct now and i will leave it to see if the time of max-min temp are updated )

Issues that are remaining are

1. the avg_speed gets higher values than the gust_speed sometimes (Its ok for me )

2. path of clientraraw.txt -  always is saved to public_html  (i send clientraw files with a second ftp report so i want to have them in public_html/WD folder) (Its ok - i made a python script to send clientraw.txt alone)

You can check now better and let me know if i miss something

Thanks again for your support

[Stefanos Kalaitzis]

[Stefanos Kalaitzis]

Now that it is raining , i noticed that rain rate and max rain rate have 0.0 value

That's all for now..... :p ......I hope that i didnt inconvenience you

[gjr80]

> How do you find me...??

That was not too difficult, your user name sounded very Greek so I looked at the WeeWX user map and there are not that many stations in Greece. I knew you were using SDR and there are not that many SDR stations around. Finding clientraw.txt was the clincher.

> 1. I cant change path of clientrraw.txt (always is saved to puplic_html and i want to public_html/WD) even if i edit the rtcr.py

I still need to finish off documenting the WeeWX-Saratoga options. You can change the location that clientraw.txt is saved using the rtcr_patth setting under [WeewxSaratoga] [[RealtimeClientraw]] in weewx.conf, eg:

[WeewxSaratoga]
    ....
    [[RealtimeClientraw]]
        # Path to clientraw.txt. Can be an absolute or relative path. Relative
        # paths are relative to HTML_ROOT. Optional, default setting is to use
        # HTML_ROOT.
        rtcr_path = /home/weewx/public_html

Until I finish documenting the options the best source of RealtimeClientraw (the service that WeeWX-Saratoga uses to generate clientraw.txt) is the comments at the top of rtcr.py. I don't recommend editing the rtcr.py code to force things, it is far to easy to break something else, it is a complex service.

> 2. The dewpoint gets value 0 (i attached a screen shot  when i made again the upgrade)

I have a suspicion this could be related to the gaps I saw in some of your plots, depending on your system dewpoint may be a calculated value and if any of the prerequisites for its calculation are missing it will not be calculated and clientraw.txt will then display it as 0.0.

> 3. When i made a split with python to clientraw.txt to data[174] for example i get 0 value

It is possible there could be some corner cases that are causing a field to be omitted when clientraw.txt is generated, I would like to think I have hardened the code to prevent this but it is possible. If one field is omitted that shuffles every later field along and they become out of place. If you use a clientraw.txt parser like the one at Saratoga Weather it is usually pretty obvious where the omission is. We can work through this one now that you have installed v4.5.1 and WeeWX-Saratoga.

> 4. Sometimes not always the avg_speed gets bigger values than the gust_speed.

This should not happen, again can work through.

> Probably when you saw my clientraw.txt that is correct was from the weewx-wd and not from Saratoga

No, was definitely from WeeWX-Saratoga, if you look at the end of the file you will see something like:

102.9 16:37 06:52 68 !!WS0.3.3!!

The 'WS0.3.3' indicates WeeWX-Saratoga v0.3.3, WeatherDisplay and WeeWX-WD generated clientraw.txt files terminate differently.

> Now that it is raining , i noticed that rain rate and max rain rate have 0.0 value

OK. I will work through this and the other issues you have raised.

> That's all for now..... :p ......I hope that i didnt inconvenience you

Not at all, it's can be difficult to write something like RealtimeClientraw and cover all the corner cases so you have to rely on people finding bugs.

Gary

[Stefanos Kalaitzis]

Hi Gary ... Thanks !!

Also Time of min-max temp still not updated 

[Stefanos Kalaitzis]

Hi Gary ...

Time of min-max temp ...ok ... It wasnt the clientraw as you said but i reinstall the weewx plugin for Sarratoga template and all good

Now i have also  max rain/rate value correct  but i dont know about rain/rate because it stop raining

Wind values are mystery.... I edited the ajaxweewx js file and i put [1] for avg_speed instead of [140] and [2] for gust_speed instead of [1]

[gjr80]

Hi,

I've spent a bit of time today observing your clientraw.txt and Belchertown web site. On thing I have noted is that your clientraw.txt only updates approximately every 1.5 to 2.5 minutes. This suggests that loop packets are not coming in very often and they arrive irregularly. This could be causing some odd effects, in particular with wind where there a couple of fields that are calculated as aggregates over one minute. It might be useful to see what loop packets you have coming in and what their contents are. To do this stop WeeWX and then run WeeWX directly. This will display loop packets (lines starting with LOOP:) and archive records (lines starting with REC:) on your console. If you like let WeeWX run for 15 minutes or so and capture and post the screen out (as text).

Just hitting the issues you have noted so far:

clientraw.txt location. Can be controlled with the rtcr_path config items as per my previous post. Any luck with this?

day max/min outTemp times. As you posted earlier these time are now updating. Throughout today (9th) when I have looked at your clientraw.txt the max/min outTemp times have been correct. It is possible to have some discrepancies with these values when WeeWX is first started but I'm not sure that is what was happening here. I suggest we monitor this for the next couple of days, particularly for the rest of the day after a WeeWX restart. If the issue comes back I can give you an instrumented version of rtcr.py to give us more detail on exactly what is happening.  

dewpoint. Appears to be fine as far as I can tell, every time I have looked the dewpoint value in clientraw.txt has agreed with your station.

avg wind speed/wind gust speed discrepancies. I gather here you are looking at the Saratoga or Alternate dashboard? (is your Saratoga dashboard publicly accessible? If it is could we have the address or if you don't wish to make it public could you advise me via 'reply to author' or by email to gjroderick at gmail dot com. There is a wealth of debug information built into the dashboard). If I understand you correctly you originally had field 140 (max gust in last minute) as average speed on the dashboard but changed it to field 1 (average wind speed in last 60 seconds). You also had field 1 (average wind speed in last 60 seconds) as gust speed on the dashboard but changed it to field 2 (current wind speed). If that is the case I am not surprised you were initially seeing average wind speed higher than the gust speed as the you had a gust speed field displaying as average and an average speed field displaying as gust speed. I would be sticking with the original values in ajaxWEEWXwx.js (circa lines 762-772):

//Wind gust

var gust = convertWind(clientraw[140]);

var maxgust = convertWind(clientraw[71]);

if (maxgust > 0.0 ) {

set_ajax_obs("ajaxmaxgust",maxgust.toFixed(1) + uomWind);

} else {

set_ajax_obs("ajaxmaxgust",'None');

}

//Windspeed ...

var wind = convertWind(clientraw[2]);

or perhaps changing gust to field 133 (max gust last hour) given your rather long loop period.

rainrate. Sounds like that is now working, unfortunately I have not observed any rain on your site.

Gary

[Stefanos Kalaitzis]

Hi Gary … Thank you again !! 

clientraw.txt location now changed (Thanks!!)

Everything working like a charm …  (day max/min outTemp times, dewpoint) Probably was the ajaxWEEWXwx.js because when I downloaded again and reinstall it all issues disappeared

For my dashboard at https://tagarades-weather.epizy.com/WD/index.php  I have downloaded the World Template .ZIP and the WeeWX .ZIP (updated every 2,5min - archive interval-ftp)

 

-is your Saratoga dashboard publicly accessible?---- I think yes , have you tried to access and faced some problem??

If you cant use the clientraw parser script try this address https://northmeteo.gr/weather_stations/tagarades/ (updated every 50 sec due to http post -post_clientraw)

When I used the weewx-wd I changed wind [values] in ajaxWEEWXwx.js file because I had a problem that I cant remember and somewhere I read that is better to change  var gust , var wind, with [2] and [1] (I guess that it was wrong)

Anyway now I changed these to normal only in /WD address above

Now I have 2 equal values for wind and gust all the time and the same I noticed in https://saratoga-weather.org/weewx/wxindex.php

[gjr80]

OK. That is good to see, it looks like it is working as it should.

What you will see with wind/wind gust speeds will depend on your station/driver, how you have configured the RealtimeClientraw service and how you have configured the Saratoga templates. The RealtimeClientraw service will generate clientraw.txt every time a loop packet is received from the WeeWX driver. You then need to get clientraw.txt to your web server (if it is not the same machine as your WeeWX server). If you just rely on the WeeWX rsync or ftp report then even though clientraw.txt will be generated frequently (perhaps every few seconds) it will only be uploaded at the end of each archive period (perhaps every few minutes). That is where you can use the RealtimeClientraw service to upload clientraw.txt via HTTP POST using post_clientraw.php as soon as clientraw.txt is generated. The final cog in the wheel is the Saratoga templates, you can configure how often the the Saratoga dashboard should attempt to update via clientraw.txt. If your clientraw.txt is generated every 60 seconds there is little point in having the Saratoga dashboard update every five seconds.

In my case I have a Davis station which emits loop packets every 2.5 odd seconds so my clientraw.txt is generated every 2.5 odd seconds. I upload clientraw.txt to my web server via HTTP POST every 2.5 odd seconds but have the Saratoga dashboard setup to update every 10 seconds (I find updating every 10 seconds gives you an opportunity to read the numbers before they change). Also in my case my Saratoga dashboard displays the current wind speed and the one minute gust speed. Because I have wind speed data arriving every 2.5 odd seconds I see quite a bit of variation between my wind speed and gust speed values.

In your case I was seeing your clientraw.txt was only being updated every 1.5 to 2.5 minutes, that seemed odd to me as your Belchertown page (I could not find your Saratoga dashboard at the time) was updating every few seconds and hence I asked to see the loop data so we could see how often loop packets were arriving. The fact that your wind speed and gust speed were always the same also indicated that loop packets were not being received very often. But you actually have loop packets with wind speed data coming in every 12 odd seconds so your clientraw.txt really should be generated every 12 odd seconds not every 1.5 to 2.5 minutes. Have you looked on your WeeWX machine (not your web server) to see how often clientraw.txt is being generated? You can have the RealtimeClientraw service log some clientraw.txt generation info by setting the debug_gen option under [WeewxSaratoga] [[RealtimeClientraw]] in weewx.conf, eg:

[WeewxSaratoga]
    ....
    [[RealtimeClientraw]]
        ....

        debug_gen = True

Save weewx.conf and restart WeeWX. You should now see entries in the WeeWX log each time clientraw.txt is generated.

Also how are you transferring clientraw.txt to your web server?

Gary

[DR]

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/

[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

[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 

[gjr80]

Hi Stefanos,

Some answers below.

Gary

On Friday, 11 March 2022 at 06:51:37 UTC+10 stefanos...@gmail.com wrote:

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

I have not specified rtcr_path as I do not use the local (WeeWX machine) copy of clientraw.txt, rather I use HTTP POST to transfer the file to my web server. The local copy is still generated and saved in the default location (/home/weewx/public_html). I have remote_server_url set to the location of the post_clientraw.php script on my web server. The RealtimeClientraw service transfers clientraw.txt to my web server via this script. I also have min_interval = 10. My station is a Davis VP2 so it emits loop packets every 2.5 odd seconds, I could omit min_interval and the ClientrawService would generate clientraw.txt on receipt of every loop packet (ie 2.5 seconds) and it would then be immediately transferred to my web server via HTTP POST; however, I decided I wanted to slow things down and only update my Saratoga dashboard every 10 seconds so hence I generate clientraw.txt every 10 seconds using min_interval = 10. min_interval specifies the minimum interval between consecutive generations of clientraw.txt, if you omit it a value of 0 is used so clientraw.txt is generated every loop packet, setting it to 10 forces it to wait until 10 seconds have passed since the last generation before the file is generated again. Irrespective of how you set min_interval you cannot have the ClientrawService generate clientraw.txt more frequently than loop packets arrive. I also set date_format, long_time_format and short_time_format to the recommended non-USA settings. Also have log_success = False and log_failure = True so my log is not full of successful HTTP POST entries but I am still alerted of HTTP POST failures.

My [[RealtimeClientraw]] stanza looks something like:

[[RealtimeClientraw]]

# If using an external website, configure remote_server_url to point to

# the post_clientraw.php script on your website like:

# remote_server_url = http://your.website.com/post_clientraw.php

#

# To disable or use the webserver on this system, leave the entry

# commented out or blank.

remote_server_url = address_obfuscated/post_clientraw.php

# min_interval sets the minimum clientraw.txt generation interval.

# 10 seconds is recommended for all Saratoga template users. Default

# is 0 seconds.

min_interval = 10

# Python date-time format strings. Format string codes as per

# https://docs.python.org/3/library/datetime.html#strftime-and-strptime-format-codes

# Date format. Recommended entries are:

# date_format = %-m/%-d/%Y # recommended for USA users

# date_format = %-d/%-m/%Y # recommended for non-USA users

date_format = %-d/%-m/%Y

# Long format times (HMS). Recommended entries are:

# long_time_format = %-I:%M:%S_%p # recommended for USA users

# long_time_format = %H:%M:%S # recommended for non-USA users

long_time_format = %H:%M:%S

# Short format times (HM). Recommended entries are:

# short_time_format = %-I:%M_%p # recommended for USA users

# short_time_format = %H:%M # recommended for non-USA users

short_time_format = %H:%M

# log successful HTTP POSTs

log_success = False

# log HTTP POST failures

log_failure = True

-- how you have configured the Saratoga templates:

untouched too now  (ajaxWEEWXwx.js is the original and virgin :P from weewx-plugin.zip )

 

My Saratoga templates are setup as per the Saratoga templates setup instructions. Nothing special there, the key points are getting the date and time formats as well as units of measure correct in Settings.php. In Settings-weather.php the key points are getting the paths to various files correct, in particular the tags file and clientraw.txt. My clientraw.txt goes to a non-standard location on my web server so I needed to adjust the path to suit. ajaxWEEWXws.js is just setup as per the instructions, key settings were units and the location of clientraw.txt. I did not alter any fields within the code.
 

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

 

As outlined above I use HTTP POST to transfer clientraw.txt to my web server. Multiple remote server URLs are not supported. I am happy to look at adding the ability to use multiple remote servers, not sure when I will get to it though. In the meantime you will be stuck transferring to one site via HTTP POST and one site via FTP/rsync report.

 

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.

 

I guess you mean this page https://saratoga-weather.org/weewx/wxindex.php. I had not noticed that behaviour before, and I see my page exhibits the same behaviour. This should not be happening and I will look into it. When you refresh the page the data that is initially displayed is from WEEWXtags.php, so you should see gust >= average wind speed. Then the AJAX updates kick in using clientraw.txt and that is when we see the incorrect behaviour.

 

[Stefanos Kalaitzis]

Hi Gary ,

Yes that page i am talking about ... I saw your page too ... (same issue)

Anyway thank you again ... You are more than helpful for me . Everything are flawless now

I will wait for an update for gust speed

Best regards

Stefanos