Re: [weewx-user] Updating database error - "weedb.OperationalError: database is locked"

[gjr80]

Ok, must have been some port filtering on the internet I was using. I suspect 
that the only data in your database is 2nd December onwards only, look at all 
your month and year highs/lows, they are identical. December 2017 must have 
been a memorable month, or you only have data for December 2017. There must be 
an early record in there somewhere to give you all those empty pages, eg if you 
have one record for 1am 1 January 2016 you will get blanks pages for all in 
between. 1 January 2016 and 2 December 2017. I will drop you a few queries to 
run shortly to see exactly what is going on, probably going to have to merge 
your backup and part of your current data.

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.

Re: [weewx-user] Updating database error - "weedb.OperationalError: database is locked"

[Andrew Milner]

Gary - the link works fine for me so it must be your internet

The issue seems to be that when regenerating the NOAA files they all now 
exist(ie the dropdown is populated), but the data content for all months 
and years up to December 2nd 2017 is missing - the reports are just 
blanks.  Looking at the plots there appears to be data for earlier periods 
in the database (apart from what looks like a glitch around January 2016)

'Tis an interesting one which I'll leave to you - 'cos I don't have a clue 
what could cause this!!  I assume it must be something odd in the DB - 
maybe the summaries need recreating from the archive or something like 
that.  


On Tuesday, 5 December 2017 06:42:40 UTC+2, gjr80 wrote:

> Joe,
>
> I am out at the moment but I am getting unreachable on that link you 
> provided. Could be my internet though.
>
> 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.

Re: [weewx-user] Updating database error - "weedb.OperationalError: database is locked"

[Joe Brockway]

Gary,

What I meant when I said "all the reports regenerated" was the text files 
in the NOAA folder were re-created.

Here is the link to the almanac page on my weewx server. 
http://73.14.239.120:32983/weewx/almanac.html

If you look at the dropdowns for the monthly and yearly summaries (upper 
right corner) there is no data. The problem is now worse that it was this 
morning. 

I have the database backing up every night at midnight to a USB stick on 
the raspberry pi. I did save the database off the USB stick on Nov 26th. 

Hopefully, there is a way to fix the database. Or I could just restore the 
database from the Nov 26th copy.

-Joe
 

On Monday, December 4, 2017 at 7:08:55 PM UTC-7, gjr80 wrote:
>
> Hi,
>
> So when you say *'All the reports regenerated*' do you mean that you now 
> have month and year reports for all months/years you expect and you are 
> just missing all data for 1st December or do you mean something else? We 
> need to be clear on what results you have now as that will determine how to 
> deal with the issue. If you have all reports you expect you should have and 
> are indeed missing output for 1st December then the issue is likely with 
> your database (given that you just forced a complete regenration).
>
> Gary
>
> On Tuesday, 5 December 2017 11:34:20 UTC+10, Joe Brockway wrote:
>>
>> Yes. I am referring to the NOAA reports. 
>>
>> I did stop weewx and delete the NOAA directory in /var/www/weewx. I 
>> started weewx. All the reports regenerated. 
>>
>> However, My yearly report for 2017 only has information for December. 
>> Plus the December 2017 report only has information from December 2 and 
>> forward. I did update weewx to 3.8.0 on December 2nd. My guess is I messed 
>> something up when i updated weewx. Could the issue be in my database? If so 
>> might they be a way to fix the database?
>>
>> -joe
>>
>> On Monday, December 4, 2017 at 5:39:31 AM UTC-7, Tom Keffer wrote:
>>>
>>> I'm not sure what you mean by CLIMATOLOGICAL data. Do you mean the NOAA 
>>> reports? If so, they are generated on a forward going basis: only reports 
>>> more recent than the last one you have will be generated. So, if you're 
>>> missing earlier reports, delete the directory and all will be regenerated.
>>>
>>> -tk
>>>
>>> On Mon, Dec 4, 2017 at 6:33 AM, Joe Brockway  wrote:
>>>
 Well now I have a new issue.

 My CLIMATOLOGICAL data for 2017 only shows December. All the data is 
 there for the other past years. And the data was there before I ran the 
 wee_database command.

 Any suggestions on how to fix this?

 --
 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+...@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: Setting up weewx.conf file

[gjr80]

Ray,

