Re: [weewx-user] Re: First steps (TFA Nexus)

[Gary Roderick]

Judging by the LOOP packet contents and the TE923 sensor map the reason for
the missing data is that the data concerned is being mapped to fields that
are not in the weewx schema (refer back to my first post on this thread).
Even if the fields were in the schema the Standard skin does not display
any of the 'Extra' fields. You will need to specify a different sensor map
in weewx.conf or alter the in use schema and Standard skin template files
to use the 'Extra' fields. I would go the former.

Gary

On 17/01/2018 6:26 PM, "Andrew Milner"  wrote:

Have you forced a reload of the page in your browser??

Have you checked the times of the generated html files in public_html to
make sure they are the latest?
Are the times of the files in whatever web you are using the same?

Have you tried reading the file in public_html directly with a browser?

Is the time of the generated page correct??

Have you checked the contents of the archive table in the database to see
if the fields contain the expected data?

You still have not given us the contents of a REC packet!!  You need to run
weewx directly (not as a daemon) as you did when you posted the LOOP data -
but this time keep it running until you have got at least one REC packet
.



On Wednesday, 17 January 2018 09:36:27 UTC+2, Emil Kolbert wrote:

> Debug option activated (syslog attacked at the end of the message and a
> few other infos using the wee_device command).
> Install was done using the install instructions for Debian (standard image
> for Odroid XU4 and up-to-date).
> I assume - but of course maybe I'm wrong -  that I missed something sensor
> based because the station is sending data and the software is reading it
> but on the generated web page I still have.
>
>
> Current Conditions
> Outside Temperature N/A
> Wind Chill 4.1°C
> Heat Index N/A
> Dewpoint N/A
> Humidity N/A
>
>
>
>
> *odroid@odroid:~$ sudo wee_device --info*
>
> [sudo] password for odroid:
> Using configuration file /etc/weewx/weewx.conf
> Using TE923 driver version 0.24 (weewx.drivers.te923)
> Traceback (most recent call last):
>   File "/usr/bin/wee_device", line 54, in 
> main()
>   File "/usr/bin/wee_device", line 51, in main
> device.configure(config_dict)
>   File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
> self.do_options(options, parser, config_dict, prompt)
>   File "/usr/share/weewx/weewx/drivers/te923.py", line 768, in do_options
> with TE923Station() as station:
>   File "/usr/share/weewx/weewx/drivers/te923.py", line 1532, in __enter__
> self.open()
>   File "/usr/share/weewx/weewx/drivers/te923.py", line 1561, in open
> raise weewx.WeeWxIOError(e)
> weewx.WeeWxIOError: [Errno 16] Resource busy
>
>
> *odroid@odroid:~$ sudo wee_device --curren*t
>
> Using configuration file /etc/weewx/weewx.conf
> Using TE923 driver version 0.24 (weewx.drivers.te923)
> Traceback (most recent call last):
>   File "/usr/bin/wee_device", line 54, in 
> main()
>   File "/usr/bin/wee_device", line 51, in main
> device.configure(config_dict)
>   File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
> self.do_options(options, parser, config_dict, prompt)
>   File "/usr/share/weewx/weewx/drivers/te923.py", line 768, in do_options
> with TE923Station() as station:
>   File "/usr/share/weewx/weewx/drivers/te923.py", line 1532, in __enter__
> self.open()
>   File "/usr/share/weewx/weewx/drivers/te923.py", line 1561, in open
> raise weewx.WeeWxIOError(e)
> weewx.WeeWxIOError: [Errno 16] Resource busy
>
>
>
> *odroid@odroid:~$ sudo /etc/init.d/weewx stop*
> *[ ok ] Stopping weewx (via systemctl): weewx.service.*
> *odroid@odroid:~$ sudo wee_device --current*
>
> Using configuration file /etc/weewx/weewx.conf
> Using TE923 driver version 0.24 (weewx.drivers.te923)
> Querying the station for current weather data...
> dateTime: 1516174470
> forecast: 0
>  h_1: None
>h_1_state: no_link
>  h_2: 36
>h_2_state: ok
>  h_3: None
>h_3_state: no_link
>  h_4: 78
>h_4_state: ok
>  h_5: 74
>h_5_state: ok
> h_in: 56
>   h_in_state: ok
> rain: 8230
>   rain_state: ok
>  slp: 995.25
>slp_state: ok
>storm: 0
>  t_1: None
>t_1_state: no_link
>  t_2: 20.6
>t_2_state: ok
>  t_3: None
>t_3_state: no_link
>  t_4: 0.5
>t_4_state: ok
>  t_5: 16.2
>t_5_state: ok
> t_in: 20.7
>   t_in_state: ok
>   uv: None
> uv_state: no_link
>windchill: 4.2
>  windchill_state: ok
>  winddir: 8
>winddir_state: ok
> windgust: 0.0
>   windgust_state: ok
>windspeed: 0.0
>  windspeed_state: ok
>
>
>
> Thank you a lot for your time and support
>
>
>
> Jan 17 08:00:19 odroid weewx[11480]: manager: Added record 

