Re: [weewx-user] Re: "vantage: no received..." with Davis Pro2 IP logger crashes weewx
Hi Luc, it seems the issue is really coming from the IP Logger. If I read the Log well the PWS and the Rasp. are/were running in a local network. Mar 3 15:04:25 raspberrypi weewx[23145]: vantage: Opened up ethernet host 192.168.0.120 on port 2 In this case it doesn´t matter if you get a static or dynamic IP from the ISP. After I have changed the conf file with: *loop_on_init = True *weewx is running well. Had yesterday a power failure for 6 hours, my local network was down - weewx reconnected after my local router was up again. Thaanks again. Michael Am Mittwoch, 12. Juli 2017 19:42:33 UTC+7 schrieb Luc Heijst: > > Hi Michael, > > I checked my old logs again. As weewx was started automatically after a > fatal error, I must have set loop_on_init = True. > See log example below: > Mar 3 15:04:25 raspberrypi weewx[23145]: vantage: Opened up ethernet host > 192.168.0.120 on port 2 > Mar 3 15:04:25 raspberrypi weewx[23145]: vantage: Getting archive packets > since 2016-03-03 14:50:00 CET (1457013000) > Mar 3 15:04:31 raspberrypi weewx[23145]: vantage: raise WeeWxIOError-8 > read chars 2 received 0 > Mar 3 15:04:31 raspberrypi weewx[23145]: vantage: remaining: 4096, raise > WeeWxIOError-7 socket error-3 |[Errno 11] Die Ressource ist zur Zeit nicht > verfügbar| > Mar 3 15:04:32 raspberrypi weewx[23145]: vantage: remaining: 2, raise > WeeWxIOError-7 socket error-3 |[Errno 104] Die Verbindung wurde vom > Kommunikationspartner zurückgesetzt| > Mar 3 15:04:32 raspberrypi weewx[23145]: engine: Main loop exiting. > Shutting engine down. > Mar 3 15:04:32 raspberrypi weewx[23145]: vantage: raise WeeWxIOError-9 > write socket error [Errno 32] Datenübergabe unterbrochen (broken pipe) > Mar 3 15:04:32 raspberrypi weewx[23145]: vantage: input buffer flushed; > read: 0 chars > Mar 3 15:04:32 raspberrypi weewx[23145]: vantage: raise WeeWxIOError-9 > write socket error [Errno 32] Datenübergabe unterbrochen (broken pipe) > Mar 3 15:07:07 raspberrypi weewx[23494]: engine: Initializing engine > Mar 3 15:07:07 raspberrypi weewx[23494]: driver version is 3.0.2 > -- 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 the SenseHat
I've played with the SenseHAT (but on a RPi3) and you may need to compensate for the fact that the chip heats up the SenseHAT and so it shows a higher than actual temperature reading. I've seen this mentioned in several places on the Web and there are suggestions about how to compensate for this. I guess it all depends on what you want the system to do for you. 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Regenerate NOAA Tables
ok - I answered my own question: add a sudo to wee_database weewx.conf --rebuild-daily On Thursday, July 13, 2017 at 1:13:04 PM UTC-7, Matt T wrote: > > I've recently cleaned my bad data 2016 and 2015 data from my database. > I've followed the procedure to remove the bad data from the weewx > database, below. It appears the data is fixed (based on sql queries). > However the NOAA tables still regenerate with the old data. Is the a way > to force them to regenerate with the new database values? I've tried > deleting them and restarting weewx, but they are regenerated with the old > data. > > https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data > > Using: weewx v3.7.1 installed with deb package on a Raspberry Pi, with > Acurite 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] Regenerate NOAA Tables
I've recently cleaned my bad data 2016 and 2015 data from my database. I've followed the procedure to remove the bad data from the weewx database, below. It appears the data is fixed (based on sql queries). However the NOAA tables still regenerate with the old data. Is the a way to force them to regenerate with the new database values? I've tried deleting them and restarting weewx, but they are regenerated with the old data. https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data Using: weewx v3.7.1 installed with deb package on a Raspberry Pi, with Acurite 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: Regenerate NOAA tables
Using : weewx v3.7.1 on a Raspberry Pi, with Acurite Hardware On Thursday, July 13, 2017 at 11:38:20 AM UTC-7, Matt T wrote: > > I've recently cleaned my bad data 2016 and 2015 data from my database. > I've followed the procedure to remove the bad data from the weewx > database, below. It appears the data is fixed (based on sql queries). > However the NOAA tables still regenerate with the old data. Is the a way > to force them to regenerate with the new database values? I've tried > deleting them and restarting weewx, but they are regenerated with the old > data. > > https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data > > Thanks, > > Matt > -- 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] Regenerate NOAA tables
I've recently cleaned my bad data 2016 and 2015 data from my database. I've followed the procedure to remove the bad data from the weewx database, below. It appears the data is fixed (based on sql queries). However the NOAA tables still regenerate with the old data. Is the a way to force them to regenerate with the new database values? I've tried deleting them and restarting weewx, but they are regenerated with the old data. https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data Thanks, Matt -- 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 Interceptor: Rain not registering
yes, indeed, but would that break other weatherstation interceptor data? Also, would that be hard to implement? I guess for a generic Wunderground Interceptor it would cover many stations in one decoding (This is me assuming all station reporting always report all the same fields tu WU?!? Probably wishful thinking...) Fred On Thursday, July 13, 2017 at 5:45:19 PM UTC+2, mwall wrote: > > On Thursday, July 13, 2017 at 11:31:33 AM UTC-4, Fred wrote: >> >> The station is not very old yet: Is it possible it posts the >> yearrain because it simply has not calculated it yet?!? >> > > i suppose that is possible. but meanwhile we are missing rainfall data! > > according to the wunderground docs: > > rainin - [rain inches over the past hour)] -- the accumulated rainfall in the > past 60 min > dailyrainin - [rain inches so far today in local time] > > > so i suppose i could make the interceptor use dailyrainin instead of > yearrainin, as long as we get the local time right... > > cannot use rainin since it is a moving window - rain in the past 60 min, > not rain since the top of the last hour. > > 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 Interceptor: Rain not registering
On Thursday, July 13, 2017 at 11:31:33 AM UTC-4, Fred wrote: > > The station is not very old yet: Is it possible it posts the yearrain > because it simply has not calculated it yet?!? > i suppose that is possible. but meanwhile we are missing rainfall data! according to the wunderground docs: rainin - [rain inches over the past hour)] -- the accumulated rainfall in the past 60 min dailyrainin - [rain inches so far today in local time] so i suppose i could make the interceptor use dailyrainin instead of yearrainin, as long as we get the local time right... cannot use rainin since it is a moving window - rain in the past 60 min, not rain since the top of the last hour. 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 Interceptor: Rain not registering
Hi Jan, Biggest problem was getting the data to the interceptor driver: My weatherstation is on a different router than my pi... Thankfully I have the ASUS wrt router software installed, so I was able to insert some rules to forward my traffic sent from port 80 to the pi: iptables -t mangle -A PREROUTING -s 192.168.2.165 -j ROUTE --tee --gw 192.168.1.45 iptables -t mangle -A POSTROUTING -d 192.168.2.165 -j ROUTE --tee --gw 192.168.1.45 The first IP is my weatherstation, the second IP is the PI ... Maybe it can help you in your quest :) Fred On Thursday, July 13, 2017 at 2:54:52 PM UTC+2, jan hallink wrote: > > > Hello Fred > Very interesting what you are trying to fix. > I also planned to buy a ventus w830 and if possible connect it to weewx. > Unfortunately I can't help you directly,but maybe you can search on fine > offset wh2900. > It's the same weather station and there was a thread about it in april/may. > They gave some hints about the archive interval time. > > Jan > -- 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 Interceptor: Rain not registering
Oh, forgot to mention: The station is not very old yet: Is it possible it posts the yearrain because it simply has not calculated it yet?!? Just theorizing :) Fred On Thursday, July 13, 2017 at 5:29:59 PM UTC+2, Fred wrote: > > Hi, > > First of all: Thank you for writing this software! Its great :) > > This is the section you requested (Full file is in my original post, but > maybe you missed it) > > [Interceptor] > # This section is for the network traffic interceptor driver. > > # 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 = enxb827eb718db1 > pcap_filter = src 192.168.2.165 and dst port 80 > > > Thanks! > > > Fred > > > On Thursday, July 13, 2017 at 5:19:35 PM UTC+2, mwall wrote: >> >> >> >> On Wednesday, July 12, 2017 at 2:38:28 PM UTC-4, Fred wrote: >>> >>> Anybody have any idea what is going wrong? >>> >>> >> fred, >> > > > >> >> please post the [Interceptor] section of your weewx configuration. >> >> it looks like your station is always sending a junk value (-) for >> yearrainin. yearrainin is the observation that the interceptor driver uses >> to determine the rainfall. so when your station always reports -, the >> driver maps that to 'None', and voila! you have no rain reported. >> >> i used yearrainin in order to minimize the effects of counter rollover, >> and because i was not seeing consistent use of rainin (is it rain since >> last sampling? in a certain time period? it seems to vary depending on >> the manufacturer and/or the firmware) >> >> it looks like your rainin is a counter, but counting since when? when >> does rainin reset? and why is there no value for your yearrainin? >> >> your station is also reporting absbaromin. this value would be preferred >> to baromin, which i assume is a derivation of absbaromin with >> altitude/temperature compensation. i'll have to see about making the >> driver prefer absbaromin if it exists. >> >> btw, at some point the wu-based portions of the interceptor probably >> belong in a separate driver that simply captures data bound for wu, either >> by sniffing or by listening. that driver *should* work with any >> manufacturer's hardware/firmware as long as they adhere to the wu protocol. >> >> 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: LaCrosse 2813U on Rpi Zero W - A little help for the new guy please
If you have a separate weewx log then that one - else syslog On Thursday, 13 July 2017 18:27:00 UTC+3, Dan Blanchard wrote: > Andrew, I understand your point and meant to send the log but got wrapped > up in thinking it was working last night. Which log are you asking for? > There are several logs at /var/log > > On Wednesday, July 12, 2017 at 10:31:17 PM UTC-7, Andrew Milner wrote: >> >> As Matthew said in his post - attaching the log from just before start-up >> of weewx would help us all to know exactly what is happening, and what (if >> any) error messages you are receiving. >> >> If the log by itself does not provide all the information you may need to >> stop weewx, set debug=1 in weewx.conf, restart weewx and get additional >> debug information. >> >> Trying to help without seeing the log is a little bit like looking for a >> needle in a haystack - virtually impossible!! >> >> The log is usually key to all problems, and seeing the log through the >> whole start-up process up to the end of the first archive period usually >> sheds some light on problems and issues in most situations. Remember - the >> log is the key!! >> >> >> >> >> >> On Thursday, 13 July 2017 08:09:45 UTC+3, Dan Blanchard wrote: >> >>> Further to this issue, I found that if I type sudo wee_device --info then >>> press the [Set] button on my station, the Tx and Rx start communicating >>> again for a few minutes. But I can't seem to keep them connected. >>> >>> Is there some trick to keep them paired once I finally get them paired? >>> I'm going to leave it on overnight and see what happens. >>> >>> >>> >>> >>> On Wednesday, July 12, 2017 at 9:06:27 PM UTC-7, Dan Blanchard wrote: Thanks for the info Gary, that was the problem, I got it to pair, but then in un-paired after about 2-3 minutes. Any thoughts there? On Wednesday, July 12, 2017 at 5:57:05 PM UTC-7, gjr80 wrote: > > On Thursday, 13 July 2017 10:28:36 UTC+10, Dan Blanchard wrote: >> >> usb.USBError: error sending control message: Operation not permitted >> > > Hi, > > Sounds like a permission issue, try prefixing the command with sudo: > > $ sudo wee_device --pair > > 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.
[weewx-user] Re: WeeWX Interceptor: Rain not registering
Hi, First of all: Thank you for writing this software! Its great :) This is the section you requested (Full file is in my original post, but maybe you missed it) [Interceptor] # This section is for the network traffic interceptor driver. # 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 = enxb827eb718db1 pcap_filter = src 192.168.2.165 and dst port 80 Thanks! Fred On Thursday, July 13, 2017 at 5:19:35 PM UTC+2, mwall wrote: > > > > On Wednesday, July 12, 2017 at 2:38:28 PM UTC-4, Fred wrote: >> >> Anybody have any idea what is going wrong? >> >> > fred, > > > please post the [Interceptor] section of your weewx configuration. > > it looks like your station is always sending a junk value (-) for > yearrainin. yearrainin is the observation that the interceptor driver uses > to determine the rainfall. so when your station always reports -, the > driver maps that to 'None', and voila! you have no rain reported. > > i used yearrainin in order to minimize the effects of counter rollover, > and because i was not seeing consistent use of rainin (is it rain since > last sampling? in a certain time period? it seems to vary depending on > the manufacturer and/or the firmware) > > it looks like your rainin is a counter, but counting since when? when > does rainin reset? and why is there no value for your yearrainin? > > your station is also reporting absbaromin. this value would be preferred > to baromin, which i assume is a derivation of absbaromin with > altitude/temperature compensation. i'll have to see about making the > driver prefer absbaromin if it exists. > > btw, at some point the wu-based portions of the interceptor probably > belong in a separate driver that simply captures data bound for wu, either > by sniffing or by listening. that driver *should* work with any > manufacturer's hardware/firmware as long as they adhere to the wu protocol. > > 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: LaCrosse 2813U on Rpi Zero W - A little help for the new guy please
Andrew, I understand your point and meant to send the log but got wrapped up in thinking it was working last night. Which log are you asking for? There are several logs at /var/log On Wednesday, July 12, 2017 at 10:31:17 PM UTC-7, Andrew Milner wrote: > > As Matthew said in his post - attaching the log from just before start-up > of weewx would help us all to know exactly what is happening, and what (if > any) error messages you are receiving. > > If the log by itself does not provide all the information you may need to > stop weewx, set debug=1 in weewx.conf, restart weewx and get additional > debug information. > > Trying to help without seeing the log is a little bit like looking for a > needle in a haystack - virtually impossible!! > > The log is usually key to all problems, and seeing the log through the > whole start-up process up to the end of the first archive period usually > sheds some light on problems and issues in most situations. Remember - the > log is the key!! > > > > > > On Thursday, 13 July 2017 08:09:45 UTC+3, Dan Blanchard wrote: > >> Further to this issue, I found that if I type sudo wee_device --info then >> press the [Set] button on my station, the Tx and Rx start communicating >> again for a few minutes. But I can't seem to keep them connected. >> >> Is there some trick to keep them paired once I finally get them paired? >> I'm going to leave it on overnight and see what happens. >> >> >> >> >> On Wednesday, July 12, 2017 at 9:06:27 PM UTC-7, Dan Blanchard wrote: >>> >>> Thanks for the info Gary, that was the problem, I got it to pair, but >>> then in un-paired after about 2-3 minutes. Any thoughts there? >>> >>> >>> >>> On Wednesday, July 12, 2017 at 5:57:05 PM UTC-7, gjr80 wrote: On Thursday, 13 July 2017 10:28:36 UTC+10, Dan Blanchard wrote: > > usb.USBError: error sending control message: Operation not permitted > Hi, Sounds like a permission issue, try prefixing the command with sudo: $ sudo wee_device --pair 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.
[weewx-user] Re: WeeWX Interceptor: Rain not registering
On Wednesday, July 12, 2017 at 2:38:28 PM UTC-4, Fred wrote: > > Anybody have any idea what is going wrong? > > fred, please post the [Interceptor] section of your weewx configuration. it looks like your station is always sending a junk value (-) for yearrainin. yearrainin is the observation that the interceptor driver uses to determine the rainfall. so when your station always reports -, the driver maps that to 'None', and voila! you have no rain reported. i used yearrainin in order to minimize the effects of counter rollover, and because i was not seeing consistent use of rainin (is it rain since last sampling? in a certain time period? it seems to vary depending on the manufacturer and/or the firmware) it looks like your rainin is a counter, but counting since when? when does rainin reset? and why is there no value for your yearrainin? your station is also reporting absbaromin. this value would be preferred to baromin, which i assume is a derivation of absbaromin with altitude/temperature compensation. i'll have to see about making the driver prefer absbaromin if it exists. btw, at some point the wu-based portions of the interceptor probably belong in a separate driver that simply captures data bound for wu, either by sniffing or by listening. that driver *should* work with any manufacturer's hardware/firmware as long as they adhere to the wu protocol. 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 Interceptor: Rain not registering
Hello Fred Very interesting what you are trying to fix. I also planned to buy a ventus w830 and if possible connect it to weewx. Unfortunately I can't help you directly,but maybe you can search on fine offset wh2900. It's the same weather station and there was a thread about it in april/may. They gave some hints about the archive interval time. Jan -- 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: Archive question
I will wait and see what Matthew says. Thank you all 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.
