Re: [weewx-user] Re: Changes with Belchertown skin & DarkSky

[Tadej Javornik]

There seems to be something written to migrate from darksky to owm. Here is the 
link

https://openweathermap.org/darksky-openweather#match

-- 
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/cabda1c0-1dc3-43d1-af8f-6dfb3e75b8ab%40googlegroups.com.

Re: [weewx-user] Re: Apple buys DarkSky, IBM own TheWeatherChannel and WU, what's the next shoe to drop?

[William Burton]

Hello,

On Sunday, April 5, 2020 at 12:49:08 PM UTC-4, Ernest Jillson wrote:
>
> I have an API key from WU. It's free (probably because my station is 
> registered with them). I haven't tried it, but I would think there would be 
> a way to embed a forecast in your page using WU with a key?  Has anyone 
> done this?
>

I tried this yesterday. Was able to get the weewx-forecast 
 extension to work when run 
with WeeWX 3.9 but when I configured my WU API key, the response was 
"service not available." On further investigation, it seems the WU API was 
shut down in February 2019. In it's place, there's an API at weather.com. 
You can see the announcement at 
https://apicommunity.wunderground.com/weatherapi/topics/weather-underground-api-update.

Here are some links to the weather.com API:
APIs for Personal Weather Station Contributors 

5 Day Daily Forecast for Personal Weather Station Owners - v3.0 


I was able to use my WU API key with the weather.com API and successfully 
retrieve a five-day forecast to my browser in JSON. At first glance, it 
appears the weather.com API bears little resemblance to the WU API other 
than the URL is specified differently. Assuming this is the case, it would 
take a bit of work to add the weather.com API to weewx-forecast as a 
supported service.

However, I found that the weewx-forecast extension did not work with WeeWX 
4 beta running with Python 3. It seems there are differences with the 
Python Thread module between v2 and v3. I was able to work around some of 
the issues but not to the extent that I could get the extension to work.

-Bill


>
> On Thu, Apr 2, 2020 at 12:58 AM William Burton  > wrote:
>
>> Hello,
>>
>> On Wednesday, April 1, 2020 at 2:07:56 PM UTC-4, Chris Richmond wrote:
>>>
>>> Just saw that Apple bought DarkSky, and the API will get disabled end of 
>>> 2021.  Also noticed that TheWeatherChannel's
>>> web site is reporting as "by IBM" now.
>>>
>>> Chris
>>>
>>>
>> Not only that, no new DarkSky API signups are being accepted effective 
>> immediately. Then, July 1st this year, embeds and the website will be 
>> disabled except for current API and iOS usage.
>>
>> You can read the official announcement at https://blog.darksky.net/.
>>
>> -Bill
>>
>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/764b9b72-ca57-48ea-99ea-2ea1c0bcd3f6%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/644dce0f-8a91-4766-a5fd-f06e8f155414%40googlegroups.com.

Re: [weewx-user] Re: SteelSeries Gauges for WeeWx install problem

[weather list]

I did finally get the right repo after digging around, and all is well. 
Apologies for not having dug far enough down to figure it out!

Thanks for your good work!

