Re: [weewx-user] "First Light", working, but with some problems

[Craig Young]

I found a solution that results in the DB and WU being updated each minute.
First, I set weewx config back to the original settings:
[StdArchive]
  archive_interval = 60
  archive_delay = 5

Then I changed the driver to output two types of loop packets:
a) if there was no data received from the data logger after 5 seconds then 
a null packet of only 'dateTime' and 'usUnits' was returned to weewx.
b) if data was received within 5 seconds then the full loop packet was 
returned to weewx.
The driver is essentially called every 5 seconds by weewx.  So 1 full loop 
packet is received each minute and this is written to the DB and WU updated.

Problem solved.

Craig


On Monday, October 2, 2023 at 10:09:52 AM UTC+13 Craig Young wrote:

> This also updates the DB and WU every minute:
> [StdArchive]
>   archive_interval = 1
>   archive_delay = 10
>
> I tried archive_interval = 0 but got a divide by zero exception.  I assume 
> that is because the software tried to calculate an average for the archive 
> record by dividing the # of loop records received in that interval by the 
> archive interval in seconds.
> Craig
>
>
> On Monday, October 2, 2023 at 4:31:18 AM UTC+13 Craig Young wrote:
>
>> The "429" error is fixed.  Thanks Karen and Tom.
>> The 2 minute update problem, I changed the driver to poll the hardware 
>> (serial port) every 15 seconds, but the database still updated every 2 
>> minutes.  After playing with several parameters in the driver and 
>> weewx.conf I finally got the database to update every 1 minute and WU to 
>> also update every minute.  To do this I had to make this change:
>> [StdArchive]
>>   archive_interval = 15
>>
>> This resulted in an error message when I started weewx (from SYSLOG):
>> WARNING weewx.engine: Archive delay (15) is unusually long
>>
>> I thought reducing it from 60 sec to 15 sec would get an error of it 
>> being too short.
>>
>> In the Database the records show an interval of 0.25 but they are now 
>> being updated every 1 minute which I assume is because the driver is 
>> sending a loop packet every 1 minute.  So the problem appears to be related 
>> to the archive record interval.  Here is what I think may be happening.  
>> Weewx gets a loop packet and processes it, control is then returned to the 
>> driver.  The driver, 1 minute later, sends another loop packet.  Weewx THEN 
>> begins a 1 minute archive interval and then processes the archive record, 
>> so two minutes later.  I did notice the error message says archive 
>> "delay".  In theory, if I set the delay to 0 then when a loop packet 
>> arrives, once every minute from the driver, then weewx would immediately 
>> write it to the DB and update WU.  Is that correct?
>>
>> Craig
>>
>> On Monday, October 2, 2023 at 1:31:06 AM UTC+13 Tom Keffer wrote:
>>
>>> First, a note on how weewxd works: the driver blocks, waiting for data 
>>> to come in. The program cannot do anything while it is blocked. Once data 
>>> comes in, then it can proceed, emit a LOOP packet, then the rest of the 
>>> program can process it.
>>>
>>> Your fileparse polling interval is 60 seconds. This means that it will 
>>> sleep for 60 seconds before reading new data from the file. Nothing will 
>>> happen until it wakes up. 
>>>
>>> Meanwhile, your archive interval is 60 seconds. This means weewxd will 
>>> take whatever data has accumulated over the previous 60 seconds and use it 
>>> to create an archive record.
>>>
>>> With such a short archive interval and long LOOP polling interval, you 
>>> can see how it's easy for the program to be sleeping, or have nothing 
>>> available at the one minute mark.
>>>
>>> Solution: if you can, have data available more frequently than once 
>>> every 60 seconds. This would allow you to shorten the fileparse polling 
>>> interval. If that's not possible, lengthen the archive interval to at least 
>>> 5 minutes.
>>>
>>> Best yet, do both.
>>>
>>> As for the "429" error, this is happening because your system is trying 
>>> to register too frequently. Almost all weewx stations do this because the 
>>> default registration interval does not work well with the station 
>>> registration. You can ignore it, or tell weewx to do the station 
>>> registration less frequently. In weewx.conf:
>>>
>>> [StdRESTful]
>>> [[StationRegistry]]
>>> register_this_station = false
>>> post_interval = 86400
>>>
>>>
>>>
>>> Station registration is working fine. 
>>>
>>> -tk
>>>
>>> On Sat, Sep 30, 2023 at 8:57 PM Craig Young  
>>> wrote:
>>>
 After writing a new driver for my station and configuring weewx to 
 support its  data stream I was able to run weewx live for a few minutes, 
 then shut it down to check SYSLOG (debug=2).
 There appears to be two problems (see attached syslog excerpt):

 a) The database and reports are updating on two minutes intervals.  The 
 config file has this set for 1 minute intervals:
 "INFO weewx.engine: Using archive interval of 60 seconds 

