[weewx-user] Exfoliation Forcast Issue

[Dave Spicer]

I am running the Exfoliation skin and I have added the exfoliation 
forecast. Everything is working but the forecast is not showing. I have 
verified that MySQL has the forecast data. I have enabled the Forecast page 
but nothing shows. I have reviewed the syslog and there are no errors. 

I am running weewx on a Raspberry Pi and used the setup.py install 
instructions. 

Does anyone have any idea on what I need to do to get the forecast working? 
I would like to see if on the Current page and also on the Forecast page

Thanks
Dave

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: interceptor sniff mode 'challenge'

[mwall]

On Tuesday, November 6, 2018 at 9:59:37 PM UTC-5, Tolip Wen wrote:
>
>
> Output from nekkid run of interceptor.py
> -
> root@H370:/home/weewx# PYTHONPATH=bin python bin/user/interceptor.py 
> --device=observer --mode=sniff --iface=tap1 --filter="src 10.10.100.3 and 
> dst port 8099"   
> Traceback (most recent call last):
>   File "bin/user/interceptor.py", line 2124, in 
> address=options.addr, port=options.port)
>   File "bin/user/interceptor.py", line 932, in __init__
> Observer.Parser(), handler=Observer.Handler, **stn_dict)
>   File "bin/user/interceptor.py", line 278, in __init__
> iface, pcap_filter, promiscuous)
>   File "bin/user/interceptor.py", line 307, in __init__
> self.packet_sniffer = pcap.pcapObject()
> AttributeError: 'module' object has no attribute 'pcapObject'
>

apparently there are two different pcap implementations for python.

https://stackoverflow.com/questions/2501138/module-object-has-no-attribute-pcapobject

they are pypcap:

https://pypi.org/project/pypcap/

and pylibpcap:

https://sourceforge.net/projects/pylibpcap/

one of them has a pcapObject attribute, the other does not.  they both 
import as pcap.

this came up at least once before, so if you want to hack the interceptor 
code a bit to make it work with either pcap implementation, a merge request 
would be quite welcome :)

btw, there is a weewx-sdr driver that will take the output from rtl_433.  
works great with those $20 usb sdr dongles.

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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] interceptor sniff mode 'challenge'

['Tolip Wen' via weewx-user]

THANKS for WeeWX and interceptor!!!

I have Interceptor working with a WS-1400-IP(WS2600) in listen mode.
When I change to sniff mode it fails to run.
Low priority, I have something that works! (but I want to use sniff mode 
because yaddayaddayadda)

A snippet from working weewx.conf below shows an example suggesting I have 
the config correct.
-
# The driver to use:
driver = user.interceptor

# Specify the hardware device to capture.  Options include:
#   acurite-bridge - acurite internet bridge
#   observer - fine offset WH2600/HP1000/HP1003, aka 'observer'
#   lw30x - oregon scientific LW301/LW302
#   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
device_type = observer

###mode = sniff
###iface = eth0
###pcap_filter = src 10.10.100.72 and dst port 80 
#.72 is the WS-1400-IP
#   the above intended to work with iptables '-tee'

###mode = sniff
###iface = eth0
###pcap_filter = src 10.10.100.3 and dst port 8099
#.3 is DD-WRT router
#the above is intended to work with iptables '-mangle' and that 
should work with sniff or listen mode
---END of snippet---

Output from nekkid run of interceptor.py
-
root@H370:/home/weewx# PYTHONPATH=bin python bin/user/interceptor.py 
--device=observer --mode=sniff --iface=tap1 --filter="src 10.10.100.3 and 
dst port 8099"   
Traceback (most recent call last):
  File "bin/user/interceptor.py", line 2124, in 
address=options.addr, port=options.port)
  File "bin/user/interceptor.py", line 932, in __init__
Observer.Parser(), handler=Observer.Handler, **stn_dict)
  File "bin/user/interceptor.py", line 278, in __init__
iface, pcap_filter, promiscuous)
  File "bin/user/interceptor.py", line 307, in __init__
self.packet_sniffer = pcap.pcapObject()
AttributeError: 'module' object has no attribute 'pcapObject'
---END of output from interceptor.py---