Just to clarify on what I am after. The log extract that I want to see is 
from when you start weeWX until 10-15 minutes after you started weeWX, it 
looks like you provided an extract from after 15-20 minutes and then for 
only a few minutes. If this is the case and since there is no mention of 
weeWX it looks like weeWX existed earlier for some reason. I want to see 
the weeWX startup seqence and what happens when a couple of archive records 
are produced (if we get that far). I woudl expect to see something like 
this:

Dec  5 12:15:56 stretch21 weewx[1388]: engine: Initializing weewx version 
3.8.0
Dec  5 12:15:56 stretch21 weewx[1388]: engine: Using Python 2.7.13 (default, 
Jan 19 2017, 14:48:08) #012[GCC 6.3.0 20170118]
Dec  5 12:15:56 stretch21 weewx[1388]: engine: Platform Linux-4.9.0-4-amd64-
x86_64-with-debian-9.2
Dec  5 12:15:56 stretch21 weewx[1388]: engine: Locale is 'en_AU.UTF-8'
Dec  5 12:15:56 stretch21 weewx[1388]: engine: pid file is /var/run/weewx.
pid
Dec  5 12:15:56 stretch21 weewx[1378]: Starting weewx weather system: weewx.
Dec  5 12:15:57 stretch21 weewx[1392]: engine: Using configuration file /
home/weewx/weewx.conf
Dec  5 12:15:57 stretch21 weewx[1392]: engine: Loading station type 
Simulator (weewx.drivers.simulator)
Dec  5 12:15:57 stretch21 weewx[1392]: engine: StdConvert target unit is 0x1
Dec  5 12:15:57 stretch21 weewx[1392]: wxcalculate: The following values 
will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, 
windrun=prefer_hardware, heatindex=prefer_hardware, maxSolarRad=
prefer_hardware, humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Dec  5 12:15:57 stretch21 weewx[1392]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Dec  5 12:15:57 stretch21 weewx[1392]: engine: Archive will use data 
binding wx_binding
Dec  5 12:15:57 stretch21 weewx[1392]: engine: Record generation will be 
attempted in 'hardware'
Dec  5 12:15:57 stretch21 weewx[1392]: engine: Using archive interval of 300 
seconds (specified in weewx configuration)
Dec  5 12:15:57 stretch21 weewx[1392]: engine: Using binding 'wx_binding' 
to database 'weewx.sdb'
Dec  5 12:15:57 stretch21 weewx[1392]: manager: Starting backfill of daily 
summaries
Dec  5 12:15:57 stretch21 weewx[1392]: restx: StationRegistry: Registration 
not requested.
Dec  5 12:15:57 stretch21 weewx[1392]: restx: Wunderground: Posting not 
enabled.
Dec  5 12:15:57 stretch21 weewx[1392]: restx: PWSweather: Posting not 
enabled.
Dec  5 12:15:57 stretch21 weewx[1392]: restx: CWOP: Posting not enabled.
Dec  5 12:15:57 stretch21 weewx[1392]: restx: WOW: Posting not enabled.
Dec  5 12:15:57 stretch21 weewx[1392]: restx: AWEKAS: Posting not enabled.
Dec  5 12:15:57 stretch21 weewx[1392]: engine: Starting up weewx version 3.8
.0
Dec  5 12:15:57 stretch21 weewx[1392]: engine: Clock error is -0.02 seconds 
(positive is fast)
Dec  5 12:15:57 stretch21 weewx[1392]: engine: Starting main packet loop.
Dec  5 12:20:14 stretch21 weewx[1392]: manager: Added record 2017-12-05 12:
20:00 AEST (1512440400) to database 'weewx.sdb'
Dec  5 12:20:14 stretch21 weewx[1392]: manager: Added record 2017-12-05 12:
20:00 AEST (1512440400) to daily summary in 'weewx.sdb'
Dec  5 12:20:14 stretch21 weewx[1392]: cheetahgenerator: Generated 0 files 
for report StandardReport in 0.01 seconds
Dec  5 12:20:14 stretch21 weewx[1392]: imagegenerator: Generated 0 images 
for StandardReport in 0.01 seconds
Dec  5 12:20:14 stretch21 weewx[1392]: copygenerator: copied 14 files to /
home/weewx/public_html

I have a dedicated weeWX log file whereas you use /var/log/syslog so there 
is a lot of other stuff in there in yours as well. If 10-15 minutes is too 
long then at least the startup and at least one complete archive/report 
cycle (again if it gets that far).

Gary

