[weewx-user] Re: whew and gw1000

[gjr80]

All WeeWX-WD is a couple of WeeWX services and a number of WeeWX 
reports/skins that generate the output. If you want to change where the 
reports/skins create their output then yes that is what you need to do. 
Have a look at your [StdReport] stanza and the corresponding skins.

Gary

On Saturday, 19 September 2020 at 11:16:44 UTC+10 eastcentra...@gmail.com 
wrote:

> So, Im using weedwd to update my site for the Saratoga template.  Is this 
> still how I would do it?
>
> On Friday, September 18, 2020 at 8:54:59 PM UTC-4 gjr80 wrote:
>
>> You can change the location that WeeWX uses to save generated reports by 
>> setting the HTML_ROOT config option. HTML_ROOT is set in the [StdReport] 
>> stanza in weewx.conf, if you set HTML_ROOT immediately under [StdReport] 
>> the setting will apply to all reports but you can override HTML_ROOT for 
>> individual reports by setting HTML_ROOT under the report stanza, eg:
>>
>> [StdReport]
>> 
>> HTML_ROOT = public_html
>> 
>> [[MyReport]]
>> skin = MySkin
>>
>> [[MyOtherReport]]
>> skin = MyOtherSkin
>> HTML_ROOT = public_html/other_report
>>
>> Would place the content generated by MyReport in the public_html 
>> directory and content generated by MyOtherReport in the 
>> public_html/other_report directory.
>>
>> HTML_ROOT can be specified as an absolute path or as a relative path. If 
>> specified as a relative path the path is relative to the WEEWX_ROOT path 
>> specified in weewx.conf.
>>
>> If you are using the FTP or RSYNC report to upload to a web server you 
>> can also use one or more instances of the FTP or RSYNC report to locate 
>> your uploaded files on the web server as required. However, 
>> setting/overriding HTML_ROOT is all that is required in most cases.
>>
>> Gary
>> On Saturday, 19 September 2020 at 04:54:43 UTC+10 eastcentra...@gmail.com 
>> wrote:
>>
>>> Ok, now that its been working for a while weewxwd has been updating to 
>>> my website.  Its been updating to a WD folder but I want to change it where 
>>> it updates to "public_html" how do I do this?
>>>
>>> On Friday, August 21, 2020 at 8:51:26 PM UTC-4 Luke Marcum wrote:
>>>
 Yes it is!


 On Friday, August 21, 2020 at 12:52:55 AM UTC-4, rich T wrote:
>
> In the weewx.config file, is your FTP section setup?
>
> On Friday, August 21, 2020 at 12:35:51 AM UTC-4, Luke Marcum wrote:
>>
>> Its out on the internet and I used the Saratoga Template!
>>
>> On Friday, August 21, 2020 at 12:34:54 AM UTC-4, rich T wrote:
>>>
>>> Is it local (on local network) or  out on internet?
>>>
>>> On Friday, August 21, 2020 at 12:04:54 AM UTC-4, Luke Marcum wrote:

 Ok, now that Ive finished configuration, how to I get weewx-wd to 
 send the testtags file to my website?
  

>>>

-- 
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/6edb068e-d6aa-4ddb-96f9-5319c1e1c49fn%40googlegroups.com.

[weewx-user] Re: whew and gw1000

[Luke Marcum]

So, Im using weedwd to update my site for the Saratoga template.  Is this 
still how I would do it?

On Friday, September 18, 2020 at 8:54:59 PM UTC-4 gjr80 wrote:

> You can change the location that WeeWX uses to save generated reports by 
> setting the HTML_ROOT config option. HTML_ROOT is set in the [StdReport] 
> stanza in weewx.conf, if you set HTML_ROOT immediately under [StdReport] 
> the setting will apply to all reports but you can override HTML_ROOT for 
> individual reports by setting HTML_ROOT under the report stanza, eg:
>
> [StdReport]
> 
> HTML_ROOT = public_html
> 
> [[MyReport]]
> skin = MySkin
>
> [[MyOtherReport]]
> skin = MyOtherSkin
> HTML_ROOT = public_html/other_report
>
> Would place the content generated by MyReport in the public_html 
> directory and content generated by MyOtherReport in the 
> public_html/other_report directory.
>
> HTML_ROOT can be specified as an absolute path or as a relative path. If 
> specified as a relative path the path is relative to the WEEWX_ROOT path 
> specified in weewx.conf.
>
> If you are using the FTP or RSYNC report to upload to a web server you can 
> also use one or more instances of the FTP or RSYNC report to locate your 
> uploaded files on the web server as required. However, setting/overriding 
> HTML_ROOT is all that is required in most cases.
>
> Gary
> On Saturday, 19 September 2020 at 04:54:43 UTC+10 eastcentra...@gmail.com 
> wrote:
>
>> Ok, now that its been working for a while weewxwd has been updating to my 
>> website.  Its been updating to a WD folder but I want to change it where it 
>> updates to "public_html" how do I do this?
>>
>> On Friday, August 21, 2020 at 8:51:26 PM UTC-4 Luke Marcum wrote:
>>
>>> Yes it is!
>>>
>>>
>>> On Friday, August 21, 2020 at 12:52:55 AM UTC-4, rich T wrote:

 In the weewx.config file, is your FTP section setup?

 On Friday, August 21, 2020 at 12:35:51 AM UTC-4, Luke Marcum wrote:
>
> Its out on the internet and I used the Saratoga Template!
>
> On Friday, August 21, 2020 at 12:34:54 AM UTC-4, rich T wrote:
>>
>> Is it local (on local network) or  out on internet?
>>
>> On Friday, August 21, 2020 at 12:04:54 AM UTC-4, Luke Marcum wrote:
>>>
>>> Ok, now that Ive finished configuration, how to I get weewx-wd to 
>>> send the testtags file to my website?
>>>  
>>>
>>

-- 
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/ae2058cc-d28b-47d6-9efd-b70c55408f2en%40googlegroups.com.

[weewx-user] Re: whew and gw1000

[gjr80]

You can change the location that WeeWX uses to save generated reports by 
setting the HTML_ROOT config option. HTML_ROOT is set in the [StdReport] 
stanza in weewx.conf, if you set HTML_ROOT immediately under [StdReport] 
the setting will apply to all reports but you can override HTML_ROOT for 
individual reports by setting HTML_ROOT under the report stanza, eg:

[StdReport]

HTML_ROOT = public_html

[[MyReport]]
skin = MySkin

[[MyOtherReport]]
skin = MyOtherSkin
HTML_ROOT = public_html/other_report

Would place the content generated by MyReport in the public_html directory 
and content generated by MyOtherReport in the public_html/other_report 
directory.

HTML_ROOT can be specified as an absolute path or as a relative path. If 
specified as a relative path the path is relative to the WEEWX_ROOT path 
specified in weewx.conf.

If you are using the FTP or RSYNC report to upload to a web server you can 
also use one or more instances of the FTP or RSYNC report to locate your 
uploaded files on the web server as required. However, setting/overriding 
HTML_ROOT is all that is required in most cases.

Gary
On Saturday, 19 September 2020 at 04:54:43 UTC+10 eastcentra...@gmail.com 
wrote:

> Ok, now that its been working for a while weewxwd has been updating to my 
> website.  Its been updating to a WD folder but I want to change it where it 
> updates to "public_html" how do I do this?
>
> On Friday, August 21, 2020 at 8:51:26 PM UTC-4 Luke Marcum wrote:
>
>> Yes it is!
>>
>>
>> On Friday, August 21, 2020 at 12:52:55 AM UTC-4, rich T wrote:
>>>
>>> In the weewx.config file, is your FTP section setup?
>>>
>>> On Friday, August 21, 2020 at 12:35:51 AM UTC-4, Luke Marcum wrote:

 Its out on the internet and I used the Saratoga Template!

 On Friday, August 21, 2020 at 12:34:54 AM UTC-4, rich T wrote:
>
> Is it local (on local network) or  out on internet?
>
> On Friday, August 21, 2020 at 12:04:54 AM UTC-4, Luke Marcum wrote:
>>
>> Ok, now that Ive finished configuration, how to I get weewx-wd to 
>> send the testtags file to my website?
>>  
>>
>

-- 
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/71e611ea-1bac-4511-a92b-be33dcdf3c2bn%40googlegroups.com.

[weewx-user] Re: whew and gw1000

[Luke Marcum]

