[weewx-user] Re: Acurite 01536 (Costco)

[David Morgan]

On Wednesday, January 18, 2017 at 4:24:16 PM UTC-8, David Morgan wrote:
>
>
>>
> The barometric pressure is way wrong on the console, and there is some 
> disagreement between the console and the WeeWx display. I am curious if 
> anyone knows yet what sensors are used.  I have resisted peeking so far, 
> but  that may change. 
>
I did take the console apart last night to see what parts were used.   I 
found the ICs were covered over with a hard black coating so you cannot 
identify what is there.  I did not find anything that looked like pressure 
sensor.   I did find what is probably the temp sensor.

I am finding that with my laptop, connecting to the console is not 
consistent.  Once connected, it seems to do OK.  I am not a programmer, so 
understanding the python code is not so easy for me.   Makes it hard to 
understand just where things are not working.  Wireshark is showing the 
system is having trouble initiating the transfer of data from the console 
to the host, even though it has already read the initialization data from 
the console.  Below is a dump from wireshark.   

Frame 595, the host issues a   USB   SET INTERFACE Request
Frame 596, the console responds,   USB   SET INTERFACE Response  :: URB 
status: Protocol error (-EPROTO) (-71)
Frame 597, the host issues a   USBHID GET_REPORT Request
Frame 598, the console responds,   USBHID GET_REPORT Response :: URB 
status: Success (0)   Console responded with 10 data bytes.

All following messages were successful.   So why did it just start working? 
 And why was the data request successful when the set interface request 
failed?  Is it not necessary for the USB interface to be set before a 
USBHID request?  Who sent the USB request?  Was it Python or the linux 
kernel?  These are things I have not figured out.


595 690.183528 host  5.14.0USB 
 64 SET INTERFACE Request

Frame 595: 64 bytes on wire (512 bits), 64 bytes captured (512 bits) on 
interface 0
USB URB
[Source: host]
[Destination: 5.14.0]
URB id: 0x88011c951300
*URB type: URB_SUBMIT ('S')*
URB transfer type: URB_CONTROL (0x02)
Endpoint: 0x00, Direction: OUT
Device: 14
URB bus id: 5
Device setup request: relevant (0)
Data: present (0)
URB sec: 1484814928
URB usec: 977890
URB status: Operation now in progress (-EINPROGRESS) (-115)
URB length [bytes]: 0
Data length [bytes]: 0
[Response in: 596]
Interval: 0
Start frame: 0
Copy of Transfer Flags: 0x
Number of ISO descriptors: 0
URB setup
  00 13 95 1c 01 88 ff ff *53* 02 00 0e 05 00 00 00   *S*... 
Submit
0010  50 7a 80 58 00 00 00 00 e2 eb 0e 00 8d ff ff ff   Pz.X
0020  00 00 00 00 00 00 00 00 01 0b 00 00 00 00 00 00   
0030  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   


596 690.187517 5.14.0host  USB 
 64 SET INTERFACE Response

Frame 596: 64 bytes on wire (512 bits), 64 bytes captured (512 bits) on 
interface 0
USB URB
  *  [Source: 5.14.0]*
*[Destination: host]*
URB id: 0x88011c951300
URB type: URB_COMPLETE ('C')
URB transfer type: URB_CONTROL (0x02)
Endpoint: 0x00, Direction: OUT
Device: 14
URB bus id: 5
Device setup request: not relevant ('-')
Data: not present ('>')
URB sec: 1484814928
URB usec: 981879
 *   URB status: Protocol error (-EPROTO) (-71)*
URB length [bytes]: 0
Data length [bytes]: 0
[Request in: 595]
[*Time from request: 0.003989000 seconds*]
Unused Setup Header
Interval: 0
Start frame: 0
Copy of Transfer Flags: 0x
Number of ISO descriptors: 0
  00 13 95 1c 01 88 ff ff 43 02 00 *0e 05 00* 2d 3e   C.-> 
  From 14  05, the console bus address
0010  50 7a 80 58 00 00 00 00 77 fb 0e 00 *b9 ff ff ff*   Pz.Xw... 
 Bold means protocol error
0020  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   
0030  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   


597 690.187738 host  5.14.0USBHID   
64 GET_REPORT Request

Frame 597: 64 bytes on wire (512 bits), 64 bytes captured (512 bits) on 
interface 0
USB URB
*[Source: host]*
*[Destination: 5.14.0]*
URB id: 0x88011c951300
*URB type: URB_SUBMIT ('S')*
URB transfer type: URB_CONTROL (0x02)
Endpoint: 0x80, Direction: IN
Device: 14
URB bus id: 5
Device setup request: relevant (0)
Data: not present ('<')
URB sec: 1484814928
URB usec: 982100
URB status: Operation now in progress (-EINPROGRESS) (-115)
URB length [bytes]: 10
Data length [bytes]: 0
[Response in: 598]
Interval: 0
Start frame: 0
Copy of Transfer Flags: 0x0200
Number of ISO descriptors: 0
[bInterfaceClass: HID (0x03)]
URB setup
bRequest: GET_REPORT (0x01)
wVal

Re: [weewx-user] Matching rain corrections with weewx and Weather Underground

[J]

Thanks for your responses and please pardon my late reply -- I wanted to 
wait until some more rain fell to confirm observations and gather more 
detailed logs.

It appears that the standard Wunderground-PWS archive method posts the 
corrected values, but Wunderground-RF rapid fire submits a combination of 
corrected and uncorrected values. I'm unclear on where the uncorrected 
value is being pulled from.

For reference, the uncorrected value (as displayed by Davis console) at the 
time of the below logs is 0.6 inches. With the weewx corrections it's 
(rounded up to) 0.7. The discrepancy has persisted and widened as more rain 
has fallen throughout the day.

Wunderground-PWS:  both dailyrainin and rainin show the corrected 0.7:

Jan 19 04:47:16 weewx[2009]: restx: Ambient: url: 
http://weatherstation.wunderground.com/weatherstation/updateweatherstation.php?action=updateraw&ID=YYY&PASSWORD=XXX&softwaretype=weewx-3.5.0&windgustmph=3.0&humidity=095&;
*dailyrainin=0.07*&winddir=270&tempf=50.8&windspeedmph=1.0&*rainin=0.07*
&baromin=29.805&dewptf=49.4&dateutc=2017-01-19%2012%3A47%3A00
Jan 19 04:47:16 weewx[2009]: restx: Wunderground-PWS: Published record 
2017-01-19 04:47:00 PST (1484830020)

Wunderground-RF rapid fire:  dailyrainin has the uncorrected value (0.6), 
but rainin uses the corrected one (0.7).  WU appears to use the dailyrainin 
value for it's displayed precipitation totals. Log:

Jan 19 04:47:16 weewx[2009]: restx: Ambient: url: 
http://weatherstation.wunderground.com/weatherstation/updateweatherstation.php?action=updateraw&ID=YYY&PASSWORD=XXX&softwaretype=weewx-3.5.0&windgustmph=5.0&humidity=095&;
*dailyrainin=0.06*&winddir=247&tempf=50.8&windspeedmph=5.0&rtfreq=2.5&
*rainin=0.07*
&baromin=29.807&dewptf=49.4&dateutc=2017-01-19%2012%3A47%3A16&realtime=1

If I enable both methods, I can see the displayed value on WU bounce down 
to 0.6 after the Wundergrond-PWS submission, then back to 0.7 with the next 
Wunderground-RF submission.  This bouncing back and forth is also reflected 
occasionally in the WU graphs.


mwall wrote:

> jesse, you can use conditionals in corrections:  [...]  each correction 
> must be a single line of python


Awesome, thank you!

- jesse


On Friday, January 13, 2017 at 6:40:17 PM UTC-8, Tom Keffer wrote:


The value sent to wunderground is calculated directly from the database. 
> It's the sum of all rain that fell during the last 60 minutes. So, if 
> you're happy with the values of 'rain' in the database, then you should 
> be getting the same at wunderground. 
>
> -tk
>
> On Fri, Jan 13, 2017 at 6:21 PM, J > 
> wrote:
>
>> Hi,
>>
>> I'm trying to apply some corrections to my rain data but am running into 
>> an issue with getting Wunderground data to match.
>>
>> I want to adjust my rain corrections based on wind data -- I'm 
>> compensating for undercatch during high winds due to my rain bucket's 
>> higher than typical elevation above ground. I'm using a Davis VantagePro2.
>>
>> Making corrections to rain and rainRate using windGust works great in 
>> weewx. Each 0.01" tip is adjusted by current wind conditions. However, 
>> Wunderground values are uncorrected. From some reading of past threads, it 
>> sounds like Wunderground data may instead use dayRain and hourRain values 
>> directly from archive records, instead of simply pushing up the weewx 
>> values. I run into the issue that if I try to adjust dayRain and/or 
>> hourRain based on wind from the archive records, not only will the totals 
>> differ because of wind values from different periods, but it seems like the 
>> entire day total would be repeatedly scaled up and down based on whatever 
>> the last wind reading was.
>>
>> Is there a way to have the data sent to Wunderground based on the totals 
>> stored by weewx? Or otherwise keep them synced in a sane manner?
>>
>> Thanks!
>> Jesse
>>
>> P.S. I'd also love to be able to use windDirection and rainRate as 
>> factors in the corrections, but that's probably overly ambitious without 
>> support for conditionals in corrections.
>>
>> -- 
>> 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] upgrading from 2.0 to 3.6

[gjr80]

On Friday, 20 January 2017 10:53:44 UTC+10, vince wrote:
>
>
> Older model pi had issues completing it successfully, but I'm 
> guessing/hoping a pi3 has enough horsepower that it'll succeed.  Be very 
> patient during the conversion process.
>

IIRC the main issue with the older RPi (other than speed) was that 
backfilling the daily summaries was done in a single transaction and for 
large archives this caused memory issues leading to a crash. This issue was 
addressed in 3.5.0 and the daily summary rebuilds are now done in 
transactions of so many days rather than one big transaction. So hopefully 
that aspect should be crash free. And a contemporary RPi should see the 
rebuild done much faster than original RPi.

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] upgrading from 2.0 to 3.6

[vince]

On Thursday, January 19, 2017 at 4:22:50 PM UTC-8, Tom Keffer wrote:
>
> Would it be better if I allow the database upgrade to finish before I 
>> connect the weather station (Vantage Pro 2 + Envoy) or it doesn't really 
>> matter?
>>
>
> Copy your old weewx.sdb file to /home/weewx/archive/weewx.sdb.
> Start weewxd. It will automatically do the database upgrade. Be prepared 
> to wait! For this step, I would suggest running weewxd from the command 
> line.
>
>
>
If you have 5 years of data, be certain you're working off a 'copy' of your 
old weewx.sdb just in case.   Also, it'll take a while, perhaps a long 
while, to do the conversion.  Older model pi had issues completing it 
successfully, but I'm guessing/hoping a pi3 has enough horsepower that 
it'll succeed.  Be very patient during the conversion process.  It'll also 
take some time to generate your NOAA reports the first time.  Watch the 
command line output. If possible ssh in and 'tail -f' your 
/var/log/messages to watch there too.

If you run into issues it's possible to offline convert things on a faster 
machine, if I remember correctly (it's been a while).

-- 
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] upgrading from 2.0 to 3.6

