[weewx-user] Re: Html formatting setup

[Andrew Milner]

the .css file(s) may be the answer



On Monday, 20 May 2019 03:32:40 UTC+3, Jaybee wrote:
>
> Brand new user. I've got weewx up and running on a rpi for a couple weeks. 
> Posting to a few sites like wow, etc. Running the standard report. Serves 
> up the html just fine locally (I have a little ngnx instance running to 
> serve it). I copy the html directory (var/www/html/weewx) to an aws s3 
> bucket to post the web page. In general it serves up, and all the data is 
> there, stats, graphs, etc. The finer formatting is missing. The colored bar 
> across the top. The day-week-month bold face, etc.
> My guess is there is some bit of formatting I am missing, and not copying. 
> It must be located elsewhere. 
>  Anyone have any insights?
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b00decdc-f2e5-4bee-98c1-9e23b9f784d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Missing Midnight database update

[Jd D]

On Sunday, May 19, 2019 at 1:40:58 PM UTC-7, Jd D wrote:
>
> Hi,
>
> station LaCrosse  ws2316
> weewx version 3.8.2
> hardware Raspberry Pi 
> NAME="Raspbian GNU/Linux"
> VERSION_ID="9"
> VERSION="9 (stretch)"
>
> I have noticed that the midnight updates to the database do not happen.  
> My cron entries is 0,5,10,15,20,25,30,35,40,45,50,55,59.  I added the 59 
> entry otherwise my report data stopped at 23:54 now I get report data at 
> 23:59. My station update interval is set for 1 minute which is supported by 
> the wx2316. Not a big deal but wanted to report this in case there is a fix 
> otherwise I will dig into the code myself and see what I can find. Not sure 
> if this is a software problem in weewx or the station itself.
>
> Here are the database timestamps. There is a jump of a 120 seconds instead 
> of 60 seconds. This is the only time in the day that jumps 120 seconds.
> "1558249380"
> *"1558249320"*
> *"1558249200"*
> "1558249140"
>
> Here is a snippet of the log. There is no record created at midnight.
>
> May 18 23:58:17 localhost weewx[1076]: reportengine: Report RSYNC skipped 
> due to report_timing setting
> *May 18 23:59:25 localhost weewx[1076]: manager: Added record 2019-05-18 
> 23:59:00 MST (1558249140) to database 'weewx.sdb'*
> *May 18 23:59:25 localhost weewx[1076]: manager: Added record 2019-05-18 
> 23:59:00 MST (1558249140) to daily summary in 'weewx.sdb'*
> May 18 23:59:25 localhost weewx[1076]: reportengine: Running reports for 
> latest time in the database.
> May 18 23:59:25 localhost weewx[1076]: reportengine: Running report 
> StandardReport
> May 18 23:59:25 localhost weewx[1076]: reportengine: Found configuration 
> file /etc/weewx/skins/Standard/skin.conf for report StandardReport
> May 18 23:59:25 localhost weewx[1076]: cheetahgenerator: using search list 
> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
> May 18 23:59:25 localhost weewx[1076]: manager: Daily summary version is 
> 2.0
> May 18 23:59:55 localhost weewx[1076]: cheetahgenerator: Generated 18 
> files for report StandardReport in 30.14 seconds
> May 18 23:59:55 localhost weewx[1076]: manager: Daily summary version is 
> 2.0
> May 18 23:59:56 localhost weewx[1076]: imagegenerator: Generated 12 images 
> for StandardReport in 1.39 seconds
> May 18 23:59:56 localhost weewx[1076]: copygenerator: copied 0 files to 
> /var/www/html/weewx
> May 18 23:59:56 localhost weewx[1076]: reportengine: Running report 
> SteelSeries
> May 18 23:59:56 localhost weewx[1076]: reportengine: Found configuration 
> file /etc/weewx/skins/ss/skin.conf for report SteelSeries
> May 18 23:59:56 localhost weewx[1076]: copygenerator: copied 0 files to 
> /var/www/html/weewx/ss
> May 18 23:59:56 localhost weewx[1076]: cheetahgenerator: using search list 
> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
> May 18 23:59:56 localhost weewx[1076]: manager: Daily summary version is 
> 2.0
> May 18 23:59:56 localhost weewx[1076]: cheetahgenerator: Generated 2 files 
> for report SteelSeries in 0.18 seconds
> May 18 23:59:56 localhost weewx[1076]: manager: Daily summary version is 
> 2.0
> May 18 23:59:58 localhost weewx[1076]: imagegenerator: Generated 11 images 
> for SteelSeries in 1.72 seconds
> May 18 23:59:58 localhost weewx[1076]: reportengine: Running report FTP
> May 18 23:59:58 localhost weewx[1076]: reportengine: Found configuration 
> file /etc/weewx/skins/Ftp/skin.conf for report FTP
> May 18 23:59:58 localhost weewx[1076]: ftpgenerator: FTP upload not 
> requested. Skipped.
> May 18 23:59:58 localhost weewx[1076]: reportengine: Running report RSYNC
> May 18 23:59:58 localhost weewx[1076]: reportengine: Found configuration 
> file /etc/weewx/skins/Rsync/skin.conf for report RSYNC
> May 18 23:59:58 localhost weewx[1076]: rsyncgenerator: rsync upload not 
> requested. Skipped.
> May 19 00:00:01 localhost CRON[25282]: (root) CMD 
> (/usr/local/HomeSeer/register_with_find.sh)
> *May 19 00:01:20 localhost weewx[1076]: manager: Added record 2019-05-19 
> 00:00:00 MST (1558249200) to database 'weewx.sdb'*
> *May 19 00:01:20 localhost weewx[1076]: manager: Added record 2019-05-19 
> 00:00:00 MST (1558249200) to daily summary in 'weewx.sdb'*
> May 19 00:01:21 localhost weewx[1076]: reportengine: Running reports for 
> latest time in the database.
> May 19 00:01:21 localhost weewx[1076]: reportengine: Running report 
> StandardReport
> May 19 00:01:21 localhost weewx[1076]: reportengine: Found configuration 
> file /etc/weewx/skins/Standard/skin.conf for report StandardReport
> May 19 00:01:21 localhost weewx[1076]: cheetahgenerator: using search list 
> ['weewx.cheetahgenerator.Almanac', 

[weewx-user] Html formatting setup

[Jim Brand]

Brand new user. I've got weewx up and running on a rpi for a couple weeks. 
Posting to a few sites like wow, etc. Running the standard report. Serves up 
the html just fine locally (I have a little ngnx instance running to serve it). 
I copy the html directory (var/www/html/weewx) to an aws s3 bucket to post the 
web page. In general it serves up, and all the data is there, stats, graphs, 
etc. The finer formatting is missing. The colored bar across the top. The 
day-week-month bold face, etc.
My guess is there is some bit of formatting I am missing, and not copying. It 
must be located elsewhere. 
 Anyone have any insights?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0fc18e22-646f-483d-9405-269d7372208e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Interceptor - Acurite Access and multi sensors - How to get the different sensor ID?

[Sylvain Martel]

No matter, I found the answer.  Acurite data is encrypted, so it can't be 
read, and only the WU data is read.  And since Acurite only allow one 
device to send data to WU...

*sigh*

An RDL receiver seems the way to go now, when I have some spare time...

On Sunday, 19 May 2019 19:22:57 UTC-4, Sylvain Martel wrote:
>
> Some more details:  I was reading the data through a RasberryPi with a 
> bridge. Since installing the Access, I had to redo the config to use the 
> Interceptor Observer driver and change the sensor map for the new labels.  
> But nowhere do I see a sensor ID anymore to differenctiate btw the 2 
> stations  when doing a debug=1
>
>
> On Sunday, 19 May 2019 19:15:05 UTC-4, Sylvain Martel wrote:
>>
>>
>> I have two 5-in-1 Acurite WS at home.  The smarthub died last week and I 
>> replaced it with the new Acurite Access, but I can't find the sensor ID 
>> info anymore.  Any tips on how to get that information?
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f7f36c02-18c1-4ddc-a09e-89675e2b6b08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Missing Midnight database update

[gjr80]

Hi,

My cron entries is 0,5,10,15,20,25,30,35,40,45,50,55,59.
>

Can you tell what these cron entries are? As far as I know WeeWX does not 
need cron entries when connected to a WS23xx.

May 19 00:01:21 localhost weewx[1076]: manager: Daily summary version is 2.0
> May 19 00:01:28 localhost weewx[1076]: engine: Launch of report thread 
> aborted: existing report thread still running
> May 19 00:01:49 localhost weewx[1076]: cheetahgenerator: Generated 18 
> files for report StandardReport in 28.29 seconds
>

This seems odd, the only previously logged report thread appeared to have 
completed normally well before. This may well be another symptom of the 
problem. Could you leave debug=1 and restart WeeWX and provide a log 
extract that shows the entire WeeWX startup through until the 2nd record is 
processed.

Gary

On Monday, 20 May 2019 06:40:58 UTC+10, Jd D wrote:
>
> Hi,
>
> station LaCrosse  ws2316
> weewx version 3.8.2
> hardware Raspberry Pi 
> NAME="Raspbian GNU/Linux"
> VERSION_ID="9"
> VERSION="9 (stretch)"
>
> I have noticed that the midnight updates to the database do not happen.  
> My cron entries is 0,5,10,15,20,25,30,35,40,45,50,55,59.  I added the 59 
> entry otherwise my report data stopped at 23:54 now I get report data at 
> 23:59. My station update interval is set for 1 minute which is supported by 
> the wx2316. Not a big deal but wanted to report this in case there is a fix 
> otherwise I will dig into the code myself and see what I can find. Not sure 
> if this is a software problem in weewx or the station itself.
>
> Here are the database timestamps. There is a jump of a 120 seconds instead 
> of 60 seconds. This is the only time in the day that jumps 120 seconds.
> "1558249380"
> *"1558249320"*
> *"1558249200"*
> "1558249140"
>
> Here is a snippet of the log. There is no record created at midnight.
>
> May 18 23:58:17 localhost weewx[1076]: reportengine: Report RSYNC skipped 
> due to report_timing setting
> *May 18 23:59:25 localhost weewx[1076]: manager: Added record 2019-05-18 
> 23:59:00 MST (1558249140) to database 'weewx.sdb'*
> *May 18 23:59:25 localhost weewx[1076]: manager: Added record 2019-05-18 
> 23:59:00 MST (1558249140) to daily summary in 'weewx.sdb'*
> May 18 23:59:25 localhost weewx[1076]: reportengine: Running reports for 
> latest time in the database.
> May 18 23:59:25 localhost weewx[1076]: reportengine: Running report 
> StandardReport
> May 18 23:59:25 localhost weewx[1076]: reportengine: Found configuration 
> file /etc/weewx/skins/Standard/skin.conf for report StandardReport
> May 18 23:59:25 localhost weewx[1076]: cheetahgenerator: using search list 
> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
> May 18 23:59:25 localhost weewx[1076]: manager: Daily summary version is 
> 2.0
> May 18 23:59:55 localhost weewx[1076]: cheetahgenerator: Generated 18 
> files for report StandardReport in 30.14 seconds
> May 18 23:59:55 localhost weewx[1076]: manager: Daily summary version is 
> 2.0
> May 18 23:59:56 localhost weewx[1076]: imagegenerator: Generated 12 images 
> for StandardReport in 1.39 seconds
> May 18 23:59:56 localhost weewx[1076]: copygenerator: copied 0 files to 
> /var/www/html/weewx
> May 18 23:59:56 localhost weewx[1076]: reportengine: Running report 
> SteelSeries
> May 18 23:59:56 localhost weewx[1076]: reportengine: Found configuration 
> file /etc/weewx/skins/ss/skin.conf for report SteelSeries
> May 18 23:59:56 localhost weewx[1076]: copygenerator: copied 0 files to 
> /var/www/html/weewx/ss
> May 18 23:59:56 localhost weewx[1076]: cheetahgenerator: using search list 
> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
> May 18 23:59:56 localhost weewx[1076]: manager: Daily summary version is 
> 2.0
> May 18 23:59:56 localhost weewx[1076]: cheetahgenerator: Generated 2 files 
> for report SteelSeries in 0.18 seconds
> May 18 23:59:56 localhost weewx[1076]: manager: Daily summary version is 
> 2.0
> May 18 23:59:58 localhost weewx[1076]: imagegenerator: Generated 11 images 
> for SteelSeries in 1.72 seconds
> May 18 23:59:58 localhost weewx[1076]: reportengine: Running report FTP
> May 18 23:59:58 localhost weewx[1076]: reportengine: Found configuration 
> file /etc/weewx/skins/Ftp/skin.conf for report FTP
> May 18 23:59:58 localhost weewx[1076]: ftpgenerator: FTP upload not 
> requested. Skipped.
> May 18 23:59:58 localhost weewx[1076]: reportengine: Running report RSYNC
> May 18 23:59:58 localhost weewx[1076]: reportengine: Found configuration 
> file /etc/weewx/skins/Rsync/skin.conf for report RSYNC
> May 18 23:59:58 localhost weewx[1076]: rsyncgenerator: rsync upload not 
> requested. Skipped.
> May 19 00:00:01 localhost 

Re: [weewx-user] Problem with display after some updates

[gjr80]

Ok, that fixed a few issues with clientraw.txt but now the parsing of 
clientraw.txt is failing when it hits fields containing a time. Again no 
spec for clientraw.txt to work from but we have found that any field 
representing a time needs to be in the format HH:MM:SS or HH:MM. At the 
moment your time fields are in the format HH:MM:SS XX where XX is AM or PM. 
This probably comes down to changes you may have made when troubleshooting 
(or perhaps something else). Rather than me asking 20 questions it is 
probably easier if you could post your [StdReport] stanza from weewx.conf - 
that will give me the [[wdClientrawReport]] and [[Defaults]] stanzas.

As an aside the parsing issues with clientraw.txt become fairly evident 
when you view your clientraw.txt in a parsed and tabulated format. There 
was (may still be - not sure) an online parser that you could give the url 
to your clientraw files and it would parse and display in tabular form. I 
created my own version and have plugged in your clientraw.txt data - I will 
leave it up for a while and you can view it here 
.
 
Have a look down the 'Value' column and you will soon see where the values 
do not match the description/units (field 134) onwards). You can then see 
why you are getting correct data in day and month but incorrect year - 
because year is after the initial parse error.