I gaggled and ducked for solutions without much luck.
Found a few results involving 'pcapObject', I applied some suggestions with 
hammer and did not change results in positive way.
I'm running Slackware 14.2-->upgraded to current as of OCT 1st
I'm running linux-4.19 kernel
Python 2.7 installed
weewx-3.8.2

I tried many combinations of --iface(eth0,br0,tap[x]) and --filter.
I tried many flavors of iptables rules. (nat -mangle and/or -tee)

I obviously 'think' I know what I'm doing with everything except the python 
troubleshooting.
My kernel is configured by me, in support of that tidbit, everything else 
network related works 'as advertised' :)
I verified firewall(DD-WRT) rules by running wireshark on host running 
weewx.
I verified firewall(DD-WRT) rules by running wireshark on host running 
weewx.
I can produce the expected layer 2 and/or 3 packets to the host running 
WeeWX.
It may have nothing to do with WeeWX, I have discovered other "features" 
running Slackware (since '95).
(I'm not a py newb but brain query returns "that data is stale and the 
buffer got flushed, reloading")
I'm willing to run tests and post results.
I don't lack direction but I lack the direction for quick sucessful self 
help in this instance.
I'm open to suggestions for things to try including upgrading or 
downgrading modules and/or patching interceptor.py
I 1/2 suspect a dumb attack on my part.
:)

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Interceptor sniff 'challenge', and an idea for a future tangent using RTL-SDR (in your spare time!)

['Tolip Wen' via weewx-user]

THANKS for WeeWX and interceptor!!!

I have Interceptor working with a WS-1400-IP(WS2600) in listen mode.
When I change to sniff mode it fails to run.
Low priority, I have something that works! (but I want to use sniff mode 
because yaddayaddayadda)

A snippet from weewx.conf below shows an example of the many things I have 
tried.
-
# The driver to use:
driver = user.interceptor

# Specify the hardware device to capture.  Options include:
#   acurite-bridge - acurite internet bridge
#   observer - fine offset WH2600/HP1000/HP1003, aka 'observer'
#   lw30x - oregon scientific LW301/LW302
#   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
device_type = observer
port = 8099
###mode = sniff
###iface = eth0
###pcap_filter = src 10.10.100.72 and dst port 80
---END of snippet---

Output from raw run of interceptor.py
-
root@H370:/home/weewx# PYTHONPATH=bin python bin/user/interceptor.py 
--device=observer --mode=sniff --iface=tap1 --filter="src 10.10.100.3 and 
dst port 8099"   
Traceback (most recent call last):
  File "bin/user/interceptor.py", line 2124, in 
address=options.addr, port=options.port)
  File "bin/user/interceptor.py", line 932, in __init__
Observer.Parser(), handler=Observer.Handler, **stn_dict)
  File "bin/user/interceptor.py", line 278, in __init__
iface, pcap_filter, promiscuous)
  File "bin/user/interceptor.py", line 307, in __init__
self.packet_sniffer = pcap.pcapObject()
AttributeError: 'module' object has no attribute 'pcapObject'
---END of output from interceptor.py---

I gaggled and ducked for solutions without much luck.
Few results involving 'pcapObject', I applied suggestions with hammer and 
did not change results in positive way.
I'm running Slackware 14.2-->upgraded to current as of OCT 1st
I'm running linux-4.19 kernel
Python 2.7 installed
weewx-3.8.2

I tried many combinations of --iface (eth0,br0,tap[x])and --filter (depends 
on how I set iptables on non host router on same LAN segment)
I tried many flavors of iptables rules. (nat -mangle and/or -tee)
I comment out "port = 8099" when I try to sniff with WeeWX BTW.

