Re: [weewx-user] Re: Raspberry pi 3 and davis vp2

[Geoff Weather]

Thanks Andrew I am about to give it ago again now all I have on pi is
raspbian so firstly will install python and then up to weewx

On 27 July 2016 at 02:03, Andrew Milner  wrote:

> Wow - in harmony with Vince is indeed unusual  :) :) :) but in the hope of
> making sure the point sticks I'll echo Vince again - and say on this
> occasion run, don't walk, to the edx class.  Your time will be very well
> spent and as Vince says your stress levels should go down significantly,
> and your confidence go up.
>
> The RPi forums also have a wealth of information you may find useful.
>
> Again, you do not need to know python or be into programming - just
> editing of text files and use of the command line for command input rather
> than using a Windows style Graphical User Interface
>
>
> On Wednesday, 27 July 2016 00:39:08 UTC+3, vince wrote:
>
>> On Tuesday, July 26, 2016 at 8:26:55 AM UTC-7, Andrew Milner wrote:
>>>
>>> You really do not need to know python or code, but you do need to be
>>> able to use a text editor such as nano, and you need to understand the
>>> different options which weewx makes available to you and how the different
>>> parameters may work - it is all done by editing the .conf parameter files -
>>> not by writing code.
>>>
>>>
>> Yikes - I agreed with Andrew three times this week :-)
>>
>>- For CWOP, WU, PWS this is done in the weewx.conf file- look at the
>>skeleton file at https://github.com/weewx/weewx/blob/master/weewx.conf
>>around line 60, it should be self-evident.  If not, ask.
>>- being in the US, I do not personally know how you set up weewx to
>>post to the Met office, but I know others here do.
>>- I do not personally know how you'd add stuff to weewx to tweet, but
>>(a) I'd like to know and (b) I'm certain others here do know how
>>
>> You will need to know how to edit simple text files.  You will need to
>> occasionally start/stop weewx from the command line.  You almost certainly
>> 'should' be able to find and examine your os system logs.   Very simple
>> stuff.
>>
>>
>> Again, run - do not walk - and 'do' that free edx.org Linux Fundamentals
>> self-paced class I keep mentioning.   Your stress level should go down as a
>> result.
>>
>>
>> --
> 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/4VeXOEfCCfo/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.
>



-- 
Regards Geoff Senior Weather Observer Prestatyn Weather Station
Met Office Climate site Run by Volunteers for the community.

northwalesweather...@btinternet.com
prestatynweat...@btinternet.com

http://www.findu.com/cgi-bin/find.cgi?call=EW4701
http://www.pwsweather.com/obs/STORM1968.html
*http://www.wunderground.com/personal-weather-station/dashboard?ID=IRHYL2
*
https://twitter.com/MW6GCN

-- 
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: Raspberry pi 3 and davis vp2

[Andrew Milner]

python should aslready be installed. 

on the command line give the command 
python -V  (capital V)

and it whould tell you the version installed
#


On Wednesday, 27 July 2016 10:24:07 UTC+3, Geoff Weather wrote:

> Thanks Andrew I am about to give it ago again now all I have on pi is 
> raspbian so firstly will install python and then up to weewx 
>
> On 27 July 2016 at 02:03, Andrew Milner  > wrote:
>
>> Wow - in harmony with Vince is indeed unusual  :) :) :) but in the hope 
>> of making sure the point sticks I'll echo Vince again - and say on this 
>> occasion run, don't walk, to the edx class.  Your time will be very well 
>> spent and as Vince says your stress levels should go down significantly, 
>> and your confidence go up.
>>
>> The RPi forums also have a wealth of information you may find useful.
>>
>> Again, you do not need to know python or be into programming - just 
>> editing of text files and use of the command line for command input rather 
>> than using a Windows style Graphical User Interface
>>
>>
>> On Wednesday, 27 July 2016 00:39:08 UTC+3, vince wrote:
>>
>>> On Tuesday, July 26, 2016 at 8:26:55 AM UTC-7, Andrew Milner wrote:

 You really do not need to know python or code, but you do need to be 
 able to use a text editor such as nano, and you need to understand the 
 different options which weewx makes available to you and how the different 
 parameters may work - it is all done by editing the .conf parameter files 
 - 
 not by writing code.


