rrect, and which are you actually using/trying to use??
>
>
> On Saturday, 10 February 2018 03:03:57 UTC+2, Sam Roza wrote:
>
>> Hello All,
>>
>> I re-installed due to a memory card issue, and I have weewx running and
>> reporting out to CWOP and WU, etc. That
Given the cost and resource use, you really con't go wrong with a RPi. I am
using a 3b. So cheap, and easy, and weewx installs and runs perfectly.
-SR
On Wednesday, January 24, 2018 at 11:38:36 AM UTC-8, Alec Bennett wrote:
>
> I've been running weeWX on a Beaglebone Black for about a year
Hello All,
I re-installed due to a memory card issue, and I have weewx running and
reporting out to CWOP and WU, etc. That's all good.
What it's not doing is creating (more accurately copying) files to the
/var/www/html/weewx directory. I see this in my logs:
Feb 9 08:20:51 raspberrypi
the bootstrap .pngs - maybe for the very reason
> that you have discovered!!! I just cannot remember!!
> .
>
> On Monday, 4 September 2017 08:11:53 UTC+3, Sam Roza wrote:
>
>> Andrew,
>>
>> All I did to Bootstrap was install it using the wee_extension command and
e your
> problem
>
> I am using Bootstrap, and use fontsizes of 14 - 18 with no problems. Have
> attached my skins/Images/skin.conf file, and also skins/Bootstrap/skin.conf
>
>
>
>
>
> On Monday, 4 September 2017 01:32:21 UTC+3, Sam Roza wrote:
>
>> Hello All,
&g
Hello All,
Working with the Bootstrap skin so that I could get some additional
historical info out of WeeWx. I have loaded it and the skin page renders,
and I have graphs and charts and historical data.
Unfortunately, the labels and measurements on both X and Y axes are so tiny
that I cannot
That fixed it, Matt.
Many thanks, again.
-SR
On Sunday, December 11, 2016 at 11:59:30 AM UTC-8, mwall wrote:
>
> On Sunday, December 11, 2016 at 2:24:53 PM UTC-5, Sam Roza wrote:
>>
>> I'm very thankful for the attentiveness you show when issues come up.
>>
>> W
-8, mwall wrote:
>
> On Sunday, December 11, 2016 at 11:23:51 AM UTC-5, Sam Roza wrote:
>>
>> But the issue of proper processing is still there. I see the POST and to
>> my eye it looks good. There are no errors and indeed-interceptor and weewx
>> seem to say t
, to me...
Let me clean this up and see if it works everything out.
-SR
On Saturday, December 10, 2016 at 3:13:16 PM UTC-8, mwall wrote:
>
> On Saturday, December 10, 2016 at 4:46:15 PM UTC-5, Sam Roza wrote:
>>
>> Hi Matt,
>>
>> I use a simple ngrep script that
Hi Matt,
I use a simple ngrep script that you and I worked out. I worked reliably for
the last few months. I have been teeing the packets out to a file, and in my
previous reply, you can see the 'wfor' shows up in there. After the tee,
it's sent to interceptor. Looking at the weewx.log
y and see if I can't unravel this.
-SR
On Saturday, December 10, 2016 at 8:34:32 AM UTC-8, Sam Roza wrote:
>
> Ah yeah. It wasn't obvious earlier what was missing, but there it is:
>
> Dec 4 10:40:04 raspberrypi weewx[17396]: interceptor: ServerThread: POST:
> mac=0004a369e0d6
I am having a baro problem:
~~~
Dec 4 21:33:03 raspberrypi weewx[4795]: interceptor: MainThread: parse
failed for
mac=0004a369e0d6=c2=0=0=0=1809==1013=0:
dictionary update sequence element #9 has length 1; 2 is required
Dec 4 21:56:03 raspberrypi weewx[4795]: interceptor: MainThread:
nterceptor: MainThread: mapped
packet: {'barometer': 1012.0, 'usUnits': 17, 'dateTime': 1480299016}
~~~
-SR
On Sunday, November 27, 2016 at 3:44:04 PM UTC-8, mwall wrote:
>
> On Sunday, November 27, 2016 at 6:28:41 PM UTC-5, Sam Roza wrote:
>>
>> BTW, I find it interesting that
the equipment reports is never the same as the data that WU reports.
For instance, the final reading above is 1012 from the station, but WU
reports is as what is probably a more accurate 30.08". 1012 looks to be
29.77"...
-SR
On Sunday, November 27, 2016 at 1:26:38 PM UTC-8, Sam
or not?
~~~
T 192.168.1.73:2850 -> 54.228.205.96:80 [AP]
mac=0004a369e0d6=84=d6=0=0=0=54=0=16.0=3=1
~~~
_SR
On Thursday, November 24, 2016 at 10:03:44 AM UTC-8, Sam Roza wrote:
>
> OK, so there were several hours again where I recorded no data into weewx,
> out to WU/CWOP, but looking
:
>
> On Friday, November 18, 2016 at 1:28:25 PM UTC-5, Sam Roza wrote:
>>
>> I find it odd that both devices were experiencing difficulties at exactly
>> the same time, don't you? That's way too coincidental. Devices having
>> issues shouldn't have issues together.
pe(s) for +=: 'float' and 'str'
Nov 17 09:56:34 raspberrypi weewx[9989]: Exiting.
~~~
I've reverted for now.
-SR
On Thursday, November 17, 2016 at 9:52:23 AM UTC-8, Sam Roza wrote:
>
> Gotcha. Just updated. Will report back.
>
> -SR
>
> On Thursday, November 17, 2016 at 8
Gotcha. Just updated. Will report back.
-SR
On Thursday, November 17, 2016 at 8:31:19 AM UTC-8, mwall wrote:
>
> Sam,
>
> update to the latest interceptor. It has the right uv mapping for lw30x
>
> m
>
>
--
You received this message because you are subscribed to the Google Groups
Matt, it looks like I am running interceptor .12.
-SR
On Wednesday, November 16, 2016 at 7:13:38 PM UTC-8, mwall wrote:
>
> sam,
>
> the database field names are case sensitive.
>
> the default mapping for the oregon scientific lw30x is UV = uvh.?:*.*
>
> which version of the driver are you
Hello All,
I have weewx 3.6.2 running. All is well, but I don't seem to have graphs
produced for UV data collected. Is there something that needs to be done? I
see the if statements in the skin.conf, and the data is collected by the
interceptor ( I can see the collected packets in syslog).
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!)-t
Unfortunately, it's repeatable. The data builds up, and then all at once,
it is fed into weewx, and the program crashes:
~~~
Oct 8 21:29:15 raspberrypi kernel: [ 110.920747] device eth0 entered
promiscuous mode
Oct 8 21:29:20 raspberrypi weewx[735]: interceptor: MainThread: empty queue
Oct
On Saturday, October 8, 2016 at 6:57:49 PM UTC-7, mwall wrote:
>
> btw, here it is with a better sed expression for the filter:
>
> ngrep -l -q -d eth0 '0004a369e0d6' | sed '/mac=/!d' | xargs -n 1 curl
> http://localhost: -s -d
>
> m
>
Ah yes. That filter is a bit more efficient, isn't it?
On Saturday, October 8, 2016 at 2:44:15 PM UTC-7, mwall wrote:
>
>
>
> On Saturday, October 8, 2016 at 5:23:30 PM UTC-4, Sam Roza wrote:
>>
>>
>>
>> On Saturday, October 8, 2016 at 1:53:31 PM UTC-7, mwall wrote:
>>>
>>> On Saturda
On Saturday, October 8, 2016 at 1:53:31 PM UTC-7, mwall wrote:
>
> On Saturday, October 8, 2016 at 4:29:20 PM UTC-4, Sam Roza wrote:
>>
>>
>> With sed command, it strips the unwanted data from the output, but for
>> some reason, it's not working. I've trie
Hello All!
I've got weewx running on an rPi3, and I have the interceptor set up. All
starts correctly, and the port is open, etc. The issue is that none of the
packet collection methods seems to work. I am receiving error 400 from both
tcpdump as well as ngrep commands that are piped to nc:
#
26 matches
Mail list logo