[Thomas Keffer]

>
> Would it be better if I allow the database upgrade to finish before I
> connect the weather station (Vantage Pro 2 + Envoy) or it doesn't really
> matter?
>

My suggested sequence. This assumes you are using the setup.py install
method (Debian install was not introduced until V2.2) and that weewx has
never been installed before.

Plug the weather station into the new RPi.
Install weewx. This will install a new skin.
Copy your old weewx.sdb file to /home/weewx/archive/weewx.sdb.
Start weewxd. It will automatically do the database upgrade. Be prepared to
wait! For this step, I would suggest running weewxd from the command line.

Then continue as usual.


> I didn't really change the default skin much (as far as I recall). Is it
> still necessary to copy the skin files?
>

You can just use the skin that comes with weewx.

-tk

-- 
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] upgrading from 2.0 to 3.6

[tds]

I'll report back when I finish the upgrade. Just ordered the Pi, RTC, etc. 
So it may take some time, depending on my schedule.

Would it be better if I allow the database upgrade to finish before I 
connect the weather station (Vantage Pro 2 + Envoy) or it doesn't really 
matter?

I didn't really change the default skin much (as far as I recall). Is it 
still necessary to copy the skin files?

On Thursday, January 19, 2017 at 4:02:14 PM UTC-8, Tom Keffer wrote:
>
> This will be a good test of the automatic upgrade. :-)
>
> Unless you are using an extension, or have done a searchlist extension, it 
> should just work. Note that there is no longer a statistical summary file 
> (stats.sdb). Instead, the daily summaries are now included inside the 
> weewx.sdb file. So, when you first start weewx up, it will take some time 
> to rebuild those summaries. For five years of data, expect it to take an 
> hour or so on an RPi. Alternatively, you can rebuild on a faster machine, 
> then copy the upgraded weewx.sdb over.
>
> Be sure to copy your skins over as well. They should be backwards 
> compatible.
>
> I'm curious how it goes.
>
> -tk
>
> On Thu, Jan 19, 2017 at 3:50 PM, tds > 
> wrote:
>
>> Hi,
>>
>> I'm planning on installing the latest weewx 3.6 on a new machine 
>> (Raspberry Pi). I've been running 2.0 on another machine for almost five 
>> years and would like to to keep my weewx.sdb. Will it work by simply coping 
>> the weewx.sdb from 2.0 to the 3.6 installation? 
>>
>> Thanks,
>>
>> TDS
>>
>> -- 
>> 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] upgrading from 2.0 to 3.6

[Thomas Keffer]

This will be a good test of the automatic upgrade. :-)

Unless you are using an extension, or have done a searchlist extension, it
should just work. Note that there is no longer a statistical summary file
(stats.sdb). Instead, the daily summaries are now included inside the
weewx.sdb file. So, when you first start weewx up, it will take some time
to rebuild those summaries. For five years of data, expect it to take an
hour or so on an RPi. Alternatively, you can rebuild on a faster machine,
then copy the upgraded weewx.sdb over.

Be sure to copy your skins over as well. They should be backwards
compatible.

I'm curious how it goes.

-tk

On Thu, Jan 19, 2017 at 3:50 PM, tds  wrote:

> Hi,
>
> I'm planning on installing the latest weewx 3.6 on a new machine
> (Raspberry Pi). I've been running 2.0 on another machine for almost five
> years and would like to to keep my weewx.sdb. Will it work by simply coping
> the weewx.sdb from 2.0 to the 3.6 installation?
>
> Thanks,
>
> TDS
>
> --
> 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] upgrading from 2.0 to 3.6

[tds]

Hi,

I'm planning on installing the latest weewx 3.6 on a new machine (Raspberry 
Pi). I've been running 2.0 on another machine for almost five years and 
would like to to keep my weewx.sdb. Will it work by simply coping the 
weewx.sdb from 2.0 to the 3.6 installation? 

Thanks,

TDS

-- 
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: gauge-data.txt file not being generated SS gauges

[gjr80]

Ok, some more thoughts. Delete the content between the {}, no * opertaions 
in there so the error is not in there. Then work through the 'chunks' of  
python in the template commenting out/deleting (keeping the template open 
in an editor and using control-Z/undo is a great timesaver) each one in 
turn until you find the culprit, eg; comment/delete the appttemp 
calculations, then the humidex. 

Another thought, run weewx directly 
 and have a look at 
what is coming out for each obs in the archive record (archive records are 
identified with a REC and appear each archive interval). Look for any obs 
used in the template that have None values. That might give you a clue.

windDir (and the gust equivalent) are often a source of 'Nones' but in this 
case I don't think any are used in a multiplication operation. But that is 
the sort of thinking you need.

I note your list has no Nones, but that is not what is used in the 
template; the template uses the data in weewx, there is a subtle 
difference. that is why we need to focus on what weewx 'sees' or 'has'.

Gary

On Friday, 20 January 2017 08:41:33 UTC+10, Robert Mantel wrote:
>
> Hey Gary, thanks for the reply.  Yes I tried doing some troubleshooting by 
> commenting out specific lines, especially the math.exp ones, but when I do 
> cheetah just complains it can't find variable "x" whatever one I have 
> commented out.  But maybe your technique will yield more info.  Here is the 
> label map I'm using in fileparse:
>
> tempf = outTemp
> humidity = outHumidity
> inches = pressure
> dewptf = dewpoint
> windspdavg = windSpeed
> winddiravg = windDir
> rainin = rainRate
> timestamp = dateTime
> windgustmph = windGust
> windgustdir = windGustDir
>
> The values on the left come from a cron job I run every minute that does a 
> jsonp query to my phant server which acts as my weather station data dump. 
>  The timestamp comes from the phant server and my cron job code converts it 
> to epoch and the query itself grabs the EST version of the timestamp. 
>  While writing this I'm wondering if I should be using UTC?  Anyways, my 
> station is inside right now so no wind is being produced but I anticipated 
> that the gauges would be able to deal with this condition, otherwise it 
> would be complaining all the time about wind and rain and such.  Here is a 
> dump of my fileparse data file (the one that weewx imports), As you can see 
> there are no null values:
>
> soc=255.9961
> rainin=0.1100
> voltage=5.1188
> humidity=35.
> windspeedmph=0.
> kilopascals=98.6170
> winddir_avg2m=90
> rainmm=2.7940
> windspeedmps=0.
> hpa=986.1700
> tempc=21.6800
> windgustmph=0.
> tempf=71.0240
> inches=29.1216
> timestamp=1484865589
> windspdmps_avg2m=0.
> windspeedkmph=0.
> winddir=90
> dewptf=42.0318
> dewptc=5.5732
> altm=235.6895
> altf=773.2595
> dailyrainin=0.6160
> windgustdir=0
>
> Obviously I'm not mapping all these to weewx as of yet.  I'm hoping you 
> can shed some light on this one.  
>
> On Thursday, 19 January 2017 16:44:52 UTC-5, gjr80 wrote:
>>
>> Hi,
>>
>> Welcome to the joys of troubleshooting a Cheetah template! The best 
>> Cheetah errors to have are those that crash in your non-template python 
>> code as that way you tend to get a meaningfull error trace, if the crash 
>> occurs in the in-template python code they can be very hard (well tedious) 
>> to track down. As you have no doubt found out the line number quoted in the 
>> error trace is usesless, it refers to a temporary file we have no access 
>> to. The best clue is the actual error message itself. in this case there is 
>> a multiplication operation occuring that is using an integer and the value 
>> None which gives the TypeError. What you need to do is carefully look at 
>> each multiplication operation in the template (there are 33 but some can be 
>> ruled out depending on your settings) and see if any of them could possibly 
>> be using a variable that is None. You have what sounds like a unique setup, 
>> I would look at what obs your setup is providing weewx and through omission 
>> could any of the common obs be None? This could cause some variable in the 
>> template to be None (which does not trigger the error) but later on that 
>> variable is used in an equation that does trigger the error. As you can see 
>> it can get complex. One technique I use is what I call the 'method of 
>> halves': 
>>
>>1. make a backup of the template as this is destructive
>>2. open the template
>>3. delete the bottom half of the template
>>4. save the template 
>>5. let weewx do a report cycle(no need to start/stop, just let weewx 
>>continue to run, you could be here a while)
>>6. did the error go away?
>>   - yes - the error is in the bottom half of the template, repeat 
>>   but this time only delete half of what you last d

[weewx-user] Re: gauge-data.txt file not being generated SS gauges

[Robert Mantel]

Hey Gary, thanks for the reply.  Yes I tried doing some troubleshooting by 
commenting out specific lines, especially the math.exp ones, but when I do 
cheetah just complains it can't find variable "x" whatever one I have 
commented out.  But maybe your technique will yield more info.  Here is the 
label map I'm using in fileparse:

tempf = outTemp
humidity = outHumidity
inches = pressure
dewptf = dewpoint
windspdavg = windSpeed
winddiravg = windDir
rainin = rainRate
timestamp = dateTime
windgustmph = windGust
windgustdir = windGustDir

The values on the left come from a cron job I run every minute that does a 
jsonp query to my phant server which acts as my weather station data dump. 
 The timestamp comes from the phant server and my cron job code converts it 
to epoch and the query itself grabs the EST version of the timestamp. 
 While writing this I'm wondering if I should be using UTC?  Anyways, my 
station is inside right now so no wind is being produced but I anticipated 
that the gauges would be able to deal with this condition, otherwise it 
would be complaining all the time about wind and rain and such.  Here is a 
dump of my fileparse data file (the one that weewx imports), As you can see 
there are no null values:

soc=255.9961
rainin=0.1100
voltage=5.1188
humidity=35.
windspeedmph=0.
kilopascals=98.6170
winddir_avg2m=90
rainmm=2.7940
windspeedmps=0.
hpa=986.1700
tempc=21.6800
windgustmph=0.
tempf=71.0240
inches=29.1216
timestamp=1484865589
windspdmps_avg2m=0.
windspeedkmph=0.
winddir=90
dewptf=42.0318
dewptc=5.5732
altm=235.6895
altf=773.2595
dailyrainin=0.6160
windgustdir=0

Obviously I'm not mapping all these to weewx as of yet.  I'm hoping you can 
shed some light on this one.  