Re: [weewx-user] want to use lux value to calculate value for 'radiation'

[gjr80]

So what is your reason for saying "it doesn't work", are you looking at web 
page output, a plot etc or did you look at the loop packet data being 
emitted by your driver? The former two are really at the end of the whole 
processing chain, so there are many opportunities for things to go awry 
beforehand. The latter is pretty much straight from the driver and if you 
observe the loop packets when running WeeWX directly you will see the 
effects of your [StdCalibrate]] [[Corrections]] stanza.

There is a lot of general comments and minor config snippets in this thread 
and it is difficult to determine exactly what is bering used and what is 
going on. Could I suggest we take this from the top and you:
1. Post the output from wee_debug 
. This will 
give a current and complete picture of your WeeWX config. When posting 
wee_debug output do check the content for sensitive information (eg user 
names, passwords, API keys etc), wee_debug is pretty good at obfuscating 
such content but it is not perfect. 
2. Run WeeWX directly 
. This will 
display loop packets (lines starting with LOOP:) and archive records (lines 
starting with REC:) directly on the console. Let WeeWX run so you see at 
least two archive records (lines starting with REC:) and post the entire 
output here.

Setting up a calibration correction such as this is not complex, this 
should be easy to troubleshoot and rectify.

Gary
On Monday, 2 October 2023 at 03:28:01 UTC+10 kevinjc...@gmail.com wrote:

> did it, still not working. oh well.
>
> On Friday, September 29, 2023 at 4:00:06 PM UTC-4 Eric K wrote:
>
>> You have to restart weewx before changes made to the weewx.conf file will 
>> take effect.
>> If you've restarted weewx, you should start to see additions to the 
>> graphs, every 5 minutes.
>>
>> On Friday, September 29, 2023 at 2:49:54 PM UTC-5 Kevin Crivelli wrote:
>>
>>> Should it reflect in the graphs immediately? I was able to login to ssh 
>>> from work and make the change but I'm not seeing any change in the graphs
>>>
>>> On Fri, Sep 29, 2023, 3:09 PM Kevin Crivelli  
>>> wrote:
>>>
 Thank you! I'm gonna try this. Let ya know how it works out 

 On Fri, Sep 29, 2023, 11:17 AM Eric Koester  
 wrote:

> Kevin Crivelli,Here's what my [[Corrections]] section looks like.
> Mine uses '> 0' rather than 'not None'
>
> [StdCalibrate]
>>
>> [[Corrections]]
>> # For each type, an arbitrary calibration expression can be 
>> given.
>> # It should be in the units defined in the StdConvert section.
>> # Example:  foo = foo + 0.2
>> radiation = luminosity * 0.00789 if luminosity > 0 else None
>> lightning_distance = lightning_distance / 1.609 if 
>> lightning_strike_count > 0 else None#convert distance to miles
>
>
> On Wed, Sep 27, 2023 at 6:49 PM Kevin Crivelli  
> wrote:
>
>> [StdCalibrate]
>> 
>> [[Corrections]]
>> windDir = windDir if windSpeed > 0 else None
>> lightning_distance = lightning_distance if 
>> lightning_strike_count > 0 else None
>> # For each type, an arbitrary calibration expression can be 
>> given.
>> # It should be in the units defined in the StdConvert 
>> section.
>> # Example:
>> foo = foo + 0.2
>> radiation = luminosity/126.7 if luminosity is not None else 
>> None
>>
>>
>> On Wednesday, September 27, 2023 at 7:11:05 PM UTC-4 Eric K wrote:
>>
>>> Share the [StdCalibrate]  [[Corrections]] section of your weewx.conf 
>>> file with us.
>>>
>>> On Wednesday, September 27, 2023 at 5:53:10 PM UTC-5 Kevin Crivelli 
>>> wrote:
>>>
>>> I have the same problem but this didn't work for me. any ideas?
>>>
>>> On Tuesday, May 18, 2021 at 6:04:08 PM UTC-4 Greg Troxel wrote:
>>>
>>>
>>> Eric K <> writes: 
>>>
>>> > The Acurite Atlas weather sensor provides a UV and a lux value, 
>>> but not a 
>>> > radiation value. 
>>> > I want to use this formula to calculate solar radiation from the 
>>> lux sensor 
>>> > in the Acurite Atlas: radiation = lux * 0.0079 
>>>
>>> See also 
>>>
>>> https://github.com/weewx/weewx/wiki/Watts-and-lux 
>>>
>>> -- 
>> 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/oWp-9LivDJo/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> 

Re: [weewx-user] "First Light", working, but with some problems

[Craig Young]

This also updates the DB and WU every minute:
[StdArchive]
  archive_interval = 1
  archive_delay = 10

I tried archive_interval = 0 but got a divide by zero exception.  I assume 
that is because the software tried to calculate an average for the archive 
record by dividing the # of loop records received in that interval by the 
archive interval in seconds.
Craig


On Monday, October 2, 2023 at 4:31:18 AM UTC+13 Craig Young wrote:

> The "429" error is fixed.  Thanks Karen and Tom.
> The 2 minute update problem, I changed the driver to poll the hardware 
> (serial port) every 15 seconds, but the database still updated every 2 
> minutes.  After playing with several parameters in the driver and 
> weewx.conf I finally got the database to update every 1 minute and WU to 
> also update every minute.  To do this I had to make this change:
> [StdArchive]
>   archive_interval = 15
>
> This resulted in an error message when I started weewx (from SYSLOG):
> WARNING weewx.engine: Archive delay (15) is unusually long
>
> I thought reducing it from 60 sec to 15 sec would get an error of it being 
> too short.
>
> In the Database the records show an interval of 0.25 but they are now 
> being updated every 1 minute which I assume is because the driver is 
> sending a loop packet every 1 minute.  So the problem appears to be related 
> to the archive record interval.  Here is what I think may be happening.  
> Weewx gets a loop packet and processes it, control is then returned to the 
> driver.  The driver, 1 minute later, sends another loop packet.  Weewx THEN 
> begins a 1 minute archive interval and then processes the archive record, 
> so two minutes later.  I did notice the error message says archive 
> "delay".  In theory, if I set the delay to 0 then when a loop packet 
> arrives, once every minute from the driver, then weewx would immediately 
> write it to the DB and update WU.  Is that correct?
>
> Craig
>
> On Monday, October 2, 2023 at 1:31:06 AM UTC+13 Tom Keffer wrote:
>
>> First, a note on how weewxd works: the driver blocks, waiting for data to 
>> come in. The program cannot do anything while it is blocked. Once data 
>> comes in, then it can proceed, emit a LOOP packet, then the rest of the 
>> program can process it.
>>
>> Your fileparse polling interval is 60 seconds. This means that it will 
>> sleep for 60 seconds before reading new data from the file. Nothing will 
>> happen until it wakes up. 
>>
>> Meanwhile, your archive interval is 60 seconds. This means weewxd will 
>> take whatever data has accumulated over the previous 60 seconds and use it 
>> to create an archive record.
>>
>> With such a short archive interval and long LOOP polling interval, you 
>> can see how it's easy for the program to be sleeping, or have nothing 
>> available at the one minute mark.
>>
>> Solution: if you can, have data available more frequently than once every 
>> 60 seconds. This would allow you to shorten the fileparse polling interval. 
>> If that's not possible, lengthen the archive interval to at least 5 minutes.
>>
>> Best yet, do both.
>>
>> As for the "429" error, this is happening because your system is trying 
>> to register too frequently. Almost all weewx stations do this because the 
>> default registration interval does not work well with the station 
>> registration. You can ignore it, or tell weewx to do the station 
>> registration less frequently. In weewx.conf:
>>
>> [StdRESTful]
>> [[StationRegistry]]
>> register_this_station = false
>> post_interval = 86400
>>
>>
>>
>> Station registration is working fine. 
>>
>> -tk
>>
>> On Sat, Sep 30, 2023 at 8:57 PM Craig Young  wrote:
>>
>>> After writing a new driver for my station and configuring weewx to 
>>> support its  data stream I was able to run weewx live for a few minutes, 
>>> then shut it down to check SYSLOG (debug=2).
>>> There appears to be two problems (see attached syslog excerpt):
>>>
>>> a) The database and reports are updating on two minutes intervals.  The 
>>> config file has this set for 1 minute intervals:
>>> "INFO weewx.engine: Using archive interval of 60 seconds (software 
>>> record generation)"
>>>
>>>  Maybe there is some other setting required?
>>>
>>> b) There are several HTTP ERROR 429: TOO MANY REQUESTS messages.  Not 
>>> sure why this is happening.
>>>
>>> I think I am close to a fully operational system, just need to clean up 
>>> a few things.
>>>
>>> Craig
>>>
>>> -- 
>>> 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/b8903053-6813-45e1-a804-aa5b566d7bdan%40googlegroups.com
>>>  
>>> 
>>> .
>>>

[weewx-user] Re: Add soil moisture data

[Invisible Man]

Ok, I'm approaching the solution. In skin.conf I added the following to 
generate the daymoistsoil.png

+   [[[daymoistsoil]]]
+soilMoist1

and then in index.html.tmpl:

+ 

It should be working... at least daymoistsoil.png gets generated.
On Sunday, October 1, 2023 at 3:51:57 PM UTC+2 Invisible Man wrote:

> Hi,
> I *just acquired a new soil moisture sensor* (EcoWitt). I added it to the 
> weather station and it works fine. Now, I'd like to get the value with 
> Weewx. 
> I already use the the *Interceptor* driver (
> https://github.com/matthewwall/weewx-interceptor) which works fine for 
> months/years, and I see now the new soil moisture data in it.
> But* I forgot how to do add the value to Weewx and both display the 
> current moisture + display a curve for it.* Can you help me out ?
>
> This is the interceptor packet:
>
> Oct  1 15:17:39 vegan weewx[14762] DEBUG user.interceptor: raw packet: 
> {'dateTime': 1696166258, 'usUnits': 1, 'temperature_in': 80.1, 
> 'humidity_in': 54.0, 'pressure': 29.935, 'temperature_out': 83.5, 
> 'humidity_out': 49.0, 'wind_dir': 279.0, 'wind_speed': 0.45, 'wind_gust': 
> 2.24, 'solar_radiation': 407.46, 'uv': 3.0, 'rain_rate': 0.0, 'rain_total': 
> 10.74, 'soil_moisture_1': 23.0, 'wh65_battery': 0.0, 'wh25_battery': 0.0, 
> 'soil_battery_1': 1.4, 'rain': 0.0}
> Oct  1 15:17:39 vegan weewx[14762] DEBUG user.interceptor: mapped packet: 
> {'dateTime': 1696166258, 'usUnits': 1, 'pressure': 29.935, 'outHumidity': 
> 49.0, 'inHumidity': 54.0, 'outTemp': 83.5, 'inTemp': 80.1, 'windSpeed': 
> 0.45, 'windGust': 2.24, 'windDir': 279.0, 'radiation': 407.46, 'rain': 0.0, 
> 'rainRate': 0.0, 'UV': 3.0,* 'soilMoist1': 23.0*}
>
> Notice soilMoist1. That's what I want to get :)
>
> I am running:
>
>
>- Weewx 4.10.2
>- on a Raspberry Pi 3
>- The weather station is a EcoWitt HP2551AE_Pro_V1.8.0
>
> I have the weather station & Weewx for years, and it works. It's just the 
> sensor that I added today :)
>
> Interceptor configuration:
>
> [Interceptor]
> driver = user.interceptor
> device_type = ecowitt-client
> port = 8090
> iface = eth0
>
> Thanks !
> Axelle
>

