from:"Bill"

Google Groups does NOT like a file names syslog. Perhaps syslog.txt will 
get through.

On Tuesday, August 4, 2020 at 2:24:23 PM UTC-5 Bill Arthur wrote:

> Gary,
> I'll grab and post the info this evening. 
> It looks like this happens only when booting, as if weewx starts before 
> the WiFi has stabilized. 
>
> On Tuesday, August 4, 2020 at 3:30:09 AM UTC-5 gjr80 wrote:
>
>> Bill,
>>
>> For some reason the driver was unable to communicate with (one of) your 
>> GW1000(s). Before you get the log could you set debug = 3 in weewx.conf, 
>> restart WeeWX then post the log from startup through until the error. Would 
>> also help if you could post your [GW1000] stanza from WeeWX.conf.
>>
>> Gary
>>
>

-- 
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/5e7aaf86-ebc7-47b1-9bf1-95c92aeeb088n%40googlegroups.com.

Aug  4 22:29:24 OpiQ-12 fake-hwclock[69]: Wed 05 Aug 2020 03:29:09 AM UTC
Aug  4 22:29:24 OpiQ-12 systemd-fsck[93]: e2fsck 1.44.5 (15-Dec-2018)
Aug  4 22:29:24 OpiQ-12 systemd-fsck[93]: rootfs: clean, 45622/1899328 files, 
450859/7725184 blocks
Aug  4 22:29:24 OpiQ-12 systemd[1]: Started File System Check on Root Device.
Aug  4 22:29:24 OpiQ-12 systemd[1]: Starting Remount Root and Kernel File 
Systems...
Aug  4 22:29:24 OpiQ-12 systemd[1]: Started udev Coldplug all Devices.
Aug  4 22:29:24 OpiQ-12 systemd[1]: Starting Helper to synchronize boot up for 
ifupdown...
Aug  4 22:29:24 OpiQ-12 systemd[1]: Started Helper to synchronize boot up for 
ifupdown.
Aug  4 22:29:24 OpiQ-12 systemd[1]: Started Remount Root and Kernel File 
Systems.
Aug  4 22:29:24 OpiQ-12 systemd[1]: Starting Create System Users...
Aug  4 22:29:24 OpiQ-12 systemd[1]: Starting Load/Save Random Seed...
Aug  4 22:29:24 OpiQ-12 systemd[1]: Condition check resulted in Rebuild 
Hardware Database being skipped.
Aug  4 22:29:24 OpiQ-12 systemd[1]: Starting Flush Journal to Persistent 
Storage...
Aug  4 22:29:24 OpiQ-12 systemd[1]: Started Set the console keyboard layout.
Aug  4 22:29:24 OpiQ-12 systemd[1]: Started Create System Users.
Aug  4 22:29:24 OpiQ-12 systemd[1]: Started Load/Save Random Seed.
Aug  4 22:29:24 OpiQ-12 systemd[1]: Starting Create Static Device Nodes in 
/dev...
Aug  4 22:29:24 OpiQ-12 systemd[1]: Started Flush Journal to Persistent Storage.
Aug  4 22:29:24 OpiQ-12 systemd[1]: Started Create Static Device Nodes in /dev.
Aug  4 22:29:24 OpiQ-12 systemd[1]: Reached target Local File Systems (Pre).
Aug  4 22:29:24 OpiQ-12 systemd[1]: Starting udev Kernel Device Manager...
Aug  4 22:29:24 OpiQ-12 systemd[1]: Started udev Kernel Device Manager.
Aug  4 22:29:24 OpiQ-12 systemd[1]: Found device /dev/serial1.
Aug  4 22:29:24 OpiQ-12 systemd[1]: Found device 
/dev/disk/by-partuuid/c595048a-01.
Aug  4 22:29:24 OpiQ-12 systemd[1]: Starting File System Check on 
/dev/disk/by-partuuid/c595048a-01...
Aug  4 22:29:24 OpiQ-12 systemd[1]: Condition check resulted in Huge Pages File 
System being skipped.
Aug  4 22:29:24 OpiQ-12 systemd[1]: Condition check resulted in FUSE Control 
File System being skipped.
Aug  4 22:29:24 OpiQ-12 systemd[1]: Condition check resulted in Set Up 
Additional Binary Formats being skipped.
Aug  4 22:29:24 OpiQ-12 systemd[1]: Condition check resulted in Rebuild 
Hardware Database being skipped.
Aug  4 22:29:24 OpiQ-12 kernel: [0.00] Booting Linux on physical CPU 0x0
Aug  4 22:29:24 OpiQ-12 kernel: [0.00] Linux version 5.4.51+ 
(dom@buildbot) (gcc version 4.9.3 (crosstool-NG 
crosstool-ng-1.22.0-88-g8460611)) #1327 Thu Jul 23 10:53:06 BST 2020
Aug  4 22:29:24 OpiQ-12 kernel: [0.00] CPU: ARMv6-compatible processor 
[410fb767] revision 7 (ARMv7), cr=00c5387d
Aug  4 22:29:24 OpiQ-12 kernel: [0.00] CPU: PIPT / VIPT nonaliasing 
data cache, VIPT nonaliasing instruction cache
Aug  4 22:29:24 OpiQ-12 kernel: [0.00] OF: fdt: Machine model: 
Raspberry Pi Zero W Rev 1.1
Aug  4 22:29:24 OpiQ-12 kernel: [0.00] Memory policy: Data cache 
writeback
Aug  4 22:29:24 OpiQ-12 kernel: [0.00] Reserved memory: created CMA 
memory pool at 0x17c0, size 64 MiB
Aug  4 22:29:24 OpiQ-12 kernel: [0.00] OF: reserved mem: initialized 
node linux,cma, compatible id shared-dma-pool
Aug  4 22:29:24 OpiQ-12 kernel: [0.00] On node 0 totalpages: 114688
Aug  4 22:29:24 OpiQ-12 kernel: [0.00]   Normal zone: 896 pages used 
for memmap
Aug  4 22:29:24 OpiQ-12 kernel: [0.00]   Normal zone: 0 pages reserved
Aug  4 22:29:24 OpiQ-12 kernel: [0.00]   Normal zone: 114688 pages, 
LIFO batch:31
Aug  4 22:29:24 OpiQ-12 kernel: [0.00] pcpu-alloc: s0 r0 d32768 u32768 
alloc=1*32768
Aug  4 22:29:24 OpiQ-12 kernel:

Re: [weewx-user] Re: New GW1000 Driver available for testing

Gary,
Here's the log and stanza. As I suspected, wlan0 was not stable until after 
WeeWx exited.
Perhaps this is specific to the Pi Zero W.

-- 
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/3f235da3-a20a-4f10-9392-57e9fe44694en%40googlegroups.com.
[GW1000]
driver = user.gw1000

poll_interval = 32  
ip_address = 192.168.0.104  

port = 45000  

At the time of the test which is recorded in the syslog, I had commented out 
the IP address.

Re: [weewx-user] Re: New GW1000 Driver available for testing

Gary,
I'll grab and post the info this evening. 
It looks like this happens only when booting, as if weewx starts before the 
WiFi has stabilized. 

On Tuesday, August 4, 2020 at 3:30:09 AM UTC-5 gjr80 wrote:

> Bill,
>
> For some reason the driver was unable to communicate with (one of) your 
> GW1000(s). Before you get the log could you set debug = 3 in weewx.conf, 
> restart WeeWX then post the log from startup through until the error. Would 
> also help if you could post your [GW1000] stanza from WeeWX.conf.
>
> Gary
>

-- 
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/7ff02b43-ffe2-4e1e-b44b-827cf2daf5d1n%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

I hope I'm not making rookie mistakes, but I get the following when doing a 
fresh install on a Pi-zero. Nothing else is added, just weewx and the 
GW-1000 driver. I'll pull all the required logs tomorrow, but here is what 
I'm seeing on a reboot:

Aug  4 02:00:48 OpiQ-12 dhcpcd[261]: wlan0: soliciting an IPv6 router
Aug  4 02:00:48 OpiQ-12 weewx[367] INFO weewx.engine: Loading station type 
GW1000 (user.gw1000)
Aug  4 02:00:48 OpiQ-12 weewx[367] ERROR gw1000: user.gw1000: Failed to 
send command 'CMD_READ_' after 3 attempts
Aug  4 02:00:48 OpiQ-12 weewx[367] ERROR weewx.engine: Import of driver 
failed: 'NoneType' object has no attribute '__getitem__' ()
Aug  4 02:00:48 OpiQ-12 weewx[367] CRITICAL weewx.engine:   
Traceback (most recent call last):
Aug  4 02:00:48 OpiQ-12 weewx[367] CRITICAL weewx.engine: File 
"/usr/share/weewx/weewx/engine.py", line 103, in setupStation
Aug  4 02:00:48 OpiQ-12 weewx[367] CRITICAL weewx.engine:   
self.console = loader_function(config_dict, self)
Aug  4 02:00:48 OpiQ-12 weewx[367] CRITICAL weewx.engine: File 
"/usr/share/weewx/user/gw1000.py", line 1021, in loader
Aug  4 02:00:48 OpiQ-12 weewx[367] CRITICAL weewx.engine:   
return Gw1000Driver(**config_dict[DRIVER_NAME])
Aug  4 02:00:48 OpiQ-12 weewx[367] CRITICAL weewx.engine: File 
"/usr/share/weewx/user/gw1000.py", line 1271, in __init__
Aug  4 02:00:48 OpiQ-12 weewx[367] CRITICAL weewx.engine:   
super(Gw1000Driver, self).__init__(**stn_dict)
Aug  4 02:00:48 OpiQ-12 weewx[367] CRITICAL weewx.engine: File 
"/usr/share/weewx/user/gw1000.py", line 728, in __init__
Aug  4 02:00:48 OpiQ-12 weewx[367] CRITICAL weewx.engine:   
use_th32=use_th32)
Aug  4 02:00:48 OpiQ-12 weewx[367] CRITICAL weewx.engine: File 
"/usr/share/weewx/user/gw1000.py", line 1463, in __init__
Aug  4 02:00:48 OpiQ-12 weewx[367] CRITICAL weewx.engine:   
is_wh24 = six.indexbytes(_sys_params, 5) == 0
Aug  4 02:00:48 OpiQ-12 weewx[367] CRITICAL weewx.engine: File 
"/usr/share/weewx/six.py", line 661, in indexbytes
Aug  4 02:00:48 OpiQ-12 weewx[367] CRITICAL weewx.engine:   
return ord(buf[i])
Aug  4 02:00:48 OpiQ-12 weewx[367] CRITICAL weewx.engine:   
TypeError: 'NoneType' object has no attribute '__getitem__'
Aug  4 02:00:48 OpiQ-12 weewx[367] CRITICAL __main__: Unable to load 
driver: 'NoneType' object has no attribute '__getitem__'
Aug  4 02:00:48 OpiQ-12 weewx[367] CRITICAL __main__:   Exiting...


On Monday, August 3, 2020 at 10:25:47 PM UTC-5 gjr80 wrote:

> On Tuesday, 4 August 2020 07:44:37 UTC+10, Paul Anderson wrote:
>>
>> So I guess I'm a perdoid control freak
>>
>
> I hope that is not too painful :)
>
> The other point of concern is over blindly pasting the full  [Accumulator] 
>> stanza into weewx.conf when running as a service. Feel it's really easy for 
>> someone not to realize the unattended consequences caused by the fact that 
>> this will affect the Accumulator type for fields generated by the normal 
>> driver and other services in use in addition to the GW1000 service.
>>
>
> Just to be clear let's work through this when using the GW1000 driver as a 
> service. Every field accumulated by the accumulator has a default extractor 
> of 'avg' (which gives the average of all loop values seen in the archive 
> period to date). If the field concerned is populated and is being mapped 
> through from the GW1000 to WeeWX under the default field map then all is 
> good, the appropriate extractor is being/will be used. If the field is 
> populated by the (non-GW1000) driver or some other service and if that 
> field was relying on the default extractor, then the GW1000 installer would 
> clobber that default extractor. If the other field had an explicit 
> extractor in weewx.conf then wee_extension would respect that existing 
> setting and it would not be clobbered. If the user defines a field map 
> using [[field_map]] or alters the default field map with 
> [[field_map_extensions]] then wee_extension will not know about these 
> changes and potentially the newly mapped field will have the wrong 
> extractor. So there are a couple of corner cases that could cause issues, 
> though the latter case is just as much of an issue when using the GW1000 
> driver as a driver as it is when using it as a service.
>
> One thing to remember, the existence of an extractor entry for a field 
> that does not exist has no affect on the operation of WeeWX other than 
> taking up a few more bytes of memory/disk space.
>
> I'll put this down as an issue to look at later, for now I think it can be 
> handled with a note or two in the install instructions. In fact that may be 
> the final solution, the extension installer is only capable of so much. I 
> am hesitant to fully remove populating the extractors, I suspect doing that 
> and the follow on need for users to manually the extractors

Re: [weewx-user] Re: New GW1000 Driver available for testing

2020-08-01 Thread Bill Arthur

Hi Gary,
I believe I found my problem. Sorry to have caused any confusion.
After I ran wee_install I saw the GW1000 stanzas at the end of weewx.conf 
and I falsely assumed it was configured.
I had a ton of problems because I didn't run wee_config.

On Saturday, August 1, 2020 at 12:41:19 AM UTC-5 Bill Arthur wrote:

> Hi Gary,
> I wasn't able to make time to get the logs tonight. I'll try again 
> tomorrow.
> But I did test running the driver directly. I have three GW-1000s, 
> 192.168.0.104, 204 and 205.
> Out of ten runs it chooses 204 four times, 205 four times and 104 two 
> times.
>
> # Options for extension 'GW1000'  
>   
> [Accumulator]  
>  
> [[lightning_strike_count]]
>   
> extractor = sum
>   
> [[lightning_last_det_time]]
>  
> extractor = last  
> 
> 
>   
> ##
>   
> 
> 
> 
> # Options for extension 'GW1000'  
>  
>  [GW1000]  
>  
>  driver = user.gw1000  
>   
> ip_address = 192.168.0.104
> 
> 
>   
> 
>
> On Friday, July 31, 2020 at 4:21:43 PM UTC-5 gjr80 wrote:
>
>> Bill,
>>
>> Does this occur every time or occasionally? Could you post your [GW1000] 
>> stanza, the output from my previous post should contain everything else I 
>> need to troubleshoot this issue.
>>
>> Gary
>>
>

-- 
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/465c1476-163a-4c83-8328-11edd280bedfn%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

2020-07-31 Thread Bill Arthur

Hi Gary,
I wasn't able to make time to get the logs tonight. I'll try again tomorrow.
But I did test running the driver directly. I have three GW-1000s, 
192.168.0.104, 204 and 205.
Out of ten runs it chooses 204 four times, 205 four times and 104 two times.

# Options for extension 'GW1000'

[Accumulator]  
 
[[lightning_strike_count]]  

extractor = sum
  
[[lightning_last_det_time]]
 
extractor = last



##  



# Options for extension 'GW1000'
   
 [GW1000]  
 
 driver = user.gw1000  
  
ip_address = 192.168.0.104  





On Friday, July 31, 2020 at 4:21:43 PM UTC-5 gjr80 wrote:

> Bill,
>
> Does this occur every time or occasionally? Could you post your [GW1000] 
> stanza, the output from my previous post should contain everything else I 
> need to troubleshoot this issue.
>
> Gary
>

-- 
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/47a025f1-210c-4f21-ace1-c90b3f9cee42n%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

2020-07-31 Thread Bill Arthur

One other thing I noticed
Even though I had set the ip_address in weewx.conf it chose to use a 
different one.
This will be hard to troubleshoot unless you have several GW-1000s to work 
with.

On Friday, July 31, 2020 at 2:53:30 PM UTC-5 Bill Arthur wrote:

