Yes I did, seems we had our wires crossed, I was waiting for the debug=1
log from startup? wee_debug tells me what should happen, debug=1 startup
log tells me what did happen. A couple more questions/requests; do these
two errors occur on every report cycle or just now and then? If all the
time could you run weeWX directly
<http://weewx.com/docs/usersguide.htm#Running_directly> and post the screen
output, only need to see the REC: line and a few LOOP: lines before the
On Friday, 2 February 2018 23:50:58 UTC+10, Rune Laegreid wrote:
> look not lokk :-)
> fredag 2. februar 2018 14.49.35 UTC+1 skrev Rune Laegreid følgende:
>> Did you have a chance to lokk at my debug report?
>> lørdag 27. januar 2018 23.28.29 UTC+1 skrev gjr80 følgende:
>>> You have errors from at last 2 extensions in the log extract you
>>> provided so I am thinking there may be a wider issue here. So we can get a
>>> clear picture of what your are running can you please post a wee_debug (
>>> http://weewx.com/docs/utilities.htm#wee_debug_utility) report, make
>>> sure you check the report for any sensitive info before posting. Can you
>>> also set debug=1 in weewx.conf then restart weeWX and post the log from
>>> startup until a couple of archive records have been processed.
>>> One other thing, I have found these sorts of errors frequently occur
>>> when some observations are missing ie None. I see part of you log extract
>>> (22:02:03-22:02:07) seems to indicate this, apart from the log errors is
>>> your station functioning as it should and displaying all observations?
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.