-- 
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/cf6fdbc2-db72-4ea1-a8fb-5378b869b8a0n%40googlegroups.com.

Re: [weewx-user] want to use lux value to calculate value for 'radiation'

[Kevin Crivelli]

did it, still not working. oh well.

On Friday, September 29, 2023 at 4:00:06 PM UTC-4 Eric K wrote:

> You have to restart weewx before changes made to the weewx.conf file will 
> take effect.
> If you've restarted weewx, you should start to see additions to the 
> graphs, every 5 minutes.
>
> On Friday, September 29, 2023 at 2:49:54 PM UTC-5 Kevin Crivelli wrote:
>
>> Should it reflect in the graphs immediately? I was able to login to ssh 
>> from work and make the change but I'm not seeing any change in the graphs
>>
>> On Fri, Sep 29, 2023, 3:09 PM Kevin Crivelli  
>> wrote:
>>
>>> Thank you! I'm gonna try this. Let ya know how it works out 
>>>
>>> On Fri, Sep 29, 2023, 11:17 AM Eric Koester  wrote:
>>>
 Kevin Crivelli,Here's what my [[Corrections]] section looks like.
 Mine uses '> 0' rather than 'not None'

 [StdCalibrate]
>
> [[Corrections]]
> # For each type, an arbitrary calibration expression can be 
> given.
> # It should be in the units defined in the StdConvert section.
> # Example:  foo = foo + 0.2
> radiation = luminosity * 0.00789 if luminosity > 0 else None
> lightning_distance = lightning_distance / 1.609 if 
> lightning_strike_count > 0 else None#convert distance to miles


 On Wed, Sep 27, 2023 at 6:49 PM Kevin Crivelli  
 wrote:

> [StdCalibrate]
> 
> [[Corrections]]
> windDir = windDir if windSpeed > 0 else None
> lightning_distance = lightning_distance if 
> lightning_strike_count > 0 else None
> # For each type, an arbitrary calibration expression can be 
> given.
> # It should be in the units defined in the StdConvert section.
> # Example:
> foo = foo + 0.2
> radiation = luminosity/126.7 if luminosity is not None else 
> None
>
>
> On Wednesday, September 27, 2023 at 7:11:05 PM UTC-4 Eric K wrote:
>
>> Share the [StdCalibrate]  [[Corrections]] section of your weewx.conf 
>> file with us.
>>
>> On Wednesday, September 27, 2023 at 5:53:10 PM UTC-5 Kevin Crivelli 
>> wrote:
>>
>> I have the same problem but this didn't work for me. any ideas?
>>
>> On Tuesday, May 18, 2021 at 6:04:08 PM UTC-4 Greg Troxel wrote:
>>
>>
>> Eric K <> writes: 
>>
>> > The Acurite Atlas weather sensor provides a UV and a lux value, but 
>> not a 
>> > radiation value. 
>> > I want to use this formula to calculate solar radiation from the 
>> lux sensor 
>> > in the Acurite Atlas: radiation = lux * 0.0079 
>>
>> See also 
>>
>> https://github.com/weewx/weewx/wiki/Watts-and-lux 
>>
>> -- 
> 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/oWp-9LivDJo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/fc6b65b0-69be-4ec7-9763-675f62302f48n%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+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/CADh_orjKiziRwWUTK%3DgGN2Kao%3DB3n4FGRvvmTDGn355iLpDRqQ%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/df1b5f69-e1b2-4f64-bd7a-eaa8353d4506n%40googlegroups.com.