> On 6Apr, 2020, at 16:21, gjr80  wrote:
> 
> To install the SteelSeries Gauges extension using wee_extension you need to 
> download steelseries-2.7.4.tar.gz package. You can usually download and 
> install an extension from a repo zip file but in this case you can’t. The 
> reason being the WeeWX SteelSeries skin files are maintained in the 
> SteelSeries Weather Gauges repo 
> (https://github.com/mcrossley/SteelSeries-Weather-Gauges) which contains the 
> SteelSeries Weather Gauges source code as well as the files required by each 
> of the SteelSeries Weather Gauges  supported PWS software packages. The WeeWX 
> installation of the SteelSeries Weather Gauges from this repo is a manual 
> process and does not provide an extension package for use with wee_extension. 
> In order to provide an extension package I decided to create a separate repo 
> that tracks just the package installer with the necessary SteelSeries Weather 
> Gauges files included but not tracked in the repo(I have no access to the 
> SteelSeries Weather Gauges repo other than public access and I don’t believe 
> it appropriate to expect the SteelSeries Weather Gauges repo owner to 
> maintain a WeeWX extension package). Unfortunately, by default github 
> includes a zip of the repo in any releases but in this case the zip cannot be 
> used as it is missing the core SteelSeries Weather Gauges code. I believe 
> this zip can be removed through a git setting, will look into that.
> 
> Suffice to say that if you follow the instructions either in the WeeWX wiki, 
> the SteelSeries Weather Gauges repo or the SteelSeries extension repo the 
> SteelSeries skin will be installed correctly.
> 
> 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/f9dcace6-ab6c-487c-a50d-b019e85292a7%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/B43CC8A0-0332-4DBD-ABA6-FCF6CF55078F%40gmail.com.

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

[John Kline]

For what it’s worth, rainRate has been a problem as I have it fixed in my copy 
of gauges.  I don’t know when I changed it as it is in my initial check in 
(Jan. 6) of my private (and modified) github copy.  In particular, I don’t know 
if I needed to change it for WeeWX 4.

> On Apr 6, 2020, at 6:27 PM, gjr80  wrote:
> 
> 
> Well looking into the rainrate/rainRate issue has been most interesting. 
> First up rainrate has been used in skin.conf for the rain rate plot as 
> follows since the SteelSeries Weather Gauges first directly supported WeeWX:
> 
>[[images]]
>x_label_format = %H:%M
>show_daynight = true 
>[[[daybarometer]]] 
>barometer
>[[[dayrain]]] 
>yscale = None, None, 0.02 
>plot_type = bar 
>rain 
>aggregate_type = sum 
>aggregate_interval = 3600 
>label = Rain (hourly total) 
> [[[dayrainrate]]] 
> rainrate
> 
> But why has this never caused a problem or been noticed before? I think the 
> way in which plot data is obtained and the introduction of xtypes holds the 
> answer. Before WeeWX v4 plot data was obtained via a call to 
> manager.getSqlVectors() which itself is encapsulated in a try...finally 
> statement. The result being that any error (for example a non-existant obs 
> type) was effectively swallowed and no data returned by 
> manager.getSqlVectors(). The image generator would then plot this non-data 
> which resulted in a plot devoid of data. Given that rain rate plots are 
> seldom looked at, quite often show no data, and also as this plot was only 
> used as a mouseover on the SteelSeries rain rate gauge, it is not surprising 
> it's lack of data was never noticed. Now consider the new xtypes regime, plot 
> data now comes from xtypes and if my xtypes understanding is correct, the 
> xtypes are searched until one is found that can return the required data. In 
> this case no xtype can return data for field rainrate which results in a 
> weewx.UnknownType error which is highlighted in the log and painfully obvious 
> to the user.
> 
> Of course the fix is simple, replace rainrate with the correct field 
> rainRate. This then got me wondering about the $hour.rain.sum.raw issue. I am 
> still convinced this is tied to an underlying lack of rain data for at least 
> one full hour in the day. My testing yesterday showed the gauge-data.txt 
> template would handle such a lack of rain data without problem, which is 
> counter to Phil's experience. But I was running under WeeWX 3.9.2 which does 
> not use xtypes, I am now thinking there is a subtle difference in the data 
> returned by xtypes in some corner cases. So far my understanding of xtypes 
> has been fairly limited to just what I have needed to bget by in working on 
> WeeWX 4.0 (which has not been much). Clearly I have a bit more reading to do 
> (@tkeffer - warning there will be some xtypes questions inbound) and I will 
> spend some time today seeing if I can replicate the issue.
> 
> 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/cf119004-27b4-4415-9c93-cc823bee6c75%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/58F37365-CB35-4A39-9BF9-2BCDEE516B0B%40johnkline.com.

[weewx-user] Re: SDR Driver

[rich T]

Michael

In the SDR section of weewx.conf, make sure the path is set.

[SDR]
# This section is for the software-defined radio driver.
# The driver to use
driver = user.sdr
cmd = rtl_433 -M utc -R 40 -F json
path = /usr/local/bin/


>
>

-- 
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/689a043d-ef55-4162-afe1-a313ed0d3067%40googlegroups.com.

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

[gjr80]

Well looking into the rainrate/rainRate issue has been most interesting. 
First up rainrate has been used in skin.conf for the rain rate plot as 
follows since the SteelSeries Weather Gauges first directly supported WeeWX:

   [[images]]
   x_label_format = %H:%M
   show_daynight = true 
   [[[daybarometer]]] 
   barometer
   [[[dayrain]]] 
   yscale = None, None, 0.02 
   plot_type = bar 
   rain 
   aggregate_type = sum 
   aggregate_interval = 3600 
   label = Rain (hourly total) 
[[[dayrainrate]]] 
rainrate

But why has this never caused a problem or been noticed before? I think the 
way in which plot data is obtained and the introduction of xtypes holds the 
answer. Before WeeWX v4 plot data was obtained via a call to 
manager.getSqlVectors() which itself is encapsulated in a try...finally 
statement. The result being that any error (for example a non-existant obs 
type) was effectively swallowed and no data returned by 
manager.getSqlVectors(). The image generator would then plot this non-data 
which resulted in a plot devoid of data. Given that rain rate plots are 
seldom looked at, quite often show no data, and also as this plot was only 
used as a mouseover on the SteelSeries rain rate gauge, it is not 
surprising it's lack of data was never noticed. Now consider the new xtypes 
regime, plot data now comes from xtypes and if my xtypes understanding is 
correct, the xtypes are searched until one is found that can return the 
required data. In this case no xtype can return data for field rainrate 
which results in a weewx.UnknownType error which is highlighted in the log 
and painfully obvious to the user.

Of course the fix is simple, replace rainrate with the correct field 
rainRate. This then got me wondering about the $hour.rain.sum.raw issue. I 
am still convinced this is tied to an underlying lack of rain data for at 
least one full hour in the day. My testing yesterday showed the 
gauge-data.txt template would handle such a lack of rain data without 
problem, which is counter to Phil's experience. But I was running under 
WeeWX 3.9.2 which does not use xtypes, I am now thinking there is a subtle 
difference in the data returned by xtypes in some corner cases. So far my 
understanding of xtypes has been fairly limited to just what I have needed 
to bget by in working on WeeWX 4.0 (which has not been much). Clearly I 
have a bit more reading to do (@tkeffer - warning there will be some xtypes 
questions inbound) and I will spend some time today seeing if I can 
replicate the issue.

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/cf119004-27b4-4415-9c93-cc823bee6c75%40googlegroups.com.

Re: [weewx-user] Re: SteelSeries Gauges for WeeWx install problem

[gjr80]

To install the SteelSeries Gauges extension using wee_extension you need to 
download steelseries-2.7.4.tar.gz package. You can usually download and install 
an extension from a repo zip file but in this case you can’t. The reason being 
the WeeWX SteelSeries skin files are maintained in the SteelSeries Weather 
Gauges repo (https://github.com/mcrossley/SteelSeries-Weather-Gauges) which 
contains the SteelSeries Weather Gauges source code as well as the files 
required by each of the SteelSeries Weather Gauges  supported PWS software 
packages. The WeeWX installation of the SteelSeries Weather Gauges from this 
repo is a manual process and does not provide an extension package for use with 
wee_extension. In order to provide an extension package I decided to create a 
separate repo that tracks just the package installer with the necessary 
SteelSeries Weather Gauges files included but not tracked in the repo(I have no 
access to the SteelSeries Weather Gauges repo other than public access and I 
don’t believe it appropriate to expect the SteelSeries Weather Gauges repo 
owner to maintain a WeeWX extension package). Unfortunately, by default github 
includes a zip of the repo in any releases but in this case the zip cannot be 
used as it is missing the core SteelSeries Weather Gauges code. I believe this 
zip can be removed through a git setting, will look into that.

Suffice to say that if you follow the instructions either in the WeeWX wiki, 
the SteelSeries Weather Gauges repo or the SteelSeries extension repo the 
SteelSeries skin will be installed correctly.

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/f9dcace6-ab6c-487c-a50d-b019e85292a7%40googlegroups.com.

[weewx-user] Re: SDR Driver

[Wes Witt]

thanks, makes sense now. i accomplish this with wifi. all my outdoor 
sensors are connected to a custom PCB that i designed which is in turn 
connected to an rpi via serial.  the rpi then posts sensor readings to a 
local mqtt server via wifi. it's extremely reliable and works very well. 
for my indoor sensors they are again a custom pcb with an esp8266 and a 
bme280 powered with a rechargable battery (which lasts 6 months).  the 
indoor sensor just posts to the same mqtt server.  for weewx i wrote a 
simple driver that reads from mqtt.  

-- 
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/60abc8f9-608f-406e-837c-0ea3ac17147d%40googlegroups.com.

Re: [weewx-user] Re: SteelSeries Gauges for WeeWx install problem

[Phil Owers]

I believe 2.7.4.tar.gz is the correct one perhaps somebody could confirm
that Please..   Phil

On Mon, 6 Apr 2020, 20:01 weather list,  wrote:

> Ah, it looks as if perhaps I got the wrong repository/version. This
>  seems to
> be the correct one. Will try again.
>
> On Monday, April 6, 2020 at 2:05:03 PM UTC-4, weather list wrote:
>>
>> Using the downloaded master from here,
>>  I ran the standard install:
>>
>> $ sudo bin/wee_extension --install /home/pi/Downloads/weewx-steelseries-
>> master.zip --config=weewx.conf
>> Request to install '/home/pi/Downloads/weewx-steelseries-master.zip'
>> Extracting from zip archive /home/pi/Downloads/weewx-steelseries-master.
>> zip
>> Traceback (most recent call last):
>>   File "bin/wee_extension", line 82, in 
>> main()
>>   File "bin/wee_extension", line 74, in main
>> ext.install_extension(options.install)
>>   File "/home/weewx/bin/weecfg/extension.py", line 116, in
>> install_extension
>> self.install_from_dir(extension_dir)
>>   File "/home/weewx/bin/weecfg/extension.py", line 174, in
>> install_from_dir
>> shutil.copy(source_path, destination_path)
>>   File "/usr/lib/python2.7/shutil.py", line 139, in copy
>> copyfile(src, dst)
>>   File "/usr/lib/python2.7/shutil.py", line 96, in copyfile
>> with open(src, 'rb') as fsrc:
>> IOError: [Errno 2] No such file or directory:
>> '/var/tmp/weewx-steelseries-master/skins/ss/gauge-data.txt.tmpl'
>> Can someone tell where I have this wrong?
>>
>> Raspbian Desktop running in a virtual machine.
>>
>> All other extensions have installed normally.
>>
>> WeeWx installed using setup.py, version 3.9.2, Python 2.7x
>>
> --
> 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/09e86a4f-9a97-4e00-8b4e-36867c10663a%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/CALTQ7pNaEW%3DOx%2BLyc%2BKmScdMAVzLGRQ3AZkStf3%3DEqxuOVMj-w%40mail.gmail.com.

[weewx-user] Re: SDR Driver

[Michael]

Hello Wes Witt,
The sdr is not used to receive radio or TV signals but the program is 
listening at the frequency 433 MHz. The outdoor sensors of the weather 
stations usually send on this. I would like to use it to read the rain 
gauge, wind sensor and outside temperature of my current weather station 
and use a bme 280 to record the inside temperature and humidity. It works 
with the rtl_433 program, but when I try to access the program with the 
driver and weewx and he can't find the program. but I don't know how to 
correct the mistake.

Best regards Michael

Am Montag, 6. April 2020 20:11:46 UTC+2 schrieb Wes Witt:
>
> this looks cool, but i'm ignorant about using an SDR with a weather 
> station. i'm curious about what exactly does this provide?  will if give 
> audio recordings from weather broadcasts?
>

-- 
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/e8c40fed-b816-4106-989b-dc563b85222f%40googlegroups.com.

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

[Phil Owers]

I used steelseries-2.7.4.tar.gz
Phil

On Mon, 6 Apr 2020, 19:46 steeple ian,  wrote:

> Phil,
> Could it be that you downloaded your installs from different places? I
> have just worked out that there are two out there.
> Ian
>
> On Mon, Apr 6, 2020 at 4:38 PM Thomas Keffer  wrote:
>
>> As far as weewx is concerned, it's always been rainRate.
>>
>> I don't know how Steelgauges works, but it's possible it's only used in
>> case-insensitive database queries.
>>
>> -tk
>>
>> On Mon, Apr 6, 2020 at 8:12 AM Phil Owers 
>> wrote:
>>
>>> This is interesting
>>> I have a pi running 3.9.2 (Python2) which runs OK with rainrate
>>> (Steelgauges 2.7.4) ( yes all lower case)
>>>
>>> But on a pi running v4.0.0.b18 (Python3) with Steelgauges 2.7.4 rainrate
>>> generates an error in the log which is corrected if its changed to rainRate.
>>>
>>> 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/8720d1b3-1d3f-4c78-9aec-5896b1b0e63e%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/CAPq0zEBL528s6%3D1SodmDsHQGDbMLW8h4aq-P3J7OaxKVfZumEQ%40mail.gmail.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

Re: [weewx-user] SteelSeries Gauges for WeeWx install problem

[Phil Owers]

I used sudo ./bin/wee_extension --install  /home
pi/Downloads/steelseries.2.7.4.tar.gzThat worked for me. Phil

On Mon, 6 Apr 2020, 19:05 weather list,  wrote:

> Using the downloaded master from here,
>  I ran the standard install:
>
> $ sudo bin/wee_extension --install /home/pi/Downloads/weewx-steelseries-
> master.zip --config=weewx.conf
> Request to install '/home/pi/Downloads/weewx-steelseries-master.zip'
> Extracting from zip archive /home/pi/Downloads/weewx-steelseries-master.
> zip
> Traceback (most recent call last):
>   File "bin/wee_extension", line 82, in 
> main()
>   File "bin/wee_extension", line 74, in main
> ext.install_extension(options.install)
>   File "/home/weewx/bin/weecfg/extension.py", line 116, in
> install_extension
> self.install_from_dir(extension_dir)
>   File "/home/weewx/bin/weecfg/extension.py", line 174, in
> install_from_dir
> shutil.copy(source_path, destination_path)
>   File "/usr/lib/python2.7/shutil.py", line 139, in copy
> copyfile(src, dst)
>   File "/usr/lib/python2.7/shutil.py", line 96, in copyfile
> with open(src, 'rb') as fsrc:
> IOError: [Errno 2] No such file or directory:
> '/var/tmp/weewx-steelseries-master/skins/ss/gauge-data.txt.tmpl'
> Can someone tell where I have this wrong?
>
> Raspbian Desktop running in a virtual machine.
>
> All other extensions have installed normally.
>
> WeeWx installed using setup.py, version 3.9.2, Python 2.7x
>
> --
> 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/131dc366-fd77-48d5-a589-c84d53483e6f%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/CALTQ7pPgyBMQhJinRQ-HF1cJkNXogyeZtt8qovS6a2%3DwMuGoQQ%40mail.gmail.com.

[weewx-user] Re: SteelSeries Gauges for WeeWx install problem

[weather list]

Ah, it looks as if perhaps I got the wrong repository/version. This 
 seems to 
be the correct one. Will try again.

On Monday, April 6, 2020 at 2:05:03 PM UTC-4, weather list wrote:
>
> Using the downloaded master from here, 
>  I ran the standard install:
>
> $ sudo bin/wee_extension --install /home/pi/Downloads/weewx-steelseries-
> master.zip --config=weewx.conf
> Request to install '/home/pi/Downloads/weewx-steelseries-master.zip'
> Extracting from zip archive /home/pi/Downloads/weewx-steelseries-master.
> zip
> Traceback (most recent call last):
>   File "bin/wee_extension", line 82, in 
> main()
>   File "bin/wee_extension", line 74, in main
> ext.install_extension(options.install)
>   File "/home/weewx/bin/weecfg/extension.py", line 116, in 
> install_extension
> self.install_from_dir(extension_dir)
>   File "/home/weewx/bin/weecfg/extension.py", line 174, in 
> install_from_dir
> shutil.copy(source_path, destination_path)
>   File "/usr/lib/python2.7/shutil.py", line 139, in copy
> copyfile(src, dst)
>   File "/usr/lib/python2.7/shutil.py", line 96, in copyfile
> with open(src, 'rb') as fsrc:
> IOError: [Errno 2] No such file or directory: 
> '/var/tmp/weewx-steelseries-master/skins/ss/gauge-data.txt.tmpl'
> Can someone tell where I have this wrong?
>
> Raspbian Desktop running in a virtual machine.
>
> All other extensions have installed normally.
>
> WeeWx installed using setup.py, version 3.9.2, Python 2.7x
>

-- 
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/09e86a4f-9a97-4e00-8b4e-36867c10663a%40googlegroups.com.

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

[steeple ian]

Phil,
Could it be that you downloaded your installs from different places? I have
just worked out that there are two out there.
Ian

On Mon, Apr 6, 2020 at 4:38 PM Thomas Keffer  wrote:

> As far as weewx is concerned, it's always been rainRate.
>
> I don't know how Steelgauges works, but it's possible it's only used in
> case-insensitive database queries.
>
> -tk
>
> On Mon, Apr 6, 2020 at 8:12 AM Phil Owers 
> wrote:
>
>> This is interesting
>> I have a pi running 3.9.2 (Python2) which runs OK with rainrate
>> (Steelgauges 2.7.4) ( yes all lower case)
>>
>> But on a pi running v4.0.0.b18 (Python3) with Steelgauges 2.7.4 rainrate
>> generates an error in the log which is corrected if its changed to rainRate.
>>
>> 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/8720d1b3-1d3f-4c78-9aec-5896b1b0e63e%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/CAPq0zEBL528s6%3D1SodmDsHQGDbMLW8h4aq-P3J7OaxKVfZumEQ%40mail.gmail.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/CADASSaSURS6sSjo4ZXdAdjOdcecGY68NvBBGR0__SzVQm%3D%3D30g%40mail.gmail.com.

[weewx-user] Re: SDR Driver

[Wes Witt]

this looks cool, but i'm ignorant about using an SDR with a weather 
station. i'm curious about what exactly does this provide?  will if give 
audio recordings from weather broadcasts?

-- 
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/c14bee53-1d77-4fe4-b8a4-22259c3aebe3%40googlegroups.com.

[weewx-user] SteelSeries Gauges for WeeWx install problem

[weather list]

Using the downloaded master from here, 
 I ran the standard install:

$ sudo bin/wee_extension --install /home/pi/Downloads/weewx-steelseries-
master.zip --config=weewx.conf
Request to install '/home/pi/Downloads/weewx-steelseries-master.zip'
Extracting from zip archive /home/pi/Downloads/weewx-steelseries-master.zip
Traceback (most recent call last):
  File "bin/wee_extension", line 82, in 
main()
  File "bin/wee_extension", line 74, in main
ext.install_extension(options.install)
  File "/home/weewx/bin/weecfg/extension.py", line 116, in install_extension
self.install_from_dir(extension_dir)
  File "/home/weewx/bin/weecfg/extension.py", line 174, in install_from_dir
shutil.copy(source_path, destination_path)
  File "/usr/lib/python2.7/shutil.py", line 139, in copy
copyfile(src, dst)
  File "/usr/lib/python2.7/shutil.py", line 96, in copyfile
with open(src, 'rb') as fsrc:
IOError: [Errno 2] No such file or directory: 
'/var/tmp/weewx-steelseries-master/skins/ss/gauge-data.txt.tmpl'
Can someone tell where I have this wrong?

Raspbian Desktop running in a virtual machine.

All other extensions have installed normally.

WeeWx installed using setup.py, version 3.9.2, Python 2.7x

-- 
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/131dc366-fd77-48d5-a589-c84d53483e6f%40googlegroups.com.

[weewx-user] SDR Driver

[Michael]

Hello, 

I try to use the driver https://github.com/matthewwall/weewx-sdr.

With the command  sudo PYTHONPATH=/usr/share/weewx python 
/usr/share/weewx/user/sdr.py --cmd="rtl_433 -M utc -F json" it do work, but 
when I start weex, then I have this fault. What I have forgot?

Thanks for the help.

Best regards Michael

-- 
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/5dccda59-ba64-4984-a5f1-835e55213cbf%40googlegroups.com.

[weewx-user] PID File Location

[G Hammer]

I run Manjaro (Arch based) and saw this entry in the system log:

Apr 06 11:10:02 srvr systemd[1]: /etc/systemd/system/weewx.service:12: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/weewx.pid → /run/weewx.pid; please update the unit file 
accordingly.


It does not matter to the running of WeeWX, but thought I'd point it out.

WeeWX version: 4.0.0b17
setup.py install method
Python 2.7.17
systemd v: 244

-- 
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/93f880dc-5d69-4669-b24a-5a30da803429%40googlegroups.com.

Re: [weewx-user] Thanks a Lot Darksky (NOT!!)

[Steve2Q]

In my initial post I plainly said I didn't want this to be a discussion of 
Android v IOs or Apple v Microsoft. I was just saying i did not like the idea 
that a piece of useful software was going uni- platform.

-- 
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/0396d757-06c0-40a8-95e3-d014ed0c4b30%40googlegroups.com.

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

[Thomas Keffer]

As far as weewx is concerned, it's always been rainRate.

I don't know how Steelgauges works, but it's possible it's only used in
case-insensitive database queries.

-tk

On Mon, Apr 6, 2020 at 8:12 AM Phil Owers  wrote:

> This is interesting
> I have a pi running 3.9.2 (Python2) which runs OK with rainrate
> (Steelgauges 2.7.4) ( yes all lower case)
>
> But on a pi running v4.0.0.b18 (Python3) with Steelgauges 2.7.4 rainrate
> generates an error in the log which is corrected if its changed to rainRate.
>
> 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/8720d1b3-1d3f-4c78-9aec-5896b1b0e63e%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/CAPq0zEBL528s6%3D1SodmDsHQGDbMLW8h4aq-P3J7OaxKVfZumEQ%40mail.gmail.com.

[weewx-user] windrose does not appear in highcharts? how to get detailed plot from month?

[Astrid]

Hello!

I am using weewx 3.9.2, niculskin and highcharts.
All is working very well.
The only thing is, that the windrose does not appear
on the webpage.
I changed in skin.conf  from highcharts:

# Plot windSpeed or windGust ?
source = windSpeed # windGust
(because at gust I have only gustsspeed, no gustdir, but
wind I have both, windspeed and winddir.)

But no windrose appearce on webpage.

Have I to do additional changes?

And 2. question:

I want to get detailed highcharts from month too.
So I copy week.json.tmpl to month.json.tmpl,
change inside all words week->month.

At highchart skin.conf I add a

# Highcharts month json data
[[[MonthJSON]]]
template = json/month.json.tmpl

and I give at the generator an additional

search_list_extensions = user.highchartsSearchX.highchartsMinRanges, 
user.highchartsSearchX.highchartsWeek, 
user.highchartsSearchX.highchartsYear, 
user.highchartsSearchX.highchartsWindRose, 
user.highchartsSearchX.highchartsMonth,

but it causes:

wee_reports 
Using configuration file /etc/weewx/weewx.conf
Generating for all time
Traceback (most recent call last):
  File "/usr/share/weewx/weewx/reportengine.py", line 204, in run
obj.start()
  File "/usr/share/weewx/weewx/reportengine.py", line 300, in start
self.run()
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 157, in run
self.initExtensions(gen_dict[section_name])
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 199, in 
initExtensions
class_ = weeutil.weeutil._get_object(x)
  File "/usr/share/weewx/weeutil/weeutil.py", line 1116, in _get_object
"Module '%s' has no attribute '%s' when searching for '%s'" % 
(mod.__name__, part, module_class))
AttributeError: Module 'user.highchartsSearchX' has no attribute 
'highchartsMonth' when searching for 
'user.highchartsSearchX.highchartsMonth'

Is it possible, to get detailed highchartplot from month too?
How can I get this?

Regards, Astrid

-- 
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/b91ba7f8-0252-4605-865b-bacf89fb536a%40googlegroups.com.

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

[Phil Owers]

This is interesting
I have a pi running 3.9.2 (Python2) which runs OK with rainrate 
(Steelgauges 2.7.4) ( yes all lower case)

But on a pi running v4.0.0.b18 (Python3) with Steelgauges 2.7.4 rainrate 
generates an error in the log which is corrected if its changed to rainRate.

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/8720d1b3-1d3f-4c78-9aec-5896b1b0e63e%40googlegroups.com.

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

[steeple ian]

Phil,
Your are correct. In the skin.conf and the .tmpl file it is rainrate not
rainRate.
Ian

On Mon, 6 Apr 2020 at 15:23, Phil Owers  wrote:

> Gary
> Couldn't understand where rainrate came from so Just wee_extension --
> install steelseries-2.7.4tar.gz onto a spare pi and rainrate and not
> rainRate is in the ss/skin.conf file.
> Any chance somebody else could try just to make sure.
> 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/2cefabaa-9937-4f4c-a4b8-385964218a2e%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/CADASSaS%3DzUbQfrvk6yy5eDs4zZTToX5C9%2BGRTb9nzebhvjDHRQ%40mail.gmail.com.

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

[Phil Owers]

Gary
Couldn't understand where rainrate came from so Just wee_extension -- 
install steelseries-2.7.4tar.gz onto a spare pi and rainrate and not 
rainRate is in the ss/skin.conf file.
Any chance somebody else could try just to make sure.
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/2cefabaa-9937-4f4c-a4b8-385964218a2e%40googlegroups.com.

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

[Phil Owers]

Yep case sure does, log clear.  Apologies for that part no idea where that 
came from
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/e27589ca-7ac5-47f9-b4d4-914e26074e74%40googlegroups.com.

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

[Thomas Keffer]

As Gary noted, it's rainRate, not rainrate. Case matters.

-tk

On Mon, Apr 6, 2020 at 6:44 AM Phil Owers  wrote:

> Here is the log
>
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine: Caught
> unrecoverable exception in generator 'weewx.imagegenerator.ImageGenerator'
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
>   rainrate
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
>   Traceback (most recent call last):
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
> File "/home/weewx/bin/weewx/reportengine.py", line 197, in run
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
>   obj.start()
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
> File "/home/weewx/bin/weewx/reportengine.py", line 280, in start
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
>   self.run()
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
> File "/home/weewx/bin/weewx/imagegenerator.py", line 41, in run
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
>   self.genImages(self.gen_ts)
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
> File "/home/weewx/bin/weewx/imagegenerator.py", line 180, in
> genImages
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
>   aggregate_interval=aggregate_interval)
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
> File "/home/weewx/bin/weewx/xtypes.py", line 91, in get_series
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
>   raise weewx.UnknownType(obs_type)
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
>   weewx.UnknownType: rainrate
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
>   Generator terminated
>
> 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/a1fd90ae-45c5-42f7-a2a5-f4eb7a96f6cb%40googlegroups.com
> 

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

