[weewx-user] Re: bootstrap history page

2019-12-07 Thread Mikael Fredriksson
Andrew,

Finally got it to work
!
Got an answer on my comment on github, and followed the proceduer. 
I must have made some misstake before because it looks like this was what 
you told me to do.
My NOAA works also but I haven't made any changes on that.

Hope you get some answer to your issue with this now!

And thanks for your answers on this!

/Mikael

Den söndag 8 december 2019 kl. 00:49:39 UTC+1 skrev Andrew Milner:
>
> does the log offer any clues??  worked for me just changing history 
> generator.py and the skin.conf.  I suspect noaa does not work for me 
> because i have changed my noaa files to html instead of txt and also 
> altered the header lines so suspect i have upset something!!  I've also 
> emailed him and also not heard anything back (yet).
>
> On Sunday, 8 December 2019 00:26:31 UTC+2, Mikael Fredriksson wrote:
>>
>> Andrew,
>>
>> I've tried to copy these files and even changed them line by line in 
>> place, but the summary columns just won't apear. 
>> Don't know what to try more, I left a comment on his github. Hope to get 
>> some answer to this.
>>
>> /Micael
>>
>>
>>
>>
>> Den måndag 2 december 2019 kl. 04:17:46 UTC+1 skrev Andrew Milner:
>>>
>>> i only copied the files a week or so ago.  The only problem I am having 
>>> is with the noaa table which is giving me an error - i have got the summary 
>>> columns for the min, max, rain tables working as expected.
>>>
>>>
>>>
>>> On Sunday, 1 December 2019 23:43:50 UTC+2, Mikael Fredriksson wrote:

 Ok, thanks Andrew!

 I did also try to update and use the new files but nothing changed so I 
 guess this has been removed in the latest update.

 Mikael



-- 
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/278d83ad-4208-469b-9db7-2b7371a8afe1%40googlegroups.com.


[weewx-user] Re: bootstrap history page

2019-12-07 Thread Andrew Milner
does the log offer any clues??  worked for me just changing history 
generator.py and the skin.conf.  I suspect noaa does not work for me 
because i have changed my noaa files to html instead of txt and also 
altered the header lines so suspect i have upset something!!  I've also 
emailed him and also not heard anything back (yet).

On Sunday, 8 December 2019 00:26:31 UTC+2, Mikael Fredriksson wrote:
>
> Andrew,
>
> I've tried to copy these files and even changed them line by line in 
> place, but the summary columns just won't apear. 
> Don't know what to try more, I left a comment on his github. Hope to get 
> some answer to this.
>
> /Micael
>
>
>
>
> Den måndag 2 december 2019 kl. 04:17:46 UTC+1 skrev Andrew Milner:
>>
>> i only copied the files a week or so ago.  The only problem I am having 
>> is with the noaa table which is giving me an error - i have got the summary 
>> columns for the min, max, rain tables working as expected.
>>
>>
>>
>> On Sunday, 1 December 2019 23:43:50 UTC+2, Mikael Fredriksson wrote:
>>>
>>> Ok, thanks Andrew!
>>>
>>> I did also try to update and use the new files but nothing changed so I 
>>> guess this has been removed in the latest update.
>>>
>>> Mikael
>>>
>>>

-- 
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/7dc92d87-0098-49f4-8724-ecb9a5f621c1%40googlegroups.com.


[weewx-user] Re: bootstrap history page

2019-12-07 Thread Mikael Fredriksson
Andrew,

I've tried to copy these files and even changed them line by line in place, 
but the summary columns just won't apear. 
Don't know what to try more, I left a comment on his github. Hope to get 
some answer to this.

/Micael




Den måndag 2 december 2019 kl. 04:17:46 UTC+1 skrev Andrew Milner:
>
> i only copied the files a week or so ago.  The only problem I am having is 
> with the noaa table which is giving me an error - i have got the summary 
> columns for the min, max, rain tables working as expected.
>
>
>
> On Sunday, 1 December 2019 23:43:50 UTC+2, Mikael Fredriksson wrote:
>>
>> Ok, thanks Andrew!
>>
>> I did also try to update and use the new files but nothing changed so I 
>> guess this has been removed in the latest update.
>>
>> Mikael
>>
>>

-- 
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/b643ac10-51e2-46d8-a6b9-109299ee7ec3%40googlegroups.com.


[weewx-user] Re: WeeWX et WS-2300

2019-12-07 Thread Olivier Garnier
Anybody can help me ?
Who can i ask ?

-- 
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/a8cdfd20-1f5b-4ffe-98d9-04712a451029%40googlegroups.com.


Re: [weewx-user] Re: Rain rate too high with SDR driver?

2019-12-07 Thread mwall
On Saturday, December 7, 2019 at 3:57:00 AM UTC-5, S1m0n3 wrote:
>
>
> After an year I've tried again to work with Weewx but I've same problem 
> with rain 😢 can I do some things?! Thanks!!!


sorry this is taking so long to resolve.

as gary pointed out, it looks like a units conversion issue.

fwiw, rtl_433 has at least three different decoding implementations for the 
fine offset x080 stations, and there have been variations in the units in 
those over the years.  that is why weewx-sdr works fine for one person but 
not for another - they are using different versions of rtl_433, and 
different fine offset packet decodings.

so what can you do?

first of all, before you try to make any sense of the rain rate, first be 
sure that the rain count is working properly.  rain rate is a derived 
quantity, so if your rain count is incorrect, the rain rate will never be 
correct.