Re: [weewx-user] "First Light", working, but with some problems

[Craig Young]

The "429" error is fixed.  Thanks Karen and Tom.
The 2 minute update problem, I changed the driver to poll the hardware 
(serial port) every 15 seconds, but the database still updated every 2 
minutes.  After playing with several parameters in the driver and 
weewx.conf I finally got the database to update every 1 minute and WU to 
also update every minute.  To do this I had to make this change:
[StdArchive]
  archive_interval = 15

This resulted in an error message when I started weewx (from SYSLOG):
WARNING weewx.engine: Archive delay (15) is unusually long

I thought reducing it from 60 sec to 15 sec would get an error of it being 
too short.

In the Database the records show an interval of 0.25 but they are now being 
updated every 1 minute which I assume is because the driver is sending a 
loop packet every 1 minute.  So the problem appears to be related to the 
archive record interval.  Here is what I think may be happening.  Weewx 
gets a loop packet and processes it, control is then returned to the 
driver.  The driver, 1 minute later, sends another loop packet.  Weewx THEN 
begins a 1 minute archive interval and then processes the archive record, 
so two minutes later.  I did notice the error message says archive 
"delay".  In theory, if I set the delay to 0 then when a loop packet 
arrives, once every minute from the driver, then weewx would immediately 
write it to the DB and update WU.  Is that correct?

Craig

On Monday, October 2, 2023 at 1:31:06 AM UTC+13 Tom Keffer wrote:

> First, a note on how weewxd works: the driver blocks, waiting for data to 
> come in. The program cannot do anything while it is blocked. Once data 
> comes in, then it can proceed, emit a LOOP packet, then the rest of the 
> program can process it.
>
> Your fileparse polling interval is 60 seconds. This means that it will 
> sleep for 60 seconds before reading new data from the file. Nothing will 
> happen until it wakes up. 
>
> Meanwhile, your archive interval is 60 seconds. This means weewxd will 
> take whatever data has accumulated over the previous 60 seconds and use it 
> to create an archive record.
>
> With such a short archive interval and long LOOP polling interval, you can 
> see how it's easy for the program to be sleeping, or have nothing available 
> at the one minute mark.
>
> Solution: if you can, have data available more frequently than once every 
> 60 seconds. This would allow you to shorten the fileparse polling interval. 
> If that's not possible, lengthen the archive interval to at least 5 minutes.
>
> Best yet, do both.
>
> As for the "429" error, this is happening because your system is trying to 
> register too frequently. Almost all weewx stations do this because the 
> default registration interval does not work well with the station 
> registration. You can ignore it, or tell weewx to do the station 
> registration less frequently. In weewx.conf:
>
> [StdRESTful]
> [[StationRegistry]]
> register_this_station = false
> post_interval = 86400
>
>
>
> Station registration is working fine. 
>
> -tk
>
> On Sat, Sep 30, 2023 at 8:57 PM Craig Young  wrote:
>
>> After writing a new driver for my station and configuring weewx to 
>> support its  data stream I was able to run weewx live for a few minutes, 
>> then shut it down to check SYSLOG (debug=2).
>> There appears to be two problems (see attached syslog excerpt):
>>
>> a) The database and reports are updating on two minutes intervals.  The 
>> config file has this set for 1 minute intervals:
>> "INFO weewx.engine: Using archive interval of 60 seconds (software record 
>> generation)"
>>
>>  Maybe there is some other setting required?
>>
>> b) There are several HTTP ERROR 429: TOO MANY REQUESTS messages.  Not 
>> sure why this is happening.
>>
>> I think I am close to a fully operational system, just need to clean up a 
>> few things.
>>
>> Craig
>>
>> -- 
>> 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/b8903053-6813-45e1-a804-aa5b566d7bdan%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/a1fe83ad-4a22-4393-907a-875566c1c49en%40googlegroups.com.