[Phil Owers]

Here is the log

Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 'weewx.imagegenerator.ImageGenerator'
Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine: 
  rainrate
Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine: 
  Traceback (most recent call last):
Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine: 
File "/home/weewx/bin/weewx/reportengine.py", line 197, in run
Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine: 
  obj.start()
Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine: 
File "/home/weewx/bin/weewx/reportengine.py", line 280, in start
Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine: 
  self.run()
Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine: 
File "/home/weewx/bin/weewx/imagegenerator.py", line 41, in run
Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine: 
  self.genImages(self.gen_ts)
Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine: 
File "/home/weewx/bin/weewx/imagegenerator.py", line 180, in 
genImages
Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine: 
  aggregate_interval=aggregate_interval)
Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine: 
File "/home/weewx/bin/weewx/xtypes.py", line 91, in get_series
Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine: 
  raise weewx.UnknownType(obs_type)
Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine: 
  weewx.UnknownType: rainrate
Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine: 
  Generator terminated

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/a1fd90ae-45c5-42f7-a2a5-f4eb7a96f6cb%40googlegroups.com.

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

[Phil Owers]

Gary
That worked and generated a gauge-data.txt file and it showed 0.2mm of 
hourly rain which is correct.

The log still has UnknownType rainrate when it try's to produce images

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/6f6735f2-7e2a-4f79-a337-e706844230c1%40googlegroups.com.

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

