Re: [weewx-user] Re: No data from station

[Alberto Sánchez]

pi@raspberrypi:~ $ dpkg -l | grep usb
ii  libusb-0.1-4:armhf2:0.1.12-25   
armhfuserspace USB programming library
ii  libusb-1.0-0:armhf2:1.0.19-1
armhfuserspace USB programming library
ii  libusbmuxd2:armhf 1.0.9-1   
armhfUSB multiplexor daemon for iPhone and iPod Touch devices - 
library
ii  python-usb0.4.3-1   
armhfUSB interface for Python
ii  usb-modeswitch2.2.0+repack0-2   
armhfmode switching tool for controlling "flip flop" USB devices
ii  usb-modeswitch-data   20150115-1
all  mode switching data for usb-modeswitch
ii  usbutils  1:007-2   
armhfLinux USB utilities

-- 
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: No data from station

[Alberto Sánchez]

Hi Mwall,

Here my error, with Rasbian Jessy:


$ sudo /etc/init.d/weewx status -l
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx)
   Active: active (running) since vie 2016-11-04 07:32:31 CET; 37s ago
  Process: 19854 ExecStop=/etc/init.d/weewx stop (code=exited, status=0/SUCCESS)
  Process: 19975 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)
   CGroup: /system.slice/weewx.service
   └─19990 python /usr/bin/weewxd --daemon --pidfile=/var/run/weewx.pid 
/etc/weewx/weewx.conf

nov 04 07:32:31 raspberrypi weewx[19990]: restx: Wunderground-PWS: Data for 
station IULTZAMA2 will be posted
nov 04 07:32:31 raspberrypi weewx[19990]: restx: PWSweather: Posting not 
enabled.
nov 04 07:32:31 raspberrypi weewx[19990]: restx: CWOP: Posting not enabled.
nov 04 07:32:31 raspberrypi weewx[19990]: restx: WOW: Posting not enabled.
nov 04 07:32:31 raspberrypi weewx[19990]: restx: AWEKAS: Posting not enabled.
nov 04 07:32:31 raspberrypi weewx[19990]: engine: Starting up weewx version 
3.6.1
nov 04 07:32:31 raspberrypi weewx[19990]: wmr300: reading records since 
2016-11-04 07:30:00 CET (1478241000)
nov 04 07:32:32 raspberrypi weewx[19990]: wmr300: usb failure: could not detach 
kernel driver from interface 0: No hay datos disponibles
nov 04 07:32:32 raspberrypi weewx[19990]: engine: Caught WeeWxIOError: could 
not detach kernel driver from interface 0: No hay datos disponibles
nov 04 07:32:32 raspberrypi weewx[19990]:   Waiting 60 seconds then 
retrying...

-- 
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] Noob question... where to find the actual data (temp) within weewx?

[Andrew Milner]

 I shake my head in despair that a simple suggestion gave rise to such 
a long thread 


On Friday, 4 November 2016 03:09:39 UTC+2, Jim W. wrote:

> THANK YOU THANK YOU THANK YOU!!! 
> and thanks for your patience!
>
> On Thursday, November 3, 2016 at 8:21:29 PM UTC-4, Tom Keffer wrote:
>>
>> The weewx report generator processes temp.txt.tmpl to produce a file 
>> temp.txt, which will contain the current temperature as a string.
>>
>> It has nothing to do with the shell.
>>
>> Take a look in /var/www/html/weewx/temp.txt
>>
>> -tk
>>
>>
>> On Thu, Nov 3, 2016 at 4:35 PM, Jim W.  wrote:
>>
>>> As I understand it, $current.outTemp represents a string variable the 
>>> value of which should be the outside temperature.  When I try to view the 
>>> value (echo $current.outTemp )  I dose't work. I've tried a few other 
>>> schemes as well, like making a shell script that does this: 
>>> #!/bin/bash
>>> current_outTemp=$current.outTemp
>>> echo $current_outTemp
>>>
>>>
>>> Can you give me an idea of how to accomplish this?
>>>
>>>
>>>
>>>
>>> On Thursday, November 3, 2016 at 5:45:26 PM UTC-4, Tom Keffer wrote:

 On Thu, Nov 3, 2016 at 2:35 PM, Jim W.  wrote:

>
> Does the temp.txt.tmpl file require special formatting? Right now this 
> is what it contains: 
> $current.outTemp
>
>
 ​It should contain just text. Why do you ask?

 -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+...@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] Noob question... where to find the actual data (temp) within weewx?

[Jim W.]

THANK YOU THANK YOU THANK YOU!!! 
and thanks for your patience!

On Thursday, November 3, 2016 at 8:21:29 PM UTC-4, Tom Keffer wrote:
>
> The weewx report generator processes temp.txt.tmpl to produce a file 
> temp.txt, which will contain the current temperature as a string.
>
> It has nothing to do with the shell.
>
> Take a look in /var/www/html/weewx/temp.txt
>
> -tk
>
>
> On Thu, Nov 3, 2016 at 4:35 PM, Jim W. > 
> wrote:
>
>> As I understand it, $current.outTemp represents a string variable the 
>> value of which should be the outside temperature.  When I try to view the 
>> value (echo $current.outTemp )  I dose't work. I've tried a few other 
>> schemes as well, like making a shell script that does this: 
>> #!/bin/bash
>> current_outTemp=$current.outTemp
>> echo $current_outTemp
>>
>>
>> Can you give me an idea of how to accomplish this?
>>
>>
>>
>>
>> On Thursday, November 3, 2016 at 5:45:26 PM UTC-4, Tom Keffer wrote:
>>>
>>> On Thu, Nov 3, 2016 at 2:35 PM, Jim W.  wrote:
>>>

 Does the temp.txt.tmpl file require special formatting? Right now this 
 is what it contains: 
 $current.outTemp


>>> ​It should contain just text. Why do you ask?
>>>
>>> -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+...@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] Noob question... where to find the actual data (temp) within weewx?

[Thomas Keffer]

The weewx report generator processes temp.txt.tmpl to produce a file
temp.txt, which will contain the current temperature as a string.

It has nothing to do with the shell.

Take a look in /var/www/html/weewx/temp.txt

-tk


On Thu, Nov 3, 2016 at 4:35 PM, Jim W.  wrote:

> As I understand it, $current.outTemp represents a string variable the
> value of which should be the outside temperature.  When I try to view the
> value (echo $current.outTemp )  I dose't work. I've tried a few other
> schemes as well, like making a shell script that does this:
> #!/bin/bash
> current_outTemp=$current.outTemp
> echo $current_outTemp
>
>
> Can you give me an idea of how to accomplish this?
>
>
>
>
> On Thursday, November 3, 2016 at 5:45:26 PM UTC-4, Tom Keffer wrote:
>>
>> On Thu, Nov 3, 2016 at 2:35 PM, Jim W.  wrote:
>>
>>>
>>> Does the temp.txt.tmpl file require special formatting? Right now this
>>> is what it contains:
>>> $current.outTemp
>>>
>>>
>> ​It should contain just text. Why do you ask?
>>
>> -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.
>

-- 
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] Pi Stops Reporting to Wunderground

[mwall]

On Thursday, November 3, 2016 at 5:41:30 AM UTC-4, Andy Harrold wrote:
>
> Ive now purchase a new USB Hub with a 2A power supply. Unfortunately it 
> hasn't fixed the problem. 
>

andy,

please update to weewx 3.6.1, or replace your te923.py driver with the 
te923.py driver from weewx 3.6.1

there were significant changes to the te923 driver between weewx 3.5.0 and 
weewx 3.6

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: WH3080 - read stored data

[mwall]

On Thursday, November 3, 2016 at 7:45:27 PM UTC-4, Günther Zinsberger wrote:

I have to power cycle my weather station (restarting weewx is not enough). 
> After some time (next weewx read) I get all the data stored from the 
> console,
>

does your station retain the history even after you power cycle it?

that is different from the 10xx/20xx stations - those stations lose their 
history when power cycled.
 

-- 
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: WH3080 - read stored data

[mwall]

On Thursday, November 3, 2016 at 7:45:27 PM UTC-4, Günther Zinsberger wrote:
>
> Sometimes (meanwhile about once a week) I have stability problems (similar 
> to the problem described at here 
> ). I have 
> to power cycle my weather station (restarting weewx is not enough). After 
> some time (next weewx read) I get all the data stored from the console, but 
> they are not correct (reverse order? time shift? ...?)
>

be sure that weewx knows you have a 30xx, not a 10xx/20xx

[FineOffsetUSB]
...
data_format = 3080

the record size for the 30xx is different than that of the 10xx/20xx 
stations.

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] WH3080 - read stored data

[Günther Zinsberger]

Hi!

Sometimes (meanwhile about once a week) I have stability problems (similar 
to the problem described at here 
). I have 
to power cycle my weather station (restarting weewx is not enough). After 
some time (next weewx read) I get all the data stored from the console, but 
they are not correct (reverse order? time shift? ...?)

My environment:
* Raspberry Pi 1 B
* Raspbian 7 (wheezy)
* Weewx 3.6.1 (since 2 weeks, before 3.3.1 with the same problem)
* Weather station WH3080; lsusb: Bus 001 Device 008: ID 1941:8021 Dream 
Link WH1080 Weather Station / USB Missile Launcher
   * new batteries inside
   * power cycle looks like this: disconnect USB, remove batteries, insert 
batteries, set date and time manually, connect USB again, perhaps start 
weewx after it has died at that time

When all data is read after the weewx restart then the graph looks like 
this (see attachment). What is wrong?

Thank you!

-- 
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] Noob question... where to find the actual data (temp) within weewx?

[Jim W.]

As I understand it, $current.outTemp represents a string variable the value 
of which should be the outside temperature.  When I try to view the value 
(echo $current.outTemp )  I dose't work. I've tried a few other schemes as 
well, like making a shell script that does this: 
#!/bin/bash
current_outTemp=$current.outTemp
echo $current_outTemp


Can you give me an idea of how to accomplish this?




On Thursday, November 3, 2016 at 5:45:26 PM UTC-4, Tom Keffer wrote:
>
> On Thu, Nov 3, 2016 at 2:35 PM, Jim W. > 
> wrote:
>
>>
>> Does the temp.txt.tmpl file require special formatting? Right now this is 
>> what it contains: 
>> $current.outTemp
>>
>>
> ​It should contain just text. Why do you ask?
>
> -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] Pi Stops Reporting to Wunderground

[gjr80]

I will preface this up front that I am not a TE923 user but I think the use 
of hardware record generation may be contributing to the problem... reading 
the TE923  section in the 
Hardware 
Guide  I see that it says 

The TE923 driver will read history records from the station when weewx 
> starts up, but it does not support hardware record generation.


But in the weewx.conf you posted you have told weewx to use hardware record 
generation:

[StdArchive]
> 
> # If the station hardware supports data logging then the archive 
> interval
> # will be downloaded from the station. Otherwise, specify it (in 
> seconds).
> archive_interval = 300
> 
> # How long to wait (in seconds) before processing new archive data. 
> Must
> # be greater than zero.
> archive_delay = 15
> 
> # If possible, new archive records are downloaded from the station
> # hardware. If the hardware does not support this, then new archive
> # records will be generated in software.
> # Set the following to "software" to force software record generation.
> record_generation = hardware
> 
> # Whether to include LOOP data in hi/low statistics
> loop_hilo = True
> 
> # The data binding used to save archive records
> data_binding = wx_binding
>

I am not sure of the exact impact this would have on weewx. But I suspect 
it would have some difficulty in producing an archive record and the 
archive record is what is stored in your archive and the WU updater will be 
looking at the archive record for updating WU. I could certainly see this 
causing problems for updating WU. If you have a look at a log extract you 
posted early on there are long periods of time when no actual archive 
record is produced and saved to the database.

My suggestion is to:

   1. stop weewx
   2. set record_generation = software in weewx.conf [StdArchive]
   3. set debug = 1 in weewx.conf
   4. clear the TE923 memory using wee_device (refer to the TE923 
    section in the Hardware 
   Guide )
   5. start weewx
   6. monitor the logs/WU and see how that goes. If posts to WU fail again, 
   post the log from weewx startup until the failure.

To make reading the logs a bit easier you might want to consider setting 
your system to use a separate log file for weewx. The steps are quite 
simple and are described in the weewx wiki here 
 (if you do implement this 
make sure you setup the logrotate part as well).


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] Pi Stops Reporting to Wunderground

[gjr80]

weewx.conf will do for now. Just for the record its included in your 
/usr/share/weewx or /home/weewx/bin directory (depending on your install 
type) since weewx 3.3.0/3.4.0 and it's use is detailed here 
 in the Utilities 
Guide .

Gary

On Friday, 4 November 2016 08:13:35 UTC+10, Andy Harrold wrote:
>
> Where do I find the wee_debug report?
>
> On Thursday, 3 November 2016 10:50:21 UTC, gjr80 wrote:
>>
>> It's also hard to see exactly what your (weewx) config is. When posting 
>> the log Andrew asked for could you please post asanitised weewx.conf or a 
>> wee_debug report.
>>
>> 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] Pi Stops Reporting to Wunderground

[Andy Harrold]

# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2015 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 1

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 3.5.0

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = "Auchindoun, Dufftown"

# Latitude and longitude in decimal degrees
latitude = 57.436
longitude = 3.084

# Altitude of the station, with unit it is in. This is downloaded from
# from the station if the hardware supports it.
altitude = 277, meter

# Set to type of station hardware. There must be a corresponding stanza
# in this file with a 'driver' parameter indicating the driver to be 
used.
station_type = TE923

# If you have a website, you may specify an URL
#station_url = http://www.example.com

# The start of the rain year (1=January; 10=October, etc.). This is
# downloaded from the station if the hardware supports it.
rain_year_start = 1

# Start of week (0=Monday, 6=Sunday)
week_start = 6

##

[Simulator]
# This section is for the weewx weather station simulator

# The time (in seconds) between LOOP packets.
loop_interval = 2.5

# The simulator mode can be either 'simulator' or 'generator'.
# Real-time simulator. Sleep between each LOOP packet.
mode = simulator
# Generator.  Emit LOOP packets as fast as possible (useful for 
testing).
#mode = generator

# The start time. If not specified, the default is to use the present 
time.
#start = 2011-01-01 00:00

# The driver to use:
driver = weewx.drivers.simulator

##

[TE923]
# This section is for the Hideki TE923 series of weather stations.

# The station model, e.g., 'Meade TE923W' or 'TFA Nexus'
model = TE923

# The driver to use:
driver = weewx.drivers.te923

# The default configuration associates the channel 1 sensor with outTemp
# and outHumidity.  To change this, or to associate other channels with
# specific columns in the database schema, use the following map.
[[map]]
bat_1 = outBatteryStatus
bat_3 = extraBatteryStatus2
bat_2 = extraBatteryStatus1
bat_5 = extraBatteryStatus4
bat_4 = extraBatteryStatus3
bat_wind = windBatteryStatus
t_in = inTemp
link_rain = rainLinkStatus
t_1 = extraTemp4
h_in = inHumidity
h_3 = extraHumid3
h_1 = extraHumid4
h_5 = extraHumid1
h_2 = extraHumid3
h_4 = outHumidity
t_5 = extraTemp1
link_2 = extraLinkStatus1
link_uv = uvLinkStatus
link_wind = windLinkStatus
uv = UV
bat_uv = uvBatteryStatus
link_5 = extraLinkStatus4
bat_rain = rainBatteryStatus
link_3 = extraLinkStatus2
t_2 = extraTemp2
link_1 = outLinkStatus
t_4 = outTemp
t_3 = extraTemp3
link_4 = extraLinkStatus3