Re: [weewx-user] Re: Question about latitude/longitude

[Gary Roderick]

Yes, suggest you edit weewx.conf and under [StdReport] comment out the
SteelSeries skin. The SteelSeries skin is set to copy all the necessary web
server files(including gauges.js) as part of the first report cycle after a
WeeWX start. Commenting out the skin will prevent this occurring in the
future.

Gary

On 21/01/2018 12:14 AM, "k_herriage via weewx-user" <
weewx-user@googlegroups.com> wrote:

> Very nice to have a clear night.
>
> By the way I just noticed that gauges stopped updating after I installed
> rtgd.py and restarted weewx. Really strong that it takes a while to start
> updating every 3 sec. after a change in gauges.js.
> I had to reedit that file for ../gauge-data.txt and then wait for it to
> start.
>
> Does rtgd pull a copy of weewx/skins/ss/scripts/gauges.js when it
> restarts? That's what it appears unless it gets it from somewhere else.
>
> Keith
>
> On Saturday, January 20, 2018 at 7:24:17 AM UTC-6, gjr80 wrote:
>>
>>
>>
>> On Saturday, 20 January 2018 23:20:36 UTC+10, k_her...@yahoo.com wrote:
>>>
>>> Downloaded 0.3.2, Fixed the cpu%.
>>> Thanks again.
>>>
>>
>> Good, and no problems.
>>
>>
>>> How did the stargazing go?
>>>
>>
>> Good, clouds cleared for a good couple of hours and saw some excellent
>> nebula and clusters in telescopes far bigger than mine. Then clouds rolled
>> in right on 9PM as forecast. 3rd attempt going to this venue and previous
>> two were clouded out so I am happy.
>>
>>  Gary
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx_wd

[Gary Roderick]

Hallo,
Ich schaue auf deine Seite. Was ist das Problem?

Gary

On Thu, 5 Apr 2018 at 20:29,  wrote:

> Hallo
> Schau dir das mal bitte an.   http://wetter-uerdingen.de/
>
>
> Am Dienstag, 3. April 2018 12:17:09 UTC+2 schrieb gjr80:
>
>> Aha. Vielleicht wurde ich als spam eingestuft, oder ich habe die falsche
>> e-mail-adresse verwendet. Meine e-mail-adresse lautet gjroderick(at)
>> gmail.com. Wenn Sie mir direkt eine e-mail senden könnten, kann ich auf
>> Ihre e-mail antworten.
>>
>> Gary
>>
>> On Tuesday, 3 April 2018 20:02:16 UTC+10, k-l...@gmx.de wrote:
>>>
>>> leider nix angekommen..
>>>
>>> Am Dienstag, 3. April 2018 11:58:53 UTC+2 schrieb k-l...@gmx.de:

 Oh ich muss mal nach sehen..

 Am Dienstag, 3. April 2018 11:56:51 UTC+2 schrieb gjr80:
>
> Hallo,
>
> Ich habe Ihnen den Code über eine separate E-Mail über das Wochenende
> geschickt. Hast du diese E-Mail bekommen?
>
> Gary

 --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
-- 

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Pascals are killing me

[Gary Roderick]

Hi,

Straight up I can see you running into a units problem. In your driver you
are using weewx.METRIC for field usUnits, so in other words all of the obs
in your loop packet should be from the weewx.METRIC unit system, for
barometer that is hPa. To calculate your barometer field you are taking
your sensor reading (I presume that is in Pa but I am not sure) and then
multiplying by a conversion factor that is in inHg/hPa, so the resulting
value will be in some sort of derivative of inHg, definitely not hPa.

I think you need to go back and trace through your barometer units very
carefully, remember the conversion factor is not just a number, but it has
units itself ie inHg/hPa. If you put values in US customary units in a
METRIC packet they will be converted/stored /displayed incorrectly
somewhere.

Gary

On 08/04/2017 8:23 AM, "Tommy Denton"  wrote:

> I have a custom hardware setup.. the DH22 and BME280 are outputting data
> las they should..(best I can tell)
>
> For my own quick and dirty webpage I did some maths to get pascals to inHg
> but now I want to do this in weewx and with some expert help on this forum
> I am like 98 percent there.. I have learned a lot but have hit the wall I
> always hit when I can't find some code to read or I don't know what code I
> am reading. Now I have read the manual and each time I get over one of
> these hurdles more of that manual changes from greek to english...but alas
> I am blocked by my own ignorance..
>
> So.. here is what I am doing for my own webpage..
>
> #Setup and pull data from the Sensor
> #bme280
> from Adafruit_BME280 import *
> sensor = BME280(mode=BME280_OSAMPLE_8)
> temperature = sensor.read_temperature()
> pascals = sensor.read_pressure()
>
> #Setup and pull data from the Sensor
> #AM2303
> import Adafruit_DHT
> sensor = Adafruit_DHT.AM2302
> pin = 17
> humidity, degrees = Adafruit_DHT.read_retry(sensor, pin)
>
> #Setup Time
> #time
> import time
> from datetime import datetime
> from time import strftime, localtime
>
> #Load up Converter
> #calcs
> from meteocalc import dew_point, heat_index
> temp = degrees*9/5+32
> baro = pascals/3386.389
> dewpoint = dew_point(temperature=degrees, humidity=humidity)
> heatindex = heat_index(temperature=degrees, humidity=humidity)
>
>
> My sensor puts out Pa
> I divide PA by 3386.839 and that gets me to inHg
>
> I output this to a file and it comes in to the right range and matches
> other weather stations around me plus or minus .10 inHg, so I feel like I
> have things setup correctly.
>
> Now this leads me to the error I am getting.
> The error I get is because the reading is outside the QA range limits.. So
> I have to tried to back into the number some to figure out what is going
> onengine: 2017-04-06 23:10:39 CDT (1491538239) LOOP value 'pressure'
> 85.32306 outside limits (24.0, 34.5)
>
> 85.32306... Where the heck did that number come from?  Well that
> is 85.32inHg/.029 = 2942.06896hPa*100 = 294206.8965517Pa
> Since hPa = mBAR there is no conversion there..
>
> The math is wrong in weewx.units?.. but I don't believe that either.. it
> has to be me messing up the math.. but I am not sure where to go from here
> to put in a custom conversion into extensions.py... I just have not been
> able to figure out the code to do so..
>
> or I am otherwise all wet..
>
> My driver looks like this.. (Expertly written by a very nice MWall)
>
> !/usr/bin/python
>
> import time
> import Adafruit_BME280
> import Adafruit_DHT
> import weewx.drivers
> from weewx.units import INHG_PER_MBAR
>
> DRIVER_NAME = 'PiHat'
> DRIVER_VERSION = '0.1'
>
> def loader(config_dict, engine):
> return PiHatDriver(**config_dict[DRIVER_NAME])
>
> class PiHatDriver(weewx.drivers.AbstractDevice):
> def __init__(self, **stn_dict):
> self._sensor1 = Adafruit_BME280.BME280(mode=
> Adafruit_BME280.BME280_OSAMPLE_8)
> self._sensor2 = Adafruit_DHT.AM2302
> self._pin = 17
>
> def genLoopPackets(self):
> while True:
> try:
> packet = dict()
> packet['dateTime'] = int(time.time() + 0.5)
> packet['usUnits'] = weewx.METRIC
> packet['inTemp'] = self._sensor1.read_temperature()
> packet['pressure'] = self._sensor1.read_pressure() *
> weewx.units.INHG_PER_MBAR
> packet['outHumidity'], packet['outTemp'] =
> Adafruit_DHT.read_retry(self._sensor2, self._pin)
> yield packet
> except IOError, e:
> syslog.syslog(syslog.LOG_ERR, "get data failed: %s" % e)
> time.sleep(10) # wait 60 seconds before getting next set of
> data
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because