On Thursday, 19 January 2017 16:44:52 UTC-5, gjr80 wrote:
>
> Hi,
>
> Welcome to the joys of troubleshooting a Cheetah template! The best 
> Cheetah errors to have are those that crash in your non-template python 
> code as that way you tend to get a meaningfull error trace, if the crash 
> occurs in the in-template python code they can be very hard (well tedious) 
> to track down. As you have no doubt found out the line number quoted in the 
> error trace is usesless, it refers to a temporary file we have no access 
> to. The best clue is the actual error message itself. in this case there is 
> a multiplication operation occuring that is using an integer and the value 
> None which gives the TypeError. What you need to do is carefully look at 
> each multiplication operation in the template (there are 33 but some can be 
> ruled out depending on your settings) and see if any of them could possibly 
> be using a variable that is None. You have what sounds like a unique setup, 
> I would look at what obs your setup is providing weewx and through omission 
> could any of the common obs be None? This could cause some variable in the 
> template to be None (which does not trigger the error) but later on that 
> variable is used in an equation that does trigger the error. As you can see 
> it can get complex. One technique I use is what I call the 'method of 
> halves': 
>
>1. make a backup of the template as this is destructive
>2. open the template
>3. delete the bottom half of the template
>4. save the template 
>5. let weewx do a report cycle(no need to start/stop, just let weewx 
>continue to run, you could be here a while)
>6. did the error go away?
>   - yes - the error is in the bottom half of the template, repeat but 
>   this time only delete half of what you last deleted
>- no - the error is the top half of the template, delete half of what 
>   is left and repeat
>
> As I said it can be tedious, also if you have a template with lots of 
> embedded python you need to be careful where you slice. Anyway I think you 
> should get the idea.
>
> Assuming you track down the issue do let us know what the cause was, that 
> way we can harden the gauge-data.txt template.
>
> Good luck
>
> Gary
>
> On Thursday, 19 January 2017 23:44:51 UTC+10, Robert Mantel wrote:
>>
>> I have a brand new Raspberry Pi running the latest version of weewx.  I 
>> have it working with the default skin and also the Bootstrap skin with no 
>> issues.  I'm using fileparse.py to grab data from a text file that gets 
>> generated from a python script that does a jsonp query to my phant server 
>> that is archiving the raw data from my particle photon weather hardware. 
>>  Like probably everyone else I came across the SS gauges and love the look 
>> and feel of them so proceeded with the install and followed the 
>> instructions, modifying the gauges.js file and movnig all the appropriate 
>> files into my weewx install.  The gauges are reproduced perfectly, but no 
>> data is being input and I get the following error in syslog:
>>
>>
>> Jan 19 08:27:04 raspberrypi weewx[23078]: manager: added record 

[weewx-user] Re: gauge-data.txt file not being generated SS gauges

[gjr80]

Hi,

Welcome to the joys of troubleshooting a Cheetah template! The best Cheetah 
errors to have are those that crash in your non-template python code as 
that way you tend to get a meaningfull error trace, if the crash occurs in 
the in-template python code they can be very hard (well tedious) to track 
down. As you have no doubt found out the line number quoted in the error 
trace is usesless, it refers to a temporary file we have no access to. The 
best clue is the actual error message itself. in this case there is a 
multiplication operation occuring that is using an integer and the value 
None which gives the TypeError. What you need to do is carefully look at 
each multiplication operation in the template (there are 33 but some can be 
ruled out depending on your settings) and see if any of them could possibly 
be using a variable that is None. You have what sounds like a unique setup, 
I would look at what obs your setup is providing weewx and through omission 
could any of the common obs be None? This could cause some variable in the 
template to be None (which does not trigger the error) but later on that 
variable is used in an equation that does trigger the error. As you can see 
it can get complex. One technique I use is what I call the 'method of 
halves': 

   1. make a backup of the template as this is destructive
   2. open the template
   3. delete the bottom half of the template
   4. save the template 
   5. let weewx do a report cycle(no need to start/stop, just let weewx 
   continue to run, you could be here a while)
   6. did the error go away?
  - yes - the error is in the bottom half of the template, repeat but 
  this time only delete half of what you last deleted
   - no - the error is the top half of the template, delete half of what is 
  left and repeat
   
As I said it can be tedious, also if you have a template with lots of 
embedded python you need to be careful where you slice. Anyway I think you 
should get the idea.

Assuming you track down the issue do let us know what the cause was, that 
way we can harden the gauge-data.txt template.

Good luck

Gary

On Thursday, 19 January 2017 23:44:51 UTC+10, Robert Mantel wrote:
>
> I have a brand new Raspberry Pi running the latest version of weewx.  I 
> have it working with the default skin and also the Bootstrap skin with no 
> issues.  I'm using fileparse.py to grab data from a text file that gets 
> generated from a python script that does a jsonp query to my phant server 
> that is archiving the raw data from my particle photon weather hardware. 
>  Like probably everyone else I came across the SS gauges and love the look 
> and feel of them so proceeded with the install and followed the 
> instructions, modifying the gauges.js file and movnig all the appropriate 
> files into my weewx install.  The gauges are reproduced perfectly, but no 
> data is being input and I get the following error in syslog:
>
>
> Jan 19 08:27:04 raspberrypi weewx[23078]: manager: added record 2017-01-19 
> 08:26:00 EST (1484832360) to database 'weewx.sdb'
> Jan 19 08:27:04 raspberrypi weewx[23078]: manager: added record 2017-01-19 
> 08:26:00 EST (1484832360) to daily summary in 'weewx.sdb'
> Jan 19 08:27:04 raspberrypi weewx[23078]: reportengine: copied 0 files to 
> /var/www/html/weewx
> Jan 19 08:27:04 raspberrypi weewx[23078]: cheetahgenerator: Generate 
> failed with exception ''
> Jan 19 08:27:04 raspberrypi weewx[23078]: cheetahgenerator:  Ignoring 
> template /etc/weewx/skins/ss/gauge-data.txt.tmpl
> Jan 19 08:27:04 raspberrypi weewx[23078]: cheetahgenerator:  Reason: 
> unsupported operand type(s) for *: 'NoneType' and 'int'
> Jan 19 08:27:04 raspberrypi weewx[23078]:   Traceback (most recent 
> call last):
> Jan 19 08:27:04 raspberrypi weewx[23078]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 315, in generate
> Jan 19 08:27:04 raspberrypi weewx[23078]:   print >> _file, text
> Jan 19 08:27:04 raspberrypi weewx[23078]: File 
> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
> __str__
> Jan 19 08:27:04 raspberrypi weewx[23078]:   rc = getattr(self, 
> mainMethName)()
> Jan 19 08:27:04 raspberrypi weewx[23078]: File 
> "cheetah__etc_weewx_skins_ss_gauge_data_txt_tmpl_1484791504_04_19193.py", 
> line 326, in respond
> Jan 19 08:27:04 raspberrypi weewx[23078]:   TypeError: unsupported 
> operand type(s) for *: 'NoneType' and 'int'
>
>
> I'm wracking my brain trying to find in the gauge-data.txt.tmpl file what 
> could be causing the operand error and obviously it's a bogus variable in 
> one of the math functions.  So I suspect that there is some missing data 
> that I'm not supplying it?  Also of note, when I set up weewx I chose 
> metricwx for the display units, but the database is using US units.  Is 
> this my problem?  Should I have stuck with US display units as well when I 
> did the initial install?
>

-- 
You received this mes

[weewx-user] Re: Problem with steel gauges

[Jerry Deibel]

Gary,

That stumped me also.   I could not fathom how the simulator data was being 
displayed...
But,,   I few times when the page updated I did see the correct data in the 
gauges for maybe 2-3 seconds
and then it went to the simulator data   
I  did NOT notice if it saidObserverip or Simulator down the bottom of 
the page.
Thanks for your help.
Jerry 