> The first time I set this up (on a fresh install) I had low barometer and 
> two digit wind direction. Wednesday I did a fresh install (on a Pi Zero) 
> and the barometer and wind direction were OK but the outside temp was about 
> 30 degrees low.
> I'm going to try another fresh install tonight.
>
>
> On Friday, July 31, 2020 at 3:54:51 AM UTC-5 gjr80 wrote:
>
>> I have released v0.1.0b9 on Github 
>> <https://github.com/gjr80/weewx-gw1000/releases>. The main change is the 
>> (I hope) final resolution of the pressures issue. In short, the GW1000 
>> Absolute Pressure is now mapped to WeeWX field pressure with WeeWX to 
>> calculate barometer and altimeter via StdWXCalculate. GW1000 Relative 
>> Pressure will be passed through to WeeWX as field relbarometer for those 
>> that may wish to access it. The default behaviour can be changed by 
>> suitable field map entries in weewx.conf.
>>
>> b9 includes requires no changes to weewx.conf; however, upgrading to b9 
>> by downloading the b9 extension package and installing with the 
>> wee_extension utility is the preferred means of installing/upgrading to 
>> b9.
>>
>> Gary
>>
>

-- 
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/3f32f9c6-cfe8-46d2-89c5-1904589190a7n%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

2020-07-31 Thread Bill Arthur

The first time I set this up (on a fresh install) I had low barometer and 
two digit wind direction. Wednesday I did a fresh install (on a Pi Zero) 
and the barometer and wind direction were OK but the outside temp was about 
30 degrees low.
I'm going to try another fresh install tonight.


On Friday, July 31, 2020 at 3:54:51 AM UTC-5 gjr80 wrote:

> I have released v0.1.0b9 on Github 
> . The main change is the 
> (I hope) final resolution of the pressures issue. In short, the GW1000 
> Absolute Pressure is now mapped to WeeWX field pressure with WeeWX to 
> calculate barometer and altimeter via StdWXCalculate. GW1000 Relative 
> Pressure will be passed through to WeeWX as field relbarometer for those 
> that may wish to access it. The default behaviour can be changed by 
> suitable field map entries in weewx.conf.
>
> b9 includes requires no changes to weewx.conf; however, upgrading to b9 
> by downloading the b9 extension package and installing with the 
> wee_extension utility is the preferred means of installing/upgrading to 
> b9.
>
> Gary
>

-- 
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/0bb6a6ad-85b4-4d0b-abd2-183c30a9c34an%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

2020-07-27 Thread Bill Arthur

Thanks Gary.  
Your instructions worked perfectly.

I'm still seeing a couple of things. Here are links to two reporting 
stations. They both receive data from the same GW-1000
The -1 station uses the old push method. The -5 station uses the new API 
method.  I'm seeing differences in wind direction and barometer
-1 Station 
-5 Station 
On Monday, July 27, 2020 at 12:58:20 AM UTC-5 gjr80 wrote:

> I have released v0.1.0b6 on Github 
> . A summary of the 
> significant changes can be found against the v0.1.0b6 release on Github. It 
> has not (fully) addressed the issue of some battery states not making their 
> way through to the loop packets, unfortunately that is still a  work in 
> progress.
>
> Those that have already installed the driver can download and install 
> v0.1.0b6 using the following commands depending on your WeeWX install type:
>
> for setup.py installs:
>
> $ sudo mv /home/weewx/bin/user/gw1000.py /home/weewx/bin/user/gw1000_orig.
> py
> $ sudo wget -P /home/weewx/bin/user https://
> raw.githubusercontent.com/gjr80/weewx-gw1000/v0.1.0b6/bin/user/gw1000.py
>
> for package installs:
>
> $ sudo mv /usr/share/weewx/user/gw1000.py /usr/share/weewx/user/
> gw1000_orig.py
> $ sudo wget -P /usr/share/weewx/user https://
> raw.githubusercontent.com/gjr80/weewx-gw1000/v0.1.0b6/bin/user/gw1000.py
>
> There has been no change to the [GW1000] structure so you can just 
> restart WeeWX/run v0.1.0b6 directly without further changes.
>
> Gary
>
>
>

-- 
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/871c9da9-3218-4bcf-9b14-321678e4e8f0n%40googlegroups.com.

[weewx-user] Re: Chrome stopped refreshing the page at localhost

2020-07-24 Thread Bill Roberts



On Friday, July 24, 2020 at 1:50:03 PM UTC-7, Bill Roberts wrote:
>
> It works correctly updating wunderground every 5 minutes 
> at https://www.wunderground.com/dashboard/pws/KAZTUCSO1729
>

-- 
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/bbd9def5-226e-4de3-80a5-8d0ffe0068a3o%40googlegroups.com.

[weewx-user] Chrome stopped refreshing the page at localhost

2020-07-24 Thread Bill Roberts

I use weewx to observe the data from my accurite 5-in-1 wx station.
I use the belchertown skin as well.
It was performing well an the webpage at localdata automatically refreshed 
every 5 minutes.
A couple of days ago, it stopped refreshing automatically, will manually 
refresh if I click the Chrome refresh.
Log attached

-- 
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/440330e6-3347-42cf-9980-6033af48c923o%40googlegroups.com.


mylog
Description: Binary data

Re: [weewx-user] Re: New GW1000 Driver available for testing

I started as you and later added a WiFi-less console.  I'm not sure where 
to look for the WH65 designation. 
No, I didn't change the map. I was unable to run the driver directly to 
test, so I just launched it blindly... and it worked.
I am seeing an anomaly with pressure, too. I'm looking at the output as 
reported to CWOP. I'm seeing 989mb where I expect 1019mb
So...I have some work to do.
On Friday, July 24, 2020 at 1:28:27 PM UTC-5 steep...@gmail.com wrote:

> That is the same array that I am using with gw1000 except I do not have a 
> console. Does this show up as WH65? I have anomaly with the barometer but I 
> cannot understand why. Have you changed the sensor map at all?
>
>
> On Fri, 24 Jul 2020 at 19:17, Bill Arthur  wrote:
>
>> Hi Ian,
>> I have the Ambient Weather WS-2902 array:  temperature, rainfall, 
>> humidity, wind speed & direction, UV and solar.  Indoor and pressure is 
>> from the GW-1000
>>
>> On Friday, July 24, 2020 at 1:07:41 PM UTC-5 steep...@gmail.com wrote:
>>
>>> Hi Bill,
>>> What sensors do you have connected?
>>>
>>> On Fri, 24 Jul 2020 at 19:06, Bill Arthur  wrote:
>>>
>>>> Ian,
>>>> Yes, just the simple Seasons skin for now. I now have 12 hours of data 
>>>> and it's looking good. 
>>>> I've compared it to my weather station console and the data all looks 
>>>> correct.
>>>>
>>>> On Friday, July 24, 2020 at 12:56:01 PM UTC-5 steep...@gmail.com wrote:
>>>>
>>>>> Hi Bill,
>>>>> No need to be sorry. Just wanted to exchange notes on experiences. I 
>>>>> assume you then using the default Seasons skin. How is that looking?
>>>>> Ian
>>>>>
>>>>> On Fri, 24 Jul 2020 at 18:12, Bill Arthur  wrote:
>>>>>
>>>>>> Hi Ian
>>>>>> No, I don't have Weather34 on the RasPi that I'm testing the GW1000 
>>>>>> extension, it's a fresh install.
>>>>>> It'll be a while until I'm ready to modify the RasPi that has 
>>>>>> Weather34. Sorry.
>>>>>>
>>>>>> On Friday, July 24, 2020 at 10:09:08 AM UTC-5 steep...@gmail.com 
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Bill,
>>>>>>>
>>>>>>> Are you still using the Weather34 skin. If so, I am interested what 
>>>>>>> barometer reading you are displaying when using the gw1000 driver.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Ian 
>>>>>>>
>>>>>>>
>>>>>>> On Friday, July 24, 2020 at 4:02:17 AM UTC+1, Bill Arthur wrote:
>>>>>>>>
>>>>>>>> I couldn't get it to run from the command line.
>>>>>>>> When I  did   python -m user.gw1000 --help
>>>>>>>> I get   /usr/bin/python: No module named user.gw1000
>>>>>>>>
>>>>>>>> But I have it up and running, everything looks good on my Seasons 
>>>>>>>> page.
>>>>>>>> I'll give the data a closer look tomorrow.
>>>>>>>>
>>>>>>>> But I'm scratching my head trying to find how to specify the IP 
>>>>>>>> address in weewx.conf
>>>>>>>> I have three GW1000s here, I have no idea which one is being used  
>>>>>>>> On Thursday, July 23, 2020 at 9:06:47 PM UTC-5 Bill Arthur wrote:
>>>>>>>>
>>>>>>>>> This link works: 
>>>>>>>>> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/gw1000-0.1.0b4.tar.gz
>>>>>>>>>
>>>>>>>>> On Thursday, July 23, 2020 at 8:57:49 PM UTC-5 Bill Arthur wrote:
>>>>>>>>>
>>>>>>>>>> FYI:
>>>>>>>>>> wget -P /var/tmp 
>>>>>>>>>> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/weewx-gw1000-0.1.0b4.tar.gz
>>>>>>>>>>  
>>>>>>>>>> gives me an Error 404 
>>>>>>>>>>
>>>>>>>>>> On Thursday, July 23, 2020 at 3:22:07 PM UTC-5 galfert wrote:
>>>>>>>>>>
>>>>>>>>>>> There is a thread in the developer section where some questions 
>>>>>>>>>>> were asked that were no

Re: [weewx-user] Re: New GW1000 Driver available for testing

Hi Ian,
I have the Ambient Weather WS-2902 array:  temperature, rainfall, humidity, 
wind speed & direction, UV and solar.  Indoor and pressure is from the 
GW-1000

On Friday, July 24, 2020 at 1:07:41 PM UTC-5 steep...@gmail.com wrote:

> Hi Bill,
> What sensors do you have connected?
>
> On Fri, 24 Jul 2020 at 19:06, Bill Arthur  wrote:
>
>> Ian,
>> Yes, just the simple Seasons skin for now. I now have 12 hours of data 
>> and it's looking good. 
>> I've compared it to my weather station console and the data all looks 
>> correct.
>>
>> On Friday, July 24, 2020 at 12:56:01 PM UTC-5 steep...@gmail.com wrote:
>>
>>> Hi Bill,
>>> No need to be sorry. Just wanted to exchange notes on experiences. I 
>>> assume you then using the default Seasons skin. How is that looking?
>>> Ian
>>>
>>> On Fri, 24 Jul 2020 at 18:12, Bill Arthur  wrote:
>>>
>>>> Hi Ian
>>>> No, I don't have Weather34 on the RasPi that I'm testing the GW1000 
>>>> extension, it's a fresh install.
>>>> It'll be a while until I'm ready to modify the RasPi that has 
>>>> Weather34. Sorry.
>>>>
>>>> On Friday, July 24, 2020 at 10:09:08 AM UTC-5 steep...@gmail.com wrote:
>>>>
>>>>> Hi Bill,
>>>>>
>>>>> Are you still using the Weather34 skin. If so, I am interested what 
>>>>> barometer reading you are displaying when using the gw1000 driver.
>>>>>
>>>>> Thanks,
>>>>> Ian 
>>>>>
>>>>>
>>>>> On Friday, July 24, 2020 at 4:02:17 AM UTC+1, Bill Arthur wrote:
>>>>>>
>>>>>> I couldn't get it to run from the command line.
>>>>>> When I  did   python -m user.gw1000 --help
>>>>>> I get   /usr/bin/python: No module named user.gw1000
>>>>>>
>>>>>> But I have it up and running, everything looks good on my Seasons 
>>>>>> page.
>>>>>> I'll give the data a closer look tomorrow.
>>>>>>
>>>>>> But I'm scratching my head trying to find how to specify the IP 
>>>>>> address in weewx.conf
>>>>>> I have three GW1000s here, I have no idea which one is being used  
>>>>>> On Thursday, July 23, 2020 at 9:06:47 PM UTC-5 Bill Arthur wrote:
>>>>>>
>>>>>>> This link works: 
>>>>>>> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/gw1000-0.1.0b4.tar.gz
>>>>>>>
>>>>>>> On Thursday, July 23, 2020 at 8:57:49 PM UTC-5 Bill Arthur wrote:
>>>>>>>
>>>>>>>> FYI:
>>>>>>>> wget -P /var/tmp 
>>>>>>>> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/weewx-gw1000-0.1.0b4.tar.gz
>>>>>>>>  
>>>>>>>> gives me an Error 404 
>>>>>>>>
>>>>>>>> On Thursday, July 23, 2020 at 3:22:07 PM UTC-5 galfert wrote:
>>>>>>>>
>>>>>>>>> There is a thread in the developer section where some questions 
>>>>>>>>> were asked that were not directly related to development. This thread 
>>>>>>>>> is 
>>>>>>>>> good. I'm just inviting people to ask their questions here in this 
>>>>>>>>> thread 
>>>>>>>>> rather than in the developer section.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thursday, July 23, 2020 at 2:56:51 PM UTC-4, steeple ian wrote:
>>>>>>>>>
>>>>>>>>>> ???
>>>>>>>>>>
>>>>>>>>>> On Thu, 23 Jul 2020 at 19:39, galfert  wrote:
>>>>>>>>>>
>>>>>>>>> For anyone discussing this new GW1000 API driver in the WeeWX 
>>>>>>>>>>> development section STOP. Use this user section instead to discuss 
>>>>>>>>>>> its use.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> -- 
>>>>>>>>>>> You received this message because you are subscribed to the 
>>>>>>>>>>> Google Groups "weewx-user" group.
>>>>>>>>>>>
>>>&

Re: [weewx-user] Re: New GW1000 Driver available for testing

Gary,
No need for apologies. I'm glad that I was able to spot these things. And 
in a small way, I feel like I'm helping improve it for everyone. 

On Friday, July 24, 2020 at 8:44:57 AM UTC-5 gjr80 wrote:

> My apologies all round Bill, a few typos and a wrong assumption about 
> package installs - have rewritten and simplfied the GitHub readmes this 
> afternoon. They should be correct now. Perhaps a bit late now but to run 
> the driver directly the following should work:
>
> $ PYTHONPATH=/usr/share/weewx python -m user.gw1000 --help
>
> When you used wee_config --reconfigure to reconfigure WeeWX to use the 
> driver it should have prompted you for the IP address, unfortunately I 
> included --no-prompt in the wee_config command and that left you with no 
> IP address set (in which case the driver uses the first GW1000 that 
> replies). You can run the following command and step through the prompts 
> until you are asked for an IP address and then enter the IP address of the 
> GW1000 you wish to use:
>
> $ wee_config --reconfigure --driver=user.gw1000
>
> Alternatively you can just edit weewx.conf and add a line ip_address 
> under [GW1000]:
>
> [GW1000]
> 
> ip_address = 1.2.3.4
>
> Either way you will need to restart once you have set the IP address.
>
> Gary
>
> On Friday, 24 July 2020 13:02:17 UTC+10, Bill Arthur wrote:
>>
>> I couldn't get it to run from the command line.
>> When I  did   python -m user.gw1000 --help
>> I get   /usr/bin/python: No module named user.gw1000
>>
>> But I have it up and running, everything looks good on my Seasons page.
>> I'll give the data a closer look tomorrow.
>>
>> But I'm scratching my head trying to find how to specify the IP address 
>> in weewx.conf
>> I have three GW1000s here, I have no idea which one is being used  
>> On Thursday, July 23, 2020 at 9:06:47 PM UTC-5 Bill Arthur wrote:
>>
>>> This link works: 
>>> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/gw1000-0.1.0b4.tar.gz
>>>
>>> On Thursday, July 23, 2020 at 8:57:49 PM UTC-5 Bill Arthur wrote:
>>>
>>>> FYI:
>>>> wget -P /var/tmp 
>>>> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/weewx-gw1000-0.1.0b4.tar.gz
>>>>  
>>>> gives me an Error 404 
>>>>
>>>> On Thursday, July 23, 2020 at 3:22:07 PM UTC-5 galfert wrote:
>>>>
>>>>> There is a thread in the developer section where some questions were 
>>>>> asked that were not directly related to development. This thread is good. 
>>>>> I'm just inviting people to ask their questions here in this thread 
>>>>> rather 
>>>>> than in the developer section.
>>>>>
>>>>>
>>>>> On Thursday, July 23, 2020 at 2:56:51 PM UTC-4, steeple ian wrote:
>>>>>
>>>>>> ???
>>>>>>
>>>>>> On Thu, 23 Jul 2020 at 19:39, galfert  wrote:
>>>>>>
>>>>> For anyone discussing this new GW1000 API driver in the WeeWX 
>>>>>>> development section STOP. Use this user section instead to discuss its 
>>>>>>> use.
>>>>>>>
>>>>>>>
>>>>>>> -- 
>>>>>>> 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...@googlegroups.com.
>>>>>>
>>>>>>
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid/weewx-user/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%40googlegroups.com
>>>>>>>  
>>>>>>> <https://groups.google.com/d/msgid/weewx-user/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%40googlegroups.com?utm_medium=email_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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/659a01a4-0fb0-4100-aa5c-c53c7342cfb3n%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

