[weewx-user] Re: getting weewx[12196]: cheetahgenerator: Skipping template index.html.tmpl: cannot find start time

[gjr80]

Hi,

Looks like another case of corrupt station memory, though a little 
different to most as you don't seem to have any recrods in your archive. I 
would try the steps under Corrupt staion memory 
 in the User's 
Guide. Note the comment about dumping the logger memory before clearing the 
logger memory, dumping the logger memory may help minimse any data loss.

Gary

On Friday, 10 January 2020 13:30:00 UTC+10, Ted Frohling wrote:
>
> Also no new data from the VantagePro2 is being updated.
>
> Weewx stopped updating a few days ago.  I have verified it's producing 
> some output by running weewxd without daemon mode.
> Here are a few slightly older records:
>
>
> LOOP:   2020-01-09 18:36:16 MST (1578620176) appTemp: 51.7532829608, 
> barometer: 29.827, beaufort: 0, cloudbase: 8949.86520147, 
> consBatteryVoltage: 4.66, dateTime: 1578620176, dayET: 0.0, dayRain: 0.0, 
> dewpoint: 28.5645931135, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
> extraAlarm8: 0, forecastIcon: 6, forecastRule: 9, heatindex: 55.8, humidex: 
> 55.8, inDewpoint: 33.5667167944, inHumidity: 22.0, insideAlarm: 0, inTemp: 
> 75.0, leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain: 0.0, 
> outHumidity: 35.0, outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 55.8, 
> pressure: None, rain: 0.0, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, 
> soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 0.0, 
> sunrise: 1578580608.0, sunset: 1578617472.0, txBatteryStatus: 0, usUnits: 
> 1, windchill: 55.8, windDir: None, windGust: 0.0, windGustDir: None, 
> windSpeed: 0.0, windSpeed10: 2.0, yearET: 0.0, yearRain: 0.0
> LOOP:   2020-01-09 18:36:18 MST (1578620178) appTemp: 51.7532829608, 
> barometer: 29.827, beaufort: 0, cloudbase: 8949.86520147, 
> consBatteryVoltage: 4.66, dateTime: 1578620178, dayET: 0.0, dayRain: 0.0, 
> dewpoint: 28.5645931135, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
> extraAlarm8: 0, forecastIcon: 6, forecastRule: 9, heatindex: 55.8, humidex: 
> 55.8, inDewpoint: 33.5667167944, inHumidity: 22.0, insideAlarm: 0, inTemp: 
> 75.0, leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain: 0.0, 
> outHumidity: 35.0, outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 55.8, 
> pressure: None, rain: 0.0, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, 
> soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 0.0, 
> sunrise: 1578580608.0, sunset: 1578617472.0, txBatteryStatus: 0, usUnits: 
> 1, windchill: 55.8, windDir: None, windGust: 0.0, windGustDir: None, 
> windSpeed: 0.0, windSpeed10: 2.0, yearET: 0.0, yearRain: 0.0
>
> In an attempt to fix the problem I did an apt purge weewx on my raspberry 
> pi, renamed the old weewx.sdb file and reinstalled weewx from the deb file 
> using the install instructions for debian, so actually apt update, apt 
> install weewx.  Answered the questions during the install, added back in 
> the authentication for wunderground, CWOP, etc from the saved weewx.conf 
> file  This really has me stumped.  Please let me know what more info I need 
> to provide to diagnose this strange problem.
>
> Oh, running NTP and it's is synced and has the correct time.  
>
> Here is the syslog output from a startup
>
> Jan  9 19:40:55 weewx weewx[12192]: engine: Initializing weewx version 
> 3.9.2
> Jan  9 19:40:55 weewx weewx[12192]: engine: Using Python 2.7.13 (default, 
> Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
> Jan  9 19:40:55 weewx weewx[12192]: engine: Platform 
> Linux-4.19.66-v7+-armv7l-with-debian-9.11
> Jan  9 19:40:55 weewx weewx[12192]: engine: Locale is 'en_US.UTF-8'
> Jan  9 19:40:55 weewx weewx[12192]: engine: pid file is /var/run/weewx.pid
> Jan  9 19:40:55 weewx weewx[12181]: Starting weewx weather system: weewx.
> Jan  9 19:40:55 weewx systemd[1]: Started LSB: weewx weather system.
> Jan  9 19:40:55 weewx weewx[12196]: engine: Using configuration file 
> /etc/weewx/weewx.conf
> Jan  9 19:40:55 weewx weewx[12196]: engine: Debug is 1
> Jan  9 19:40:55 weewx weewx[12196]: engine: Initializing engine
> Jan  9 19:40:55 weewx weewx[12196]: engine: Loading station type Vantage 
> (weewx.drivers.vantage)
> Jan  9 19:40:55 weewx weewx[12196]: vantage: Driver version is 3.1.1
> Jan  9 19:40:55 weewx weewx[12196]: vantage: Opened up serial port 
> /dev/ttyUSB0; baud 19200; timeout 4.00
> Jan  9 19:40:55 weewx weewx[12196]: vantage: Gentle wake up of console 
> successful
> Jan  9 19:40:55 weewx weewx[12196]: vantage: Hardware type is 16
> Jan  9 19:40:55 weewx weewx[12196]: vantage: ISS ID is 1
> Jan  9 19:40:55 weewx weewx[12196]: vantage: Hardware name: Vantage Pro2
> Jan  9 19:40:55 weewx weewx[12196]: engine: Loading service 
> weewx.engine.StdTimeSynch
> Jan  9 19:40:55 weewx weewx[12196]: engine: Finished loading service 
> weewx.engine.StdTimeSynch
> Jan  9 19:40:55

[weewx-user] Re: Which weather station would you buy ?

[PJO]

I ordered an Ecowitt  station in December; it's due 
to be delivered on Monday. Am currently using a FineOffset WH1080 and a 
Raspberry Pi running WeeWX. Not sure what you mean by walls being too big. 
Too big for what?

-- 
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/6c9f1409-4c5f-4541-b178-f64ecd846649%40googlegroups.com.

Re: [weewx-user] Re: Weewx 3.9.2 is acting strangely after an unexpected shutdown

[Thomas Keffer]

An alternative is to use the wee_device utility with the --dump command.
Linky
.
It can often salvage nearly everything in the logger.

-tk

On Thu, Jan 9, 2020 at 3:42 PM Jarom Hatch  wrote:

> Okay, while it wasn't perfect, I was able to reclaim much of the missing
> data from clearing the memory from what got sent to WU via rapidfire using
> the wee_import utility.  I gotta say I am super glad that exists.  You guys
> think of everything!  Had to use the 4.0 beta version but it worked great.
>
> --
> 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/a4238027-ba01-4a1f-9ee4-32a44b55c9ef%40googlegroups.com
> 
> .
>

-- 
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/CAPq0zECCJ_q42ckcA_xVZgixO0h4sfY14p%3DsZN_3XGR3gXA6_Q%40mail.gmail.com.

[weewx-user] Re: Weewx 3.9.2 is acting strangely after an unexpected shutdown

[Jarom Hatch]

Okay, while it wasn't perfect, I was able to reclaim much of the missing 
data from clearing the memory from what got sent to WU via rapidfire using 
the wee_import utility.  I gotta say I am super glad that exists.  You guys 
think of everything!  Had to use the 4.0 beta version but it worked great.

-- 
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/a4238027-ba01-4a1f-9ee4-32a44b55c9ef%40googlegroups.com.

Re: [weewx-user] Using Sofaskin wrong date format

[Thomas Keffer]

I don't know anything about Sofaskin, but assuming it behaves like other
skins, these things are set in weewx.conf, under section
TimeFormats.

See the section *Translate labels and modify local options
*
in
the Customizing Guide.

-tk




On Thu, Jan 9, 2020 at 8:21 AM Mike  wrote:

> Hello world,
>
> I am confused with time format. In the plots the time format is right.
>
> I have marked the wrong date format black.
>
> Would like to have day/month/year
>
> Where do I have to change the time format. I was looking in the weewx.conf
> and the skin.conf
>
> Thanks in advance.
>
> Kind Reg.
> Mike
>
>
> [image: ss2.JPG]
>
>
> [image: ss1.JPG]
>
> --
> 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/0511-3998-46b1-9a4c-8338e70b866b%40googlegroups.com
> 
> .
>

-- 
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/CAPq0zEDL2rkULjx2h%2BKYCykSr8_%3D8%3DM61Z5pA3Oad9s4XESnrQ%40mail.gmail.com.

[weewx-user] Re: Windy plugin error

[mwall]

On Thursday, January 9, 2020 at 1:24:08 PM UTC-5, raenrfm wrote:
>
> Hey Vince, thanks for the tip.  Turns out I needed to send from my base 
> station the "barometer" value pre calculated in the base station before 
> sending it to the mqtt server, so seeing as windy.py needs the barometer 
> implicitly I had to send it to weewx already corrected for my altitude.  I 
> guess I assumed that weewx would calculate it at the end of every archive 
> cycle.  Weird. 
>

it looks like 'barometer' is, indeed, in the record, but it has a value of 
'None'.  does your station send partial packets, or does your station 
sometimes have no barometric reading in enough loop packets so that it 
reports an archive record with a value of 'None' for 
pressure/barometer/altimeter? 

fixed at commit add0332f89cd621f4dc9e49bbcd072698f22fbc4 - if there is no 
barometer, the weewx-windy extension will upload a value of None (not sure 
how windy will deal with this, but that is what happens for all of the 
other observations, so at least it will be consistent and will not crash 
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/6b1a509c-203a-4e68-91e7-3840f3675406%40googlegroups.com.

[weewx-user] Re: Windy plugin error

[raenrfm]

Hey Vince, thanks for the tip.  Turns out I needed to send from my base 
station the "barometer" value pre calculated in the base station before 
sending it to the mqtt server, so seeing as windy.py needs the barometer 
implicitly I had to send it to weewx already corrected for my altitude.  I 
guess I assumed that weewx would calculate it at the end of every archive 
cycle.  Weird.   

On Thursday, 9 January 2020 10:38:28 UTC-5, vince wrote:
>
> On Thursday, January 9, 2020 at 5:47:19 AM UTC-8, raenrfm wrote:
>>
>> Seems like it's this line in the windy.py:
>>
>> if 'barometer' in record_m:
>>
>> data['pressure'] = 100.0 * record_m['barometer'] # Pascalsthat is 
>> causing the issue, but there is no mqtt topic in my setup called 
>> "barometer", I'm only posting "pressure", so why would it even be trying to 
>> execute this function?
>>
>>
>>
> Without looking at windy.py, my guess is there is something in your loop 
> and/or archive content that 'has' a barometer item in there. 
>

-- 
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/3f0e39bc-6896-412b-a779-521aeb3518d9%40googlegroups.com.

[weewx-user] Re: Windy plugin error

[vince]

On Thursday, January 9, 2020 at 5:47:19 AM UTC-8, raenrfm wrote:
>
> Seems like it's this line in the windy.py:
>
> if 'barometer' in record_m:
>
> data['pressure'] = 100.0 * record_m['barometer'] # Pascalsthat is causing 
> the issue, but there is no mqtt topic in my setup called "barometer", I'm 
> only posting "pressure", so why would it even be trying to execute this 
> function?
>
>
>
Without looking at windy.py, my guess is there is something in your loop 
and/or archive content that 'has' a barometer item in there. 

-- 
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/a0f07831-a640-4258-b138-4720ac356864%40googlegroups.com.

[weewx-user] Using Sofaskin wrong date format

[Mike]

Hello world,

I am confused with time format. In the plots the time format is right.

I have marked the wrong date format black.

Would like to have day/month/year

Where do I have to change the time format. I was looking in the weewx.conf 
and the skin.conf

Thanks in advance.

Kind Reg.
Mike


[image: ss2.JPG]


[image: ss1.JPG]

-- 
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/0511-3998-46b1-9a4c-8338e70b866b%40googlegroups.com.

[weewx-user] Re: Weewx 3.9.2 is acting strangely after an unexpected shutdown

[Jarom Hatch]

Well, clearing the memory fixed it.  Not sure what caused the corruption, 
only the RPI lost power.  First thing I tried last night was power cycling 
the station and that didn't help.  Thanks for the tip!

On Thursday, January 9, 2020 at 4:10:40 AM UTC-7, gjr80 wrote:
>
> Hi, 
>
> Classic case of corrupt station memory. Have a look at the ‘Corrupt 
> station memory’ section (
> http://weewx.com/docs/usersguide.htm#Corrupt_station_memory) in the 
> User’s Guide. Common occurrence when a Davis station has a power 
> interruption. Worthwhile noting the symptoms for future. 
>
> 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/d394b696-0dd3-4833-92c4-6024f1b51365%40googlegroups.com.

Re: [weewx-user] Re: Which weather station would you buy ?

[G Hammer]

Look at either Ambient Weather or Ecowitt series. Both are supported well 
with WeeWX, are easy to own, and inexpensive (for me).


On Thursday, January 9, 2020 at 5:01:22 AM UTC-5, Olivier Garnier wrote:
>
> Thanks,
> I've seen it ... but i won't have enougth time to ?"manage"? it ...
> Need something simple ;)
>
> Thank you ;)
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a21cc686-eb57-4f37-a6fd-0dcaaf595640%40googlegroups.com.

[weewx-user] Re: Windy plugin error

[raenrfm]

Seems like it's this line in the windy.py:

if 'barometer' in record_m:
data['pressure'] = 100.0 * record_m['barometer'] # Pascalsthat is causing 
the issue, but there is no mqtt topic in my setup called "barometer", I'm 
only posting "pressure", so why would it even be trying to execute this 
function?

Any takers on this one?

On Wednesday, 8 January 2020 13:15:45 UTC-5, raenrfm wrote:
>
> Posting to windy works for a while but then I inevitably get this error:
>
> Jan  8 12:21:18 6a4c8de67d74 weewx[7295]: restx: Windy: Unexpected 
> exception of type 
> Jan  8 12:21:18 6a4c8de67d74 weewx[7295]: *** Traceback (most recent call 
> last):
> Jan  8 12:21:18 6a4c8de67d74 weewx[7295]: ***   File 
> "/usr/share/weewx/weewx/restx.py", line 343, in run_loop
> Jan  8 12:21:18 6a4c8de67d74 weewx[7295]: ***
>  self.process_record(_record, dbmanager)
> Jan  8 12:21:18 6a4c8de67d74 weewx[7295]: ***   File 
> "/usr/share/weewx/weewx/restx.py", line 392, in process_record
> Jan  8 12:21:18 6a4c8de67d74 weewx[7295]: *** _payload = 
> self.get_post_body(_full_record)
> Jan  8 12:21:18 6a4c8de67d74 weewx[7295]: ***   File 
> "/usr/share/weewx/user/windy.py", line 164, in get_post_body
> Jan  8 12:21:18 6a4c8de67d74 weewx[7295]: *** data['pressure'] = 100.0 
> * record_m['barometer']  # Pascals
> Jan  8 12:21:18 6a4c8de67d74 weewx[7295]: *** TypeError: unsupported 
> operand type(s) for *: 'float' and 'NoneType'
> Jan  8 12:21:18 6a4c8de67d74 weewx[7295]: restx: Windy: Thread exiting. 
> Reason: unsupported operand type(s) for *: 'float' and 'NoneType'
>
> Is it because I'm getting a null entry for pressure in a given archive 
> cycle?
>

-- 
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/acf0a660-8050-417e-ab04-cd2d9dab5c73%40googlegroups.com.

Re: [weewx-user] Re: Which weather station would you buy ?

[raenrfm]

My system is pretty autonomous.  I rarely need to touch it, but I suppose 
it's not quite as hands off as a pre-built system.  I saw this one on 
Kickstarter, looks quite robust with ultrasonic wind speed and direction 
sensor, hepatic sensor for rain and even does UV and Radiance.  I just 
don't want anything "cloud" in my house so that is a negative to me.

https://www.kickstarter.com/projects/weatherflow/tempest-a-revolutionary-personal-weather-system


On Thursday, 9 January 2020 05:01:22 UTC-5, Olivier Garnier wrote:
>
> Thanks,
> I've seen it ... but i won't have enougth time to ?"manage"? it ...
> Need something simple ;)
>
> Thank you ;)
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/627eeb39-a88a-46f6-9581-27f4d1dc9328%40googlegroups.com.

