[weewx-user] Re: Issues with new FW in Acu-Link bridge and the interceptor driver

yep its in the script i like to watch it on the console here is what it looks like if you want to see On Sunday, October 16, 2016 at 12:51:43 AM UTC-5, Radar wrote: > > i have tried ngrep too but the only way i have got it on a single line is > to out put to a file. don't know why it won't put

[weewx-user] Re: Issues with new FW in Acu-Link bridge and the interceptor driver

i have tried ngrep too but the only way i have got it on a single line is to out put to a file. don't know why it won't put that to the console out put. i think i read that the latest version of ngrep would work but haven't tried it On Sunday, October 16, 2016 at 12:40:14 AM UTC-5, Jerome Helbe

[weewx-user] Re: Issues with new FW in Acu-Link bridge and the interceptor driver

ok, I see what radar is doing... Most of the "magic" is going to happen in a perl script that he is piping the stream into. His tcpdump and stdbuf all pretty much give the same stuff as the ngrep/sed stuff I have been trying to use (spread across multiple lines still) and then he has a perl scri

Re: [weewx-user] Re: External site reporting irregular timing schedule

No, I had turned debug back to 0 a while ago. I'll turn it back to 1 and repost later. ​Tim​ ​ On Sat, Oct 15, 2016 at 9:37 PM, gjr80 wrote: > Was debug=1? If debug=1we should see what messages if any are coming in > from the station. There are a lot of stale data entries but they seem to > di

Re: [weewx-user] Re: External site reporting irregular timing schedule

Was debug=1? If debug=1we should see what messages if any are coming in from the station. There are a lot of stale data entries but they seem to disappear in time. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group an

Re: [weewx-user] Re: External site reporting irregular timing schedule

