Re: [weewx-user] Re: Sudden error running reports? Any help appreciated

['andyhud...@googlemail.com' via weewx-user]

Yep, it was the time in my yesterday graph.conf - much appreciated. I 
decided to remove the 'yesterday' option and the reports all run fine now.

Thanks again!

Andy
On Saturday, 19 February 2022 at 16:18:35 UTC tke...@gmail.com wrote:

> Option "time_length 
> " is set 
> to the string 'yesterday', instead of a number. 
>
> On Sat, Feb 19, 2022 at 8:04 AM 'andyhud...@googlemail.com' via 
> weewx-user  wrote:
>
>> Edit - noting it's not a sudden error, my Yesterday Graph has not updated 
>> for 10 days, so i must be something in my graphs.conf ... :)
>>
>> Andy
>>
>> On Saturday, 19 February 2022 at 15:35:10 UTC andyhud...@googlemail.com 
>> wrote:
>>
>>> Afternoon - weewx has been happily running, i noticed when i run reports 
>>> i get an error (yet the website seems to be working ok? -  
>>> http://www.finchamweather.co.uk/) 
>>>
>>> Any help would be really appreciated:
>>>
>>> Using configuration file /etc/weewx/weewx.conf
>>>
>>> Generating for all time
>>>
>>> Traceback (most recent call last):
>>>
>>>   File "/usr/share/weewx/weewx/reportengine.py", line 196, in run
>>>
>>> obj.start()
>>>
>>>   File "/usr/share/weewx/weewx/reportengine.py", line 281, in start
>>>
>>> self.run()
>>>
>>>   File "/usr/share/weewx/user/belchertown.py", line 2520, in run
>>>
>>> time_length = int(time_length)
>>>
>>> ValueError: invalid literal for int() with base 10: 'yesterday'
>>>
>>>
>>> Andy
>>>
>> -- 
>> 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/fb81a4c6-39b6-4542-9d23-aff2ec4cefd5n%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/0dd8cbe1-f88d-4f79-b4fd-1612a828d8fen%40googlegroups.com.

[weewx-user] MQTT to WeewX

[Guido Groetie]

I want to add a watertemperature sensor (DS18B01) with a NodeMCU ESP8266 
board into weewx, it will be the first MQTT things i will do.

I got the following working:
Beside a RPI with WeewX I have another RPI with Domotizcz.
I got it running that the temp mearurements of the ESP Easy software is 
getting through Domoticz MQTT into Domoticz (topic: domoticz/in)

So I use the Domoticz RPI as a broker for WeewX.

In the ESP Easy webinterface I see in JSON:

So my fieldname should me temperature
Topic should be: domoticz/in


In WeewX I want the values of meaurements in extraTemp2 place in database. 
But I see no result in my neo-wx material skin...
www.weerindedraai.nl

Here is a piece of weewx.conf file:
[MQTTSubscribeService]
# This section is for the MQTTSubscribe service.

# Turn the service on and off.
# Default is: true
# Only used by the service.
enable = true

# The MQTT server.
# Default is localhost.
host = 192.168.1.71

# The port to connect to.
# Default is 1883.
port = 1883

# Maximum period in seconds allowed between communications with the 
broker.
# Default is 60.
keepalive = 60

# username for broker authentication.
# Default is None.
username = admin

# password for broker authentication.
# Default is None.
password = wh0racl3

# The binding, loop or archive.
# Default is: loop
# Only used by the service.
binding = loop

# The message handler to use
[[message_callback]]
# The format of the MQTT payload.
# Currently support: individual, json, keyword
# Must be specified.
type = json

# The topics to subscribe to.
[[topics]]
# Units for MQTT payloads without unit value.
# Valid values: US, METRIC, METRICWX
# Default is: US
unit_system = METRIC

[[[topic/domoticz/in]]]
  temperature
# The WeeWX name.
# Default is the name from MQTT.
name = extraTemp2

# True if the incoming data should not be processed into WeeWX.
# Valid values: True, False
# Default is False
ignore = False

# True if the incoming data is cumulative.
# Valid values: True, False
# Default is False
contains_total = False

# The conversion type necessary for WeeWX compatibility
# Valid values: bool, float, int, none
# Default is float
conversion_type = float

# The units of the incoming data.
# Useful if this field's units differ from the topic's 
unit_system's units.
# Valid values: see, 
http://www.weewx.com/docs/customizing.htm#units
# Default is not set
units = degree_C  

I changed the topic name to something without an / an is now: openwatertemp

in logfile WeewX:
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
Version is 2.0.0
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) Log 
level: 0
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) Log 
debug setting: 0
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) Log 
console: False
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) Log 
file: None
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
message_callback_provider_name is user.MQTTSubscribe.MessageCallbackProvider
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
clientid is MQTTSubscribe-9039
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
client_session is True
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) host 
is 192.168.1.71
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) port 
is 1883
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
keepalive is 60
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
username is admin
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
password is set
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
Archive topic is None
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
binding is loop
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
Waiting for MQTT connection.
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
Connected with result code 0
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
Connected flags {'session present': 0}
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
Subscribing to topic/openwatertemp has a mid 1 and rc 0
Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
Subscribed to mid: 1 is size 1 has a QOS of 0

Does rc 0 means that is does not receiving data??

Can somebody help m

Re: [weewx-user] Trying to install docker and need yml assistance

[Doug Jenkins]

Essentially yes. I would login with the user account that has docker access
and clone my repo in the current directory (~). Then I would configure the
docker-compose.yml and the weewx.conf files inside my config folder and use
the shell script to build it out.