Re: [weewx-user] Re: US - Metric problem

[Thomas Keffer]

You're not giving a lot of information, but it sounds like your weather
station is emitting values in the US System, to which you are adding a
value in the metric system without converting one or the other first.

You need to inject your value *after* the service StdConvert has done its
work converting the record to metric, not before.

But, that's just an educated guess. Without seeing details of your
weewx.conf file, we can't be sure.

No need to be "offended." The option target_unit clearly warns not to
change the value without knowing what you're doing. Heed the warning.

-tk






On Thu, Jan 9, 2020 at 4:56 AM Pila  wrote:

> Just to be clear, page on pondservice (example) says in Units "
> *You must make sure the units match!" Which units? I do not understand
> what the next sentence refers to. My station is metric, all my data is
> metric, all works fine. I could work around by writing down data in F, but
> this is an offensive solution to me as I never use anything but metric
> anywhere.  *
>
> *As to converting, I just found by accident "*Changing the database unit
> system" so I expect that should solve my 2) question if I choose to do it.
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/e68ac729-dc93-4699-bde9-770c569faa84%40googlegroups.com
> 
> .
>

-- 
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/CAPq0zECL5qxCmUDN%3DKn157_SW7WLARvG8Y2tng_XaCLN6TV2zQ%40mail.gmail.com.