On Monday, 4 December 2017 23:19:57 UTC+10, Ray wrote:
>
> Stopped weewx then started, after 15-20 mins syslog shows this:
> Dec  4 10:58:13 ray-Aspire-5735 wpa_supplicant[832]: wlp3s0: SME: Trying 
> to authenticate with 70:4f:57:17:68:13 (SSID='TP-Link_Extender' freq=2417 
> MHz)
> .
>

-- 
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] Updating database error - "weedb.OperationalError: database is locked"

[gjr80]

Hi,

So when you say *'All the reports regenerated*' do you mean that you now 
have month and year reports for all months/years you expect and you are 
just missing all data for 1st December or do you mean something else? We 
need to be clear on what results you have now as that will determine how to 
deal with the issue. If you have all reports you expect you should have and 
are indeed missing output for 1st December then the issue is likely with 
your database (given that you just forced a complete regenration).

Gary

On Tuesday, 5 December 2017 11:34:20 UTC+10, Joe Brockway wrote:
>
> Yes. I am referring to the NOAA reports. 
>
> I did stop weewx and delete the NOAA directory in /var/www/weewx. I 
> started weewx. All the reports regenerated. 
>
> However, My yearly report for 2017 only has information for December. Plus 
> the December 2017 report only has information from December 2 and forward. 
> I did update weewx to 3.8.0 on December 2nd. My guess is I messed something 
> up when i updated weewx. Could the issue be in my database? If so might 
> they be a way to fix the database?
>
> -joe
>
> On Monday, December 4, 2017 at 5:39:31 AM UTC-7, Tom Keffer wrote:
>>
>> I'm not sure what you mean by CLIMATOLOGICAL data. Do you mean the NOAA 
>> reports? If so, they are generated on a forward going basis: only reports 
>> more recent than the last one you have will be generated. So, if you're 
>> missing earlier reports, delete the directory and all will be regenerated.
>>
>> -tk
>>
>> On Mon, Dec 4, 2017 at 6:33 AM, Joe Brockway  wrote:
>>
>>> Well now I have a new issue.
>>>
>>> My CLIMATOLOGICAL data for 2017 only shows December. All the data is 
>>> there for the other past years. And the data was there before I ran the 
>>> wee_database command.
>>>
>>> Any suggestions on how to fix this?
>>>
>>> --
>>> 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+...@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] Updating database error - "weedb.OperationalError: database is locked"

[Joe Brockway]

Yes. I am referring to the NOAA reports. 

I did stop weewx and delete the NOAA directory in /var/www/weewx. I started 
weewx. All the reports regenerated. 

However, My yearly report for 2017 only has information for December. Plus 
the December 2017 report only has information from December 2 and forward. 
I did update weewx to 3.8.0 on December 2nd. My guess is I messed something 
up when i updated weewx. Could the issue be in my database? If so might 
they be a way to fix the database?

-joe

On Monday, December 4, 2017 at 5:39:31 AM UTC-7, Tom Keffer wrote:
>
> I'm not sure what you mean by CLIMATOLOGICAL data. Do you mean the NOAA 
> reports? If so, they are generated on a forward going basis: only reports 
> more recent than the last one you have will be generated. So, if you're 
> missing earlier reports, delete the directory and all will be regenerated.
>
> -tk
>
> On Mon, Dec 4, 2017 at 6:33 AM, Joe Brockway  > wrote:
>
>> Well now I have a new issue.
>>
>> My CLIMATOLOGICAL data for 2017 only shows December. All the data is 
>> there for the other past years. And the data was there before I ran the 
>> wee_database command.
>>
>> Any suggestions on how to fix this?
>>
>> --
>> 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+...@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] [HELP] XML data without unit (raw?)

[Simone Urbani]

Thanks, works perfectly :)

Il giorno lunedì 4 dicembre 2017 22:53:38 UTC+1, Tom Keffer ha scritto:
>
> The *Customizing Guide*  has all 
> this information. 
>
> If you want temperature without the unit tag, then use 
> $current.inTemp.formatted. This will be a *string*. If you want a raw 
> number, that is, something you can do arithmetic with, then use 
> $current.inTemp.raw.
>
> See the section *Formatting Options 
> * for details.
>
> -tk
>
>
> On Mon, Dec 4, 2017 at 3:43 PM, Simone Urbani  > wrote:
>
>> Hello,
>> i migrated from wview to weewx.
>> My default skin was heavly customized...
>> now i'm trying to do the same with weewx.
>> I have a question:
>> i used an xml file to interface weewx to the domotics.
>> The problem is that the data are not in raw format.
>> I need that data are 
>> 15,8
>> and not 
>> 15,8°C
>>
>> This is the xml data:
>> $current.inTemp
>>
>> Thanks in advance and sorry for the question; i try to check the guide 
>> but didn't understand how to fix it
>>
>>
>> -- 
>> 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+...@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] [HELP] XML data without unit (raw?)

