Re: [weewx-user] Re: WeeWX Interceptor: Rain not registering

[kan6526]

root@debian6-ANN:~# /etc/init.d/weewx stop

---/var/log/syslog 
--
Nov 22 13:51:31 debian6-ANN weewx[5104]: interceptor: MainThread: ignored 
parameter softwaretype=WeatherSmart%V1.7.0
Nov 22 13:51:31 debian6-ANN weewx[5104]: interceptor: ServerThread: sniff: 
skip 00 00 00 00 00 00
Nov 22 13:51:31 debian6-ANN weewx[5104]: interceptor: MainThread: ignored 
parameter action=updateraw
Nov 22 13:51:46 debian6-ANN weewx[5104]: engine: Received signal TERM (15).
Nov 22 13:51:46 debian6-ANN weewx[5104]: engine: Main loop exiting. 
Shutting engine down.
Nov 22 13:51:46 debian6-ANN weewx[5104]: interceptor: MainThread: shutting 
down server thread
Nov 22 13:51:46 debian6-ANN weewx[5104]: interceptor: ServerThread: sniff: 
timestamp=1511329906.99 pktlen=60 data=9c 5c 8e c0 dc ea 5c cf 7f 23 ba 2a 
08 00 45 00 00 2c ab b7 00 00 ff 06 6c 5e c0 a8 02 fc 34 23 ab ee 5b 65 00 
50 ef c8 fd 92 00 00 00 00 60 02 16 d0 94 8f 00 00 02 04 05 b4 00 00
Nov 22 13:51:46 debian6-ANN weewx[5104]: interceptor: MainThread: stop 
sniff server
Nov 22 13:51:46 debian6-ANN weewx[5104]: interceptor: ServerThread: sniff: 
skip 02 04 05 b4 00 00
Nov 22 13:51:46 debian6-ANN weewx[5104]: engine: Terminating weewx version 
3.7.1
Nov 22 13:51:46 debian6-ANN weewx[5104]:   Traceback (most recent 
call last):
Nov 22 13:51:46 debian6-ANN weewx[5104]: File 
"/usr/share/weewx/weewx/engine.py", line 871, in main
Nov 22 13:51:46 debian6-ANN weewx[5104]:   engine.run()
Nov 22 13:51:46 debian6-ANN weewx[5104]: File 
"/usr/share/weewx/weewx/engine.py", line 187, in run
Nov 22 13:51:46 debian6-ANN weewx[5104]:   for packet in 
self.console.genLoopPackets():
Nov 22 13:51:46 debian6-ANN weewx[5104]: File 
"/usr/share/weewx/user/interceptor.py", line 1986, in genLoopPackets
Nov 22 13:51:46 debian6-ANN weewx[5104]:   pkt = 
self._device.parser.parse(data)
Nov 22 13:51:46 debian6-ANN weewx[5104]: File 
"/usr/share/weewx/user/interceptor.py", line 1031, in parse
Nov 22 13:51:46 debian6-ANN weewx[5104]:   logdbg("ignored 
parameter %s=%s" % (n, data[n]))
Nov 22 13:51:46 debian6-ANN weewx[5104]: File 
"/usr/share/weewx/user/interceptor.py", line 227, in logdbg
Nov 22 13:51:46 debian6-ANN weewx[5104]:   
logmsg(syslog.LOG_DEBUG, msg)
Nov 22 13:51:46 debian6-ANN weewx[5104]: File 
"/usr/share/weewx/user/interceptor.py", line 224, in logmsg
Nov 22 13:51:46 debian6-ANN weewx[5104]:   
(threading.currentThread().getName(), msg))
Nov 22 13:51:46 debian6-ANN weewx[5104]: File 
"/usr/share/weewx/weewx/engine.py", line 794, in sigTERMhandler
Nov 22 13:51:46 debian6-ANN weewx[5104]:   raise Terminate
Nov 22 13:51:46 debian6-ANN weewx[5104]:   Terminate
 

-- 
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: Limiting weewx logging only to error/fail

[mwall]