Ok, now that its been working for a while weewxwd has been updating to my 
website.  Its been updating to a WD folder but I want to change it where it 
updates to "public_html" how do I do this?

On Friday, August 21, 2020 at 8:51:26 PM UTC-4 Luke Marcum wrote:

> Yes it is!
>
>
> On Friday, August 21, 2020 at 12:52:55 AM UTC-4, rich T wrote:
>>
>> In the weewx.config file, is your FTP section setup?
>>
>> On Friday, August 21, 2020 at 12:35:51 AM UTC-4, Luke Marcum wrote:
>>>
>>> Its out on the internet and I used the Saratoga Template!
>>>
>>> On Friday, August 21, 2020 at 12:34:54 AM UTC-4, rich T wrote:

 Is it local (on local network) or  out on internet?

 On Friday, August 21, 2020 at 12:04:54 AM UTC-4, Luke Marcum wrote:
>
> Ok, now that Ive finished configuration, how to I get weewx-wd to send 
> the testtags file to my website?
>  
>


-- 
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/6e28e3e9-a269-4dbd-ab30-0f01c6eaceadn%40googlegroups.com.

[weewx-user] Re: Replacement for WMR200 ? --> Feedback on Froggit stations with Weewx please

[ian...@kinnon.org]

The Froggit is a clone of Ecowitt stuff I believe and its 
the weewx-interceptor in ecowitt mode
https://github.com/matthewwall/weewx-interceptor

I think there are a couple of threads in this forum about them

My Pi is a Pi 3 Model B so has Wifi built in, I use the wired interface for 
access to the pi itself and to run the weewx webserver on, but you can do 
it over just the wifi

using the WS View android app (I assume there is an apple version) you then 
configure the console to push data over wifi to the ip address of the pi

On Wednesday, 16 September 2020 at 14:13:43 UTC+1 axelle@gmail.com 
wrote:

> >I use the ecowitt client and sniff the wifi via my Pi, and it just works 
> with no issues
>
> Interesting, as I already use a RPi...
>
> What is the EcoWitt client ? (is that something you purchase and I missed, 
> or is something else?)
> How do you sniff the wifi on the Pi ?
>
> Thanks
> Axelle
>
>
> On Wednesday, September 16, 2020 at 12:58:50 PM UTC+2 ian...@kinnon.org 
> wrote:
>
>> I replaced my ageing Oregon Scientific with a  Froggit WH3000 SE   
>> I use the ecowitt client and sniff the wifi via my Pi, and it just works 
>> with no issues
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Tuesday, 15 September 2020 at 20:58:52 UTC+1 axelle@gmail.com 
>> wrote:
>>
>>> Can somebody provide some more feedback with connection of Froggit 
>>> weather stations to Weewx please ?
>>> How do you connect Froggit to Weewx ? USB cable ? Wifi ?
>>> Are weewx drivers ok?
>>>
>>> Also, I'm a bit lost in Froggit products. They seem to be an all-in-one 
>>> sensor box, but then how can you get indoor temperature?? You have to buy 
>>> additional sensors and connect them to the main console?
>>>
>>>
>>> (E.g WH4000SE WiFi Weather station)
>>>
>>> Thanks,
>>>
>>>
>>> On Thursday, August 20, 2020 at 4:17:46 PM UTC+2 galfert wrote:
>>>
 Ecowitt or Froggit stations.
 Just about any model from either of these with some minor exceptions... 
 with the Ecowitt GW1000 or the Froggit DP1500. These are the same 
 hardware. 
 The DP1500 is a GW1000.


 On Thursday, August 20, 2020 at 7:24:04 AM UTC-4, Invisible Man wrote:
>
>
> Hi,
> I've had a (Oregon Scientific) WMR200 weather station for years and 
> been very happy with it. Lately, I've been encountering several hardware 
> issues with it, and I fear it is perhaps going to be the end of it, soon 
> or 
> later.
> What replacement weather station would you recommend? I'm looking for 
> something below 500 euros, and of course supported by weewx. 
> 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/a75cb8bf-0f57-402b-a1ef-ca76308b47c8n%40googlegroups.com.

[weewx-user] Re: Acurite Atlas SDR Sensor Mapping and Pressure Readings

[Andy]

This  for pressure, some 
else here suggested it and it seems to work ok.