>>> Yikes - I agreed with Andrew three times this week :-)
>>>
>>>- For CWOP, WU, PWS this is done in the weewx.conf file- look at the 
>>>skeleton file at 
>>>https://github.com/weewx/weewx/blob/master/weewx.conf around line 
>>>60, it should be self-evident.  If not, ask.
>>>- being in the US, I do not personally know how you set up weewx to 
>>>post to the Met office, but I know others here do.
>>>- I do not personally know how you'd add stuff to weewx to tweet, 
>>>but (a) I'd like to know and (b) I'm certain others here do know how
>>>
>>> You will need to know how to edit simple text files.  You will need to 
>>> occasionally start/stop weewx from the command line.  You almost certainly 
>>> 'should' be able to find and examine your os system logs.   Very simple 
>>> stuff.
>>>
>>>
>>> Again, run - do not walk - and 'do' that free edx.org Linux 
>>> Fundamentals self-paced class I keep mentioning.   Your stress level should 
>>> go down as a result.
>>>
>>>
>>> -- 
>> 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/4VeXOEfCCfo/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Regards Geoff Senior Weather Observer Prestatyn Weather Station
> Met Office Climate site Run by Volunteers for the community. 
>
> northwales...@btinternet.com 
> prestaty...@btinternet.com 
>
> http://www.findu.com/cgi-bin/find.cgi?call=EW4701
> http://www.pwsweather.com/obs/STORM1968.html
> *http://www.wunderground.com/personal-weather-station/dashboard?ID=IRHYL2 
> *
> https://twitter.com/MW6GCN
>
>

-- 
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: Apache is not showing /weewx on Ubuntu 16.04.1

[Andrew Milner]

It is either :
a) you not understanding how to make apache serve web pages that are not 
immediately in the apache2 root tree 
or 
b) you not configuring weewx to make the pages within the apache tree

weewx is set up to create the pages in weewx/public_html and then ftp them 
top a web server hosted externally.  If your web server is local to 
weewx then you have got options a and b above, and the instructions are for 
option b) above I think.







On Wednesday, 27 July 2016 09:52:30 UTC+3, Vlad Rafeev wrote:

> Thank you, I will try.
>
> Do you think it is my fault? Or documentation should be updated with your 
> advice?
>

-- 
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: Apache is not showing /weewx on Ubuntu 16.04.1

[gjr80]

Actually, if the issue was a Vince pointed out:

You didn't add a symbolic link from your apache2 document root to the 
> public_html tree weewx writes to.


then I think under the circumstances it may not have been you and rather 
the docs could be at fault.

I am following this tutorial
> http://weewx.com/docs/usersguide.htm#integrating_with_webserver
>
> 1. I have installed clean Ubuntu 16.04.1
> 2. I have installed weewx from DEB package
> 3. I have installed apache2 with "sudo apt-get install apache2" command
> 4. I see test Apache page on localhost (its working)
>

The OP did a deb package install and the link he is following clearly says 
all you need do is install apache2 and then go to http://localhost/weewx. 
The bit about copying conf files etc clearly applies to a setup.py install 
which the OP does not have.

If there is a need to so something else other then 'install apache2 and 
then open http://localhost/weewx' then perhaps the docs need a bit of 
clarrification/further guidance. That being said, I am not an apache2 user.

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] Re: Apache is not showing /weewx on Ubuntu 16.04.1

[Andrew Milner]

You're probably right in that it looks as though the guide assumes apache2 
is installed first, before the deb install - although there then appear to 
be some linguistic issues with present tense used when maybe it should 
be future!! I don't use apache2 either - preferring lighttpd on my rpi.