Ian,
Yes, just the simple Seasons skin for now. I now have 12 hours of data and 
it's looking good. 
I've compared it to my weather station console and the data all looks 
correct.

On Friday, July 24, 2020 at 12:56:01 PM UTC-5 steep...@gmail.com wrote:

> Hi Bill,
> No need to be sorry. Just wanted to exchange notes on experiences. I 
> assume you then using the default Seasons skin. How is that looking?
> Ian
>
> On Fri, 24 Jul 2020 at 18:12, Bill Arthur  wrote:
>
>> Hi Ian
>> No, I don't have Weather34 on the RasPi that I'm testing the GW1000 
>> extension, it's a fresh install.
>> It'll be a while until I'm ready to modify the RasPi that has Weather34. 
>> Sorry.
>>
>> On Friday, July 24, 2020 at 10:09:08 AM UTC-5 steep...@gmail.com wrote:
>>
>>> Hi Bill,
>>>
>>> Are you still using the Weather34 skin. If so, I am interested what 
>>> barometer reading you are displaying when using the gw1000 driver.
>>>
>>> Thanks,
>>> Ian 
>>>
>>>
>>> On Friday, July 24, 2020 at 4:02:17 AM UTC+1, Bill Arthur wrote:
>>>>
>>>> I couldn't get it to run from the command line.
>>>> When I  did   python -m user.gw1000 --help
>>>> I get   /usr/bin/python: No module named user.gw1000
>>>>
>>>> But I have it up and running, everything looks good on my Seasons page.
>>>> I'll give the data a closer look tomorrow.
>>>>
>>>> But I'm scratching my head trying to find how to specify the IP address 
>>>> in weewx.conf
>>>> I have three GW1000s here, I have no idea which one is being used  
>>>> On Thursday, July 23, 2020 at 9:06:47 PM UTC-5 Bill Arthur wrote:
>>>>
>>>>> This link works: 
>>>>> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/gw1000-0.1.0b4.tar.gz
>>>>>
>>>>> On Thursday, July 23, 2020 at 8:57:49 PM UTC-5 Bill Arthur wrote:
>>>>>
>>>>>> FYI:
>>>>>> wget -P /var/tmp 
>>>>>> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/weewx-gw1000-0.1.0b4.tar.gz
>>>>>>  
>>>>>> gives me an Error 404 
>>>>>>
>>>>>> On Thursday, July 23, 2020 at 3:22:07 PM UTC-5 galfert wrote:
>>>>>>
>>>>>>> There is a thread in the developer section where some questions were 
>>>>>>> asked that were not directly related to development. This thread is 
>>>>>>> good. 
>>>>>>> I'm just inviting people to ask their questions here in this thread 
>>>>>>> rather 
>>>>>>> than in the developer section.
>>>>>>>
>>>>>>>
>>>>>>> On Thursday, July 23, 2020 at 2:56:51 PM UTC-4, steeple ian wrote:
>>>>>>>
>>>>>>>> ???
>>>>>>>>
>>>>>>>> On Thu, 23 Jul 2020 at 19:39, galfert  wrote:
>>>>>>>>
>>>>>>> For anyone discussing this new GW1000 API driver in the WeeWX 
>>>>>>>>> development section STOP. Use this user section instead to discuss 
>>>>>>>>> its use.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -- 
>>>>>>>>> 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...@googlegroups.com.
>>>>>>>>
>>>>>>>>
>>>>>>>>> To view this discussion on the web visit 
>>>>>>>>> https://groups.google.com/d/msgid/weewx-user/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%40googlegroups.com
>>>>>>>>>  
>>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%40googlegroups.com?utm_medium=email_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 weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/6cb996ae-fc26-4cb8-85ce-b408a9cefa5dn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/6cb996ae-fc26-4cb8-85ce-b408a9cefa5dn%40googlegroups.com?utm_medium=email_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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/bf6c137d-9973-4a6c-896f-6d43b535ab94n%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

Hi Ian
No, I don't have Weather34 on the RasPi that I'm testing the GW1000 
extension, it's a fresh install.
It'll be a while until I'm ready to modify the RasPi that has Weather34. 
Sorry.

On Friday, July 24, 2020 at 10:09:08 AM UTC-5 steep...@gmail.com wrote:

> Hi Bill,
>
> Are you still using the Weather34 skin. If so, I am interested what 
> barometer reading you are displaying when using the gw1000 driver.
>
> Thanks,
> Ian 
>
>
> On Friday, July 24, 2020 at 4:02:17 AM UTC+1, Bill Arthur wrote:
>>
>> I couldn't get it to run from the command line.
>> When I  did   python -m user.gw1000 --help
>> I get   /usr/bin/python: No module named user.gw1000
>>
>> But I have it up and running, everything looks good on my Seasons page.
>> I'll give the data a closer look tomorrow.
>>
>> But I'm scratching my head trying to find how to specify the IP address 
>> in weewx.conf
>> I have three GW1000s here, I have no idea which one is being used  
>> On Thursday, July 23, 2020 at 9:06:47 PM UTC-5 Bill Arthur wrote:
>>
>>> This link works: 
>>> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/gw1000-0.1.0b4.tar.gz
>>>
>>> On Thursday, July 23, 2020 at 8:57:49 PM UTC-5 Bill Arthur wrote:
>>>
>>>> FYI:
>>>> wget -P /var/tmp 
>>>> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/weewx-gw1000-0.1.0b4.tar.gz
>>>>  
>>>> gives me an Error 404 
>>>>
>>>> On Thursday, July 23, 2020 at 3:22:07 PM UTC-5 galfert wrote:
>>>>
>>>>> There is a thread in the developer section where some questions were 
>>>>> asked that were not directly related to development. This thread is good. 
>>>>> I'm just inviting people to ask their questions here in this thread 
>>>>> rather 
>>>>> than in the developer section.
>>>>>
>>>>>
>>>>> On Thursday, July 23, 2020 at 2:56:51 PM UTC-4, steeple ian wrote:
>>>>>
>>>>>> ???
>>>>>>
>>>>>> On Thu, 23 Jul 2020 at 19:39, galfert  wrote:
>>>>>>
>>>>> For anyone discussing this new GW1000 API driver in the WeeWX 
>>>>>>> development section STOP. Use this user section instead to discuss its 
>>>>>>> use.
>>>>>>>
>>>>>>>
>>>>>>> -- 
>>>>>>> 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...@googlegroups.com.
>>>>>>
>>>>>>
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid/weewx-user/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%40googlegroups.com
>>>>>>>  
>>>>>>> <https://groups.google.com/d/msgid/weewx-user/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%40googlegroups.com?utm_medium=email_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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6cb996ae-fc26-4cb8-85ce-b408a9cefa5dn%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

I couldn't get it to run from the command line.
When I  did   python -m user.gw1000 --help
I get   /usr/bin/python: No module named user.gw1000

But I have it up and running, everything looks good on my Seasons page.
I'll give the data a closer look tomorrow.

But I'm scratching my head trying to find how to specify the IP address in 
weewx.conf
I have three GW1000s here, I have no idea which one is being used  
On Thursday, July 23, 2020 at 9:06:47 PM UTC-5 Bill Arthur wrote:

> This link works: 
> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/gw1000-0.1.0b4.tar.gz
>
> On Thursday, July 23, 2020 at 8:57:49 PM UTC-5 Bill Arthur wrote:
>
>> FYI:
>> wget -P /var/tmp 
>> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/weewx-gw1000-0.1.0b4.tar.gz
>>  
>> gives me an Error 404 
>>
>> On Thursday, July 23, 2020 at 3:22:07 PM UTC-5 galfert wrote:
>>
>>> There is a thread in the developer section where some questions were 
>>> asked that were not directly related to development. This thread is good. 
>>> I'm just inviting people to ask their questions here in this thread rather 
>>> than in the developer section.
>>>
>>>
>>> On Thursday, July 23, 2020 at 2:56:51 PM UTC-4, steeple ian wrote:
>>>
>>>> ???
>>>>
>>>> On Thu, 23 Jul 2020 at 19:39, galfert  wrote:
>>>>
>>> For anyone discussing this new GW1000 API driver in the WeeWX 
>>>>> development section STOP. Use this user section instead to discuss its 
>>>>> use.
>>>>>
>>>>>
>>>>> -- 
>>>>> 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...@googlegroups.com.
>>>>
>>>>
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/weewx-user/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/weewx-user/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%40googlegroups.com?utm_medium=email_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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/82d0a22f-2f73-43a9-b016-be349e19d221n%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

I have it up and running, everything looks good on my Seasons page.
I'll give the data a closer look tomorrow.
But I'm scratching my head trying to find how to specify the IP address in 
weewx.conf
I have three GW1000s here, I have no idea which one is being used..

On Thursday, July 23, 2020 at 9:06:47 PM UTC-5 Bill Arthur wrote:

> This link works: 
> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/gw1000-0.1.0b4.tar.gz
>
> On Thursday, July 23, 2020 at 8:57:49 PM UTC-5 Bill Arthur wrote:
>
>> FYI:
>> wget -P /var/tmp 
>> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/weewx-gw1000-0.1.0b4.tar.gz
>>  
>> gives me an Error 404 
>>
>> On Thursday, July 23, 2020 at 3:22:07 PM UTC-5 galfert wrote:
>>
>>> There is a thread in the developer section where some questions were 
>>> asked that were not directly related to development. This thread is good. 
>>> I'm just inviting people to ask their questions here in this thread rather 
>>> than in the developer section.
>>>
>>>
>>> On Thursday, July 23, 2020 at 2:56:51 PM UTC-4, steeple ian wrote:
>>>
>>>> ???
>>>>
>>>> On Thu, 23 Jul 2020 at 19:39, galfert  wrote:
>>>>
>>> For anyone discussing this new GW1000 API driver in the WeeWX 
>>>>> development section STOP. Use this user section instead to discuss its 
>>>>> use.
>>>>>
>>>>>
>>>>> -- 
>>>>> 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...@googlegroups.com.
>>>>
>>>>
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/weewx-user/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/weewx-user/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%40googlegroups.com?utm_medium=email_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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6760390b-8d52-4267-8a40-56ff89ef5b6cn%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

This link 
works: 
https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/gw1000-0.1.0b4.tar.gz

On Thursday, July 23, 2020 at 8:57:49 PM UTC-5 Bill Arthur wrote:

> FYI:
> wget -P /var/tmp 
> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/weewx-gw1000-0.1.0b4.tar.gz
>  
> gives me an Error 404 
>
> On Thursday, July 23, 2020 at 3:22:07 PM UTC-5 galfert wrote:
>
>> There is a thread in the developer section where some questions were 
>> asked that were not directly related to development. This thread is good. 
>> I'm just inviting people to ask their questions here in this thread rather 
>> than in the developer section.
>>
>>
>> On Thursday, July 23, 2020 at 2:56:51 PM UTC-4, steeple ian wrote:
>>
>>> ???
>>>
>>> On Thu, 23 Jul 2020 at 19:39, galfert  wrote:
>>>
>> For anyone discussing this new GW1000 API driver in the WeeWX development 
>>>> section STOP. Use this user section instead to discuss its use.
>>>>
>>>>
>>>> -- 
>>>> 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...@googlegroups.com.
>>>
>>>
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%40googlegroups.com?utm_medium=email_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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/dc6cb1a4-3e7d-45b2-8aaf-489d5c186380n%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

FYI:
wget -P /var/tmp 
https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/weewx-gw1000-0.1.0b4.tar.gz
 
gives me an Error 404 

On Thursday, July 23, 2020 at 3:22:07 PM UTC-5 galfert wrote:

> There is a thread in the developer section where some questions were asked 
> that were not directly related to development. This thread is good. I'm 
> just inviting people to ask their questions here in this thread rather than 
> in the developer section.
>
>
> On Thursday, July 23, 2020 at 2:56:51 PM UTC-4, steeple ian wrote:
>
>> ???
>>
>> On Thu, 23 Jul 2020 at 19:39, galfert  wrote:
>>
> For anyone discussing this new GW1000 API driver in the WeeWX development 
>>> section STOP. Use this user section instead to discuss its use.
>>>
>>>
>>> -- 
>>> 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...@googlegroups.com.
>>
>>
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%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/eb5f0739-2fdb-4345-910a-81c4f6f69584n%40googlegroups.com.

[weewx-user] Re: Need help with ignore_zero_wind and interceptor

2020-07-22 Thread Bill Arthur

Gary,
I'm happy to report that all stations are reporting correctly.
Thanks again for your quick response.
Bill

On Wednesday, July 22, 2020 at 12:31:29 AM UTC-5 gjr80 wrote:

> Yep Bill, in this case order is important not indenting.
>
> Gary
>
> On Wednesday, 22 July 2020 at 15:24:27 UTC+10 wa4...@gmail.com wrote:
>
>> Gary,
>>
>> No. I have it in the wrong place. Unless instructions say other wise I 
>> generally add to the bottom.
>> I'll change it and reply back tomorrow.
>>
>> Thanks !!
>> Bill
>>
>> On Wednesday, July 22, 2020 at 12:21:08 AM UTC-5 gjr80 wrote:
>>
>>> Bill,
>>>
>>> Just to confirm [StdWXCalculate] should look like this:
>>>
>>> [StdWCalculate]
>>> ignore_zero_wind = False
>>> [[Calculations]]
>>> pressure = prefer_hardware
>>> ...
>>>
>>> From memory putting ignore_zero_wind as the last line will put it under 
>>> [[Calculations]] which would explain it's incorrect operation.
>>>
>>> Gary
>>>
>>> On Wednesday, 22 July 2020 at 14:37:47 UTC+10 wa4...@gmail.com wrote:
>>>
>>>> Thanks Gary!!
>>>> I was able to run interceptor directly and with a wind speed of 0.0 my 
>>>> direction reads 262.0. I immediately ran weewd and with a wind speed of 
>>>> 0.0 
>>>> my wind direction is none.
>>>> I have ignore_zero_wind = False as the last line in StdWxCalculate
>>>>
>>>> Bill
>>>> On Tuesday, July 21, 2020 at 11:26:03 PM UTC-5 gjr80 wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Your device will be sending the same wind obs to WeeWX and the 
>>>>> Meteobridge. I can't speak for the Meteobridge but you are right in that 
>>>>> you can control the wind direction within WeeWX when windSpeed is 
>>>>> zero through use of the ignore_zero_wind config option. The 
>>>>> ignore_zero_wind config option is nothing to do with the interceptor 
>>>>> driver per se, rather once WeeWX has a packet from the interceptor driver 
>>>>> WeeWX will check the ignore_zero_wind setting and if it is True (the 
>>>>> default) windDir will be set to the python value None if windSpeed is 
>>>>> zero. If ignore_zero_wind is False then windDir will be left 
>>>>> unchanged (whatever value was reported by the station).
>>>>>
>>>>> That being said you have a lot of moving parts there and I think the 
>>>>> best approach is to work through from sensor to output. I would be 
>>>>> running 
>>>>> the interceptor driver directly and looking at what happens when 
>>>>> windSpeed is zero, what is windDir? Then step forward a bit and run 
>>>>> WeeWX directly <http://weewx.com/docs/usersguide.htm#Running_directly>, 
>>>>> what do you see for windDir when windSpeed is zero? What about if you 
>>>>> set ignore_zero_wind = False (remember True is the default).
>>>>>
>>>>> Your error when running interceptor is due to a little WeeWX shorthand 
>>>>> in the instructions. Try using full paths (you have a package install), 
>>>>> something like:
>>>>>
>>>>> $ PYTHONPATH=/usr/share/weewx python 
>>>>> /usr/share/weewx/user/interceptor.py --device=fineoffset-bridge 
>>>>> --mode=listen --port=8007
>>>>>
>>>>> Gary
>>>>>
>>>>> On Wednesday, 22 July 2020 at 03:57:43 UTC+10 wa4...@gmail.com wrote:
>>>>>
>>>>>> I need assistance to figure out where to look for a problem with 
>>>>>> "ignore_zero_wind". (and interceptor)
>>>>>>
>>>>>> I have five Raspberry Pi's at three physical locations: zero, 3B+ and 
>>>>>> 4. All are running 05/2020 OS
>>>>>> Four are running Weewx 4.1.1, one is 3.9.2  All have the same issue.
>>>>>> At my remote locations Weewx runs in parallel with Meteobridge, both 
>>>>>> receiving the same data through a GW1000, from  WS-2902 arrays.
>>>>>> Meteobridge never shows 0 for wind_dir. I would prefer consistancy 
>>>>>> between the two systems.
>>>>>> My bad windir data comes out in three ways:
>>>>>>  "0" from my output extensions, cwxn and weewx2aprx
>>>>>>  "NaN" from W34 charts
>>>&g