secondly, update to the latest rtl_433 and the latest weewx-sdr.  there are 
just too many variations of rtl_433 out there for me to make weewx-sdr work 
with every one.

then do some tests.  run weewx directly so that you can see each loop and 
archive packet as it happens.  capture them to file.  pour water into the 
rain bucket and see what happens.

sudo weewxd weewx.conf | tee /var/tmp/rain-test-packets.log

at that point it should be obvious where the problem is.

m

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/faa08a51-2d80-4e1f-944d-ac58df380430%40googlegroups.com.


Re: [weewx-user] Re: Rain rate too high with SDR driver?

2019-12-07 Thread S1m0n3
Il giorno martedì 27 novembre 2018 05:56:43 UTC+1, gjr80 ha scritto:
> OK, let's do the maths...
> 
> Assume the default rain window (rain_period) of 900 seconds (15 minutes). 
> WeeWX will calculate loop rainRate as sum of loop rainfall over the last 900 
> seconds * 3600/900.
> 
> First rain event is loop packet at 08:40:27 where 0.11811023622 fell. 
> Previous rainRate was 0.0 so we know no rain fell in the previous 15 minutes. 
> weeWX would calculate rainRate as 0.11811023622*3600/900 = 0.472440945. Log 
> indicates 0.472440944882.
> 
> Loop packets from 08:40:28 to 08:51:15 inclusive have no recorded rainfall so 
> rainRate remains at 0.11811023622*3600/900 = 0.472440945. Log indicates 
> 0.472440944882 in each loop packet.
> 
> Loop packet 08:51:40 has a rain event that includes 0.11811023622 rainfall. 
> weeWX would calculate rainRate as (0.11811023622+0.11811023622)*3600/900 = 
> 0.94488189. Log indicates 0.944881889764.
> 
> No further loop rainfall occurs so loop rainRate remains 0.944881889764 for 
> the rest of the screen capture. Had the screen capture continued and no 
> further rainfall occurred I would expect loop rainRate would decay to 
> 0.472440944882 in the first loop packet after 08:55:27. rainRate would drop 
> to 0.0 in the first loop packet after 09:06:40.
> 
> rainRate in archive records works a little differently, in particular when 
> software record generation is used (it's not clear what is being used in this 
> case but I expect it will be software record generation). When software 
> record generation is used the archive record rainRate is taken as the average 
> of the loop rainRate values seen during the archive period. In this case the 
> first archive record at 08:40:00 had seen no rain and rainRate = 0. The 
> screen capture indicates 0.0
> 
> The 08:42:00 archive record would have seen loop packets at 08:40:15, 
> 08:40:27 and 08:40:28 with respective rainRate values of 0, 0.472440944882 
> and 0.472440944882. The average of these is (2*0.472440944882)/3 = 
> 0.31496063. The screen capture indicates 0.31496063.
> 
> The 08:44:00 archive record will have seen the loop rainRate value of 
> 0.472440944882 seven times. The average being 0.472440944882. The screen 
> capture indicates 0.472440944882.
> 
> The 08:46:00 archive record saw loop rainRate of 0.472440944882 three times 
> so the resulting average is 0.472440944882. The 08:48:00 archive record saw 
> loop rainRate of 0.472440944882 four times so the resulting average is 
> 0.472440944882. The 08:50:00 archive record saw loop rainRate of 
> 0.472440944882 once so the resulting average is 0.472440944882. These values 
> agree with the screen capture.
> 
> The 08:52:00 archive record saw loop rainRate of 0.472440944882 three times 
> and 0.944881889764 once so the resulting average is 0.590551181102. The 
> screen capture indicates 0.590551181102.
> 
> The 08:54:00 archive record saw loop rainRate of 0.944881889764 three times 
> so the resulting average is 0.944881889764. The screen capture indicates 
> 0.944881889764.
> 
> So the upshot is given the rain values in the loop packets weeWX is 
> calculating loop and archive rainRate exactly as it should. Where I believe 
> the error lies is in the loop rain values as mentioned by the OP in post #3. 
> If we look at the first rain event the rain_total jumps from 63.0 to 63.3 yet 
> rain is recorded as 0.11811023622; we would have expected 0.3 ie the simple 
> difference between success rain_total values. Also, if we multiply 
> 0.11811023622 by 2.54 we get 0.3. So clearly we have a cm to inches 
> conversion occurring somewhere that is not needed. My quick look at the SDR 
> driver did not reveal anything, probably needs Matthew's eye!
> 
> Gary
> 
> 
> On Tuesday, 27 November 2018 01:49:13 UTC+10, Andrew Milner  wrote:
> 
> I cant get anything like the given rainrates for the period of the log
> 
> 
> A longer log extract is definitely needed!!
> 
> 
> 
> 
> On Monday, 26 November 2018 10:39:48 UTC+2, gjr80  wrote:Hi,
> What makes you say the rainRate is wrong? By default weeWX calculates 
> rainRate over a 15 minute sliding window, your screen capture covers 
> approximately 16 minutes with at least two rain events so seeing a non-zero 
> rain rate in all packets/records after the first rain event is expected. You 
> can change the window size by setting the rain_period config option in 
> weewx.cnf:
> [StdWXCalculate]
>     
>     [[Calculations]]
>         
>         rain_period = xxx
>         
> Where xxx is the rain_period to be used in seconds. You will need to restart 
> WeeWX or do a config reload for the new setting to take effect.
> Gary

After an year I've tried again to work with Weewx but I've same problem with 
rain 😢 can I do some things?! 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-us