You probably have to tinker with the setup as I got this to work on Ubuntu
and not on Debian.

Also, you do not have to use MariaDB with weewx. I like using MariaDB
because I like to query the live db to run checks and to build a new
interface in the future.

Let me know where you end up. I am checking my email daily now so I can be
more available to help.

On Fri, Feb 18, 2022, 10:03 AM Adam Morgan  wrote:

> Thank you again Doug!  I can't tell you how much I appreciate it.
>
> Ok, I think I got most of what you are saying.  So for your example I
> would be copying all of the files in your repo to the /weewx folder on my
> host, modify the yml file, and then execute the config.sh file?
>
>
>
> On Friday, February 18, 2022 at 8:41:09 AM UTC-5 do...@dougjenkins.com
> wrote:
>
>> Adam:
>>
>> Sorry for the late reply. I am still adjusting my gmail filters to get
>> all the weewx-users and weewx-developer messages through.
>>
>> I ran into the same problem when I started using the docker image for my
>> custom install. I wanted to bring in a few of the popular weewx extensions
>> (MQTT, Belchertown, Windy) yet if I recreate the container, I would have to
>> manually re-add these extensions and then post my weewx.conf back into the
>> solution. This can be a problem when you have to reboot the server for
>> maintenance.
>>
>> So going back to my notes and repo internally, what I did was to create
>> my own docker image using Tom Mitchell's image, then loading the extensions
>> and then copying my weewx.conf file back AFTER the extensions were
>> installed. I also updated his executing script (/bin/run) to point the
>> weewx.conf file to a specific folder (/home/weewx/config/weewx.conf). This
>> way I can make changes to the weewx.conf, redeploy the solution, rebuild
>> the image, etc.
>>
>> To help understand all of this (as this took some time to set up as I was
>> learning docker), I created a public github repo that has all of these
>> files and configurations set so you can see how I set up my station. All of
>> the sensitive items have been removed, so you will need to go through the
>> config files and update them for your station.
>>
>> here is that link : WeeWX Docker Stack Example (NGINX | MQTT | WEEWX |
>> MARIADB) 
>>
>> Please let me know if this helps and let me know the next issue that you
>> run into.
>>
>> DDJ
>>
>>
>> On Thu, Feb 17, 2022 at 8:25 PM Adam Morgan  wrote:
>>
>>> @DougJenkins I am hoping that you might be able to see what I am doing
>>> wrong.  I can see that the config files are being written inside the docker
>>> container and not the path in /AppData.  The weird thing is that it does
>>> create the WeeWx folder in AppData but it is empty.
>>>
>>> https://hub.docker.com/r/mitct02/weewx
>>>
>>> The documentation is for docker run and thus it isn't the same thing:
>>>
>>> docker run -d --volume /Users/tom/weewx.conf:/home/weewx/weewx.conf
>>> --volume
>>>
>>> I did try this - I ended up with a subfolder of "weex.conf" that was
>>> again empty.
>>>
>>>
>>>
>>> On Wednesday, February 16, 2022 at 9:27:07 AM UTC-5 Adam Morgan wrote:
>>>
 Do you see anything wrong in the config that I posted yesterday?

 Here is the view from putty:



 On Tuesday, February 15, 2022 at 9:24:51 PM UTC-5 vince wrote:

> Wild guess is that you either tried to map to directories that don't
> exist, or your volume mounts aren't working.
>
>
> --
>>> 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/7f7a2556-0ba4-4a86-80bb-7c3a120dd335n%40googlegroups.com
>>> 
>>> .
>>>
>>
>>
>>
>> --
> 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/fy3nqJ34Ho0/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/b6283982-ca35-4220-80cd-fa4f770b11e7n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscri

[weewx-user] RTLDavis windRun calculation and rain records

[Andrew Roberts]

Hi,
I'm after a steer as to where to look to fix/block this issue. I'm running 
RTLDavis  with a Vantage Vue and 
weewx 4.6.1. The indoor temperature and pressure (BMP280) is coming through 
as a data service over a serial link.

When I start up weewx and use loopdata 
, syslog shows:

Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata: 
  Traceback (most recent call last):
Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata: 
File "/usr/share/weewx/user/loopdata.py", line 810, in process_queue
Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata: 
  windrun_val = weewx.wxxtypes.WXXTypes.calc_windrun('windrun', pkt)
Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata: 
File "/usr/share/weewx/weewx/wxxtypes.py", line 303, in calc_windrun
Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata: 
  raise weewx.CannotCalculate(key)
Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata: 
  weewx.CannotCalculate: windrun

1. Looking into the code it seems to be a lack of interval data. I can not 
find a way of sorting this in weewx.conf and close inspection of the 
RTLDavis DEBUG data  in Syslog (attached) doesn't have any interval data in 
it.

2. In spite of it raining, the console reporting rain and after tipping a 
cup of water into the bucket I'm not reliably getting rain data from the 
ISS. the DEBUG (all three debug options set to 3) log records:

DEBUG user.rtldavis:  data_pkt: {'channel': 1, 'bat_iss': 0, 
'wind_speed_ec': 15, 'wind_speed_raw': 14, 'wind_dir': 273.9486166007905, 
'wind_speed': 6.7055833, 'rain_count': 37, 'curr_cnt0': 2982, 
'curr_cnt1': 0, 'curr_cnt2': 0, 'curr_cnt3': 0}
DEBUG user.rtldavis: rain=0.0 rain_count=0 last_rain_count=37
DEBUG user.rtldavis: pkt= {'windSpeed': 6.7055833, 'windDir': 
273.9486166007905, 'txBatteryStatus': 0, 'rain': 0.0, 'dateTime': 
1645353107, 'usUnits': 17}