On Wednesday, January 18, 2017 at 6:43:53 PM UTC-5, Jerry Deibel wrote:
>
> Hi all,
> I just installed the steel gauges to my weewx system.
> When I first start it and look at my web pagen2uz.net/myweather/ss
> It looks ok,( observerIP is the station and temps, etc are ok,  but 5 
> minutes later the web page updates and the station says  Simulator 
> and the temps, etc change.
> Question is why is it updating by itself and how is it getting to the 
> simulator?
> At the same time i can look at my normal weewx output to my web page   
> n2uz.net/myweather/ 
> and that is ok.
> Can weewx do both the normal display and the steel gauge display at the 
> same time?
> Am I missing something,   Do I have to somehow stop the normal weewx 
> output.
> You can try looking at both web pages and see what is happening.
> Jerry
>
> I used the following procedure.   steelgauge version 2.5.17
> 
>
> Extract the zip package and: 
>
> copy weather_server/WeeWX/skin.conf WEEWX_SKINS_DIR/ss/ 
>
> copy weather_server/WeeWX/index.html.tmpl WEEWX_SKINS_DIR/ss/ 
>
> copy weather_server/WeeWX/gauge-data.txt.tmpl WEEWX_SKINS_DIR/ss/ 
>
> copy web_server/css folder to WEEWX_SKINS_DIR/ss/ 
>
> copy web_server/scripts folder to WEEWX_SKINS_DIR/ss/ 
>
> we need to edit: WEEWX_SKINS_DIR/ss/scripts/gauges.js 
>
> weatherProgram : 6
> imgPathURL : ''
> stationTimeout : 10 // set to twice archive interval, in minutes
> showUvGauge : true or false // false if there is no UV sensor
> showSolarGauge : true or false  // false if there is no solar radiation sensor
>
> add a SteelSeries section to StdReport in weewx.conf 
>
> [StdReport]
> ...
> [[SteelSeries]]
> skin = ss
> HTML_ROOT = public_html/ss
>
> The path on HTML_ROOT = public_html/ss may need to be altered to match 
> your setup. 
>
> Then restart server: 
>
> service weewx stop
> service weewx start
>
> You should be now able to access your gauges from 
> http://your-server-address/ss once the gauges have been generated. 
>
> You'll need to create a link from your main page to the ss page so people 
> and reach 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: Problem with steel gauges

[gjr80]

Good to hear it is fixed but I am a little perplexed as to why it cured the 
appearance of 'Simulator', the simulator data and associated mouseover 
plots. Probably a good reason why we need to get the SteelGauges packaged 
as an extension.

Gary

On Friday, 20 January 2017 07:00:49 UTC+10, Jerry Deibel wrote:
>
>  FIXED,
>
> Ok,  in weewx.conf [[StandardReport]] section moving the [[SteelSeries]] 
> report in front of the FTP  worked.  '
> I had it at the end.
>
> I have been running for 3 hours now and all is ok.
> Thanks to everyone who helped.
> Jerry
>
> On Wednesday, January 18, 2017 at 6:43:53 PM UTC-5, Jerry Deibel wrote:
>>
>> Hi all,
>> I just installed the steel gauges to my weewx system.
>> When I first start it and look at my web pagen2uz.net/myweather/ss
>> It looks ok,( observerIP is the station and temps, etc are ok,  but 5 
>> minutes later the web page updates and the station says  Simulator 
>> and the temps, etc change.
>> Question is why is it updating by itself and how is it getting to the 
>> simulator?
>> At the same time i can look at my normal weewx output to my web page   
>> n2uz.net/myweather/ 
>> and that is ok.
>> Can weewx do both the normal display and the steel gauge display at the 
>> same time?
>> Am I missing something,   Do I have to somehow stop the normal weewx 
>> output.
>> You can try looking at both web pages and see what is happening.
>> Jerry
>>
>> I used the following procedure.   steelgauge version 2.5.17
>> 
>>
>> Extract the zip package and: 
>>
>> copy weather_server/WeeWX/skin.conf WEEWX_SKINS_DIR/ss/ 
>>
>> copy weather_server/WeeWX/index.html.tmpl WEEWX_SKINS_DIR/ss/ 
>>
>> copy weather_server/WeeWX/gauge-data.txt.tmpl WEEWX_SKINS_DIR/ss/ 
>>
>> copy web_server/css folder to WEEWX_SKINS_DIR/ss/ 
>>
>> copy web_server/scripts folder to WEEWX_SKINS_DIR/ss/ 
>>
>> we need to edit: WEEWX_SKINS_DIR/ss/scripts/gauges.js 
>>
>> weatherProgram : 6
>> imgPathURL : ''
>> stationTimeout : 10 // set to twice archive interval, in minutes
>> showUvGauge : true or false // false if there is no UV sensor
>> showSolarGauge : true or false  // false if there is no solar radiation 
>> sensor
>>
>> add a SteelSeries section to StdReport in weewx.conf 
>>
>> [StdReport]
>> ...
>> [[SteelSeries]]
>> skin = ss
>> HTML_ROOT = public_html/ss
>>
>> The path on HTML_ROOT = public_html/ss may need to be altered to match 
>> your setup. 
>>
>> Then restart server: 
>>
>> service weewx stop
>> service weewx start
>>
>> You should be now able to access your gauges from 
>> http://your-server-address/ss once the gauges have been generated. 
>>
>> You'll need to create a link from your main page to the ss page so people 
>> and reach 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: Added sensors to weewx and Pi

[Ruben Navarro Huedo]

A lot of thank's for this great post.
I will install only a bmp280.
Can i use your scripts with it? (i will not use sht31)

Thank's a lot.

El viernes, 8 de abril de 2016, 3:06:25 (UTC+2), Neville Davis escribió:
>
> I am breadboarding with a pi and weewx my own weather station. I have a 
> WMR200a with weewx and it has been running for a couple of years. I have 
> noticed that there have been other queries about adding sensors to weewx 
> but no follow up if they were successful.
>
> I am providing here what I have working incase others may be interested. 
> The sensors in use so far are the BMP280 and SHT31, as well as OWFS rain 
> sensor. I am in the process of adding a davis wind vane and direction.
>
> The screen shots show how the 2 temp sensors track and you can see the 
> effect when I turned on the aircon for a test.
>
> Run simplest to get data from the BMP280 (enable the debug data), and the 
> sensordata script is the main script to create the csv file for weewx.
>
> Because there is a lot of writing to the SD card I have created and use a 
> RAM disk.
>
> Hope this maybe useful
>
> Neville 
>

-- 
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: Problem with steel gauges

[Jerry Deibel]

 FIXED,

Ok,  in weewx.conf [[StandardReport]] section moving the [[SteelSeries]] 
report in front of the FTP  worked.  '
I had it at the end.

I have been running for 3 hours now and all is ok.
Thanks to everyone who helped.
Jerry

On Wednesday, January 18, 2017 at 6:43:53 PM UTC-5, Jerry Deibel wrote:
>
> Hi all,
> I just installed the steel gauges to my weewx system.
> When I first start it and look at my web pagen2uz.net/myweather/ss
> It looks ok,( observerIP is the station and temps, etc are ok,  but 5 
> minutes later the web page updates and the station says  Simulator 
> and the temps, etc change.
> Question is why is it updating by itself and how is it getting to the 
> simulator?
> At the same time i can look at my normal weewx output to my web page   
> n2uz.net/myweather/ 
> and that is ok.
> Can weewx do both the normal display and the steel gauge display at the 
> same time?
> Am I missing something,   Do I have to somehow stop the normal weewx 
> output.
> You can try looking at both web pages and see what is happening.
> Jerry
>
> I used the following procedure.   steelgauge version 2.5.17
> 
>
> Extract the zip package and: 
>
> copy weather_server/WeeWX/skin.conf WEEWX_SKINS_DIR/ss/ 
>
> copy weather_server/WeeWX/index.html.tmpl WEEWX_SKINS_DIR/ss/ 
>
> copy weather_server/WeeWX/gauge-data.txt.tmpl WEEWX_SKINS_DIR/ss/ 
>
> copy web_server/css folder to WEEWX_SKINS_DIR/ss/ 
>
> copy web_server/scripts folder to WEEWX_SKINS_DIR/ss/ 
>
> we need to edit: WEEWX_SKINS_DIR/ss/scripts/gauges.js 
>
> weatherProgram : 6
> imgPathURL : ''
> stationTimeout : 10 // set to twice archive interval, in minutes
> showUvGauge : true or false // false if there is no UV sensor
> showSolarGauge : true or false  // false if there is no solar radiation sensor
>
> add a SteelSeries section to StdReport in weewx.conf 
>
> [StdReport]
> ...
> [[SteelSeries]]
> skin = ss
> HTML_ROOT = public_html/ss
>
> The path on HTML_ROOT = public_html/ss may need to be altered to match 
> your setup. 
>
> Then restart server: 
>
> service weewx stop
> service weewx start
>
> You should be now able to access your gauges from 
> http://your-server-address/ss once the gauges have been generated. 
>
> You'll need to create a link from your main page to the ss page so people 
> and reach 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.

Re: [weewx-user] Re: Trying to run SDR

[Ruben Navarro Huedo]

Hello again:

A little question:
How can i show battery status on html?
what variable must i use?

root@raspberrypi:/usr/share/
weewx # sudo PYTHONPATH=/usr/share/weewx python 
/usr/share/weewx/user/sdr.py --cmd="rtl_433 -q -U -G"
out: ['2017-01-18 13:01:39 \t:\tOS :\tTHGR122N\n', '\tHouse Code:\t 211\n', 
'\tChannel:\t 1\n', '\tBattery:\t LOW\n', '\tTemperature:\t 7.30 C\n', 
'\tHumidity:\t 28 %\n']
parsed: {'temperature.1:211.OSTHGR122NPacket': 7.3, 
'humidity.1:211.OSTHGR122NPacket': 28.0, 'battery.1:211.OSTHGR122NPacket': 
1, 'usUnits': 16, 'dateTime': 1484744499}
out: ['2017-01-18 13:01:39 \t:\tOS :\tTHGR122N\n', '\tHouse Code:\t 211\n', 
'\tChannel:\t 1\n', '\tBattery:\t LOW\n', '\tTemperature:\t 7.30 C\n', 
'\tHumidity:\t 28 %\n']
parsed: {'temperature.1:211.OSTHGR122NPacket': 7.3, 
'humidity.1:211.OSTHGR122NPacket': 28.0, 'battery.1:211.OSTHGR122NPacket': 
1, 'usUnits': 16, 'dateTime': 1484744499}

tnx a lot.

El miércoles, 18 de enero de 2017, 16:31:03 (UTC+1), mwall escribió:
>
> On Wednesday, January 18, 2017 at 9:58:14 AM UTC-5, Ruben Navarro Huedo 
> wrote:
>>
>> My rtl_433 is located in /usr/local/bin 
>>
>> I have modified weewx.conf and i think something is better now, but it 
>> is not updating files in /var/www/html/weewx 
>>
>> What is wrong now? 
>>
>
> perhaps you just need to wait awhile?  html files are generated by 
> StdReport, which runs every archive interval.
>
> btw, you are missing temperature (see the 'sdr: MainThread: packet=' 
> message).  the packet reports temperature_C not temperature.
>
> (this is another inconsistency in the rtl_433 decoders.  it makes it 
> difficult to do consistent unit conversions and sensor mappings.)
>
> 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] Re: engine: Unable to load driver: (5, 'Input/output error')

[mwall]

On Thursday, January 19, 2017 at 9:23:10 AM UTC-5, Kevin Bosworth wrote:
>
> It is a old dell laptop. Latitude D600. Serial port and ttyS0 exists. Do I 
> need to install a different library?


no need to install any libraries.

now try running the driver directly.  if you installed from deb package, it 
looks like this:

cd /usr/share/weewx
sudo PYTHONPATH=. python weewx/drivers/ws23xx.py --port /dev/ttyS0 
--readings

if you installed using setup.py it looks like this:

cd /home/weewx/bin
sudo PYTHONPATH=. python weewx/drivers/ws23xx.py --port /dev/ttyS0 
--readings

you should see readings from the station sensors.

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] Re: engine: Unable to load driver: (5, 'Input/output error')

[kevin.w7...@gmail.com]

It is a old dell laptop. Latitude D600. Serial port and ttyS0 exists. Do I need 
to install a different library?

Kevin

Sent from Yahoo Mail on Android 
 
  On Thu, Jan 19, 2017 at 6:38 AM, mwall wrote:   
On Thursday, January 19, 2017 at 8:14:46 AM UTC-5, Kevin Bosworth wrote:
What is fcntl/select?

 kevin,

those are the functions that the ws23xx driver uses to communicate over the 
serial port.  they are more direct than the pyserial library that many other 
drivers use.

what kind of computer are you using now?

is the weather station connected to a serial port, or to a usb port using a 
serial-to-usb adapter?

m 


-- 
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/topic/weewx-user/NpeOl7xJ0BQ/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.

[weewx-user] Re: Error charts update

[aleandro93]

For Gary
So if i open url of my website that's into log posted, i see my page 
index.html reloaded perfectly, but if i open my website from broswer i see 
charts stops.

For Andrew 
If i go to /var/www/html/weewx (from my raspberry) i see all files 
reloaded, correct images and file, but i don't find public_html/index.html 
on my folder.

-- 
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] weewx[5570]: engine: Caught database OperationalError: (1054, "Unknown column 'usUnits' in 'field list'")