[Phil Owers]

It rained this morning and it registered ok on another page
Cant tell about the gauges as while the log reports this error the 
gauge-data.txt file does not generate.
Loading your new gauge-data file now
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/175840bb-2986-4711-abd9-cf4c5e8ae404%40googlegroups.com.

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

[gjr80]

Hi Phil,

Now I am confused. I can see the mechanism that is causing the failure. The 
following code in the template:

#set $hourlyrainTH = 0
#set $ThourlyrainTH = ''
#for $hour in $day.hours
#if $hour.rain.sum.raw > $hourlyrainTH
#set $hourlyrainTH = $hour.rain.sum.raw
#set $ThourlyrainTH = $hour.dateTime.format("%H:%M")
#end if
#end for

determines the maximum hourly rainfall for the day and the hour in which it 
occurred by iterating over each hour in the current day. But for some 
reason $hour.rain.sum.raw returns python value None for at least one of the 
hours. Hence the error message:

Apr  5 13:00:19 raspberrypi weewx[604] ERROR weewx.cheetahgenerator:  
Ignoring template /home/weewx/skins/ss/gauge-data.txt.tmpl
Apr  5 13:00:19 raspberrypi weewx[604] ERROR weewx.cheetahgenerator:  
Reason: '>' not supported between instances of 'NoneType' and 'int'