Gary

On Monday, 20 May 2019 02:16:07 UTC+10, Sean Garland wrote:
>
> Good morning!
>
> Thanks Gary for that insight.  I've noticed the behavior of the correct 
> into being overwritten by something in the past and didn't really 
> understand what was happening.  It's very clear now.
>
> What was really interesting is that although N/A was still present in the 
> clientraw.txt, the page was displaying correctly this morning.  I did add 
> the section you recommended, and it did replace the N/A's with "- -".  Now 
> when I use the Saratoga clientraw parser, things seem to be in all the 
> right places, and correct in value.  Doing a refresh however, shows 
> incorrect date now (after showing correct), but everything else looks 
> good.  
>
> Since the date should be M-d- (which shows for a second), and then 
> after refresh is m/d/-Y (negative)... I'm assuming now it's a simple(r) 
> data parsing issue.  
>
> Thank you!
> Sean
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e7a5108e-e9ef-459e-a65c-6fd1a12a5840%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Interceptor - Acurite Access and multi sensors - How to get the different sensor ID?

[Sylvain Martel]

Some more details:  I was reading the data through a RasberryPi with a 
bridge. Since installing the Access, I had to redo the config to use the 
Interceptor Observer driver and change the sensor map for the new labels.  
But nowhere do I see a sensor ID anymore to differenctiate btw the 2 
stations  when doing a debug=1