Going by the posts in this thread we have not seen a log since record_generation was changed to software. Would be good to see that from when weewx was started. Also, might be worth running a wee_debug report ( http://weewx.com/docs/utilities.htm#wee_debug_utility ) to give us a look at weewx.c

Re: [weewx-user] Re: External site reporting irregular timing schedule

Maybe I put it at ad oddball interval like 8 minutes and see what it does? ​Tim​ ​ On Sat, Oct 15, 2016 at 7:38 PM, mwall wrote: > On Saturday, October 15, 2016 at 9:58:28 PM UTC-4, Tim Phillips wrote: >> >> So what do you guys think? Are the external sites just reporting a little >> flakey o

Re: [weewx-user] Re: External site reporting irregular timing schedule

On Saturday, October 15, 2016 at 9:58:28 PM UTC-4, Tim Phillips wrote: > > So what do you guys think? Are the external sites just reporting a little > flakey or is weewx skipping uploads? Check the PWS link and notice that is > takes either a 5 or 10 minute interval with seemingly no pattern. >

Re: [weewx-user] Re: External site reporting irregular timing schedule

So what do you guys think? Are the external sites just reporting a little flakey or is weewx skipping uploads? Check the PWS link and notice that is takes either a 5 or 10 minute interval with seemingly no pattern. Tim On Oct 15, 2016 6:36 PM, "vince" wrote: On Saturday, October 15, 2016 at 4:

Re: [weewx-user] Re: External site reporting irregular timing schedule

On Saturday, October 15, 2016 at 4:25:10 PM UTC-7, mwall wrote: > > On Saturday, October 15, 2016 at 4:27:47 PM UTC-4, Tim Phillips wrote: >> >> Attached the new (longer) log that's been going all day. I took a glance >> at it and saw a few things that kept popping up and look out of the >> ordin

[weewx-user] Re: Version 3.6.1

wow thanks This saves much time. Am Freitag, 14. Oktober 2016 01:24:35 UTC+2 schrieb Tom Keffer: > > Oh, I should mention: weewx now has an apt repository! > > Installs and upgrades can be done using apt-get. Follow the directions > here . > > -tk > > On Thu,

[weewx-user] Re: Issues with new FW in Acu-Link bridge and the interceptor driver

This is also only an issue for someone not sniffing and redirecting, only if the bridge is talking directly to the driver. On Saturday, October 15, 2016 at 3:04:22 PM UTC-5, mwall wrote: > > > there is an (untested) fix for this at commit b27acc1 (interceptor driver > 0.13a) > > [Interceptor] >

[weewx-user] Re: Issues with new FW in Acu-Link bridge and the interceptor driver

I didnt get notifications that these messages came in, and just now saw them. I'll give it a shot in a bit after the kid goes to bed. On Saturday, October 15, 2016 at 3:04:22 PM UTC-5, mwall wrote: > > On Saturday, October 15, 2016 at 12:21:13 PM UTC-4, Jerome Helbert wrote: > > >> Two things h

[weewx-user] Re: Issues with new FW in Acu-Link bridge and the interceptor driver

Yeah, this is the primary reason I wanted to switch to the interceptor instead of rewriting my version of the hackulink On Saturday, October 15, 2016 at 2:45:16 PM UTC-5, Radar wrote: > > i thought that it would but i have it working with a put togohter driver i > made that works and edited some

Re: [weewx-user] Rebuild stats database

Sorry. Because a NOAA monthly report is a daily summaries list, I thought that the data was the same. Many thanks El domingo, 16 de octubre de 2016, 0:53:13 (UTC+2), Tom Keffer escribió: > > ​The stats database (which went away in v3.x) summarizes by day, not by > month. > > Unfortunately, I th

Re: [weewx-user] Re: External site reporting irregular timing schedule

On Saturday, October 15, 2016 at 5:56:48 PM UTC-4, Tom Keffer wrote: > > I'm not familiar with the Acurite. What sort of interval should we > expected between LOOP packets? > the 5-in-1 instrument clusters emit a packet every 18 seconds. the acurite console emits loop packets every 18 to 60 seco

Re: [weewx-user] Re: External site reporting irregular timing schedule

On Saturday, October 15, 2016 at 4:27:47 PM UTC-4, Tim Phillips wrote: > > Attached the new (longer) log that's been going all day. I took a glance > at it and saw a few things that kept popping up and look out of the > ordinary: > > 1) "Oct 15 12:46:38 raspberrypi rsyslogd-2007: action 'action 1

Re: [weewx-user] Rebuild stats database

​The stats database (which went away in v3.x) summarizes by day, not by month. Unfortunately, I think you're screwed. Next time, be sure to do regular backups! -tk​ On Sat, Oct 15, 2016 at 1:47 PM, tomres wrote: > Hello, > > All my old databases are lost, but I still have the monthly NOAA .txt

[weewx-user] Re: Extract maximum value of an observation from loop packet

hi andrew, it is pretty simple, actually. make a service that is bound to LOOP packets. on each loop packet, spit the value(s) to file/disk/database. create a file in user/captureloop.py that has something like this: import weewx from weewx.engine import StdService class CaptureLOOP(StdServi

Re: [weewx-user] Extract maximum value of an observation from loop packet

If foo is the observation type, then $current.foo.max is the max loop value seen during the archive period. Or, are you looking to access it in a Python program? -tk On Sat, Oct 15, 2016 at 3:24 PM, Andrew Potter wrote: > Hi > I'm hoping to extract and log the maximum value of a sensor from an

Re: [weewx-user] Windows Development

Tom, Regarding delete=False, most like to do with the exclusive mode used on Windows, see https://bugs.python.org/issue14243. For logging I would advocate for a or size fits all model. With Python logging you can also load config from a file, so this would allow developers to specify their own

Re: [weewx-user] Re: External site reporting irregular timing schedule

Just set record_generation=hardware to record_generation=software. We'll see how that goes. I have the interval set to (300) 5 minutes, but as you are seeing it doesn't seem to be sticking to that. ​ Tim On Sat, Oct 15, 2016 at 2:56 PM, Thomas Keffer wrote: > Good suggestion, and I'll be intere

[weewx-user] Extract maximum value of an observation from loop packet

Hi I'm hoping to extract and log the maximum value of a sensor from any given loop (instead of the average by default). Is there a way to do this? (I've had a look at accum.py but my Python obviously isn't up to scratch to figure it out). I'm comfortable with needing to add to extensions.py but l

Re: [weewx-user] Re: External site reporting irregular timing schedule

Good suggestion, and I'll be interested to see what happens once record_generation is set to software, but I don't think things are that simple. Sometimes the driver saves to the database every 5 minutes, and sometimes only every 10 minutes. If the issue was that the archive interval is wrong, it m

[weewx-user] Rebuild stats database

Hello, All my old databases are lost, but I still have the monthly NOAA .txt reports. Someone has managed to rebuild stats.sdb from them? NOAA reports were generated with weewx 2.7. I have not config files, but I think they are near standard. Thanks -- You received this message because you are

Re: [weewx-user] Re: External site reporting irregular timing schedule

You have record_generation=hardware under [StdArchive] in weewx.conf but I don't believe your weather station actually produces archive records. Stop weewx, edit weewx.conf and set record_generation=software then start weewx. See how that goes. Gary -- You received this message because you ar

[weewx-user] Re: Issues with new FW in Acu-Link bridge and the interceptor driver

On Saturday, October 15, 2016 at 12:21:13 PM UTC-4, Jerome Helbert wrote: > Two things here... > >1. I need some way to get ngrep or tcpdump to piece together the http >stream properly... I tried to use sed, but since sed operates on a line by >line basis - it is not very easy (if

[weewx-user] Re: Issues with new FW in Acu-Link bridge and the interceptor driver

i thought that it would but i have it working with a put togohter driver i made that works and edited some parts of weewx for the extra rain and wind and wind gust and noaa reports was looking at how it did the rain after the fireware upgrade for some reason i could not figure it out how to do t

[weewx-user] Re: Issues with new FW in Acu-Link bridge and the interceptor driver

On Saturday, October 15, 2016 at 3:26:23 PM UTC-4, Radar wrote: > > and i can't use it because i use two 5n1 sensors and a rain gauge and a > about 10 temp/humid sensors i was just playing with it but it worked > you should be able to capture data from all of those sensors using the interceptor

[weewx-user] Re: Issues with new FW in Acu-Link bridge and the interceptor driver

and i can't use it because i use two 5n1 sensors and a rain gauge and a about 10 temp/humid sensors i was just playing with it but it worked On Saturday, October 15, 2016 at 1:54:20 PM UTC-5, Radar wrote: > > hi, > i tested the interceptor driver using tcpdump piped to a perl script to > put the

[weewx-user] Re: Issues with new FW in Acu-Link bridge and the interceptor driver

hi, i tested the interceptor driver using tcpdump piped to a perl script to put the packets in one string then send it to weewx interceptor driver using using LWP::UserAgent that seamed to work tcpdump -A -n -p -l -i eth0 -s0 -W tcp dst port 80 | stdbuf -oL strings -n8 | stdbuf -oL grep "&" | t

Re: [weewx-user] Re: External site reporting irregular timing schedule

Unfortunately, you stopped the log 10 seconds before the next record was due, so we only saw one post, the one for 0955, which showed up on PWS. Let weewx run longer, and make sure at least a couple of posts are included. Attaching the syslog is fine. -tk On Sat, Oct 15, 2016 at 10:17 AM, Tim P

Re: [weewx-user] Re: External site reporting irregular timing schedule

And here's my PWS station that shows the upload times as being erratic. http://www.pwsweather.com/obs/HHFRLND11.html -- 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 emai

Re: [weewx-user] Re: External site reporting irregular timing schedule

(facepalm) Deleted the "]" at the end of "[Extras]" when I was adding a radar image... On Sat, Oct 15, 2016 at 10:17 AM, Tim Phillips wrote: > Here's what looks like an issue for the standard report: > > "Oct 15 09:40:06 raspberrypi weewx[754]: acurite: Found station at bus=001 > device=004

[weewx-user] Re: External site reporting irregular timing schedule

Here's what looks like an issue for the standard report: "Oct 15 09:40:06 raspberrypi weewx[754]: acurite: Found station at bus=001 device=004 Oct 15 09:40:06 raspberrypi weewx[754]: manager: added record 2016-10-15 09:40:00 PDT (1476549600) to database 'weewx.sdb' Oct 15 09:40:06 raspberrypi we

[weewx-user] Issues with new FW in Acu-Link bridge and the interceptor driver

I've had a weewx system running for a couple years uses a variant of the hackulink driver that I had created (used libpcap python libraries to directly sniff the traffic passing through the router (linux based distro running on a laptop) without needing to have an external ngrep or tcpdump comm

[weewx-user] Re: Froggit ws8800 / Hideki TF966

Hi. I take the te923 driver. lsusb say: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 005 Device 001: ID 1d6b:0001 Linux

[weewx-user] Re: $station.uptime should not reset to Zero when weewx is only doing a reload

You can also use wee_reports to see your 'quick' changes in the templates etc immediately (not waiting for the next report cycle) without reloading or restarting weewx. http://www.weewx.com/docs/utilities.htm#wee_reports_utility Regards, Steve. On Friday, 14 October 2016 20:18:31 UTC+11, erbe

Re: [weewx-user] Re: Version 3.6.1

On Saturday, October 15, 2016 at 12:58:14 AM UTC-4, Liz wrote: > > On Fri, 14 Oct 2016 04:51:37 -0700 (PDT) > mwall wrote: > > > liz, > > > > could you provide more detail about the process you went through so i > > can duplicate the behavior? > > Weewx 3.5.0 installed by deb file upgrade >

Re: [weewx-user] Errors during the report generation

Pier, I've got to say, that if Tom reckons he's found a bug in the code that may be causing it, I've got to defer to him. I can glean a few errors by reading the logs - carefully - but I really know naught when it comes to those who've actually written and therefore understand the code! And havi

[weewx-user] Re: Froggit ws8800 / Hideki TF966

On Saturday, October 15, 2016 at 7:18:23 AM UTC-4, wp180 wrote: > > Is it possible to use the software with a FROGGIT WS8800? Its the same as > HIDEKI TF966. > I tried it some times, but until now its not working here. > mika, did you try the te923 driver in weewx? with the station connected

Re: [weewx-user] Errors during the report generation

Your OS may care if you pulled the plug, but weewx does not. Any temporary files created by it will be written over at the next file generation. The log confirms that somehow the filename is being presented in Unicode (instead as an ordinary string). Now we need to figure out why. Again, please r

Re: [weewx-user] Windows Development

That's encouraging! We'll see whether the drivers are so simple! :-) Your port looks pretty straightforward. Any idea why the delete=False flag is needed in setup.py? Is that a Windows thing? I've been meaning to encapsulate the logging. The various weewx modules vary in how they handle it. Some

[weewx-user] Froggit ws8800 / Hideki TF966

Hi. Is it possible to use the software with a FROGGIT WS8800? Its the same as HIDEKI TF966. I tried it some times, but until now its not working here. Any hints? Regards Mika -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe fro

[weewx-user] Windows Development

Hi All, I have been working on changes required to run an out of the box Weewx installation on Windows. I have been able to achieve install using setup.py and running the simulator with minimal changes, the main being writing a *syslog* wrapper. See https://github.com/dcapslock/weewx/tree/windo

[weewx-user] Re: Version 3.6.1

I set up the apt repo and updated using it and everything worked as expected. Thanks for the repo! On Thursday, October 13, 2016 at 5:24:35 PM UTC-6, Tom Keffer wrote: > > Oh, I should mention: weewx now has an apt repository! > > Installs and upgrades can be done using apt-get. Follow the direc