There are only two > comparisons in the gauge-data.txt.tmpl; the other one 
is not rain related and is not causing the error. This is confirmed by you 
commenting out all the rain related lines in the template. As far as I can 
tell the only way that $hour.rain.sum.raw would return None is if there was 
no rain data in the archive for that hour or if some other error was 
involved. Normally field rain is zero if there is no rain recorded so 
$hour.rain.sum.raw would return 0 if there was no rain. Hence my questions 
about missing data, but once you have a solid compete day of data you 
should be fine.

In any case, I have modified the gauge-data.txt.tmpl so that it will skip 
the comparision if $hour.rain.sum.raw is None. I suspect there is some 
other underlying issue but at least now the template will generate without 
error. I will give this some more thought as how to track down what else 
might be going on. To install the revised gauge-data.txt.tmpl:

1. rename your existing skins/ss/gauge-data.txt.tmpl to 
gauge-data_orig.txt.tmpl or some other name in case you need to revert
2. download the attached gauge-data.txt.tmpl in place of your current 
version
3. wait for the next report cycle and confirm in the log that gauge-data.txt 
was generated without error.

Just out of interest have you had any rain since installing 4.0? If so has 
it been recorded/displayed correctly by WeeWX on the SteelSeries gauges or 
other pages?

Oh, and regards the imagegenrator error:

Apr  5 13:00:19 raspberrypi weewx[604] ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 'weewx.imagegenerator.ImageGenerator'
Apr  5 13:00:19 raspberrypi weewx[604] ERROR weewx.reportengine: 
  rainrate
Apr  5 13:00:19 raspberrypi weewx[604] ERROR weewx.reportengine: 
  Traceback (most recent call last):
Apr  5 13:00:19 raspberrypi weewx[604] ERROR weewx.reportengine: 
File "/home/weewx/bin/weewx/reportengine.py", line 197, in run
Apr  5 13:00:19 raspberrypi weewx[604] ERROR weewx.reportengine: 
  obj.start()
Apr  5 13:00:19 raspberrypi weewx[604] ERROR weewx.reportengine: 
File "/home/weewx/bin/weewx/reportengine.py", line 280, in start
Apr  5 13:00:19 raspberrypi weewx[604] ERROR weewx.reportengine: 
  self.run()
Apr  5 13:00:19 raspberrypi weewx[604] ERROR weewx.reportengine: 
File "/home/weewx/bin/weewx/imagegenerator.py", line 41, in run
Apr  5 13:00:19 raspberrypi weewx[604] ERROR weewx.reportengine: 
  self.genImages(self.gen_ts)
Apr  5 13:00:19 raspberrypi weewx[604] ERROR weewx.reportengine: 
File "/home/weewx/bin/weewx/imagegenerator.py", line 180, in 
genImages
Apr  5 13:00:19 raspberrypi weewx[604] ERROR weewx.reportengine: 
  aggregate_interval=aggregate_interval)