I obviously 'think' I know what I'm doing with everything except the python 
troubleshooting.
My kernel is hand configured by me, in support of that tidbit, everything 
else network related works 'as advertised' :)
I verified firewall(DD-WRT) rules by running wireshark on host running 
weewx.
I verified firewall(DD-WRT) rules by running wireshark on host running 
weewx.
I can produce the expected layer 2 and/or 3 packets to the host running 
WeeWX.
It may have nothing to do with WeeWX, I have discovered other "features" 
running Slackware (since '95).
I'm open to suggestions for things to try including upgrading or 
downgrading modules and/or patching interceptor.py
(I'm not a py newb but brain query returns "that data is stale and the 
buffer got flushed, reloading")
I'm willing to run tests and post results.
I don't lack direction but I lack the direction for quick sucessful self 
help in this instance.
:)



Now for my tangent idea in 2 parts:

Part1;
A US$20.00 USB RTL-SDR and a PC running rtl_433 can decode packets from a 
433 or 915 MHz weatherstation.
There are also ethernet flavors of SDR but they are NOT U$20.00 a copy.
There are already rtl_433 modules written for a few weatherstation sensors 
to produce output that looks similar to weewx in the foreground.

A partial list of answers to the question "WHY?".
  An RTL_SDR has flexible antenna options potentially extending range a 
long way.
  WeeWX users could POTENTIALLY mix and match a variety of sensors from 
other vendors.
  Any PC and an SDR could allow to use neighbors sensors for free! (or work 
as backup/etc)
  (For example I have a 915MHz WS2600 but I also have a bunch of 433MHz 
temperature/humidity sensors.)
  An SDR might/could also function as a LIGHTNING and/or Solar storm 
detector.
  Some strange netizen thinks it's a good idea!

That project is located
https://github.com/merbanan/rtl_433


Part2;
You have demonstrated posession of details on lots of output from lots of 
different WX sensors.
The folks @ rtl_433 claim to want that type of data to add/fix things.

Their solicitation for data is in the following document
https://github.com/merbanan/rtl_433/blob/master/README.md
That leads to
https://groups.google.com/forum/#!forum/rtl_433

They might have answers you might seek.
They definately could use help with formatting of recieved WX data.
rtl_433 captures the W2600 RF packets but fails to format and output all 
data contained within because they are ignorant of what is there.
If you have condensed sensor format info, you could contribute what you 
have and help expand the list of supported sensor*s.*

If you do contribute to that 

Re: [weewx-user] Rsync error

[Maginos]

Thank you mwall for your tip, it helped me too. For your information, the 
path of the ssh_config file was for me /etc/ssh/ssh_config.

Best regards and thank you again!
Maginos

Am Samstag, 1. September 2018 15:29:22 UTC+2 schrieb mwall:
>
> you should also specify the user in the ssh config file:
>
> Host rsyncserver.com
>   User jens
>   IdentityFile /home/jens/.ssh/id_rsa
>
> in the world of ssh, the user is independent of the ssh certificates.  so 
> it is usually a good idea to specify user just to be safe.
>
> for example, you might be 'jens' on the computer on which weewx is 
> running, but jensjorgen on the rsync server.  in that case you would 
> specify 'User jensjorgen' in the ssh config file.
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Raspberry kernels later than 4.4 hang when running weewx.

[Ruben Navarro Huedo]

for me it has been very stable  

El martes, 6 de noviembre de 2018, 7:59:53 (UTC+1), Alberto Sánchez 
escribió:
>
> I am testing with kernel 4.4.50, the last Cameron's driver and weewx 3.8.2.
>
> I will inform if i have problems or not. 
>
> Thanks for your support Cameron. 
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Multiple errors in weewx 3.8.2

[Jonis Maurin Ceará]

Yes, logs from fresh install yesterday.


Nov  5 10:02:31 SkyWeather weewx[30084]: engine: Initializing weewx version
>> 3.8.2
>
> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: Using Python 2.7.13
>> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
>
> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: Platform
>> Linux-4.14.71-v7+-armv7l-with-debian-9.4
>
> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: Locale is 'en_GB.UTF-8'
>
> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: pid file is
>> /var/run/weewx.pid
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Using configuration file
>> /etc/weewx/weewx.conf
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Loading station type
>> Simulator (weewx.drivers.simulator)
>
> Nov  5 10:02:31 SkyWeather weewx[30073]: Starting weewx weather system:
>> weewx.
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: StdConvert target unit is
>> 0x1
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: wxcalculate: The following values
>> will be calculated: barometer=prefer_hardware, windchill=prefer_hardware,
>> dewpoint=prefer_hardware, appTemp=prefer_hardware,
>> rainRate=prefer_hardware, windrun=prefer_hardware,
>> heatindex=prefer_hardware, maxSolarRad=prefer_hardware,
>> humidex=prefer_hardware, pressure=prefer_hardware,
>> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware,
>> cloudbase=prefer_hardware
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: wxcalculate: The following
>> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Archive will use data
>> binding wx_binding
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Record generation will be
>> attempted in 'hardware'
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Using archive interval of
>> 300 seconds (specified in weewx configuration)
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: manager: Created and initialized
>> table 'archive' in database 'weewx.sdb'
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: manager: Created daily summary
>> tables
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Using binding
>> 'wx_binding' to database 'weewx.sdb'
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: manager: Starting backfill of
>> daily summaries
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: restx: StationRegistry:
>> Registration not requested.
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: restx: Wunderground: Posting not
>> enabled.
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: restx: PWSweather: Posting not
>> enabled.
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: restx: CWOP: Posting not enabled.
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: restx: WOW: Posting not enabled.
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: restx: AWEKAS: Posting not
>> enabled.
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Starting up weewx version
>> 3.8.2
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Clock error is -0.30
>> seconds (positive is fast)
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Starting main packet loop.
>
> Nov  5 10:05:16 SkyWeather weewx[30088]: manager: Added record 2018-11-05
>> 10:05:00 -02 (1541419500) to database 'weewx.sdb'
>
> Nov  5 10:05:16 SkyWeather weewx[30088]: manager: Added record 2018-11-05
>> 10:05:00 -02 (1541419500) to daily summary in 'weewx.sdb'
>
> Nov  5 10:05:19 SkyWeather weewx[30088]: cheetahgenerator: Generate failed
>> with exception ''
>
> Nov  5 10:05:19 SkyWeather weewx[30088]: cheetahgenerator:  Ignoring
>> template /etc/weewx/skins/Standard/week.html.tmpl
>
> Nov  5 10:05:19 SkyWeather weewx[30088]: cheetahgenerator:  Reason: no
>> such column: wind
>
> Nov  5 10:05:19 SkyWeather weewx[30088]:   Traceback (most recent call
>> last):
>
> Nov  5 10:05:19 SkyWeather weewx[30088]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in generate
>
> Nov  5 10:05:19 SkyWeather weewx[30088]:   print >> _file,
>> compiled_template
>
> Nov  5 10:05:19 SkyWeather weewx[30088]: File
>> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in
>> __str__
>
> Nov  5 10:05:19 SkyWeather weewx[30088]:   rc = getattr(self,
>> mainMethName)()
>
> Nov  5 10:05:19 SkyWeather weewx[30088]: File
>> "_etc_weewx_skins_Standard_week_html_tmpl.py", line 949, in respond
>
> Nov  5 10:05:19 SkyWeather weewx[30088]: File
>> "_etc_weewx_skins_Standard_week_html_tmpl.py", line 245, in __errorCatcher26
>
> Nov  5 10:05:19 SkyWeather weewx[30088]: File "", line 1,
>> in 
>
> Nov  5 10:05:19 SkyWeather weewx[30088]: File
>> "/usr/share/weewx/weewx/tags.py", line 329, in __getattr__
>
> Nov  5 10:05:19 SkyWeather weewx[30088]:   return
>> self._do_query(aggregate_type)
>
> Nov  5 10:05:19 SkyWeather weewx[30088]: File
>> "/usr/share/weewx/weewx/tags.py", line 343, in _do_query
>
> Nov  5 10:05:19 SkyWeather weewx[30088]:   val=val,
>> **self.option_dict)
>
> 

[weewx-user] Re: Android weather app for weeWx users

[weerman]

Am Dienstag, 6. November 2018 02:13:36 UTC+1 schrieb John Smith:
>
> On Tuesday, 6 November 2018 09:57:13 UTC+11, weerman wrote:
>>
>> Using the latest version 0.512 here. 
>>> Edit: Missed the url: https://weatherfrog80.bplaced.net/weewx/ 
>>> 
>>>  
>>>
>>
> I'm using the same version and used the url:
>
> https://weatherfrog80.bplaced.net/weewx/inigo-settings.txt
>
> and there was no problem
>


Hi John,

Yes, it works now. After i wrote my last post, i tried another approach in 
removing the leading /www folder for the url of the data file and this 
works. 
My provider has a leading /www folder which is a non public folder, before 
the public folders so i had to remove the "www" to get it working.  

-- 
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.
For more options, visit https://groups.google.com/d/optout.