[weewx-user] Probleme WMR200

[mtev...@gmail.com]

Hello.
I have a problem. Weewx crashes regularly. Here are the log.
Do you have any ideas ?

Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.drivers.wmr200: 
open_device() Unable to claim USB interface. Reason: [Errno 16] Resource 
busy 
Dec 15 21:30:42 Nas weewx[495153] ERROR weewx.engine: Import of driver 
failed: [Errno 16] Resource busy () 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
 Traceback (most recent call last): 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
"/usr/share/weewx/weewx/drivers/wmr200.py", line 193, in open_device 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
 self.handle.claimInterface(self.interface) 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
"/usr/lib/python3/dist-packages/usb/legacy.py", line 230, in claimInterface 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
 util.claim_interface(self.dev, interface) 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
"/usr/lib/python3/dist-packages/usb/util.py", line 205, in claim_interface 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
 device._ctx.managed_claim_interface(device, interface) 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
"/usr/lib/python3/dist-packages/usb/core.py", line 102, in wrapper 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
 return f(self, *args, **kwargs) 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
"/usr/lib/python3/dist-packages/usb/core.py", line 167, in 
managed_claim_interface 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
 self.backend.claim_interface(self.handle, i) 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
"/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 811, in 
claim_interface 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
 _check(self.lib.libusb_claim_interface(dev_handle.handle, intf)) 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
"/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 595, in 
_check 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
 raise USBError(_strerror(ret), ret, _libusb_errno[ret]) 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
 usb.core.USBError: [Errno 16] Resource busy 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:    
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:   During 
handling of the above exception, another exception occurred: 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:    
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
 Traceback (most recent call last): 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
"/usr/share/weewx/weewx/engine.py", line 109, in setupStation 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
 self.console = loader_function(config_dict, self) 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
"/usr/share/weewx/weewx/drivers/wmr200.py", line 58, in loader 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
 return WMR200(**config_dict[DRIVER_NAME]) 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
"/usr/share/weewx/weewx/drivers/wmr200.py", line 1468, in __init__ 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
 self.usb_device.open_device() 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
"/usr/share/weewx/weewx/drivers/wmr200.py", line 196, in open_device 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
 raise weewx.WakeupError(exception) 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
 weewx.WakeupError: [Errno 16] Resource busy 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL __main__: Unable to load driver: 
[Errno 16] Resource busy 
Dec 15 21:30:42 Nas weewx[495153] CRITICAL __main__:   Exiting...

-- 
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/6112d4f8-8e15-429a-96d1-6ecd7ce5a1ean%40googlegroups.com.

[weewx-user] Re: Probleme WMR200

[Mark Jenks]

Mine did that once in awhile, and I never did figure out why..  I just 
wrote a script to watch it and restart it, if it saw "Exiting.."

# more watch-weewx.sh
#!/bin/bash
service=weewx.service
if (( $(/usr/bin/systemctl status $service | grep running | wc -l) < 1 ))
then
echo “$service was down and was restarted!!!”
systemctl stop $service
systemctl start $service
fi
if (( $(/usr/bin/systemctl status $service | grep "Exiting..." | wc -l) > 0 
))
then
echo “$service Exited and was restarted!!!”
systemctl stop $service
systemctl start $service
fi


On Tuesday, December 15, 2020 at 4:36:36 AM UTC-6 mtev...@gmail.com wrote:

> Hello.
> I have a problem. Weewx crashes regularly. Here are the log.
> Do you have any ideas ?
>
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.drivers.wmr200: 
> open_device() Unable to claim USB interface. Reason: [Errno 16] Resource 
> busy 
> Dec 15 21:30:42 Nas weewx[495153] ERROR weewx.engine: Import of driver 
> failed: [Errno 16] Resource busy () 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  Traceback (most recent call last): 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/share/weewx/weewx/drivers/wmr200.py", line 193, in open_device 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  self.handle.claimInterface(self.interface) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/lib/python3/dist-packages/usb/legacy.py", line 230, in claimInterface 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  util.claim_interface(self.dev, interface) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/lib/python3/dist-packages/usb/util.py", line 205, in claim_interface 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  device._ctx.managed_claim_interface(device, interface) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/lib/python3/dist-packages/usb/core.py", line 102, in wrapper 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  return f(self, *args, **kwargs) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/lib/python3/dist-packages/usb/core.py", line 167, in 
> managed_claim_interface 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  self.backend.claim_interface(self.handle, i) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 811, in 
> claim_interface 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  _check(self.lib.libusb_claim_interface(dev_handle.handle, intf)) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 595, in 
> _check 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  raise USBError(_strerror(ret), ret, _libusb_errno[ret]) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  usb.core.USBError: [Errno 16] Resource busy 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:    
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:   During 
> handling of the above exception, another exception occurred: 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:    
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  Traceback (most recent call last): 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/share/weewx/weewx/engine.py", line 109, in setupStation 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  self.console = loader_function(config_dict, self) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/share/weewx/weewx/drivers/wmr200.py", line 58, in loader 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  return WMR200(**config_dict[DRIVER_NAME]) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/share/weewx/weewx/drivers/wmr200.py", line 1468, in __init__ 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  self.usb_device.open_device() 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/share/weewx/weewx/drivers/wmr200.py", line 196, in open_device 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  raise weewx.WakeupError(exception) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  weewx.WakeupError: [Errno 16] Resource busy 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL __main__: Unable to load 
> driver: [Errno 16] Resource busy 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL __main__:   Exiting...
>