Apr  5 13:00:19 raspberrypi weewx[604] ERROR weewx.reportengine: 
File "/home/weewx/bin/weewx/xtypes.py", line 91, in get_series
Apr  5 13:00:19 raspberrypi weewx[604] ERROR weewx.reportengine: 
  raise weewx.UnknownType(obs_type)
Apr  5 13:00:19 raspberrypi weewx[604] ERROR weewx.reportengine: 
  weewx.UnknownType: rainrate
Apr  5 13:00:19 raspberrypi weewx[604] ERROR weewx.reportengine: 
  Generator terminated

that will be due to the use of rainrate somewhere in the [ImageGenerator] 
stanza in skin.conf, the actual field name that WeeWX uses for rain rate is 
rainRate - case matters in this case.

Gary

On Monday, 6 April 2020 20:09:45 UTC+10, Phil Owers wrote:
>
> Hi Gary
> Returned gauge template to normal and restored rainrate in ss/skin.conf.
> Its still failing at the moment
> 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

[weewx-user] Re: ftp problems

['Richard O' via weewx-user]

Thanks everyone, everything is up and running. 

On Saturday, April 4, 2020 at 6:20:47 PM UTC+1, Richard O wrote:
>
> Thanks very much for your replies. It shall have a look at the manually 
> ftp'ing something.  Sounds like a longer term project!! I think though I 
> would really like to make sure I am getting the obvious right ie...
>
>   user = ftp.mywebsite.com
>
> password = 'xxx' (please note the password is in one set of 
> inverted commas..??)
>
> server = www.mywebsite.com 
> 
>   
>   # The ftp server name, e.g$
>
> path = /default.html# The destination directory, e.g., /weather
>
>
> Am I correct in putting the user = ftp.etc ?   The server as my web 
> address www.etc?  and also  /default as the path? I shall remove the '' and 
> see what happens 
>
>
> Many thanks for your help
>
>
> Richard
>
>
>
> On Saturday, April 4, 2020 at 5:41:19 PM UTC+1, Richard O wrote:
>>
>> Hi All
>>
>> I am having a problem getting my external website to work. Nothing 
>> downloads onto it. i have tried every combination I can think of!
>>
>> Hardware Davis vue with meteo pi and RPi
>> Software latest Raspbian lite and latest weewx
>> server software latest Nginx
>>
>> The program is running well and all works  well within the browser.
>>
>> The log reads as follows
>>
>> Apr  4 17:00:54 ro weewx[4537]: imagegenerator: Generated 24 images for 
>> StandardReport in 13.20 seconds
>>
>> Apr  4 17:00:54 ro weewx[4537]: copygenerator: copied 14 files to 
>> /var/www/html/weewx
>>
>> Apr  4 17:00:54 ro weewx[4537]: reportengine: Running report 'FTP'
>>
>> Apr  4 17:00:54 ro weewx[4537]: reportengine: Found configuration file 
>> /etc/weewx/skins/Ftp/skin.conf for report 'FTP'
>>
>> Apr  4 17:00:54 ro weewx[4537]: ftpupload: Attempting connection to 
>> www.xx.com
>>
>> Apr  4 17:01:14 ro weewx[4537]: ftpupload: Unable to connect or log into 
>> server : timed out
>>
>> Apr  4 17:01:34 ro weewx[4537]: ftpupload: Unable to connect or log into 
>> server : timed out
>>
>> Apr  4 17:01:54 ro weewx[4537]: ftpupload: Unable to connect or log into 
>> server : timed out
>>
>> Apr  4 17:01:54 ro weewx[4537]: ftpupload: Attempted 3 times to connect 
>> to server www.x.com. Giving up.
>>
>> Apr  4 17:01:54 ro weewx[4537]: ftpgenerator: ftp'd 0 files in 60.12 
>> seconds
>>
>> Apr  4 17:01:54 ro weewx[4537]: reportengine: Report 'RSYNC' not 
>> enabled. Skipping.
>>
>> Apr  4 17:06:52 ro weewx[4537]: vantage: Requesting 200 LOOP packets.
>>
>> Apr  4 17:06:52 ro weewx[4537]: vantage: Gentle wake up of console 
>> successful
>>
>> Apr  4 17:13:30 ro weewx[4537]: vantage: Requesting 200 LOOP packets.
>>
>> Apr  4 17:13:30 ro weewx[4537]: vantage: Gentle wake up of console 
>> successful
>>
>> Apr  4 17:17:01 ro CRON[4807]: (root) CMD (   cd / && run-parts --report 
>> /etc/cron.hourly)
>>
>>
>> My config file reads like this...
>>
>>
>>  [[FTP]]
>>
>> # FTP'ing the results to a webserver is treated as just another 
>> report,
>>
>> # albeit one with an unusual report generator!
>>
>> skin = Ftp
>>
>>
>> # If you wish to use FTP, set "enable" to "true", then
>>
>> # fill out the next four lines.
>>
>> # Use quotes around passwords to guard against parsing errors.
>>
>> enable = true
>>
>> user = ftp.mywebsite.com
>>
>> password = 'xxx' (please note the password is in one set of 
>> inverted commas..??)
>>
>> server = www.mywebsite.com# The ftp server name, e.g$
>>
>> path = /default.html# The destination directory, e.g., 
>> /weather
>>
>>
>> # Set to True for an FTP over TLS (FTPS) connection. Not all 
>> servers
>>
>> # support this.
>>
>> secure_ftp = False
>>
>>
>> I think it may be just as simple as one of the above four being inputted 
>> wrong but I have tried every combination!!
>>
>>
>> My web hosting is with fasthost who tell me to  Ensure that you upload 
>> your files to the HTDOCS folder
>>
>>
>> I understand from their web site that any linux system should be sent to 
>> /default.html
>>
>>
>> I am not computer literate and I am surprised how far I have travelled so 
>> far but I just cant work this one out. Any thoughts anyone?? Thanks Richard
>>
>