On Wednesday, 27 July 2016 11:47:41 UTC+3, gjr80 wrote:
>
> Actually, if the issue was a Vince pointed out:
>
> You didn't add a symbolic link from your apache2 document root to the 
>> public_html tree weewx writes to.
>
>
> then I think under the circumstances it may not have been you and rather 
> the docs could be at fault.
>
> I am following this tutorial
>> http://weewx.com/docs/usersguide.htm#integrating_with_webserver
>>
>> 1. I have installed clean Ubuntu 16.04.1
>> 2. I have installed weewx from DEB package
>> 3. I have installed apache2 with "sudo apt-get install apache2" command
>> 4. I see test Apache page on localhost (its working)
>>
>
> The OP did a deb package install and the link he is following clearly says 
> all you need do is install apache2 and then go to http://localhost/weewx. 
> The bit about copying conf files etc clearly applies to a setup.py 
> install which the OP does not have.
>
> If there is a need to so something else other then 'install apache2 and 
> then open http://localhost/weewx' then perhaps the docs need a bit of 
> clarrification/further guidance. That being said, I am not an apache2 
> user.
>
> 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] Re: Apache is not showing /weewx on Ubuntu 16.04.1

[Vlad Rafeev]

> First, install a web server on the computer on which weewx is running

>From this line it is clear, that weewx is already running. So I install 
apache2 according to this guide.

The correct sequence is to install apache2 first and add weewx later?

On Wednesday, July 27, 2016 at 11:19:59 AM UTC+2, Andrew Milner wrote:
>
> You're probably right in that it looks as though the guide assumes apache2 
> is installed first, before the deb install - although there then appear to 
> be some linguistic issues with present tense used when maybe it should 
> be future!! I don't use apache2 either - preferring lighttpd on my rpi.
>

-- 
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: Apache is not showing /weewx on Ubuntu 16.04.1

[Andrew Milner]

The simple answer is to do what Vince said - put a symbolic link in the 
apache root.

Looking at other instructions, out of curiosity - from the quick start 
guide:

After about 5 minutes, open the station web page in a web browser. You 
should see your station information and data. 

*file:///var/www/weewx/index.html* 

If your hardware supports hardware archiving, then how long you wait will 
depend on the *archive interval* 
 set in your 
hardware. 


does the browser find the page??


Although if you have changed things in weewx.conf the files could now be 
being put into different places!!



On Wednesday, 27 July 2016 12:29:25 UTC+3, Vlad Rafeev wrote:

> > First, install a web server on the computer on which weewx is running
>
> From this line it is clear, that weewx is already running. So I install 
> apache2 according to this guide.
>
> The correct sequence is to install apache2 first and add weewx later?
>
> On Wednesday, July 27, 2016 at 11:19:59 AM UTC+2, Andrew Milner wrote:
>>
>> You're probably right in that it looks as though the guide assumes 
>> apache2 is installed first, before the deb install - although there then 
>> appear to be some linguistic issues with present tense used when maybe it 
>> should be future!! I don't use apache2 either - preferring lighttpd on my 
>> rpi.
>>
>

-- 
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: Instromet Sunshine Sensor

[Robin]

Thank you Susan, the voltage divider I understand.

Now I get into territory that I have not a clue about! I can manage English 
(most of the time) and a little Greek (some of the time) but code comes in 
at none of the time!!!

Can anyone help me here.


   - I need to record (at short intervals) if there is a voltage present 
   via GPIO (the sun is casting a shadow).
   - at each archive interval I need to write the data to the database and 
   reset the record to zero, then start over again.

I hope that there is some kind soul out there with the time, skill and 
interest to help me. If I can get this sorted with a dummy sensor I will 
buy the Instromet Sunshine Sensor and report back.

Measuring the hours of sunshine has been a 'bee in my bonnet' for a while 
and I currently estimate this from solar radiation. The Instromat sensor 
seems to be a much more precise tool. I would love to have this working and 
compare it to my estimated method.

Thanks for reading this far.
Regards
Robin



-- 
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: Raspian TE923 USB Problem

[Dennis slagers]

Lucky I saw that the 018rc8 = 0.18

https://github.com/weewx/weewx/commit/2f8c3ec69f3d662b7ddf43d266924f80ed500cda

I have modified the driver a very little due to some raspberry pi issue (I 
think)
wrote a blog entry about it and also added previous suggestions

https://www.aroundmyroom.com/2016/07/17/weatherstation-and-te923-usb-issues-on-a-raspberry-pi/