[Simone Urbani]

Hello,
i migrated from wview to weewx.
My default skin was heavly customized...
now i'm trying to do the same with weewx.
I have a question:
i used an xml file to interface weewx to the domotics.
The problem is that the data are not in raw format.
I need that data are 
15,8
and not 
15,8°C

This is the xml data:
$current.inTemp

Thanks in advance and sorry for the question; i try to check the guide but 
didn't understand how to fix it


-- 
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: Air quality sensors?

[Daniel Rich]

A friend of mine pointed me at the PurpleAir back when we had a valley full 
of smoke from the Napa/Sonoma fires a few months ago. This thread just 
convinced me to buy one. :-)  If no one else has tackled it by the time it 
shows up and I have time to install it, I'll look into adding a data source 
for it. It shouldn't be too hard to pull the JSON and convert it to a 2nd 
database in weewx (and in my InfluxDB as well).

On Monday, December 4, 2017 at 8:51:03 AM UTC-8, Thomas Carlin wrote:
>
> I have not.  It should be pretty easy with the google doc link above, and 
> the documentation provided by TK and the crew here: 
> http://www.weewx.com/docs/customizing.htm#Adding_2nd_source.  You would 
> just need to parse and sanitize the data coming in from the json output, 
> and stuff it into the database.  Once it is there, it's just a matter of 
> modifying the weewx UI to display as desired.
>
> I have a handful of other projects going right now, but this is definitely 
> on the list.  When it happens is anyone's guess.
>

-- 
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] Updating database error - "weedb.OperationalError: database is locked"

[Joe Brockway]

Yes I am referring to the NOAA reports.  I will delete everything in the 
NOAA directory and let it re-create the reports.

Thank you.

On Monday, December 4, 2017 at 5:39:31 AM UTC-7, Tom Keffer wrote:
>
> I'm not sure what you mean by CLIMATOLOGICAL data. Do you mean the NOAA 
> reports? If so, they are generated on a forward going basis: only reports 
> more recent than the last one you have will be generated. So, if you're 
> missing earlier reports, delete the directory and all will be regenerated.
>
> -tk
>
> On Mon, Dec 4, 2017 at 6:33 AM, Joe Brockway  > wrote:
>
>> Well now I have a new issue.
>>
>> My CLIMATOLOGICAL data for 2017 only shows December. All the data is 
>> there for the other past years. And the data was there before I ran the 
>> wee_database command.
>>
>> Any suggestions on how to fix this?
>>
>> --
>> 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+...@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] Updating database error - "weedb.OperationalError: database is locked"

[Joe Brockway]

Yes I am referring to the NOAA reports.  I will delete everything in the 
NOAA directory and let it re-create the reports.

Thanks you.

On Monday, December 4, 2017 at 5:42:28 AM UTC-7, Andrew Milner wrote:
>
> If you are referring to the NOAA reports the simplest way is to delete 
> them all and let weewx recreate them at the next archive interval:
> a) stop weewx
> b) delete all files in NOAA directory
> c) start weewx
>
> as long as the underlying data is in the archive database the NOAA reports 
> will all be recreated as part of the first archive interval processing
>
>
>
> On Monday, 4 December 2017 14:33:28 UTC+2, Joe Brockway wrote:
>
>> Well now I have a new issue.
>>
>> My CLIMATOLOGICAL data for 2017 only shows December. All the data is 
>> there for the other past years. And the data was there before I ran the 
>> wee_database command.
>>
>> Any suggestions on how to fix this? 
>>
>>

-- 
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: Air quality sensors?

[Thomas Carlin]

I have not.  It should be pretty easy with the google doc link above, and 
the documentation provided by TK and the crew here: 
http://www.weewx.com/docs/customizing.htm#Adding_2nd_source.  You would 
just need to parse and sanitize the data coming in from the json output, 
and stuff it into the database.  Once it is there, it's just a matter of 
modifying the weewx UI to display as desired.