Re: [weewx-user] trouble getting a calculated max solar radiation written in archive table

[Gary Roderick]

Pardon my typo, obviously 'macSolarRad' should be 'maxSolarRad'

Gary

On Tue, 26 Dec 2017 at 08:06, gjr80  wrote:

> Hi,
>
> First off, a quick stab in the dark, have you installed pyephem(
> http://weewx.com/docs/setup.htm)? Pyephem is required to calculate
> maxSolarRad otherwise it will always be None/null.
>
> No reason why calculated values can't be added, as long as (1) the
> calculated field actually appears in the weeWX produced archive record and
> (2) there is a field of that name in the archive. Might be worth checking
> what is in your archive records by running weeWX directly (
> http://www.weewx.com/docs/usersguide.htm#Running_directly) and looking at
> the lines starting with REC (will appear once every archive period). Is
> there a macSolarRad field and does it have a value?
>
> As for wee_database, sure it is very simple to add a field using tools
> like myphpadmin, but it is equally easy to screw things right up.
> Wee_database helps avoid such issues.
>
> Gary
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
-- 

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Disabling Weewx Autostart

[Gary Roderick]

Hi,

*sudo rm /etc/init.d/weewx *

should what you want.

Gary

On Tue, 26 Dec 2017 at 19:12, Phil Green  wrote:

> Hi,
> I have just been updating my Pi hardware from a Pi2 to Pi3.
> I use to use a hardware RTC module to set the clock time on boot.
> However the new Pi3 case I have no longer suits the RTC module.
> Because Weewx is set to autostart and the clock is set using the fake
> clock method and is incorrect until the NTP service sets it, Weewx doesn't
> run properly due to incorrect time.  I have to stop the service on boot
> manually and restart manually once the time has been set via internet NTP
> service.
> My question is how do I disable the auto starting of Weewx, I presume then
> I can manually start and stop Weewx in the usual way using:-
>
> *sudo /etc/init.d/weewx start*
>
> *sudo /etc/init.d/weewx stop*
>
>
> I installed Weewx using the apt-get method and using the current version
> of Jessie if this affects the solution.
> I look forward to getting advice.
> Regards
> Phil.
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
-- 

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Conversion from VWS to weewx

[Gary Roderick]

Joe,

You need to get the latest wxservices.py from the weewx repo on github, it
was updated since the last weewx release so has not been included in a
release version yet. Just move your existing wxservices.py aside and slot
in the updated version. There is a link in the readme on wee_import page if
you can't find it. Unfortunately am away from PC at the moment.

Gary

On 04/08/2016 11:17 AM, "jmltech"  wrote:

> Hi Gary,
> had a few minutes tonight, so I tried the import on a few daily text
> files.  Received this error on the command line:
> root@knoxville1:/home/weewx/bin# ./wee_import --vws
> --source=/home/weewx/daily --calc-missing --dry-run
> Starting wee_import...
> Traceback (most recent call last):
>   File "./wee_import", line 2446, in 
> main()
>   File "./wee_import", line 631, in main
> source_obj = Source.sourceFactory(options, args)
>   File "./wee_import", line 945, in sourceFactory
> options)
>   File "./wee_import", line 2275, in __init__
> super(VwsSource, self).__init__(config_dict, vws_config_dict, options)
>   File "./wee_import", line 836, in __init__
> self.wxcalculate = weewx.wxservices.WXCalculate(config_dict,
> AttributeError: 'module' object has no attribute 'WXCalculate'
>
> I didn't see anything in /var/log/syslog (I don't have weewx running)
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/gc_F0w_rtQw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Backfill from WU

[Gary Roderick]

My bad,  needs latest wxservices.py from weewx master branch.

On 01/09/2016 10:37 AM, "Andrew Milner"  wrote:

> Just had a go trying to use this for a dry run.  First of all got an error
> where weewx.wxservices.WXCalculate could not be found - changed to
> weewx.wxservices.StdWXCalculate to get past that one, now got another
> error from init saying 3 params needed but 5 supplied.
>
> Am I using an old or the wrong version of wee_import or something?
>
> was trying to import from wunder with the command:
> sudo ./wee_import --wunder --calc-missing --dry-run --station=ILIMASSO5
> --date=2013-02-01
>
>
>
> On Wednesday, 31 August 2016 11:50:20 UTC+3, Andrew Milner wrote:
>
>> Well I never knew that!!!  I use the api to get temperatures for another
>> project - and I guess the only difference is in the format of the returned
>> data!!
>>
>>
>> On Wednesday, 31 August 2016 11:29:17 UTC+3, gjr80 wrote:
>>
>>>
  a) where/how are the WU API key and station ID specified when
 retrieving history data from WU?