after 3 days it crashed due to not having my SD card size deployed totally. 
I was missing 6GB or so ;-) .. 
drive full . .(duh) .. 
fixed that with the piconfig.

It's up 7 days now. Longest uptime was during my holiday 21 days, so we 
have some days to gooo .. 


Op vrijdag 15 juli 2016 13:42:58 UTC+2 schreef hf:
>
> The following points have helped me. work Probably the newer drivers. 
> Cause was certainly the erroneous detection of the interface. Thank you 
> very much.
>
>
>1. *te923*-0.18*rc5* 
>2. vi /etc/udev/rules.d/99-te923.rules 
>3. 
>
>ATTRS{idVendor}=="1130", ATTRS{idProduct}=="6801", MODE="0660", 
> GROUP="plugdev", RUN="/bin/sh -c 'echo -n $id:1.0 > 
> /sys/bus/usb/drivers/usbhid/unbind'"
>
>4. 
>
>udevadm control --reload-rules
>
>
> 2-3: http://www.tdressler.net/ipsymcon/te923.html
>

-- 
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: Raspian TE923 USB Problem

[mwall]

On Wednesday, July 27, 2016 at 9:03:02 AM UTC-4, Dennis slagers wrote:
>
> Lucky I saw that the 018rc8 = 0.18
>
>
> https://github.com/weewx/weewx/commit/2f8c3ec69f3d662b7ddf43d266924f80ed500cda
>
> I have modified the driver a very little due to some raspberry pi issue (I 
> think)
> wrote a blog entry about it and also added previous suggestions
>
>
> https://www.aroundmyroom.com/2016/07/17/weatherstation-and-te923-usb-issues-on-a-raspberry-pi/
>
> after 3 days it crashed due to not having my SD card size deployed 
> totally. I was missing 6GB or so ;-) .. 
> drive full . .(duh) .. 
> fixed that with the piconfig.
>
> It's up 7 days now. Longest uptime was during my holiday 21 days, so we 
> have some days to gooo .. 
>
>
>
dennis,

thank you for documenting your steps in your blog posting.

it is not clear whether the reset is necessary.  it is supposed to provide 
a clean slate for the driver to start communicating with the usb.  however, 
i think its actual efficacy depends on the operating system, libusb, and 
pyusb versions.

the bind command seems to be the important part here:

echo -n $id:1.0 > /sys/bus/usb/drivers/usbhid/unbind


what is $id?  you can find out by doing:

cat /sys/bus/usb/drivers/usbhid/unbind

so far this seems to be specific to rpi, but perhaps not all rpi.  could 
you tell us which os you are running on your pi?

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: Raspian TE923 USB Problem

[Dennis slagers]

Op woensdag 27 juli 2016 16:10:36 UTC+2 schreef mwall:
>
>
>
> On Wednesday, July 27, 2016 at 9:03:02 AM UTC-4, Dennis slagers wrote:
>>
>> Lucky I saw that the 018rc8 = 0.18
>>
>>
>> https://github.com/weewx/weewx/commit/2f8c3ec69f3d662b7ddf43d266924f80ed500cda
>>
>> I have modified the driver a very little due to some raspberry pi issue 
>> (I think)
>> wrote a blog entry about it and also added previous suggestions
>>
>>
>> https://www.aroundmyroom.com/2016/07/17/weatherstation-and-te923-usb-issues-on-a-raspberry-pi/
>>
>> after 3 days it crashed due to not having my SD card size deployed 
>> totally. I was missing 6GB or so ;-) .. 
>> drive full . .(duh) .. 
>> fixed that with the piconfig.
>>
>> It's up 7 days now. Longest uptime was during my holiday 21 days, so we 
>> have some days to gooo .. 
>>
>>
>>
> dennis,
>
> thank you for documenting your steps in your blog posting.
>
> it is not clear whether the reset is necessary.  it is supposed to provide 
> a clean slate for the driver to start communicating with the usb.  however, 
> i think its actual efficacy depends on the operating system, libusb, and 
> pyusb versions.
>
> the bind command seems to be the important part here:
>
> echo -n $id:1.0 > /sys/bus/usb/drivers/usbhid/unbind
>
>
> what is $id?  you can find out by doing:
>
> cat /sys/bus/usb/drivers/usbhid/unbind
>
> so far this seems to be specific to rpi, but perhaps not all rpi.  could 
> you tell us which os you are running on your pi?
>
> m
>