[weewx-user] Add soil moisture data

[Invisible Man]

Hi,
I *just acquired a new soil moisture sensor* (EcoWitt). I added it to the 
weather station and it works fine. Now, I'd like to get the value with 
Weewx. 
I already use the the *Interceptor* driver 
(https://github.com/matthewwall/weewx-interceptor) which works fine for 
months/years, and I see now the new soil moisture data in it.
But* I forgot how to do add the value to Weewx and both display the current 
moisture + display a curve for it.* Can you help me out ?

This is the interceptor packet:

Oct  1 15:17:39 vegan weewx[14762] DEBUG user.interceptor: raw packet: 
{'dateTime': 1696166258, 'usUnits': 1, 'temperature_in': 80.1, 
'humidity_in': 54.0, 'pressure': 29.935, 'temperature_out': 83.5, 
'humidity_out': 49.0, 'wind_dir': 279.0, 'wind_speed': 0.45, 'wind_gust': 
2.24, 'solar_radiation': 407.46, 'uv': 3.0, 'rain_rate': 0.0, 'rain_total': 
10.74, 'soil_moisture_1': 23.0, 'wh65_battery': 0.0, 'wh25_battery': 0.0, 
'soil_battery_1': 1.4, 'rain': 0.0}
Oct  1 15:17:39 vegan weewx[14762] DEBUG user.interceptor: mapped packet: 
{'dateTime': 1696166258, 'usUnits': 1, 'pressure': 29.935, 'outHumidity': 
49.0, 'inHumidity': 54.0, 'outTemp': 83.5, 'inTemp': 80.1, 'windSpeed': 
0.45, 'windGust': 2.24, 'windDir': 279.0, 'radiation': 407.46, 'rain': 0.0, 
'rainRate': 0.0, 'UV': 3.0,* 'soilMoist1': 23.0*}

Notice soilMoist1. That's what I want to get :)

I am running:


   - Weewx 4.10.2
   - on a Raspberry Pi 3
   - The weather station is a EcoWitt HP2551AE_Pro_V1.8.0

I have the weather station & Weewx for years, and it works. It's just the 
sensor that I added today :)

Interceptor configuration:

[Interceptor]
driver = user.interceptor
device_type = ecowitt-client
port = 8090
iface = eth0

Thanks !
Axelle

-- 
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/e5d7e20e-0724-422b-90b3-e31f3028a7e3n%40googlegroups.com.

Re: [weewx-user] Re: Getting no chart or graph - just the looped data

[kd4e]

Great news for many as the inovato Quadra comes already in a cabinet, and 
is easy to set up.

I appreciate all the work you've done on WeeWx and your patience in helping 
me to get it working.

Next step are to feed to WU, my personal web site, and Amateur Radio APRS.

Thanks again!  
On Saturday, September 30, 2023 at 8:37:59 PM UTC-7 vince wrote:

> Yes - thanks
>
> Here's my 4GB RAM pi4 speeds writing to SD card...
> Sep 30 20:35:18 pi4 weewx[29063] INFO weewx.cheetahgenerator: Generated 8 
> files for report SeasonsReport in 1.99 seconds
> Sep 30 20:35:19 pi4 weewx[29063] INFO weewx.imagegenerator: Generated 17 
> images for report SeasonsReport in 0.81 seconds
> Sep 30 20:35:19 pi4 weewx[29063] INFO weewx.reportengine: Copied 0 files 
> to /home/pi/weewx-data/public_html/Seasons
>
> And your Quadro's speeds from your logs...
> Sep 30 17:55:19 inovato weewx[5282] INFO weewx.cheetahgenerator: Generated 
> 8 files for report SeasonsReport in 3.24 seconds
> Sep 30 17:55:20 inovato weewx[5282] INFO weewx.imagegenerator: Generated 
> 10 images for report SeasonsReport in 0.90 seconds
>
> So your box definitely looks like a great little weewx platform for a very 
> good price
>
>

