[weewx-user] Re: UV index

2018-04-18 Thread Damjan Hajsek
Yes I see now sorry forget to reconfigure. I also didn't have HP1000 driver so I downloaded it, install it and reconfigure it. but now It doesn't work I get this error. localhost weewx[21212]: HP1000: Timed out too many times Dne četrtek, 19. april 2018 04.39.36 UTC+2 je oseba vk3...@gmail.com

[weewx-user] Re: UV index

2018-04-18 Thread vk3anz
That indicates that you have not followed the instructions for installing the driver and configuring the 'weewx.conf' file. Susan On Thursday, April 19, 2018 at 4:38:24 AM UTC+10, Damjan Hajsek wrote: > > I also tried HP1000 driver as it was suggested by some use, but get this > error. > > Apr 1

Re: [weewx-user] Re: Records not updating from loop hilo

2018-04-18 Thread Praveen Chandrasekaran
The issue seems to be resolved now. I think enabling TimeSynch helped. On Wed, 18 Apr 2018, 23:19 Praveen Chandrasekaran, wrote: > The other issue I can think of is I had disabled TimeSynch. Hence if there > was mismatch between timestamp from station and the raspberry time, I think > the python

[weewx-user] Re: Preloading values in the database

2018-04-18 Thread Andrew Milner
The simplest and nastiest method would be to create one or more archive records for time(s) before you connected to the pi - so stop weewx, make a copy of the database. To create the archive record just use some basic sql to insert into archive and set dateTime, usUnits, interval, rain. If y

[weewx-user] Preloading values in the database

2018-04-18 Thread Paul Dixon
I have just installed weewx on a pi 0W attached to an Acurite 02064. All looks good until I select Year, when it reports the total rainfall for the year as 0. I have had the unit working for a while before attaching the pi so I know the rainfall so far this year. Is there some way I can enter thi

[weewx-user] Re: Ambient Weather WS-2902 reporting troubles with the interceptor extension

2018-04-18 Thread Lorin Tremblay
So just ordered a WS-2902 and was wondering if you ever got it to work? On Saturday, March 17, 2018 at 1:27:17 PM UTC-4, Jim Woodruff wrote: > > > I am using the interceptor extension for my Ambient Weather WS-2902. Data > sent to wunderground, ambientweather.net, and weathercloud are the same >

[weewx-user] Re: weewx.com/apt squeeze Release' does no longer have a Release file

2018-04-18 Thread Andre
That's it! Thank you very much. Andre Am Mittwoch, 18. April 2018 15:25:57 UTC+2 schrieb mwall: > > On Wednesday, April 18, 2018 at 5:44:08 AM UTC-4, Andre wrote: >> >> >> Do I have a secure problem or is it a global issue? >> > > andre, > > did you add the weewx keys to your trusted repositories

Re: [weewx-user] WS-2902

2018-04-18 Thread Jim Myers
I have an Arris TG1682 On Wed, Apr 18, 2018 at 1:15 PM, jan hallink wrote: > When you search on this forum for ws-2902 or ventus w830, you will find > information how to setup the interceptor driver. > But the difficult part is often the router. The weatherdata send to WU > must also be routed t

[weewx-user] WS-2902

2018-04-18 Thread jan hallink
When you search on this forum for ws-2902 or ventus w830, you will find information how to setup the interceptor driver. But the difficult part is often the router. The weatherdata send to WU must also be routed to your raspberry pi (by ip tables). Not every router has this possibility. Which ro

[weewx-user] Re: UV index