sudo cat /sys/bus/usb/drivers/usbhid/unbind
cat: /sys/bus/usb/drivers/usbhid/unbind: Permission denied

sudo echo -n $id:1.0 > /sys/bus/usb/drivers/usbhid/unbind
-bash: /sys/bus/usb/drivers/usbhid/unbind: Permission denied

even as root .. permission denied... 


PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/";
SUPPORT_URL="http://www.raspbian.org/RaspbianForums";
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs";

drwxr-xr-x 2 root root0 Jul 27 16:31 .
drwxr-xr-x 8 root root0 Jul 27 16:31 ..
--w--- 1 root root 4096 Jul 27 16:31 bind
lrwxrwxrwx 1 root root0 Jul 27 16:31 module -> ../../../../module/usbhid
-rw-r--r-- 1 root root 4096 Jul 27 16:31 new_id
-rw-r--r-- 1 root root 4096 Jul 27 16:31 remove_id
--w--- 1 root root 4096 Jul 27 16:31 uevent
--w--- 1 root root 4096 Jul 23 15:34 unbind
root@weatherstation:/sys/bus/usb/drivers/usbhid#

-- 
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: Raspian TE923 USB Problem

[Dennis slagers]

>
>
>
> sudo cat /sys/bus/usb/drivers/usbhid/unbind
> cat: /sys/bus/usb/drivers/usbhid/unbind: Permission denied
>
> sudo echo -n $id:1.0 > /sys/bus/usb/drivers/usbhid/unbind
> -bash: /sys/bus/usb/drivers/usbhid/unbind: Permission denied
>
> even as root .. permission denied... 
>
>
> PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
> NAME="Raspbian GNU/Linux"
> VERSION_ID="8"
> VERSION="8 (jessie)"
> ID=raspbian
> ID_LIKE=debian
> HOME_URL="http://www.raspbian.org/";
> SUPPORT_URL="http://www.raspbian.org/RaspbianForums";
> BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs";
>
> drwxr-xr-x 2 root root0 Jul 27 16:31 .
> drwxr-xr-x 8 root root0 Jul 27 16:31 ..
> --w--- 1 root root 4096 Jul 27 16:31 bind
> lrwxrwxrwx 1 root root0 Jul 27 16:31 module -> 
> ../../../../module/usbhid
> -rw-r--r-- 1 root root 4096 Jul 27 16:31 new_id
> -rw-r--r-- 1 root root 4096 Jul 27 16:31 remove_id
> --w--- 1 root root 4096 Jul 27 16:31 uevent
> --w--- 1 root root 4096 Jul 23 15:34 unbind
> root@weatherstation:/sys/bus/usb/drivers/usbhid#
>

lsusb gives
root@weatherstation:/home/pi# lsusb
Bus 001 Device 005: ID 1130:6801 Tenx Technology, Inc.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 

-- 
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] Sensor Error (Started out of nowhere)

[Lymkin]

I've started getting the following error and nothing logs to WUnderground 
anymore.

weewx[975]: acurite: R1: ignoring stale data (rssi indicates no 
communication from sensors): 01 cf da 71 01 1d 15 69 00 00

Was working fine and just started this behavior.  The Accurite display 
shows current values, so I know it is talking to the outdoor sensors.

Any ideas?

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: Sensor Error (Started out of nowhere)

[mwall]

On Wednesday, July 27, 2016 at 12:06:37 PM UTC-4, Lymkin wrote:
>
> I've started getting the following error and nothing logs to WUnderground 
> anymore.
>
> weewx[975]: acurite: R1: ignoring stale data (rssi indicates no 
> communication from sensors): 01 cf da 71 01 1d 15 69 00 00
>
> Was working fine and just started this behavior.  The Accurite display 
> shows current values, so I know it is talking to the outdoor sensors.
>
> Any ideas?
>