I have a handful of other projects going right now, but this is definitely 
on the list.  When it happens is anyone's guess.

-- 
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] --reading failure in weewx_3.8.0-1 and weewx-owfs-0.21 Raspberry Pi & DS18B20

[Miguel Andres]

Hello,


I have been suggested to post this question to this group as a weewx-user 
group instead of the issues in github.


I have read issue 77  and has 
helped but --readings do not seem to show...


My setup is:


Raspberry Pi 1 Model B running Raspbian Minimal (Stretch)
2017-09-07-raspbian-stretch-lite.img

One-Wire enabled from raspi-configTemperature


Temperature sensor DS18B20 (outdoor-friendly) is pinned to Raspberry GPIO 
and running python thermometer.py script outputs correct temperature 
readings.

pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.9.66+ #1059 Fri Dec 1 15:15:38 GMT 2017 armv6l GNU/Linux


I have installed Weewx from a .deb as follows:

sudo dpkg -i weewx_3.8.0-1_all.deb
sudo apt-get update
sudo apt­-get -f install
sudo apt-get install lighttpd

open http://192.168.1.2/weewx/ in web browser and it shows default server
Configured as Simulator because the other options are branded weather 
stations that do not match my simple temperature sensor setup.

wget http://lancet.mit.edu/mwall/projects/weather/releases/weewx-owfs-0.21.tgz
sudo apt-get install python-ow
wee_extension --install weewx-owfs-0.21.tgz
sudo wee_extension --install weewx-owfs-0.21.tgz

(without sudo would not work)

To install OWFS as a service...

sudo apt-get install python-ow
sudo apt-get install owfs
wee_extension --install weewx-owfs-0.21.tgz

To find out sensors I tried with no success:

sudo PYTHONPATH=/home/weewx/bin python /home/weewx/bin/user/owfs.py 
--sensors

But in Issue 77 using -iface localhost:4304 is suggested and it works!

pi@raspberrypi:~ $ sudo PYTHONPATH=/usr/share/weewx python 
/usr/share/weewx/user/owfs.py --iface localhost:4304 --sensors
67C6697351FF: /10.67C6697351FF DS18S20
4AEC29CDBAAB: /05.4AEC29CDBAAB DS2405

Two things here, my sensor is DS18B20 but three-pin layout is the same, 
though. No idea about DS2405 but it seems it is a 1-wire network branch 
controller. See... DS2405 at owfs.org 


And, as in that Issue, when trying to do the readings this is the output:

pi@raspberrypi:~ $ sudo PYTHONPATH=/usr/share/weewx python 
/usr/share/weewx/user/owfs.py --iface localhost:4304 --readings
67C6697351FF
_usePath: /10.67C6697351FF
_type: DS18S20
_path: /10.67C6697351FF
_useCache: True
  /10.67C6697351FF/scratchpad: f▒\KQ
  /10.67C6697351FF/power: 1
  /10.67C6697351FF/family: 10
  /10.67C6697351FF/locator: ttzxlqrnldwfriez
  /10.67C6697351FF/type: DS18S20
  /10.67C6697351FF/crc8: 8D
  /10.67C6697351FF/temphigh: 24.2793
  /10.67C6697351FF/templow: 7.71973
  /10.67C6697351FF/latesttemp: 4.78051
  /10.67C6697351FF/r_id: FF517369C667
  /10.67C6697351FF/address: 1067C6697351FF8D
  /10.67C6697351FF/errata/: die,trim,trimblanket,trimvalid
  /10.67C6697351FF/r_address: 8DFF517369C66710
  /10.67C6697351FF/r_locator: lqyfpwbewksoflnc
  /10.67C6697351FF/id: 67C6697351FF
  /10.67C6697351FF/temperature: 50.105
4AEC29CDBAAB
_usePath: /05.4AEC29CDBAAB
_type: DS2405
_path: /05.4AEC29CDBAAB
_useCache: True
  /05.4AEC29CDBAAB/type: DS2405
  /05.4AEC29CDBAAB/family: 05
  /05.4AEC29CDBAAB/PIO: 1
  /05.4AEC29CDBAAB/r_locator: vlqbixssctrotcgt
  /05.4AEC29CDBAAB/crc8: 42
  /05.4AEC29CDBAAB/sensed: 0
  /05.4AEC29CDBAAB/r_id: ABBACD29EC4A
  /05.4AEC29CDBAAB/address: 054AEC29CDBAAB42
  /05.4AEC29CDBAAB/r_address: 42ABBACD29EC4A05
  /05.4AEC29CDBAAB/locator: xplcmywcfhrkhwft
  /05.4AEC29CDBAAB/id: 4AEC29CDBAAB