[weewx-user] Re: US - Metric problem

[Pila]

Just to be clear, page on pondservice (example) says in Units "
*You must make sure the units match!" Which units? I do not understand what 
the next sentence refers to. My station is metric, all my data is metric, 
all works fine. I could work around by writing down data in F, but this is 
an offensive solution to me as I never use anything but metric anywhere.  *

*As to converting, I just found by accident "*Changing the database unit 
system" so I expect that should solve my 2) question if I choose to do it.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e68ac729-dc93-4699-bde9-770c569faa84%40googlegroups.com.

[weewx-user] US - Metric problem

[Pila]

I use exclusively metric units. I am adding extra Celsius temperatures to 
the database. Unfortunatelly for me, when I was building this particular 
system, I neglected to switch the database from US to Metric units 
(target_unit).

1) WeeWx is correctly reading my extraTemp1 as 18.4 but is saving it in F. 
So, my graph shows -8C instead of 18C. How can I tell WeeWx this input unit 
is C and not F?

2) Is there a (relatively) simple way of converting my existing database 
from US to Metric units? Google assumes I am illiterate so I can not find 
an answer. I am sure this will byte me again, so I would prefer to convert 
and have all my bases in Metric units.

-- 
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/99c8e325-c318-4422-8b56-f9b4d952d631%40googlegroups.com.