>>>
>>> station ID is specified on the command line with the --station= option.
>>> No need for an API key, in this case WU is the opposite of a bank; you need
>>> an API key to put your data in but you don't need a key to take it out! (of
>>> course you do need an API key if you want to use some of the WUs 'value
>>> added' services through their API). wee_import doesn't use the WU API,
>>> no need, just uses a plain old http request. Try the following in your
>>> browser substituting your station ID for XXYYY:
>>>
>>> https://www.wunderground.com/weatherstation/WXDailyHistory.a
>>> sp?ID=YYY&month=8&day=30&year=2016&format=1
>>>
>>>
 b) Is it possible to specify start and stop dates and times for the
 importing from WU via wee_import?

>>>
>>> Yep, with --date command line option. You will get the details when you
>>> run wee_import --help.
>>>
>>> Gary
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Steel Series Gauges and RealTime update - 2.5 second interval - how?

[Gary Roderick]

Yes,  thought it would, my gauges exhibit the same behaviour. The
SteelSeries gauges do a lot of funky stuff to calculate gauge scales etc, I
need to sit down and work through the data.

Of course,  we could just disable F :)

Gary

On 19/02/2017 11:28 AM, "tempus"  wrote:
>
> On Saturday, February 18, 2017 at 3:19:44 PM UTC-8, gjr80 wrote:
>>
>> Bob,
>>
>> If you want to try the realtime gauge-gate.txt you can find it here:
>>
>> https://github.com/gjr80/weewx-realtime_gauge-data
>>
>> Extension package is under the releases tab, install instructions are in
the readme.
>>
>> Gary
>
>
> It is installed and running with the same F scaling problem.
>
> Bob
>
> --
> You received this message because you are subscribed to the Google Groups
"weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx beta version 4.0.0b18

[Gary Roderick]

Ok, thinking some more the error could also occur if the current day has a
one hour period (from the top of the hour) where there is no rain data (as
distinct from  rain data that is zero). The issue is definitely tied to the
current days rain data, that is confirmed by your modifications. Give it a
day of continuous operation and return the template to normal and see if
the error has gone. Meantime I will try to harden the template today.

Gary

On Mon, 6 Apr 2020 at 01:34, Phil Owers  wrote:

> If I take out the rainrate in ss/skin.conf that gets rid of the rainrate
> error in the log
> If I ## all the lines with rain in them in gauge.date.txt file in SS then
> all the other errors in the log then go and the gauge.data.txt is formed
> correctly(all be it without the rain info)
>
> Phil
>
> On Saturday, April 4, 2020 at 10:40:41 AM UTC+1, Phil Owers wrote:
>
>> Hi Guys
>>
>> First of all I hope everybody is staying safe and well
>>
>> Before I go into to many details  should weewx v4.0.0b18 work on its own.
>>
>> Followed the Installation using setup.py, loaded all the prerequisites
>> for Debian 10(Buster)
>> Installed using python3 ./setup.py build  , sudo python3 ./setup.py
>> install
>>
>> Entered the name, vantage (6), serial , metric, ttyusb0  etc.
>>
>> Then started weewx using sudo ./bin/weewx
>> It downloaded all the data from my test console (This works fine plug
>> into another rasp pi v 3.9.2) then failed continuously overnight with no
>> graphs being generated.
>> The weewx.sdb was generated.
>>
>> Apr  4 10:22:20 raspberrypi weewx[1030] INFO weewx.manager: Starting
>> backfill of daily summaries
>> Apr  4 10:22:22 raspberrypi weewx[1030] INFO weewx.engine: Starting main
>> packet loop.
>> Apr  4 10:22:26 raspberrypi weewx[1030] INFO weewx.engine: Main loop
>> exiting. Shutting engine down.
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: Caught
>> OSError: [Errno 5] Input/output error
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> Traceback (most recent call last):
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> File "./bin/weewxd", line 154, in main
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> engine.run()
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 191, in run
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> callback(event)
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 740, in new_loop_packet
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> to_sorted_string(event.packet))
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> OSError: [Errno 5] Input/output error
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> Waiting 10 seconds then retrying...
>> Apr  4 10:22:28 raspberrypi kernel: [38075.324656] usb 1-1.3: new
>> high-speed USB device number 6 using xhci_hcd
>>
>> No extensions have been added . Apologies if Ive jumped the gun and this
>> doesn't work yet as a standalone
>> Phil
>>
> --
> 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/34f4fc85-6725-4b27-8871-0f1623f7cf37%40googlegroups.com
> 
> .
>
-- 

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/CAOJRuzz-jFUQ9XnMZ6Ou5UuyGbHVj8gaP-W-E77BkmZF%3Dvro7Q%40mail.gmail.com.

Re: [weewx-user] Re: which skin is aborting on me ?

[Gary Roderick]

Tracking down the skin should be easy with debug = 1, you simply look for
the line containing:

Found configuration file /home/weewx/skins/xx/skin.conf for report
'y'

immediately before the error, the problem skin will be xx and the
problem report (in weewx.conf) will be y. In your case the issue is
with the WeeWX image generator so would be looking at the plots in the
problem skin.

Agree it would be good to see skin or report in debug=0 logs, did look at
that some time ago and left it, can’t remember why (too hard, detail that
is not available, not sure.

Gary

On Sat, 3 Apr 2021 at 07:59, vince  wrote:

> I'm leaning that way, but might be a custom extension I cooked up years
> ago.   I'm bleeding through reenabling them one by one to figure it out.
>
> My more general question is whether there's a way to log which skin was
> being processed when an abort like this happened.   That might be a nice
> feature addition if it doesn't already exist.
>
>
> On Friday, April 2, 2021 at 2:55:19 PM UTC-7 gjr80 wrote:
>
>> Perhaps vds-local?
>
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/vjOV4j6PVRc/unsubscribe.
> To unsubscribe from this group and all its topics, 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/996f7c5b-4b68-402a-9978-5365757fcf50n%40googlegroups.com
> 
> .
>
-- 

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/CAOJRuzx_WV1ZpFE8thFy0-KLMA8Oy85KR6puyEQ3OPApDA5q3Q%40mail.gmail.com.