[weewx-user] Re: Need help with ignore_zero_wind and interceptor

2020-07-21 Thread Bill Arthur

Gary,

No. I have it in the wrong place. Unless instructions say other wise I 
generally add to the bottom.
I'll change it and reply back tomorrow.

Thanks !!
Bill

On Wednesday, July 22, 2020 at 12:21:08 AM UTC-5 gjr80 wrote:

> Bill,
>
> Just to confirm [StdWXCalculate] should look like this:
>
> [StdWCalculate]
> ignore_zero_wind = False
> [[Calculations]]
> pressure = prefer_hardware
> ...
>
> From memory putting ignore_zero_wind as the last line will put it under 
> [[Calculations]] which would explain it's incorrect operation.
>
> Gary
>
> On Wednesday, 22 July 2020 at 14:37:47 UTC+10 wa4...@gmail.com wrote:
>
>> Thanks Gary!!
>> I was able to run interceptor directly and with a wind speed of 0.0 my 
>> direction reads 262.0. I immediately ran weewd and with a wind speed of 0.0 
>> my wind direction is none.
>> I have ignore_zero_wind = False as the last line in StdWxCalculate
>>
>> Bill
>> On Tuesday, July 21, 2020 at 11:26:03 PM UTC-5 gjr80 wrote:
>>
>>> Hi,
>>>
>>> Your device will be sending the same wind obs to WeeWX and the 
>>> Meteobridge. I can't speak for the Meteobridge but you are right in that 
>>> you can control the wind direction within WeeWX when windSpeed is zero 
>>> through use of the ignore_zero_wind config option. The ignore_zero_wind 
>>> config option is nothing to do with the interceptor driver per se, rather 
>>> once WeeWX has a packet from the interceptor driver WeeWX will check the 
>>> ignore_zero_wind setting and if it is True (the default) windDir will 
>>> be set to the python value None if windSpeed is zero. If 
>>> ignore_zero_wind is False then windDir will be left unchanged (whatever 
>>> value was reported by the station).
>>>
>>> That being said you have a lot of moving parts there and I think the 
>>> best approach is to work through from sensor to output. I would be running 
>>> the interceptor driver directly and looking at what happens when 
>>> windSpeed is zero, what is windDir? Then step forward a bit and run 
>>> WeeWX directly <http://weewx.com/docs/usersguide.htm#Running_directly>, 
>>> what do you see for windDir when windSpeed is zero? What about if you 
>>> set ignore_zero_wind = False (remember True is the default).
>>>
>>> Your error when running interceptor is due to a little WeeWX shorthand 
>>> in the instructions. Try using full paths (you have a package install), 
>>> something like:
>>>
>>> $ PYTHONPATH=/usr/share/weewx python 
>>> /usr/share/weewx/user/interceptor.py --device=fineoffset-bridge 
>>> --mode=listen --port=8007
>>>
>>> Gary
>>>
>>> On Wednesday, 22 July 2020 at 03:57:43 UTC+10 wa4...@gmail.com wrote:
>>>
>>>> I need assistance to figure out where to look for a problem with 
>>>> "ignore_zero_wind". (and interceptor)
>>>>
>>>> I have five Raspberry Pi's at three physical locations: zero, 3B+ and 
>>>> 4. All are running 05/2020 OS
>>>> Four are running Weewx 4.1.1, one is 3.9.2  All have the same issue.
>>>> At my remote locations Weewx runs in parallel with Meteobridge, both 
>>>> receiving the same data through a GW1000, from  WS-2902 arrays.
>>>> Meteobridge never shows 0 for wind_dir. I would prefer consistancy 
>>>> between the two systems.
>>>> My bad windir data comes out in three ways:
>>>>  "0" from my output extensions, cwxn and weewx2aprx
>>>>  "NaN" from W34 charts
>>>>  "None" from a custom Seasons report file
>>>> Three different output methods allowed me to conclude it wasn't the 
>>>> output. I added "ignore_zero_wind" with no effect. Nothing unusual in the 
>>>> logs.
>>>> I studied previous posts with the same issue and saw suggestions to run 
>>>> weewxd. When I did, in the loop packets I saw "none" as wind_dir when wind 
>>>> speed was 0
>>>> My suspicion is that if the loop packet has "none" it isn't weewx, more 
>>>> likely the interceptor. Is that correct?
>>>>
>>>> So I'm trying to run weewx-interceptor directly, which in my case was 
>>>> given as PYTHONPATH=bin python bin/user/interceptor.py 
>>>> --device=fineoffset-bridge --mode=listen --port=8007
>>>> I used /usr/share/weewx/user/interceptor.py and got an error in line 
>>>> 302, "Import Error: no module named weewx.drivers". So I tried 
>>>> interceptor.py --help, as suggested in github, and got the same error.
>>>>
>>>> Since I'm so all over the place I haven't yet attached logs or configs 
>>>> yet. I need direction.
>>>>
>>>

-- 
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/d573b0ea-af19-424e-b687-adfbc1aa7f32n%40googlegroups.com.

[weewx-user] Re: Need help with ignore_zero_wind and interceptor

2020-07-21 Thread Bill Arthur

Thanks Gary!!
I was able to run interceptor directly and with a wind speed of 0.0 my 
direction reads 262.0. I immediately ran weewd and with a wind speed of 0.0 
my wind direction is none.
I have ignore_zero_wind = False as the last line in StdWxCalculate

Bill
On Tuesday, July 21, 2020 at 11:26:03 PM UTC-5 gjr80 wrote:

> Hi,
>
> Your device will be sending the same wind obs to WeeWX and the 
> Meteobridge. I can't speak for the Meteobridge but you are right in that 
> you can control the wind direction within WeeWX when windSpeed is zero 
> through use of the ignore_zero_wind config option. The ignore_zero_wind 
> config option is nothing to do with the interceptor driver per se, rather 
> once WeeWX has a packet from the interceptor driver WeeWX will check the 
> ignore_zero_wind setting and if it is True (the default) windDir will be 
> set to the python value None if windSpeed is zero. If ignore_zero_wind is 
> False then windDir will be left unchanged (whatever value was reported by 
> the station).
>
> That being said you have a lot of moving parts there and I think the best 
> approach is to work through from sensor to output. I would be running the 
> interceptor driver directly and looking at what happens when windSpeed is 
> zero, what is windDir? Then step forward a bit and run WeeWX directly 
> <http://weewx.com/docs/usersguide.htm#Running_directly>, what do you see 
> for windDir when windSpeed is zero? What about if you set ignore_zero_wind 
> = False (remember True is the default).
>
> Your error when running interceptor is due to a little WeeWX shorthand in 
> the instructions. Try using full paths (you have a package install), 
> something like:
>
> $ PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/interceptor.py 
> --device=fineoffset-bridge --mode=listen --port=8007
>
> Gary
>
> On Wednesday, 22 July 2020 at 03:57:43 UTC+10 wa4...@gmail.com wrote:
>
>> I need assistance to figure out where to look for a problem with 
>> "ignore_zero_wind". (and interceptor)
>>
>> I have five Raspberry Pi's at three physical locations: zero, 3B+ and 4. 
>> All are running 05/2020 OS
>> Four are running Weewx 4.1.1, one is 3.9.2  All have the same issue.
>> At my remote locations Weewx runs in parallel with Meteobridge, both 
>> receiving the same data through a GW1000, from  WS-2902 arrays.
>> Meteobridge never shows 0 for wind_dir. I would prefer consistancy 
>> between the two systems.
>> My bad windir data comes out in three ways:
>>  "0" from my output extensions, cwxn and weewx2aprx
>>  "NaN" from W34 charts
>>  "None" from a custom Seasons report file
>> Three different output methods allowed me to conclude it wasn't the 
>> output. I added "ignore_zero_wind" with no effect. Nothing unusual in the 
>> logs.
>> I studied previous posts with the same issue and saw suggestions to run 
>> weewxd. When I did, in the loop packets I saw "none" as wind_dir when wind 
>> speed was 0
>> My suspicion is that if the loop packet has "none" it isn't weewx, more 
>> likely the interceptor. Is that correct?
>>
>> So I'm trying to run weewx-interceptor directly, which in my case was 
>> given as PYTHONPATH=bin python bin/user/interceptor.py 
>> --device=fineoffset-bridge --mode=listen --port=8007
>> I used /usr/share/weewx/user/interceptor.py and got an error in line 302, 
>> "Import Error: no module named weewx.drivers". So I tried interceptor.py 
>> --help, as suggested in github, and got the same error.
>>
>> Since I'm so all over the place I haven't yet attached logs or configs 
>> yet. I need direction.
>>
>

-- 
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/569ed731-3a51-4943-865b-002f9a05c63bn%40googlegroups.com.

[weewx-user] Need help with ignore_zero_wind and interceptor

2020-07-21 Thread Bill Arthur

I need assistance to figure out where to look for a problem with
"ignore_zero_wind". (and interceptor)

I have five Raspberry Pi's at three physical locations: zero, 3B+ and 4.
All are running 05/2020 OS
Four are running Weewx 4.1.1, one is 3.9.2 All have the same issue.
At my remote locations Weewx runs in parallel with Meteobridge, both
receiving the same data through a GW1000, from WS-2902 arrays.
Meteobridge never shows 0 for wind_dir. I would prefer consistancy between
the two systems.
My bad windir data comes out in three ways:
"0" from my output extensions, cwxn and weewx2aprx
"NaN" from W34 charts
"None" from a custom Seasons report file
Three different output methods allowed me to conclude it wasn't the output.
I added "ignore_zero_wind" with no effect. Nothing unusual in the logs.
I studied previous posts with the same issue and saw suggestions to run
weewxd. When I did, in the loop packets I saw "none" as wind_dir when wind
speed was 0
My suspicion is that if the loop packet has "none" it isn't weewx, more
likely the interceptor. Is that correct?

So I'm trying to run weewx-interceptor directly, which in my case was given
as PYTHONPATH=bin python bin/user/interceptor.py --device=fineoffset-bridge
--mode=listen --port=8007
I used /usr/share/weewx/user/interceptor.py and got an error in line 302,
"Import Error: no module named weewx.drivers". So I tried interceptor.py
--help, as suggested in github, and got the same error.

Since I'm so all over the place I haven't yet attached logs or configs yet.
I need direction.

--
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/47caf7ab-7223-4c6f-b178-668d410296f2n%40googlegroups.com.

Re: [weewx-user] windDir missing from archive records

2020-07-16 Thread Bill Arthur

Thanks for bringing this up.  I've been busy troubleshooting this issue 
with my stations. I should have RTFM'd.
I've added  ignore_zero_wind = False, we'll see how it looks tomorrow.


On Wednesday, July 15, 2020 at 5:15:01 PM UTC-5, Tom Keffer wrote:
>
> See if the documentation answers your question: 
> http://weewx.com/docs/usersguide.htm#zero_windspeed
>
> On Wed, Jul 15, 2020 at 3:05 PM Pat > 
> wrote:
>
>> Can you post some of your loop and rec records from weewxd? 
>>
>> Any errors in syslog? 
>>
>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/6df048e3-1403-4083-9da2-8848b186106fo%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/d4ef4fb4-f889-4bbc-baf6-466a6e3dd4c8o%40googlegroups.com.

[weewx-user] Re: howto receive MQTT data from a running broker and put the data into database with weewx..?

2020-07-11 Thread Bill Morrow

Sorry for the late reply. I don't have much time to work on my original 
wxMesh driver. 

>From what I have seen of MQTTSubscribe, it's a much more complete 
implementation of an MQTT subscriber, and offers the features I was 
planning on adding some day. When I get a chance, I plan on switching to 
using MQTTSubscribe.



On Wednesday, 24 June 2020 18:00:44 UTC-3, Rich Bell wrote:
>
> Great to hear. Just give a shout if you run into any other difficulties.
> rich
>
> On Wednesday, 24 June 2020 16:50:26 UTC-4, Christian Peters wrote:
>>
>> Hi Rich,
>>
>> thank you very much. 
>> It works like a charm! :-) 
>>
>> I set up a temporary mapping to values already available in the databae. 
>> For the temp and humid values it works out of the box, for CPM, CPS and 
>> radiation I have to setup unit groups later. 
>>
>> This is my working setup - just to have that written down for others:
>>
>> my data form the MQTT broker:
>>
>>
>> radiation:0.17,cpm:31,cps:0,temp_2m:25.97,temp_5cm:27.24,temp_dht22:34.30,hum_dht22:45.30,rain:0.00
>>
>> weewx.conf:
>>
>> [MQTTSubscribeService]
>> host = xxx.xxx.xxx.xxx # IP of the broker
>> payload_type = keyword
>> console = True
>> [[topics]]
>>  [[[weather]]]   # The topic you are subscribing to
>>unit_system = METRICWX # Not sure weather you want METRICWX or 
>> METRIC. See http://weewx.com/docs/customizing.htm#units
>>temp_2m # Name in the MQTT message
>>name = extraTemp1 # WeeWX name
>>temp_5cm
>>name = extraTemp2
>>temp_dht22
>>name = extraTemp3
>>hum_dht22
>>name = extraHumid3
>>rain
>>name = hail
>>radiation
>>name = signal1
>>cpm
>>name = signal2
>>cps
>>name = signal3
>>
>> [[message_callback]]
>>  type = keyword
>>  keyword_delimiter = "," # The delimiter between the name/value pairs
>>  keyword_separator = ":" # The separator between the name and the value
>>
>> [[Services]]
>> data_services = user.MQTTSubscribe.MQTTSubscribeService
>>
>> That's quite nice and more elegant as to set up a second weewx instance 
>> with a MQTT driver! 
>> Thank you very much.
>>
>> My MQTT broker runs on a BananaPi which is located in the garden near the 
>> sensors (Temp2m, Temp5cm, raingauge, temp and hum sensor inside the 
>> controlbox and a MightyOhm Geiger Counter Kit).
>> I can't figure out why...but somtimes I lost the WLAN connection (after 
>> 7-30 days). Then I restart the BananPi, start the mosquitto deamon...but 
>> the weewx instance running the wxMesh driver didn't reconnect. 
>> I have to start and stop this instance, then it works again. But I saw a 
>> post in weewx-development that someone pointed out the connection was setup 
>> once at initialisation...maybe there is no check of the connection and a 
>> reconnect condition?
>>
>> If the setup goes online (at the moment I run the simulator whil 
>> mograting all sensors and tweak the new webpage) and the VanatgeVP2 is 
>> connected, I will check the behavior of your drriver in my setup. 
>>
>> Thanks again for the excellent support. If I run into some problems I 
>> will contact you again. :-)
>>
>> Regards,
>>
>> Christian 
>>
>> P.S. Ken, thanks for you fix...it works..! :-) But the 
>> MQTTSubscribeService works great and I will prefer to run only one weewx 
>> instance to deal with all sensors. 
>>
>>
>> Am Mittwoch, 24. Juni 2020 19:25:05 UTC+2 schrieb Rich Bell:
>>>
>>>
>>> Well, I haven't heard of having to restart WeeWX when the connection is 
>>> lost, and if that happens I would certainly want to look into fixing that. 
>>> I'll do some experiments to see if I can recreate. 
>>>
>>> Sounds like picking the service might be the best long term choice, with 
>>> the caveat about the reconnect logic needing to be verified. But if you 
>>> want to get your feet wet, I would suggest that we get it up and running as 
>>> a driver - perhaps even running from the command line for a bit. The actual 
>>> configuration work is really the same. So you could migrate to the service 
>>> as you get more comfortable or after we prove that lost connections are not 
>>> a problem. 
>>>
>>> The following assumes that you install 1.5.4-rc01. This changed the way 
>>> to configure MQTTSubscribe. Once installed, there will be three key 
>>> sections the [MQTTSubscribeDriver]/[MQTTSubscribeService] section. This is 
>>> the MQTT connection information, and I believe this is pretty straight 
>>> forward. But after looking at it, if you have questions let me know.
>>>
>>> Next up is the [[topics]] section. Based on the information you posted, 
>>> I think this is what you would want
>>>
>>> [[topics]]
>>>  [[[weather]]]   # The topic you are subscribing to
>>>unit_system = METRICWX # Not sure weather you want METRICWX or 
>>> METRIC. See