[Dan'l B]

On Thursday, January 19, 2017 at 7:37:43 AM UTC-5, Tom Keffer wrote:
>
> I have been unable to get these to work with any debug message on my copy 
> of Sierra. For example, try this:
>
>
> Clunky non-intuitive interface. This is an improvement?
>
> Any Mac experts out there? The inability to read debug log messages is 
> making it tough to get weewx working on a Mac.
>

Tom,

While I'm the one who started this thread, let me say that WeeWx works 
beautifully on my El Cap setup; this particular logging issue has been 
confined to my MySQL issue; in general the log with debug=1 works fine. 
That said, i have not ventured into customization very far so this may not 
be useful feedback.
 

>
> On Wed, Jan 18, 2017 at 5:29 PM, mwall  > wrote:
>
>> for those running macos sierra: the 'unified logging system' has replaced 
>> asl and syslog:
>>
>>
>> https://developer.apple.com/library/content/releasenotes/MacOSX/WhatsNewInOSX/Articles/OSXv10.html
>>
>> this has some useful details for using the new 'log' command to read the 
>> new binary logs:
>>
>>
>> https://www.mac4n6.com/blog/2016/11/13/new-macos-sierra-1012-forensic-artifacts-introducing-unified-logging
>>
>> it also notes that by default, the 'info' and 'debug' levels are not 
>> displayed.
>>
>> 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+...@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: engine: Unable to load driver: (5, 'Input/output error')

[Andrew Milner]

See 'running weewx' in the user guide.


On Thursday, 19 January 2017 14:52:42 UTC+2, Kevin Bosworth wrote:

> How do I run it normally and not as a daemon?
>
> Kevin
>
> Sent from Yahoo Mail on Android
>
> On Thu, Jan 19, 2017 at 4:40 AM, Thomas Keffer
> > wrote:
> Things to try:
>
> Does /dev/ttyS0 actually exist?
>
> It looks like you are running weewxd as a daemon, which is usually run as 
> root, so adding yourself to the dialout group will not make any difference. 
> In any case, try running from the command line, and try running as root (by 
> using a 'sudo' prefix). This may give you clues. 
>
> Try running the driver directly. It can give you more clues about what's 
> happening. The command
>
> PYTHONPATH=/usr/share/weewx python 
> /usr/share/weewx/weewx/drivers/ws23xx.py --help
>
> will show you the options available.
>
> -tk
>
> On Thu, Jan 19, 2017 at 3:17 AM, Kevin Bosworth  
> wrote:
>
>> Can anyone help me out here??!!
>>
>>
>>
>> On Monday, January 9, 2017 at 4:39:17 AM UTC-7, Kevin Bosworth wrote:
>>>
>>> I had this running on an older Lubuntu laptop that died. Seems I had no 
>>> problems then. So here is what I have.
>>>
>>> Lubuntu 12.04
>>>
>>>
>>> sudo tail -f /var/log/syslog
>>> Jan  9 04:25:54 weather weewx[3277]: engine: Platform 
>>> Linux-3.2.0-119-generic-i686-w ith-Ubuntu-12.04-precise
>>> Jan  9 04:25:54 weather weewx[3277]: engine: pid file is 
>>> /var/run/weewx.pid
>>> Jan  9 04:25:54 weather weewx[3281]: engine: Using configuration file 
>>> /etc/weewx/weewx.conf
>>> Jan  9 04:25:54 weather weewx[3281]: engine: Loading station type WS23xx 
>>> (weewx.drivers.ws23xx)
>>> Jan  9 04:25:54 weather weewx[3281]: ws23xx: driver version is 0.25
>>> Jan  9 04:25:54 weather weewx[3281]: ws23xx: serial port is /dev/ttyS0
>>> Jan  9 04:25:54 weather weewx[3281]: ws23xx: polling interval is None
>>> Jan  9 04:25:54 weather weewx[3281]: import of driver failed: (5, 
>>> 'Input/output error') ()
>>> Jan  9 04:25:54 weather weewx[3281]: engine: Unable to load driver: (5, 
>>> 'Input/output error')
>>> Jan  9 04:25:54 weather weewx[3281]:   Exiting...
>>> Jan  9 04:30:07 weather kernel: [ 4758.327907] b43legacy-phy0 ERROR: PHY 
>>> transmission error
>>> Jan  9 04:31:23 weather wpa_supplicant[1050]: WPA: Group rekeying 
>>> completed with 14:91:82:bd:0f:77 [GTK=TKIP]
>>> Jan  9 04:33:57 weather kernel: [ 4988.761336] b43legacy-phy0 ERROR: PHY 
>>> transmission error
>>>
>>> Not sure what else to do. Tried copying my old backup config files with 
>>> the same results. I did add myself to to the dailout group.
>>>
>>> Thanks, Kevin
>>>
>> -- 
>> 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+unsubscribe@ 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/topic/weewx-user/NpeOl7xJ0BQ/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.

[weewx-user] Re: Error charts update

[Andrew Milner]

If you brouse to /var/www/html/weewx/index.html on your local machine do 
you see the correct page AND correct images??
If you browse to /etc/weewx/public_html/index.html on your local machine do 
you see the correct page and correct images??

Can you give the output from ls -l *.png in public_html and also from ls -l 
*.png in /var/www/html/weewx



On Thursday, 19 January 2017 15:35:52 UTC+2, gjr80 wrote:

> Well, after much flicking from screen to screen :) , it appears that weewx 
> is generating the day images :
>
> 13:36:43 genimages: Generated 12 images for StandardReport in 4.92 seconds
>
> and despite the ftp error message:
>
> 13:36:43 ftpupload: Unable to connect or log into server : [Errno 104] 
> Connection reset by peer
>
> it appears that 12 day pngs are uploaded along with the other html etc 
> files. The html files are all making it to your web server so should the 
> pngs. The only thing I can think of is to download one of the day png 
> files, eg daytempdex.png to your PC, open the file and see what timestamp 
> it has. The file will be in /var/www/html/weewx on your weewx machine. If 
> the timestamp is current then it is an FTP problem otherwise it is 
> something really weird.
>
> Gary
>
> On Thursday, 19 January 2017 22:42:42 UTC+10, alean...@hotmail.com wrote:
>>
>>
>> These are the logs of startup of weewx.
>>
>

-- 
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: Error charts update

[aleandro93]

 sudo tail -f -n50 /var/log/syslog
Jan 19 14:41:10 raspberrypi weewx[3166]: reportengine: Found configuration 
file /etc/weewx/skins/Standard/skin.conf for report StandardReport
Jan 19 14:41:10 raspberrypi weewx[3166]: restx: Wunderground-PWS: Published 
record 2017-01-19 14:40:00 CET (1484833200)
Jan 19 14:41:11 raspberrypi weewx[3166]: cheetahgenerator: using search 
list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras']
Jan 19 14:41:36 raspberrypi weewx[3166]: cheetahgenerator: Generated 14 
files for report StandardReport in 25.50 seconds
Jan 19 14:41:36 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
next retry is Thu Jan 19 14:43:06 2017 [try http://www.rsyslog.com/e/2007 ]
Jan 19 14:41:41 raspberrypi weewx[3166]: genimages: Generated 12 images for 
StandardReport in 4.93 seconds
Jan 19 14:41:41 raspberrypi weewx[3166]: reportengine: copied 9 files to 
/var/www/html/weewx
Jan 19 14:41:41 raspberrypi weewx[3166]: reportengine: Running report FTP
Jan 19 14:41:41 raspberrypi weewx[3166]: reportengine: Found configuration 
file /etc/weewx/skins/Ftp/skin.conf for report FTP
Jan 19 14:41:41 raspberrypi weewx[3166]: ftpupload: Attempting secure 
connection to ftp.stazionemeteopce.altervista.org
Jan 19 14:41:42 raspberrypi weewx[3166]: ftpupload: Secure connection to 
ftp.stazionemeteopce.altervista.org
Jan 19 14:41:43 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/daytempdew.png
Jan 19 14:41:44 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/index.html
Jan 19 14:41:45 raspberrypi weewx[3166]: ftpupload: Uploaded file /year.html
Jan 19 14:41:46 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/daybarometer.png
Jan 19 14:41:47 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/daywindvec.png
Jan 19 14:41:48 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/dayinside.png
Jan 19 14:41:48 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/daywind.png
Jan 19 14:41:49 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/dayrain.png
Jan 19 14:41:50 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/month.html
Jan 19 14:41:51 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/favicon.ico
Jan 19 14:41:52 raspberrypi weewx[3166]: ftpupload: Uploaded file /weewx.css
Jan 19 14:41:53 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/daywinddir.png
Jan 19 14:41:53 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/dayradiation.png
Jan 19 14:41:54 raspberrypi weewx[3166]: ftpupload: Uploaded file /week.html
Jan 19 14:41:55 raspberrypi weewx[3166]: ftpupload: Uploaded file /dayrx.png
Jan 19 14:41:56 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/mobile.html
Jan 19 14:41:57 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/daypond.png
Jan 19 14:41:58 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/daytempchill.png
Jan 19 14:41:59 raspberrypi weewx[3166]: ftpupload: Uploaded file /dayuv.png
Jan 19 14:41:59 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/mobile.css
Jan 19 14:42:00 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/NOAA/NOAA-2017.txt
Jan 19 14:42:01 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/NOAA/NOAA-2017-01.txt
Jan 19 14:42:02 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/backgrounds/band.gif
Jan 19 14:42:03 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/RSS/weewx_rss.xml
Jan 19 14:42:04 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/smartphone/index.html
Jan 19 14:42:04 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/smartphone/wind.html
Jan 19 14:42:05 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/smartphone/barometer.html
Jan 19 14:42:06 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/smartphone/temp_outside.html
Jan 19 14:42:07 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/smartphone/rain.html
Jan 19 14:42:08 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/smartphone/radar.html
Jan 19 14:42:08 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/smartphone/custom.js
Jan 19 14:42:09 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/smartphone/icons/icon_ipad_x2.png
Jan 19 14:42:10 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/smartphone/icons/icon_iphone_x1.png
Jan 19 14:42:11 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/smartphone/icons/icon_iphone_x2.png
Jan 19 14:42:12 raspberrypi weewx[3166]: ftpupload: Uploaded file 
/smartphone/icons/icon_ipad_x1.png
Jan 19 14:42:12 raspberrypi weewx[3166]: reportengine: ftp'd 35 files in 
30.41 seconds
Jan 19 14:42:12 raspberrypi weewx[3166]: reportengine: Running report RSYNC
Jan 19 14:42:12 raspberrypi weewx[3166]: reportengine: Found configuration 
file /etc/weewx/skins/Rsync/skin.conf for report RSYNC
Jan 19 14:42:12 raspberrypi weewx[3166]: reportengine: rsync upload not 
requested. Skipped.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiv

[weewx-user] gauge-data.txt file not being generated SS gauges

[Robert Mantel]

I have a brand new Raspberry Pi running the latest version of weewx.  I 
have it working with the default skin and also the Bootstrap skin with no 
issues.  I'm using fileparse.py to grab data from a text file that gets 
generated from a python script that does a jsonp query to my phant server 
that is archiving the raw data from my particle photon weather hardware. 
 Like probably everyone else I came across the SS gauges and love the look 
and feel of them so proceeded with the install and followed the 
instructions, modifying the gauges.js file and movnig all the appropriate 
files into my weewx install.  The gauges are reproduced perfectly, but no 
data is being input and I get the following error in syslog:


Jan 19 08:27:04 raspberrypi weewx[23078]: manager: added record 2017-01-19 
08:26:00 EST (1484832360) to database 'weewx.sdb'
Jan 19 08:27:04 raspberrypi weewx[23078]: manager: added record 2017-01-19 
08:26:00 EST (1484832360) to daily summary in 'weewx.sdb'
Jan 19 08:27:04 raspberrypi weewx[23078]: reportengine: copied 0 files to 
/var/www/html/weewx
Jan 19 08:27:04 raspberrypi weewx[23078]: cheetahgenerator: Generate failed 
with exception ''
Jan 19 08:27:04 raspberrypi weewx[23078]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/ss/gauge-data.txt.tmpl
Jan 19 08:27:04 raspberrypi weewx[23078]: cheetahgenerator:  Reason: 
unsupported operand type(s) for *: 'NoneType' and 'int'
Jan 19 08:27:04 raspberrypi weewx[23078]:   Traceback (most recent call 
last):
Jan 19 08:27:04 raspberrypi weewx[23078]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 315, in generate
Jan 19 08:27:04 raspberrypi weewx[23078]:   print >> _file, text
Jan 19 08:27:04 raspberrypi weewx[23078]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Jan 19 08:27:04 raspberrypi weewx[23078]:   rc = getattr(self, 
mainMethName)()
Jan 19 08:27:04 raspberrypi weewx[23078]: File 
"cheetah__etc_weewx_skins_ss_gauge_data_txt_tmpl_1484791504_04_19193.py", 
line 326, in respond
Jan 19 08:27:04 raspberrypi weewx[23078]:   TypeError: unsupported 
operand type(s) for *: 'NoneType' and 'int'


I'm wracking my brain trying to find in the gauge-data.txt.tmpl file what 
could be causing the operand error and obviously it's a bogus variable in 
one of the math functions.  So I suspect that there is some missing data 
that I'm not supplying it?  Also of note, when I set up weewx I chose 
metricwx for the display units, but the database is using US units.  Is 
this my problem?  Should I have stuck with US display units as well when I 
did the initial install?

-- 
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: engine: Unable to load driver: (5, 'Input/output error')

[mwall]

On Thursday, January 19, 2017 at 8:14:46 AM UTC-5, Kevin Bosworth wrote:
>
> What is fcntl/select?


 
kevin,

those are the functions that the ws23xx driver uses to communicate over the 
serial port.  they are more direct than the pyserial library that many 
other drivers use.

what kind of computer are you using now?

is the weather station connected to a serial port, or to a usb port using a 
serial-to-usb adapter?

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.

[weewx-user] Re: Error charts update

[gjr80]

Well, after much flicking from screen to screen :) , it appears that weewx 
is generating the day images :