Any suggestions as to next steps for me troubleshooting these would be 
welcome.

Andrew

-- 
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/a75644e9-5c1b-44a9-a345-70803e116d81n%40googlegroups.com.
Feb 20 10:20:01 Weather-Centre weewx[8905] DEBUG user.rtldavis: no_rain=0 mm/h
Feb 20 10:20:01 Weather-Centre weewx[8905] DEBUG user.rtldavis: data_pkt: 
{'channel': 1, 'bat_iss': 0, 'wind_speed_ec': 21, 'wind_speed_raw': 20, 
'wind_dir': 242.85770750988144, 'wind_speed': 9.3878166, 'rain_rate': 
0, 'curr_cnt0': 2935, 'curr_cnt1': 0, 'curr_cnt2': 0, 'curr_cnt3': 0}
Feb 20 10:20:01 Weather-Centre weewx[8905] DEBUG user.rtldavis: pkt= 
{'windSpeed': 9.3878166, 'windDir': 242.85770750988144, 'rainRate': 0, 
'txBatteryStatus': 0, 'dateTime': 1645352402, 'usUnits': 17}
Feb 20 10:20:09 Weather-Centre weewx[8905] DEBUG user.rtldavis: chan: 
00:11:31.749797 Hop: {ChannelIdx:4 ChannelFreq:868557250 FreqError:4629 
Transmitter:0}
Feb 20 10:20:09 Weather-Centre weewx[8905] DEBUG user.rtldavis: Store 
freqError4: 4629 for transmitter: 0
Feb 20 10:20:09 Weather-Centre weewx[8905] DEBUG user.rtldavis: chan_pkt: 
{'dateTime': 1645352409, 'usUnits': 17, 'freqError4': 4629}
Feb 20 10:20:09 Weather-Centre weewx[8905] DEBUG user.rtldavis: pkt= 
{'heatingVoltage': 4629, 'dateTime': 1645352409, 'usUnits': 17}
Feb 20 10:20:16 Weather-Centre weewx[8905] DEBUG user.rtldavis: data: 
00:11:34.313519 800A7A1D590FFCAA 2936 0 0 0 0 msg.ID=0
Feb 20 10:20:16 Weather-Centre weewx[8905] DEBUG user.rtldavis: 
wind_speed_raw=00a wind_dir_raw=0x07a
Feb 20 10:20:16 Weather-Centre weewx[8905] DEBUG user.rtldavis: rx0=120, 
rx1=124, ry0=10, ry1=10, x0=2, x1=1, y0=2, y1=1, x=122, y=10
Feb 20 10:20:16 Weather-Centre weewx[8905] DEBUG user.rtldavis: 
WS=5.3644667 WD=172.56521739130434 WS_raw=10 WS_ec=12 WD_raw=122 
WD_pro=172.56521739130434 WD_vue=171.8625
Feb 20 10:20:16 Weather-Centre weewx[8905] DEBUG user.rtldavis: digital 
temp_raw=0x1d5 temp_f=46.9 temp_c=8.277
Feb 20 10:20:16 Weather-Centre weewx[8905] DEBUG user.rtldavis: data_pkt: 
{'channel': 1, 'bat_iss': 0, 'wind_speed_ec': 12, 'wind_speed_raw': 10, 
'wind_dir': 172.56521739130434, 'wind_speed': 5.3644667, 'temperature': 
8.277, 'curr_cnt0': 2936, 'curr_cnt1': 0, 'curr_cnt2': 0, 
'curr_cnt3': 0}
Feb 20 10:20:16 Weather-Centre weewx[8905] DEBUG user.rtldavis: pkt= 
{'windSpeed': 5.3644667, 'windDir': 172.56521739130434, 'outTemp': 
8.277, 'txBatteryStatus': 0, 'dateTime': 1645352417, 'usUnits': 17}
Feb 20 10:20:24 Weather-Centre weewx[8905] DEBUG user.rtldavis: 
new_archive_record
Feb 20 10:20:24 Weather

[weewx-user] 4.6.2. update problem with wee_import

[jannep...@gmail.com]

Hi, I updated from 4.5 to 4.6.2 and my wee_import stop to next message:

I use WS6in1-driver with my Ventus.

...
Using WeeWX configuration file /etc/weewx/weewx.conf
Starting wee_import...
A CSV import from source file '/var/tmp/data.csv' has been requested.
Using database binding 'wx_binding', which is bound to database 'weewx.sdb'
Destination table 'archive' unit system is '0x11' (METRICWX).
Missing derived observations will be calculated.
This is a dry run, imported data will not be saved to archive.
Starting dry run import ...
Traceback (most recent call last):
  File "/usr/share/weewx/wee_import", line 899, in 
main()
  File "/usr/share/weewx/wee_import", line 829, in main
source_obj.run()
  File "/usr/share/weewx/weeimport/weeimport.py", line 372, in run
_raw_data = self.getRawData(period)
  File "/usr/share/weewx/weeimport/csvimport.py", line 246, in getRawData
self.map = self.parseMap('CSV', _csv_reader, self.csv_config_dict)
  File "/usr/share/weewx/weeimport/weeimport.py", line 635, in parseMap
and _val['units'] not in weewx.units.USUnits.values():
AttributeError: 'ListOfDicts' object has no attribute 'values'
..

What this does mean? Any help? 

Is there easy way to get back to working configuration (4.5)? 

regards
Janne

-- 
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/68f5ce52-0ead-46ff-a293-43691c2e079cn%40googlegroups.com.

