Re: [weewx-user] Re: No RainData in Database (Ecowitt GW1000 driver)

[gjr80]

I forgot about that earlier post. It is up to you, the Seasons skin does 
not use any of the other fields, only rain and rainRate. I believe some of 
the RESTful uploads use dayRain if it exists, if dayRain does not exist 
todays rainfall is calculated from the database. There is little point in 
saving any of the other cumulative fields to database; they just take up 
space for none, if any, benefit as WeeWX can calculate day, week, month and 
year totals from WeeWX field rain.

Gary
On Saturday, 17 September 2022 at 23:09:45 UTC+10 marcusz...@gmail.com 
wrote:

> Hi Gary, all,
>
> am I assuming correctly that I need to map further fields beyond the ones 
> you mentioned?
> I was looking up "p_rain" and found this [1] conversation from early 
> summer.  
>
> Regards,
>   Marcus
>
>
>
> [1[   https://groups.google.com/g/weewx-user/c/lfkWXzsWaxw/m/jr6z0euNAwAJ
>
> Marcus Zurhorst schrieb am Samstag, 17. September 2022 um 13:33:31 UTC+2:
>
>> Thanks a lot, Gary.  👍
>>
>> Am Sa., 17. Sept. 2022 um 11:08 Uhr schrieb gjr80 :
>>
>>> The problem you are experiencing is that the Ecowitt Gateway driver 
>>> (formerly the GW1000 driver) emits the WS90 haptic rainfall data in fields 
>>> with a p_ prefix (eg p_rain instead of the default WeeWX field rain). 
>>> The reason for this is so as to not break support for existing tipping rain 
>>> gauges such as the WH40.
>>>
>>> You have two courses of action. If you have no plans to add a tipping 
>>> rain gauge, such as the WH40, you can simply map the required internal 
>>> Ecowitt Gateway driver haptic rainfall fields to the traditional WeeWX rain 
>>> fields. Alternatively, if you may add a tipping rain gauge in the future 
>>> you may wish to modify the WeeWX database to store the haptic rainfall 
>>> data. You would then need to modify the Seasons skin to display the haptic 
>>> rainfall data.
>>>
>>> Mapping the haptic rain fields to the traditional WeeWX rainfall fields 
>>> can be achieved with an alteration to the Ecowitt Gateway driver field map. 
>>> To do this:
>>> 1. edit weewx.conf and locate the [GW1000] stanza
>>> 2. at the end of the [GW1000] stanza contents (and before the next [] 
>>> stanza starts) add the following:
>>> [[field_map_extensions]]
>>> rain = p_rain
>>> rainRate = p_rainrate
>>> 3. save weewx.conf
>>>
>>> Restart WeeWX and the WeeWX rain and rainRate fields should now be 
>>> populated with haptic rainfall data (when it rains of course). The Seasons 
>>> skin should now display rain data/plots without alteration.
>>>
>>> If you wish to use the second approach you need to:
>>> 1. stop WeeWX if it is running
>>> 2. use the wee_database utility 
>>>  with the 
>>> --add-column action to add the columns (fields) p_rain and p_rainRate 
>>> to the database
>>> 3. edit the Seasons skin config file skin.conf (it should be located in 
>>> /home/weewx/skins/Seasons or /etc/weewx/skins/Seasons depending on your 
>>> WeeWX install type) and locate the [DisplayOptions] stanza
>>> 4. add p_rain and p_rainRate to the observations_current settings, it 
>>> should now look something like:
>>> observations_current = outTemp, heatindex, windchill, dewpoint, 
>>> outHumidity, barometer, windSpeed, rain, rainRate, p_rain, p_rainRate, 
>>> UV, radiation, lightning_strike_count, inTemp, inHumidity, extraTemp1, 
>>> extraHumid1, extraTemp2, extraHumid2, pm1_0, pm2_5, pm10_0
>>> note that obs will be displayed (if they exist) in the order they 
>>> appear in the list
>>> 5. repeat step 4 for the observations_stats, obs_type_sum and 
>>> obs_type_max (p_rainRate only) settings
>>> 6. locate the [ImageGenerator] [[dayimages]] [[[dayrain]]] stanza and 
>>> replace rain with p_rain, eg: 
>>>
>>> [[[dayrain]]]
>>> # Make sure the y-axis increment is at least 0.02 for the 
>>> rain plot
>>> yscale = None, None, 0.02
>>> plot_type = bar
>>> p_rain
>>> aggregate_type = sum
>>> aggregate_interval = hour
>>> label = Rain (hourly total)
>>> 7. repeat step 6 for [weekimages], [monthimages] and [yearimages]
>>> 8. save skin.conf
>>>
>>> Restart WeeWX and you should find the p_rain and p_rainRate fields now 
>>> exist in the database and are populated (when it rains) and the Seasons 
>>> skin should display the haptic rain data. Note the Seasons skin will also 
>>> display the tradition rain data without modification if you ever add a 
>>> tipping rain gauge, but there will need to be some modification to the 
>>> image plot definitions to include both rain and p_rain data in order 
>>> for both rain and p_rain to be plotted.
>>>
>>> Gary
>>>
>>> On Saturday, 17 September 2022 at 16:12:17 UTC+10 marcusz...@gmail.com 
>>> wrote:
>>>
 Hello all,

 I installed my WS90 some days ago and was surprised how easy this was 
 going.  The captured temperatures 

Re: [weewx-user] Re: FTP failure

[Steve Meltz]

Gary..I will check for the .php file later today...thanks
Vince..I intend on changing to Rsync once I get the gauges working again.
I'm sure I will have some problems when I do it,  and don't want to try and
fix 2 problems at the same time.

On Sat, Sep 17, 2022, 10:13 PM vince  wrote:

> You really should consider switching to rsync as your uploader.   It will
> go through all those files in a second or two total if you have any kind of
> reasonable internet bandwidth.   All you need to do is some relatively
> simple ssh setup so you can do a password-less ssh to your internet site.
>
> --
> 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/Nb_3fPRRiok/unsubscribe.
> To unsubscribe from this group and all its topics, 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/b9f21a2a-6a77-4cdf-bce9-d009f6623b8an%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/CAH0o-akG%3Df6K4suRMWCYYP98rYfiRQJFt2c7EsJu_Ch5eubcBw%40mail.gmail.com.

[weewx-user] Re: Driver for Tenx 1130:0829?

[Hans-Åke Lund]

Any progress on the driver for the this Cotech weather station from Clas 
Ohlson (36-7959)?
I have started to try to understand its USB protocol by sniffing with 
Wireshark on WeatherHome running in VirtualBox.
/Hans-Åke

måndag 29 augusti 2022 kl. 11:29:47 UTC+2 skrev sast...@gmail.com:

> So to be clear, what I did was connect via USB to the weather station 
> console.
> Outside unit reports to console, I wanted to read from the console.
> It also bears to mention that the unit is "off site", i.e. at the cabin.
>
> In my efforts I have seen some who have used RTL SDR units to get data 
> directly from the outside unit - I have not tried that. Lack of an SDR unit 
> .. and skills...
>
> What I *did* have though was an old Windows based laptop lying around.
> So I set that up to start the supplied WeatherHome software automatically 
> on boot, which will populate the WeatherHome.mdb database file - MS Access 
> I presume.
> In addition I setup WSL - Windows Subsystem for Linux - and installed the 
> "mdbtools" package.
> Inside WSL, the "mdb-export" tool inside "mdbtools" was able to export 
> data from "/mnt/c/ProgramData/WeatherHome/WeatherHome.mdb" and I could send 
> that data back to my home server.
>
> No, this is not a driver, but at least I'm getting data for now...
>
> So the next thing is getting a proper mapping for "wee_import". Separate 
> thread I guess.
>
> mandag 29. august 2022 kl. 10:55:14 UTC+2 skrev sven@gmail.com:
>
>> Great to see others interested. 
>> I will try to do something in the next weeks (heavy workload at the 
>> office right now).
>>
>> /Sven
>>
>> fredag 26 augusti 2022 kl. 15:10:25 UTC+2 skrev sast...@gmail.com:
>>
>>> There is probably a better way, and I'm not there yet, but here are the 
>>> changes:
>>>
>>> $ diff /usr/share/weewx/weewx/drivers/te923.py{,-20220826}
>>> 1503c1503
>>> < ENDPOINT_IN = 0x81
>>> ---
>>> > ENDPOINT_IN = 0x83  # 0x81
>>> 1513c1513,1514
>>> < def __init__(self, vendor_id=0x1130, product_id=0x6801,
>>> ---
>>> > #def __init__(self, vendor_id=0x1130, product_id=0x6801,
>>> > def __init__(self, vendor_id=0x1130, product_id=0x0829,
>>>
>>> Still only get a timeout.
>>>
>>> Aug 26 15:04:43 hostname systemd[1]: Starting LSB: weewx weather 
>>> system...
>>> Aug 26 15:04:43 hostname weewx[40158]:  * Starting weewx weather 
>>> system weewx
>>> Aug 26 15:04:43 hostname weewx[40169] INFO __main__: Initializing 
>>> weewx version 4.8.0
>>> Aug 26 15:04:43 hostname weewx[40169] INFO __main__: Using Python 
>>> 3.10.4 (main, Jun 29 2022, 12:14:53) [GCC 11.2.0]
>>> Aug 26 15:04:43 hostname weewx[40169] INFO __main__: Platform 
>>> Linux-5.15.0-46-generic-x86_64-with-glibc2.35
>>> Aug 26 15:04:43 hostname weewx[40169] INFO __main__: Locale is 
>>> 'LC_CTYPE=en_US.UTF-8;LC_NUMERIC=nb_NO.UTF-8;LC_TIME=nb_NO.UTF-8;LC_COLLATE=en_US.UTF-8;LC_MONETARY=nb_NO.UTF-8;LC_MESSAGES=en_US.UTF-8;LC_PAPER=nb_NO.UTF-8;LC_NAME=nb_NO.UTF-8;LC_ADDRESS=nb_NO.UTF-8;LC_TELEPHONE=nb_NO.UTF-8;LC_MEASUREMENT=nb_NO.UTF-8;LC_IDENTIFICATION=nb_NO.UTF-8'
>>> Aug 26 15:04:43 hostname weewx[40169] INFO __main__: Using 
>>> configuration file /etc/weewx/weewx.conf
>>> Aug 26 15:04:43 hostname weewx[40169] INFO __main__: Debug is 0
>>> Aug 26 15:04:43 hostname weewx[40169] INFO __main__: PID file is 
>>> /var/run/weewx.pid
>>> Aug 26 15:04:43 hostname weewx[40172] INFO weewx.engine: Loading 
>>> station type TE923 (weewx.drivers.te923)
>>> Aug 26 15:04:43 hostname weewx[40172] INFO weewx.drivers.te923: 
>>> driver version is 0.41.1
>>> Aug 26 15:04:43 hostname weewx[40172] INFO weewx.drivers.te923: 
>>> polling interval is 60
>>> Aug 26 15:04:43 hostname weewx[40172] INFO weewx.drivers.te923: 
>>> sensor map is {'windLinkStatus': 'link_wind', 'windBatteryStatus': 
>>> 'bat_wind', 'rainLinkStatus': 'link_rain', 'rainBatteryStatus': 'bat_rain', 
>>> 'uvLinkStatus': 'link_uv', 'uvBatteryStatus': 'bat_uv', 'inTemp': 't_in', 
>>> 'inHumidity': 'h_in', 'outTemp': 't_1', 'outHumidity': 'h_1', 
>>> 'outTempBatteryStatus': 'bat_1', 'outLinkStatus': 'link_1', 'extraTemp1': 
>>> 't_2', 'extraHumid1': 'h_2', 'extraBatteryStatus1': 'bat_2', 
>>> 'extraLinkStatus1': 'link_2', 'extraTemp2': 't_3', 'extraHumid2': 'h_3', 
>>> 'extraBatteryStatus2': 'bat_3', 'extraLinkStatus2': 'link_3', 'extraTemp3': 
>>> 't_4', 'extraHumid3': 'h_4', 'extraBatteryStatus3': 'bat_4', 
>>> 'extraLinkStatus3': 'link_4', 'extraTemp4': 't_5', 'extraHumid4': 'h_5', 
>>> 'extraBatteryStatus4': 'bat_5', 'extraLinkStatus4': 'link_5'}
>>> Aug 26 15:04:43 hostname weewx[40158]:...done.
>>> Aug 26 15:04:43 hostname systemd[1]: Started LSB: weewx weather 
>>> system.
>>> Aug 26 15:04:43 hostname weewx[40172] INFO weewx.drivers.te923: 
>>> Found device on USB bus= device=
>>> Aug 26 15:04:44 hostname weewx[40172] ERROR weewx.drivers.te923: 
>>> Failed attempt 1 of 5 to read data: [Errno 110] Operation t

Re: [weewx-user] Re: FTP failure

[Steve2Q]

Gary: my host told me how to access my log files, and in the instructions 
was this:

" I checked on the error logs, and today's log is empty, which is good in
the way that it would indicate the hosting environment is working
correctly. Please check on the logs and if you need further support let
us know, we'll be happy to help."

The error.log for today is empty.

The .php file WAS missing from /Weather, but my adding it does not appear 
to have changed anything.


-- 
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/24068202-678f-4b7f-99b0-d967ad85a015n%40googlegroups.com.

RE: [weewx-user] Re: Lightning Strike issues

[dave.spicer2012]

Thank you Gary, That seems to have done the trick.

 

Thanks

Dave

 

From: weewx-user@googlegroups.com  On Behalf Of 
gjr80
Sent: Friday, September 16, 2022 7:37 PM
To: weewx-user 
Subject: Re: [weewx-user] Re: Lightning Strike issues

 

The reason you are seeing such large lightning strike numbers reported by WeeWX 
is that your station reports a cumulative lightning strike count, but WeeWX 
requires a per-period count. As posted earlier, the solution is to tell the SDR 
driver the lightning_strike_count field is a delta that is derived from the 
cumulative strike count. This is done via the highlighted lines below that were 
included in the earlier post:

 

[SDR]

[[sensors_map]]

strike_total = strike_count.494.AcuriteAtlasPacket

lightning_distance = strike_distance.494.AcuriteAtlasPacket

[[deltas]]

lightning_strike_count = strike_total

 

Have you included similar lines? Did you restart WeeWX after making the 
changes? Also note that unless you deleted the old cumulative data from WeeWX 
it will likely take an hour for the effects of any old cumulative data to 
disappear from last hour total.

 

Gary

On Saturday, 17 September 2022 at 08:10:54 UTC+10 dave.sp...@gmail.com 
  wrote:

My acurite sensor is reporting correct lightning data. In the loop data I see 
'lightning_distance': 7, 'lightning_strike_count': 296, but on the web page it 
is saying that strikes are 9768 and the hourly total of approx. 28+. How do 
I get it to where it shows that current data instead of erroneous values?

 

 

  

 

 

I would except to see strikes by at 7

 

Also how do I get a graft to see the distance? I am running the default seasons 
4.8.0 skin

 

Thanks

Dave

 

From: weewx...@googlegroups.com   
mailto:weewx...@googlegroups.com> > On Behalf Of 
vince
Sent: Friday, September 16, 2022 12:53 PM
To: weewx-user mailto:weewx...@googlegroups.com> >
Subject: [weewx-user] Re: Lightning Strike issues

 

"Is not correct" isn't much to go on. What are you expecting to see ?

 

See https://github.com/weewx/weewx/wiki/faq-how-to-report-a-problem

 

I don't know about your station in particular, but WeatherFlow stations 
frequently can show thousands of bogus lightning strikes due to the inexpensive 
sensor that vendor uses.  Fix there is to rotate the sensor 90 degrees which 
amazingly does work in quieting down erroneous strike readings.  Acurite has a 
web page on your station at 
https://support.acurite.com/hc/en-us/articles/360045278273-AcuRite-Atlas-7-in-1-Inaccurate-Lightning
 if that helps any.

-- 
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/07aa5e30-cafe-456c-a4a7-3dcb55fa460bn%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/8ddac774-6eab-4bad-820b-46341af2bd35n%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/03ec01d8cba6%24fa3e82c0%24eebb8840%24%40gmail.com.

Re: [weewx-user] Re: FTP failure

[gjr80]

Steve,

That has partially fixed the problem; I can now see gauge-data.txt is being 
uploaded to your web server, though it is appearing in a different 
directory to that expected by the SteelSeries Gauges javascript. I 
recommend leaving the SteelsSeries gauges as is and altering 
post_gauge-data.php to save gauge-data.txt to the correct directory. If you 
can edit the post_gauge-data.php file on your web server and locate the 
following line (circa line 28):

$json_file = "./gauge-data.txt";

then change it to read:

$json_file = "./ss/gauge-data.txt";

Save the file. Note depending on your host you may not be able to edit 
files directly on the web server, you may need to edit a local copy and 
then manually upload it.

No need to restart anything, the gauges should start to work again in a few 
seconds.

Gary

On Monday, 19 September 2022 at 03:53:49 UTC+10 Steve2Q wrote:

>
> Gary: my host told me how to access my log files, and in the instructions 
> was this:
>
> " I checked on the error logs, and today's log is empty, which is good in
> the way that it would indicate the hosting environment is working
> correctly. Please check on the logs and if you need further support let
> us know, we'll be happy to help."
>
> The error.log for today is empty.
>
> The .php file WAS missing from /Weather, but my adding it does not appear 
> to have changed anything.
>
>
>

-- 
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/b92f8f92-9702-41dd-9803-b2aecd5e7941n%40googlegroups.com.