On Sunday, 19 May 2019 19:15:05 UTC-4, Sylvain Martel wrote:
>
>
> I have two 5-in-1 Acurite WS at home.  The smarthub died last week and I 
> replaced it with the new Acurite Access, but I can't find the sensor ID 
> info anymore.  Any tips on how to get that information?
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/019b3575-6d0a-4e23-9123-2b8224addc8b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Interceptor - Acurite Access and multi sensors - How to get the different sensor ID?

[Sylvain Martel]

I have two 5-in-1 Acurite WS at home.  The smarthub died last week and I 
replaced it with the new Acurite Access, but I can't find the sensor ID 
info anymore.  Any tips on how to get that information?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/929d2069-5fe8-400b-8312-9553e181eaa0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Add additional rain gauge via second data source

[gjr80]

Hi,

Perhaps you could give us some more details as to how the extra temperature 
data is being obtained/provided/added to WeeWX, happy to see code/data 
formats etc - code usually gives an unambiguous picture, descriptions are 
often open to interpretation. I am having a little difficulty understanding 
how the numeric data is always being received but not the units, but 
perhaps that will become clear once you provide some more detail.

Gary

On Monday, 20 May 2019 05:55:18 UTC+10, engolling wrote:
>
> Hello,
>
> me again :).
> Thank you for your last answer Thomas. Works fine.
>
> Now I have a new "thing" I do not understand.
> As discussed above I'm augmenting different data - also rain data to the 
> archive records as described in the customization guide.
>
> I also augment temperature signals and sometimes they are converted to 
> metric variables and sometimes not. The problem is the signal is already in 
> °C and should be in °C, but if it is converted it looks like this:
>
> 
> The database is mertric. If I get for example a temperature of 22.61°C 
> which should be imported into the database directly and it is most time. 
> But sometimes I get -5.21°C (which is the result of the Farenheit Celsius 
> conversion of 22.61°C).
>
> My Raspberry Pi has a bad WIFI internet connection and FTP often fails and 
> it seems to be related to this.
>
> Could this be a reason and do you know how to handle the conversion?
>
> Regards,
> engolling
>
> Am Dienstag, 7. Mai 2019 23:30:27 UTC+2 schrieb Thomas Keffer:
>>
>> Yes. That's certainly possible. 
>>
>> -tk
>>
>> On Tue, May 7, 2019 at 1:35 PM engolling  wrote:
>>
>>> Hello together,
>>>
>>> it's me again with hopefully a last question...
>>> As you know I'm augmenting some extra data from my service to the WeeWx 
>>> archive records. But if archive records are loaded of the stations logger 
>>> this data (which is in the future) is also augmented.
>>> Is it possible to read the timestamp of the archive record beeing saved 
>>> at the moment and then decide if data should be augmented or not?
>>> Im thinking of a code like this:
>>> if dateTime_AugmentedData - event.record[dateTime] < 300:
>>>--> augment_data
>>>
>>>
>>>
>>>
>>>
>>> Am Mittwoch, 3. April 2019 00:54:17 UTC+2 schrieb gjr80:

 Good that you have tracked down the issue. Running hardware record 
 generation on a Davis station has it advantages, though maybe not so 
 advantageous on emulated hardware.

 Regards plotting rain data from two sensors. The current WeeWX plot 
 engine will certainly allow you to plot two obs in a bar graph plot, 
 though 
 I expect the outcome will be one bar plotted over the top of the other. 
 Not 
 really what you are seeking. There is no option to plot the bars adjacent 
 to each other. It may be possible to modify the plot engine though I do 
 not 
 expect it would be a simple modification, the plot engine is fairly 
 rudimentary. You may need to use an external charting package which should 
 easily do what you want, though this too will not be a turn key solution 
 as 
 you will need to generate the necessary data for the package as well as 
 integrate it into your web page(s).

 Gary

 On Wednesday, 3 April 2019 03:44:09 UTC+10, engolling wrote:
>
> Hi Gary,
>
> again thanks for your extended reply.
> Meanwhile I added a lot of debugging code in the vantage driver and 
> the WeatherDuino code and was able to find out the reason what happened.
> Their is a buffer on the flash chip which is written before storing 
> the data in the flash page. And this buffer always had the outdated data 
> of 
> the page before in the last entries.
> This lead to this behaviour that the actual written page contained 
> wrong data, but the page before and the page after was pretty fine...
>
> It took me quite some time to find the system behind this error.
> I'm in touch with the developper of the WeatherDuino and this issue 
> will be fixed in the next firmware release so there will be full 
> compatibility with WeeWx.
>
> Now that erverything is working I have a last question - do you, or 
> anybody else, think it is possible to draw a bar graph having the rain 
> bars 
> of two sensors right beside?
> I did not find anything in the manual and if I define the diagramm 
> like in the line / dot graphs the two bars overlay, so that the bar of 
> the 
> second rain sensor is not visible, if it is a bit smaller.
>
> Thank you for all your replies.
>
> Regards,
> engolling
>
> Am Dienstag, 2. April 2019 16:01:11 UTC+2 schrieb gjr80:
>>
>> Sorry for being a little tardy in replying but I wanted to sit down 
>> and work my way through the Davis protocol. It seems everything is being 
>> followed, I 

[weewx-user] Re: Can't get interceptor to read data in sniff mode

[mwall]

On Sunday, May 19, 2019 at 8:52:51 AM UTC-4, Ray Pfaff wrote:
>
> I've been trying to get the 0.41 version of weewx interceptor working with 
> my Acurite access and haven't had any luck.
>

could you try using 0.45?

the device_type of wu-client was not added until 0.43