On Tuesday, November 21, 2017 at 4:36:10 PM UTC-5, Daniel Jönsson wrote:
>
> I cant seem to get it to work. And I cant find it in the user guide (
> http://www.weewx.com/docs/usersguide.htm) were to put it.
> I would also very much like to only have errors in my log.
>>
>>
>>
commit 6b461c9 

 applies 
to reports

use it like this:

[StdReport]
  log_success = False
  log_failure = True

then optionally specialize for individual reports.  for example, to log 
success for StandardReport but not for others:

[StdReport]
  log_success = False
  log_failure = True
...
  [[StandardReport]]
log_success = True
...
  [[AnotherReport]]
...

this pattern should also work for uploaders:

[StdRESTful]
  log_succes = False
  log_failure = True

we probably should do it for the archive service as well, which would 
probably indicate that one should be able to specify log_success and 
log_failure at the root of weewx.conf then override for each service as 
necessary.

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.

Re: [weewx-user] Question

[Thomas Keffer]

You can search either through the Google Groups website
, or through the
mail-archive
service .

-tk

On Tue, Nov 21, 2017 at 3:34 PM, Jerry Kutche  wrote:

> Is there a way to search for keywords on here?
> Thanks
> Jerry
>
> --
> 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.
>

-- 
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: Limiting weewx logging only to error/fail

[Daniel Jönsson]

I cant seem to get it to work. And I cant find it in the user guide 
(http://www.weewx.com/docs/usersguide.htm) were to put it.
I would also very much like to only have errors in my log.

Den torsdag 14 april 2016 kl. 00:42:38 UTC+2 skrev mwall:
>
> On Wednesday, April 13, 2016 at 12:00:49 PM UTC-4, vince wrote:
>>
>> Great stuff - is there any plan/way to have a global log_success or 
>> global log_failure that the sections can supersede perhaps, rather than 
>> requiring setting log_success=false in a bunch of places ?
>>
>
> there is now :)
>
> https://github.com/weewx/weewx/issues/116 
>

-- 
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, raspberry pi and sd cards - the lifetime for card

[Jerry Kutche]

I Use only Samsung 32GB Evo + Nothing else ever I have had some in service 
for years running 24/7

On Monday, October 31, 2016 at 4:34:25 AM UTC-4, Jacek Skowroński wrote:
>
> Hi,
> How does Your sd card "live" in raspberry pi?
> On my example I lost 5 cards already - all of them by 3-4months long.
> Is it normal?
>
> Yust now I'm looking to get rid of sd cards and write down data somewhere 
> else.
> Any topics? Any hints?
>

-- 
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] Weewx APRS extension

[Jerry Kutche]

I had this working?? How do you get it to start with weewx Seems to have 
stopped creating the aprs.pkt file..

Thanks

Raspbian 9

73 jerry n9lya

-- 
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: Meteotemplate Uploader possible bug

[Bill M]

I've changed the battery so the problem has disappeared for now!

I don't think I explained myself clearly, weewx appeared to be showing the 
correct data, ie null or nothing, the default html pages showed NA for all 
outside readings when I suspect the ISS was down due to the battery 
failure. Data sent to WU, AWEKAS, PWS , etc also show blanks.

However the data sent to meteotemplate via the api interface always showed 
the last valic current value!

It's nothing to worry about since this hopefully only occurs every couple 
of years, I was more curious than anything!

Bill

I should have taken some screen shots but didn't sorry!

-- 
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] Re: Weewx crashing

[Thomas Keffer]

Good point. I went with

val != val


Commit  0bce71e



-tk

On Mon, Nov 20, 2017 at 9:47 PM, Thomas Carlin 
wrote:

> True, didn't think about that.  It's dirty, but
>
> str(val) == 'nan'
>
> would work also.  Aside from isnan(), that is the most readable solution
> that I am aware of.
>
>
> On Monday, November 20, 2017 at 8:33:28 PM UTC-7, gjr80 wrote:
>>
>> Might have to be careful we don't break python 2.5 compatibility, I think
>> isnan() was introduced in python 2.6.
>>
>> 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.
>