[weewx-user] Re: 2 systems in parallel. Meteobridge and Raspberry PI

2020-06-28 Thread Bill Arthur

I run WeeWx in parallel with Meteobridge.  My setup is different than yours 
and I don't have the issues you have.

I have three stations, two are remote require a considerable drive. I am 
using the GW-1000 which sends data to both devices. I can log in remotely 
to both the RasPi (using VNC) and Meteobridge so that I can remotely 
reconfigure if I see a problem.

It's working very well for me. It saves a lot of driving.
I hope you are able to get the kinks out.

On Friday, May 19, 2017 at 5:54:54 AM UTC-5, Gert Andersen wrote:
>
> Hi
>
> I'm moving away from Meteobridge to weeWX, installed on a Raspberry PI. 
> Now the question. Is it possible to have 2 installations at the same time. 
> The Meteobridge continues as now and sends data to my productionserver and 
> the Raspberry should send data to my testserver. The Meteobridge receives 
> data via USB from a Davis Vantage Pro2 station.
>
> I would then set up a USB hub where Davis, Meteobridge and Raspberry are 
> connected to. That way, I can hopefully run the 2 systems in parallel for a 
> while.
>
> Would this configuration be possible?
>
> Thanks
>
> Rgds
> Gert
>

-- 
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/cb500240-c01d-46c8-a6eb-acf35f03a5cbo%40googlegroups.com.

[weewx-user] Re: Upgrade to 4.1 and shift to Interceptor from ObeserverIP

2020-06-04 Thread Bill Arthur

I had several stations using ObserverIPs, and switched them all over to 
Ecowitt GW1000s. 
So with my (now surplus) ObserverIPs I tried getting them to report to 
WeeWx. I finally gave up from frustration.
The solution to your problem may be getting a GW1000, it's only about $35 
and works flawlessly.



On Wednesday, June 3, 2020 at 9:34:49 AM UTC-5, Jonathan Zitelman wrote:
>
> After six years I am finally upgrading my Raspberry Pi to a newer model, 
> and re-vamping my base image.  While transitioning to Debian 10, I am 
> upgrading from WeeWX 3.8 to 4.1.  My biggest issue has been getting a 
> working driver.  I have an Ambient WS-1400 and was originally using the 
> ObserverIP driver (mwall version) with no issues.  The device is running 
> "Ambient Weather 4.5.8" and reports directly to Weather Underground 
> (non-customizable).
>
> I have tried installing Interceptor, but have had no luck with either the 
> sniff or listen modes.  I have run the driver directly, separately from 
> WeeWX, in both modes with no errors, but no results either.  I looked to 
> reinstall ObserverIP, but unfortunately I have not been able to find the 
> location of a release. (Matthew Wall, any suggestions? I looked on GitHub 
> but couldn't find a file).
>
> I just wanted to seek some advice before intercepting and re-directing the 
> traffic, as noted in the Interceptor documentation, as that seems to add a 
> larger level of complication and creates more opportunities for issues.  If 
> I can find the ObserverIP driver, I would probably go that route.
>
> Thanks,
> Jonathan †
>

-- 
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/7b1b63ac-a866-4f83-9dff-29bacdfbdcb2o%40googlegroups.com.

Re: [weewx-user] Re: Registering on weewx map.

2020-06-04 Thread Bill Burton

Hello Matt,

On Wed, Jun 3, 2020 at 4:10 PM mwall  wrote:

> On Wednesday, June 3, 2020 at 1:55:15 PM UTC-4, William Burton wrote:
>>
>> If the screen capture for your own site fails or if the site's skin has
>> been changed, is there a way to get the registration process to retry the
>> screen capture?
>>
>> Is there a way to test the screen capture outside of the registration
>> process to see if it will work correctly?
>>
>
> hi bill,
>
> i made a wiki page to explain the registry:
>
> https://github.com/weewx/weewx/wiki/registry
>
>
Thanks, this is helpful. Does the description come from [Station], location?

i'm still working on the capture process.  the previous implementation used
> wkhtmltoimage, but that would periodically suck up every bit of memory and
> swap, bringing the capture server to its knees.  using phantomjs has
> alleviated that somewhat, but there are still some problems.  i'll try to
> remember to write up what i learn once its sorted out.
>

I tried a few test captures using phantomjs 2.1.1 and there were a number
of problems due to missing content or sections being rendered incorrectly.

>
> there is no way to force an update of the capture.  it is a somewhat
> stochastic process (intentionally, to avoid overloading the system).
>

Yes, of course.

>
> once the capture process is more reliable we will be able to tune it.  who
> knows, some kind of waybackmachine-like abilities might even be possible!
>

A couple of challenges I can see are some of the skins are sensitive to
width such that a certain minimum around 1300px is needed and the second is
that if the capture is done at a random time, it may not reflect what the
site owner would like for the image due to the time of day or other factors.

-Bill

-- 
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/CAKKfUm93QAwEvnsyOtFnc2pCCdeP6ScK%2BeMWOsCNO4G8P5TT6g%40mail.gmail.com.

[weewx-user] Re: Account of setting up an Ambient WS-2902A with SDR and an additional sensor

2020-05-28 Thread Bill Arthur

Thanks for the great writeup.  I'm currently using GW-1000s for my 
stations, but my next project will be solar powered  Your method uses a 
great deal less power and will come in very handy.

On Monday, May 25, 2020 at 1:33:40 AM UTC-5, David Robinson wrote:
>
> Of possible interest:
>
> I wrote a detailed end-to-end guide 
> based on my 
> experiences setting up a weather station  
> with the following specs:
>
>- Ambient Weather WS-2902A
>- NooElec NESDR Smart v4 SDR
>- BMP180 sensor board
>- Raspberry Pi 3B+ running Raspbian Buster
>- WeeWX
>- RTL-SDR
>- RTL_433
>- WeeWX SDR Adapter (modified)
>- Adafruit_Python_BMP Library
>- WeeWX Extra Sensors Adapter (modified)
>
> I hope someone finds it useful.
>
> Regards,
>
> David Robinson
>

-- 
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/8ea6323a-3b0f-4b2c-8571-857191b2eed3%40googlegroups.com.

[weewx-user] Re: Looking for somewhat 'open' weather station to use with Raspberry based projects

2020-05-17 Thread Bill Arthur



I like the Ecowitt GW-1000 for importing data, it uses the Interceptor 
> driver. The GW-1000 will collect weather data from Ambient Weather, Ecowitt 
> and Fine Offset weather stations.
>
While the weather stations will not last as long as a Davis they are 
very economical and easy to replace. 

-- 
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/5d5a8df2-9aec-40cd-8293-0271935cd5c6%40googlegroups.com.

[weewx-user] apt-get update error

2020-05-03 Thread Bill Arthur

Currently running 3.9.2, Python2.7, Raspbian Buster,
I did an apt-get update, and got this:

Reading package lists... Done  

E: Repository 'http://weewx.com/apt squeeze InRelease' changed its 'Origin' 
value from '. squeeze' to 'python2 squeeze'
E: Repository 'http://weewx.com/apt squeeze InRelease' changed its 'Label' 
value from '. squeeze' to 'python2 squeeze'
N: This must be accepted explicitly before updates for this repository can 
be applied. See apt-secure(8) manpage for details.

What's the best thing to do? Maybe I'll hold off until this get sorted out, 
3.92 is working smoothly.

-- 
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/3a71914f-a370-4adc-b914-33b7ceb9b692%40googlegroups.com.

[weewx-user] apt-get update error on raspbian

2020-05-03 Thread Bill Arthur

I did an apt-get update, Raspbian Buster and got this:

Reading package lists... Done  

E: Repository 'http://weewx.com/apt squeeze InRelease' changed its 'Origin' 
value from '. squeeze' to 'python2 squeeze'
E: Repository 'http://weewx.com/apt squeeze InRelease' changed its 'Label' 
value from '. squeeze' to 'python2 squeeze'
N: This must be accepted explicitly before updates for this repository can 
be applied. See apt-secure(8) manpage for details.

What's the best thing to do? Maybe I'll hold off until this get sorted out.

-- 
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/a5e20b02-05f2-4295-80c8-ec6e3da62360%40googlegroups.com.

Re: [weewx-user] Re: Version 4.0 is (finally) here!

2020-05-02 Thread Bill M

Finally got a few minutes to upgrade, still using Python 2.7 and Debian 9 
but it went smoothly almost.

Must have missed comments that maxSolrRad is now maxSolarRad

Would have only taken 5 minutes if I'd seen that first
No biggie

-- 
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/36e9db90-c3f7-4480-be4f-ed342e86%40googlegroups.com.

Re: [weewx-user] Re: fileparse polling interval

2020-04-22 Thread Bill Burton

Hello,

On Tue, Apr 21, 2020 at 8:53 AM jf42  wrote:

> My station is a german "MWS 55V", which is read out by a Python program,
> writing the data to a tcp port. Another computer
> collects the data, does a quality check, many other stuff, and writes a
> file. Weewx uses the file parser to get the data.
> The station provides the data every 2 secs, the file resolution is about 5
> secs. We use the data for a lidar instrument
> (light radar) for weather monitoring during atmospheric measurements.
> Thus: the faster the better ;-)
> That's for the background of my question.
>

So it sounds like you are using the WeeWX report generation or archive
records creation to send data to the lidar?

Normally, the archive interval is configured to match reporting
requirements that will work for a day/week/month/year which is why the
default is 300 seconds/5 minutes. Also as some weather stations send data
less frequently, this gives time to collect most if not all the data of
each type. The archive interval is a different requirement than how fast a
WeeWX driver receives data.

Since you are trying to get data to the lidar as fast as possible, have you
considered using MQTT to transfer data? The message based publish-subscribe
model may be more suitable for event based data transfer than polling for
files. For instance:

   - The program that writes the data file after quality control could
   instead publish it to an MQTT topic
   <https://github.com/bellrichm/WeeWX-MQTTSubscribe/blob/master/pubmqtt.py>
   .
   - WeeWX would be configured to use the MQTT Subscribe Driver
   <https://github.com/bellrichm/WeeWX-MQTTSubscribe> and receive these
   messages as loop packets. At the appropriate time, WeeWX would write the
   archive record and generate the reports.
   - You would implement another (Python) program that subscribes to the
   same MQTT topic
   <https://github.com/bellrichm/WeeWX-MQTTSubscribe/blob/master/mqtt_test.py>
   and sends that information to the lidar as fast as data is received.

With this approach, the lidar would receive the data almost immediately
after the QC machine publishes it without going through the WeeWX archival
and report generation process. This way, the archive interval could be
configured at the right amount to meet your reporting requirements would
likely be much less frequent then how often data is received. However, if
your requirement is that all data sent to the lidar must be logged, then
you either have to log it elsewhere or use a short archive interval.
However, the MQTT driver can be configured to publish archive data which
should make it available more quickly than other methods that provide the
archive data.
The page, How to setup your own MQTT Broker
<https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/>
<https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/> is a nice
overview on setting up MQTT to work with WeeWX even if you don't use the
Belchertown skin. However, the MQTT extension for WeeWX mentioned in that
post is used to *publish* loop packets after WeeWX receives them, it cannot
act as a driver to *subscribe* to an MQTT topic for receiving data.

Hope this helps,
-Bill

-- 
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/CAKKfUm9PjshLTTbB_BCwo2m0Vm5cHfkgxLHwPUf1StcbG8ch1w%40mail.gmail.com.

[weewx-user] Weewx2aprx does not show rainfall accumulation

2020-04-09 Thread Bill Arthur

I am trying to set up a weather station in an area without internet, it 
will transmit the data back through ham radio APRS. I've tried a number of 
programs and extensions with varying degrees of poor reliability. I've 
finally found a combination that works.

My present setup is WS-2902 > GW1000 > weewx interceptor > weewx > 
weewx2aprx > aprx > APRS > NWS.  

Weewx2aprx was written by Hamid Misnan and is based on cwxn. It shares a 
problem that cwxn had, in that it reports the hourly rain but not the 12 
hour rain and rain since midnight.
I worked with Hamid to fix a humidity issue, but he no longer uses weewx 
and cannot help with the rainfall issue.
Hamid's page is here, the files can be found there:   
https://9m2tpt.blogspot.com/2015/09/getting-your-fine-offset-wx-on-rf-with.html
gjr80 was kind to fix the problem with cwxn, any assistance is appreciated.

-- 
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/d6d35da8-473b-4d11-9323-cbc79951c2ec%40googlegroups.com.

[weewx-user] SVG icons for Weather34

2020-03-21 Thread Bill Arthur

If you want to add links to the sidebar of Weather34, like Weather 
Underground, CWOP or NOAA, you'll find that you don't have all the icons 
you need.
I've attached a selection that I used. I found some on demo sites and I 
created a few.

-- 
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/052320ec-e30f-4f03-8dd6-8318220fcd1a%40googlegroups.com.
<>

[weewx-user] Re: New Weewx/W34 install works OK, but with error msgs

2020-03-18 Thread Bill Arthur

Thank you both.  I can certainly wait for for a bit. 
I'm just happy that it wasn't something stupid I did during install. 
And I look forward to helping test the new copy.




On Wednesday, March 18, 2020 at 1:56:56 PM UTC-5, Bill Arthur wrote:
>
> I just reinstalled Weewx and Weather34. It's working OK, but I get the 
> following error messages. Any idea where the problem lies?
>
> Mar 18 13:50:27 OpiQ-2 weewx[498]: cheetahgenerator: Generate failed with 
> exception ''
> Mar 18 13:50:27 OpiQ-2 weewx[498]: cheetahgenerator:  Ignoring 
> template /etc/weewx/skins/Weather34/w34charts/chartdata/result.csv.tmpl
> Mar 18 13:50:27 OpiQ-2 weewx[498]: cheetahgenerator:  Reason: 
> unsupported operand type(s) for +: 'float' and 'NoneType'
> Mar 18 13:50:27 OpiQ-2 weewx[498]:   Traceback (most recent call last):
> Mar 18 13:50:27 OpiQ-2 weewx[498]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 332, in generate
> Mar 18 13:50:27 OpiQ-2 weewx[498]:   
> fd.write(str(compiled_template))
> Mar 18 13:50:27 OpiQ-2 weewx[498]: File 
> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1045, in 
> __str__
> Mar 18 13:50:27 OpiQ-2 weewx[498]:   rc = getattr(self, 
> mainMethName)()
> Mar 18 13:50:27 OpiQ-2 weewx[498]: File 
> "_etc_weewx_skins_Weather34_w34charts_chartdata_result_csv_tmpl.py", line 
> 251, in respond
> Mar 18 13:50:27 OpiQ-2 weewx[498]:   TypeError: unsupported operand 
> type(s) for +: 'float' and 'NoneType'
> Mar 18 13:50:27 OpiQ-2 weewx[498]: cheetahgenerator: Generated 3 files for 
> report Weather34Report in 0.70 seconds
> Mar 18 13:50:27 OpiQ-2 weewx[498]: copygenerator: copied 0 files to 
> /var/weewx/reports
>

-- 
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/4e97af33-51b7-4f1a-92ef-0c1731ecf8ab%40googlegroups.com.

[weewx-user] Re: New Weewx/W34 install works OK, but with error msgs

2020-03-18 Thread Bill Arthur

Thanks for the quick response! 

3.9.2   Downloaded and installed last night.