[weewx-user] Weewx 3.9.2 is acting strangely after an unexpected shutdown

[gjr80]

Hi,

Classic case of corrupt station memory. Have a look at the ‘Corrupt station 
memory’ section (http://weewx.com/docs/usersguide.htm#Corrupt_station_memory) 
in the User’s Guide. Common occurrence when a Davis station has a power 
interruption. Worthwhile noting the symptoms for future.

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/e933773c-2cf7-4349-808e-02e75702f5bd%40googlegroups.com.

[weewx-user] Weewx 3.9.2 is acting strangely after an unexpected shutdown

[Jarom Hatch]

I've had power outages and stuff before and it's never been a big deal.  
Weewx was working fine up until my kids shut off the power strip the 
raspberry pi is plugged into.  Upon discovering that a few hours later I 
turned it on, it backfilled the past few hours of data, then just stopped 
inserting new data into the database, generating updated html files, 
uploading to external services (except for wunderground which now only does 
anything in rapidfire mode).  Every minute it generates the reports, but 
never updates them.  The database looks clean (remote mysql) and there are 
no errors being printed to the logs, even in debug mode.  Anyone know what 
might be going on here?  Here are some examples of what I'm seeing:
Jan  9 01:37:57 weather weewx[765]: restx: PWSWeather: Published record 
2020-01-09 01:33:00 MST (1578558780)
Jan  9 01:37:57 weather weewx[765]: manager: Added record 2020-01-09 
01:35:00 MST (1578558900) to database 'weewx'
Jan  9 01:37:57 weather weewx[765]: restx: OWM: Published record 2020-01-09 
01:32:00 MST (1578558720)
Jan  9 01:37:57 weather weewx[765]: manager: Added record 2020-01-09 
01:35:00 MST (1578558900) to daily summary in 'weewx'
Jan  9 01:37:57 weather weewx[765]: manager: Added record 2020-01-09 
01:35:00 MST (1578558900) to database 'weewxwd'
Jan  9 01:37:57 weather weewx[765]: manager: Added record 2020-01-09 
01:35:00 MST (1578558900) to daily summary in 'weewxwd'
Jan  9 01:37:57 weather weewx[765]: restx: PWSWeather: Published record 
2020-01-09 01:34:00 MST (1578558840)
Jan  9 01:37:57 weather weewx[765]: restx: PWSWeather: Published record 
2020-01-09 01:35:00 MST (1578558900)
Jan  9 01:37:57 weather weewx[765]: manager: Added record 2020-01-09 
01:36:00 MST (1578558960) to database 'weewx'
Jan  9 01:37:58 weather weewx[765]: restx: OWM: Published record 2020-01-09 
01:34:00 MST (1578558840)
Jan  9 01:37:58 weather weewx[765]: manager: Added record 2020-01-09 
01:36:00 MST (1578558960) to daily summary in 'weewx'
Jan  9 01:37:58 weather weewx[765]: manager: Added record 2020-01-09 
01:36:00 MST (1578558960) to database 'weewxwd'
Jan  9 01:37:58 weather weewx[765]: manager: Added record 2020-01-09 
01:36:00 MST (1578558960) to daily summary in 'weewxwd'
Jan  9 01:37:58 weather weewx[765]: engine: Starting main packet loop.
Jan  9 01:37:58 weather weewx[765]: restx: PWSWeather: Published record 
2020-01-09 01:36:00 MST (1578558960)
Jan  9 01:37:58 weather weewx[765]: engine: Clock error is -22780.28 
seconds (positive is fast)
Jan  9 01:37:58 weather weewx[765]: vantage: Clock set to 2020-01-09 
01:37:59 MST (1578559079)
Jan  9 01:37:58 weather weewx[765]: restx: OWM: Published record 2020-01-09 
01:35:00 MST (1578558900)
Jan  9 01:37:58 weather weewx[765]: restx: OWM: Published record 2020-01-09 
01:36:00 MST (1578558960)

That is the last time records were added to the DB.  After that last line 
all I get are these:
Jan  9 01:38:00 weather weewx[765]: restx: Wunderground-RF: Published 
record 2020-01-09 01:38:00 MST (1578559080)
Jan  9 01:38:00 weather weewx[765]: restx: Wunderground-RF: Published 
record 2020-01-09 01:38:00 MST (1578559080)
Jan  9 01:38:05 weather weewx[765]: restx: Wunderground-RF: Published 
record 2020-01-09 01:38:04 MST (1578559084)
Jan  9 01:38:05 weather weewx[765]: restx: Wunderground-RF: Published 
record 2020-01-09 01:38:04 MST (1578559084)
...
Jan  9 01:41:16 weather weewx[765]: restx: Wunderground-RF: Published 
record 2020-01-09 01:41:16 MST (1578559276)
Jan  9 01:41:16 weather weewx[765]: restx: Wunderground-RF: Published 
record 2020-01-09 01:41:16 MST (1578559276)
Jan  9 01:41:18 weather weewx[765]: restx: Wunderground-RF: Published 
record 2020-01-09 01:41:18 MST (1578559278)
Jan  9 01:41:19 weather weewx[765]: cheetahgenerator: Generated 7 files for 
report StandardReport in 2.99 seconds
Jan  9 01:41:20 weather weewx[765]: restx: Wunderground-RF: Published 
record 2020-01-09 01:41:20 MST (1578559280)
Jan  9 01:41:22 weather weewx[765]: restx: Wunderground-RF: Published 
record 2020-01-09 01:41:22 MST (1578559282)
Jan  9 01:41:22 weather weewx[765]: imagegenerator: Generated 8 images for 
StandardReport in 3.05 seconds
Jan  9 01:41:22 weather weewx[765]: copygenerator: copied 0 files to 
/var/www/weewx
Jan  9 01:41:22 weather weewx[765]: cheetahgenerator: Generated 1 files for 
report wdPWS in 0.14 seconds
Jan  9 01:41:23 weather weewx[765]: imageStackedWindRose: Generated 1 
images for wdStackedWindRose in 0.49 seconds
Jan  9 01:41:23 weather weewx[765]: rsyncupload: rsync'd 17 files (149,612 
bytes) in 0.86 seconds
Jan  9 01:41:24 weather weewx[765]: restx: Wunderground-RF: Published 
record 2020-01-09 01:41:24 MST (1578559284)
Jan  9 01:41:26 weather weewx[765]: restx: Wunderground-RF: Published 
record 2020-01-09 01:41:26 MST (1578559286)