13:36:43 genimages: Generated 12 images for StandardReport in 4.92 seconds

and despite the ftp error message:

13:36:43 ftpupload: Unable to connect or log into server : [Errno 104] 
Connection reset by peer

it appears that 12 day pngs are uploaded along with the other html etc 
files. The html files are all making it to your web server so should the 
pngs. The only thing I can think of is to download one of the day png 
files, eg daytempdex.png to your PC, open the file and see what timestamp 
it has. The file will be in /var/www/html/weewx on your weewx machine. If 
the timestamp is current then it is an FTP problem otherwise it is 
something really weird.

Gary

On Thursday, 19 January 2017 22:42:42 UTC+10, alean...@hotmail.com wrote:
>
>
> These are the logs of startup of weewx.
>

-- 
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: engine: Unable to load driver: (5, 'Input/output error')

[kevin.w7...@gmail.com]

What is fcntl/select?

Kevin

Sent from Yahoo Mail on Android 
 
  On Thu, Jan 19, 2017 at 6:05 AM, kevin.w7...@gmail.com 
wrote:   I have read that big freaking manual 20 times already. Wonder how I 
ever got the dang thing working in the first place. For some reason it seems 
like I had heavyweather running also But I don't remember.

Kevin

Sent from Yahoo Mail on Android 
 
  On Thu, Jan 19, 2017 at 5:58 AM, Thomas Keffer wrote:   
See the manual.
-tk
On Thu, Jan 19, 2017 at 4:52 AM, kevin.w7...@gmail.com  
wrote:

How do I run it normally and not as a daemon?

Kevin

Sent from Yahoo Mail on Android 
 
 On Thu, Jan 19, 2017 at 4:40 AM, Thomas Keffer wrote:  
Things to try:
Does /dev/ttyS0 actually exist?
It looks like you are running weewxd as a daemon, which is usually run as root, 
so adding yourself to the dialout group will not make any difference. In any 
case, try running from the command line, and try running as root (by using a 
'sudo' prefix). This may give you clues. 
Try running the driver directly. It can give you more clues about what's 
happening. The command
PYTHONPATH=/usr/share/weewx python /usr/share/weewx/weewx/ drivers/ws23xx.py 
--help
will show you the options available.
-tk
On Thu, Jan 19, 2017 at 3:17 AM, Kevin Bosworth  wrote:

Can anyone help me out here??!!


On Monday, January 9, 2017 at 4:39:17 AM UTC-7, Kevin Bosworth wrote:
I had this running on an older Lubuntu laptop that died. Seems I had no 
problems then. So here is what I have.

Lubuntu 12.04