##

#   This section is for uploading data to Internet sites

[StdRESTful]

[[StationRegistry]]
# To register this weather station with weewx, set this to true
register_this_station = false

[[AWEKAS]]
# This section is for configuring posts to AWEKAS.

# If you wish to do this, set the option 'enable' to true,
# and specify a username and password.
enable = false
username = replace_me
password = replace_me

[[CWOP]]
# This section is for configuring posts to CWOP.

# If you wish to do this, set the option 'enable' to true,
# and specify the station ID (e.g., CW1234).
enable = false
station = replace_me

# If this is an APRS (radio amateur) station, uncomment
# the following and replace with a passcode (e.g., 12345).
#passcode = replace_me (APRS stations only)

[[PWSweather]]
# This section is for configuring posts to PWSweather.com.

# If you wish to do this, set the option 'enable' to true,
# and specify a station and password.
enable = false
station = replace_me
password = replace_me

[[WOW]]
 

Re: [weewx-user] start problems

[Glenn McKechnie]

On 4 November 2016 at 01:42, J.L. Blom  wrote:

>
> Glenn,
> Tanks for your reply.
> The most remarkable thing happened. I was running weewxd and did a
> /etc/init.d/weewx status and it showed a lot of old starts but not the
> running weewxd.
> Next I killed weewxd and the started the stansard way:
> 
> joep@kangoo:~ $ sudo kill -9 2303
>

That's likely to be your problem there.
kill -9 is a good way of getting weewx to stop instantly - it's the same as
a head shot. Trouble with that is there is no chance for weewx to pack its
bags, tidy the room and generally exit gracefully, which means there's a
mess left behind to clean up. PID files, uncompleted processess.

kill -15 is a little cleaner, it allows weewx to pack its bags, clean up
and exit stage left. But it still doesn't play well (or vice versa) with
init.d scripts

They do their jobs well. But if you do use them, then expect some
unpredictable results (keyword being unpredictable) - one of them being
that /etc/init.d/weewx start won't necessarily start up again. weewx start
will say it has indeed started but as you've found it's just a hollow
message.

If you use the kill command. The fix is to run* /etc/init.d.weewx stop*
before you do the */etc/init.d/weews start  *(or simply run */etc/init.d/weewx
restart*) That at least cleans up the stale PID file, something else might
be left confused but weewx will more than likely clean that up.

The same logic applies for systemd (service / systemctl)



> [...]




>
> Another annoying problem is that the gauge generator generates 104 lines
> with
> "GaugeGenerator: Cannot decode reading of 'None' for gauge 'windDir'" but
> then it gave a reading followed by another run of the error message.
> I think it is a bug somewhere but it inflates the log file to no use.
> Do you know how to get rid of this?
>


No. I don't have the fix but I agree that it was annoying. I think it was
when I was road testing the Bootstrap skin.




Cheers
 Glenn

rorpi - read only raspberry pi + weewx: now with scripts


-- 
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] Pi Stops Reporting to Wunderground

[Andy Harrold]

Where do I find the wee_debug report?

On Thursday, 3 November 2016 10:50:21 UTC, gjr80 wrote:
>
> It's also hard to see exactly what your (weewx) config is. When posting 
> the log Andrew asked for could you please post asanitised weewx.conf or a 
> wee_debug report.
>
> 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] Pi Stops Reporting to Wunderground

[Andy Harrold]

Powering the Hub.


On Thursday, 3 November 2016 09:50:00 UTC, Andrew Milner wrote:
>
> Is the 2A supply powering the hub or the pi?
>
> since it is some time since your original post - can you post a section of 
> log which highlights the problem now.
>
> I had a problem with debian wheezy and an rpi2 B which after running \ok 
> for a few years suddenly started to just stop and no errors in logs or 
> anything - it just ceased processing altogether and the first I knew was an 
> email from wunderground!!  Have replaced it with an rpi3 and debian Jessie 
> and so far, touch wood, all is ok again.  I have not yet started really 
> investigating what actually was going wrong - I had several theories which 
> were disproved one by one until swapping the pi seemed the only option.  I 
> don't know if it was debian, weewx, my hdd or what - but I think it was not 
> weewx (since Jessie seems to be running fine)
>
>
>
>
>
> On Thursday, 3 November 2016 11:41:30 UTC+2, Andy Harrold wrote:
>
>> Ive now purchase a new USB Hub with a 2A power supply. Unfortunately it 
>> hasn't fixed the problem. 
>>
>> On Sunday, 2 October 2016 01:41:04 UTC+1, Andrew Milner wrote:
>>>
>>> Try a 1.5A or 2A supply and see if it helps.
>>>
>>>
>>>
>>> On Saturday, 1 October 2016 23:06:05 UTC+3, Andy Harrold wrote:
>>>
 Hi.

 1. Using a powered USB Hub
 2. 5v 1.0amp

 On Saturday, 1 October 2016 12:45:38 UTC+1, Andrew Milner wrote:
>
> 1. Are you using a powered usb hub (recommended) or the usb ports on 
> the RPi itself?
> 2. What size power supply are you using?
>
> RPis can be quite critical and finicky concerning both.
>
> Your problem would appear to be a basic usb issue though, and the 
> wunderground loss etc are mere by-products of a device communication 
> failure.
>
>
>
>
>
> On Saturday, 1 October 2016 14:40:00 UTC+3, Andy Harrold wrote:
>
>> Hi,
>> Managed to find a log of a failure.
>>
>> Sep 28 19:07:05 raspberrypi weewx[2083]: te923: read: address 0x020001
>> Sep 28 19:07:05 raspberrypi weewx[2083]: te923: read: 5a 81 a1 70 aa 
>> 0a aa aa 0a aa aa 0a aa 52 c1 08 aa 0a aa ff ff 9d 3d 03 ee ee ee ee ee 
>> ee 
>> 07 ee 00 db
>> Sep 28 19:07:05 raspberrypi weewx[2083]: te923: read: address 0x4c
>> Sep 28 19:07:05 raspberrypi weewx[2083]: te923: read: 5a 7f ff ff ff 
>> ff ff ff ff ff ff ff ff ff 10 c6 00 07 33 ff ff 39 28 18 22 98 3d 98 3d 
>> c0 
>> 3d d5 3d f9
>> Sep 28 19:07:15 raspberrypi weewx[2083]: te923: read: address 0x020001
>> Sep 28 19:07:16 raspberrypi weewx[2083]: te923: read: 5a 81 a1 70 aa 
>> 0a aa aa 0a aa aa 0a aa 52 c1 08 aa 0a aa ff ff 9d 3d 03 ee ee ee ee ee 
>> ee 
>> 07 ee 00 db
>> Sep 28 19:07:16 raspberrypi weewx[2083]: te923: read: address 0x4c
>> Sep 28 19:07:16 raspberrypi weewx[2083]: te923: read: 5a 7f ff ff ff 
>> ff ff ff ff ff ff ff ff ff 10 c6 00 07 33 ff ff 39 28 18 22 98 3d 98 3d 
>> c0 
>> 3d d5 3d f9
>> Sep 28 19:07:26 raspberrypi weewx[2083]: te923: read: address 0x020001
>> Sep 28 19:07:26 raspberrypi weewx[2083]: te923: read: 5a 81 a1 70 aa 
>> 0a aa aa 0a aa aa 0a aa 52 c1 08 aa 0a aa ff ff 9d 3d 03 ee ee ee ee ee 
>> ee 
>> 07 ee 00 db
>> Sep 28 19:07:26 raspberrypi weewx[2083]: te923: read: address 0x4c
>> Sep 28 19:07:26 raspberrypi weewx[2083]: te923: read: 5a 7f ff ff ff 
>> ff ff ff ff ff ff ff ff ff 10 c6 00 07 33 ff ff 39 28 18 22 98 3d 98 3d 
>> c0 
>> 3d d5 3d f9
>> Sep 28 19:07:33 raspberrypi kernel: [87218.944317] usb 1-1.2.1.2: USB 
>> disconnect, device number 8
>> Sep 28 19:07:33 raspberrypi rsyslogd-2007: action 'action 17' 
>> suspended, next retry is Wed Sep 28 19:09:03 2016 [try 
>> http://www.rsyslog.com/e/2007 ]
>> Sep 28 19:07:33 raspberrypi kernel: [87219.193350] usb 1-1.2.1.2: new 
>> low-speed USB device number 9 using dwc_otg
>> Sep 28 19:07:33 raspberrypi kernel: [87219.299415] usb 1-1.2.1.2: New 
>> USB device found, idVendor=1130, idProduct=6801
>> Sep 28 19:07:33 raspberrypi kernel: [87219.299456] usb 1-1.2.1.2: New 
>> USB device strings: Mfr=0, Product=1, SerialNumber=0
>> Sep 28 19:07:33 raspberrypi kernel: [87219.299479] usb 1-1.2.1.2: 
>> Product:  
>> Sep 28 19:07:33 raspberrypi kernel: [87219.318477] hid-generic 
>> 0003:1130:6801.0002: hiddev0,hidraw0: USB HID v1.10 Device [ ] on 
>> usb-2098.usb-1.2.1.2/input0
>> Sep 28 19:07:33 raspberrypi mtp-probe: checking bus 1, device 9: 
>> "/sys/devices/platform/soc/2098.usb/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1.2"
>> Sep 28 19:07:33 raspberrypi mtp-probe: bus: 1, device: 9 was not an 
>> MTP device
>> Sep 28 19:07:36 raspberrypi weewx[2083]: te923: read: address 0x020001
>> Sep 28 19:07:36 raspberrypi weewx[2083]: te923: Failed attempt 1 of 5 
>> to read data: error sending con

[weewx-user] Re: Interceptor using bridge new Accurate firmware

[Radar]

the perl script was made to work with tcpdump it won't work with the new 
tcpflow that puts out every thing on one line

On Wednesday, November 2, 2016 at 7:21:17 PM UTC-5, Brad Tucker wrote:
>
> Only thing I noticed is you are running it off the bridge device. I can't 
> get any data off my bridge device. only eth0. I also see a stream similar 
> to yours when its communicating with weatherunderground. Is it possible you 
> didn't let it run long enough? Im assuming you let it run for a min or two 
> and had the same results? 
>
> Past that I have no more ideas :( sorry...
> B
>
> On Wednesday, November 2, 2016 at 5:06:51 PM UTC-7, Pat Hayes wrote:
>>
>> Looks like yours minus the good stuff.
>>
>> [root@weewx ~]# tcpdump -A -n -p -l -i bridge0 -s0 -W tcp dst port 80 | 
>> stdbuf -oL strings -n8 | stdbuf -oL grep "&"
>> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
>> listening on bridge0, link-type EN10MB (Ethernet), capture size 65535 
>> bytes
>> E..4l.@.1..+b..7...*...P.&9.R...
>> E..(l.@.1..6b..7...*...P.&...v.PP...3.
>> E...l.@.1...b..7...*...P.&...v.PP...{4..GET / HTTP/1.0
>> E..4l.@.1..(b..7...*...P.&...v.P.{.
>> E..4l.@.1..'b..7...*...P.&...v"8...
>> E..4l.@.1..&b..7...*...P.&...v'
>> E..4l.@.1..%b..7...*...P.&...v.l..-..C.
>> E..4l.@.1..$b..7...*...P.&...v.l..-..?.
>> E..(..@.1.Y.b..7...*...P.&..P.
>> E..(..@.1.Y.b..7...*...P.&..P.
>> E..(..@.1.Y.b..7...*...P.&..P.
>> E..(..@.1.Y.b..7...*...P.&..P.
>> E..(..@.1.Y.b..7...*...P.&..P.
>> E.@.5.&.F,4*...PX~4..;...*.
>> E&@.5...F,4*...P..-..X.R.$.
>> E..4.&@.5.+.F,4*...PX~6M.<.w...
>> f.6.&,.[.
>> f.6.&,...
>> f.6.&-.5.
>> ^C62 packets captured
>> 62 packets received by filter
>> 0 packets dropped by kernel
>>
>>
>>
>>
>> On Wednesday, November 2, 2016 at 7:38:41 PM UTC-4, Brad Tucker wrote:
>>>
>>> what does you output look like on tcpdump w/o the perl script? mine 
>>> always looked strange but it worked... Also don't do it off the bridge but 
>>> use eth0 or your main ethernet to the router.
>>> sudo tcpdump -A -n -p -l -i eth0 -s0 -W tcp dst port 80 | stdbuf -oL 
>>> strings -n8 | stdbuf -oL grep "&"
>>>
>>> output always looks strange but it works well with the perl script:
>>> pi@weather:~ $ sudo tcpdump -A -n -p -l -i eth0 -s0 -W tcp dst port 80 | 
>>> stdbuf -oL strings -n8 | stdbuf -oL grep "&"
>>> tcpdump: verbose output suppressed, use -v or -vv for full protocol 
>>> decode
>>> listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
>>> E..xfd..d.=.4}.P.. B...cP...D...GET 
>>> /weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1
>>> E..Qfe..d.=.4}.P.. 
>>> cPg..&id=24C86E06B15C&mt=tower&sensor=00012694
>>> 4}.P.. cP...OD..&humidity=53&tempf=73.0
>>> E..Lfg..d.=.4}.P.. 
>>> cP|..&baromin=29.31&battery=normal&rssi=3
>>> E..xfs..d...4~.P..0jP...GET 
>>> /weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1
>>>
>>> E..Qft..d...4~.P..0jP...UH..&id=24C86E06B15C&mt=tower&sensor=8384
>>> E..?fu..d...4~.P..1jP$..&humidity=37&tempf=82.3
>>>
>>> E..Lfv..d...4~.P..1/...jP..._c..&baromin=29.31&battery=normal&rssi=2
>>> E..xf...d.^.46._...P/...P...3...GET 
>>> /weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1
>>>
>>> E..Rf...d.^.46._...P/..LP5..&id=24C86E06B15C&mt=5N1x38&sensor=2179
>>> E..Cf...d.^.46._...P/..vP6..&windspeedmph=3&humidity=15
>>> E..3f...d.^.46._...P/...P...Rg..&tempf=78.4
>>>
>>> E..Lf...d.^.46._...P/...P...&baromin=29.31&battery=normal&rssi=3
>>>
>>> GLUCK!
>>> B
>>>
>>>
>>> On Wednesday, November 2, 2016 at 4:30:08 PM UTC-7, Pat Hayes wrote:

 With just the tcpflow command, it shows this.

 [root@weewx ~]# tcpflow -C -0 -s tcp dst port 80
 tcpflow: listening on bridge0
 GET 
 /weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1&id=24C86E08150D&mt=5N1x38&sensor=2701&windspeedmph=0&humidity=86&tempf=58.8&baromin=30.34&battery=normal&rssi=3
  
 HTTP/1.1
 Host: hubapi.myacurite.com
 User-Agent: Hub/224
 Connection: close

 GET 
 /weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1&id=24C86E08150D&mt=5N1x31&sensor=2701&windspeedmph=0&winddir=158&rainin=0.00&dailyrainin=0.00&humidity=86&tempf=58.8&dewptf=54&baromin=30.34&battery=normal&rssi=3
  
 HTTP/1.1
 Host: hubapi.myacurite.com
 User-Agent: Hub/224
 Connection: close

 GET 
 /weatherstation/updateweatherstation.php?ID=KNJNEWJE4&PASSWORD=pat6854&dateutc=now&action=updateraw&realtime=1&rtfreq=36&id=24C86E08150D&mt=5N1x31&sensor=2701&windspeedmph=0&wi

Re: [weewx-user] Noob question... where to find the actual data (temp) within weewx?

[Thomas Keffer]

On Thu, Nov 3, 2016 at 2:35 PM, Jim W.  wrote:

>
> Does the temp.txt.tmpl file require special formatting? Right now this is
> what it contains:
> $current.outTemp
>
>
​It should contain just text. Why do you ask?

-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] Noob question... where to find the actual data (temp) within weewx?

[Jim W.]

This is what I have added to skin.config


  [[ToDate]]
# Reports that show statistics "to date", such as day-to-date,
# week-to-date, month-to-date, etc.
[[[day]]]
template = index.html.tmpl


[[[temp.txt]]]
# Report that makes current outTemp availibal to other program
encoding = strict_ascii
template = temp.txt.tmpl


[[[week]]]
template = week.html.tmpl

[[[month]]]
template = month.html.tmpl

[[[year]]]
template = year.html.tmpl


Does the temp.txt.tmpl file require special formatting? Right now this is 
what it contains: 
$current.outTemp

THANKS!!!



On Wednesday, November 2, 2016 at 8:07:49 PM UTC-4, Tom Keffer wrote:
>
> Close.
>
> For a simple report like this, you want "ToDate" generation (as opposed to 
> summaries by month or year, like the NOAA reports). So, you need to tuck 
> your addition under [[ToDate]] and add one more set of brackets. It will 
> look like:
>
> [[ToDate]]
>
> ... (other templates)
>
> [[[temp.txt]]]
> # Report that makes current outTemp available to other program
> encoding = strict_ascii
> template = temp.txt.tmpl
>
> -tk  
>
> On Wed, Nov 2, 2016 at 4:04 PM, Jim W. > 
> wrote:
>
>> Tom and Andrew,
>> I have created a new template called temp.txt.tmpl in the 
>> etc/weewx/skins/Standard directory. It's only content is: $current.outTemp
>>
>> In the skin.conf file under [CheetahGenerator] I added:
>>
>>[[temp.txt]]
>> # Report that makes current outTemp available to other program
>> encoding = strict_ascii
>> template = temp.txt.tmpl
>>
>> Am I on the right track? Thanks for your patience!
>>
>>
>>
>>
>>
>> On Monday, October 31, 2016 at 9:23:13 AM UTC-4, Jim W. wrote:
>>>
>>> THANKS ALL... now i'm heading in the right direction!!!
>>>
>>>  
>>>
>>> On Sunday, October 30, 2016 at 9:31:54 PM UTC-4, Tom Keffer wrote:

 Jim,

 Did you check the Customizing Guide 
 ? It has an abundance of 
 information about how to access the data. As Andrew suggests, the easiest 
 is to specify that the report generator create another (tiny) file, with 
 just a single tag $current.outTemp. On every reporting cycle the tag will 
 be replaced with the current temperature.

 -tk

 On Sat, Oct 29, 2016 at 1:50 PM, Jim W.  wrote:

> I have very little Linux (or other programming) experience...  Decades 
> ago I did a little Visual Basic programming but that is a dim memory. I 
> have managed (with the generous help of this forum) to setup and run 
> weewx 
> on a Rpi3b. WS2080 WU and Motion sending images to WU.
>
> My next project is to add overlays of temperature and wind speed and 
> direction to the images I'm sending to WU. Most of it I have figured out 
> but what I don't know is where to find the actual data (temp) within 
> weewx?
>
> 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+...@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+...@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: No data from station

[mwall]

On Thursday, November 3, 2016 at 4:45:22 PM UTC-4, Alberto Sánchez wrote:
>
> Hi,
>
> I just test the new driver and I have the same Roland error. Thank you 
> very much.
>

alberto, could you post the errors you get with the 0.15rc1 driver?  thank 
you!
 

-- 
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: No data from station

['Roland Ehle' via weewx-user]

ii  libusb-0.1-4:amd64  
2:0.1.12-28   amd64userspace USB 
programming library
ii  libusb-1.0-0:amd64  
2:1.0.20-1amd64userspace USB 
programming library
hi  python-usb  
0.4.3-1   amd64USB interface 
for Python

I have downgraded to python-usb version 0.4.3 due to your recommendation.

System is running on Ubuntu 16.04 LTS with kernel 4.4.0-45-generic 
#66-Ubuntu

Am Donnerstag, 3. November 2016 21:37:56 UTC+1 schrieb mwall:
>
> On Thursday, November 3, 2016 at 1:07:53 PM UTC-4, Roland Ehle wrote:
>>
>> I gave it a try, but I had the following errors in the log with debug = 0
>>
>> Nov  3 18:01:42 lin01 weewx[19698]: wmr300: usb failure: could not detach 
>> kernel driver from interface 0: Keine Daten verfügbar
>> Nov  3 18:01:42 lin01 weewx[19698]: engine: Caught WeeWxIOError: could 
>> not detach kernel driver from interface 0: Keine Daten verfügbar
>> Nov  3 18:01:42 lin01 weewx[19698]:   Waiting 60 seconds then 
>> retrying..
>>>
>>>
>>>
> roland,
>
> thank you for trying this.  please post the usb info for your system, 
> specifically which libusb and pyusb.  for example, on a debian system do 
> this:
>
> dpkg -l | grep usb
>
> 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: No data from station

['Roland Ehle' via weewx-user]

Full output of dpkg -l | grep usb is attached for better reading.

Regards,
Roland

Am Donnerstag, 3. November 2016 21:37:56 UTC+1 schrieb mwall:
>
> On Thursday, November 3, 2016 at 1:07:53 PM UTC-4, Roland Ehle wrote:
>>
>> I gave it a try, but I had the following errors in the log with debug = 0
>>
>> Nov  3 18:01:42 lin01 weewx[19698]: wmr300: usb failure: could not detach 
>> kernel driver from interface 0: Keine Daten verfügbar
>> Nov  3 18:01:42 lin01 weewx[19698]: engine: Caught WeeWxIOError: could 
>> not detach kernel driver from interface 0: Keine Daten verfügbar
>> Nov  3 18:01:42 lin01 weewx[19698]:   Waiting 60 seconds then 
>> retrying..
>>>
>>>
>>>
> roland,
>
> thank you for trying this.  please post the usb info for your system, 
> specifically which libusb and pyusb.  for example, on a debian system do 
> this:
>
> dpkg -l | grep usb
>
> 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.
ii  ippusbxd1.23-1  
  amd64Daemon for IPP USB printer support
ii  libgusb2:amd64  0.2.9-0ubuntu1  
  amd64GLib wrapper around libusb1
ii  libusb-0.1-4:amd64  2:0.1.12-28 
  amd64userspace USB programming library
ii  libusb-1.0-0:amd64  2:1.0.20-1  
  amd64userspace USB programming library
ii  libusbmuxd4:amd64   1.0.10-2ubuntu0.1   
  amd64USB multiplexor daemon for iPhone and iPod Touch 
devices - library
hi  python-usb  0.4.3-1 
  amd64USB interface for Python
ii  usb-creator-common  0.3.2   
  amd64create a startup disk using a CD or disc image 
(common files)
ii  usb-creator-gtk 0.3.2   
  amd64create a startup disk using a CD or disc image (for 
GNOME)
ii  usb-modeswitch  2.2.5+repack0-1ubuntu1  
  amd64mode switching tool for controlling "flip flop" USB 
devices
ii  usb-modeswitch-data 20151101-1  
  all  mode switching data for usb-modeswitch
ii  usbmuxd 1.1.0-2 
  amd64USB multiplexor daemon for iPhone and iPod Touch 
devices
ii  usbutils1:007-4 
  amd64Linux USB utilities

Re: [weewx-user] Re: No data from station

[mwall]

On Thursday, November 3, 2016 at 1:07:53 PM UTC-4, Roland Ehle wrote:
>
> I gave it a try, but I had the following errors in the log with debug = 0
>
> Nov  3 18:01:42 lin01 weewx[19698]: wmr300: usb failure: could not detach 
> kernel driver from interface 0: Keine Daten verfügbar
> Nov  3 18:01:42 lin01 weewx[19698]: engine: Caught WeeWxIOError: could not 
> detach kernel driver from interface 0: Keine Daten verfügbar
> Nov  3 18:01:42 lin01 weewx[19698]:   Waiting 60 seconds then 
> retrying..
>>
>>
>>
roland,

thank you for trying this.  please post the usb info for your system, 
specifically which libusb and pyusb.  for example, on a debian system do 
this:

dpkg -l | grep usb

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: No data from station

[Alberto Sánchez]

Hi,

I just test the new driver and I have the same Roland error. Thank you very 
much.

-- 
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: No data from station

[mwall]

On Thursday, November 3, 2016 at 4:17:43 PM UTC-4, Alberto Sánchez wrote:
>
> Thank you very much for your answer.
>
> I have tested the new driver and report me this error:
>

alberto, the DOCTYPE indicates that the wmr300.py file was not downloaded 
properly.  you must download the raw .py file.  use this link instead:

https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/wmr300.py

 

-- 
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: No data from station

[Alberto Sánchez]

Thank you very much for your answer.

I have tested the new driver and report me this error:


 weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx)
   Active: active (exited) since jue 2016-11-03 20:59:24 CET; 3s ago
  Process: 14515 ExecStop=/etc/init.d/weewx stop (code=exited, status=0/SUCCESS)
  Process: 14652 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)

nov 03 20:59:24 raspberrypi weewx[14667]:   
self.setupStation(config_dict)
nov 03 20:59:24 raspberrypi weewx[14667]: File 
"/usr/share/weewx/weewx/engine.py", line 94, in setupStation
nov 03 20:59:24 raspberrypi weewx[14667]:   __import__(driver)
nov 03 20:59:24 raspberrypi weewx[14667]: File 
"/usr/share/weewx/weewx/drivers/wmr300.py", line 1
nov 03 20:59:24 raspberrypi weewx[14667]:   
nov 03 20:59:24 raspberrypi weewx[14667]:   ^
nov 03 20:59:24 raspberrypi weewx[14667]:   SyntaxError: invalid syntax
nov 03 20:59:24 raspberrypi weewx[14667]:   Exiting.
nov 03 20:59:24 raspberrypi systemd[1]: Started LSB: weewx weather system.
nov 03 20:59:24 raspberrypi weewx[14652]: Starting weewx weather system: 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] outTemp, windchill & heatindex all registering the same temp.

[Brad Tucker]

Thanks for the info Tom. This would explain it then as the Acurite 5n1 does 
not record its own windchill or heat index. We are over 80 today here in 
socal but only 12% humidity so I can't test it out...

Thanks Again,
Brad

On Thursday, November 3, 2016 at 12:07:53 PM UTC-7, Tom Keffer wrote:
>
> If you asked weewx to calculate windchill and heatindex 
> , they will differ 
> from outTemp only if certain criteria are met:
>
> windchill: temperature must be below 50F, and wind speed above 3mph (ref: 
> http://www.nws.noaa.gov/om/winter/windchill.shtml)
>
> heatindex: temperature must be above 80F, and relative humidity over 40% 
> (ref: http://www.wpc.ncep.noaa.gov/html/heatindex_equation.shtml)
>
> If you asked weewx to use hardware values, then weewx uses whatever value 
> is emitted from your Acurite.
>
> -tk
>
>
> On Thu, Nov 3, 2016 at 11:59 AM, Brad Tucker  > wrote:
>
>> outTemp, windchill & heatindex are all registering the same temp. on my 
>> system. Anyone have any ideas on where to look? When I look at the 
>> myAcurite web display they are al different but for some reason whew is 
>> reporting them all the same. I thought maybe the value where just drawing 
>> on top of themselves so I decided to look in the SQLite database and sure 
>> enough they are all exactly the same values all the time with no 
>> differences.
>>
>> Thanks!
>> Brad
>>
>> -- 
>> 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] outTemp, windchill & heatindex all registering the same temp.

[Thomas Keffer]

If you asked weewx to calculate windchill and heatindex
, they will differ
from outTemp only if certain criteria are met:

windchill: temperature must be below 50F, and wind speed above 3mph (ref:
http://www.nws.noaa.gov/om/winter/windchill.shtml)

heatindex: temperature must be above 80F, and relative humidity over 40%
(ref: http://www.wpc.ncep.noaa.gov/html/heatindex_equation.shtml)

If you asked weewx to use hardware values, then weewx uses whatever value
is emitted from your Acurite.

-tk


On Thu, Nov 3, 2016 at 11:59 AM, Brad Tucker  wrote:

> outTemp, windchill & heatindex are all registering the same temp. on my
> system. Anyone have any ideas on where to look? When I look at the
> myAcurite web display they are al different but for some reason whew is
> reporting them all the same. I thought maybe the value where just drawing
> on top of themselves so I decided to look in the SQLite database and sure
> enough they are all exactly the same values all the time with no
> differences.
>
> Thanks!
> Brad
>
> --
> 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] outTemp, windchill & heatindex all registering the same temp.

[Brad Tucker]

outTemp, windchill & heatindex are all registering the same temp. on my 
system. Anyone have any ideas on where to look? When I look at the 
myAcurite web display they are al different but for some reason whew is 
reporting them all the same. I thought maybe the value where just drawing 
on top of themselves so I decided to look in the SQLite database and sure 
enough they are all exactly the same values all the time with no 
differences.

Thanks!
Brad

-- 
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: No data from station

['Roland Ehle' via weewx-user]

I gave it a try, but I had the following errors in the log with debug = 0

Nov  3 18:01:42 lin01 weewx[19698]: wmr300: usb failure: could not detach 
kernel driver from interface 0: Keine Daten verfügbar
Nov  3 18:01:42 lin01 weewx[19698]: engine: Caught WeeWxIOError: could not 
detach kernel driver from interface 0: Keine Daten verfügbar
Nov  3 18:01:42 lin01 weewx[19698]:   Waiting 60 seconds then 
retrying..

Am Mittwoch, 2. November 2016 19:05:33 UTC+1 schrieb mwall:
>
> On Tuesday, November 1, 2016 at 4:49:24 PM UTC-4, Alberto Sánchez wrote:
>>
>> I have had the same problem and I have solve it with the same solution. 
>> Using 3.5.0 wmr 300 driver.
>
>
> alberto, roland, and others,
>
> please try the latest wmr300 driver (0.15rc1).  it uses the usb 
> initialization logic from 0.10, but it has the pressure/barometer and wind 
> direction fixex that came later.
>
> https://github.com/weewx/weewx/blob/master/bin/weewx/drivers/wmr300.py
>
> it turns out that the wmr300 stations do not default to spewing data to 
> the usb - the driver must invoke an interruptWrite periodically to keep the 
> data flowing.
>
> 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] start problems

[J.L. Blom]

Glenn,
Tanks for your reply.
The most remarkable thing happened. I was running weewxd and did a 
/etc/init.d/weewx status and it showed a lot of old starts but not the 
running weewxd.

Next I killed weewxd and the started the stansard way:

joep@kangoo:~ $ sudo kill -9 2303
joep@kangoo:~ $ sudo /etc/init.d/weewx start
[ ok ] Starting weewx (via systemctl): weewx.service.

It gave the same message as before but this time weewx was started!!
The syslog page gave:

Nov  3 10:55:49 kangoo systemd[1]: Stopping LSB: weewx weather system...
Nov  3 10:55:49 kangoo systemd[1]: Stopped LSB: weewx weather system.
Nov  3 10:58:22 kangoo systemd[1]: Starting LSB: weewx weather system...
Nov  3 10:58:22 kangoo systemd[1]: Started LSB: weewx weather system.
--
But this time ps -ef|grep weewx gave the running weewx and all looks 
normal. I haven't tried to do a start and stop to test of it remains 
working.
Another annoying problem is that the gauge generator generates 104 lines 
with
"GaugeGenerator: Cannot decode reading of 'None' for gauge 'windDir'" 
but then it gave a reading followed by another run of the error message.

I think it is a bug somewhere but it inflates the log file to no use.
Do you know how to get rid of this?
Joep



On 02/11/16 23:58, Glenn McKechnie wrote:

First thought is to open two terminals.
In the first one run *sudo tail -f /var/log/syslog
*
In the second run your start commands. Additionally, make sure you 
run*sudo /etc/init.d/weewx stop* first, or use*restart / reload *instead*.


*
**
**run*sudo /etc/init.d/weewx status *or*sudo service weewx status* 
immediately after and you will be given a short log extract, a status 
report of that daemon*

*
*
*
You can add -x to the top of //etc/init.d/weewx/ - ie #!/bin/sh -x**to 
get some feedback - whether it's helpful or not is probably debatable. 
Make sure you*run systemctl daemon-reload *anytime you edit an init.d 
config file.


Second thought - have you changed from a deb to a setup.py install 
recently? ie:- is it the correct init.d script for your installation?

*

*



Cheers
 Glenn

rorpi - read only raspberry pi + weewx: now with scripts 





--
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] Pi Stops Reporting to Wunderground

[gjr80]

It's also hard to see exactly what your (weewx) config is. When posting the log 
Andrew asked for could you please post asanitised weewx.conf or a wee_debug 
report.

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] Pi Stops Reporting to Wunderground

[Andrew Milner]

Is the 2A supply powering the hub or the pi?

since it is some time since your original post - can you post a section of 
log which highlights the problem now.

I had a problem with debian wheezy and an rpi2 B which after running \ok 
for a few years suddenly started to just stop and no errors in logs or 
anything - it just ceased processing altogether and the first I knew was an 
email from wunderground!!  Have replaced it with an rpi3 and debian Jessie 
and so far, touch wood, all is ok again.  I have not yet started really 
investigating what actually was going wrong - I had several theories which 
were disproved one by one until swapping the pi seemed the only option.  I 
don't know if it was debian, weewx, my hdd or what - but I think it was not 
weewx (since Jessie seems to be running fine)





On Thursday, 3 November 2016 11:41:30 UTC+2, Andy Harrold wrote:

> Ive now purchase a new USB Hub with a 2A power supply. Unfortunately it 
> hasn't fixed the problem. 
>
> On Sunday, 2 October 2016 01:41:04 UTC+1, Andrew Milner wrote:
>>
>> Try a 1.5A or 2A supply and see if it helps.
>>
>>
>>
>> On Saturday, 1 October 2016 23:06:05 UTC+3, Andy Harrold wrote:
>>
>>> Hi.
>>>
>>> 1. Using a powered USB Hub
>>> 2. 5v 1.0amp
>>>
>>> On Saturday, 1 October 2016 12:45:38 UTC+1, Andrew Milner wrote:

 1. Are you using a powered usb hub (recommended) or the usb ports on 
 the RPi itself?
 2. What size power supply are you using?

 RPis can be quite critical and finicky concerning both.

 Your problem would appear to be a basic usb issue though, and the 
 wunderground loss etc are mere by-products of a device communication 
 failure.





 On Saturday, 1 October 2016 14:40:00 UTC+3, Andy Harrold wrote:

> Hi,
> Managed to find a log of a failure.
>
> Sep 28 19:07:05 raspberrypi weewx[2083]: te923: read: address 0x020001
> Sep 28 19:07:05 raspberrypi weewx[2083]: te923: read: 5a 81 a1 70 aa 
> 0a aa aa 0a aa aa 0a aa 52 c1 08 aa 0a aa ff ff 9d 3d 03 ee ee ee ee ee 
> ee 
> 07 ee 00 db
> Sep 28 19:07:05 raspberrypi weewx[2083]: te923: read: address 0x4c
> Sep 28 19:07:05 raspberrypi weewx[2083]: te923: read: 5a 7f ff ff ff 
> ff ff ff ff ff ff ff ff ff 10 c6 00 07 33 ff ff 39 28 18 22 98 3d 98 3d 
> c0 
> 3d d5 3d f9
> Sep 28 19:07:15 raspberrypi weewx[2083]: te923: read: address 0x020001
> Sep 28 19:07:16 raspberrypi weewx[2083]: te923: read: 5a 81 a1 70 aa 
> 0a aa aa 0a aa aa 0a aa 52 c1 08 aa 0a aa ff ff 9d 3d 03 ee ee ee ee ee 
> ee 
> 07 ee 00 db
> Sep 28 19:07:16 raspberrypi weewx[2083]: te923: read: address 0x4c
> Sep 28 19:07:16 raspberrypi weewx[2083]: te923: read: 5a 7f ff ff ff 
> ff ff ff ff ff ff ff ff ff 10 c6 00 07 33 ff ff 39 28 18 22 98 3d 98 3d 
> c0 
> 3d d5 3d f9
> Sep 28 19:07:26 raspberrypi weewx[2083]: te923: read: address 0x020001
> Sep 28 19:07:26 raspberrypi weewx[2083]: te923: read: 5a 81 a1 70 aa 
> 0a aa aa 0a aa aa 0a aa 52 c1 08 aa 0a aa ff ff 9d 3d 03 ee ee ee ee ee 
> ee 
> 07 ee 00 db
> Sep 28 19:07:26 raspberrypi weewx[2083]: te923: read: address 0x4c
> Sep 28 19:07:26 raspberrypi weewx[2083]: te923: read: 5a 7f ff ff ff 
> ff ff ff ff ff ff ff ff ff 10 c6 00 07 33 ff ff 39 28 18 22 98 3d 98 3d 
> c0 
> 3d d5 3d f9
> Sep 28 19:07:33 raspberrypi kernel: [87218.944317] usb 1-1.2.1.2: USB 
> disconnect, device number 8
> Sep 28 19:07:33 raspberrypi rsyslogd-2007: action 'action 17' 
> suspended, next retry is Wed Sep 28 19:09:03 2016 [try 
> http://www.rsyslog.com/e/2007 ]
> Sep 28 19:07:33 raspberrypi kernel: [87219.193350] usb 1-1.2.1.2: new 
> low-speed USB device number 9 using dwc_otg
> Sep 28 19:07:33 raspberrypi kernel: [87219.299415] usb 1-1.2.1.2: New 
> USB device found, idVendor=1130, idProduct=6801
> Sep 28 19:07:33 raspberrypi kernel: [87219.299456] usb 1-1.2.1.2: New 
> USB device strings: Mfr=0, Product=1, SerialNumber=0
> Sep 28 19:07:33 raspberrypi kernel: [87219.299479] usb 1-1.2.1.2: 
> Product:  
> Sep 28 19:07:33 raspberrypi kernel: [87219.318477] hid-generic 
> 0003:1130:6801.0002: hiddev0,hidraw0: USB HID v1.10 Device [ ] on 
> usb-2098.usb-1.2.1.2/input0
> Sep 28 19:07:33 raspberrypi mtp-probe: checking bus 1, device 9: 
> "/sys/devices/platform/soc/2098.usb/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1.2"
> Sep 28 19:07:33 raspberrypi mtp-probe: bus: 1, device: 9 was not an 
> MTP device
> Sep 28 19:07:36 raspberrypi weewx[2083]: te923: read: address 0x020001
> Sep 28 19:07:36 raspberrypi weewx[2083]: te923: Failed attempt 1 of 5 
> to read data: error sending control message: No such device
> Sep 28 19:07:36 raspberrypi weewx[2083]: te923: Waiting 3 seconds 
> before retry
> Sep 28 19:07:39 raspberrypi weewx[2083]: te923: Failed attempt 2 of 5 
> to rea

Re: [weewx-user] Pi Stops Reporting to Wunderground

[Andy Harrold]

Ive now purchase a new USB Hub with a 2A power supply. Unfortunately it 
hasn't fixed the problem. 

On Sunday, 2 October 2016 01:41:04 UTC+1, Andrew Milner wrote:
>
> Try a 1.5A or 2A supply and see if it helps.
>
>
>
> On Saturday, 1 October 2016 23:06:05 UTC+3, Andy Harrold wrote:
>
>> Hi.
>>
>> 1. Using a powered USB Hub
>> 2. 5v 1.0amp
>>
>> On Saturday, 1 October 2016 12:45:38 UTC+1, Andrew Milner wrote:
>>>
>>> 1. Are you using a powered usb hub (recommended) or the usb ports on the 
>>> RPi itself?
>>> 2. What size power supply are you using?
>>>
>>> RPis can be quite critical and finicky concerning both.
>>>
>>> Your problem would appear to be a basic usb issue though, and the 
>>> wunderground loss etc are mere by-products of a device communication 
>>> failure.
>>>
>>>
>>>
>>>
>>>
>>> On Saturday, 1 October 2016 14:40:00 UTC+3, Andy Harrold wrote:
>>>
 Hi,
 Managed to find a log of a failure.

 Sep 28 19:07:05 raspberrypi weewx[2083]: te923: read: address 0x020001
 Sep 28 19:07:05 raspberrypi weewx[2083]: te923: read: 5a 81 a1 70 aa 0a 
 aa aa 0a aa aa 0a aa 52 c1 08 aa 0a aa ff ff 9d 3d 03 ee ee ee ee ee ee 07 
 ee 00 db
 Sep 28 19:07:05 raspberrypi weewx[2083]: te923: read: address 0x4c
 Sep 28 19:07:05 raspberrypi weewx[2083]: te923: read: 5a 7f ff ff ff ff 
 ff ff ff ff ff ff ff ff 10 c6 00 07 33 ff ff 39 28 18 22 98 3d 98 3d c0 3d 
 d5 3d f9
 Sep 28 19:07:15 raspberrypi weewx[2083]: te923: read: address 0x020001
 Sep 28 19:07:16 raspberrypi weewx[2083]: te923: read: 5a 81 a1 70 aa 0a 
 aa aa 0a aa aa 0a aa 52 c1 08 aa 0a aa ff ff 9d 3d 03 ee ee ee ee ee ee 07 
 ee 00 db
 Sep 28 19:07:16 raspberrypi weewx[2083]: te923: read: address 0x4c
 Sep 28 19:07:16 raspberrypi weewx[2083]: te923: read: 5a 7f ff ff ff ff 
 ff ff ff ff ff ff ff ff 10 c6 00 07 33 ff ff 39 28 18 22 98 3d 98 3d c0 3d 
 d5 3d f9
 Sep 28 19:07:26 raspberrypi weewx[2083]: te923: read: address 0x020001
 Sep 28 19:07:26 raspberrypi weewx[2083]: te923: read: 5a 81 a1 70 aa 0a 
 aa aa 0a aa aa 0a aa 52 c1 08 aa 0a aa ff ff 9d 3d 03 ee ee ee ee ee ee 07 
 ee 00 db
 Sep 28 19:07:26 raspberrypi weewx[2083]: te923: read: address 0x4c
 Sep 28 19:07:26 raspberrypi weewx[2083]: te923: read: 5a 7f ff ff ff ff 
 ff ff ff ff ff ff ff ff 10 c6 00 07 33 ff ff 39 28 18 22 98 3d 98 3d c0 3d 
 d5 3d f9
 Sep 28 19:07:33 raspberrypi kernel: [87218.944317] usb 1-1.2.1.2: USB 
 disconnect, device number 8
 Sep 28 19:07:33 raspberrypi rsyslogd-2007: action 'action 17' 
 suspended, next retry is Wed Sep 28 19:09:03 2016 [try 
 http://www.rsyslog.com/e/2007 ]
 Sep 28 19:07:33 raspberrypi kernel: [87219.193350] usb 1-1.2.1.2: new 
 low-speed USB device number 9 using dwc_otg
 Sep 28 19:07:33 raspberrypi kernel: [87219.299415] usb 1-1.2.1.2: New 
 USB device found, idVendor=1130, idProduct=6801
 Sep 28 19:07:33 raspberrypi kernel: [87219.299456] usb 1-1.2.1.2: New 
 USB device strings: Mfr=0, Product=1, SerialNumber=0
 Sep 28 19:07:33 raspberrypi kernel: [87219.299479] usb 1-1.2.1.2: 
 Product:  
 Sep 28 19:07:33 raspberrypi kernel: [87219.318477] hid-generic 
 0003:1130:6801.0002: hiddev0,hidraw0: USB HID v1.10 Device [ ] on 
 usb-2098.usb-1.2.1.2/input0
 Sep 28 19:07:33 raspberrypi mtp-probe: checking bus 1, device 9: 
 "/sys/devices/platform/soc/2098.usb/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1.2"
 Sep 28 19:07:33 raspberrypi mtp-probe: bus: 1, device: 9 was not an MTP 
 device
 Sep 28 19:07:36 raspberrypi weewx[2083]: te923: read: address 0x020001
 Sep 28 19:07:36 raspberrypi weewx[2083]: te923: Failed attempt 1 of 5 
 to read data: error sending control message: No such device
 Sep 28 19:07:36 raspberrypi weewx[2083]: te923: Waiting 3 seconds 
 before retry
 Sep 28 19:07:39 raspberrypi weewx[2083]: te923: Failed attempt 2 of 5 
 to read data: error sending control message: No such device
 Sep 28 19:07:39 raspberrypi weewx[2083]: te923: Waiting 3 seconds 
 before retry
 Sep 28 19:07:42 raspberrypi weewx[2083]: te923: Failed attempt 3 of 5 
 to read data: error sending control message: No such device
 Sep 28 19:07:42 raspberrypi weewx[2083]: te923: Waiting 3 seconds 
 before retry
 Sep 28 19:07:45 raspberrypi weewx[2083]: te923: Failed attempt 4 of 5 
 to read data: error sending control message: No such device
 Sep 28 19:07:45 raspberrypi weewx[2083]: te923: Waiting 3 seconds 
 before retry
 Sep 28 19:07:48 raspberrypi weewx[2083]: te923: Failed attempt 5 of 5 
 to read data: error sending control message: No such device
 Sep 28 19:07:48 raspberrypi weewx[2083]: te923: Waiting 3 seconds 
 before retry
 Sep 28 19:07:51 raspberrypi weewx[2083]: engine: Main loop exiting. 
 Shutting engine down.
 Sep 28 19:07:51 raspberrypi weewx[2083]: engine: Shutting down