Re: [weewx-user] Trying to install docker and need yml assistance

[Adam Morgan]

Wow, thank you again Doug!  You clearly put a lot of effort into this.

Ok, a lot to unpack here.   I downloaded your repo into a setup folder on 
my server and updated .conf with the values that seemed to make sense to 
me.  
 I already have MariaDB running in another container for Kodi but I left 
all of that in the docker compose file because in the short term I'll be 
happy if I can just get this to work.  I did add the new user and databases 
to my existing MariaDB installation, just in case.

I then ran all of your commands by hand.  The first was running "docker 
build ." to initiate the build.  I then did each command one by one.  That 
seemed to go well - I see the image and the folders populated as expected.  
Now what?  Should I see a container?  I do see the image pulled down and 
there is a lot of information inside of it that came from the files in your 
repo.  

here is the output from the docker build:

build .
Sending build context to Docker daemon  1.637MB
Step 1/9 : FROM mitct02/weewx:4.5.1
4.5.1: Pulling from mitct02/weewx
23884877105a: Already exists
bc38caa0f5b9: Already exists
2910811b6c42: Already exists
36505266dcc6: Already exists
07a923053093: Already exists
776b7eaf0a03: Already exists
bc700a6f34b5: Already exists
67577fd8c8eb: Pull complete
31df857523bd: Pull complete
ecd6e0ddf182: Pull complete
bb9aba96460d: Pull complete
3d3e5fc6d05d: Pull complete
6754665d41ef: Pull complete
6135e7b935ea: Pull complete
9b10839751a1: Pull complete
3017c664af94: Pull complete
e844a912b1d5: Pull complete
7b5bb4deb379: Pull complete
f1c5b3b47d82: Pull complete
7d1f4fb1b49c: Pull complete
7bd1db2eac8f: Pull complete
bfc9e864b8db: Pull complete
c0191d0c7ecb: Pull complete
Digest: 
sha256:8416c7b57ff50e43538218c8834bdce0238aee0aaaf13dc812148c101862ee9f
Status: Downloaded newer image for mitct02/weewx:4.5.1
 ---> 92c42aedddc5
Step 2/9 : WORKDIR /home/weewx
 ---> Running in 5d7735458fe1
Removing intermediate container 5d7735458fe1
 ---> 8d4a708a3959
Step 3/9 : ADD config/weewx.conf /home/weewx/
 ---> 51a0752dad14