Battery:

inTempBatteryStatus = battery.152.FOWH25Packe
outTempBatteryStatus = battery.1:14.HidekiTS04Packet
windBatteryStatus = battery.0A66.Acurite5n1Packet

  [image: Screenshot_2020-09-18_06-04-42.png]

On Thursday, September 17, 2020 at 12:05:49 PM UTC-7 tarob...@gmail.com 
wrote:

> I'm not well versed on getting other pressure readings into weewx. I'm 
> sure there is a way but might be more work for just a temp situation.
>
> I think the distance packets should always show up, it would just show the 
> last storm distance in the packets. Although I have a standalone lightning 
> tower, not an atlas, so maybe the behavior is different. This site 
>  has some information on 
> that discussion.
>
> Assigning battery to outTempBatteryStatus should work but I haven't done 
> this. From my understanding, acurite signal for battery is either 1 or 0.
>
> On Thursday, September 17, 2020 at 1:51:19 PM UTC-4 wxwatching wrote:
>
>> I have ordered a pressure sensor, but delivery looks like it will take a 
>> month. Meanwhile, I thought I could just use my own console from my AcuRite 
>> 5-n-1 (Model 1036), but haven't figured out how to just use the pressure 
>> readings from it and combine with my Atlas readings.
>>
>> So, I assume the distance..AcuriteLightningPacket packets will not 
>> show in the SDR output until an actual storm is taking place?
>>
>> In reference to the battery, is that to mapped then as:
>>
>> outTempBatteryStatus = battery..0222.AcuriteAtlasPacket 
>>
>> On Thursday, September 17, 2020 at 8:58:53 AM UTC-4 tarob...@gmail.com 
>> wrote:
>>
>>> The lightning data is handled a bit differently and from searching the 
>>> user group I was able to get it working with the following sensor map:
>>>
>>> [[sensor_map]]
>>> ...
>>> lightning_distance = distance..AcuriteLightningPacket
>>> strikes_total = strikes_total..AcuriteLightningPacket
>>> [[deltas]]
>>> rain = rain_total
>>> lightning_strike_count = strikes_total
>>>
>>> and then in the calibration section in the weewx.conf file I added the 
>>> following:
>>>
>>> [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
>>> lightning_distance = lightning_distance if 
>>> lightning_strike_count > 0 else None
>>>
>>> More info here 
>>> 
>>>
>>> I haven't been able to determine how to capture signal strength from 
>>> Acurite via SDR. The battery status as I understand it is either "1" which 
>>> is good or "0" which is bad.
>>>
>>> Depending on your setup, there are a couple ways to get pressure. I am 
>>> using a raspberry pi 3 and added a pressure sensor to it using these 
>>> instructions 
>>> .
>>>
>>

-- 
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/2045f698-0d99-4b97-8f70-34c19f8c5250n%40googlegroups.com.

[weewx-user] Re: Migrating/Importing WD data in MySql DB to WeeWx MySql DB

[gjr80]

Andrew,

Can you try the attached wdimport.py in place of your current version. To 
install:

1. rename your current wdimport.py:

$ mv 
/usr/share/weewx/weeimport/wdimport.py 
/usr/share/weewx/weeimport/wdimport_orig.py

2. download the attached wdimport.py to /usr/share/weewx/weeimport/

3. run the import on the problem files again

This version of wdimport.py checks each log file line for null bytes and if 
found removes them before the line is parsed. Any such lines are listed on 
the console and saved to log but given the number of lines being imported 
they could be quite easy to miss in the log. The 82013 file had a lot of 
duplicate timestamps (which are listed to screen at the end of the import) 
so it is quite easy to miss the null byte line output to console as well.

Let us know how this goes and if successful I will include it in the next 
release.

Gary

On Thursday, 17 September 2020 20:20:12 UTC+10, gjr80 wrote:
>
> Apologies Andrew, I misread and thought you provided the data files for 
> use in improving wee_import WD imports rather than seeking help with the 
> import. Other things have taken up my time, I will try to have a look 
> Friday.
>
> Gary
>
> On Thursday, 17 September 2020 at 08:39:49 UTC+10 Andrew M wrote:
>
>> Bumping this post to see if anyone has any suggestions on my the attached 
>> is failing import.
>>
>> Thank you in advance.
>>
>>
>>
>> On Wednesday, September 9, 2020 at 11:02:01 PM UTC-4, Andrew M wrote:
>>>
>>>
>>> I do appreciate the assistance. Hopefully this will help others in 
>>> either with what I am doing or identifying a problem with the import 
>>> process.
>>>
>>> I have attached a copy of one Weather Display log file I am having 
>>> issues with (82013lg.txt.zip) as well as one I did not have any issues with 
>>> (52013lg.txt.zip).
>>> Also attached is output from wee_debug
>>>
>>> I am not seeing any differences in the data between these files that is 
>>> causing 82013lg.txt to choke.
>>>
>>> ~20 files out of ~400 files had an issue.
>>>
>>> Please let me know if any additional information is needed.
>>>
>>>
>>>
>>> From running wee_import on 82013lg.txt
>>> pi@weather:/var/tmp $ wee_import --import-config=/var/tmp/wd.conf 
>>> --dry-run --verbose
>>> Using WeeWX configuration file /etc/weewx/weewx.conf
>>> Starting wee_import...
>>> Weather Display monthly log files in the '/var/tmp/WD' directory will be 
>>> imported
>>> The following options will be used:
>>>  config=/etc/weewx/weewx.conf, import-config=/var/tmp/wd.conf
>>>  from=None, to=None
>>>  dry-run=True, calc_missing=False, ignore_invalid_data=True
>>>  monthly logs are in US units
>>>  tranche=300, interval=60
>>>  UV=True, radiation=True ignore extreme temperature and humidity=True
>>> Using database binding 'wx_binding', which is bound to database 
>>> 'roundhillvaw_archive'
>>> Destination table 'archive' unit system is '0x01' (US).
>>> This is a dry run, imported data will not be saved to archive.
>>> Starting dry run import ...
>>> Records covering multiple periods have been identified for import.
>>> Obtaining raw import data for period 1 ...
>>> Traceback (most recent call last):
>>>   File "/usr/share/weewx/wee_import", line 900, in 
>>> main()
>>>   File "/usr/share/weewx/wee_import", line 830, in main
>>> source_obj.run()
>>>   File "/usr/share/weewx/weeimport/weeimport.py", line 368, in run
>>> _raw_data = self.getRawData(period)
>>>   File "/usr/share/weewx/weeimport/wdimport.py", line 568, in getRawData
>>> for rec in _reader:
>>>   File "/usr/lib/python3.7/csv.py", line 112, in __next__
>>> row = next(self.reader)
>>> _csv.Error: line contains NULL byte
>>>
>>>
>>>
>>> From log file
>>> pi@weather:~ $ sudo tail -f /var/log/weewx.log
>>> Sep  9 22:39:01 weather wee_import[16538] DEBUG weeimport.wdimport: The 
>>> following options will be used:
>>> Sep  9 22:39:01 weather wee_import[16538] DEBUG weeimport.wdimport:  
>>> config=/etc/weewx/weewx.conf, import-config=/var/tmp/wd.conf
>>> Sep  9 22:39:01 weather wee_import[16538] DEBUG weeimport.wdimport:  
>>> from=None, to=None
>>> Sep  9 22:39:01 weather wee_import[16538] DEBUG weeimport.wdimport:  
>>> dry-run=True, calc_missing=False, ignore_invalid_data=True
>>> Sep  9 22:39:01 weather wee_import[16538] DEBUG weeimport.wdimport:  
>>> monthly logs are in US units
>>> Sep  9 22:39:01 weather wee_import[16538] DEBUG weeimport.wdimport:  
>>> tranche=300, interval=60
>>> Sep  9 22:39:01 weather wee_import[16538] DEBUG weeimport.wdimport:  
>>> UV=True, radiation=True ignore extreme temperature and humidity=True
>>> Sep  9 22:39:01 weather wee_import[16538] INFO weeimport.wdimport: Using 
>>> database binding 'wx_binding', which is bound to database 
>>> 'roundhillvaw_archive'
>>> Sep  9 22:39:01 weather wee_import[16538] INFO weeimport.wdimport: 
>>> Destination table 'archive' unit system is '0x01' (US).
>>> Sep  9 22:39:01 weather wee_import[16538] INFO weeim