-- 
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] Re: daily graphs stuck on an old date

[Andrew Milner]

Sometimes the obvious proves to be the 'solution'!!  Gets harder trying to
work out why the cache clear worked whilst the refresh didn't though!!!

Glad to hear you're sorted now though.  From experience it's often best to
put weewx itself at the end of any list of possible causes!!




On 21 November 2017 at 10:47, Richard Beare  wrote:

> Well, this is embarrassing. Data is going in, and timestamp is appropriate:
>
> SELECT dateTime, outTemp FROM archive ORDER BY dateTime DESC LIMIT 20;
>
> 1511253600|84.08
>
> as.POSIXct(1511253600, origin = "1970-01-01")
>
> [1] "2017-11-21 19:40:00 AEDT"
>
>
> Repeated refresh of page from chrome, and restarts of chrome didn't change
> the image in the web page. But using a different browser and viewing the
> graph images manually showed that they're actually OK. Explicitly clearing
> the image cache in chrome eventually did the trick.
>
> I'll go and hide now...
>
> Thanks for all the prompt help.
>
>
>
>
> On Tue, Nov 21, 2017 at 4:00 PM, Richard Beare 
> wrote:
>
>> Have done the refreshing, but not separate viewing. Will confirm.
>> Thanks
>>
>> On Tue, Nov 21, 2017 at 3:51 PM, Andrew Milner <
>> andrew.s.r.mil...@gmail.com> wrote:
>>
>>> An obvious one - but it's caught me out before - have you forced a page
>>> reload in the browser and/or have you viewed the .png file directly via a
>>> file explorer?
>>>
>>> On Tuesday, 21 November 2017 05:16:42 UTC+2, Richard Beare wrote:

 OK, thanks, I'll check that tonight.

 On Tue, Nov 21, 2017 at 1:51 PM, gjr80  wrote:

> max(dateTime) will just show you the most recent archive record
> timestamp, what we need to see is whether there is any observational data
> being recorded in the archive. It is quite possible that no observational
> data is being recorded for some reason and hence the generated plots show
> no data. Weekly and greater plots display some form of aggregate data so
> they may well still show something whilst the daily plot does not.
>
> Gary
>
> On Tuesday, 21 November 2017 11:37:17 UTC+10, Richard Beare wrote:
>>
>> I'm not in front of the machine at the moment, but I did check the
>> most recent time, and it matched the current time.
>>
>> from memory:
>>
>> select max(timeDate) from archive;
>>
>> which I then converted to a readable form (with R). It was definitely
>> today, not the stuck date of 3 days ago.
>>
>> Mysterious!
>>
>> On Tue, Nov 21, 2017 at 12:18 PM, gjr80  wrote:
>>
>>> On Tuesday, 21 November 2017 07:27:15 UTC+10, Richard Beare wrote:


 At this point I'm starting to think I need to reinstall, but I hope
 I'm missing something basic.


>>> Don't go doing this, it is seldom required and is usually a waste of
>>> your and our time. If forcing regeneration by deletion has not helped 
>>> then
>>> I would have a look at what is in your database, are you getting current
>>> data in there or not? Assuming you are using SQLite and not MySQL try 
>>> the
>>> following (assumes sqlite3 is installed, if not you need something
>>> like sudo apt-get install sqlite3 to install it, also change paths
>>> to suit your install):
>>>
>>> $ sqlite3 /home/weewx/archive/weewx.sdb
>>> sqlite> SELECT STRFTIME('%d-%m-%Y %H:%M:%S', datetime(dateTime,
>>> 'unixepoch')), outTemp FROM archive ORDER BY dateTime DESC LIMIT 20;
>>> sqlite> .quit
>>>
>>> What does the SQLite query return? This will show whether you in
>>> fact have current data being saved to archive or not.
>>>
>>> Gary
>>>
>>> --
>>> You received this message because you are subscribed to a topic in
>>> the Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>>> pic/weewx-user/Qkb5l9fjk9Q/unsubscribe.
>>> To unsubscribe from this group and all its topics, 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 a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/to
> pic/weewx-user/Qkb5l9fjk9Q/unsubscribe.
> To unsubscribe from this group and all its topics, 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 a topic in the
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>>> pic/weewx-user/Qkb5l9fjk9Q/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> 