-- 
You rece

Re: [weewx-user] Probleme WMR200

[Tom Keffer]

Issue #578  addresses this
problem with the WMR200. Unfortunately, no fix has been found.

What kind of computer are you using? A Raspberry Pi? Something else?

On Tue, Dec 15, 2020 at 2:36 AM mtev...@gmail.com 
wrote:

> Hello.
> I have a problem. Weewx crashes regularly. Here are the log.
> Do you have any ideas ?
>
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.drivers.wmr200:
> open_device() Unable to claim USB interface. Reason: [Errno 16] Resource
> busy
> Dec 15 21:30:42 Nas weewx[495153] ERROR weewx.engine: Import of driver
> failed: [Errno 16] Resource busy ()
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: 
>  Traceback (most recent call last):
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File
> "/usr/share/weewx/weewx/drivers/wmr200.py", line 193, in open_device
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: 
>  self.handle.claimInterface(self.interface)
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File
> "/usr/lib/python3/dist-packages/usb/legacy.py", line 230, in claimInterface
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: 
>  util.claim_interface(self.dev, interface)
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File
> "/usr/lib/python3/dist-packages/usb/util.py", line 205, in claim_interface
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: 
>  device._ctx.managed_claim_interface(device, interface)
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File
> "/usr/lib/python3/dist-packages/usb/core.py", line 102, in wrapper
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: 
>  return f(self, *args, **kwargs)
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File
> "/usr/lib/python3/dist-packages/usb/core.py", line 167, in
> managed_claim_interface
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: 
>  self.backend.claim_interface(self.handle, i)
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File
> "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 811, in
> claim_interface
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: 
>  _check(self.lib.libusb_claim_interface(dev_handle.handle, intf))
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File
> "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 595, in
> _check
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: 
>  raise USBError(_strerror(ret), ret, _libusb_errno[ret])
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: 
>  usb.core.USBError: [Errno 16] Resource busy
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:   During
> handling of the above exception, another exception occurred:
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: 
>  Traceback (most recent call last):
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File
> "/usr/share/weewx/weewx/engine.py", line 109, in setupStation
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: 
>  self.console = loader_function(config_dict, self)
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File
> "/usr/share/weewx/weewx/drivers/wmr200.py", line 58, in loader
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: 
>  return WMR200(**config_dict[DRIVER_NAME])
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File
> "/usr/share/weewx/weewx/drivers/wmr200.py", line 1468, in __init__
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: 
>  self.usb_device.open_device()
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File
> "/usr/share/weewx/weewx/drivers/wmr200.py", line 196, in open_device
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: 
>  raise weewx.WakeupError(exception)
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: 
>  weewx.WakeupError: [Errno 16] Resource busy
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL __main__: Unable to load
> driver: [Errno 16] Resource busy
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL __main__:   Exiting...
>
> --
> 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/6112d4f8-8e15-429a-96d1-6ecd7ce5a1ean%40googlegroups.com
> 

Re: [weewx-user] Re: wee_import error using Weathercloud downloaded .csv

[Will Wray]

Hi Gary,

I really appreciate the response. I moved the file out of the /var/tmp/
directly and edited it from my home directory and it seems to be reading
better now. There is something odd going on with my Rpi which is unrelated
to this issue. I apologize for the screenshot, I'm doing this through a
digital ocean console which doesn't allow me to copy and paste. Thank you
again for your help!

Will

On Mon, Dec 14, 2020 at 7:28 PM gjr80  wrote:

> Oh, and one more thing. Would appreciate if you could post screen captures
> as text rather than images. Images are often hard to read, especially on
> mobile devices.
>
> Gary
>
> On Tuesday, 15 December 2020 at 10:27:15 UTC+10 gjr80 wrote:
>
>> Hi,
>>
>> It looks like you may have a degree symbol character (0xb8) in your
>> import data and that is causing the python CSV reader to fail. Open your
>> source data file and have a look. If there is a degree symbol in there you
>> should be able to delete it/them and save the file. Probably worth while
>> looking for any other symbols as well. If you cannot find a degree symbol
>> in the source data could you please post the source data file or email it
>> to me and I will see what I can find.
>>
>> Gary
>>
>> On Tuesday, 15 December 2020 at 02:54:25 UTC+10 will...@gmail.com wrote:
>>
>>> Hi all,
>>>
>>> I apologize if this was already asked. I did a quick search and didn't
>>> find anything. I'm trying to import data using wee_import from a downloaded
>>> file from Weathercloud. I lost my internal temperature data and I'm trying
>>> to rebuild it.
>>>
>>> I'm getting an error when trying to import using a conf file called
>>> weathercloud.conf that I created using the example for CSV in the
>>> /etc/weewx/import directory.
>>>
>>> I'm using the command
>>>
>>> sudo wee_import --import-config/home/wwray/weathercloud.conf --dry-run
>>> --verbose
>>>
>>> I'm getting the following error.
>>> [image: Screenshot 2020-12-14 115135.jpg]
>>>
>>> I have tried with ascii and the source_encoding = ascii  I've tried
>>> editing the file in notepad++ to convert to utf-8 and I've even opened it
>>> up in a hex editor online. I can't see any reason why it won't import.
>>>
>>> Any help would be appreciated.
>>>
>>> Thanks,
>>> Will
>>>
>>>
>>> --
> 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/KlJ9arvEk-8/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/e988b9b7-e40c-446c-95d6-67e83b54e81fn%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/CAN4jKGzYjT4MkqjT5xEH1kaD2CcoVm-uhxVgP5nxcECxdS5Z0g%40mail.gmail.com.

[weewx-user] "Grassland Temperature Sum" (or how it is called in English, german "Grünlandtemperatursumme" (GTS))

[Karen K]

I found the aggregation type "growing degree day" ("growdeg"). 

There is a special version of that in Europe. In Germany it is called 
"Grünlandtemperatursumme". I found no translation to English. The word in 
the subject is translated word by word.

It is based on the daily average temperature, as growing degree day is. The 
base temperature is 0 degrees centigrade (32 degrees Fahrenheit).

   - In January, all the values are multiplied by 0.5.
   - In February, all the values are multiplied by 0.75.
   - Form March on, the values are used as is.
   
The sum is calculated from Jan. 1st to May 31st.

The day, when the value exceeds 200 in spring (if calculated in 
centigrade), is considered the start of growing of the plants.

Some german weather networks ask for those values (sum and date).

It seems to me that the actual aggregation function does not cover that 
version.



-- 
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/422873ce-dcbd-4e15-9748-573af73f6ccfn%40googlegroups.com.

Re: [weewx-user] Re: Installation at remote site using RPi and VNC?

[Sunray]

Progress report : Success!

I was able to visit the cabin today for two hours (cold!) and installed the 
RPI  hardware. After some headscratching due to a security camera on the 
same LAN, I was able to establish a RealVNC Connect session between the RPI 
connected by cable on the cabin's LAN and my laptop running on my 
cellphone's wifi hotspot. This enabled me to find out all necessary IP 
addresses including the Vantage Vue's Weatherlink IP address, which I 
needed for the WeeWx setup. 

I then did the reconfiguration of WeeWx from Simulator to Vantage Vue but 
did not manage to get a html update. A reduction of the Vantage's archiving 
interval from 2 hours to 5 minutes did not help. I could, however, using 
the weewxd command see that the LOOP packets now originated from the 
weather station and not simulated. So it looked promising!

Back home, error messages suggested database errors. After some study I 
changed in the config file: 

   - Driver model_type changed from 2 to 1 
   - Archive record generation from hardware to software. 

After these changes the html generation works fine!

 

Thank you everyone for your advice and suggestions! I have one immediate 
issue - the wind direction graphs only display on a 16-point scale (22.5 
degrees intervals). 

My next project will be to try to implement a realtime wind display 
(displaying each LOOP packet's data - advice welcome!) and to publish the 
weather data in a safe way.

On Thursday, 10 December 2020 at 21:49:56 UTC+2 vince wrote:

> Indeed.   I used to fail2ban ssh attempts from other than my home ip 'one' 
> address.  I had over 100 countries hitting me, with the vast majority the 
> usual APT countries we've all read about.   That said, geoip fencing is an 
> inexact science and it's not that hard to make it look like a different 
> source address.
>
> I only let in US+CA+AU to my website due to too many attacks, by adding 
> geoip fencing to nginx which is pretty easy to set up.   I also have a 
> custom fail2ban to ban anybody trying to look for php/wordpress stuff as 
> that's a big attack vector by the bots and script kiddies attacking 
> websites.
>
> I've locked myself out of my AWS box a couple times via messing up 
> fail2ban blocks of ssh incoming, requiring me to just nuke+rebuild it, so I 
> probably need another solution there.   Thinking of just permitting my LAN 
> ip there once again, if I can come up with a second path in just-in-case.  
> Maybe I'll try WireGuard there and let my home box tunnel into the cloud 
> VM.  Maybe.  I'll have to think about it some more.
>
> It's an arms race and it's tiring even needing to fight it...
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f6b284ff-246b-4f14-9e4a-a55ff3b2667dn%40googlegroups.com.

[weewx-user] Re: "Grassland Temperature Sum" (or how it is called in English, german "Grünlandtemperatursumme" (GTS))

[Ton vanN]

Your observation is correct: "Grünland' is different from the '*general*' 
GrowingDegreeDays:
wikipedia explains as per https://en.wikipedia.org/wiki/Growing_degree-day 
With your observation if fact you open can of worms, because a large amount 
of variations of GrowingDegree Days related to different animals, insects 
and plants.

;-) Each country has it's variations as well .