sudo tail -f /var/log/syslog
Jan  9 04:25:54 weather weewx[3277]: engine: Platform 
Linux-3.2.0-119-generic-i686-w ith-Ubuntu-12.04-precise
Jan  9 04:25:54 weather weewx[3277]: engine: pid file is /var/run/weewx.pid
Jan  9 04:25:54 weather weewx[3281]: engine: Using configuration file 
/etc/weewx/weewx.conf
Jan  9 04:25:54 weather weewx[3281]: engine: Loading station type WS23xx 
(weewx.drivers.ws23xx)
Jan  9 04:25:54 weather weewx[3281]: ws23xx: driver version is 0.25
Jan  9 04:25:54 weather weewx[3281]: ws23xx: serial port is /dev/ttyS0
Jan  9 04:25:54 weather weewx[3281]: ws23xx: polling interval is None
Jan  9 04:25:54 weather weewx[3281]: import of driver failed: (5, 'Input/output 
error') ()
Jan  9 04:25:54 weather weewx[3281]: engine: Unable to load driver: (5, 
'Input/output error')
Jan  9 04:25:54 weather weewx[3281]:   Exiting...
Jan  9 04:30:07 weather kernel: [ 4758.327907] b43legacy-phy0 ERROR: PHY 
transmission error
Jan  9 04:31:23 weather wpa_supplicant[1050]: WPA: Group rekeying completed 
with 14:91:82:bd:0f:77 [GTK=TKIP]
Jan  9 04:33:57 weather kernel: [ 4988.761336] b43legacy-phy0 ERROR: PHY 
transmission error

Not sure what else to do. Tried copying my old backup config files with the 
same results. I did add myself to to the dailout group.

Thanks, Kevin



-- 
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+unsubscribe@ 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/ 
topic/weewx-user/NpeOl7xJ0BQ/ unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscribe@ 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+unsubscribe@ 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/topic/weewx-user/NpeOl7xJ0BQ/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.

[weewx-user] Re: Error charts update

[gjr80]

I thought you were installing putty so you could capture the text rather 
than post screen captures! When you are using putty if you run the command:

$ tail -f -n 50 /var/log/syslog

in the putty session window you will see the last 50 lines of syslog in the 
putty window and any subsequent lines sent to log will appear at the 
bottom. Open another putty session and execute the command you want to 
capture the log output from eg:

$ sudo service weewx stop
$ sudo service weewx start

You will see the syslog output from the commands (in this case stop then 
start weewx) appear on the screen and you can use you mouse to highlight 
the syslog text you want. Once the text is highlighted with the mouse it is 
automatically copied to the clipboard and you can then paste the text (not 
a picture or a jpg) to the forums. Much easier for us to help then.

Gary

On Thursday, 19 January 2017 22:42:42 UTC+10, alean...@hotmail.com wrote:
>
>
> These are the logs of startup of weewx.
>

-- 
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: engine: Unable to load driver: (5, 'Input/output error')

[kevin.w7...@gmail.com]

I have read that big freaking manual 20 times already. Wonder how I ever got 
the dang thing working in the first place. For some reason it seems like I had 
heavyweather running also But I don't remember.

Kevin

Sent from Yahoo Mail on Android 
 
  On Thu, Jan 19, 2017 at 5:58 AM, Thomas Keffer wrote:   
See the manual.
-tk
On Thu, Jan 19, 2017 at 4:52 AM, kevin.w7...@gmail.com  
wrote:

How do I run it normally and not as a daemon?

Kevin

Sent from Yahoo Mail on Android 
 
 On Thu, Jan 19, 2017 at 4:40 AM, Thomas Keffer wrote:  
Things to try:
Does /dev/ttyS0 actually exist?
It looks like you are running weewxd as a daemon, which is usually run as root, 
so adding yourself to the dialout group will not make any difference. In any 
case, try running from the command line, and try running as root (by using a 
'sudo' prefix). This may give you clues. 
Try running the driver directly. It can give you more clues about what's 
happening. The command
PYTHONPATH=/usr/share/weewx python /usr/share/weewx/weewx/ drivers/ws23xx.py 
--help
will show you the options available.
-tk
On Thu, Jan 19, 2017 at 3:17 AM, Kevin Bosworth  wrote:

Can anyone help me out here??!!


On Monday, January 9, 2017 at 4:39:17 AM UTC-7, Kevin Bosworth wrote:
I had this running on an older Lubuntu laptop that died. Seems I had no 
problems then. So here is what I have.

Lubuntu 12.04


sudo tail -f /var/log/syslog
Jan  9 04:25:54 weather weewx[3277]: engine: Platform 
Linux-3.2.0-119-generic-i686-w ith-Ubuntu-12.04-precise
Jan  9 04:25:54 weather weewx[3277]: engine: pid file is /var/run/weewx.pid
Jan  9 04:25:54 weather weewx[3281]: engine: Using configuration file 
/etc/weewx/weewx.conf
Jan  9 04:25:54 weather weewx[3281]: engine: Loading station type WS23xx 
(weewx.drivers.ws23xx)
Jan  9 04:25:54 weather weewx[3281]: ws23xx: driver version is 0.25
Jan  9 04:25:54 weather weewx[3281]: ws23xx: serial port is /dev/ttyS0
Jan  9 04:25:54 weather weewx[3281]: ws23xx: polling interval is None
Jan  9 04:25:54 weather weewx[3281]: import of driver failed: (5, 'Input/output 
error') ()
Jan  9 04:25:54 weather weewx[3281]: engine: Unable to load driver: (5, 
'Input/output error')
Jan  9 04:25:54 weather weewx[3281]:   Exiting...
Jan  9 04:30:07 weather kernel: [ 4758.327907] b43legacy-phy0 ERROR: PHY 
transmission error
Jan  9 04:31:23 weather wpa_supplicant[1050]: WPA: Group rekeying completed 
with 14:91:82:bd:0f:77 [GTK=TKIP]
Jan  9 04:33:57 weather kernel: [ 4988.761336] b43legacy-phy0 ERROR: PHY 
transmission error

Not sure what else to do. Tried copying my old backup config files with the 
same results. I did add myself to to the dailout group.

Thanks, Kevin



-- 
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+unsubscribe@ 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/ 
topic/weewx-user/NpeOl7xJ0BQ/ unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscribe@ 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+unsubscribe@ 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/topic/weewx-user/NpeOl7xJ0BQ/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.

Re: [weewx-user] Re: engine: Unable to load driver: (5, 'Input/output error')

[Thomas Keffer]

See the manual .

-tk

On Thu, Jan 19, 2017 at 4:52 AM, kevin.w7...@gmail.com <
kevin.w7...@gmail.com> wrote:

> How do I run it normally and not as a daemon?
>
> Kevin
>
> Sent from Yahoo Mail on Android
>
> On Thu, Jan 19, 2017 at 4:40 AM, Thomas Keffer
>  wrote:
> Things to try:
>
> Does /dev/ttyS0 actually exist?
>
> It looks like you are running weewxd as a daemon, which is usually run as
> root, so adding yourself to the dialout group will not make any difference.
> In any case, try running from the command line, and try running as root (by
> using a 'sudo' prefix). This may give you clues.
>
> Try running the driver directly. It can give you more clues about what's
> happening. The command
>
> PYTHONPATH=/usr/share/weewx python /usr/share/weewx/weewx/drivers/ws23xx.py
> --help
>
> will show you the options available.
>
> -tk
>
> On Thu, Jan 19, 2017 at 3:17 AM, Kevin Bosworth 
> wrote:
>
>> Can anyone help me out here??!!
>>
>>
>>
>> On Monday, January 9, 2017 at 4:39:17 AM UTC-7, Kevin Bosworth wrote:
>>>
>>> I had this running on an older Lubuntu laptop that died. Seems I had no
>>> problems then. So here is what I have.
>>>
>>> Lubuntu 12.04
>>>
>>>
>>> sudo tail -f /var/log/syslog
>>> Jan  9 04:25:54 weather weewx[3277]: engine: Platform
>>> Linux-3.2.0-119-generic-i686-w ith-Ubuntu-12.04-precise
>>> Jan  9 04:25:54 weather weewx[3277]: engine: pid file is
>>> /var/run/weewx.pid
>>> Jan  9 04:25:54 weather weewx[3281]: engine: Using configuration file
>>> /etc/weewx/weewx.conf
>>> Jan  9 04:25:54 weather weewx[3281]: engine: Loading station type WS23xx
>>> (weewx.drivers.ws23xx)
>>> Jan  9 04:25:54 weather weewx[3281]: ws23xx: driver version is 0.25
>>> Jan  9 04:25:54 weather weewx[3281]: ws23xx: serial port is /dev/ttyS0
>>> Jan  9 04:25:54 weather weewx[3281]: ws23xx: polling interval is None
>>> Jan  9 04:25:54 weather weewx[3281]: import of driver failed: (5,
>>> 'Input/output error') ()
>>> Jan  9 04:25:54 weather weewx[3281]: engine: Unable to load driver: (5,
>>> 'Input/output error')
>>> Jan  9 04:25:54 weather weewx[3281]:   Exiting...
>>> Jan  9 04:30:07 weather kernel: [ 4758.327907] b43legacy-phy0 ERROR: PHY
>>> transmission error
>>> Jan  9 04:31:23 weather wpa_supplicant[1050]: WPA: Group rekeying
>>> completed with 14:91:82:bd:0f:77 [GTK=TKIP]
>>> Jan  9 04:33:57 weather kernel: [ 4988.761336] b43legacy-phy0 ERROR: PHY
>>> transmission error
>>>
>>> Not sure what else to do. Tried copying my old backup config files with
>>> the same results. I did add myself to to the dailout group.
>>>
>>> Thanks, Kevin
>>>
>> --
>> 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+unsubscribe@ 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/
> topic/weewx-user/NpeOl7xJ0BQ/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.
>

-- 
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: engine: Unable to load driver: (5, 'Input/output error')

[kevin.w7...@gmail.com]

How do I run it normally and not as a daemon?

Kevin

Sent from Yahoo Mail on Android 
 
  On Thu, Jan 19, 2017 at 4:40 AM, Thomas Keffer wrote:   
Things to try:
Does /dev/ttyS0 actually exist?
It looks like you are running weewxd as a daemon, which is usually run as root, 
so adding yourself to the dialout group will not make any difference. In any 
case, try running from the command line, and try running as root (by using a 
'sudo' prefix). This may give you clues. 
Try running the driver directly. It can give you more clues about what's 
happening. The command
PYTHONPATH=/usr/share/weewx python /usr/share/weewx/weewx/drivers/ws23xx.py 
--help
will show you the options available.
-tk
On Thu, Jan 19, 2017 at 3:17 AM, Kevin Bosworth  wrote:

Can anyone help me out here??!!


On Monday, January 9, 2017 at 4:39:17 AM UTC-7, Kevin Bosworth wrote:
I had this running on an older Lubuntu laptop that died. Seems I had no 
problems then. So here is what I have.

Lubuntu 12.04


sudo tail -f /var/log/syslog
Jan  9 04:25:54 weather weewx[3277]: engine: Platform 
Linux-3.2.0-119-generic-i686-w ith-Ubuntu-12.04-precise
Jan  9 04:25:54 weather weewx[3277]: engine: pid file is /var/run/weewx.pid
Jan  9 04:25:54 weather weewx[3281]: engine: Using configuration file 
/etc/weewx/weewx.conf
Jan  9 04:25:54 weather weewx[3281]: engine: Loading station type WS23xx 
(weewx.drivers.ws23xx)
Jan  9 04:25:54 weather weewx[3281]: ws23xx: driver version is 0.25
Jan  9 04:25:54 weather weewx[3281]: ws23xx: serial port is /dev/ttyS0
Jan  9 04:25:54 weather weewx[3281]: ws23xx: polling interval is None
Jan  9 04:25:54 weather weewx[3281]: import of driver failed: (5, 'Input/output 
error') ()
Jan  9 04:25:54 weather weewx[3281]: engine: Unable to load driver: (5, 
'Input/output error')
Jan  9 04:25:54 weather weewx[3281]:   Exiting...
Jan  9 04:30:07 weather kernel: [ 4758.327907] b43legacy-phy0 ERROR: PHY 
transmission error
Jan  9 04:31:23 weather wpa_supplicant[1050]: WPA: Group rekeying completed 
with 14:91:82:bd:0f:77 [GTK=TKIP]
Jan  9 04:33:57 weather kernel: [ 4988.761336] b43legacy-phy0 ERROR: PHY 
transmission error

Not sure what else to do. Tried copying my old backup config files with the 
same results. I did add myself to to the dailout group.

Thanks, Kevin



-- 
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+unsubscribe@ 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/topic/weewx-user/NpeOl7xJ0BQ/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.

[weewx-user] Re: ultimeter setup troubles

[Steve2Q]

Eelco...glad to hear you have it working now. One thing to watch is the time on 
the 2100 console itself. It should stay accurate  and if it doesn't try the 
earlier driver version I posted 

Steve 

-- 
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] weewx[5570]: engine: Caught database OperationalError: (1054, "Unknown column 'usUnits' in 'field list'")

[Thomas Keffer]

I have been unable to get these to work with any debug message on my copy
of Sierra. For example, try this:

Log a message:

logger -p user.debug "Hello weewx"


Now try to  find it:

log show --debug --start "2017-01-19" |grep weewx


Nothing...

Clunky non-intuitive interface. This is an improvement?

Any Mac experts out there? The inability to read debug log messages is
making it tough to get weewx working on a Mac.

-tk


On Wed, Jan 18, 2017 at 5:29 PM, mwall  wrote:

> for those running macos sierra: the 'unified logging system' has replaced
> asl and syslog:
>
> https://developer.apple.com/library/content/releasenotes/
> MacOSX/WhatsNewInOSX/Articles/OSXv10.html
>
> this has some useful details for using the new 'log' command to read the
> new binary logs:
>
> https://www.mac4n6.com/blog/2016/11/13/new-macos-sierra-
> 1012-forensic-artifacts-introducing-unified-logging
>
> it also notes that by default, the 'info' and 'debug' levels are not
> displayed.
>
> 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.
>

-- 
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: engine: Unable to load driver: (5, 'Input/output error')

[Thomas Keffer]

Things to try:

Does /dev/ttyS0 actually exist?

It looks like you are running weewxd as a daemon, which is usually run as
root, so adding yourself to the dialout group will not make any difference.
In any case, try running from the command line, and try running as root (by
using a 'sudo' prefix). This may give you clues.

Try running the driver directly. It can give you more clues about what's
happening. The command

PYTHONPATH=/usr/share/weewx python /usr/share/weewx/weewx/drivers/ws23xx.py
--help

will show you the options available.

-tk

On Thu, Jan 19, 2017 at 3:17 AM, Kevin Bosworth 
wrote:

> Can anyone help me out here??!!
>
>
>
> On Monday, January 9, 2017 at 4:39:17 AM UTC-7, Kevin Bosworth wrote:
>>
>> I had this running on an older Lubuntu laptop that died. Seems I had no
>> problems then. So here is what I have.
>>
>> Lubuntu 12.04
>>
>>
>> sudo tail -f /var/log/syslog
>> Jan  9 04:25:54 weather weewx[3277]: engine: Platform
>> Linux-3.2.0-119-generic-i686-with-Ubuntu-12.04-precise
>> Jan  9 04:25:54 weather weewx[3277]: engine: pid file is
>> /var/run/weewx.pid
>> Jan  9 04:25:54 weather weewx[3281]: engine: Using configuration file
>> /etc/weewx/weewx.conf
>> Jan  9 04:25:54 weather weewx[3281]: engine: Loading station type WS23xx
>> (weewx.drivers.ws23xx)
>> Jan  9 04:25:54 weather weewx[3281]: ws23xx: driver version is 0.25
>> Jan  9 04:25:54 weather weewx[3281]: ws23xx: serial port is /dev/ttyS0
>> Jan  9 04:25:54 weather weewx[3281]: ws23xx: polling interval is None
>> Jan  9 04:25:54 weather weewx[3281]: import of driver failed: (5,
>> 'Input/output error') ()
>> Jan  9 04:25:54 weather weewx[3281]: engine: Unable to load driver: (5,
>> 'Input/output error')
>> Jan  9 04:25:54 weather weewx[3281]:   Exiting...
>> Jan  9 04:30:07 weather kernel: [ 4758.327907] b43legacy-phy0 ERROR: PHY
>> transmission error
>> Jan  9 04:31:23 weather wpa_supplicant[1050]: WPA: Group rekeying
>> completed with 14:91:82:bd:0f:77 [GTK=TKIP]
>> Jan  9 04:33:57 weather kernel: [ 4988.761336] b43legacy-phy0 ERROR: PHY
>> transmission error
>>
>> Not sure what else to do. Tried copying my old backup config files with
>> the same results. I did add myself to to the dailout group.
>>
>> Thanks, Kevin
>>
> --
> 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: Aercus Instruments WeatherSleuth IP - how to guide

[Steve]

Have you plugged the bridge into the router?

The 433MHz is from the station to the bridge. The bridge is a wired 
connection to the router.

On Thursday, 19 January 2017 21:20:58 UTC+11, m...@iinet.net.au wrote:
>
> Can anyone help in Australia, I have a iinet N600 Dual Band WiFi Gigabit 
> Modem Router on a Mac based system. The setting on the box indicate a 
> 433MHz Weather Sleuth. My WiFi is 2.4 and 5 GHz. I am unable to see the 
> Weather Sleuth on my network, using either IPTool or network scanner. Is 
> this a possible reason? If not why can I not see the Weathersleuth, all 
> blue lights are active except for Server. Any help would be greatly 
> appreciated
>
> On Friday, May 13, 2016 at 10:37:13 PM UTC+8, Ashley Hinton wrote:
>>
>> Hello
>>
>> Just thought I'd post a how-to for the Aercus Instruments WeatherSleuth 
>> IP (www.aercusinstruments.com) in case anyone else considers one of 
>> these.
>> I found the unit on Amazon, supplied by Greenfrog Scientific through 
>> their Amazon store. I purchased this to replace a finally dead 
>> Gadget-branded (maplin/fine-offset) WH1080
>>
>> Thanks very much to everyone who has contributed to getting these IP 
>> weather stations running in weewx, & to Matthew (and anyone who 
>> contributed) for the Interceptor driver and for helping me diagnose a 
>> problem - nothing to do with the WeatherSleuth or the Interceptor driver, 
>> but the fact I was using an old version of the owfs driver which I use to 
>> add a couple of extra temperature measurements from my greenhouse.
>>
>> After getting this unit set-up in Weewx I thought I would post a run 
>> through of what I did.
>>
>> *The WeatherSleuth weather station*
>>
>> The outdoor array has the usual sensors (wind direction, wind speed, 
>> rain, temperature, humidity) + UV & Solar Radiation.
>> Meanwhile the indoor sensor has temperature, pressure & humidity 
>> (although I don't think indoor humidity is recorded by weewx as a default)
>>
>> The receiver base station is a small box which has an aerial for 
>> receiving the data from the outdoor & indoor sensors, an RJ-45 ethernet 
>> port & a power socket for the supplied 5vDC supply.
>> It does not feature WiFi, it must be physically plugged into using an 
>> ethernet cable, which is also supplied.
>>
>> There are a variety of status lights on the receiver, which incidentally 
>> is tiny - fits in the palm of your hand - and since it doesn't display any 
>> weather info (there is no console display) it makes it ideal if you just 
>> want to feed data into weewx and not bother with USB cables from desktop 
>> weather stations etc.
>>
>> The default set-up out of the box is feeding to Weather Underground, but 
>> this is one of the IP-based systems where the data feed destination can be 
>> easily changed.
>>
>> Mine was shipped with Firmware 2.1.9, which is the latest.
>>
>> Out of the box it comes set for DHCP, so you will have to dive into your 
>> router or use some network scanning software to find it.
>> Alternatively there is a Windows utility supplied on the (tiny**) CD 
>> (** don't slot that in your laptop or any other slot-loading drive, you'll 
>> wreck the drive)
>> Since I'm a Mac & Linux user I didn't use the windows utility but instead 
>> logged into my router and found the device - fairly easy since the 
>> MAC/hardware address is printed on a label stuck on the bottom of the 
>> receiver.
>>
>> In my case I set a Static DHCP lease in the router, but alternatively you 
>> may want to just set a static IP address within the weather station itself 
>> or just leave it DHCP, see Local Network config below.
>> Once you have the IP, open up a web browser and head to the weather 
>> station's IP address config page:
>>
>> http://*ip.address.of.the.weathersleuth.*
>>
>> There you'll see the config tabs, first one speaks for itself -*Local 
>> Network* -  DHCP or manual IP, plus fields for the router IP, DNS, 
>> Subnet etc. If you're happy to find it on DHCP if & when you need to change 
>> anything I don't see any reason not to leave it set to DHCP, as it pushes 
>> data to weewx and not the other way around.
>>
>> Next tab is for the *Weather Network*, which is where we will set it up 
>> to feed to your weewx system.
>> From the *Remote Server *pull-down menu, choose *Customized*
>>
>> In the *Server/Hostname *box, type in the IP address of the computer 
>> you're running Weeex on. In my case, its 192.168.45.100
>> I don't know, and haven't tried, whether you could supply a local named 
>> address such as "weewx.local" if your computer is called that. The only 
>> reason you might want to do this is if the computer running weewx is using 
>> DHCP - I run weewx on a ubuntu server which also does other stuff, so its 
>> on a static address on my network.
>>
>> In the *Server Port *box, specify a unique port that Weewx or other 
>> software on the computer isn't using. Try not to use standard ports even if 
>> you're not using them right no

[weewx-user] Re: engine: Unable to load driver: (5, 'Input/output error')

[Kevin Bosworth]

Can anyone help me out here??!!


On Monday, January 9, 2017 at 4:39:17 AM UTC-7, Kevin Bosworth wrote:
>
> I had this running on an older Lubuntu laptop that died. Seems I had no 
> problems then. So here is what I have.
>
> Lubuntu 12.04
>
>
> sudo tail -f /var/log/syslog
> Jan  9 04:25:54 weather weewx[3277]: engine: Platform 
> Linux-3.2.0-119-generic-i686-with-Ubuntu-12.04-precise
> Jan  9 04:25:54 weather weewx[3277]: engine: pid file is /var/run/weewx.pid
> Jan  9 04:25:54 weather weewx[3281]: engine: Using configuration file 
> /etc/weewx/weewx.conf
> Jan  9 04:25:54 weather weewx[3281]: engine: Loading station type WS23xx 
> (weewx.drivers.ws23xx)
> Jan  9 04:25:54 weather weewx[3281]: ws23xx: driver version is 0.25
> Jan  9 04:25:54 weather weewx[3281]: ws23xx: serial port is /dev/ttyS0
> Jan  9 04:25:54 weather weewx[3281]: ws23xx: polling interval is None
> Jan  9 04:25:54 weather weewx[3281]: import of driver failed: (5, 
> 'Input/output error') ()
> Jan  9 04:25:54 weather weewx[3281]: engine: Unable to load driver: (5, 
> 'Input/output error')
> Jan  9 04:25:54 weather weewx[3281]:   Exiting...
> Jan  9 04:30:07 weather kernel: [ 4758.327907] b43legacy-phy0 ERROR: PHY 
> transmission error
> Jan  9 04:31:23 weather wpa_supplicant[1050]: WPA: Group rekeying 
> completed with 14:91:82:bd:0f:77 [GTK=TKIP]
> Jan  9 04:33:57 weather kernel: [ 4988.761336] b43legacy-phy0 ERROR: PHY 
> transmission error
>
> Not sure what else to do. Tried copying my old backup config files with 
> the same results. I did add myself to to the dailout group.
>
> Thanks, Kevin
>

-- 
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: Error charts update

[aleandro93]

I think of no. Thanks.

-- 
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: Error charts update

[gjr80]

Have you enabled SSH on your RPi?  
https://www.raspberrypi.org/documentation/remote-access/ssh/

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.

[weewx-user] Re: Error charts update

[aleandro93]

Gary about for post the log of startup  of weewx (berfore stop it) i 
downloaded putty, when i try to connect to my raspberry, putty say me 
"network error: connection refused". 

-- 
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: Error charts update

[aleandro93]

Thank Milner. I managed to move the file.

-- 
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: Aercus Instruments WeatherSleuth IP - how to guide

[mm2]

Can anyone help in Australia, I have a iinet N600 Dual Band WiFi Gigabit 
Modem Router on a Mac based system. The setting on the box indicate a 
433MHz Weather Sleuth. My WiFi is 2.4 and 5 GHz. I am unable to see the 
Weather Sleuth on my network, using either IPTool or network scanner. Is 
this a possible reason? If not why can I not see the Weathersleuth, all 
blue lights are active except for Server. Any help would be greatly 
appreciated

On Friday, May 13, 2016 at 10:37:13 PM UTC+8, Ashley Hinton wrote:
>
> Hello
>
> Just thought I'd post a how-to for the Aercus Instruments WeatherSleuth IP 
> (www.aercusinstruments.com) in case anyone else considers one of these.
> I found the unit on Amazon, supplied by Greenfrog Scientific through their 
> Amazon store. I purchased this to replace a finally dead Gadget-branded 
> (maplin/fine-offset) WH1080
>
> Thanks very much to everyone who has contributed to getting these IP 
> weather stations running in weewx, & to Matthew (and anyone who 
> contributed) for the Interceptor driver and for helping me diagnose a 
> problem - nothing to do with the WeatherSleuth or the Interceptor driver, 
> but the fact I was using an old version of the owfs driver which I use to 
> add a couple of extra temperature measurements from my greenhouse.
>
> After getting this unit set-up in Weewx I thought I would post a run 
> through of what I did.
>
> *The WeatherSleuth weather station*
>
> The outdoor array has the usual sensors (wind direction, wind speed, rain, 
> temperature, humidity) + UV & Solar Radiation.
> Meanwhile the indoor sensor has temperature, pressure & humidity (although 
> I don't think indoor humidity is recorded by weewx as a default)
>
> The receiver base station is a small box which has an aerial for receiving 
> the data from the outdoor & indoor sensors, an RJ-45 ethernet port & a 
> power socket for the supplied 5vDC supply.
> It does not feature WiFi, it must be physically plugged into using an 
> ethernet cable, which is also supplied.
>
> There are a variety of status lights on the receiver, which incidentally 
> is tiny - fits in the palm of your hand - and since it doesn't display any 
> weather info (there is no console display) it makes it ideal if you just 
> want to feed data into weewx and not bother with USB cables from desktop 
> weather stations etc.
>
> The default set-up out of the box is feeding to Weather Underground, but 
> this is one of the IP-based systems where the data feed destination can be 
> easily changed.
>
> Mine was shipped with Firmware 2.1.9, which is the latest.
>
> Out of the box it comes set for DHCP, so you will have to dive into your 
> router or use some network scanning software to find it.
> Alternatively there is a Windows utility supplied on the (tiny**) CD 
> (** don't slot that in your laptop or any other slot-loading drive, you'll 
> wreck the drive)
> Since I'm a Mac & Linux user I didn't use the windows utility but instead 
> logged into my router and found the device - fairly easy since the 
> MAC/hardware address is printed on a label stuck on the bottom of the 
> receiver.
>
> In my case I set a Static DHCP lease in the router, but alternatively you 
> may want to just set a static IP address within the weather station itself 
> or just leave it DHCP, see Local Network config below.
> Once you have the IP, open up a web browser and head to the weather 
> station's IP address config page:
>
> http://*ip.address.of.the.weathersleuth.*
>
> There you'll see the config tabs, first one speaks for itself -*Local 
> Network* -  DHCP or manual IP, plus fields for the router IP, DNS, Subnet 
> etc. If you're happy to find it on DHCP if & when you need to change 
> anything I don't see any reason not to leave it set to DHCP, as it pushes 
> data to weewx and not the other way around.
>
> Next tab is for the *Weather Network*, which is where we will set it up 
> to feed to your weewx system.
> From the *Remote Server *pull-down menu, choose *Customized*
>
> In the *Server/Hostname *box, type in the IP address of the computer 
> you're running Weeex on. In my case, its 192.168.45.100
> I don't know, and haven't tried, whether you could supply a local named 
> address such as "weewx.local" if your computer is called that. The only 
> reason you might want to do this is if the computer running weewx is using 
> DHCP - I run weewx on a ubuntu server which also does other stuff, so its 
> on a static address on my network.
>
> In the *Server Port *box, specify a unique port that Weewx or other 
> software on the computer isn't using. Try not to use standard ports even if 
> you're not using them right now - you may in the future.
> I chose 55, which might be a mistake further down the line, but it can 
> always be changed - with the relevant change in weewx.conf to match.
>
> In the *Server Type* pull-down menu, choose *PHP *- note that the other 
> options, JSP & ASP, didn't seem to provide accurate data in my case.

[weewx-user] Re: ultimeter setup troubles

[Eelco F]

Ok, I did a rewiring of a new DB9 plug, according to the scheme on the site 
of peetbros. Now it works! So it was a wrong pinout on the DB9 plug.
A bit strange, since it came straight from the importer of peetbros 
equipment in our country. Maybe just a monday morning example ;)
Thanks for everybodys comments on this.

E

>
> So to put it all together, The time stamps are coming from the script 
> itself I assume, as they show up when the station isn't even connected. 
> When disconnecting the display from my computer, some buffer seems to be 
> dumped or something.
> There may some wiring problem? should I follow the DB9 to computer scheme? 
> (sounds logical).
>
>
> Op zaterdag 14 januari 2017 15:54:36 UTC+1 schreef mwall:
>>
>> just for fun, try ultimeter-0.17rc1.py
>>
>> it has write timeouts, so if the driver is unable to write (but able to 
>> read) this should be reflected in the log
>>
>>
>>

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