On Wednesday, March 18, 2020 at 1:56:56 PM UTC-5, Bill Arthur wrote:
>
> I just reinstalled Weewx and Weather34. It's working OK, but I get the 
> following error messages. Any idea where the problem lies?
>
> Mar 18 13:50:27 OpiQ-2 weewx[498]: cheetahgenerator: Generate failed with 
> exception ''
> Mar 18 13:50:27 OpiQ-2 weewx[498]: cheetahgenerator:  Ignoring 
> template /etc/weewx/skins/Weather34/w34charts/chartdata/result.csv.tmpl
> Mar 18 13:50:27 OpiQ-2 weewx[498]: cheetahgenerator:  Reason: 
> unsupported operand type(s) for +: 'float' and 'NoneType'
> Mar 18 13:50:27 OpiQ-2 weewx[498]:   Traceback (most recent call last):
> Mar 18 13:50:27 OpiQ-2 weewx[498]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 332, in generate
> Mar 18 13:50:27 OpiQ-2 weewx[498]:   
> fd.write(str(compiled_template))
> Mar 18 13:50:27 OpiQ-2 weewx[498]: File 
> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1045, in 
> __str__
> Mar 18 13:50:27 OpiQ-2 weewx[498]:   rc = getattr(self, 
> mainMethName)()
> Mar 18 13:50:27 OpiQ-2 weewx[498]: File 
> "_etc_weewx_skins_Weather34_w34charts_chartdata_result_csv_tmpl.py", line 
> 251, in respond
> Mar 18 13:50:27 OpiQ-2 weewx[498]:   TypeError: unsupported operand 
> type(s) for +: 'float' and 'NoneType'
> Mar 18 13:50:27 OpiQ-2 weewx[498]: cheetahgenerator: Generated 3 files for 
> report Weather34Report in 0.70 seconds
> Mar 18 13:50:27 OpiQ-2 weewx[498]: copygenerator: copied 0 files to 
> /var/weewx/reports
>

-- 
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/2f63ba12-4ee2-49eb-9f20-210d11056b58%40googlegroups.com.

[weewx-user] New Weewx/W34 install works OK, but with error msgs

2020-03-18 Thread Bill Arthur

I just reinstalled Weewx and Weather34. It's working OK, but I get the 
following error messages. Any idea where the problem lies?

Mar 18 13:50:27 OpiQ-2 weewx[498]: cheetahgenerator: Generate failed with 
exception ''
Mar 18 13:50:27 OpiQ-2 weewx[498]: cheetahgenerator:  Ignoring template 
/etc/weewx/skins/Weather34/w34charts/chartdata/result.csv.tmpl
Mar 18 13:50:27 OpiQ-2 weewx[498]: cheetahgenerator:  Reason: 
unsupported operand type(s) for +: 'float' and 'NoneType'
Mar 18 13:50:27 OpiQ-2 weewx[498]:   Traceback (most recent call last):
Mar 18 13:50:27 OpiQ-2 weewx[498]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 332, in generate
Mar 18 13:50:27 OpiQ-2 weewx[498]:   
fd.write(str(compiled_template))
Mar 18 13:50:27 OpiQ-2 weewx[498]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1045, in 
__str__
Mar 18 13:50:27 OpiQ-2 weewx[498]:   rc = getattr(self, 
mainMethName)()
Mar 18 13:50:27 OpiQ-2 weewx[498]: File 
"_etc_weewx_skins_Weather34_w34charts_chartdata_result_csv_tmpl.py", line 
251, in respond
Mar 18 13:50:27 OpiQ-2 weewx[498]:   TypeError: unsupported operand 
type(s) for +: 'float' and 'NoneType'
Mar 18 13:50:27 OpiQ-2 weewx[498]: cheetahgenerator: Generated 3 files for 
report Weather34Report in 0.70 seconds
Mar 18 13:50:27 OpiQ-2 weewx[498]: copygenerator: copied 0 files to 
/var/weewx/reports

-- 
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/d9dbfe80-19d3-40e6-969f-2e6031e20da9%40googlegroups.com.

[weewx-user] Re: Need help with chron job for Weather34

2020-03-14 Thread Bill Arthur


Thanks !!
My WeeWx is working perfectly on the ramdisk. This should keep my SD card 
healthy. 
Now I'm going to copy & backup the card before I screw it up.



On Friday, March 13, 2020 at 10:16:00 PM UTC-5, Bill Arthur wrote:
>
>
>
> Thanks!  I should have trusted Google more. I was foolishly going through 
> long tutorials that never had what I wanted.
>
>
>
>
> On Friday, March 13, 2020 at 8:34:14 PM UTC-5, Bill Arthur wrote:
>>
>> I'm trying to find a way to execute a function 15 minutes after the RasPi 
>> boots up.
>>
>> I've managed to move Weather34 to a ramdisk, so none of the directories 
>> or files exist until the first loop.   In order for Weather34 to work I 
>> need to chown the jsondata directory just after it has been created.
>>
>> I'm not expereinced at setting up chron jobs and I can't find online info 
>> on how to create a one time event that occurs 15 minutes after boot up.
>>
>> Can someone point me in the right direction?
>>
>> 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-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/594887f7-1066-4ff3-b8da-e8716a95572e%40googlegroups.com.

[weewx-user] Re: Need help with chron job for Weather34



Thanks!  I should have trusted Google more. I was foolishly going through 
long tutorials that never had what I wanted.




On Friday, March 13, 2020 at 8:34:14 PM UTC-5, Bill Arthur wrote:
>
> I'm trying to find a way to execute a function 15 minutes after the RasPi 
> boots up.
>
> I've managed to move Weather34 to a ramdisk, so none of the directories or 
> files exist until the first loop.   In order for Weather34 to work I need 
> to chown the jsondata directory just after it has been created.
>
> I'm not expereinced at setting up chron jobs and I can't find online info 
> on how to create a one time event that occurs 15 minutes after boot up.
>
> Can someone point me in the right direction?
>
> 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-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d612414e-4264-49bb-bfa0-8b7f4e6d7ffa%40googlegroups.com.

[weewx-user] Need help with chron job for Weather34

I'm trying to find a way to execute a function 15 minutes after the RasPi 
boots up.

I've managed to move Weather34 to a ramdisk, so none of the directories or 
files exist until the first loop.   In order for Weather34 to work I need 
to chown the jsondata directory just after it has been created.

I'm not expereinced at setting up chron jobs and I can't find online info 
on how to create a one time event that occurs 15 minutes after boot up.

Can someone point me in the right direction?

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-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8d857263-d38b-4c14-be2a-3c71c0814635%40googlegroups.com.

[weewx-user] Re: Looking for some new hardware

Fine Offset's latest offerings are an excellent choice. They are offered in 
two or three wing models, and are electrically identical. I have several of 
the three wing WH-2900. 
Add a GW-1000 and you'll have an economical setup with excellent 
performance.
I've found the GW-1000 connecting with weewx to be trouble free. The 
GW-1000 includes a barometer and internal temp & humidity.
It's called Ambient WS-2902 in the US and you'll find a lot of help and 
ideas in wxforum.net
Good luck!

On Thursday, March 12, 2020 at 2:53:22 AM UTC-5, Michael Jackson wrote:
>
> I'm looking to upgrade from my Fineoffset WH1081-PC which has shown some 
> issues recently with the fousb connection to both my PC and Raspberry Pi.  
> I am currently running weewx via an SDR and rtl_433, far from optimal as I 
> can't get barometer or internal temperature.
>
> I'd like some cost effective solutions for a replacement with a budget of 
> say NZ$300 (currently ~US$190) that will allow me a reasonably sound 
> connection to a Raspberry Pi4 (4GHz model).
>
> Thanks for any input :-)
>

-- 
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/26a1d011-91ef-4403-843c-e3bcedf24c07%40googlegroups.com.

[weewx-user] Re: Weather34 on ramdisk

As I seemed to be spinning my wheels, I started over with a fresh install. 
This time it works OK.
However I was surprised that this installation now has the Weather34 (php) 
files combined with the weewx (html) files in the /var/weewx/reports 
directory.
All log and webpage files are now going to the ramdisk, this is a 
configuration that I can work with. I'm going to archive and back up this 
configuration.





On Monday, March 9, 2020 at 6:41:50 PM UTC-5, Bill Arthur wrote:
>
> I'm putting together a remote weather station using WeeWx and ARPS radio. 
> It's a bit of a drive so reliability is very important to me. For that 
> reason I've installed the ramdisk according to the WeeWx manual. But I'm 
> having problems because I also want to use Weather34 on my home station.
>
> I installed WeeWx, PHP, Apache and Weather34. Everything is working, the 
> default WeeWx html page and the Weather34 html & PHP page.
>
> Then I installed the ramdisk. I confirmed the path was correct in the 
> weewx and apache configs. The WeeWx default page works great.
> The weather34 files are in the correct location 
> /var/weewx/reports/weather34. I can bring up stationinfo.php and 
> easyW34SkinSetup.php OK.
> But /var/weewx/reports/weather34/index.php has write permission problems. 
> I get:
>
> *Unable to write to the website's folder. Make sure the root of the 
> website is writable by your webserver.*
> *If you're using Apache on linux, Apache should be running as user 
> 'www-data' and group 'www-data'. If so, run these commands or adjust them 
> for Apache's user:group*
> *find . -type d -exec sudo chown www-data:www-data {} \; -exec sudo chmod 
> 2775 {} \;*
> *and*
> *find . -type f -exec sudo chown www-data:www-data {} \; -exec sudo chmod 
> 664 {} \;*
> *from within the root of your website's folder, probably located in 
> '/var/www/example.com/html/pws <http://example.com/html/pws>.'*
> *or, do yourself a huge favor and navigate into your 'html' folder and use 
> these 3 commands to automatically set the permissions on all files and 
> folders created inside it:*
> *chmod g+s .*
> *setfacl -d -m g::rwx .*
> *setfacl -d -m o::rx .*
>
>
>
>
>
>
>
>
>
>
>
> *After trying the first two commands (2775&664) I then got  a sad face and 
> error 500So I rebooted and tried the last three. Done inside the reports 
> folder I got the "Unable to write" screen again.I did the three commands in 
> the weather34 directory and had the same resultsSo I guess I need help 
> getting write premissions correct so that weather34's index.php is 
> happy.then I'm going to need a chron event to apply that to files after 
> they are created, 10 minutes after bootup.Thanks,Bill*
>

-- 
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/b3593f12-2dc3-4ea1-8fec-e95934bf3d7d%40googlegroups.com.

[weewx-user] Re: Weather34 on ramdisk

I don't know if this is relevant, but my Apache error log is spitting this 
out every second:

Tue Mar 10 19:38:25.186962 2020] [core:warn] [pid 465] (99)Cannot assign 
requested address: AH00056: connect to listener on [::]:80


On Tuesday, March 10, 2020 at 7:41:22 PM UTC-5, Bill Arthur wrote:
>
> JD
>
> I did a chown and tested:  error 500
> I did a chgrp and tested: error 500
>
> Bill
>
> On Tuesday, March 10, 2020 at 5:11:30 PM UTC-5, J D wrote:
>>
>> Hi,
>> Here is what I have done on my setup. sudo chown www-data for all files 
>> in Weather34 including Weather34 directory. Then sudo chgrp www-data for 
>> the same set of files and directories. In my case my Weather34 directory 
>> exists in the weewx.
>>
>> On Monday, March 9, 2020 at 4:41:50 PM UTC-7, Bill Arthur wrote:
>>>
>>> I'm putting together a remote weather station using WeeWx and ARPS 
>>> radio. It's a bit of a drive so reliability is very important to me. For 
>>> that reason I've installed the ramdisk according to the WeeWx manual. But 
>>> I'm having problems because I also want to use Weather34 on my home station.
>>>
>>> I installed WeeWx, PHP, Apache and Weather34. Everything is working, the 
>>> default WeeWx html page and the Weather34 html & PHP page.
>>>
>>> Then I installed the ramdisk. I confirmed the path was correct in the 
>>> weewx and apache configs. The WeeWx default page works great.
>>> The weather34 files are in the correct location 
>>> /var/weewx/reports/weather34. I can bring up stationinfo.php and 
>>> easyW34SkinSetup.php OK.
>>> But /var/weewx/reports/weather34/index.php has write permission 
>>> problems. I get:
>>>
>>> *Unable to write to the website's folder. Make sure the root of the 
>>> website is writable by your webserver.*
>>> *If you're using Apache on linux, Apache should be running as user 
>>> 'www-data' and group 'www-data'. If so, run these commands or adjust them 
>>> for Apache's user:group*
>>> *find . -type d -exec sudo chown www-data:www-data {} \; -exec sudo 
>>> chmod 2775 {} \;*
>>> *and*
>>> *find . -type f -exec sudo chown www-data:www-data {} \; -exec sudo 
>>> chmod 664 {} \;*
>>> *from within the root of your website's folder, probably located in 
>>> '/var/www/example.com/html/pws <http://example.com/html/pws>.'*
>>> *or, do yourself a huge favor and navigate into your 'html' folder and 
>>> use these 3 commands to automatically set the permissions on all files and 
>>> folders created inside it:*
>>> *chmod g+s .*
>>> *setfacl -d -m g::rwx .*
>>> *setfacl -d -m o::rx .*
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *After trying the first two commands (2775&664) I then got  a sad face 
>>> and error 500So I rebooted and tried the last three. Done inside 
>>> the reports folder I got the "Unable to write" screen again.I did the three 
>>> commands in the weather34 directory and had the same resultsSo I guess I 
>>> need help getting write premissions correct so that weather34's index.php 
>>> is happy.then I'm going to need a chron event to apply that to files after 
>>> they are created, 10 minutes after bootup.Thanks,Bill*
>>>
>>

-- 
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/6c6d753f-38ea-4c25-a58c-d73ea5ae139b%40googlegroups.com.

[weewx-user] Re: Weather34 on ramdisk

JD

I did a chown and tested:  error 500
I did a chgrp and tested: error 500

Bill

On Tuesday, March 10, 2020 at 5:11:30 PM UTC-5, J D wrote:
>
> Hi,
> Here is what I have done on my setup. sudo chown www-data for all files in 
> Weather34 including Weather34 directory. Then sudo chgrp www-data for the 
> same set of files and directories. In my case my Weather34 directory exists 
> in the weewx.
>
> On Monday, March 9, 2020 at 4:41:50 PM UTC-7, Bill Arthur wrote:
>>
>> I'm putting together a remote weather station using WeeWx and ARPS radio. 
>> It's a bit of a drive so reliability is very important to me. For that 
>> reason I've installed the ramdisk according to the WeeWx manual. But I'm 
>> having problems because I also want to use Weather34 on my home station.
>>
>> I installed WeeWx, PHP, Apache and Weather34. Everything is working, the 
>> default WeeWx html page and the Weather34 html & PHP page.
>>
>> Then I installed the ramdisk. I confirmed the path was correct in the 
>> weewx and apache configs. The WeeWx default page works great.
>> The weather34 files are in the correct location 
>> /var/weewx/reports/weather34. I can bring up stationinfo.php and 
>> easyW34SkinSetup.php OK.
>> But /var/weewx/reports/weather34/index.php has write permission problems. 
>> I get:
>>
>> *Unable to write to the website's folder. Make sure the root of the 
>> website is writable by your webserver.*
>> *If you're using Apache on linux, Apache should be running as user 
>> 'www-data' and group 'www-data'. If so, run these commands or adjust them 
>> for Apache's user:group*
>> *find . -type d -exec sudo chown www-data:www-data {} \; -exec sudo chmod 
>> 2775 {} \;*
>> *and*
>> *find . -type f -exec sudo chown www-data:www-data {} \; -exec sudo chmod 
>> 664 {} \;*
>> *from within the root of your website's folder, probably located in 
>> '/var/www/example.com/html/pws <http://example.com/html/pws>.'*
>> *or, do yourself a huge favor and navigate into your 'html' folder and 
>> use these 3 commands to automatically set the permissions on all files and 
>> folders created inside it:*
>> *chmod g+s .*
>> *setfacl -d -m g::rwx .*
>> *setfacl -d -m o::rx .*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *After trying the first two commands (2775&664) I then got  a sad face 
>> and error 500So I rebooted and tried the last three. Done inside 
>> the reports folder I got the "Unable to write" screen again.I did the three 
>> commands in the weather34 directory and had the same resultsSo I guess I 
>> need help getting write premissions correct so that weather34's index.php 
>> is happy.then I'm going to need a chron event to apply that to files after 
>> they are created, 10 minutes after bootup.Thanks,Bill*
>>
>

