[weewx-user] Re: WS-1001 connection to Raspberry PI for Weewx
That appears the be the problem. Using 192.168.255.255 and it found the correct address for the station. Now it's updating the database. Should take awhile. Thanks On Thursday, August 1, 2019 at 12:38:54 AM UTC-4, Bill Volz wrote: > > I did change the network mask from 255.255.255.0 to 255.255.0.0. Should I > use a broadcast mask of 192.168.255.255 for HP1000? > > On Wednesday, July 31, 2019 at 11:01:59 PM UTC-4, Susan Mackay wrote: >> >> Have you changed any settings on the router? What I'm thinking is that it >> is not letting through the broadcast packets. >> If that is the case, then all I can suggest in the short term is to do >> what I suggested in my first post and edit the Python code to simply try to >> connect directly to the IP address. >> (I'll add that to the "wishlist' for the next version of the driver, just >> after making sure that it works with Python 3 and the latest WeeWx code! Of >> course that is all after 'getting some time for all this playing'!) >> Susan >> > -- 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/5a96a058-ff0e-405c-bdaa-159da2e42437%40googlegroups.com.
[weewx-user] Re: WS-1001 connection to Raspberry PI for Weewx
I did change the network mask from 255.255.255.0 to 255.255.0.0. Should I use a broadcast mask of 192.168.255.255 for HP1000? On Wednesday, July 31, 2019 at 11:01:59 PM UTC-4, Susan Mackay wrote: > > Have you changed any settings on the router? What I'm thinking is that it > is not letting through the broadcast packets. > If that is the case, then all I can suggest in the short term is to do > what I suggested in my first post and edit the Python code to simply try to > connect directly to the IP address. > (I'll add that to the "wishlist' for the next version of the driver, just > after making sure that it works with Python 3 and the latest WeeWx code! Of > course that is all after 'getting some time for all this playing'!) > Susan > -- 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/9612ba7b-a6bb-4702-98aa-c487dc9d59c4%40googlegroups.com.
[weewx-user] Re: WS-1001 connection to Raspberry PI for Weewx
I uninstalled and reinstalled weewx, along with interceptor, crt and HP1000. Here's the section in the weewx.conf file with comments removed. [HP1000] ip_address_mask = "192.168.0.255" retry_count = 5 socket_timeout = 5 loop_delay = 15 max_retry = 3 retry_wait = 5 driver = user.HP1000 The section from user.log: The ws-1001 is at static IP addr 192.168.0.197. Pinging that addr shows something is there. Jul 31 12:01:02 raspberrypi weewx[24848]: engine: Using configuration file /etc/weewx/weewx.conf Jul 31 12:01:02 raspberrypi weewx[24848]: engine: Loading station type HP1000 (user.HP1000) Jul 31 12:01:02 raspberrypi weewx[24848]: HP1000: HP1000 Starting Jul 31 12:01:02 raspberrypi weewx[24848]: HP1000: Using user-defined broadcast mask - 192.168.0.255 Jul 31 12:01:02 raspberrypi weewx[24848]: HP1000: Address Mask = 192.168.0.255 Jul 31 12:01:02 raspberrypi weewx[24848]: HP1000: Retry count = 5.00 Jul 31 12:01:02 raspberrypi weewx[24848]: HP1000: Socket timeout = 5.00 Jul 31 12:01:02 raspberrypi weewx[24848]: HP1000: Loop delay = 15.00 Jul 31 12:01:02 raspberrypi weewx[24848]: HP1000: Retry Wait = 5.00 Jul 31 12:01:02 raspberrypi weewx[24848]: HP1000: Max Retry = 3.00 Jul 31 12:01:02 raspberrypi weewx[24848]: engine: StdConvert target unit is 0x1 Later I get this in the user.log file: Jul 31 12:01:27 raspberrypi weewx[24848]: HP1000: Timed out too many times That repeats. what to fix now? Thanks On Monday, July 29, 2019 at 10:47:49 PM UTC-4, Susan Mackay wrote: > > In the weewx.conf file, you can uncomment the 'ip_address_mask' line and > set it to whatever is the correct address mask for your network. > The HP1000 code must be running on a computer that is on the same network > sub-net as the weather console. Setting the 'ip_address_mask' overrides the > automatic selection of the computers IP address as the default. > Failing that,if you know Python, then go into the HP1000.py code and > remove the stat of the 'connectToWeatherStation' function and set > 'self.ws_socket' to be an open connection to the remote IP address. > Susan > > On Tuesday, July 30, 2019 at 4:55:44 AM UTC+10, Bill Volz wrote: >> >> I had this working for 2 years but it stopped Saturday. I got it working >> 2 years ago and don't quite recall what I did. I think I used EasyWeatherIP >> to change web page in the setup page from "www.wunderground.com' to >> 'www.***.com". Now when I try to change it with EWIP, it doesn't make the >> change - it has made other changes. Not sure if there is a trick. I've >> tried to install HP1001 but it times out and can't find the WS-1001. Is >> there a way to tell HP1001 what the IP address of the WS_1001 is - I have >> it on a static address using the MAC address on my router. I tried to >> install ObserverIP and that's not working either. Current WS-1001 firmware >> is 2.4.3 and would prefer to not have to upgrade that since it's a pain in >> a$$ to get everything update again. >> >> Any hints on how to get it connected again would be appreciated. Thanks >> > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/9169a730-96fc-4cb7-a213-fa0a8f0f5f9c%40googlegroups.com.
[weewx-user] WS-1001 connection to Raspberry PI for Weewx
I had this working for 2 years but it stopped Saturday. I got it working 2 years ago and don't quite recall what I did. I think I used EasyWeatherIP to change web page in the setup page from "www.wunderground.com' to 'www.***.com". Now when I try to change it with EWIP, it doesn't make the change - it has made other changes. Not sure if there is a trick. I've tried to install HP1001 but it times out and can't find the WS-1001. Is there a way to tell HP1001 what the IP address of the WS_1001 is - I have it on a static address using the MAC address on my router. I tried to install ObserverIP and that's not working either. Current WS-1001 firmware is 2.4.3 and would prefer to not have to upgrade that since it's a pain in a$$ to get everything update again. Any hints on how to get it connected again would be appreciated. Thanks -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/528a2670-894b-42f9-a156-08d6238d3cbc%40googlegroups.com.
Re: [weewx-user] hello weather skin and ftp
Solved. I used inotifwait in a script to upload the file. Works like a charm. Added the script to crontab to run on reboot so I don't have to worry about it. Thanks for all help, On Monday, August 28, 2017 at 4:42:39 PM UTC-4, Bill Volz wrote: > > Thanks for getting back to me. I'm not sure what file structure your > referring to. Actually I didn't change any skin. I installed the Cumulus > Real Time extension and modified the crt.py file to write the file I want. > I can specify the file to write in the weewx.conf file. The crt.py is > called when every reading is received. I don't think I can use the skin > because that only runs when the web page is updated, not on each incoming > reading. I have the FTP section filled in and working but the file is not > uploaded. > > I have weewx running on a Raspberry and it's working, receiving packets > and forwarding them on to WU and writing the file I need. There is another > Windows computer in the same network that I need to upload the file created > by the crt extension to. > > I might be able to use a tool outside of weewx. I found > https://github.com/rvoicilas/inotify-tools/wiki that provides a function > (inotifywait) to wait for a file to change. All I'd need to do is run this > in a small script that just looks for the file to change and initiate the > ftp inside of that. > > > > On Monday, August 28, 2017 at 4:12:47 PM UTC-4, Tom Keffer wrote: >> >> The structure of your file system is not super clear, but I'm assuming >> that you've changed skin.conf so that it now specifies that only your >> simple BI template be processed. If this is the case, then the results (a >> single file) will be put in HTML_ROOT. >> >> If I've got this right, then all you need to do is fill out the [FTP] >> section in weewx.conf with the location of your FTP server and with the >> user credentials. Specifically, options user, password, server, and path. >> >> If I don't have this right, then give us the rest of the details. >> >> -tk >> >> >> On Mon, Aug 28, 2017 at 11:51 AM, Bill Volz <billr...@gmail.com> wrote: >> >>> Hi. I have a computer that runs Blue Iris (BI) surveillance software. At >>> this time I run a small Ruby program on that computer that downloads the >>> weather data every 3 minutes from Wunderground (WU) and creates a simple >>> text file. This file is then read by BI as a weather overlay on the video >>> streams. The program does a query every 3 minutes due to the 500 query/day >>> limit by WU before one has to cough up $$$. >>> >>> I now have weewx running on a Raspberry and receiving data from the PWS >>> (WS-1001-wifi) and uploading it to WU. I've set up FTP and it works (but >>> only when I update the web page for weewx). >>> >>> This is an example of the file I need to create: >>> >>> 66.6F 58% >>> 0.0 / 0 North >>> 0.00 in >>> 30.10- inHg >>> 08/28/17 13:05:47 >>> >>> The format is: >>> [temp]F [humidity]% >>> [wind speed] / [wind gust] [direction ordinal, eg, ESE] >>> [daily rainfall] in >>> [rel pressure][trend] inHg >>> [date/time of reading] >>> >>> Note the trend is a field supplied by WU that is '+' if the pressure is >>> rising, '-' if it's falling and blank if it's steady. I will use the >>> barometer 3 hour trend as shown on the weewx web page under the current >>> conditions - it's more informative. >>> >>> I've looked around and don't see any simple skin like a 'hello weather' >>> skin. The standard skin is rather long and complicated for a NOOB, does far >>> more than I need and only runs as needed, not at every loop event. In fact, >>> I'm not sure that I need a skin. >>> >>> So what do I want? >>> >>> Every time a reading is received from the PWS, write the text file, then >>> ftp that file to the other computer. >>> >>> I found Cumulus Real Time extension that does something like what I >>> want. I managed to modify it to produce the desired file format and info I >>> want: >>> >>> 64.4 F 64 % >>> 0.0 / 15.0 --- >>> 0.00 in >>> 29.88 -0.04 inHg >>> 08/28/17 14:49:30 >>> >>> Except for some extra spaces I don't want, it's acceptable. The --- for >>> the wind direction is because the windspeed is zero. >>> >>> So the only thing I need now is how to initiate FTP to upload the file. >>> >>> All help is appreciated. Thanks in advance. >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "weewx-user" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to weewx-user+...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- 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] hello weather skin and ftp
Thanks for getting back to me. I'm not sure what file structure your referring to. Actually I didn't change any skin. I installed the Cumulus Real Time extension and modified the crt.py file to write the file I want. I can specify the file to write in the weewx.conf file. The crt.py is called when every reading is received. I don't think I can use the skin because that only runs when the web page is updated, not on each incoming reading. I have the FTP section filled in and working but the file is not uploaded. I have weewx running on a Raspberry and it's working, receiving packets and forwarding them on to WU and writing the file I need. There is another Windows computer in the same network that I need to upload the file created by the crt extension to. I might be able to use a tool outside of weewx. I found https://github.com/rvoicilas/inotify-tools/wiki that provides a function (inotifywait) to wait for a file to change. All I'd need to do is run this in a small script that just looks for the file to change and initiate the ftp inside of that. On Monday, August 28, 2017 at 4:12:47 PM UTC-4, Tom Keffer wrote: > > The structure of your file system is not super clear, but I'm assuming > that you've changed skin.conf so that it now specifies that only your > simple BI template be processed. If this is the case, then the results (a > single file) will be put in HTML_ROOT. > > If I've got this right, then all you need to do is fill out the [FTP] > section in weewx.conf with the location of your FTP server and with the > user credentials. Specifically, options user, password, server, and path. > > If I don't have this right, then give us the rest of the details. > > -tk > > > On Mon, Aug 28, 2017 at 11:51 AM, Bill Volz <billr...@gmail.com > > wrote: > >> Hi. I have a computer that runs Blue Iris (BI) surveillance software. At >> this time I run a small Ruby program on that computer that downloads the >> weather data every 3 minutes from Wunderground (WU) and creates a simple >> text file. This file is then read by BI as a weather overlay on the video >> streams. The program does a query every 3 minutes due to the 500 query/day >> limit by WU before one has to cough up $$$. >> >> I now have weewx running on a Raspberry and receiving data from the PWS >> (WS-1001-wifi) and uploading it to WU. I've set up FTP and it works (but >> only when I update the web page for weewx). >> >> This is an example of the file I need to create: >> >> 66.6F 58% >> 0.0 / 0 North >> 0.00 in >> 30.10- inHg >> 08/28/17 13:05:47 >> >> The format is: >> [temp]F [humidity]% >> [wind speed] / [wind gust] [direction ordinal, eg, ESE] >> [daily rainfall] in >> [rel pressure][trend] inHg >> [date/time of reading] >> >> Note the trend is a field supplied by WU that is '+' if the pressure is >> rising, '-' if it's falling and blank if it's steady. I will use the >> barometer 3 hour trend as shown on the weewx web page under the current >> conditions - it's more informative. >> >> I've looked around and don't see any simple skin like a 'hello weather' >> skin. The standard skin is rather long and complicated for a NOOB, does far >> more than I need and only runs as needed, not at every loop event. In fact, >> I'm not sure that I need a skin. >> >> So what do I want? >> >> Every time a reading is received from the PWS, write the text file, then >> ftp that file to the other computer. >> >> I found Cumulus Real Time extension that does something like what I want. >> I managed to modify it to produce the desired file format and info I want: >> >> 64.4 F 64 % >> 0.0 / 15.0 --- >> 0.00 in >> 29.88 -0.04 inHg >> 08/28/17 14:49:30 >> >> Except for some extra spaces I don't want, it's acceptable. The --- for >> the wind direction is because the windspeed is zero. >> >> So the only thing I need now is how to initiate FTP to upload the file. >> >> All help is appreciated. Thanks in advance. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "weewx-user" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to weewx-user+...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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] hello weather skin and ftp
Hi. I have a computer that runs Blue Iris (BI) surveillance software. At this time I run a small Ruby program on that computer that downloads the weather data every 3 minutes from Wunderground (WU) and creates a simple text file. This file is then read by BI as a weather overlay on the video streams. The program does a query every 3 minutes due to the 500 query/day limit by WU before one has to cough up $$$. I now have weewx running on a Raspberry and receiving data from the PWS (WS-1001-wifi) and uploading it to WU. I've set up FTP and it works (but only when I update the web page for weewx). This is an example of the file I need to create: 66.6F 58% 0.0 / 0 North 0.00 in 30.10- inHg 08/28/17 13:05:47 The format is: [temp]F [humidity]% [wind speed] / [wind gust] [direction ordinal, eg, ESE] [daily rainfall] in [rel pressure][trend] inHg [date/time of reading] Note the trend is a field supplied by WU that is '+' if the pressure is rising, '-' if it's falling and blank if it's steady. I will use the barometer 3 hour trend as shown on the weewx web page under the current conditions - it's more informative. I've looked around and don't see any simple skin like a 'hello weather' skin. The standard skin is rather long and complicated for a NOOB, does far more than I need and only runs as needed, not at every loop event. In fact, I'm not sure that I need a skin. So what do I want? Every time a reading is received from the PWS, write the text file, then ftp that file to the other computer. I found Cumulus Real Time extension that does something like what I want. I managed to modify it to produce the desired file format and info I want: 64.4 F 64 % 0.0 / 15.0 --- 0.00 in 29.88 -0.04 inHg 08/28/17 14:49:30 Except for some extra spaces I don't want, it's acceptable. The --- for the wind direction is because the windspeed is zero. So the only thing I need now is how to initiate FTP to upload the file. All help is appreciated. Thanks in advance. -- 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: trouble getting weewx to listen for ws-1001-wifi
Thanks, that fixed it. And I found the rsyslog issue so no more double log entries. On Monday, August 28, 2017 at 9:38:19 AM UTC-4, mwall wrote: > > > > On Monday, August 28, 2017 at 8:43:03 AM UTC-4, Bill Volz wrote: >> >> The restart was a manual restart with 'service weewx restart'. >> Firmware is version 2.4.3. >> >> Here's the log with debug = 1: thanks, >> > > bill, > > thanks for that. please try weewx-interceptor v0.31 > > this will recognize the absbaromin parameter > > it does nothing for your double log entries - that is probably something > in your rsyslog or systemd configuration > > 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: trouble getting weewx to listen for ws-1001-wifi
).get(True, self._queue_timeout) Aug 28 08:30:09 raspberrypi weewx[7098]: data = self._device.get_queue().get(True, self._queue_timeout) Aug 28 08:30:09 raspberrypi weewx[7098]: File "/usr/lib/python2.7/Queue.py", line 177, in get Aug 28 08:30:09 raspberrypi weewx[7098]: File "/usr/lib/python2.7/Queue.py", line 177, in get Aug 28 08:30:09 raspberrypi weewx[7098]: self.not_empty.wait(remaining) Aug 28 08:30:09 raspberrypi weewx[7098]: self.not_empty.wait(remaining) Aug 28 08:30:09 raspberrypi weewx[7098]: File "/usr/lib/python2.7/threading.py", line 359, in wait Aug 28 08:30:09 raspberrypi weewx[7098]: File "/usr/lib/python2.7/threading.py", line 359, in wait Aug 28 08:30:09 raspberrypi weewx[7098]: _sleep(delay) Aug 28 08:30:09 raspberrypi weewx[7098]: _sleep(delay) Aug 28 08:30:09 raspberrypi weewx[7098]: File "/usr/share/weewx/weewx/engine.py", line 794, in sigTERMhandler Aug 28 08:30:09 raspberrypi weewx[7098]: File "/usr/share/weewx/weewx/engine.py", line 794, in sigTERMhandler Aug 28 08:30:09 raspberrypi weewx[7098]: raise Terminate Aug 28 08:30:09 raspberrypi weewx[7098]: raise Terminate Aug 28 08:30:09 raspberrypi weewx[7098]: Terminate Aug 28 08:30:09 raspberrypi weewx[7098]: Terminate Aug 28 08:30:14 raspberrypi weewx[7114]: Stopping weewx weather system: weewx.. Aug 28 08:30:14 raspberrypi weewx[7114]: Stopping weewx weather system: weewx.. On Monday, August 28, 2017 at 6:38:03 AM UTC-4, mwall wrote: > > > > On Monday, August 28, 2017 at 12:56:08 AM UTC-4, Bill Volz wrote: >> >> >> Seems to be working now. The message was from a restart of the service. >> Left it alone for a while and it fixed itself. >> > > you are using a magical raspberry pi! this is the first time i've heard > of weewx starting itself after an exit. > > > >> But now getting this message in syslog: >> : >> Aug 28 00:52:40 raspberrypi weewx[4022]: interceptor: MainThread: >> unrecognized parameter absbaromin=26.83 >> > > what firmware is your weather station running? > > please some 'raw packet' output. set debug=1, then post the 'raw packet' > output that results. > > 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: trouble getting weewx to listen for ws-1001-wifi
Seems to have fixed itself. I guess time heals all wounds? But now getting this message: Aug 28 00:44:40 raspberrypi weewx[4022]: interceptor: MainThread: unrecognized parameter absbaromin=26.82 On Sunday, August 27, 2017 at 10:21:54 PM UTC-4, mwall wrote: > > On Sunday, August 27, 2017 at 10:01:28 PM UTC-4, Bill Volz wrote: >> >> I'm having trouble getting the weewx to listen for the incoming info from >> a ws-1001-wifi. Here's what in syslog: >> >> Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: mode is >> listen >> Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: mode is >> listen >> Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: listen >> on 192.168.0.196:8081 >> Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: listen >> on 192.168.0.196:8081 >> Aug 27 21:43:26 raspberrypi weewx[2809]: import of driver failed: [Errno >> 99] Cannot assign requested address () >> Aug 27 21:43:26 raspberrypi weewx[2809]: import of driver failed: [Errno >> 99] Cannot assign requested address () >> Aug 27 21:43:26 raspberrypi weewx[2809]: engine: Unable to load driver: >> [Errno 99] Cannot assign requested address >> Aug 27 21:43:26 raspberrypi weewx[2809]: engine: Unable to load driver: >> [Errno 99] Cannot assign requested address >> Aug 27 21:43:26 raspberrypi weewx[2809]: Exiting... >> Aug 27 21:43:26 raspberrypi weewx[2809]: Exiting... >> >> > has the network been initialized by the time that weewx starts? > > syslog will tell you > > you can also test: for example, does weewx work when you start it > manually, but not when started by the system at system startup? > > 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] trouble getting weewx to listen for ws-1001-wifi
I'm having trouble getting the weewx to listen for the incoming info from a ws-1001-wifi. Here's what in syslog: Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: mode is listen Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: mode is listen Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: listen on 192.168.0.196:8081 Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: listen on 192.168.0.196:8081 Aug 27 21:43:26 raspberrypi weewx[2809]: import of driver failed: [Errno 99] Cannot assign requested address () Aug 27 21:43:26 raspberrypi weewx[2809]: import of driver failed: [Errno 99] Cannot assign requested address () Aug 27 21:43:26 raspberrypi weewx[2809]: engine: Unable to load driver: [Errno 99] Cannot assign requested address Aug 27 21:43:26 raspberrypi weewx[2809]: engine: Unable to load driver: [Errno 99] Cannot assign requested address Aug 27 21:43:26 raspberrypi weewx[2809]: Exiting... Aug 27 21:43:26 raspberrypi weewx[2809]: Exiting... Not sure why everything is repeated but that's the least of the issues. I;d rather not specify the ip address to listen on since the ws-1001 uses DHCP and the address might change. I set a port to one that's not being used and should be able to listen for anything on that port. Here's the weewx.conf file: # WEEWX CONFIGURATION FILE # # Copyright (c) 2009-2015 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 = 0 # Root directory of the weewx data file hierarchy for this station WEEWX_ROOT = / # 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.7.1 ## # This section is for information about the station. [Station] # Description of the station location location = "Black Mountain, NC" # Latitude and longitude in decimal degrees latitude = 35.6671 longitude = -82.36 # Altitude of the station, with unit it is in. This is downloaded from # from the station if the hardware supports it. altitude = 3350, 3350 # 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 = Interceptor # 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 ## [Simulator] # This section is for the weewx weather station simulator # The time (in seconds) between LOOP packets. loop_interval = 2.5 # The simulator mode can be either 'simulator' or 'generator'. # Real-time simulator. Sleep between each LOOP packet. mode = simulator # Generator. Emit LOOP packets as fast as possible (useful for testing). #mode = generator # The start time. If not specified, the default is to use the present time. #start = 2011-01-01 00:00 # The driver to use: driver = weewx.drivers.simulator ## # This section is for uploading data to Internet sites [StdRESTful] [[StationRegistry]] # To register this weather station with weewx, set this to true register_this_station = false [[AWEKAS]] # This section is for configuring posts to AWEKAS. # If you wish to do this, set the option 'enable' to true, # and specify a username and password. enable = false username = replace_me # To guard against parsing errors, put your password in quotes: password = replace_me [[CWOP]] # This section is for configuring posts to CWOP. # If you wish to do this, set the option 'enable' to true, # and specify the station ID (e.g., CW1234). enable = false station = replace_me # If this is an APRS (radio amateur) station, uncomment # the following and replace with a passcode (e.g., 12345). #passcode = replace_me (APRS stations only) [[PWSweather]] # This section is for configuring posts to PWSweather.com. # If you wish to do this, set the option 'enable' to true, # and specify a station and password. enable = false station = replace_me # To guard