Op dinsdag 15 december 2020 om 17:13:50 UTC+1 schreef kk44...@gmail.com:

> I found the aggregation type "growing degree day" ("growdeg"). 
>
> There is a special version of that in Europe. In Germany it is called 
> "Grünlandtemperatursumme". I found no translation to English. The word in 
> the subject is translated word by word.
>
> It is based on the daily average temperature, as growing degree day is. 
> The base temperature is 0 degrees centigrade (32 degrees Fahrenheit).
>
>- In January, all the values are multiplied by 0.5.
>- In February, all the values are multiplied by 0.75.
>- Form March on, the values are used as is.
>
> The sum is calculated from Jan. 1st to May 31st.
>
> The day, when the value exceeds 200 in spring (if calculated in 
> centigrade), is considered the start of growing of the plants.
>
> Some german weather networks ask for those values (sum and date).
>
> It seems to me that the actual aggregation function does not cover that 
> version.
>
>
>
>

-- 
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/09d811ed-e5fd-4843-969c-695c85edc579n%40googlegroups.com.

[weewx-user] Installation of version 4.2.0

[Ton vanN]

Tried a fresh installation of weewx on Raspberry3B+/RaspianBuster.
Stuck, being unable to install some prerequisites.
Prior to install of main program of weewx already difficulties, but very 
clear message when running the install-instruction from Raspberry's CLI:
apt-get install weewx

Then reports (with related dutch text that installation not possible):
python-configobj (>= 4.5) maar het is niet installeerbaar
python-cheetah (>= 2.0) maar het is niet installeerbaar
python-usb (>= 0.4) maar het is niet installeerbaar

Looked in the manuals and tried the various options, and looked in this 
group, but not yet seen a remedy:

*a workaround available for installation of these 3 prerequisites?Is this 
effect version-dependent, and might install of older version better work?*

-- 
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/f5f85a12-8982-4283-807b-8efa7d4b9a72n%40googlegroups.com.

[weewx-user] Re: Installation of version 4.2.0

[vince]

Please post the exact transcript of everything you did and what the 
computer returned.

It's fine if you would like to google translate the transcript into English.


-- 
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/f382c114-e17f-465a-a338-831b3fc0cfdcn%40googlegroups.com.

Re: [weewx-user] Re: Installation at remote site using RPi and VNC?

[Sunray]

Correction, the wind direction problem affected only the data archived in 
the WLIP logger before Weewx came on line. 

But another issue is that the Weewx traffic seems to block the WLIP logger 
from doing its regular uploading of data to Davis Weatherlink.com. Any 
advice on this ?

On Tuesday, 15 December 2020 at 18:39:22 UTC+2 Sunray wrote:

> Progress report : Success!
>
> I was able to visit the cabin today for two hours (cold!) and installed 
> the RPI  hardware. After some headscratching due to a security camera on 
> the same LAN, I was able to establish a RealVNC Connect session between the 
> RPI connected by cable on the cabin's LAN and my laptop running on my 
> cellphone's wifi hotspot. This enabled me to find out all necessary IP 
> addresses including the Vantage Vue's Weatherlink IP address, which I 
> needed for the WeeWx setup. 
>
> I then did the reconfiguration of WeeWx from Simulator to Vantage Vue but 
> did not manage to get a html update. A reduction of the Vantage's archiving 
> interval from 2 hours to 5 minutes did not help. I could, however, using 
> the weewxd command see that the LOOP packets now originated from the 
> weather station and not simulated. So it looked promising!
>
> Back home, error messages suggested database errors. After some study I 
> changed in the config file: 
>
>- Driver model_type changed from 2 to 1 
>- Archive record generation from hardware to software. 
>
> After these changes the html generation works fine!
>
>  
>
> Thank you everyone for your advice and suggestions! I have one immediate 
> issue - the wind direction graphs only display on a 16-point scale (22.5 
> degrees intervals). 
>
> My next project will be to try to implement a realtime wind display 
> (displaying each LOOP packet's data - advice welcome!) and to publish the 
> weather data in a safe way.
>
> On Thursday, 10 December 2020 at 21:49:56 UTC+2 vince wrote:
>
>> Indeed.   I used to fail2ban ssh attempts from other than my home ip 
>> 'one' address.  I had over 100 countries hitting me, with the vast majority 
>> the usual APT countries we've all read about.   That said, geoip fencing is 
>> an inexact science and it's not that hard to make it look like a different 
>> source address.
>>
>> I only let in US+CA+AU to my website due to too many attacks, by adding 
>> geoip fencing to nginx which is pretty easy to set up.   I also have a 
>> custom fail2ban to ban anybody trying to look for php/wordpress stuff as 
>> that's a big attack vector by the bots and script kiddies attacking 
>> websites.
>>
>> I've locked myself out of my AWS box a couple times via messing up 
>> fail2ban blocks of ssh incoming, requiring me to just nuke+rebuild it, so I 
>> probably need another solution there.   Thinking of just permitting my LAN 
>> ip there once again, if I can come up with a second path in just-in-case.  
>> Maybe I'll try WireGuard there and let my home box tunnel into the cloud 
>> VM.  Maybe.  I'll have to think about it some more.
>>
>> It's an arms race and it's tiring even needing to fight it...
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/77f28840-c014-495c-9984-425303a6e6cfn%40googlegroups.com.

[weewx-user] yet another question to GW1000 api driver mapping

[Vetti52]

Well, I started this conversation already at another thread 
(https://groups.google.com/g/weewx-user/c/ua0JjTp1DW8/m/AFGZf7AyAgAJ), 
concerning wind.gust.dir in version 4.2.0. As TK managed to solve the main 
problem, there is still the other part unsolved. So, I want to move this 
topic into a new thread, knowing, that there were similar questions during 
the last months, whicht could help only partially.

I am not able to change from interceptor's ecowitt-client to GW1000 without 
loss of some data. Gary provided the crucial hints in the thread mentioned 
above, which brought me almost to the successful end of this story. But 
still one thing remains to be much too complicated for me:

According to Gary's explanations, I introduced an extra stanza in 
weewx.conf:
# Options for extension 'GW1000'
[GW1000]
driver = user.gw1000
[[field_map_extensions]]
# WeeWX field name = GW1000 field name
rainEvent = rainevent
wh65_battery = wh65_batt

I took these two values from the original ecowitt-client mappings in 
interceptor.py:

DEFAULT_SENSOR_MAP = {
...
   'rainEvent': 'rain_event',
'UV': 'uv',

where the Weewx field is on the left and the Ecowitt-client field to the 
right side. 
And here is the other map in weewx.conf:

[Interceptor]
driver = user.interceptor
device_type = ecowitt-client
mode = listen
port = 9000
[[sensor_map_extensions]]
txBatteryStatus = wh65_battery

Here, the Ecowitt client field is at the left and thus the Weewx field 
should be to the right.
The GW1000 field map extension works! But this is true only for rainEvent, 
no for the battery status. I had a look into sensors.inc in the seasons 
skin:

#def get_battery_status($x)
#if $x == 0
$x: GOOD
#else
$x: LOW
#end if
#end def

and found out, that, using the ecowitt-client, $wx == 0.0, but with GW1000 
it does not even exist, no value at all. Although I trend to assume, that I 
understand now, how the mappings work (thanks to Gary), I am still helpless 
to map the battery sensor properly.

Hopefully someone can bring me on the right track.

--ph

-- 
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/867997ae-14fe-4a90-a78c-6e83928cc1f2n%40googlegroups.com.

[weewx-user] weewx-aqi plugin

[miso k]

Hello,
I am trying to install weewx AQI plugin
https://github.com/jonathankoren/weewx-aqi

My weewx is 4.2.0 with extended database, pm10_0 and pm2_5 values.
I dont have weewx-purpleair, but custom sensor, which fills out the 
database through FilePile. So I modified the weewx.conf to:

# Options for extension 'aqi'
[AqiService]
[[standard]]
data_binding = aqi_binding
standard = user.aqi.us.NowCast
[[air_sensor]]
data_binding = wx_binding
usUnits = usUnits
dateTime = dateTime
#temp = extraTemp1
#pressure = pressure
pm2_5 = pm2_5
pm10_0 = pm10_0

but I got the errors:

Dec 15 23:07:06 WeeWX /weewxd: AqiService: ValueError AQI calculation for 
pm2_5 on 1608069960 failed: NowCast AQI could not be calculated for the 
observations. Too many missing. Missing 2, which meets or exceeding the 
limit of 1
Dec 15 23:07:06 WeeWX /weewxd: AqiService: ValueError AQI calculation for 
pm10_0 on 1608069960 failed: NowCast AQI could not be calculated for the 
observations. Too many missing. Missing 2, which meets or exceeding the 
limit of 1
Dec 15 23:07:06 WeeWX /weewxd: AqiService: not storing record for dateTime 
1608069960

what I have done wrong?

Thanks, 
Michal, Slovakia

-- 
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/641ba9ea-1e2c-4899-9588-a307177fac80n%40googlegroups.com.

[weewx-user] Re: yet another question to GW1000 api driver mapping

[gjr80]

Some comments below. Hopefully it gives you a process to work through to 
identify your problem.

Gary

On Wednesday, 16 December 2020 at 06:37:40 UTC+10 Vetti52 wrote:

> Well, I started this conversation already at another thread (
> https://groups.google.com/g/weewx-user/c/ua0JjTp1DW8/m/AFGZf7AyAgAJ), 
> concerning wind.gust.dir in version 4.2.0. As TK managed to solve the main 
> problem, there is still the other part unsolved. So, I want to move this 
> topic into a new thread, knowing, that there were similar questions during 
> the last months, whicht could help only partially.
>
> I am not able to change from interceptor's ecowitt-client to GW1000 
> without loss of some data. Gary provided the crucial hints in the thread 
> mentioned above, which brought me almost to the successful end of this 
> story. But still one thing remains to be much too complicated for me:
>
> According to Gary's explanations, I introduced an extra stanza in 
> weewx.conf:
> # Options for extension 'GW1000'
> [GW1000]
> driver = user.gw1000
> [[field_map_extensions]]
> # WeeWX field name = GW1000 field name
> rainEvent = rainevent
> wh65_battery = wh65_batt
>
> I took these two values from the original ecowitt-client mappings in 
> interceptor.py:
>
> DEFAULT_SENSOR_MAP = {
> ...
>'rainEvent': 'rain_event',
> 'UV': 'uv',
>
> where the Weewx field is on the left and the Ecowitt-client field to the 
> right side. 
> And here is the other map in weewx.conf:
>
> [Interceptor]
> driver = user.interceptor
> device_type = ecowitt-client
> mode = listen
> port = 9000
> [[sensor_map_extensions]]
> txBatteryStatus = wh65_battery
>
> Here, the Ecowitt client field is at the left and thus the Weewx field 
> should be to the right.
>

Not quite, the sensor map extensions in weewx.conf for the interceptor 
driver are in the format:

WeeWX field name = interceptor field name

This convention has been used by the WeeWX development team now for some 
time in all contemporary drivers with some form of sensor/field mapping. 
Note, drivers developed by others may or may not use the same convention.
 

> The GW1000 field map extension works! But this is true only for rainEvent, 
> no for the battery status. I had a look into sensors.inc in the seasons 
> skin:
>
> #def get_battery_status($x)
> #if $x == 0
> $x: GOOD
> #else
> $x: LOW
> #end if
> #end def
>
> and found out, that, using the ecowitt-client, $wx == 0.0, but with GW1000 
> it does not even exist, no value at all. Although I trend to assume, that I 
> understand now, how the mappings work (thanks to Gary), I am still helpless 
> to map the battery sensor properly.
>
> Hopefully someone can bring me on the right track.
>

I think you need to be taking a step back working through this in a 
methodical manner. Data that goes from sensor to web page is processed by 
many different parts of WeeWX each of which could be the cause of your 
problem. The driver reads sensor data and emits data in loop packets, the 
StdArchive service accumulates these loop packets and emits archive 
records, the StdReport service then uses Cheetah and a system of tags to 
present this data in a report. At the moment you are looking at the very 
last step in the process and the result is not what you expect. To 
troubleshoot you need to work through the process from driver onwards.

First up, is the GW1000 driver actually emitting reinvent and wh65_batt 
fields. This can be checked by running the GW1000 driver directly with the 
--live-data command line option, something like:

$ PYTHONPATH=/home/weewx/bin python -m user.gw1000 --live-data

Note you may need to use PYTHONPATH=/usr/share/weewx if WeeWX was installed 
as a package and you may need to explicitly specify the python version to 
run by replacing python with python2 or python3.

The command should result all sensor data available to the GW1000 being 
displayed on the console. The data is raw data from the console before any 
mapping, so you should be looking for rainevent and wh65_batt fields. Do 
they exist, if so good, if not then the GW1000 driver is not obtaining data 
from the relevant sensor.

If you have rainevent and wh65_batt fields the next thing to check is the 
operation of the field mapping. The field mapping occurs in the GW1000 
driver so you need to look at the loop packets emitted by the GW1000 driver 
to see what they contain. If you have the following in 
[[field_map-extensions]]:

[[field_map_extensions]]
rainEvent = rainevent
wh65_battery = wh65_batt
 
Then you should see fields rainEvent and wh65_battery in the loop packets 
emitted by the GW1000 driver. The easiest way to do this is to run WeeWX 
directly  and 
observe the loop packet output (lines beginning with LOOP:) on the console. 
Do the loop packets include field rainEvent and wh65_battery? If so the 
field mapping e

Re: [weewx-user] "Grassland Temperature Sum" (or how it is called in English, german "Grünlandtemperatursumme" (GTS))

[Tom Keffer]

Aggregates like heating, cooling, or growing degree-days are not hardwired
into WeeWX. They are actually XType extensions
. You are
free to define your own extension, or even override the existing
definitions.

Take a look at class AggregateHeatCool
, and
follow the pattern.

-tk

On Tue, Dec 15, 2020 at 8:13 AM Karen K  wrote:

> I found the aggregation type "growing degree day" ("growdeg").
>
> There is a special version of that in Europe. In Germany it is called
> "Grünlandtemperatursumme". I found no translation to English. The word in
> the subject is translated word by word.
>
> It is based on the daily average temperature, as growing degree day is.
> The base temperature is 0 degrees centigrade (32 degrees Fahrenheit).
>
>- In January, all the values are multiplied by 0.5.
>- In February, all the values are multiplied by 0.75.
>- Form March on, the values are used as is.
>
> The sum is calculated from Jan. 1st to May 31st.
>
> The day, when the value exceeds 200 in spring (if calculated in
> centigrade), is considered the start of growing of the plants.
>
> Some german weather networks ask for those values (sum and date).
>
> It seems to me that the actual aggregation function does not cover that
> version.
>
>
>
> --
> 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/422873ce-dcbd-4e15-9748-573af73f6ccfn%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/CAPq0zEA%3DN-bJVwNNaBvtCSt7K-yabEWcp7Yz0-5yOzEc%2BZ2ohw%40mail.gmail.com.

Re: [weewx-user] Probleme WMR200

[Mark Jenks]

Mine did it with Python 2, HTPC Intel MB with Fedora on it.  I never did 
notice the USB changing, but it's very possible.

I'd go back and check, but I'm now on a Vantage Vue..  :)

On Tuesday, December 15, 2020 at 6:11:45 AM UTC-6 tke...@gmail.com wrote:

> Issue #578  addresses this 
> problem with the WMR200. Unfortunately, no fix has been found.
>
> What kind of computer are you using? A Raspberry Pi? Something else?
>
> On Tue, Dec 15, 2020 at 2:36 AM mtev...@gmail.com  
> wrote:
>
>> Hello.
>> I have a problem. Weewx crashes regularly. Here are the log.
>> Do you have any ideas ?
>>
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.drivers.wmr200: 
>> open_device() Unable to claim USB interface. Reason: [Errno 16] Resource 
>> busy 
>> Dec 15 21:30:42 Nas weewx[495153] ERROR weewx.engine: Import of driver 
>> failed: [Errno 16] Resource busy () 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  Traceback (most recent call last): 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/share/weewx/weewx/drivers/wmr200.py", line 193, in open_device 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  self.handle.claimInterface(self.interface) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/lib/python3/dist-packages/usb/legacy.py", line 230, in claimInterface 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  util.claim_interface(self.dev, interface) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/lib/python3/dist-packages/usb/util.py", line 205, in claim_interface 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  device._ctx.managed_claim_interface(device, interface) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/lib/python3/dist-packages/usb/core.py", line 102, in wrapper 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  return f(self, *args, **kwargs) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/lib/python3/dist-packages/usb/core.py", line 167, in 
>> managed_claim_interface 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  self.backend.claim_interface(self.handle, i) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 811, in 
>> claim_interface 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  _check(self.lib.libusb_claim_interface(dev_handle.handle, intf)) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 595, in 
>> _check 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  raise USBError(_strerror(ret), ret, _libusb_errno[ret]) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  usb.core.USBError: [Errno 16] Resource busy 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:    
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:   During 
>> handling of the above exception, another exception occurred: 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:    
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  Traceback (most recent call last): 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/share/weewx/weewx/engine.py", line 109, in setupStation 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  self.console = loader_function(config_dict, self) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/share/weewx/weewx/drivers/wmr200.py", line 58, in loader 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  return WMR200(**config_dict[DRIVER_NAME]) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/share/weewx/weewx/drivers/wmr200.py", line 1468, in __init__ 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  self.usb_device.open_device() 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/share/weewx/weewx/drivers/wmr200.py", line 196, in open_device 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  raise weewx.WakeupError(exception) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  weewx.WakeupError: [Errno 16] Resource busy 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL __main__: Unable to load 
>> driver: [Errno 16] Resource busy 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL __main__:   Exiting...
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups

Re: [weewx-user] Re: "Grassland Temperature Sum" (or how it is called in English, german "Grünlandtemperatursumme" (GTS))

[Chuck Rhode]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, 15 Dec 2020 09:25:48 -0800 (PST)
Ton vanN  wrote:

> You open can of worms, because [there are] a large amount of
> variations of Growing Degree Days related to different animals,
> insects and plants.

See:

o University of California, Agriculture and Natural
Resources. "Research Models: Insects, Mites, Diseases, Plants, and
Beneficials." 2014. 15 Apr. 2018
.

o Coop, Len. "Library of Degree-Day Models for Insects and Plants." 11
Feb. 2007. Integrated Plant Protection Center, Oregon State U. 1
Nov. 2020 

The models for insect development are very similar but have different
threshold and cutoff temperatures and use different cutoff techniques.
Models developed in one part of the world may not be immediately
applicable to other parts.  Many insect species apparently have local
strains that are adapted to local conditions.  The models are robust
enough to be useful without exactly matching local conditions, and
differences between modeling techniques are minor.

There are all kinds of weather-related mathematical models with
agribusiness applications beyond just weather prediction.  Recently,
I stumbled upon one that models the growth of pollen tubes in apples
dependent upon temperature.  The idea is that you can burn off the
flowers by spraying lime sulfur.  The trick is to do this after the
pollen tubes for the king fruit have reached their ovaries and to keep
doing it often enough to keep new pollen tubes from reaching theirs.
This favors the earliest flowers while thinning the rest of the crop in
(hopefully) an organically acceptable way.  There are attendant risks.
Early pollination may not be as reliable as you suppose or as you
hope.  Different varieties of apples have different pollen-tube
lengths, and the germ plasm traverses them at different rates, so you
may not be using an appropriate model if you have a different
pollinator or an odd-ball variety of apple or even a variant of a well
tested variety.  I guess the gee-whiz factor makes up for the
uncertainties of the technology.

- -- 
.. Be Seeing You,
.. Chuck Rhode, Sheboygan, WI, USA
.. Weather:  http://LacusVeris.com/WX
.. 30° — Wind N 3 mph — Sky overcast.

-BEGIN PGP SIGNATURE-

iF0EARECAB0WIQT+MY/5I/LMPSswTbVg2/xipKOWUgUCX9l8XwAKCRBg2/xipKOW
UgvzAJ4nE9JmF89LohMhcmDJ9Y+eu2DbVgCfZnpV0byyhhQVdbIJr5Gf9ySgkk8=
=fJJ8
-END PGP SIGNATURE-

-- 
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/20201215211751.4a3e6639%40wealthy.

Re: [weewx-user] Wind Rose empty in Steel Series

[fpb]

@Tom, 

I'm having a similar issue but I'm trying to figure out what the correct 
schema (assuming that is the issue)  but I can't find a combination. 

This is what I have;

[DataBindings]

[[wx_binding]]
# The database must match one of the sections in [Databases].
# This is likely to be the only option you would want to change.
database = archive_sqlite
# The name of the table within the database
table_name = archive
# The manager handles aggregation of data for historical summaries
manager = weewx.manager.DaySummaryManager
# The schema defines the structure of the database.
# It is *only* used when the database is created.
schema = schemas.wview_extended.schema
[[forecast_binding]]
database = forecast_sqlite

and below my log errors;

ec 16 00:55:18 weewx-vm weewx[11753] ERROR weewx.cheetahgenerator: Generate 
failed with exception ''

Dec 16 00:55:18 weewx-vm weewx[11753] ERROR weewx.cheetahgenerator:  
Ignoring template /etc/weewx/skins/Seasons/NOAA/NOAA-%Y-%m.txt.tmpl

Dec 16 00:55:18 weewx-vm weewx[11753] ERROR weewx.cheetahgenerator:  
Reason: cannot find 'raw' while searching for 'day.wind.count.raw'

Dec 16 00:55:18 weewx-vm weewx[11753] ERROR weewx.cheetahgenerator:   
Traceback (most recent call last):

Dec 16 00:55:18 weewx-vm weewx[11753] ERROR weewx.cheetahgenerator: 
File "/usr/share/weewx/weewx/cheetahgenerator.py", line 323, in generate

Dec 16 00:55:18 weewx-vm weewx[11753] ERROR weewx.cheetahgenerator: 
  unicode_string = compiled_template.respond()

Dec 16 00:55:18 weewx-vm weewx[11753] ERROR weewx.cheetahgenerator: 
File "_etc_weewx_skins_Seasons_NOAA_NOAA__Y__m_txt_tmpl.py", line 430, in 
respond

Dec 16 00:55:18 weewx-vm weewx[11753] ERROR weewx.cheetahgenerator:   
NotFound: cannot find 'raw' while searching for 'day.wind.count.raw'
Any help will be appreciate. 

On Thursday, June 4, 2020 at 6:01:51 PM UTC-4 tke...@gmail.com wrote:

> That's probably what happened.
>
> You're not the first to get tripped up by this. Obviously, I need to 
> rethink how to manage the transition to the new way of specifying schemas.
>
> On Thu, Jun 4, 2020 at 11:20 AM Jacques Terrettaz  
> wrote:
>
>> Forget my last message :  I used a new Raspberry PI to install weewx V4, 
>> and then I transferred my "old" mysql database  to the new installation...
>>
>>
>> Le 4 juin 2020 à 20:01, Jacques Terrettaz  a écrit :
>>
>> Tom,  
>>
>> One comment about the old and new database schema :  I didn't change 
>> anything by myself in the [DataBinding] section of weewx.conf after  the 
>> upgrade to V4.0, so I suspect that the  manager = weewx.manager.
>> DaySummaryManager  line  was automatically modified during the upgrade 
>> process.
>> Is it right ?
>>
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/ACB63400-3370-43DF-A186-A96D3BC23AA3%40gmail.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/d4d9e47e-ca30-4729-a81b-9d1cfd8dde76n%40googlegroups.com.