Step 4/9 : ADD extensions/*.zip /home/weewx/extensions/
 ---> a0e7a30a9b7e
Step 5/9 : ADD bin/run /etc/service/weewx/
 ---> 431aa0d66516
Step 6/9 : RUN chmod 755 /etc/service/weewx/run
 ---> Running in 06d3d16a3ecc
Removing intermediate container 06d3d16a3ecc
 ---> c7cd9bed645c
Step 7/9 : RUN ./bin/wee_extension --config=weewx.conf --install 
/home/weewx/ext  ensions/weewx-mqtt.zip
 ---> Running in 993acec9f543
Request to install '/home/weewx/extensions/weewx-mqtt.zip'
Extracting from zip archive /home/weewx/extensions/weewx-mqtt.zip
Saving installer file to /home/weewx/bin/user/installer/mqtt
Saved configuration dictionary. Backup copy at weewx.conf.20220220133527
Finished installing extension '/home/weewx/extensions/weewx-mqtt.zip'
Removing intermediate container 993acec9f543
 ---> 29570a351dde
Step 8/9 : RUN ./bin/wee_extension --config=weewx.conf --install 
/home/weewx/ext  ensions/weewx-belchertown-master.zip
 ---> Running in 92413d3b743d
Request to install '/home/weewx/extensions/weewx-belchertown-master.zip'
Extracting from zip archive 
/home/weewx/extensions/weewx-belchertown-master.zip
Saving installer file to /home/weewx/bin/user/installer/Belchertown
Saved configuration dictionary. Backup copy at weewx.conf.20220220133530
Finished installing extension 
'/home/weewx/extensions/weewx-belchertown-master.z  ip'
Removing intermediate container 92413d3b743d
 ---> b9849746c7d4
Step 9/9 : RUN ./bin/wee_extension --config=weewx.conf --install 
/home/weewx/ext  ensions/weewx-windy.zip
 ---> Running in 98b470bf89fe
Request to install '/home/weewx/extensions/weewx-windy.zip'
Extracting from zip archive /home/weewx/extensions/weewx-windy.zip
Saving installer file to /home/weewx/bin/user/installer/windy
Saved configuration dictionary. Backup copy at weewx.conf.20220220133534
Finished installing extension '/home/weewx/extensions/weewx-windy.zip'
Removing intermediate container 98b470bf89fe
 ---> 640a0fa3c5b3
Successfully built 640a0fa3c5b3
root@HAL:/srv/dev-disk-by-label-Docker/AppData/weewx_setup/docker-build# cd 
..
root@HAL:/srv/dev-disk-by-label-Docker/AppData/weewx_setup# cp 
docker-build/conf  ig/weewx.conf 
/srv/dev-disk-by-label-Docker/AppData/weewx/config/
root@HAL:/srv/dev-disk-by-label-Docker/AppData/weewx_setup# cp -r skins/* 
/srv/d  ev-disk-by-label-Docker/AppData/weewx/skins/
root@HAL:/srv/dev-disk-by-label-Docker/AppData/weewx_setup# cp 
mosquitto_mqtt/co  nfig/* 
/srv/dev-disk-by-label-Docker/AppData/weewx/mosquitto/config/
On Sunday, February 20, 2022 at 9:31:08 AM UTC-5 do...@dougjenkins.com 
wrote:

> Essentially yes. I would login with the user account that has docker 
> access and clone my repo in the current directory (~). Then I would 
> configure the docker-compose.yml and the weewx.conf files inside my config 
> folder and use the s

Re: [weewx-user] Trying to install docker and need yml assistance

[vince]

On Sunday, February 20, 2022 at 11:15:42 AM UTC-8 muchgoo...@gmail.com 
wrote:

> I then ran all of your commands by hand.  The first was running "docker 
> build ." to initiate the build.  I then did each command one by one.  That 
> seemed to go well - I see the image and the folders populated as expected.  
> Now what?  Should I see a container? 
>

You guys might want to consider taking this one offline to email at this 
point, but...

Tom - I'd suggest you do might some more reading up on Docker
(do https://www.docker.com/101-tutorial - it's pretty good)

   - An "image" is a built configured reusable thing.
   - A "container" is a running instance of that image. 
   - Building an image ala 'docker build' or 'docker-compose build' does 
   not create a running instance (container) of that image.
   - You have to do "docker run' or 'docker-compose up' to start a 
   container running.
   - Changes made while building an image persist.
   - Changes made within a running container go 'poof' when the container 
   stops

What his scripts are doing is populating an external mounted directory 
under /srv on persistent storage.

But blindly running somebody else's script without spinning yourself up a 
bit more on how Docker works is just going to be confusing and frustrating.

-- 
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/dd8d9bc1-77ec-43f9-a2c2-9a06ac9580bcn%40googlegroups.com.

Re: [weewx-user] Re: sftp on 3.9.2, RPI3B -- **still** not working with several methods

[Rob Cranfill]

Funny you should bring this up now. I recently upgraded to WeeWX 2.6, and
my modified code no longer works. I was always able to adapt to each new
version, but the new codebase is quite different than the previous ones. I
have kind of given up on trying to adapt it to 2.6. Sorry.

Instead, I use a cron job to “rsynch” my local files to the remote. It
sounds like maybe you are doing something similar.

If you are using some version of WeeWX less than 2.6 I could still send you
my code. Although even that code requires the pysftp library, so maybe none
of this will help you. :-/

Let me know if you’d like to try it.


On Fri, Feb 18, 2022 at 23:03 'Dr. Thomas Tuch' via weewx-user <
weewx-user@googlegroups.com> wrote:

> Dear Rob
> After moving to a different server i have been trying to get sftp to work
> with weewx and never managed to get pysftp compiled, probably because my pi
> is running Ubuntu 16. This I cannot change because my home automation is
> running on the same pi3b - I would not like to mess with heating etc in
> German winter :-) I would therefore be happy to get a copy of your hack.
> Thank you in advance. Thomas
>
>
> robcr...@gmail.com schrieb am Mittwoch, 27. Mai 2020 um 18:09:56 UTC+2:
>
>> Dear Mr or Ms Potamia, ;-)
>>
>> I have code that I hacked into the standard Weewx base that implements
>> proper sftp. If you would like a copy I can send it to you. (And anyone
>> else who’d like a copy.) Just one modified file.
>>
>> /rob
>
> --
> 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/GdlSK3vTvYE/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/f0444643-d438-47ab-b11c-5a9bf624222en%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/CAOVFAvoDwnxjLgRh6ctWRz%2BaGvLT-bwMtZ7%2BvmMUZ57BiEnGHQ%40mail.gmail.com.

[weewx-user] Problem with Vantage Vue

[geo...@gmail.com]

I want to use my Vantage Vue with weewx per tcp/ip. After installing weewx 
I get the following error messages:

*** 

Feb 20 21:42:43 weewx weewx[1198] CRITICAL weewx.engine:  
 Vantage.__init__(self, **config_dict[DRIVER_NAME])
Feb 20 21:42:43 weewx weewx[1198] CRITICAL weewx.engine: File 
"/usr/share/weewx/weewx/drivers/vantage.py", line 514, in __init__
Feb 20 21:42:43 weewx weewx[1198] CRITICAL weewx.engine:  
 self.port.openPort()
Feb 20 21:42:43 weewx weewx[1198] CRITICAL weewx.engine: File 
"/usr/share/weewx/weewx/drivers/vantage.py", line 346, in openPort
Feb 20 21:42:43 weewx weewx[1198] CRITICAL weewx.engine:  
 raise weewx.WeeWxIOError(ex)
Feb 20 21:42:43 weewx weewx[1198] CRITICAL weewx.engine:  
 weewx.WeeWxIOError: [Errno 111] Connection refused
Feb 20 21:42:43 weewx weewx[1198] CRITICAL __main__: Unable to load driver: 
[Errno 111] Connection refused
Feb 20 21:42:43 weewx weewx[1198] CRITICAL __main__:   Exiting...
***

Do I have to install a vantage-driver afterwards? 

-- 
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/c535886d-3cdf-4212-a6ed-f05247fe8302n%40googlegroups.com.

[weewx-user] Re: MQTT to WeewX

[morr...@gmail.com]

Could you use mosquitto_sub to ensure the broker is publishing your data in 
the form you expect? Something like:

mosquitto_sub -h 192.168.1.71 -u admin -P wh0racl3 -t 'domoticz/in/#' -v

On Sunday, February 20, 2022 at 7:03:11 a.m. UTC-4 g.g...@gmail.com wrote:

> I want to add a watertemperature sensor (DS18B01) with a NodeMCU ESP8266 
> board into weewx, it will be the first MQTT things i will do.
>
> I got the following working:
> Beside a RPI with WeewX I have another RPI with Domotizcz.
> I got it running that the temp mearurements of the ESP Easy software is 
> getting through Domoticz MQTT into Domoticz (topic: domoticz/in)
>
> So I use the Domoticz RPI as a broker for WeewX.
>
> In the ESP Easy webinterface I see in JSON:
>
> So my fieldname should me temperature
> Topic should be: domoticz/in
>
>
> In WeewX I want the values of meaurements in extraTemp2 place in database. 
> But I see no result in my neo-wx material skin...
> www.weerindedraai.nl
>
> Here is a piece of weewx.conf file:
> [MQTTSubscribeService]
> # This section is for the MQTTSubscribe service.
> 
> # Turn the service on and off.
> # Default is: true
> # Only used by the service.
> enable = true
> 
> # The MQTT server.
> # Default is localhost.
> host = 192.168.1.71
> 
> # The port to connect to.
> # Default is 1883.
> port = 1883
> 
> # Maximum period in seconds allowed between communications with the 
> broker.
> # Default is 60.
> keepalive = 60
> 
> # username for broker authentication.
> # Default is None.
> username = admin
> 
> # password for broker authentication.
> # Default is None.
> password = wh0racl3
> 
> # The binding, loop or archive.
> # Default is: loop
> # Only used by the service.
> binding = loop
> 
> # The message handler to use
> [[message_callback]]
> # The format of the MQTT payload.
> # Currently support: individual, json, keyword
> # Must be specified.
> type = json
> 
> # The topics to subscribe to.
> [[topics]]
> # Units for MQTT payloads without unit value.
> # Valid values: US, METRIC, METRICWX
> # Default is: US
> unit_system = METRIC
> 
> [[[topic/domoticz/in]]]
>   temperature
> # The WeeWX name.
> # Default is the name from MQTT.
> name = extraTemp2
>
> # True if the incoming data should not be processed into WeeWX.
> # Valid values: True, False
> # Default is False
> ignore = False
>
> # True if the incoming data is cumulative.
> # Valid values: True, False
> # Default is False
> contains_total = False
>
> # The conversion type necessary for WeeWX compatibility
> # Valid values: bool, float, int, none
> # Default is float
> conversion_type = float
>
> # The units of the incoming data.
> # Useful if this field's units differ from the topic's 
> unit_system's units.
> # Valid values: see, 
> http://www.weewx.com/docs/customizing.htm#units
> # Default is not set
> units = degree_C  
>
> I changed the topic name to something without an / an is now: openwatertemp
>
> in logfile WeewX:
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> Version is 2.0.0
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) Log 
> level: 0
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) Log 
> debug setting: 0
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) Log 
> console: False
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) Log 
> file: None
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> message_callback_provider_name is user.MQTTSubscribe.MessageCallbackProvider
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> clientid is MQTTSubscribe-9039
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> client_session is True
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) host 
> is 192.168.1.71
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) port 
> is 1883
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> keepalive is 60
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> username is admin
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> password is set
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> Archive topic is None
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> binding is loop
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> Waiting for MQTT connection.
> Feb 2

Re: [weewx-user] Trying to install docker and need yml assistance

[Adam Morgan]

Sorry, did a private response by mistake a minute ago.  I do understand the 
basics of docker.   This particular approach is a bit new to me so I 
thought I would ask what to do next.  The config files are in place - is it 
a matter of just issuing a docker run with the image?  

On Sunday, February 20, 2022 at 2:53:33 PM UTC-5 vince wrote:

> On Sunday, February 20, 2022 at 11:15:42 AM UTC-8 muchgoo...@gmail.com 
> wrote:
>
>> I then ran all of your commands by hand.  The first was running "docker 
>> build ." to initiate the build.  I then did each command one by one.  That 
>> seemed to go well - I see the image and the folders populated as expected.  
>> Now what?  Should I see a container? 
>>
>
> You guys might want to consider taking this one offline to email at this 
> point, but...
>
> Tom - I'd suggest you do might some more reading up on Docker
> (do https://www.docker.com/101-tutorial - it's pretty good)
>
>- An "image" is a built configured reusable thing.
>- A "container" is a running instance of that image. 
>- Building an image ala 'docker build' or 'docker-compose build' does 
>not create a running instance (container) of that image.
>- You have to do "docker run' or 'docker-compose up' to start a 
>container running.
>- Changes made while building an image persist.
>- Changes made within a running container go 'poof' when the container 
>stops
>
> What his scripts are doing is populating an external mounted directory 
> under /srv on persistent storage.
>
> But blindly running somebody else's script without spinning yourself up a 
> bit more on how Docker works is just going to be confusing and frustrating.
>
>

-- 
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/63f503fd-c774-45c9-9690-31c9fc7f3b7bn%40googlegroups.com.

Re: [weewx-user] Trying to install docker and need yml assistance

[Doug Jenkins]

Yes. I would run docker-compose up and check to see if the docker
containers are running. If you are using portainer, check the stack there.

You will know if weewx is working by reviewing the log from the docker
container. Again I like using portainer for this as the GUI allows an easy
interface to see the results.

Common issues that you will run into are permissions to the host
directories that weewx/MQTT/NGINX need to access. then the next possible
issue would be access to your weather station hardware (assumed you plugged
the console to the RPI). You will need to debug this a bit to get it to
work properly.

if you need to debug the solution, just edit the weewx.conf located in your
config folder on the host and restart the containers. Weewx.conf is the
main file that governs weewx.

DDJ

On Sun, Feb 20, 2022 at 4:37 PM Adam Morgan 
wrote:

> Sorry, did a private response by mistake a minute ago.  I do understand
> the basics of docker.   This particular approach is a bit new to me so I
> thought I would ask what to do next.  The config files are in place - is it
> a matter of just issuing a docker run with the image?
>
> On Sunday, February 20, 2022 at 2:53:33 PM UTC-5 vince wrote:
>
>> On Sunday, February 20, 2022 at 11:15:42 AM UTC-8 muchgoo...@gmail.com
>> wrote:
>>
>>> I then ran all of your commands by hand.  The first was running "docker
>>> build ." to initiate the build.  I then did each command one by one.  That
>>> seemed to go well - I see the image and the folders populated as expected.
>>> Now what?  Should I see a container?
>>>
>>
>> You guys might want to consider taking this one offline to email at this
>> point, but...
>>
>> Tom - I'd suggest you do might some more reading up on Docker
>> (do https://www.docker.com/101-tutorial - it's pretty good)
>>
>>- An "image" is a built configured reusable thing.
>>- A "container" is a running instance of that image.
>>- Building an image ala 'docker build' or 'docker-compose build' does
>>not create a running instance (container) of that image.
>>- You have to do "docker run' or 'docker-compose up' to start a
>>container running.
>>- Changes made while building an image persist.
>>- Changes made within a running container go 'poof' when the
>>container stops
>>
>> What his scripts are doing is populating an external mounted directory
>> under /srv on persistent storage.
>>
>> But blindly running somebody else's script without spinning yourself up a
>> bit more on how Docker works is just going to be confusing and frustrating.
>>
>> --
> 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/63f503fd-c774-45c9-9690-31c9fc7f3b7bn%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/CACC0i0yGMaCoT0U6F6ijA%2BVdxiOiW4A4OWi%3DDJLQhRm9UBjb7Q%40mail.gmail.com.

[weewx-user] Re: MQTT to WeewX

[bell...@gmail.com]

I think the problem is that you have a 'topic/' at the beginning of your 
topics. Try either [[[domoticz/in]]] or [[[openwatertemp]]], depending on 
what topic you are publishing to.
rich

On Sunday, 20 February 2022 at 06:03:11 UTC-5 g.g...@gmail.com wrote:

> I want to add a watertemperature sensor (DS18B01) with a NodeMCU ESP8266 
> board into weewx, it will be the first MQTT things i will do.
>
> I got the following working:
> Beside a RPI with WeewX I have another RPI with Domotizcz.
> I got it running that the temp mearurements of the ESP Easy software is 
> getting through Domoticz MQTT into Domoticz (topic: domoticz/in)
>
> So I use the Domoticz RPI as a broker for WeewX.
>
> In the ESP Easy webinterface I see in JSON:
>
> So my fieldname should me temperature
> Topic should be: domoticz/in
>
>
> In WeewX I want the values of meaurements in extraTemp2 place in database. 
> But I see no result in my neo-wx material skin...
> www.weerindedraai.nl
>
> Here is a piece of weewx.conf file:
> [MQTTSubscribeService]
> # This section is for the MQTTSubscribe service.
> 
> # Turn the service on and off.
> # Default is: true
> # Only used by the service.
> enable = true
> 
> # The MQTT server.
> # Default is localhost.
> host = 192.168.1.71
> 
> # The port to connect to.
> # Default is 1883.
> port = 1883
> 
> # Maximum period in seconds allowed between communications with the 
> broker.
> # Default is 60.
> keepalive = 60
> 
> # username for broker authentication.
> # Default is None.
> username = admin
> 
> # password for broker authentication.
> # Default is None.
> password = wh0racl3
> 
> # The binding, loop or archive.
> # Default is: loop
> # Only used by the service.
> binding = loop
> 
> # The message handler to use
> [[message_callback]]
> # The format of the MQTT payload.
> # Currently support: individual, json, keyword
> # Must be specified.
> type = json
> 
> # The topics to subscribe to.
> [[topics]]
> # Units for MQTT payloads without unit value.
> # Valid values: US, METRIC, METRICWX
> # Default is: US
> unit_system = METRIC
> 
> [[[topic/domoticz/in]]]
>   temperature
> # The WeeWX name.
> # Default is the name from MQTT.
> name = extraTemp2
>
> # True if the incoming data should not be processed into WeeWX.
> # Valid values: True, False
> # Default is False
> ignore = False
>
> # True if the incoming data is cumulative.
> # Valid values: True, False
> # Default is False
> contains_total = False
>
> # The conversion type necessary for WeeWX compatibility
> # Valid values: bool, float, int, none
> # Default is float
> conversion_type = float
>
> # The units of the incoming data.
> # Useful if this field's units differ from the topic's 
> unit_system's units.
> # Valid values: see, 
> http://www.weewx.com/docs/customizing.htm#units
> # Default is not set
> units = degree_C  
>
> I changed the topic name to something without an / an is now: openwatertemp
>
> in logfile WeewX:
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> Version is 2.0.0
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) Log 
> level: 0
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) Log 
> debug setting: 0
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) Log 
> console: False
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) Log 
> file: None
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> message_callback_provider_name is user.MQTTSubscribe.MessageCallbackProvider
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> clientid is MQTTSubscribe-9039
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> client_session is True
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) host 
> is 192.168.1.71
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) port 
> is 1883
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> keepalive is 60
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> username is admin
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> password is set
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> Archive topic is None
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> binding is loop
> Feb 20 11:58:55 weewx weewx[32438] INFO user.MQTTSubscribe: (Service) 
> Waiting for MQTT connection.
> Feb 20 11:

[weewx-user] Re: Problem with Vantage Vue

[vince]

Connection refused is the other computer isn't listening and accepting 
traffic on that port.
Check you have the right ip address set in your weewx.conf file

-- 
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/a5ca40aa-5560-4d30-b8f8-db3472829054n%40googlegroups.com.

Re: [weewx-user] Vantage Vue wind cup size setting with wee_device

[Gary Strand]

I know this is an old thread but is precisely the question I have. 
"wee_device" reports the cups as "large", but the cups on my sensor don't 
seem large to me. Are the "small" really tiny?

Just curious because what counts as "extraordinary circumstances"? On the 
day of the Colorado Marshall Fire, I recorded a gust of 49 mph when other 
stations were reporting much higher numbers; is this such a circumstance?

Thanks!


On Saturday, October 20, 2018 at 7:57:52 PM UTC-6 tke...@gmail.com wrote:

> Thanks, Philip. That's the first reference I've seen to "Vue" cups. As I 
> said, you'd have to ask Davis.
>
> But, in any case, don't worry about it. Only under extraordinary 
> circumstances do you need to set it.
>
> -tk
>
> On Sat, Oct 20, 2018 at 6:51 PM Philip Kutzenco  wrote:
>
>> Thomas,
>>
>> Thanks for the reply. I won't worry about it. The reason I asked is that 
>> the help file for Davis' Weatherlink software shows three options. See the 
>> attached screen shot I took for setting that in the console with 
>> Weatherlink. Evidently, you can set a VantagePro to use small cups or 
>> Vue/Other cups. I'll just leave the value as it is set in the console 
>> without setting it explicitly.
>> phil
>>
>> On Saturday, October 20, 2018 at 8:22:26 PM UTC-4, Thomas Keffer wrote:
>>>
>>> A Vantage (whether a Vue or a VantagePro) ships with a value in the 
>>> EEPROM firmware that matches its cup size. Unless you change the cups, 
>>> there is no reason to mess with this value. The wee_device utility option 
>>> is there if, for some reason, you have to change the cups.
>>>
>>> To answer your question, the Davis documentation lists only two sizes: 
>>> small and large. If there's a third "Vue" sized, I haven't heard of it. 
>>> You'd have to ask Davis.
>>>
>>> -tk
>>>
>>> On Sat, Oct 20, 2018 at 7:35 AM Philip Kutzenco  
>>> wrote:
>>>
 Now that I have my external website operational (
 https://wx.kutzenco.com) with a Mosquitto MQTT broker and Belchertown 
 skin, I'm spending a bit more time reviewing the weeWX documentation to 
 get 
 a deeper understanding of my system. I'm hoping to do some customization.

 I have a Davis Vantage Vue weather station and weeWX running on a 
 Raspberry Pi Zero W. I see that the Davis Weatherlink software gives the 
 options for wind cup size as Small, Large or Vue/Other. That Davis 
 documentation says that Vantage Pro systems generally ship with large 
 cups, 
 and that (obviously) Vantage Vue systems ship with Vue cups.

 The wee_device --help command mentions only Small and Large options for 
 wind cup size. Is there an option for Vue/other cups? I don't know what is 
 adjusted in the readings/calculations by specifying different cup sizes. I 
 didn't see that called out in the weeWX documention. I suspect the 
 difference is minimal, but, just to ensure that everything can be set 
 properly with weeWX does that option need to be added to wee_device for 
 Vantage systems, if it isn't there?

 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+...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

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

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

[weewx-user] Re: 4.6.2. update problem with wee_import

[gjr80]

Janne,

Could you please let me know whether WeeWX is being run under python 2 or 
3? You can tell by looking at the WeeWX log during WeeWX startup (the 
python version is logged) or you can look at the first line of any of the 
wee_xx (eg wee_database) utilities in the /usr/share/weewx directory.

If yo cannot work it out please restart WeeWX and post a log extract 
showing the full WeeWX startup.

Gary

On Monday, 21 February 2022 at 04:21:57 UTC+10 jannep...@gmail.com wrote:

> Hi, I updated from 4.5 to 4.6.2 and my wee_import stop to next message:
>
> I use WS6in1-driver with my Ventus.
>
> ...
> Using WeeWX configuration file /etc/weewx/weewx.conf
> Starting wee_import...
> A CSV import from source file '/var/tmp/data.csv' has been requested.
> Using database binding 'wx_binding', which is bound to database 'weewx.sdb'
> Destination table 'archive' unit system is '0x11' (METRICWX).
> Missing derived observations will be calculated.
> This is a dry run, imported data will not be saved to archive.
> Starting dry run import ...
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_import", line 899, in 
> main()
>   File "/usr/share/weewx/wee_import", line 829, in main
> source_obj.run()
>   File "/usr/share/weewx/weeimport/weeimport.py", line 372, in run
> _raw_data = self.getRawData(period)
>   File "/usr/share/weewx/weeimport/csvimport.py", line 246, in getRawData
> self.map = self.parseMap('CSV', _csv_reader, self.csv_config_dict)
>   File "/usr/share/weewx/weeimport/weeimport.py", line 635, in parseMap
> and _val['units'] not in weewx.units.USUnits.values():
> AttributeError: 'ListOfDicts' object has no attribute 'values'
> ..
>
> What this does mean? Any help? 
>
> Is there easy way to get back to working configuration (4.5)? 
>
> regards
> Janne
>

-- 
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/98eabde5-bd94-4121-a692-c634c66ef5fcn%40googlegroups.com.