[weewx-user] Re: v3.6.0 - WMR 300 - WeeWxIOError: [Errno 110]
Please, find attached versions and log as required. Thank you. On Sunday, October 9, 2016 at 12:02:58 AM UTC+2, mwall wrote: > > On Saturday, October 8, 2016 at 5:23:07 PM UTC-4, Miguel Iniesta wrote: >> >> The log attached has been obtained with debug = 1. >>> >>> >>> > ok, lets go back a step. which versions do you have for pyusb and libusb? > > dpkg -l | grep libusb > dpkg -l | grep python-usb > > then try this: > > cd /home/weewx > sudo PYTHONPATH=bin python bin/weewx/drivers/wmr300.py > > and post the log. > > this will load the driver and attempt to capture loop packets, with > debug_comm and debug_counts enabled. it should help us figure out where > the timeout exception is coming from. > > i suspect that the problem is the encapsulation/naming of a usb error. it > also appears that ubuntu 16.x is missing bus.dirname and dev.filename like > recent centos. > > 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. dpkg -l |grep libusb ii libgusb2:i386 0.2.9-0ubuntu1 i386 GLib wrapper around libusb1 ii libusb-0.1-4:i386 2:0.1.12-28 i386 userspace USB programming library ii libusb-1.0-0:i386 2:1.0.20-1 i386 userspace USB programming library ii libusbmuxd4:i386 1.0.10-2ubuntu0.1 i386 USB multiplexor daemon for iPhone and iPod Touch devices - library ls /usr/local/lib/python2.7/dist-packages Cheetah Markdown-2.6.6.dist-info pysub usb Cheetah-2.4.4.dist-info PIL pysub-0.2.egg-info markdown Pillow-3.3.1.dist-infopyusb-1.0.0.dist-info /home/weewx$ sudo PYTHONPATH=bin python bin/weewx/drivers/wmr300.py Traceback (most recent call last): File "bin/weewx/drivers/wmr300.py", line 1388, in for packet in stn.genLoopPackets(): File "bin/weewx/drivers/wmr300.py", line 841, in genLoopPackets raise weewx.WeeWxIOError(e) weewx.WeeWxIOError: [Errno 110] Operation timed out
[weewx-user] Re: v3.6.0 - WMR 300 - WeeWxIOError: [Errno 110]
Python-usb was not installed because Weewx has been installed using the tool setup py Afer install it, the version is: ii python-usb 1.0.0~b2-2 On Sunday, October 9, 2016 at 11:25:54 AM UTC+2, Miguel Iniesta wrote: > > Please, find attached versions and log as required. > > Thank you. > > On Sunday, October 9, 2016 at 12:02:58 AM UTC+2, mwall wrote: >> >> On Saturday, October 8, 2016 at 5:23:07 PM UTC-4, Miguel Iniesta wrote: >>> >>> The log attached has been obtained with debug = 1. >> ok, lets go back a step. which versions do you have for pyusb and libusb? >> >> dpkg -l | grep libusb >> dpkg -l | grep python-usb >> >> then try this: >> >> cd /home/weewx >> sudo PYTHONPATH=bin python bin/weewx/drivers/wmr300.py >> >> and post the log. >> >> this will load the driver and attempt to capture loop packets, with >> debug_comm and debug_counts enabled. it should help us figure out where >> the timeout exception is coming from. >> >> i suspect that the problem is the encapsulation/naming of a usb error. >> it also appears that ubuntu 16.x is missing bus.dirname and dev.filename >> like recent centos. >> >> 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: weewx with OS LW301 and interceptor driver
On Sunday, October 9, 2016 at 2:12:51 AM UTC-4, Sam Roza wrote: > > So, while it started working and that was great-we figured out how to get > all that lw301 data into weewx (yay!)-this issue with the unsupported > operand crops up often, and once it does that, I don't seem to be able to > properly restart weewx using systemctl. > > sam, please install the latest interceptor - it includes a fix for the unsupported operand (conversion of the 'uv' value) as well as a proper shutdown of the sockserver. 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: v3.6.0 - WMR 300 - WeeWxIOError: [Errno 110]
On Sunday, October 9, 2016 at 6:03:30 AM UTC-4, Miguel Iniesta wrote: > > Python-usb was not installed because Weewx has been installed using the > tool setup py > Afer install it, the version is: > > ii python-usb 1.0.0~b2-2 >> >> >>> thank you miguel. please install the attached 0.13rc1 mv bin/weewx/drivers/wmr300.py bin/weewx/drivers/wmr300-0.12.py cp ~/Downloads/wmr300-0.13rc1.py bin/weewx/drivers/wmr300.py then start weewx and post the log. v0.13 adds retries to the usb read/write methods, and it is more selective about usb error propagation. 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. #!/usr/bin/env python # Copyright 2015 Matthew Wall # See the file LICENSE.txt for your rights. # # Credits: # Thanks to Benji for the identification and decoding of 7 packet types # # Thanks to Eric G for posting USB captures and providing hardware for testing # https://groups.google.com/forum/#!topic/weewx-development/5R1ahy2NFsk # # Thanks to Zahlii # https://bsweather.myworkbook.de/category/weather-software/ # # No thanks to oregon scientific - repeated requests for hardware and/or # specifications resulted in no response at all. # TODO: battery level for each sensor # TODO: signal strength for each sensor # TODO: altitude # TODO: archive interval """Driver for Oregon Scientific WMR300 weather stations. Sensor data transmission frequencies: wind: 2.5 to 3 seconds TH: 10 to 12 seconds rain: 20 to 24 seconds The station supports 1 wind, 1 rain, 1 UV, and up to 8 temperature/humidity sensors. Sniffing USB traffic shows all communication is interrupt. The endpoint descriptors for the device show this as well. Response timing is 1. The station ships with "Weather OS PRO" software for windows. This was used for the USB sniffing. Internal observation names use the convention name_with_specifier. These are mapped to the wview or other schema as needed with a configuration setting. For example, for the wview schema, wind_speed maps to windSpeed, temperature_0 maps to inTemp, and humidity_1 maps to outHumidity. Message types - packet types from station: 57 - station type/model; history count 41 - ACK D2 - history; 128 bytes D3 - temperature/humidity/dewpoint; 61 bytes D4 - wind; 54 bytes D5 - rain; 40 bytes D6 - pressure; 46 bytes DB - forecast; 32 bytes DC - temperature/humidity ranges; 62 bytes packet types from host: A6 - heartbeat 41 - ACK 65 - ? each of these is ack-ed by the station cd - ? start history request? last two bytes are one after most recent read 35 - ? finish history request? last two bytes are latest record count 72 - ? 73 - ? notes: WOP sends A6 message every 20 seconds WOP requests history at startup, then again every 120 minutes each A6 is followed by a 57 from the station each data packet D* from the station is followed by an ack packet 41 from host D2 (history) records are recorded every minute D6 (pressure) packets seem to come every 15 minutes (900 seconds) 4,5 of 7x match 12,13 of 57 Message field decodings --- Values are stored in 1 to 3 bytes in big endian order. Negative numbers are stored as Two's Complement (if the first byte starts with F it is a negative number). no data: 7f ff values for channel number: 0 - console sensor 1 - sensor 1 2 - sensor 2 ... 8 - sensor 8 values for trend: 0 - steady 1 - rising 2 - falling bitwise transformation for compass direction: 1000 = NNW 0100 = NW 0010 = WNW 0001 = W 1000 = WSW 0100 = SW 0010 = SSW 0001 = S 1000 = SSE 0100 = SE 0010 = ESE 0001 = E 1000 = ENE 0100 = NE 0010 = NNE 0001 = N values for forecast: 0x08 - cloudy 0x0c - rainy 0x1e - partly cloudy 0x0e - partly cloudy at night 0x70 - sunny 0x00 - clear night Message decodings - message: ACK byte hex dec description decoded value 0 41 A acknowledgement ACK 1 43 C 2 4b K 3 73 4 e5 5 0a 6 26 7 0e 8 c1 examples: 41 43 4b 73 e5 0a 26 0e c1 41 43 4b 65 19 e5 04 message: station info byte hex dec description decoded value 0 57 W station typeWMR300 1 4d M 2 52 R 3 33 3 4 30 0 5 30 0 6 2c , 7 41 A station model A002 8 30 0 9 30 0 10 32 2 11 2c , 12 0e 13 c1 14 00 15 00 16 2c , 17 67 lastest history record
[weewx-user] Re: weewx with OS LW301 and interceptor driver
On Sunday, October 9, 2016 at 4:11:39 AM UTC-7, mwall wrote: > > > > On Sunday, October 9, 2016 at 2:12:51 AM UTC-4, Sam Roza wrote: >> >> So, while it started working and that was great-we figured out how to get >> all that lw301 data into weewx (yay!)-this issue with the unsupported >> operand crops up often, and once it does that, I don't seem to be able to >> properly restart weewx using systemctl. >> >> > sam, > > please install the latest interceptor - it includes a fix for the > unsupported operand (conversion of the 'uv' value) as well as a proper > shutdown of the sockserver. > > m > Sorry, didn't see that. 12 dropped. I will get, that loaded... I've had it sucvcessfully collecting data for about an hour, now. It's publishing to Wunderground and CWOP, too. So all is well! Note that I needed to make a change to the capture script in order for it to work without barfing 20 minutes of data at once, and that was the '-u' flag on the sed command: ~~~ #!/bin/sh ngrep -l -q -d eth0 '0004a369e0d6' | sed -u '/mac=/!d' | xargs -n 1 curl http://localhost: -s -d ~~~ Thanks for all the great assistance! I'm happy to have a reporting weatherstation, again. -Sam -- 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: v3.6.0 - WMR 300 - WeeWxIOError: [Errno 110]
Please, fin log attached. Thank you. On Sunday, October 9, 2016 at 3:55:13 PM UTC+2, mwall wrote: > > On Sunday, October 9, 2016 at 6:03:30 AM UTC-4, Miguel Iniesta wrote: >> >> Python-usb was not installed because Weewx has been installed using the >> tool setup py >> Afer install it, the version is: >> >> ii python-usb 1.0.0~b2-2 >>> >>> > thank you miguel. > > please install the attached 0.13rc1 > > mv bin/weewx/drivers/wmr300.py bin/weewx/drivers/wmr300-0.12.py > cp ~/Downloads/wmr300-0.13rc1.py bin/weewx/drivers/wmr300.py > > then start weewx and post the log. > > v0.13 adds retries to the usb read/write methods, and it is more selective > about usb error propagation. > > 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. 201610091721-syslog-env Description: Binary data
[weewx-user] Changing Apache WAN port- HTTP security?
Is it a good idea to change the default port for the Weewx server on my Pi from 80 to something else that's not so common? I'd like to be able to access my weather station feed over from WAN but am hesitant to just port forward my Pi's IP address out into the wild on port 80. I have a password set for the Pi login already. On top of that, if it's HTTP, is the login password being sent in plain text over the connection? Do I understand that correctly? If somebody was snooping wouldn't they see it? It's becoming increasingly worrisome all of these internet of things (IoT) devices are lacking decent security, so I've been focused on securing my IP camera's, NAS boxes, etc, lately. My understanding of how my Weewx on my Pi is: Weewx running as a daemon (service/background process). Apache2 is the web server so a user can access the Weewx service (daemon) from a browser on LAN/WAN (if port forwarded). - Apache2 runs in the background and is the "gatekeeper" to the services that request a browser-based information request. - Services get access *through *the Apache server to the destination port it's assigned to. In Weewx's case it's "/weewx". BUT, if the port to Apache is 80, and that directs to Weewx, then how would I set up multiple WAN access, say if I had a webcam service running on the same Pi? Hope *some *of that made some sense... -- 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: Changing Apache WAN port- HTTP security?
The first thing you need to grasp is that your web server is NOT part of weewx!! Weewx will put your webpages wherever you tell it to - on the same machine or a remote machine. The web server and it's permissions and access are outside the realms of weewx!! You can either have weewx PUT the generated pages WITHIN your web server page hierarchy - or you can leave the pages in /home/weewx/public_html and direct your web server to access them at that location (by using a symlink or similar). You can run apache or lighttpd on the same machine as weewx, on a separate machine on your local network, or even hosted at a remote web hosting site - the choice is yours!! All that weewx needs to know is where to build the pages, and where to transfer them to if necessary. Access to the generated pages is under the control of the web server - a server for which you are the administrator or a remotely hosted server - the choice is yours. On Sunday, 9 October 2016 20:10:00 UTC+3, Tim Phillips wrote: > Is it a good idea to change the default port for the Weewx server on my Pi > from 80 to something else that's not so common? I'd like to be able to > access my weather station feed over from WAN but am hesitant to just port > forward my Pi's IP address out into the wild on port 80. I have a password > set for the Pi login already. On top of that, if it's HTTP, is the login > password being sent in plain text over the connection? Do I understand that > correctly? If somebody was snooping wouldn't they see it? > > It's becoming increasingly worrisome all of these internet of things (IoT) > devices are lacking decent security, so I've been focused on securing my IP > camera's, NAS boxes, etc, lately. > > My understanding of how my Weewx on my Pi is: > > Weewx running as a daemon (service/background process). > Apache2 is the web server so a user can access the Weewx service (daemon) > from a browser on LAN/WAN (if port forwarded). > - Apache2 runs in the background and is the "gatekeeper" to the > services that request a browser-based information request. > - Services get access *through *the Apache server to the > destination port it's assigned to. In Weewx's case it's "/weewx". > > BUT, if the port to Apache is 80, and that directs to Weewx, then how > would I set up multiple WAN access, say if I had a webcam service running > on the same Pi? > > Hope *some *of that made some sense... > > > > -- 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: Changing Apache WAN port- HTTP security?
Thank you for the help. I'm running Apache on my Pi that's on 24/7. So any changes I wish to make to the WAN access will solely be through Apache's setup, if I understand your response correctly. I have Weewx send the weather data to the weewx stations map as well as Weather Underground. The weewx stations URL I used directs to the Weather Underground site, so I'm not directing the public to my Pi address... On Sunday, October 9, 2016 at 10:23:45 AM UTC-7, Andrew Milner wrote: > > The first thing you need to grasp is that your web server is NOT part of > weewx!! > > Weewx will put your webpages wherever you tell it to - on the same machine > or a remote machine. > > The web server and it's permissions and access are outside the realms of > weewx!! > > You can either have weewx PUT the generated pages WITHIN your web server > page hierarchy - or you can leave the pages in /home/weewx/public_html and > direct your web server to access them at that location (by using a symlink > or similar). > > You can run apache or lighttpd on the same machine as weewx, on a separate > machine on your local network, or even hosted at a remote web hosting site > - the choice is yours!! > > All that weewx needs to know is where to build the pages, and where to > transfer them to if necessary. > > Access to the generated pages is under the control of the web server - a > server for which you are the administrator or a remotely hosted server - > the choice is yours. > > > > > > On Sunday, 9 October 2016 20:10:00 UTC+3, Tim Phillips wrote: > >> Is it a good idea to change the default port for the Weewx server on my >> Pi from 80 to something else that's not so common? I'd like to be able to >> access my weather station feed over from WAN but am hesitant to just port >> forward my Pi's IP address out into the wild on port 80. I have a password >> set for the Pi login already. On top of that, if it's HTTP, is the login >> password being sent in plain text over the connection? Do I understand that >> correctly? If somebody was snooping wouldn't they see it? >> >> It's becoming increasingly worrisome all of these internet of things >> (IoT) devices are lacking decent security, so I've been focused on securing >> my IP camera's, NAS boxes, etc, lately. >> >> My understanding of how my Weewx on my Pi is: >> >> Weewx running as a daemon (service/background process). >> Apache2 is the web server so a user can access the Weewx service (daemon) >> from a browser on LAN/WAN (if port forwarded). >> - Apache2 runs in the background and is the "gatekeeper" to the >> services that request a browser-based information request. >> - Services get access *through *the Apache server to the >> destination port it's assigned to. In Weewx's case it's "/weewx". >> >> BUT, if the port to Apache is 80, and that directs to Weewx, then how >> would I set up multiple WAN access, say if I had a webcam service running >> on the same Pi? >> >> Hope *some *of that made some sense... >> >> >> >> -- 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: Changing Apache WAN port- HTTP security?
It's up to you entirely! There is more to website security than the port being used. A true hacker will likely test all port numbers anyway if trying to obtain access. Weewx is ignorant about your WAN, WAN access, and your web server - it just puts your data where you tell it to. On Sunday, 9 October 2016 20:34:04 UTC+3, Tim Phillips wrote: > Thank you for the help. > > I'm running Apache on my Pi that's on 24/7. So any changes I wish to make > to the WAN access will solely be through Apache's setup, if I understand > your response correctly. > > I have Weewx send the weather data to the weewx stations map as well as > Weather Underground. The weewx stations URL I used directs to the Weather > Underground site, so I'm not directing the public to my Pi address... > > > On Sunday, October 9, 2016 at 10:23:45 AM UTC-7, Andrew Milner wrote: >> >> The first thing you need to grasp is that your web server is NOT part of >> weewx!! >> >> Weewx will put your webpages wherever you tell it to - on the same >> machine or a remote machine. >> >> The web server and it's permissions and access are outside the realms of >> weewx!! >> >> You can either have weewx PUT the generated pages WITHIN your web server >> page hierarchy - or you can leave the pages in /home/weewx/public_html and >> direct your web server to access them at that location (by using a symlink >> or similar). >> >> You can run apache or lighttpd on the same machine as weewx, on a >> separate machine on your local network, or even hosted at a remote web >> hosting site - the choice is yours!! >> >> All that weewx needs to know is where to build the pages, and where to >> transfer them to if necessary. >> >> Access to the generated pages is under the control of the web server - a >> server for which you are the administrator or a remotely hosted server - >> the choice is yours. >> >> >> >> >> >> On Sunday, 9 October 2016 20:10:00 UTC+3, Tim Phillips wrote: >> >>> Is it a good idea to change the default port for the Weewx server on my >>> Pi from 80 to something else that's not so common? I'd like to be able to >>> access my weather station feed over from WAN but am hesitant to just port >>> forward my Pi's IP address out into the wild on port 80. I have a password >>> set for the Pi login already. On top of that, if it's HTTP, is the login >>> password being sent in plain text over the connection? Do I understand that >>> correctly? If somebody was snooping wouldn't they see it? >>> >>> It's becoming increasingly worrisome all of these internet of things >>> (IoT) devices are lacking decent security, so I've been focused on securing >>> my IP camera's, NAS boxes, etc, lately. >>> >>> My understanding of how my Weewx on my Pi is: >>> >>> Weewx running as a daemon (service/background process). >>> Apache2 is the web server so a user can access the Weewx service >>> (daemon) from a browser on LAN/WAN (if port forwarded). >>> - Apache2 runs in the background and is the "gatekeeper" to the >>> services that request a browser-based information request. >>> - Services get access *through *the Apache server to the >>> destination port it's assigned to. In Weewx's case it's "/weewx". >>> >>> BUT, if the port to Apache is 80, and that directs to Weewx, then how >>> would I set up multiple WAN access, say if I had a webcam service running >>> on the same Pi? >>> >>> Hope *some *of that made some sense... >>> >>> >>> >>> -- 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: Changing Apache WAN port- HTTP security?
On Sunday, October 9, 2016 at 10:10:00 AM UTC-7, Tim Phillips wrote: > > My understanding of how my Weewx on my Pi is: > > Weewx running as a daemon (service/background process). > almost certainly yes > Apache2 is the web server so a user can access the Weewx service (daemon) > from a browser on LAN/WAN (if port forwarded). > no. Apache does not talk to the weewx daemon at all. It listens on the port(s) you have it configured to listen on, commonly http (tcp/80), and makes available whatever data or programs apache is configured to permit (typically, just a document tree). Sometimes your web pages are executable (php typically) but most times not. Initially it's set up to just return data. The default weewx output from the default skins is just datahtml files and image files. Other skins might have executable php content (saratoga templates to name one). Again, the apache configuration must be set up to permit php files to execute, and there is additional software you'd install to do that. There are a lot of apache-related packages. - Apache2 runs in the background and is the "gatekeeper" to the > services that request a browser-based information request. > not really. It's a daemon that listens on the port(s) it is configured for, and does what it's configured to do based on the apache config file(s). Again, usually it just provides a way to read files using a remote web browser kind of interface, from a well-defined directory on the filesystem. - Services get access *through *the Apache server to the > destination port it's assigned to. In Weewx's case it's "/weewx". > > no. Apache makes some files (in locations defined by the apache config files) on the pi accessible via http or https, assuming those files are accessible by the non-privileged account the apache daemon runs as. > BUT, if the port to Apache is 80, and that directs to Weewx, then how > would I set up multiple WAN access, say if I had a webcam service running > on the same Pi? > > Again, apache doesn't really 'direct' to weewx, it can make weewx-generated output files available, if weewx puts it in a place apache is configured to know about, and if the files are set with the right permissions so the apache daemon can read them. You would configure the webcam to accept incoming requests on another port typically, hopefully over https with a strong non-default password required to see the files. This seems to be what most of the IoT break-ins seem to be exploitingfolks who just go shields-down in a insecure vendor-default configuration. I'm not quite sure what you're asking about WAN vs. LAN access, but if you're a typical home user you likely have your LAN behind a gateway device that blocks all incoming WAN access, unless you forward particular ports through your firewall. Be very careful here. If you're asking the types of questions you're asking, I'd suggest doing it right might be a little above your understanding/expertise at this point in time. By far the safest thing to do is to permit 'no' incoming traffic WAN=>LAN even through port forwarding. -- 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] Glitch in new report_timing feature?
This feature is pretty exciting for me, as I had to hack up a way to post my reports to github every 10 minutes so I don't overrun my update quota (I host my site on github pages, and I have an archive period of 60 seconds, which got me shut off for pushing too frequently once). The report_timing feature is perfect because I can now update my reports locally at my house on the minute interval and still push to github every 10 minutes. The problem: The archive interval isn't exactly 60 seconds, and sometimes a minute is skipped. I wondered what would happen if the minute I'm supposed to push is skipped, so I waited until it happened and saw that it did not push during that 10 minute interval. I read in the documentation that if the archive period and the report_timing don't match, the report will run at the next scheduled interval. But that does not seem to be the case if the interval is 1 minute. Other than reverting back to the hacky way I've been doing it, is there a workaround? -- 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] Best practices for wind calculations
Now that i've got my homebrew station installed and working, I'd like to clear up some of my confusion about how wind speeds and directions are calculated. Can anyone point me to some authoritative information.In particular I would like to answer: 1. Is there a standard period for averaging wind speeds? I found one document that said 3 seconds sampled every 1/4 second and averaged. 2. Are averages supposed to be scalar or vector (i.e., taking wind direction into account)? 3. Does a 0 wind speed have a direction? 4. My cup anemometer puts out a sine wave with a frequency proportional to wind speed. The frequency ranges from about 0.7Hz to 60Hz. Such low frequencies are often measured using reciprocal counting (i.e., measure the period). Are there preferred techniques or algorithms for doing that? A simple technique just counts the number of zero-crossing (tick's) per measurement period, but that is only approximately correct. 5. What is a gust? One very unhelpful definition I saw was the highest "instantaneous" measurement. Is that right, or does it need to last for a certain period of time? 6. What is the gust direction? If a gust really is an instantaneous sample, then given the momentum of the gauge the direction corresponding to that gust probably is lagging. Thank you for any help. -- 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: v3.6.0 - WMR 300 - WeeWxIOError: [Errno 110]
miguel, did you have the wmr300 station working with a previous version of weewx, or on different hardware? or is this your first time to use the wmr300 with weewx? please change line 986 in wmr300.py v0.13rc1 from this: self.timeout = 100 to this: self.timeout = 3000 then try running weewx again. 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: Glitch in new report_timing feature?
For what it's worth, I might be seeing the same issue but I have mine set to 300 seconds (5 minutes) and it's updating every 10 minutes- sometimes it misses and does 20. I think I read somewhere that if you change the update interval you need to redo the config setup? Maybe I'm hallucinating... On Sunday, October 9, 2016 at 12:54:19 PM UTC-7, Jarom Hatch wrote: > > This feature is pretty exciting for me, as I had to hack up a way to post > my reports to github every 10 minutes so I don't overrun my update quota (I > host my site on github pages, and I have an archive period of 60 seconds, > which got me shut off for pushing too frequently once). The report_timing > feature is perfect because I can now update my reports locally at my house > on the minute interval and still push to github every 10 minutes. > > The problem: The archive interval isn't exactly 60 seconds, and sometimes > a minute is skipped. I wondered what would happen if the minute I'm > supposed to push is skipped, so I waited until it happened and saw that it > did not push during that 10 minute interval. I read in the documentation > that if the archive period and the report_timing don't match, the report > will run at the next scheduled interval. But that does not seem to be the > case if the interval is 1 minute. > > Other than reverting back to the hacky way I've been doing it, is there a > workaround? > -- 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] New extension for generating APRS-compliant weather packets
Hi everybody, I wrote a small extension that generates APRS-compliant weather packets so that I can send them out via aprx. The extension is available https://github.com/cavedon/weewx-aprs in case someone else finds that useful. Feedback/suggestions are welcome, Ludovico K6LUD -- 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: Changing Apache WAN port- HTTP security?
So I've totally misinterpreted what Apache does for the weewx serviceI'm super new to this so I'm sorry you need to explain these things like this. My WAN/IP education is limited to setting up a handful of foscam's on WAN manually as well as doing a RPi webcam project (RPi-Cam-Interface) which worked well. I ALWAYS set a custom password on my stuff and change the username if possible. Actually, I decided to use my RPi as a weather station server because the Acurite "bridge" accessory gave no indication of how their security works, which I disliked. So I took it as an opportunity to learn all about it, hopefully via this project as a starting point. I was not keen on just plugging in their bridge accessory to my router and thinking that's A-OK. I appreciate the clarification! On Sunday, October 9, 2016 at 12:28:56 PM UTC-7, vince wrote: > > On Sunday, October 9, 2016 at 10:10:00 AM UTC-7, Tim Phillips wrote: >> >> My understanding of how my Weewx on my Pi is: >> >> Weewx running as a daemon (service/background process). >> > > almost certainly yes > > >> Apache2 is the web server so a user can access the Weewx service (daemon) >> from a browser on LAN/WAN (if port forwarded). >> > > no. Apache does not talk to the weewx daemon at all. > > It listens on the port(s) you have it configured to listen on, commonly > http (tcp/80), and makes available whatever data or programs apache is > configured to permit (typically, just a document tree). Sometimes your web > pages are executable (php typically) but most times not. Initially it's set > up to just return data. > > The default weewx output from the default skins is just datahtml files > and image files. Other skins might have executable php content (saratoga > templates to name one). Again, the apache configuration must be set up to > permit php files to execute, and there is additional software you'd install > to do that. There are a lot of apache-related packages. > > > - Apache2 runs in the background and is the "gatekeeper" to the >> services that request a browser-based information request. >> > > not really. It's a daemon that listens on the port(s) it is configured > for, and does what it's configured to do based on the apache config > file(s). Again, usually it just provides a way to read files using a > remote web browser kind of interface, from a well-defined directory on the > filesystem. > > - Services get access *through *the Apache server to the >> destination port it's assigned to. In Weewx's case it's "/weewx". >> >> > no. Apache makes some files (in locations defined by the apache config > files) on the pi accessible via http or https, assuming those files are > accessible by the non-privileged account the apache daemon runs as. > > >> BUT, if the port to Apache is 80, and that directs to Weewx, then how >> would I set up multiple WAN access, say if I had a webcam service running >> on the same Pi? >> >> > Again, apache doesn't really 'direct' to weewx, it can make > weewx-generated output files available, if weewx puts it in a place apache > is configured to know about, and if the files are set with the right > permissions so the apache daemon can read them. > > You would configure the webcam to accept incoming requests on another port > typically, hopefully over https with a strong non-default password required > to see the files. This seems to be what most of the IoT break-ins seem to > be exploitingfolks who just go shields-down in a insecure > vendor-default configuration. > > I'm not quite sure what you're asking about WAN vs. LAN access, but if > you're a typical home user you likely have your LAN behind a gateway device > that blocks all incoming WAN access, unless you forward particular ports > through your firewall. > > Be very careful here. If you're asking the types of questions you're > asking, I'd suggest doing it right might be a little above your > understanding/expertise at this point in time. By far the safest thing to > do is to permit 'no' incoming traffic WAN=>LAN even through port forwarding. > > > > -- 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] WMR 200 Calibrate Barometer
Hello i want to use StdCalibrate at the config file to Calibrate the Barometer. I have 1 hPa to much. But i not understand what i must to enter . I Try pressure, barometer, and altimeter. pressure = pressure - 1 Only pressure do anything but false it comes to 9xx hPa (from 1026) Thank you for your Help. -- 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: WMR 200 Calibrate Barometer
Or must i set that to Software ? This section controls the origin of derived values. [StdWXCalculate] # Derived quantities are calculated by this service. Possible values are: # hardware- use the value provided by hardware # software- use the value calculated by weewx # prefer_hardware - use value provide by hardware if available, # otherwise use value calculated by weewx pressure = prefer_hardware barometer = prefer_hardware altimeter = prefer_hardware windchill = prefer_hardware heatindex = prefer_hardware dewpoint = prefer_hardware inDewpoint = prefer_hardware rainRate = prefer_hardware -- 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: WMR 200 Calibrate Barometer
On Sunday, October 9, 2016 at 8:31:25 PM UTC-4, Markus Roth wrote: > > Hello > > i want to use StdCalibrate at the config file to Calibrate the Barometer. > I have 1 hPa to much. > > But i not understand what i must to enter . > > I Try pressure, barometer, and altimeter. > > pressure = pressure - 1 > > Only pressure do anything but false it comes to 9xx hPa (from 1026) > markus, the units in StdCalibrate must be in the unit system specified in StdConvert assuming that your StdConvert.target_unit=US (the default), you want this: pressure = pressure - 0.029529 since 1 inHg is equal to 33.863 hPa also, you must be sure that you specify an independent variable. in the case of WMR200, the station reports pressure, and barometer and altimeter are derived. so modifying pressure is the correct calibration. 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: WMR 200 Calibrate Barometer
Thank you. Yes i have the default US. Im Germany that was the Problem. But to cange it from the default gave only Problems by the support. Therefore I do not change it. Gave it not the https://en.wikipedia.org/wiki/International_System_of_Units ? When it gave it for the Weather units then it was better to use it in the next new version of weewx. Only an improvement idea. Am Montag, 10. Oktober 2016 02:46:05 UTC+2 schrieb mwall: > > On Sunday, October 9, 2016 at 8:31:25 PM UTC-4, Markus Roth wrote: >> >> Hello >> >> i want to use StdCalibrate at the config file to Calibrate the Barometer. >> I have 1 hPa to much. >> >> But i not understand what i must to enter . >> >> I Try pressure, barometer, and altimeter. >> >> pressure = pressure - 1 >> >> Only pressure do anything but false it comes to 9xx hPa (from 1026) >> > > markus, > > the units in StdCalibrate must be in the unit system specified in > StdConvert > > assuming that your StdConvert.target_unit=US (the default), you want this: > > pressure = pressure - 0.029529 > > since 1 inHg is equal to 33.863 hPa > > also, you must be sure that you specify an independent variable. in the > case of WMR200, the station reports pressure, and barometer and altimeter > are derived. so modifying pressure is the correct calibration. > > 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: Changing Apache WAN port- HTTP security?
This tells you how the bridge works: http://moderntoil.com/?p=794 It would appear to me that the bridge has no real need for security as such since it only transmits data to acurite web site from your weather station using POST commands. It's security is controlled by your own router, and it would only respond to incoming data when it switched to update mode to update its firmware. On Monday, 10 October 2016 02:28:39 UTC+3, Tim Phillips wrote: > So I've totally misinterpreted what Apache does for the weewx > serviceI'm super new to this so I'm sorry you need to explain these > things like this. My WAN/IP education is limited to setting up a handful of > foscam's on WAN manually as well as doing a RPi webcam project > (RPi-Cam-Interface) which worked well. > > I ALWAYS set a custom password on my stuff and change the username if > possible. Actually, I decided to use my RPi as a weather station server > because the Acurite "bridge" accessory gave no indication of how their > security works, which I disliked. So I took it as an opportunity to learn > all about it, hopefully via this project as a starting point. I was not > keen on just plugging in their bridge accessory to my router and thinking > that's A-OK. > > > I appreciate the clarification! > > > > On Sunday, October 9, 2016 at 12:28:56 PM UTC-7, vince wrote: >> >> On Sunday, October 9, 2016 at 10:10:00 AM UTC-7, Tim Phillips wrote: >>> >>> My understanding of how my Weewx on my Pi is: >>> >>> Weewx running as a daemon (service/background process). >>> >> >> almost certainly yes >> >> >>> Apache2 is the web server so a user can access the Weewx service >>> (daemon) from a browser on LAN/WAN (if port forwarded). >>> >> >> no. Apache does not talk to the weewx daemon at all. >> >> It listens on the port(s) you have it configured to listen on, commonly >> http (tcp/80), and makes available whatever data or programs apache is >> configured to permit (typically, just a document tree). Sometimes your web >> pages are executable (php typically) but most times not. Initially it's set >> up to just return data. >> >> The default weewx output from the default skins is just datahtml >> files and image files. Other skins might have executable php content >> (saratoga templates to name one). Again, the apache configuration must be >> set up to permit php files to execute, and there is additional software >> you'd install to do that. There are a lot of apache-related packages. >> >> >> - Apache2 runs in the background and is the "gatekeeper" to the >>> services that request a browser-based information request. >>> >> >> not really. It's a daemon that listens on the port(s) it is configured >> for, and does what it's configured to do based on the apache config >> file(s). Again, usually it just provides a way to read files using a >> remote web browser kind of interface, from a well-defined directory on the >> filesystem. >> >> - Services get access *through *the Apache server to the >>> destination port it's assigned to. In Weewx's case it's "/weewx". >>> >>> >> no. Apache makes some files (in locations defined by the apache config >> files) on the pi accessible via http or https, assuming those files are >> accessible by the non-privileged account the apache daemon runs as. >> >> >>> BUT, if the port to Apache is 80, and that directs to Weewx, then how >>> would I set up multiple WAN access, say if I had a webcam service running >>> on the same Pi? >>> >>> >> Again, apache doesn't really 'direct' to weewx, it can make >> weewx-generated output files available, if weewx puts it in a place apache >> is configured to know about, and if the files are set with the right >> permissions so the apache daemon can read them. >> >> You would configure the webcam to accept incoming requests on another >> port typically, hopefully over https with a strong non-default password >> required to see the files. This seems to be what most of the IoT break-ins >> seem to be exploitingfolks who just go shields-down in a insecure >> vendor-default configuration. >> >> I'm not quite sure what you're asking about WAN vs. LAN access, but if >> you're a typical home user you likely have your LAN behind a gateway device >> that blocks all incoming WAN access, unless you forward particular ports >> through your firewall. >> >> Be very careful here. If you're asking the types of questions you're >> asking, I'd suggest doing it right might be a little above your >> understanding/expertise at this point in time. By far the safest thing to >> do is to permit 'no' incoming traffic WAN=>LAN even through port forwarding. >> >> >> >> -- 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.
Re: [weewx-user] Re: Changing Apache WAN port- HTTP security?
An excellent read. I wish they would market the device better to people like me (us?) that require web security. I might have bought their product. Might still, in fact, after reading that. It's important to take some caution to adding and trusting IoT devices. On Oct 9, 2016 6:42 PM, "Andrew Milner" wrote: > This tells you how the bridge works: > http://moderntoil.com/?p=794 > > It would appear to me that the bridge has no real need for security as > such since it only transmits data to acurite web site from your weather > station using POST commands. It's security is controlled by your own > router, and it would only respond to incoming data when it switched to > update mode to update its firmware. > > > > On Monday, 10 October 2016 02:28:39 UTC+3, Tim Phillips wrote: > >> So I've totally misinterpreted what Apache does for the weewx >> serviceI'm super new to this so I'm sorry you need to explain these >> things like this. My WAN/IP education is limited to setting up a handful of >> foscam's on WAN manually as well as doing a RPi webcam project >> (RPi-Cam-Interface) which worked well. >> >> I ALWAYS set a custom password on my stuff and change the username if >> possible. Actually, I decided to use my RPi as a weather station server >> because the Acurite "bridge" accessory gave no indication of how their >> security works, which I disliked. So I took it as an opportunity to learn >> all about it, hopefully via this project as a starting point. I was not >> keen on just plugging in their bridge accessory to my router and thinking >> that's A-OK. >> >> >> I appreciate the clarification! >> >> >> >> On Sunday, October 9, 2016 at 12:28:56 PM UTC-7, vince wrote: >>> >>> On Sunday, October 9, 2016 at 10:10:00 AM UTC-7, Tim Phillips wrote: My understanding of how my Weewx on my Pi is: Weewx running as a daemon (service/background process). >>> >>> almost certainly yes >>> >>> Apache2 is the web server so a user can access the Weewx service (daemon) from a browser on LAN/WAN (if port forwarded). >>> >>> no. Apache does not talk to the weewx daemon at all. >>> >>> It listens on the port(s) you have it configured to listen on, commonly >>> http (tcp/80), and makes available whatever data or programs apache is >>> configured to permit (typically, just a document tree). Sometimes your web >>> pages are executable (php typically) but most times not. Initially it's set >>> up to just return data. >>> >>> The default weewx output from the default skins is just datahtml >>> files and image files. Other skins might have executable php content >>> (saratoga templates to name one). Again, the apache configuration must be >>> set up to permit php files to execute, and there is additional software >>> you'd install to do that. There are a lot of apache-related packages. >>> >>> >>> - Apache2 runs in the background and is the "gatekeeper" to the services that request a browser-based information request. >>> >>> not really. It's a daemon that listens on the port(s) it is configured >>> for, and does what it's configured to do based on the apache config >>> file(s). Again, usually it just provides a way to read files using a >>> remote web browser kind of interface, from a well-defined directory on the >>> filesystem. >>> >>> - Services get access *through *the Apache server to the destination port it's assigned to. In Weewx's case it's "/weewx". >>> no. Apache makes some files (in locations defined by the apache config >>> files) on the pi accessible via http or https, assuming those files are >>> accessible by the non-privileged account the apache daemon runs as. >>> >>> BUT, if the port to Apache is 80, and that directs to Weewx, then how would I set up multiple WAN access, say if I had a webcam service running on the same Pi? >>> Again, apache doesn't really 'direct' to weewx, it can make >>> weewx-generated output files available, if weewx puts it in a place apache >>> is configured to know about, and if the files are set with the right >>> permissions so the apache daemon can read them. >>> >>> You would configure the webcam to accept incoming requests on another >>> port typically, hopefully over https with a strong non-default password >>> required to see the files. This seems to be what most of the IoT break-ins >>> seem to be exploitingfolks who just go shields-down in a insecure >>> vendor-default configuration. >>> >>> I'm not quite sure what you're asking about WAN vs. LAN access, but if >>> you're a typical home user you likely have your LAN behind a gateway device >>> that blocks all incoming WAN access, unless you forward particular ports >>> through your firewall. >>> >>> Be very careful here. If you're asking the types of questions you're >>> asking, I'd suggest doing it right might be a little above your >>> understanding/expertise at this point in time. By far the safest
[weewx-user] Re: Glitch in new report_timing feature?
Jarom and Tim, I will see if I can work out what is going on but will need a little more info. Could you please provide copies of the [StdReport] and [StdArchive] sections of weewx.conf. A log extract would help too, if you could set debug=1 in weewx.conf then stop/start weewx and post the log. I would like to see the weewx startup and if you see the anomalous behaviour, an extract covering a couple of report cycles before the anomalous behaviour until a couple of report cycles after the behaviour would be good. Somewhat under the weather today so it may take a day or 2 for me to get back to you. 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. For more options, visit https://groups.google.com/d/optout.