how often does this happen?  for how long?

how do you know that the display is talking to the sensors?  the display 
will show the last values received, even if they are not current.

when the rssi goes to zero, the sensor values reported by the console 
cannot be trusted.  (the rssi is the second to last byte in the R1 message 
you posted)

it is possible that the firmware is confused and sends a value of 00 for 
rssi no matter what the actual value is.  you would have to power cycle the 
console to fix that.

usually you can simply wait until the console re-establishes connection and 
receives new data.

if this happens often, then look for patterns in the log to see if you can 
correlate bad rssi with radio interference sources.

if it happens for extended periods, and you have ruled out rf interference, 
then consider relocating the console so that it has a more reliable signal 
from the sensors.

or purchase one of the new acurite repeaters:

https://www.acurite.com/wireless-signal-extender-for-acurite-sensors.html

http://www.wxforum.net/index.php?topic=29898.0

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: Sensor Error (Started out of nowhere)

[Lymkin]

I know the sensors were working because I could see wind, temp, etc. 
changing over time.

I did end up clearing the memory and it has been stable for the past hour 
or so.  I'm wondering if it was trying to read memory and saw old 
values.not sure at this point.

On Wednesday, July 27, 2016 at 11:29:29 AM UTC-5, mwall wrote:
>
> On Wednesday, July 27, 2016 at 12:06:37 PM UTC-4, Lymkin wrote:
>>
>> I've started getting the following error and nothing logs to WUnderground 
>> anymore.
>>
>> weewx[975]: acurite: R1: ignoring stale data (rssi indicates no 
>> communication from sensors): 01 cf da 71 01 1d 15 69 00 00
>>
>> Was working fine and just started this behavior.  The Accurite display 
>> shows current values, so I know it is talking to the outdoor sensors.
>>
>> Any ideas?
>>
>
> how often does this happen?  for how long?
>
> how do you know that the display is talking to the sensors?  the display 
> will show the last values received, even if they are not current.
>
> when the rssi goes to zero, the sensor values reported by the console 
> cannot be trusted.  (the rssi is the second to last byte in the R1 message 
> you posted)
>
> it is possible that the firmware is confused and sends a value of 00 for 
> rssi no matter what the actual value is.  you would have to power cycle the 
> console to fix that.
>
> usually you can simply wait until the console re-establishes connection 
> and receives new data.
>
> if this happens often, then look for patterns in the log to see if you can 
> correlate bad rssi with radio interference sources.
>
> if it happens for extended periods, and you have ruled out rf 
> interference, then consider relocating the console so that it has a more 
> reliable signal from the sensors.
>
> or purchase one of the new acurite repeaters:
>
> https://www.acurite.com/wireless-signal-extender-for-acurite-sensors.html
>
> http://www.wxforum.net/index.php?topic=29898.0
>
> 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: Apache is not showing /weewx on Ubuntu 16.04.1

[vince]

The alternate solution is for you to edit weewx.conf to have it save its 
files in the place the webserver expects things.

The underlying issues are:

   - there are lots of webservers to pick from, they pick different 
   locations for document root
   - operating systems differ in where they set the webserver document root
   - 'versions' of a particular operating system also can change where they 
   set this

So weewx can't possibly keep track of this, there are too many 
ever-changing upstream providers of software.


The user/admin 'must' have enough knowledge to know how to get the files 
weewx generates into

the place 'they' want them to appear when viewed from a web browser.  There 
is no one-true-answer.



-- 
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: Apache is not showing /weewx on Ubuntu 16.04.1

[Vlad Rafeev]

Vince, thank you for clearing this out. I think your great explanation
deserves to be included in the documentation. Right now it feels like
everything should work out of the box, which is clearly not the case.


---
Влад Рафеев
http://dandaka.com/

On Wed, Jul 27, 2016 at 7:13 PM, vince  wrote:

> The alternate solution is for you to edit weewx.conf to have it save its
> files in the place the webserver expects things.
>
> The underlying issues are:
>
>- there are lots of webservers to pick from, they pick different
>locations for document root
>- operating systems differ in where they set the webserver document
>root
>- 'versions' of a particular operating system also can change where
>they set this
>
> So weewx can't possibly keep track of this, there are too many
> ever-changing upstream providers of software.
>
>
> The user/admin 'must' have enough knowledge to know how to get the files
> weewx generates into
>
> the place 'they' want them to appear when viewed from a web browser.
> There is no one-true-answer.
>
>
>
> --
> 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/kzXjvLjWI-k/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: Apache is not showing /weewx on Ubuntu 16.04.1

[Thomas Keffer]

I am not an apache expert either, but from what I can tell, the problem is
that the weewx Debian installs sets HTML_ROOT incorrectly. It's being set
to /var/www, when it should be /var/www/html.

Because of this, the HTML files are being put in a directory that is not
accessible to the Apache server, at least not without modifying its
configuration file.

Try going into /etc/weewx/weewx.conf and changing the lines

# Where the generated reports should go, relative to WEEWX_ROOT
HTML_ROOT = /var/www/weewx

to

# Where the generated reports should go, relative to WEEWX_ROOT
HTML_ROOT = /var/www/weewx/html

then restart weewx.

If my diagnosis is correct, I'm amazed that this problem has been sitting
here all this time. Perhaps Apache changed the default DocumentRoot
recently?

-tk


On Wed, Jul 27, 2016 at 12:00 PM, Vlad Rafeev  wrote:

> Vince, thank you for clearing this out. I think your great explanation
> deserves to be included in the documentation. Right now it feels like
> everything should work out of the box, which is clearly not the case.
>
>
> ---
> Влад Рафеев
> http://dandaka.com/
>
> On Wed, Jul 27, 2016 at 7:13 PM, vince  wrote:
>
>> The alternate solution is for you to edit weewx.conf to have it save its
>> files in the place the webserver expects things.
>>
>> The underlying issues are:
>>
>>- there are lots of webservers to pick from, they pick different
>>locations for document root
>>- operating systems differ in where they set the webserver document
>>root
>>- 'versions' of a particular operating system also can change where
>>they set this
>>
>> So weewx can't possibly keep track of this, there are too many
>> ever-changing upstream providers of software.
>>
>>
>> The user/admin 'must' have enough knowledge to know how to get the files
>> weewx generates into
>>
>> the place 'they' want them to appear when viewed from a web browser.
>> There is no one-true-answer.
>>
>>
>>
>> --
>> 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/kzXjvLjWI-k/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: Apache is not showing /weewx on Ubuntu 16.04.1

[mwall]

On Wednesday, July 27, 2016 at 4:47:09 PM UTC-4, Tom Keffer wrote:
>
> I am not an apache expert either, but from what I can tell, the problem is 
> that the weewx Debian installs sets HTML_ROOT incorrectly. It's being set 
> to /var/www, when it should be /var/www/html. 
>

blame it on more redhat-ification (and disregard for users) of debian.

in debian 7 and earlier, DocumentRoot was /var/www

in debian 8, DocumentRoot is /var/www/html

in redhat and suse, DocumentRoot has been /var/www/html for quite some time

there are at least two solutions:

a) modify HTML_ROOT in weewx.conf:

sudo sed -i -e 's%HTML_ROOT =.*%HTML_ROOT = /var/www/html/weewx%' 
/etc/weewx/weewx.conf

b) create a symlink to the weewx report directory:

sudo ln -s ../weewx /var/www/html

i tend to prefer the latter, especially for systems such as rpi where the 
weewx reports are on a tmpfs to minimize sd card wear.

i have not yet figured out a solution for the weewx .deb package that will 
work out-of-the-box with pre deb8 and post deb8 systems.  it would be nice 
if it worked with lighthttpd and nginx web servers as well as apache.

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: Apache is not showing /weewx on Ubuntu 16.04.1

[Thomas Keffer]

Mystery solved! Thanks, Matthew

I've started issue #137  to
track it.

-tk

On Wed, Jul 27, 2016 at 2:50 PM, mwall  wrote:

> On Wednesday, July 27, 2016 at 4:47:09 PM UTC-4, Tom Keffer wrote:
>>
>> I am not an apache expert either, but from what I can tell, the problem
>> is that the weewx Debian installs sets HTML_ROOT incorrectly. It's being
>> set to /var/www, when it should be /var/www/html.
>>
>
> blame it on more redhat-ification (and disregard for users) of debian.
>
> in debian 7 and earlier, DocumentRoot was /var/www
>
> in debian 8, DocumentRoot is /var/www/html
>
> in redhat and suse, DocumentRoot has been /var/www/html for quite some time
>
> there are at least two solutions:
>
> a) modify HTML_ROOT in weewx.conf:
>
> sudo sed -i -e 's%HTML_ROOT =.*%HTML_ROOT = /var/www/html/weewx%'
> /etc/weewx/weewx.conf
>
> b) create a symlink to the weewx report directory:
>
> sudo ln -s ../weewx /var/www/html
>
> i tend to prefer the latter, especially for systems such as rpi where the
> weewx reports are on a tmpfs to minimize sd card wear.
>
> i have not yet figured out a solution for the weewx .deb package that will
> work out-of-the-box with pre deb8 and post deb8 systems.  it would be nice
> if it worked with lighthttpd and nginx web servers as well as apache.
>
> 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.

[weewx-user] HowTo: Raspberry Pi installation with read-only root

[Glenn McKechnie]

Slightly Off topic, but I'll throw this hat in the ring and hope it doesn't 
come back too fast!

As the title suggests, it's about locking up the SDcard as a read only 
filesystem, then adding weewx to utilize those same features. It works for 
me, it should work for others but given the variation in setups - mainly 
your weather hardware - that statement may be prematurely optimistic?

The current version is at 
https://github.com/glennmckechnie/rorpi-raspberrypi and the rather long 
winded wiki HowTo 
 
should help to fill in the expected blanks.

Anyone feel up to trying it out? If it breaks, you get to keep all the 
pieces, if it works it's yours to polish and shine; or mistreat as you 
desire.
I've used the notes on a RPi3 and it worked for a simulator, running since 
the 31st May, and a WS1080 since the 22nd May. However it needs a wider and 
more varied audience, also a more critical one - I know the routine too 
well so am possibly making assumptions.

Rank beginners would need to take vinces advice and visit edx.org Linux 
class at 
 https://www.edx.org/course/introduction-linux-linuxfoundationx-lfs101x-0 
 
or find another way to come up to speed. (Always happy to be proven wrong 
though.)
Apprentices will probably need to wade through the HowTo, unless your close 
to coming out of your time; in which case you can probably skim those 
notes. (but if you do run into problems, go back and read the notes. It's 
what they are there for!)
Hardened journeymen can probably just the grab the zip file and start 
placing/replacing/linking them as they should be. ( and if you get the 
message "mount is busy" visit the tips page.)
If you don't fall into any of those types, or refuse to be classified, then 
go for it anyway. It's the way a lot of us learnt, and will continue to do 
so.

All feedback welcome.
Testimonials (that would be success stories) especially welcome (ie: it 
will have been useful to others besides myself!)
Problems? Yeah, let me know those too. Sometimes there's no hiding.

Hopefully I haven't bitten off more than I can chew.
Hopefully it won't generate too much extra traffic here, and if it does I 
may need to learn more about google groups?

I've added a section to the weewx wiki pointing to the above HowTo.

That's all Folks... or is it?

cheers
Glenn







-- 
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] Upgrade won't start

[lonehighway]

I've never had this happen before. Trying to upgrade from 3.2.1 to 3.5.0 
and I did what I've always done, download the file, unpack it, cd into it, 
then sudo ./setup-py build, sudo ./setup.py install.

Everything looks normal but when I use /etc/init.d/weewx start nothing at 
all happens. Using tail -f /var/log/syslog shows nothing at all, except the 
previous shutdown of 3.2.1. 

Setting debug=1 also does nothing because the program is not starting, 
there is no log output.

I am intending to migrate my data to a newer server (raspi) and installing 
3.5.0 on the new system works as expected with the simulator.

I am at a loss as to what to look at or should I even bother, but I'd like 
to keep the old server in good order for a backup. Any hints would be 
appreciated.

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