-- 
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/1949e8a2-63ba-42b7-a00c-f90775c5dbbf%40googlegroups.com.

Re: [weewx-user] Re: Weather34 on ramdisk

steeple ian,

Previously I could still reach the default weewx html page, now I get:
localhost refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED

I'm going to set the document root back

Bill

On Tuesday, March 10, 2020 at 6:39:47 PM UTC-5, steeple ian wrote:
>
> Try */etc/apache2/sites-available/000-default.conf*
>
> On 10 Mar 2020, at 23:36, Bill Arthur > 
> wrote:
>
> steeple ian,
>
> From /etc/apache2/apache2.conf it appears not to be set.  But it also 
> appears to be using /etc/apache2 for the conf files and /var/log/apache2 
> for the log files.
> Is there somewhere else to look for the answer to your question?
>
> Bill
>
> # ServerRoot: The top of the directory tree under which the server's
> # configuration, error, and log files are kept.
> #
> # NOTE!  If you intend to place this on an NFS (or otherwise network)
> # mounted filesystem then please read the Mutex documentation (available
> # at http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
> # you will save yourself a lot of trouble.
> #
> # Do NOT add a slash at the end of the directory path.
> #
> #ServerRoot "/etc/apache2"
>
> #
> # The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
> #
> #Mutex file:${APACHE_LOCK_DIR} default
>
>
>
> On Tuesday, March 10, 2020 at 6:12:13 PM UTC-5, steeple ian wrote:
>>
>> Bill, 
>> What is your server’s document root?
>
>
> -- 
> 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...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/a2a5a440-8bc1-4f52-b02e-31d06d7edd6f%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/a2a5a440-8bc1-4f52-b02e-31d06d7edd6f%40googlegroups.com?utm_medium=email_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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5b127cee-77b0-4d48-b92b-85f51367fa01%40googlegroups.com.

[weewx-user] Re: Weather34 on ramdisk

JD,

That was the path before I installed the ramdisk. Here is the procedure I 
followed.

https://github.com/weewx/weewx/wiki/Minimize-writes-on-SD-cards

Bill

On Tuesday, March 10, 2020 at 6:34:43 PM UTC-5, J D wrote:
>
> The full path is 
> /var/www/html/weewx/Weather34
>
> the url is 
> http://192.168.0.21:88/weewx/Weather34/?units=us 
> <http://192.168.0.21:88/weewx/weather34/?units=us>
>
> On Monday, March 9, 2020 at 4:41:50 PM UTC-7, Bill Arthur wrote:
>>
>> I'm putting together a remote weather station using WeeWx and ARPS radio. 
>> It's a bit of a drive so reliability is very important to me. For that 
>> reason I've installed the ramdisk according to the WeeWx manual. But I'm 
>> having problems because I also want to use Weather34 on my home station.
>>
>> I installed WeeWx, PHP, Apache and Weather34. Everything is working, the 
>> default WeeWx html page and the Weather34 html & PHP page.
>>
>> Then I installed the ramdisk. I confirmed the path was correct in the 
>> weewx and apache configs. The WeeWx default page works great.
>> The weather34 files are in the correct location 
>> /var/weewx/reports/weather34. I can bring up stationinfo.php and 
>> easyW34SkinSetup.php OK.
>> But /var/weewx/reports/weather34/index.php has write permission problems. 
>> I get:
>>
>> *Unable to write to the website's folder. Make sure the root of the 
>> website is writable by your webserver.*
>> *If you're using Apache on linux, Apache should be running as user 
>> 'www-data' and group 'www-data'. If so, run these commands or adjust them 
>> for Apache's user:group*
>> *find . -type d -exec sudo chown www-data:www-data {} \; -exec sudo chmod 
>> 2775 {} \;*
>> *and*
>> *find . -type f -exec sudo chown www-data:www-data {} \; -exec sudo chmod 
>> 664 {} \;*
>> *from within the root of your website's folder, probably located in 
>> '/var/www/example.com/html/pws <http://example.com/html/pws>.'*
>> *or, do yourself a huge favor and navigate into your 'html' folder and 
>> use these 3 commands to automatically set the permissions on all files and 
>> folders created inside it:*
>> *chmod g+s .*
>> *setfacl -d -m g::rwx .*
>> *setfacl -d -m o::rx .*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *After trying the first two commands (2775&664) I then got  a sad face 
>> and error 500So I rebooted and tried the last three. Done inside 
>> the reports folder I got the "Unable to write" screen again.I did the three 
>> commands in the weather34 directory and had the same resultsSo I guess I 
>> need help getting write premissions correct so that weather34's index.php 
>> is happy.then I'm going to need a chron event to apply that to files after 
>> they are created, 10 minutes after bootup.Thanks,Bill*
>>
>

-- 
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/b9e4a2e2-65cb-4ecd-91b3-1045451ea88c%40googlegroups.com.

[weewx-user] Re: Weather34 on ramdisk

steeple ian

RE-reading, you asked for the document root.

I've gone into /etc/apache2/sites-enabled/000-default.conf and changed the 
document root to /var/weewx/reports.
I'm rebooting and I'll soon see the results

Bill

On Tuesday, March 10, 2020 at 6:36:30 PM UTC-5, Bill Arthur wrote:
>
> steeple ian,
>
> From /etc/apache2/apache2.conf it appears not to be set.  But it also 
> appears to be using /etc/apache2 for the conf files and /var/log/apache2 
> for the log files.
> Is there somewhere else to look for the answer to your question?
>
> Bill
>
> # ServerRoot: The top of the directory tree under which the server's
> # configuration, error, and log files are kept.
> #
> # NOTE!  If you intend to place this on an NFS (or otherwise network)
> # mounted filesystem then please read the Mutex documentation (available
> # at http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
> # you will save yourself a lot of trouble.
> #
> # Do NOT add a slash at the end of the directory path.
> #
> #ServerRoot "/etc/apache2"
>
> #
> # The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
> #
> #Mutex file:${APACHE_LOCK_DIR} default
>
>
>
> On Tuesday, March 10, 2020 at 6:12:13 PM UTC-5, steeple ian wrote:
>>
>> Bill, 
>> What is your server’s document root?
>
>

-- 
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/ca3a11f8-a0ee-4858-8f81-38c180d66179%40googlegroups.com.

[weewx-user] Re: Weather34 on ramdisk

steeple ian,

>From /etc/apache2/apache2.conf it appears not to be set.  But it also 
appears to be using /etc/apache2 for the conf files and /var/log/apache2 
for the log files.
Is there somewhere else to look for the answer to your question?

Bill

# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
#Mutex file:${APACHE_LOCK_DIR} default

On Tuesday, March 10, 2020 at 6:12:13 PM UTC-5, steeple ian wrote:
>
> Bill, 
> What is your server’s document root?

-- 
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/a2a5a440-8bc1-4f52-b02e-31d06d7edd6f%40googlegroups.com.

[weewx-user] Re: Weather34 on ramdisk

I know just enough to be dangerous, so my techniques can be crude. But here 
goes

I chown'd all the files in the weather34 directory to www-data. Did the 
directory itself, also. Then chmod'd them to 644.. Then tried 755 
All attempts ended in error 500

I'm going to read some more and find some other things to try.

Help!




On Monday, March 9, 2020 at 8:25:01 PM UTC-5, Bill Arthur wrote:
>
> JD
>
> I thought that the commands that I did would have done that.
> Do you have any suggestions?
> Thanks!
>
>
> On Monday, March 9, 2020 at 7:12:07 PM UTC-5, J D wrote:
>>
>> Make sure  the Weather34 directory has the correct permissions and 
>> ownership also.
>>
>> On Monday, March 9, 2020 at 4:41:50 PM UTC-7, Bill Arthur wrote:
>>>
>>> I'm putting together a remote weather station using WeeWx and ARPS 
>>> radio. It's a bit of a drive so reliability is very important to me. For 
>>> that reason I've installed the ramdisk according to the WeeWx manual. But 
>>> I'm having problems because I also want to use Weather34 on my home station.
>>>
>>> I installed WeeWx, PHP, Apache and Weather34. Everything is working, the 
>>> default WeeWx html page and the Weather34 html & PHP page.
>>>
>>> Then I installed the ramdisk. I confirmed the path was correct in the 
>>> weewx and apache configs. The WeeWx default page works great.
>>> The weather34 files are in the correct location 
>>> /var/weewx/reports/weather34. I can bring up stationinfo.php and 
>>> easyW34SkinSetup.php OK.
>>> But /var/weewx/reports/weather34/index.php has write permission 
>>> problems. I get:
>>>
>>> *Unable to write to the website's folder. Make sure the root of the 
>>> website is writable by your webserver.*
>>> *If you're using Apache on linux, Apache should be running as user 
>>> 'www-data' and group 'www-data'. If so, run these commands or adjust them 
>>> for Apache's user:group*
>>> *find . -type d -exec sudo chown www-data:www-data {} \; -exec sudo 
>>> chmod 2775 {} \;*
>>> *and*
>>> *find . -type f -exec sudo chown www-data:www-data {} \; -exec sudo 
>>> chmod 664 {} \;*
>>> *from within the root of your website's folder, probably located in 
>>> '/var/www/example.com/html/pws <http://example.com/html/pws>.'*
>>> *or, do yourself a huge favor and navigate into your 'html' folder and 
>>> use these 3 commands to automatically set the permissions on all files and 
>>> folders created inside it:*
>>> *chmod g+s .*
>>> *setfacl -d -m g::rwx .*
>>> *setfacl -d -m o::rx .*
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *After trying the first two commands (2775&664) I then got  a sad face 
>>> and error 500So I rebooted and tried the last three. Done inside 
>>> the reports folder I got the "Unable to write" screen again.I did the three 
>>> commands in the weather34 directory and had the same resultsSo I guess I 
>>> need help getting write premissions correct so that weather34's index.php 
>>> is happy.then I'm going to need a chron event to apply that to files after 
>>> they are created, 10 minutes after bootup.Thanks,Bill*
>>>
>>

-- 
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/4964aacd-0f6a-471a-bb95-f1d4bd0da738%40googlegroups.com.

[weewx-user] Re: Weather34 on ramdisk

2020-03-09 Thread Bill Arthur

JD

I thought that the commands that I did would have done that.
Do you have any suggestions?
Thanks!


On Monday, March 9, 2020 at 7:12:07 PM UTC-5, J D wrote:
>
> Make sure  the Weather34 directory has the correct permissions and 
> ownership also.
>
> On Monday, March 9, 2020 at 4:41:50 PM UTC-7, Bill Arthur wrote:
>>
>> I'm putting together a remote weather station using WeeWx and ARPS radio. 
>> It's a bit of a drive so reliability is very important to me. For that 
>> reason I've installed the ramdisk according to the WeeWx manual. But I'm 
>> having problems because I also want to use Weather34 on my home station.
>>
>> I installed WeeWx, PHP, Apache and Weather34. Everything is working, the 
>> default WeeWx html page and the Weather34 html & PHP page.
>>
>> Then I installed the ramdisk. I confirmed the path was correct in the 
>> weewx and apache configs. The WeeWx default page works great.
>> The weather34 files are in the correct location 
>> /var/weewx/reports/weather34. I can bring up stationinfo.php and 
>> easyW34SkinSetup.php OK.
>> But /var/weewx/reports/weather34/index.php has write permission problems. 
>> I get:
>>
>> *Unable to write to the website's folder. Make sure the root of the 
>> website is writable by your webserver.*
>> *If you're using Apache on linux, Apache should be running as user 
>> 'www-data' and group 'www-data'. If so, run these commands or adjust them 
>> for Apache's user:group*
>> *find . -type d -exec sudo chown www-data:www-data {} \; -exec sudo chmod 
>> 2775 {} \;*
>> *and*
>> *find . -type f -exec sudo chown www-data:www-data {} \; -exec sudo chmod 
>> 664 {} \;*
>> *from within the root of your website's folder, probably located in 
>> '/var/www/example.com/html/pws <http://example.com/html/pws>.'*
>> *or, do yourself a huge favor and navigate into your 'html' folder and 
>> use these 3 commands to automatically set the permissions on all files and 
>> folders created inside it:*
>> *chmod g+s .*
>> *setfacl -d -m g::rwx .*
>> *setfacl -d -m o::rx .*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *After trying the first two commands (2775&664) I then got  a sad face 
>> and error 500So I rebooted and tried the last three. Done inside 
>> the reports folder I got the "Unable to write" screen again.I did the three 
>> commands in the weather34 directory and had the same resultsSo I guess I 
>> need help getting write premissions correct so that weather34's index.php 
>> is happy.then I'm going to need a chron event to apply that to files after 
>> they are created, 10 minutes after bootup.Thanks,Bill*
>>
>

-- 
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/446c9bdd-66b3-4b67-9e47-c7eedab7e998%40googlegroups.com.

[weewx-user] Weather34 on ramdisk

2020-03-09 Thread Bill Arthur

I'm putting together a remote weather station using WeeWx and ARPS radio.
It's a bit of a drive so reliability is very important to me. For that
reason I've installed the ramdisk according to the WeeWx manual. But I'm
having problems because I also want to use Weather34 on my home station.

I installed WeeWx, PHP, Apache and Weather34. Everything is working, the
default WeeWx html page and the Weather34 html & PHP page.

Then I installed the ramdisk. I confirmed the path was correct in the weewx
and apache configs. The WeeWx default page works great.
The weather34 files are in the correct location
/var/weewx/reports/weather34. I can bring up stationinfo.php and
easyW34SkinSetup.php OK.
But /var/weewx/reports/weather34/index.php has write permission problems. I
get:

*Unable to write to the website's folder. Make sure the root of the website
is writable by your webserver.*
*If you're using Apache on linux, Apache should be running as user
'www-data' and group 'www-data'. If so, run these commands or adjust them
for Apache's user:group*
*find . -type d -exec sudo chown www-data:www-data {} \; -exec sudo chmod
2775 {} \;*
*and*
*find . -type f -exec sudo chown www-data:www-data {} \; -exec sudo chmod
664 {} \;*
*from within the root of your website's folder, probably located in
'/var/www/example.com/html/pws.'*
*or, do yourself a huge favor and navigate into your 'html' folder and use
these 3 commands to automatically set the permissions on all files and
folders created inside it:*
*chmod g+s .*
*setfacl -d -m g::rwx .*
*setfacl -d -m o::rx .*

*After trying the first two commands (2775&664) I then got a sad face and
error 500So I rebooted and tried the last three. Done inside the reports
folder I got the "Unable to write" screen again.I did the three commands in
the weather34 directory and had the same resultsSo I guess I need help
getting write premissions correct so that weather34's index.php is
happy.then I'm going to need a chron event to apply that to files after
they are created, 10 minutes after bootup.Thanks,Bill*

--
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/e2cc8f33-64fb-4c47-b0f1-fb8d67f729f9%40googlegroups.com.

[weewx-user] Re: wxnow.txt does not contain precipitation totals

2020-03-02 Thread Bill Arthur

Gary,

Thanks again. Everything is working perfectly. 

BTW, I installed Weewx on a new RasPi.  "binding  = archive" works perfectly

Bill

On Sunday, March 1, 2020 at 9:36:30 PM UTC-6, Bill Arthur wrote:
>
> Gary,
>
> I watched the results after the last rain. The midnight column went to 0.0 
> at midnight and the 24hr went down after 24 hours. Everything as expected.
>
> It has now just started raining and all three columns are at 0.01.
>
> I believe we can say that the problem has been resolved. Thank you for 
> your quick and precise solution.
>
> Bill
>
>
>
>
>
>
> On Saturday, February 29, 2020 at 12:21:26 AM UTC-6, Bill Arthur wrote:
>>
>> Going through the log it looks like I may have restarted the box when I 
>> installed an app. I didn't think I did it that early in the day, but I may 
>> have. I'll take the blame. 
>>
>> Since then it's working flawlessly, the midnight total went away at 
>> 00:00. 
>>
>> I'll know more Monday when it rains. 
>>
>> Bill 
>>
>>
>>
>>
>> On Friday, February 28, 2020 at 8:55:59 PM UTC-6, gjr80 wrote:
>>>
>>> Don’t get too hung up on wxnow.txt, it merely pulls data from the 
>>> database/the current archive record and presents it. If the WeeWX generated 
>>> plot you posted is correct then there is a discrepancy between what WeeWX 
>>> is receiving and what your meteobridge is receiving. This is best tracked 
>>> down by looking at the underlying data.  Once we know the correct data is 
>>> being received/archived by WeeWX we can follow that data through WeeWX. 
>>>
>>> Gary
>>
>>