also, there were some significant pcap changes in 0.42

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ef676e71-d8b1-478f-bc58-e036c2e5e7b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Can't get interceptor to read data in sniff mode

[mwall]

On Sunday, May 19, 2019 at 5:44:55 PM UTC-4, Ray Pfaff wrote:
>
> Am I missing something?  Both of those apply to the bridge, not the 
> access.  I do have access to a server that receives my data as 
> myacurite.com (and for that matter wunderground.com) both receive data 
> from it.
>

sorry about that, i missed the 'access' bit.

with the device type as wu-client, could you set debug=1 in weewx.conf then 
post the log output from the time weewx start until the first reporting 
cycle?

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9277010a-a165-41c7-9d19-97081511d4ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Can't get interceptor to read data in sniff mode

[Ray Pfaff]

Am I missing something?  Both of those apply to the bridge, not the 
access.  I do have access to a server that receives my data as 
myacurite.com (and for that matter wunderground.com) both receive data from 
it.

On Sunday, May 19, 2019 at 8:52:51 AM UTC-4, Ray Pfaff wrote:
>
> I've been trying to get the 0.41 version of weewx interceptor working with 
> my Acurite access and haven't had any luck.  I can read packets to 
> wunderground if I do a tcpdump and I've even written a python script to 
> extract the data and put it in a database.  But when I run interceptor 
> stand alone, I get nothing on screen or in the syslog.  The relevant parts 
> of weewx.conf  is so:
> # 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 = Interceptor
> [Interceptor]
> # This section is for the network traffic interceptor driver.
>  
> # The driver to use:
> driver = user.interceptor
>  
> # Specify the hardware device to capture.  Options include:
> #   acurite-bridge - acurite internet bridge
> #   observer - fine offset WH2600/HP1000/HP1003, aka 'observer'
> #   lw30x - oregon scientific LW301/LW302
> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
> device_type = wu-client
> port=80
> mode=sniff
> iface= wlp2s0
> pcap_filter= src  and dst port 80
>
> wu
> I've tried 'acurite-device' and 'wu-client' for the device type both in 
> the configuration and on the command line.  --deivce='wu-client' isn't a 
> valid input on the command line.   When I run the interceptor:
> ~/Downloads$ sudo PYTHONPATH=/usr/share/weewx python 
> /usr/share/weewx/user/interceptor.py --mode=sniff --iface=wlp2s0 
> --filter=" and port 80"
> I get nothing.
>
> However, if I do this:
> ~/Downloads$ sudo tcpdump -U -i wlp2s0 src  and port 80 
> | ./weather.py
> I get:
> ['2019-05-19 08:03:11', '30.04', '99', '66.2', '0', '225', '0', '45', 
> '65.9', '0.02', '0.00 ']
> ['2019-05-19 08:13:23', '30.04', '96', '67.6', '1', '203', '2', '203', 
> '66.4', '0.02', '0.00 ']
> ['2019-05-19 08:32:53', '30.05', '95', '68.0', '0', '203', '0', '203', 
> '66.5', '0.02', '0.00 ']
>
>
>
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/dd9d09dc-d5e4-4c08-a59f-72f1993f9092%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Can't get interceptor to read data in sniff mode

[mwall]

the wiki page has been updated to reflect the changes at acurite:

https://github.com/weewx/weewx/wiki/acuritebridge

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/fd19ea3c-8d3e-49f8-9c40-f2bfc0d7cfc3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Missing Midnight database update

[Jd D]

Hi,

station LaCrosse  ws2316
weewx version 3.8.2
hardware Raspberry Pi 
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"

I have noticed that the midnight updates to the database do not happen.  My 
cron entries is 0,5,10,15,20,25,30,35,40,45,50,55,59.  I added the 59 entry 
otherwise my report data stopped at 23:54 now I get report data at 23:59. 
My station update interval is set for 1 minute which is supported by the 
wx2316. Not a big deal but wanted to report this in case there is a fix 
otherwise I will dig into the code myself and see what I can find. Not sure 
if this is a software problem in weewx or the station itself.

Here are the database timestamps. There is a jump of a 120 seconds instead 
of 60 seconds. This is the only time in the day that jumps 120 seconds.
"1558249380"
*"1558249320"*
*"1558249200"*
"1558249140"

Here is a snippet of the log. There is no record created at midnight.