-- 
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/aaec9e1b-e386-410c-b0c7-83e4db523bf4n%40googlegroups.com.

Re: [weewx-user] "First Light", working, but with some problems

[Tom Keffer]

First, a note on how weewxd works: the driver blocks, waiting for data to
come in. The program cannot do anything while it is blocked. Once data
comes in, then it can proceed, emit a LOOP packet, then the rest of the
program can process it.

Your fileparse polling interval is 60 seconds. This means that it will
sleep for 60 seconds before reading new data from the file. Nothing will
happen until it wakes up.

Meanwhile, your archive interval is 60 seconds. This means weewxd will take
whatever data has accumulated over the previous 60 seconds and use it to
create an archive record.

With such a short archive interval and long LOOP polling interval, you can
see how it's easy for the program to be sleeping, or have nothing available
at the one minute mark.

Solution: if you can, have data available more frequently than once every
60 seconds. This would allow you to shorten the fileparse polling interval.
If that's not possible, lengthen the archive interval to at least 5 minutes.

Best yet, do both.

As for the "429" error, this is happening because your system is trying to
register too frequently. Almost all weewx stations do this because the
default registration interval does not work well with the station
registration. You can ignore it, or tell weewx to do the station
registration less frequently. In weewx.conf:

[StdRESTful]
[[StationRegistry]]
register_this_station = false
post_interval = 86400



Station registration is working fine.

-tk

On Sat, Sep 30, 2023 at 8:57 PM Craig Young 
wrote:

> After writing a new driver for my station and configuring weewx to support
> its  data stream I was able to run weewx live for a few minutes, then shut
> it down to check SYSLOG (debug=2).
> There appears to be two problems (see attached syslog excerpt):
>
> a) The database and reports are updating on two minutes intervals.  The
> config file has this set for 1 minute intervals:
> "INFO weewx.engine: Using archive interval of 60 seconds (software record
> generation)"
>
>  Maybe there is some other setting required?
>
> b) There are several HTTP ERROR 429: TOO MANY REQUESTS messages.  Not sure
> why this is happening.
>
> I think I am close to a fully operational system, just need to clean up a
> few things.
>
> Craig
>
> --
> 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/b8903053-6813-45e1-a804-aa5b566d7bdan%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/CAPq0zECD4k69SRaqQok7MhQC6OtMF0SQEBw7%2B5pAJzm6HGXfGQ%40mail.gmail.com.

[weewx-user] Re: "First Light", working, but with some problems

[Karen K]

b) Your should look which service creates those messages. According to your 
log it ist "StationRegistry". So, what is "post_interval" saying in your 
weewx.conf? Besides that, if I remember it correctly, station registry is 
not working actually. Try setting "register_this_station" to "false".

Craig Young schrieb am Sonntag, 1. Oktober 2023 um 05:57:10 UTC+2:

> After writing a new driver for my station and configuring weewx to support 
> its  data stream I was able to run weewx live for a few minutes, then shut 
> it down to check SYSLOG (debug=2).
> There appears to be two problems (see attached syslog excerpt):
>
> a) The database and reports are updating on two minutes intervals.  The 
> config file has this set for 1 minute intervals:
> "INFO weewx.engine: Using archive interval of 60 seconds (software record 
> generation)"
>
>  Maybe there is some other setting required?
>
> b) There are several HTTP ERROR 429: TOO MANY REQUESTS messages.  Not sure 
> why this is happening.
>
> I think I am close to a fully operational system, just need to clean up a 
> few things.
>
> Craig
>

-- 
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/e7efb0cf-2c97-49f2-a006-3daca83690e9n%40googlegroups.com.