-- 
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/6d76537c-e086-4fc6-bfa6-6beb163c2801%40googlegroups.com.

[weewx-user] Re: replacement station questions (mostly WS-2902a/WS-2000)

2020-03-01 Thread Bill Arthur

I'd like to help answer some of your questions.

Here's a little back story: I moved to a rural county and decided to build 
my own mesonet. I wish I could afford six Davis stations but I can't. I 
found the WS-2902 to be what I needed. Originally no display console was 
used, just array, ObserverIP and Meteobridge. (I've since added a WS-1900 
display in my home)
The 2902 array is not Davis quality, but is the best available under $250. 
It is well made and spare parts are available.  I now use the Gw1000 
instead of the ObserverIP, it pushes the data to WeeWx

I mount them low to the ground, 5' to 6'. I've had bird problems at one 
site, even with bird spikes. Cleaning bird poo atop a ladder is no fun. The 
rain funnel is twist-lock so it's easy to do on ground level.

Bill

On Thursday, February 27, 2020 at 10:12:37 AM UTC-6, Your Name Here wrote:
>
> So sorry if this should have been found via searches (I tried, for 
> hours!), but I'm exhausted trying to collate these answers into a simple 
> form I can comprehend.
>
> *Questions that relate to WeeWX usage*
>
> Do these models allow for completely offline (no Internet, just intranet 
> (home) access) data extraction for processing by weewx? I have read about 
> the weewx-interceptor <https://github.com/matthewwall/weewx-interceptor> 
> and the listen mode. These two units are not explicitly mentioned 
> (including on the hardware guide <http://weewx.com/docs/hardware.htm> or 
> supported 
> hardware <http://weewx.com/hardware.html> pages).
>
> Does the SD card for the WS-2000 do any continuous collection? 
> If my computer is down, is any data maintained in the console that can be 
> retrieved later? 
> Is it "automatic" the way the Davis data logger would have the last 44 
> hours of data (every minute collection) and my computer would get 
> everything missed to catch up and resume regular collection?
> Or do I have to be aware of it, trigger the export on the console, and 
> move the SD card elsewhere to import it?
> I see it has an archive mode, but I don't understand if that is merely for 
> console display or if it helps achieve what I'm asking.
>
> I have years of data in an MySQL database from a Davis 6152. How cleanly 
> does the data from these go into that database or should I start a new one?
>
> Does the low battery information get exported with the weather data?
>
> *Questions that are not related to WeeWX*
>
> My mount is a 10' mast and my current station is mid-pole. These seem only 
> designed to go on top of a pole (what about something higher than the 
> station for lightning strikes?), do I need to get some side mount extension 
> for these?
> The Davis has the u-bolts opposing each other for a stable mounting and 
> these are oriented facing the same direction. Does that affect the quality 
> of attachment?
> How easy is it to clean out the rain gauge?
> Is the bird spike worth getting?
> Why not position/bend the spikes prior to installation?
>
> Side question: how much of an "issue" is it that the integrated 
> temperature sensor is 5' above the apex of a two story house instead of 5' 
> above ground?
>
> *Background*
>
> I moved into a new house and the wind was significantly more than I was 
> used to. That made me curious about its speed and I bought a cheap LaCrosse 
> WeatherChannel unit from Best Buy. 
>
> That interested me enough to look into getting something better and I got 
> a Davis 6152C for $333 from Ambient Weather (.com) plus the 6510SER for 
> another $139 (+tax + shipping $488). That was May 2007.
>
> The mount is a 10' pole on the apex of a two story house with the station 
> about 5' up so I can reach it and lightning strikes would be several feet 
> above. It was (unfortunately, not currently) grounded to a 6' ground spike 
> put in by the installer to protect his equipment on it (long-range radio 
> for Internet access which has been gone for a decade or so).
>
> In January 2008, a winter electrical storm strike took out the station all 
> the way to the console (but thankfully not the COM port on the WinXP box). 
> Nearly $500 taken out, what would reduce that happening again?
>
> In March 2008 I spent more money to get a 6152 ($400), a new 6510SER 
> ($139), and a 6316 ($139). That's $700 spent just to get conditions at my 
> house versus a web page (or app) showing me a 15+ minutes old, 10º off 
> reading from elsewhere.
>
> That's a lot of money, but I liked it and have been proud of it. Other 
> than a repair to the rain gauge (soldering a complimentary new resistor for 
> the reed switch), it's been working pretty well. Although, the solar panel 
> is rather clouded over and new batteries only last one year (remember to 
> put a f

[weewx-user] Re: wxnow.txt does not contain precipitation totals

2020-03-01 Thread Bill Arthur

Gary,

I watched the results after the last rain. The midnight column went to 0.0 
at midnight and the 24hr went down after 24 hours. Everything as expected.

It has now just started raining and all three columns are at 0.01.

I believe we can say that the problem has been resolved. Thank you for your 
quick and precise solution.

Bill






On Saturday, February 29, 2020 at 12:21:26 AM UTC-6, Bill Arthur wrote:
>
> Going through the log it looks like I may have restarted the box when I 
> installed an app. I didn't think I did it that early in the day, but I may 
> have. I'll take the blame. 
>
> Since then it's working flawlessly, the midnight total went away at 00:00. 
>
> I'll know more Monday when it rains. 
>
> Bill 
>
>
>
>
> On Friday, February 28, 2020 at 8:55:59 PM UTC-6, gjr80 wrote:
>>
>> Don’t get too hung up on wxnow.txt, it merely pulls data from the 
>> database/the current archive record and presents it. If the WeeWX generated 
>> plot you posted is correct then there is a discrepancy between what WeeWX 
>> is receiving and what your meteobridge is receiving. This is best tracked 
>> down by looking at the underlying data.  Once we know the correct data is 
>> being received/archived by WeeWX we can follow that data through WeeWX. 
>>
>> Gary
>
>

-- 
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/fe3eeef8-145d-4abf-b73b-95041bb3da6d%40googlegroups.com.

[weewx-user] Re: wxnow.txt does not contain precipitation totals

Going through the log it looks like I may have restarted the box when I 
installed an app. I didn't think I did it that early in the day, but I may 
have. I'll take the blame. 

Since then it's working flawlessly, the midnight total went away at 00:00. 

I'll know more Monday when it rains. 

Bill 




On Friday, February 28, 2020 at 8:55:59 PM UTC-6, gjr80 wrote:
>
> Don’t get too hung up on wxnow.txt, it merely pulls data from the 
> database/the current archive record and presents it. If the WeeWX generated 
> plot you posted is correct then there is a discrepancy between what WeeWX 
> is receiving and what your meteobridge is receiving. This is best tracked 
> down by looking at the underlying data.  Once we know the correct data is 
> being received/archived by WeeWX we can follow that data through WeeWX. 
>
> Gary

-- 
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/006ca4bf-da22-408c-8a4b-c7acff802a2b%40googlegroups.com.

[weewx-user] Re: wxnow.txt does not contain precipitation totals

Gary,

Oh, what a trip this has been. It seems we keep finding other 
inconsistencies.
For both of our sanity sake I will try to keep on topic. It looks like the 
24 hour data is good. (Not sure why I was calling it 12)

Thanks for suggesting the debug=1 log. I will try to get it going on time. 
I think it'll tell us a lot. (but it looks like cwxn doesn't log any info)

We'll see what Monday brings.

Bill




On Friday, February 28, 2020 at 6:24:38 PM UTC-6, gjr80 wrote:
>
> Bill,
>
> Perhaps this has all been overtaken by your last three posts. But looking 
> at your table of data in the first post that 2 hour gap could easily 
> account for the figures in the table.
>
> I'm not sure what the 2nd plot in your 2nd post shows; since one goes to 
> 0.15 and stays there I am guessing that is your day rainfall meteobridge 
> data on WU. What is the other, 'Prec. Rate' (I think that is what WU calls 
> it)? Again from the meteobridge? If so that is merely rainfall in the last 
> hour so I would expect that to go up and down and unlikely to match the 
> 0.15in. Agree though there appears to be some inconsistency there between 
> WeeWX and meteobridge/WU, but you would need complete WeeWX data and 
> meteobridge/WU data from the same period to track down what is going on. It 
> may create a lot of log chatter but setting debug = 1 just before the rain 
> hits will give you all the raw data that the interceptor driver receives 
> from the GW1000 as well as the parsed data passed from the interceptor 
> driver to WeeWX.
>
> You've mentioned the '12 hour data' a couple of times. What does that 
> refer to? As far as I am aware you have 1 hour data, 24 hours data and day 
> data.
>
> As for the 2 hour odd outage, what is in the WeeWX logs? Rain went from 
> 0.01 to 0.09 so clearly WeeWX was receiving data for at least some art of 
> that period.
>
> Guess we wait for Monday.
>
> Gary
>
> PS. As I understand it the meteobridge obtains its data from the GW1000 
> via the GW1000 API whereas WeeWX obtains its data from the GW1000 
> differently by intercepting HTTP POSTS made by the GW1000. Ideally they 
> should provide the same data but it is possible they do not.
>
> On Saturday, 29 February 2020 08:36:25 UTC+10, Bill Arthur wrote:
>>
>> It looks like the 12 hour data is good. but I don't understand the 1 
>> hour. Rain starts at 15:54 and I would have expected 1hr to track 12hr for 
>> the first hour. 
>> But it looks like we have an unexplained stoppage of data from 16:04 to 
>> 18:08. So I will have to collect data on another day. It should be raining 
>> on Monday.
>> And I' need to find out what caused the two hour outage.
>>
>> Bill
>>
>> On Monday, February 24, 2020 at 6:33:29 PM UTC-6, Bill Arthur wrote:
>>>
>>> I recently added the cwxn extension so that I could pass the weather to 
>>> my APRS/CWOP app
>>>
>>> Its working fairly well, but it only reports the current rain rate. The 
>>> 1hr and 12hr (p and P) are always 000  
>>> We had 1.03" today so I had plenty of opportunities to test. The weewx 
>>> html page shows the rain.
>>>
>>> Here's my example:
>>> Feb 24 2020 18:20
>>> 129/002g004t052r000p000P000h096b10067
>>>
>>> I put "binding = archive"  in  weewx.conf
>>>
>>> I'm missing something here, any ideas?
>>>
>>>

-- 
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/0f1881e7-7f65-4c3c-a325-0d8d01bfc27f%40googlegroups.com.

[weewx-user] Re: wxnow.txt does not contain precipitation totals

It looks like the 12 hour data is good. but I don't understand the 1 hour. 
Rain starts at 15:54 and I would have expected 1hr to track 12hr for the 
first hour. 
But it looks like we have an unexplained stoppage of data from 16:04 to 
18:08. So I will have to collect data on another day. It should be raining 
on Monday.
And I' need to find out what caused the two hour outage.

Bill

On Monday, February 24, 2020 at 6:33:29 PM UTC-6, Bill Arthur wrote:
>
> I recently added the cwxn extension so that I could pass the weather to my 
> APRS/CWOP app
>
> Its working fairly well, but it only reports the current rain rate. The 
> 1hr and 12hr (p and P) are always 000  
> We had 1.03" today so I had plenty of opportunities to test. The weewx 
> html page shows the rain.
>
> Here's my example:
> Feb 24 2020 18:20
> 129/002g004t052r000p000P000h096b10067
>
> I put "binding = archive"  in  weewx.conf
>
> I'm missing something here, any ideas?
>
>

-- 
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/62f39f20-1e8c-4bca-a757-2ed9ecd45c74%40googlegroups.com.

[weewx-user] Re: wxnow.txt does not contain precipitation totals

Some more info:
Weewx saw a total of .10
my meteobridge saw .15 and reported it to wunderground.



On Friday, February 28, 2020 at 12:25:04 PM UTC-6, Bill Arthur wrote:
>
> Gary,
>
> I was happy today as we had a light snowfall this morning; when it melted 
> we had some "rain" to measure. The first hundredth was great. What happened 
> at .02?
>
> Bill
>
> On Thursday, February 27, 2020 at 7:23:39 AM UTC-6, Bill Arthur wrote:
>>
>> Gary,
>>
>> I use nano as editor.   
>> We're supposed to have a good rain here on Monday, so I should be able to 
>> let you know if it solved the problem.
>> I have another RasPi arriving in a few days and will be installing this 
>> on it. Perhaps it will not have the problem.
>> For now I'm staying focused on the 1hr and 12hr problem.
>> Thank you so much for your quick and helpful response.
>>
>> Bill
>>
>> On Thursday, February 27, 2020 at 7:04:03 AM UTC-6, gjr80 wrote:
>>>
>>> Bill,
>>>
>>> Well it is good that it is working as it should. As for binding = 
>>> archive and what is displayed in the log during startup, well the code 
>>> is pretty cut and dry. If binding is set to archive it should be displaying 
>>> archive, so that suggests that whilst it looks like binding = archive 
>>> there may be some other invisible characters in there that are interfering. 
>>> What editor do you use to edit weewx.conf, is it a proper text or code 
>>> editor?
>>>
>>> I guess it is up to you if you want to look at this any further, when I 
>>> see things that are working for the wrong reason I like to look closer as 
>>> you don't know what else might be being masked by a potential issue. If you 
>>> do want to look any further the next thing I would do would be post a 
>>> wee_debug 
>>> report <http://weewx.com/docs/utilities.htm#wee_debug_utility>, that 
>>> will give us a clear picture of your config (which we haven't seen yet). If 
>>> you do post a wee_debug report do check it for sensitive info such as 
>>> user names, passwords, API keys etc before posting, wee_debug does a 
>>> good job at obfuscating these things but it is not perfect.
>>>
>>> Gary
>>>
>>> On Thursday, 27 February 2020 13:17:01 UTC+10, Bill Arthur wrote:
>>>>
>>>> Gary,
>>>>
>>>> Almost 24 hours later  cwxn 0.5a is chugging along. It's outputting 
>>>> wxnow.txt every five minutes. I'm good with that.
>>>> Maybe cwxn binding is actually set for archive but it's just not 
>>>> displaying properly in the log. Output at exactly five minutes makes me 
>>>> think it is.
>>>>
>>>> Now we just need some rain.
>>>>
>>>> Bill
>>>>
>>>> On Wednesday, February 26, 2020 at 12:15:44 AM UTC-6, Bill Arthur wrote:
>>>>>
>>>>>
>>>>> Instead of spinning my wheels over binding=archive, I updated 
>>>>> cwxn.py.  It seems to be working fine. Syslog reports version 0.5a and 
>>>>> "binding is loop"  Wxnow.txt is updating and new data is making it to 
>>>>> findu
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tuesday, February 25, 2020 at 10:50:30 PM UTC-6, Bill Arthur wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> One more thing...
>>>>>> The original problem was that when I had added binding=archive my 
>>>>>> output was static for a day. Now, I have binding=archive in weewx.conf 
>>>>>> and 
>>>>>> my output is updating regularly.. But we seem to have a different 
>>>>>> problem 
>>>>>> now, with binding=archive not showing up in the syslog.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tuesday, February 25, 2020 at 10:20:13 PM UTC-6, Bill Arthur wrote:
>>>>>>>
>>>>>>> I've configured it (after stopping) with binding=archive in 
>>>>>>> /etc/weewx/weewx.conf.. saved. viewed to confirm. restarted. syslog 
>>>>>>> says 
>>>>>>> binding=loop. rebooted. same results. 
>>>>>>> stopped weewx. deleted line.saved. viewed to confirm. restarted. 
>>>>>>> read syslog. syslog says binding=loop. stopped. set binding=archive. 
&

[weewx-user] Re: wxnow.txt does not contain precipitation totals