-- 
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/1418fee0-afbe-4362-803f-e1da29e4bd0f%40googlegroups.com.

[weewx-user] Re: Removed an erroneous daily rainfall reading from the database and now its back after reboot

[Muireadach O Connor]

Thanks Gary,

I found the source of my issue, I was logging the output of my putty 
session to a file in case I needed to put the steps taken on here as per 
your suggestions.
To show exactly what and where i was editing i did a "locate" command on 
the weewx.sdb file and only then realised I was editing the wrong one, I 
was actually editing an old backup in the wrong location, hense it not 
working! Doh!

Thanks for offering to help, you already did in a roundabout way in the end!

On Friday, April 3, 2020 at 4:20:20 PM UTC+1, Muireadach O Connor wrote:
>
> Hi guys,
>
> I'm struggling to understand what I'm doing wrong here.
>
> I want to remove a daily reading of 134mm rain from February 2013 as its 
> bothering me in my records page. I had cleaned the rain gauge that day and 
> never got around to correcting it.
> I'd previously amended a max rainRate figure from the database without too 
> much issue so thought this would be the same but its proving much more 
> troublesome.
>
> I removed it using :
>
> update archive set rain=NULL where rain > 4; (db in imperial)
>
> Next made a  new copy of this new database
>
> Then..
>
> sudo wee_database --drop-daily
> sudo wee_database weewx.conf --rebuild-daily
>
> then ran :
>
> wee_reports --config=/etc/weewx/weewx.conf
>
> However the records webpage on my pi (reports folder) in still showed the 
> old value in there.
>
> At this stage I figured maybe its cached in memory so stopped the WeeWX 
> service and restarted the raspberry pi
>
> Now the old value is back in the database again (/shakes fist at cloud)
> I've looked at my amended copy and the latest one and the old maximum 
> daily reading is definitely back and definitely was removed.
>
> I'm guessing this is being pulled from the console somehow, should I have 
> cleared it also there also before restarting?
> If not, anyone any ideas how to fix this?
>
>

-- 
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/520ab5e9-03a8-461d-802f-12550449d5d1%40googlegroups.com.

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

[Phil Owers]

Hi Gary
Returned gauge template to normal and restored rainrate in ss/skin.conf.
Its still failing at the moment
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/41b9d852-ef8a-4c07-8b4f-b156f72504b2%40googlegroups.com.