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

On Monday, March 7, 2022 at 7:39:33 PM UTC+2 Stefanos Kalaitzis wrote:

> Also i didnt mentioned that the issue is maybe the correspondence with the 
> template fields and not the client raw file itself
>
>
> On Monday, March 7, 2022 at 11:25:17 AM UTC+2 Stefanos Kalaitzis wrote:
>
>> 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)
>>
>>  
>>
>>
>> On Monday, March 7, 2022 at 5:02:26 AM UTC+2 gjr80 wrote:
>>
>>> 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
>>>
>>> On Monday, 7 March 2022 at 07:48:44 UTC+10 gjr80 wrote:
>>>
>>>> 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
>>>>
>>>> On Monday, 7 March 2022 at 03:11:45 UTC+10 [email protected] wrote:
>>>>
>>>>> 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 ... :)
>>>>>
>>>>> On Saturday, March 5, 2022 at 9:57:59 PM UTC+2 [email protected] wrote:
>>>>>
>>>>>> See if this thread helps: 
>>>>>> https://groups.google.com/g/weewx-user/c/rnLNpNoX0U0/m/stFp0t_MEAAJ
>>>>>>
>>>>>> On Sat, Mar 5, 2022 at 8:41 AM Stefanos Kalaitzis <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>> 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 
>>>>>>>
>>>>>>> -- 
>>>>>>> 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 [email protected].
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid/weewx-user/b200d823-4ee6-4e64-8164-b531a227d54bn%40googlegroups.com
>>>>>>>  
>>>>>>> <https://groups.google.com/d/msgid/weewx-user/b200d823-4ee6-4e64-8164-b531a227d54bn%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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b1dc72a6-e05a-4195-95a7-26153d2cf743n%40googlegroups.com.

Reply via email to