As I try to stick to group rules, please links to my log as well:

Log November https://pastebin.com/z01hTdCP

Log December https://pastebin.com/WKGm34Jy and https://pastebin.com/LSjK7t2U

Thank you in advance for your suggestions and advice.

Regards,

-- 
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: Air quality sensors?

[Kenneth Baker]

On Sunday, November 26, 2017 at 10:58:10 PM UTC-5, Thomas Carlin wrote:
>
> For anyone that is interested, I did finally get a response from the folks 
> at purple air, and you can remotely access the data from the sensors in 
> JSON format by going to http:///json.  This sensor system 
> seems to be an excellent compromise between system quality, price, and 
> *hopefully* longevity and reliability.  
>
> I don't know if the document is publically readable or not, but their 
> documentation can be found Here: 
> https://docs.google.com/document/d/15ijz94dXJ-YAZLi9iZ_RaBwrZ4KtYeCy08goGBwnbCU/edit#heading=h.l6r1b1hpfhod
>


Hi Thomas,

My Purple Air device just arrived...  Have you written a weewx driver for 
Purple Air?

-- Ken

-- 
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: add external sensors on remote computer to a main weewx installation?

['Christian Peters' via weewx-user]

Okso as usual: the user! :-D

Thanks for your patience and help!

Regards,

Christian 