May 18 23:58:17 localhost weewx[1076]: reportengine: Report RSYNC skipped 
due to report_timing setting
*May 18 23:59:25 localhost weewx[1076]: manager: Added record 2019-05-18 
23:59:00 MST (1558249140) to database 'weewx.sdb'*
*May 18 23:59:25 localhost weewx[1076]: manager: Added record 2019-05-18 
23:59:00 MST (1558249140) to daily summary in 'weewx.sdb'*
May 18 23:59:25 localhost weewx[1076]: reportengine: Running reports for 
latest time in the database.
May 18 23:59:25 localhost weewx[1076]: reportengine: Running report 
StandardReport
May 18 23:59:25 localhost weewx[1076]: reportengine: Found configuration 
file /etc/weewx/skins/Standard/skin.conf for report StandardReport
May 18 23:59:25 localhost weewx[1076]: cheetahgenerator: using search list 
['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
May 18 23:59:25 localhost weewx[1076]: manager: Daily summary version is 2.0
May 18 23:59:55 localhost weewx[1076]: cheetahgenerator: Generated 18 files 
for report StandardReport in 30.14 seconds
May 18 23:59:55 localhost weewx[1076]: manager: Daily summary version is 2.0
May 18 23:59:56 localhost weewx[1076]: imagegenerator: Generated 12 images 
for StandardReport in 1.39 seconds
May 18 23:59:56 localhost weewx[1076]: copygenerator: copied 0 files to 
/var/www/html/weewx
May 18 23:59:56 localhost weewx[1076]: reportengine: Running report 
SteelSeries
May 18 23:59:56 localhost weewx[1076]: reportengine: Found configuration 
file /etc/weewx/skins/ss/skin.conf for report SteelSeries
May 18 23:59:56 localhost weewx[1076]: copygenerator: copied 0 files to 
/var/www/html/weewx/ss
May 18 23:59:56 localhost weewx[1076]: cheetahgenerator: using search list 
['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
May 18 23:59:56 localhost weewx[1076]: manager: Daily summary version is 2.0
May 18 23:59:56 localhost weewx[1076]: cheetahgenerator: Generated 2 files 
for report SteelSeries in 0.18 seconds
May 18 23:59:56 localhost weewx[1076]: manager: Daily summary version is 2.0
May 18 23:59:58 localhost weewx[1076]: imagegenerator: Generated 11 images 
for SteelSeries in 1.72 seconds
May 18 23:59:58 localhost weewx[1076]: reportengine: Running report FTP
May 18 23:59:58 localhost weewx[1076]: reportengine: Found configuration 
file /etc/weewx/skins/Ftp/skin.conf for report FTP
May 18 23:59:58 localhost weewx[1076]: ftpgenerator: FTP upload not 
requested. Skipped.
May 18 23:59:58 localhost weewx[1076]: reportengine: Running report RSYNC
May 18 23:59:58 localhost weewx[1076]: reportengine: Found configuration 
file /etc/weewx/skins/Rsync/skin.conf for report RSYNC
May 18 23:59:58 localhost weewx[1076]: rsyncgenerator: rsync upload not 
requested. Skipped.
May 19 00:00:01 localhost CRON[25282]: (root) CMD 
(/usr/local/HomeSeer/register_with_find.sh)
*May 19 00:01:20 localhost weewx[1076]: manager: Added record 2019-05-19 
00:00:00 MST (1558249200) to database 'weewx.sdb'*
*May 19 00:01:20 localhost weewx[1076]: manager: Added record 2019-05-19 
00:00:00 MST (1558249200) to daily summary in 'weewx.sdb'*
May 19 00:01:21 localhost weewx[1076]: reportengine: Running reports for 
latest time in the database.
May 19 00:01:21 localhost weewx[1076]: reportengine: Running report 
StandardReport
May 19 00:01:21 localhost weewx[1076]: reportengine: Found configuration 
file /etc/weewx/skins/Standard/skin.conf for report StandardReport
May 19 00:01:21 localhost weewx[1076]: cheetahgenerator: using search list 
['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
May 19 00:01:21 localhost weewx[1076]: manager: Daily summary version is 2.0
May 19 00:01:28 localhost 

Re: [weewx-user] Re: Add additional rain gauge via second data source

[engolling]

Hello,

me again :).
Thank you for your last answer Thomas. Works fine.

Now I have a new "thing" I do not understand.
As discussed above I'm augmenting different data - also rain data to the 
archive records as described in the customization guide.

I also augment temperature signals and sometimes they are converted to 
metric variables and sometimes not. The problem is the signal is already in 
°C and should be in °C, but if it is converted it looks like this:


The database is mertric. If I get for example a temperature of 22.61°C 
which should be imported into the database directly and it is most time. 
But sometimes I get -5.21°C (which is the result of the Farenheit Celsius 
conversion of 22.61°C).

My Raspberry Pi has a bad WIFI internet connection and FTP often fails and 
it seems to be related to this.

Could this be a reason and do you know how to handle the conversion?

Regards,
engolling

Am Dienstag, 7. Mai 2019 23:30:27 UTC+2 schrieb Thomas Keffer:
>
> Yes. That's certainly possible. 
>
> -tk
>
> On Tue, May 7, 2019 at 1:35 PM engolling  > wrote:
>
>> Hello together,
>>
>> it's me again with hopefully a last question...
>> As you know I'm augmenting some extra data from my service to the WeeWx 
>> archive records. But if archive records are loaded of the stations logger 
>> this data (which is in the future) is also augmented.
>> Is it possible to read the timestamp of the archive record beeing saved 
>> at the moment and then decide if data should be augmented or not?
>> Im thinking of a code like this:
>> if dateTime_AugmentedData - event.record[dateTime] < 300:
>>--> augment_data
>>
>>
>>
>>
>>
>> Am Mittwoch, 3. April 2019 00:54:17 UTC+2 schrieb gjr80:
>>>
>>> Good that you have tracked down the issue. Running hardware record 
>>> generation on a Davis station has it advantages, though maybe not so 
>>> advantageous on emulated hardware.
>>>
>>> Regards plotting rain data from two sensors. The current WeeWX plot 
>>> engine will certainly allow you to plot two obs in a bar graph plot, though 
>>> I expect the outcome will be one bar plotted over the top of the other. Not 
>>> really what you are seeking. There is no option to plot the bars adjacent 
>>> to each other. It may be possible to modify the plot engine though I do not 
>>> expect it would be a simple modification, the plot engine is fairly 
>>> rudimentary. You may need to use an external charting package which should 
>>> easily do what you want, though this too will not be a turn key solution as 
>>> you will need to generate the necessary data for the package as well as 
>>> integrate it into your web page(s).
>>>
>>> Gary
>>>
>>> On Wednesday, 3 April 2019 03:44:09 UTC+10, engolling wrote:

 Hi Gary,

 again thanks for your extended reply.
 Meanwhile I added a lot of debugging code in the vantage driver and the 
 WeatherDuino code and was able to find out the reason what happened.
 Their is a buffer on the flash chip which is written before storing the 
 data in the flash page. And this buffer always had the outdated data of 
 the 
 page before in the last entries.
 This lead to this behaviour that the actual written page contained 
 wrong data, but the page before and the page after was pretty fine...

 It took me quite some time to find the system behind this error.
 I'm in touch with the developper of the WeatherDuino and this issue 
 will be fixed in the next firmware release so there will be full 
 compatibility with WeeWx.

 Now that erverything is working I have a last question - do you, or 
 anybody else, think it is possible to draw a bar graph having the rain 
 bars 
 of two sensors right beside?
 I did not find anything in the manual and if I define the diagramm like 
 in the line / dot graphs the two bars overlay, so that the bar of the 
 second rain sensor is not visible, if it is a bit smaller.

 Thank you for all your replies.

 Regards,
 engolling

 Am Dienstag, 2. April 2019 16:01:11 UTC+2 schrieb gjr80:
>
> Sorry for being a little tardy in replying but I wanted to sit down 
> and work my way through the Davis protocol. It seems everything is being 
> followed, I do not know if the lack of a final acknowledgement is 
> critical 
> or not but what I would say is that the Davis driver works with real 
> Davis 
> hardware without issue.
>
> One thing I did wonder, the DMPAFT command downloads all archive 
> records after a given timestamp. Archive records are downloaded a page at 
> a 
> time and a page contains 5 archive records. When we look at the earlier 
> log 
> extracts you have provided there seems to be groups of 5 archive records 
> being processed (1 page?) but of course all that are already in the 
> archive 
> are rejected, for example:
>
> 

Re: [weewx-user] Problem with display after some updates

[Sean Garland]

Good morning!

Thanks Gary for that insight.  I've noticed the behavior of the correct 
into being overwritten by something in the past and didn't really 
understand what was happening.  It's very clear now.

What was really interesting is that although N/A was still present in the 
clientraw.txt, the page was displaying correctly this morning.  I did add 
the section you recommended, and it did replace the N/A's with "- -".  Now 
when I use the Saratoga clientraw parser, things seem to be in all the 
right places, and correct in value.  Doing a refresh however, shows 
incorrect date now (after showing correct), but everything else looks 
good.  

Since the date should be M-d- (which shows for a second), and then 
after refresh is m/d/-Y (negative)... I'm assuming now it's a simple(r) 
data parsing issue.  

Thank you!
Sean

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/68eacb6c-7219-4c76-bf92-92a5de169580%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Fresh install of weewx 3.9.1 with WMR300A on RPI, Non-positive value for record field 'interval': 0.0

[Leon Shaner]

Yeah, good catch.

I expect it was running the old wmr300.pyc since the html one named wmr300.py 
was invalid.

Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPhone)

> On May 19, 2019, at 7:36 AM, gjr80  wrote:
> 
> Hi, 
> 
> If you are downloading a source file from github you need to get the raw 
> source otherwise you end up with the github htmml used to display the file. 
> Try using the following commands to download and install wmr300.py:
> 
> $ wget -P /tmp 
> https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/wmr300.py
> $ sudo cp /tmp/wmr300.py /usr/share/weewx/weewx/drivers/wmr300.py
> 
> Then restart WeeWX.
> 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/8281aa25-d717-4df6-8f61-7f4ca8ef4564%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8600EB2A-E8FD-45A4-80B8-49E5D9B60DC0%40isylum.org.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Can't get interceptor to read data in sniff mode

[RobbH]

See this message and the rest of the thread:

https://groups.google.com/d/msg/weewx-user/0e2E3F7EG7Y/mVv7oUZ1BgAJ



On Sunday, May 19, 2019 at 8:52:51 AM UTC-4, Ray Pfaff wrote:
>
> I've been trying to get the 0.41 version of weewx interceptor working with 
> my Acurite access and haven't had any luck.  I can read packets to 
> wunderground if I do a tcpdump and I've even written a python script to 
> extract the data and put it in a database.  But when I run interceptor 
> stand alone, I get nothing on screen or in the syslog.  The relevant parts 
> of weewx.conf  is so:
> # 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 = Interceptor
> [Interceptor]
> # This section is for the network traffic interceptor driver.
>  
> # The driver to use:
> driver = user.interceptor
>  
> # Specify the hardware device to capture.  Options include:
> #   acurite-bridge - acurite internet bridge
> #   observer - fine offset WH2600/HP1000/HP1003, aka 'observer'
> #   lw30x - oregon scientific LW301/LW302
> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
> device_type = wu-client
> port=80
> mode=sniff
> iface= wlp2s0
> pcap_filter= src  and dst port 80
>
> wu
> I've tried 'acurite-device' and 'wu-client' for the device type both in 
> the configuration and on the command line.  --deivce='wu-client' isn't a 
> valid input on the command line.   When I run the interceptor:
> ~/Downloads$ sudo PYTHONPATH=/usr/share/weewx python 
> /usr/share/weewx/user/interceptor.py --mode=sniff --iface=wlp2s0 
> --filter=" and port 80"
> I get nothing.
>
> However, if I do this:
> ~/Downloads$ sudo tcpdump -U -i wlp2s0 src  and port 80 
> | ./weather.py
> I get:
> ['2019-05-19 08:03:11', '30.04', '99', '66.2', '0', '225', '0', '45', 
> '65.9', '0.02', '0.00 ']
> ['2019-05-19 08:13:23', '30.04', '96', '67.6', '1', '203', '2', '203', 
> '66.4', '0.02', '0.00 ']
> ['2019-05-19 08:32:53', '30.05', '95', '68.0', '0', '203', '0', '203', 
> '66.5', '0.02', '0.00 ']
>
>
>
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d7af0342-4ca1-4bbf-a34d-e14ca1cdda2d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Can't get interceptor to read data in sniff mode

[Ray Pfaff]

I've been trying to get the 0.41 version of weewx interceptor working with 
my Acurite access and haven't had any luck.  I can read packets to 
wunderground if I do a tcpdump and I've even written a python script to 
extract the data and put it in a database.  But when I run interceptor 
stand alone, I get nothing on screen or in the syslog.  The relevant parts 
of weewx.conf  is so:
# 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 = Interceptor
[Interceptor]
# This section is for the network traffic interceptor driver.
 
# The driver to use:
driver = user.interceptor
 
# Specify the hardware device to capture.  Options include:
#   acurite-bridge - acurite internet bridge
#   observer - fine offset WH2600/HP1000/HP1003, aka 'observer'
#   lw30x - oregon scientific LW301/LW302
#   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
device_type = wu-client
port=80
mode=sniff
iface= wlp2s0
pcap_filter= src  and dst port 80

wu
I've tried 'acurite-device' and 'wu-client' for the device type both in the 
configuration and on the command line.  --deivce='wu-client' isn't a valid 
input on the command line.   When I run the interceptor:
~/Downloads$ sudo PYTHONPATH=/usr/share/weewx python 
/usr/share/weewx/user/interceptor.py --mode=sniff --iface=wlp2s0 
--filter=" and port 80"
I get nothing.

However, if I do this:
~/Downloads$ sudo tcpdump -U -i wlp2s0 src  and port 80 
| ./weather.py
I get:
['2019-05-19 08:03:11', '30.04', '99', '66.2', '0', '225', '0', '45', 
'65.9', '0.02', '0.00 ']
['2019-05-19 08:13:23', '30.04', '96', '67.6', '1', '203', '2', '203', 
'66.4', '0.02', '0.00 ']
['2019-05-19 08:32:53', '30.05', '95', '68.0', '0', '203', '0', '203', 
'66.5', '0.02', '0.00 ']





-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e410aaf7-c516-4d86-824f-923301360ca1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Fresh install of weewx 3.9.1 with WMR300A on RPI, Non-positive value for record field 'interval': 0.0

[gjr80]

Hi, 

If you are downloading a source file from github you need to get the raw source 
otherwise you end up with the github htmml used to display the file. Try using 
the following commands to download and install wmr300.py:

$ wget -P /tmp 
https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/wmr300.py
$ sudo cp /tmp/wmr300.py /usr/share/weewx/weewx/drivers/wmr300.py

Then restart WeeWX.

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8281aa25-d717-4df6-8f61-7f4ca8ef4564%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Fresh install of weewx 3.9.1 with WMR300A on RPI, Non-positive value for record field 'interval': 0.0

[Miguel Angel Peña Morales]

New thing, I restarted the rpi and now this is the log:

May 19 11:17:05 raspberrypi systemd[1]: Starting LSB: weewx weather 
system...
May 19 11:17:05 raspberrypi weewx[982]: engine: Initializing weewx version 
3.9.1
May 19 11:17:05 raspberrypi weewx[982]: engine: Using Python 2.7.13 
(default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
May 19 11:17:05 raspberrypi weewx[982]: engine: Platform 
Linux-4.19.42-v7+-armv7l-with-debian-9.9
May 19 11:17:05 raspberrypi weewx[982]: engine: Locale is 'es_ES.UTF-8'
May 19 11:17:05 raspberrypi weewx[982]: engine: pid file is 
/var/run/weewx.pid
May 19 11:17:06 raspberrypi weewx[971]: Starting weewx weather system: 
weewx.
May 19 11:17:06 raspberrypi systemd[1]: Started LSB: weewx weather system.
May 19 11:17:06 raspberrypi weewx[986]: engine: Using configuration file 
/etc/weewx/weewx.conf
May 19 11:17:06 raspberrypi weewx[986]: engine: Loading station type WMR300 
(weewx.drivers.wmr300)
May 19 11:17:06 raspberrypi weewx[986]: engine: Caught unrecoverable 
exception in engine:
May 19 11:17:06 raspberrypi weewx[986]:   invalid syntax 
(wmr300.py, line 7)
May 19 11:17:06 raspberrypi weewx[986]:   Traceback (most recent 
call last):
May 19 11:17:06 raspberrypi weewx[986]: File 
"/usr/share/weewx/weewx/engine.py", line 884, in main
May 19 11:17:06 raspberrypi weewx[986]:   engine = 
engine_class(config_dict)
May 19 11:17:06 raspberrypi weewx[986]: File 
"/usr/share/weewx/weewx/engine.py", line 72, in __init__
May 19 11:17:06 raspberrypi weewx[986]:   
self.setupStation(config_dict)
May 19 11:17:06 raspberrypi weewx[986]: File 
"/usr/share/weewx/weewx/engine.py", line 96, in setupStation
May 19 11:17:06 raspberrypi weewx[986]:   __import__(driver)
May 19 11:17:06 raspberrypi weewx[986]: File 
"/usr/share/weewx/weewx/drivers/wmr300.py", line 7
May 19 11:17:06 raspberrypi weewx[986]:   
May 19 11:17:06 raspberrypi weewx[986]:   ^
May 19 11:17:06 raspberrypi weewx[986]:   SyntaxError: invalid 
syntax
May 19 11:17:06 raspberrypi weewx[986]:   Exiting.




El domingo, 19 de mayo de 2019, 12:56:27 (UTC+2), Miguel Angel Peña Morales 
escribió:
>
> Hello again, no luck. I even tried to reinstall from purge and deleting 
> all the folders of weewx and nothing new...
>
> The thing I'm just seeing is the version of  the wmr300 driver in my old 
> log and this log is the same. 19rc6. Shouldn't be that different?
>
> Regards and thanks.
>
> New log.
>
> May 19 10:43:12 raspberrypi weewx[1048]: Stopping weewx weather system: 
> weewx not running
> May 19 10:43:12 raspberrypi systemd[1]: Stopped LSB: weewx weather system.
> May 19 10:43:13 raspberrypi systemd[1]: Reloading.
> May 19 10:43:18 raspberrypi systemd[1]: Reloading.
> May 19 10:43:21 raspberrypi dbus[373]: [system] Activating via systemd: 
> service name='org.freedesktop.PackageKit' unit='packagekit.service'
> May 19 10:43:21 raspberrypi systemd[1]: Starting PackageKit Daemon...
> May 19 10:43:21 raspberrypi PackageKit: daemon start
> May 19 10:43:21 raspberrypi dbus[373]: [system] Successfully activated 
> service 'org.freedesktop.PackageKit'
> May 19 10:43:21 raspberrypi systemd[1]: Started PackageKit Daemon.
> May 19 10:45:15 raspberrypi systemd[1]: Reloading.
> May 19 10:45:16 raspberrypi systemd[1]: Reloading.
> May 19 10:45:17 raspberrypi systemd[1]: Starting LSB: weewx weather 
> system...
> May 19 10:45:17 raspberrypi weewx[1314]: engine: Initializing weewx 
> version 3.9.1
> May 19 10:45:17 raspberrypi weewx[1314]: engine: Using Python 2.7.13 
> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
> May 19 10:45:17 raspberrypi weewx[1314]: engine: Platform 
> Linux-4.14.98-v7+-armv7l-with-debian-9.9
> May 19 10:45:17 raspberrypi weewx[1314]: engine: Locale is 'es_ES.UTF-8'
> May 19 10:45:17 raspberrypi weewx[1314]: engine: pid file is 
> /var/run/weewx.pid
> May 19 10:45:18 raspberrypi weewx[1303]: Starting weewx weather system: 
> weewx.
> May 19 10:45:18 raspberrypi systemd[1]: Started LSB: weewx weather system.
> May 19 10:45:18 raspberrypi weewx[1318]: engine: Using configuration file 
> /etc/weewx/weewx.conf
> May 19 10:45:18 raspberrypi weewx[1318]: engine: Loading station type 
> WMR300 (weewx.drivers.wmr300)
> May 19 10:45:18 raspberrypi weewx[1318]: wmr300: driver version is 0.19rc6
> May 19 10:45:18 raspberrypi weewx[1318]: wmr300: usb info: 
> pyusb_version=1.0.0
> May 19 10:45:18 raspberrypi weewx[1318]: wmr300: sensor map is 
> {'outHumidity': 'humidity_1', 'extraDewpoint6': 'dewpoint_7', 'windchill': 
> 'windchill', 'extraDewpoint4': 'dewpoint_5', 'rainRate': 'rain_rate', 
> 'heatindex': 'heatindex_1', 'inTemp': 'temperature_0', 'windGustDir': 
> 'wind_gust_dir', 'extraDewpoint2': 'dewpoint_3', 'extraDewpoint3': 
> 'dewpoint_4', 'extraDewpoint1': 'dewpoint_2', 'barometer': 'barometer', 
> 'extraDewpoint7': 'dewpoint_8', 'dewpoint': 'dewpoint_1', 

Re: [weewx-user] Re: Fresh install of weewx 3.9.1 with WMR300A on RPI, Non-positive value for record field 'interval': 0.0

[Miguel Angel Peña Morales]

Hello again, no luck. I even tried to reinstall from purge and deleting all 
the folders of weewx and nothing new...

The thing I'm just seeing is the version of  the wmr300 driver in my old 
log and this log is the same. 19rc6. Shouldn't be that different?

Regards and thanks.

New log.

May 19 10:43:12 raspberrypi weewx[1048]: Stopping weewx weather system: 
weewx not running
May 19 10:43:12 raspberrypi systemd[1]: Stopped LSB: weewx weather system.
May 19 10:43:13 raspberrypi systemd[1]: Reloading.
May 19 10:43:18 raspberrypi systemd[1]: Reloading.
May 19 10:43:21 raspberrypi dbus[373]: [system] Activating via systemd: 
service name='org.freedesktop.PackageKit' unit='packagekit.service'
May 19 10:43:21 raspberrypi systemd[1]: Starting PackageKit Daemon...
May 19 10:43:21 raspberrypi PackageKit: daemon start
May 19 10:43:21 raspberrypi dbus[373]: [system] Successfully activated 
service 'org.freedesktop.PackageKit'
May 19 10:43:21 raspberrypi systemd[1]: Started PackageKit Daemon.
May 19 10:45:15 raspberrypi systemd[1]: Reloading.
May 19 10:45:16 raspberrypi systemd[1]: Reloading.
May 19 10:45:17 raspberrypi systemd[1]: Starting LSB: weewx weather 
system...
May 19 10:45:17 raspberrypi weewx[1314]: engine: Initializing weewx version 
3.9.1
May 19 10:45:17 raspberrypi weewx[1314]: engine: Using Python 2.7.13 
(default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
May 19 10:45:17 raspberrypi weewx[1314]: engine: Platform 
Linux-4.14.98-v7+-armv7l-with-debian-9.9
May 19 10:45:17 raspberrypi weewx[1314]: engine: Locale is 'es_ES.UTF-8'
May 19 10:45:17 raspberrypi weewx[1314]: engine: pid file is 
/var/run/weewx.pid
May 19 10:45:18 raspberrypi weewx[1303]: Starting weewx weather system: 
weewx.
May 19 10:45:18 raspberrypi systemd[1]: Started LSB: weewx weather system.
May 19 10:45:18 raspberrypi weewx[1318]: engine: Using configuration file 
/etc/weewx/weewx.conf
May 19 10:45:18 raspberrypi weewx[1318]: engine: Loading station type 
WMR300 (weewx.drivers.wmr300)
May 19 10:45:18 raspberrypi weewx[1318]: wmr300: driver version is 0.19rc6
May 19 10:45:18 raspberrypi weewx[1318]: wmr300: usb info: 
pyusb_version=1.0.0
May 19 10:45:18 raspberrypi weewx[1318]: wmr300: sensor map is 
{'outHumidity': 'humidity_1', 'extraDewpoint6': 'dewpoint_7', 'windchill': 
'windchill', 'extraDewpoint4': 'dewpoint_5', 'rainRate': 'rain_rate', 
'heatindex': 'heatindex_1', 'inTemp': 'temperature_0', 'windGustDir': 
'wind_gust_dir', 'extraDewpoint2': 'dewpoint_3', 'extraDewpoint3': 
'dewpoint_4', 'extraDewpoint1': 'dewpoint_2', 'barometer': 'barometer', 
'extraDewpoint7': 'dewpoint_8', 'dewpoint': 'dewpoint_1', 'extraDewpoint5': 
'dewpoint_6', 'extraHumid6': 'humidity_7', 'pressure': 'pressure', 
'extraHumid4': 'humidity_5', 'extraHumid5': 'humidity_6', 'extraHumid2': 
'humidity_3', 'extraHumid3': 'humidity_4', 'extraHumid1': 'humidity_2', 
'extraTemp6': 'temperature_7', 'extraTemp7': 'temperature_8', 'extraTemp4': 
'temperature_5', 'extraTemp5': 'temperature_6', 'extraTemp2': 
'temperature_3', 'extraTemp3': 'temperature_4', 'extraTemp1': 
'temperature_2', 'extraHeatindex3': 'heatindex_4', 'extraHeatindex2': 
'heatindex_3', 'extraHeatindex1': 'heatindex_2', 'extraHeatindex7': 
'heatindex_8', 'extraHeatindex6': 'heatindex_7', 'extraHeatindex5': 
'heatindex_6', 'extraHumid7': 'humidity_8', 'extraHeatindex4': 
'heatindex_5', 'windDir': 'wind_dir', 'outTemp': 'temperature_1', 
'windSpeed': 'wind_avg', 'inHumidity': 'humidity_0', 'windGust': 
'wind_gust'}
May 19 10:45:18 raspberrypi weewx[1318]: wmr300: history limit is 20%
May 19 10:45:18 raspberrypi kernel: [  415.383352] usb 1-1.4: reset 
full-speed USB device number 8 using dwc_otg
May 19 10:45:18 raspberrypi systemd[1]: Reloading.
May 19 10:45:18 raspberrypi weewx[1318]: wmr300: communication established: 
{'station_model': 'A004', 'latest_index': 32736, 'station_type': 'WMR300', 
'mystery1': 44, 'mystery0': 73, 'history_cleared': False, 'magic1': 139, 
'magic0': 136, 'packet_type': 87}
May 19 10:45:18 raspberrypi weewx[1318]: engine: StdConvert target unit is 
0x1
May 19 10:45:18 raspberrypi weewx[1318]: wxcalculate: The following values 
will be calculated: barometer=prefer_hardware, windchill=hardware, 
dewpoint=software, appTemp=prefer_hardware, rainRate=hardware, 
windrun=prefer_hardware, heatindex=hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
May 19 10:45:18 raspberrypi weewx[1318]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
May 19 10:45:18 raspberrypi weewx[1318]: engine: Archive will use data 
binding wx_binding
May 19 10:45:18 raspberrypi weewx[1318]: engine: Record generation will be 
attempted in 'hardware'
May 19 10:45:18 raspberrypi weewx[1318]: engine: Using archive interval of 
300 seconds (specified in weewx configuration)
May 19 10:45:18 raspberrypi 

Re: [weewx-user] Re: upgrade from 3.8.2 to 3.9.1 failure

[Ian Prescott]

Thanks Mathew
The code change has been done
database checked first then purged.appears to have
done the trick.
fyi.just a couple of rather old entries

sqlite> select dateTime, datetime(dateTime,'unixepoch','localtime'),
interval from archive WHERE interval <= 0 order by dateTime;

1508786399|2017-10-24 05:19:59|0

1508935799|2017-10-25 22:49:59|0

sqlite>




On Sun, 19 May 2019 at 19:22, mwall  wrote:

> you must also purge your database of any non-positive values for
> 'interval'.  as tom posted in this thread:
>
> https://groups.google.com/d/msg/weewx-user/69RvQnD_OQc/ZyF0_jZqAwAJ
>
>
> You may have to install the tool sqlite3, if you haven't already:
> *sudo apt-get install sqlite3*
>
> Then delete any non-positive values:
> *sudo sqlite3 /var/lib/weewx/weewx.sdb*
> sqlite> *delete from archive where interval <= 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/739d93c6-616f-4db4-8458-46914e6c51b3%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAN84nRvixFfC9cmADoiCPOGdJ0jYF2VUC5XWi3xGPk9u9vOQ-A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Belchertown skin for weewx now available!

[Mike Harold Chan]

can you teach me how to edit these skins in raspberry and what kind of
software to edit the skins with .htmpl extensions so that anytime I can
changes the windy map into gif maps or changing link templates? thanks

On Sun, May 19, 2019 at 9:54 AM WILWetter25 
wrote:

> Hey everyone,
>
> I have a problem with the main-page of the skin: Forecast, Earth-Quakes
> and Graphs aren't loading since a week.
>
> My Website: http://www.mosel-wetter.com/
>
> Does anyone know a solution?
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/3eb39651-49af-4f72-8a93-834f387f8d8d%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAKjfRK%3D5buK7epWvstTXSymuRHVO7MVO8cX56cSwmyvpuwrxDw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: upgrade from 3.8.2 to 3.9.1 failure

[mwall]

you must also purge your database of any non-positive values for 
'interval'.  as tom posted in this thread:

https://groups.google.com/d/msg/weewx-user/69RvQnD_OQc/ZyF0_jZqAwAJ


You may have to install the tool sqlite3, if you haven't already:
*sudo apt-get install sqlite3*

Then delete any non-positive values:
*sudo sqlite3 /var/lib/weewx/weewx.sdb*
sqlite> *delete from archive where interval <= 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/739d93c6-616f-4db4-8458-46914e6c51b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: upgrade from 3.8.2 to 3.9.1 failure

[mwall]

ian,

please try the following modification.  in the file fousb.py, change line 
1321 from this:

while dts > dt and count < num_rec:
raw_data = self.get_raw_data(ptr)
data = self.decode(raw_data)
if data['delay'] is None or data['delay'] > 30:
logerr('invalid data in get_records at 0x%04x, %s' %
   (ptr, dts.isoformat()))
dts -= 
datetime.timedelta(minutes=fixed_block['read_period'])

to this:

while dts > dt and count < num_rec:
raw_data = self.get_raw_data(ptr)
data = self.decode(raw_data)
if data['delay'] is None or data['delay'] < 1 or 
data['delay'] > 30:
logerr('invalid data in get_records at 0x%04x, %s' %
   (ptr, dts.isoformat()))
dts -= 
datetime.timedelta(minutes=fixed_block['read_period'])

then restart weewx

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/086a4699-1005-41b3-845b-85fd9586d1c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.