After I disabled rapidfire, all I get in the logs are report generations:
Jan  9 02:08:53 weather weewx[702]: engine: Starting main packet loop.
Jan  9 02:09:21 weather weewx[702]: cheet

Re: [weewx-user] Re: Which weather station would you buy ?

[Olivier Garnier]

Thanks,
I've seen it ... but i won't have enougth time to ?"manage"? it ...
Need something simple ;)

Thank you ;)

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8c50f4f2-1c20-4889-9eb4-35f336cc0962%40googlegroups.com.

[weewx-user] Re: recalculating heatindex ?

[gjr80]

Hi,

If it is indeed the heatindex data that is incorrect you should be able to 
use the new --calc-missing action in the wee_database utility to be 
released with WeeWX v4 to re-calculate your heatindex data. That is of 
course provided the obs used to calculate heatindex (outTemp and outHumidity) 
are in fact correct. It would require a little SQL to first set heatindex 
to None/null in the archive table for the period over which you wish to 
re-calculate heatindex (--calc-missing only calculates derived observations 
(eg heatindex) if they are missing, hence the set to None/null) and then just 
use wee_database --calc-missing. 

Gary

On Tuesday, 7 January 2020 19:45:44 UTC+10, Tim Tuck wrote:
>
> Hi all,
>
> Is there a way to recalculate heatindex ?
>
> I've just installed the Belchertown skin and I'm looking at the graphs and 
> I see that heatindex was incorrectly calculated i.e. windchill and 
> heatindex appear to be swapped.
>
> Checking my weewx.conf I found that I had set heatindex to 
> hardware_preferred when it should have been software so I think that may 
> have contributed to the problem since I originally had h/w that did that 
> but it failed and I swapped to the Ecowitt which doesn't.
>
> Here is a graph of the data I want to fix...
>
> cheers
>
> Tim
>

-- 
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/b88d0407-2c04-4939-90ff-0c42ac801798%40googlegroups.com.