Am Montag, 4. Dezember 2017 13:18:14 UTC+1 schrieb Tom Keffer:
>
> I don't think so. "hail" is treated no differently than "rain."
>
> -tk
>
> On Sun, Dec 3, 2017 at 6:42 PM, 'Christian Peters' via weewx-user <
> weewx...@googlegroups.com > wrote:
>
>> Tom,
>>
>> I got it working...but I don't now why?! :-D
>>
>> To clarify I used a second instance of weewx running wxMesh. As I has 
>> only one rain bucket per weewx I thougth I could change back in the weewx 
>> instance running wxMesh to the rain database entry.
>> My binding for wxMesh is now 'rain=rain'. 
>> I changed in the wxMesh driver to METRICWX as I want the mm for rain and 
>> send 0.1 as value per bucket tip. 5 time tip: wxMesh grabs 0.5 
>>
>> wxMesh: Got message 
>> TIME:0,radiation:0.25,cpm:45,cps:1,temp_2m:50.81,temp_5cm:50.60,temp_dht22:19.70,hum_dht22:38.50,rain:0.50
>> Dec  4 01:17:22 sensweewx[24607]: wxMesh: Working on payload : 
>> TIME:0,radiation:0.25,cpm:45,cps:1,temp_2m:50.81,temp_5cm:50.60,temp_dht22:19.70,hum_dht22:38.50,rain:0.50
>> Dec  4 01:17:22 sensweewx[24607]: wxMesh: key: TIME value: 1512346642
>> Dec  4 01:17:22 sensweewx[24607]: wxMesh: key: radiation value: 0.25
>> Dec  4 01:17:22 sensweewx[24607]: wxMesh: key: cpm value: 45
>> Dec  4 01:17:22 sensweewx[24607]: wxMesh: key: cps value: 1
>> Dec  4 01:17:22 sensweewx[24607]: wxMesh: key: temp_2m value: 50.81
>> Dec  4 01:17:22 sensweewx[24607]: wxMesh: key: temp_5cm value: 50.60
>> Dec  4 01:17:22 sensweewx[24607]: wxMesh: key: temp_dht22 value: 19.70
>> Dec  4 01:17:22 sensweewx[24607]: wxMesh: key: hum_dht22 value: 38.50
>> Dec  4 01:17:22 rumo sensweewx[24607]: wxMesh: key: *rain value: 0.50*
>> Dec  4 01:17:22 rumo sensweewx[24607]: wxMesh: Sleeping for 5
>>
>> The query in my main weewx instance to the wxMesh (sensweewx with mqtt):
>>
>>  
>> Rain today Lambrecht
>> > class="stats_data">$day($data_binding='mqtt_binding').rain.sum
>>   
>>
>> and the result is now ok:
>>
>> Rain today Lambrecht: 0,5 mm
>>
>> Maybe the mapping to hail was the problem...now all works as expected!? 
>>
>>
>> Regards,
>>
>> Christian 
>>
>>
>>
>>
>>
>> Am Sonntag, 3. Dezember 2017 20:14:42 UTC+1 schrieb Tom Keffer:
>>>
>>> I'm still a little hazy on what the issue is. What do you mean by "the 
>>> values don't match"? Which values? And I don't know where your website is.
>>>
>>> ​The wxMesh driver (at least as posted here 
>>> ) 
>>> expects weewx.METRIC units, that is, rain (and hail) should be in 
>>> centimeters, not millimeters.​ You can't just simply change to 
>>> weewx.METRICWX in your copy, because then the other units will be wrong. 
>>>
>>> Run weewx from the command line and watch what it prints. Tip the bucket 
>>> and see what value gets printed. Is it what you expected?
>>>
>>> -tk
>>>
>>> On Sun, Dec 3, 2017 at 9:16 AM, 'Christian Peters' via weewx-user <
>>> weewx...@googlegroups.com> wrote:
>>>
 Tom,

 I use the wxMesh driver but I think your demo code is imlemented in 
 that way you posted:

 #!/usr/bin/python 
 # 
 # weewx driver that reads data from MQTT subscription 
 # 
 # This program is free software: you can redistribute it and/or modify 
 it under 
 # the terms of the GNU General Public License as published by the Free 
 Software 
 # Foundation, either version 3 of the License, or any later version. 
 # 
 # This program is distributed in the hope that it will be useful, but 
 WITHOUT 
 # ANY WARRANTY; without even the implied warranty of MERCHANTABILITY 
 or FITNESS 
 # FOR A PARTICULAR PURPOSE. 
 # 
 # See http://www.gnu.org/licenses/ 

 # 
 # The units must be weewx.US: 
 # degree_F, inHg, inch, inch_per_hour, mile_per_hour 
 # 
 # To use this driver, put this file in the weewx user directory, then 
 make 
 # the following changes to weewx.conf: 
 # 
 # [Station] 
 # station_type = wxMesh 
 # [wxMesh] 
 # host = localhost # MQTT broker hostname 
 # topic = weather # topic 
 # driver = user.wxMesh 
 # 
 # If the variables in the file have names different from those in 
 weewx, then 
 # create a mapping such as this: 
 # 
 # [wxMesh] 
 # ... 
 # [[label_map]] 
 # temp = outTemp 
 # humi = outHumidity 
 # in_temp = inTemp 
 # in_humid = inHumidity 

 from __future__ import with_statement 
 import syslog 
 import time 
 import paho.mqtt.client as mqtt 
 import weewx.drivers 

 DRIVER_VERSION = "0.1" 

 def logmsg(dst, msg): 
 syslog.syslog(dst, 'wxMesh: %s' % msg) 

 def logdbg(msg): 
 logmsg(syslog.LOG_DEBUG, msg) 

 def loginf(msg): 
 logmsg(syslog.LOG_INFO, msg) 

 def 

[weewx-user] Weewx + Weatherlink drivers hangs.

[Ruben Navarro Huedo]

Hello friends:

Using last weewx with last wlink driver.
We are having some power problems with out Davis.
I think problem is its getting n/a from weatherlink.com
Is this possible?

Sometimes weewx exists:

Here you have log:
Dec  4 04:29:00 MeteoElche cabo[9821]: engine: Main loop exiting. Shutting 
engine down.
Dec  4 04:29:00 MeteoElche cabo[9821]: engine: Shutting down StdReport 
thread
Dec  4 04:29:00 MeteoElche cabo[9821]: engine: StdReport thread has been 
terminated
Dec  4 04:29:00 MeteoElche cabo[9821]: engine: Caught unrecoverable 
exception in engine:
Dec  4 04:29:00 MeteoElche cabo[9821]:   could not convert string 
to float: n/a
Dec  4 04:29:00 MeteoElche cabo[9821]:   Traceback (most recent 
call last):
Dec  4 04:29:00 MeteoElche cabo[9821]: File 
"/usr/share/weewx/weewx/engine.py", line 871, in main
Dec  4 04:29:00 MeteoElche cabo[9821]:   engine.run()
Dec  4 04:29:00 MeteoElche cabo[9821]: File 
"/usr/share/weewx/weewx/engine.py", line 187, in run
Dec  4 04:29:00 MeteoElche cabo[9821]:   for packet in 
self.console.genLoopPackets():
Dec  4 04:29:00 MeteoElche cabo[9821]: File 
"/usr/share/weewx/user/wlink.py", line 143, in genLoopPackets
Dec  4 04:29:00 MeteoElche cabo[9821]:   
packet.update(self.parse_page(data))
Dec  4 04:29:00 MeteoElche cabo[9821]: File 
"/usr/share/weewx/user/wlink.py", line 190, in parse_page
Dec  4 04:29:00 MeteoElche cabo[9821]:   parser.feed(text)
Dec  4 04:29:00 MeteoElche cabo[9821]: File 
"/usr/lib/python2.7/HTMLParser.py", line 117, in feed
Dec  4 04:29:00 MeteoElche cabo[9821]:   self.goahead(0)
Dec  4 04:29:00 MeteoElche cabo[9821]: File 
"/usr/lib/python2.7/HTMLParser.py", line 155, in goahead
Dec  4 04:29:00 MeteoElche cabo[9821]:   if i < j: 
self.handle_data(rawdata[i:j])
Dec  4 04:29:00 MeteoElche cabo[9821]: File 
"/usr/share/weewx/user/wlink.py", line 514, in handle_data
Dec  4 04:29:00 MeteoElche cabo[9821]:   
self.packet['outHumidity'] = float(data)
Dec  4 04:29:00 MeteoElche cabo[9821]:   ValueError: could not 
convert string to float: n/a
Dec  4 04:29:00 MeteoElche cabo[9821]:   Exiting.

-- 
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] Updating database error - "weedb.OperationalError: database is locked"

[Andrew Milner]

If you are referring to the NOAA reports the simplest way is to delete them 
all and let weewx recreate them at the next archive interval:
a) stop weewx
b) delete all files in NOAA directory
c) start weewx

as long as the underlying data is in the archive database the NOAA reports 
will all be recreated as part of the first archive interval processing



On Monday, 4 December 2017 14:33:28 UTC+2, Joe Brockway wrote:

> Well now I have a new issue.
>
> My CLIMATOLOGICAL data for 2017 only shows December. All the data is there 
> for the other past years. And the data was there before I ran the 
> wee_database command.
>
> Any suggestions on how to fix this? 
>
>

-- 
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] Updating database error - "weedb.OperationalError: database is locked"

[Thomas Keffer]

I'm not sure what you mean by CLIMATOLOGICAL data. Do you mean the NOAA
reports? If so, they are generated on a forward going basis: only reports
more recent than the last one you have will be generated. So, if you're
missing earlier reports, delete the directory and all will be regenerated.

-tk

On Mon, Dec 4, 2017 at 6:33 AM, Joe Brockway  wrote:

> Well now I have a new issue.
>
> My CLIMATOLOGICAL data for 2017 only shows December. All the data is there
> for the other past years. And the data was there before I ran the
> wee_database command.
>
> Any suggestions on how to fix this?
>
> --
> 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] Updating database error - "weedb.OperationalError: database is locked"

[Joe Brockway]

On Monday, December 4, 2017 at 5:33:28 AM UTC-7, Joe Brockway wrote:
> Well now I have a new issue.
> 
> My CLIMATOLOGICAL data for 2017 only shows December. All the data is there 
> for the other past years. And the data was there before I ran the 
> wee_database command.
> 
> Any suggestions on how to fix this?

I forgot to menttion when I look at the monthly data for any month in 2017 the 
data is there.

-- 
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: Oregon scientific WMR300 issues

[scott arnott]

yes would be good to get some help i have tried different things but still 
get the same error have tried on linux pc also a raspberry pi and a odroid 
c1 but still get the same error message but the WMR300 works fine on 
weather display and WeatherTracker on windows 10 with no problem 

it would be good if someone had a working image for the raspberry pi that  
is using a wmr300 that could upload it to a download site 

thanks 

On Friday, 1 December 2017 11:17:39 UTC, mwall wrote:
>
>
>
> On Friday, December 1, 2017 at 2:11:15 AM UTC-5, Markus Benedikt Biewer 
> wrote:
>>
>> Nobody out there willing to help me and Scott? We seem to have the same 
>> problem
>>
>> What can we do or try and how?
>>>
>>>
>>>
> there are some things you can try.  i can walk you through it, but i am 
> rather pressed for time right now (a boat to catch).  will get back to you 
> in a couple of days...
>  
>

-- 
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.