2018-04-18 Thread Damjan Hajsek
I also tried HP1000 driver as it was suggested by some use, but get this error. Apr 18 20:31:49 localhost weewx[593]: engine: Caught unrecoverable exception in engine: Apr 18 20:31:49 localhost weewx[593]: No module named HP1000 Apr 18 20:31:49 localhost weewx[593]: Traceback (

Re: [weewx-user] Re: UV index

2018-04-18 Thread Damjan Hajsek
I will do that and post results here Dne sreda, 18. april 2018 15.22.25 UTC+2 je oseba Greg Troxel napisala: > > Damjan Hajsek > writes: > > > So we can't do nothing to make UV index show right value, because with > > calibrating I can not get real data? > > This can probably be solved, but "ca

[weewx-user] Re: UV index

2018-04-18 Thread Ian Millard
I have come to this discussion late in the day. I noticed from one of the earlier posts a dump of your config file. I am I right in understanding that you are using the interceptor driver? It also looks as though you have the HP1000 driver installed as well. Have you tried using this along the

Re: [weewx-user] Re: Records not updating from loop hilo

2018-04-18 Thread Praveen Chandrasekaran
The other issue I can think of is I had disabled TimeSynch. Hence if there was mismatch between timestamp from station and the raspberry time, I think the python code discards the loop data it is outside timespan of accumulator (not entirely sure what it means!). I ahd disabled TimeSynch when I did

Re: [weewx-user] Re: Records not updating from loop hilo

2018-04-18 Thread Praveen Chandrasekaran
Loop Hi-Lo has been true since installation. I m just viewing the StdReport. I always used to look at WU and never bothered about StdReport. Only now I noticed that StdReport max min are a tad off due to 5 minutes sampling. Wouldn't changing record generation to software solve the issue? On Wed,

Re: [weewx-user] Re: Records not updating from loop hilo

2018-04-18 Thread Andrew Milner
Personally I always prefer to stop and start weewx rather than just re-reading the conf - but that is my preference!! What are you using to display the max values? ie what is actually in the template for displaying the max fields?? The wrong syntax/dot code could result in an archive search ra

Re: [weewx-user] Re: Records not updating from loop hilo

2018-04-18 Thread Praveen Chandrasekaran
Loop Hi-Lo was always true. I did kill hup after updating record augmentation Will attach conf in a while. On Wed, 18 Apr 2018, 21:24 Andrew Milner, wrote: > did you stop/start weewx or restart it after changing loop_hilo to true?? > > can you attach your weewx.conf?? > > > > On Wednesday, 18 A

[weewx-user] Re: Records not updating from loop hilo

2018-04-18 Thread Andrew Milner
did you stop/start weewx or restart it after changing loop_hilo to true?? can you attach your weewx.conf?? On Wednesday, 18 April 2018 18:24:19 UTC+3, Praveen Chandrasekaran wrote: > I have Davis Vantage vue with belfryboy data logger. Archive interval set > to 5 minutes. > Record generation

[weewx-user] Records not updating from loop hilo

2018-04-18 Thread Praveen Chandrasekaran
I have Davis Vantage vue with belfryboy data logger. Archive interval set to 5 minutes. Record generation set to hardware in weewx.conf Loop_hilo set to true. However records still seem to built only from archives. I see that all max min times are at 5 min boundary. Today my console shows ma

[weewx-user] Re: weewx.com/apt squeeze Release' does no longer have a Release file

2018-04-18 Thread mwall
On Wednesday, April 18, 2018 at 5:44:08 AM UTC-4, Andre wrote: > > > Do I have a secure problem or is it a global issue? > andre, did you add the weewx keys to your trusted repositories? try this: curl -s http://weewx.com/keys.html | sudo apt-key add - then do your search again. m -- You

Re: [weewx-user] Re: UV index

2018-04-18 Thread Greg Troxel
Damjan Hajsek writes: > So we can't do nothing to make UV index show right value, because with > calibrating I can not get real data? This can probably be solved, but "calibration" is very likely not the approach. Let me try to summarize what we know. Your station seems to show reasonable U

[weewx-user] weewx.com/apt squeeze Release' does no longer have a Release file

2018-04-18 Thread Andre
Hi, I've noticed that I get this message if I try to search updates... E: The repository 'http://weewx.com/apt squeeze Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for r

Re: [weewx-user] Re: Any Netatmo cloud users working?

2018-04-18 Thread José-Manuel Anguita
I've been testing with other systems and I can confirm you that, at least in Debian, the sudo wee_config --reconfigure doesn't modify the netatmo part of /etc/weewx/weewx.conf. The problem is solved if you edit /etc/weewx/weewx.conf manually and at the end of file, you add the four parameters f