Re: [weewx-user] Re: daily graphs stuck on an old date

[Richard Beare]

Well, this is embarrassing. Data is going in, and timestamp is appropriate:

SELECT dateTime, outTemp FROM archive ORDER BY dateTime DESC LIMIT 20;

1511253600|84.08

as.POSIXct(1511253600, origin = "1970-01-01")

[1] "2017-11-21 19:40:00 AEDT"


Repeated refresh of page from chrome, and restarts of chrome didn't change
the image in the web page. But using a different browser and viewing the
graph images manually showed that they're actually OK. Explicitly clearing
the image cache in chrome eventually did the trick.

I'll go and hide now...

Thanks for all the prompt help.




On Tue, Nov 21, 2017 at 4:00 PM, Richard Beare 
wrote:

> Have done the refreshing, but not separate viewing. Will confirm.
> Thanks
>
> On Tue, Nov 21, 2017 at 3:51 PM, Andrew Milner <
> andrew.s.r.mil...@gmail.com> wrote:
>
>> An obvious one - but it's caught me out before - have you forced a page
>> reload in the browser and/or have you viewed the .png file directly via a
>> file explorer?
>>
>> On Tuesday, 21 November 2017 05:16:42 UTC+2, Richard Beare wrote:
>>>
>>> OK, thanks, I'll check that tonight.
>>>
>>> On Tue, Nov 21, 2017 at 1:51 PM, gjr80  wrote:
>>>
 max(dateTime) will just show you the most recent archive record
 timestamp, what we need to see is whether there is any observational data
 being recorded in the archive. It is quite possible that no observational
 data is being recorded for some reason and hence the generated plots show
 no data. Weekly and greater plots display some form of aggregate data so
 they may well still show something whilst the daily plot does not.

 Gary

 On Tuesday, 21 November 2017 11:37:17 UTC+10, Richard Beare wrote:
>
> I'm not in front of the machine at the moment, but I did check the
> most recent time, and it matched the current time.
>
> from memory:
>
> select max(timeDate) from archive;
>
> which I then converted to a readable form (with R). It was definitely
> today, not the stuck date of 3 days ago.
>
> Mysterious!
>
> On Tue, Nov 21, 2017 at 12:18 PM, gjr80  wrote:
>
>> On Tuesday, 21 November 2017 07:27:15 UTC+10, Richard Beare wrote:
>>>
>>>
>>> At this point I'm starting to think I need to reinstall, but I hope
>>> I'm missing something basic.
>>>
>>>
>> Don't go doing this, it is seldom required and is usually a waste of
>> your and our time. If forcing regeneration by deletion has not helped 
>> then
>> I would have a look at what is in your database, are you getting current
>> data in there or not? Assuming you are using SQLite and not MySQL try the
>> following (assumes sqlite3 is installed, if not you need something
>> like sudo apt-get install sqlite3 to install it, also change paths
>> to suit your install):
>>
>> $ sqlite3 /home/weewx/archive/weewx.sdb
>> sqlite> SELECT STRFTIME('%d-%m-%Y %H:%M:%S', datetime(dateTime,
>> 'unixepoch')), outTemp FROM archive ORDER BY dateTime DESC LIMIT 20;
>> sqlite> .quit
>>
>> What does the SQLite query return? This will show whether you in fact
>> have current data being saved to archive or not.
>>
>> Gary
>>
>> --
>> You received this message because you are subscribed to a topic in
>> the Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/weewx-user/Qkb5l9fjk9Q/unsubscribe.
>> To unsubscribe from this group and all its topics, 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 a topic in the
 Google Groups "weewx-user" group.
 To unsubscribe from this topic, visit https://groups.google.com/d/to
 pic/weewx-user/Qkb5l9fjk9Q/unsubscribe.
 To unsubscribe from this group and all its topics, 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 a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/weewx-user/Qkb5l9fjk9Q/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx-user+unsubscr...@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.