Re: [weewx-development] v4 setup.py removed option --no-prompt

sigh - I missed the "-e" option there. I see from the man page what it does. Thanks. I would like to keep trying on setup.py, just for the education at a minimum. Adding the code to __init.py__ for weecfg was trivial, I just can't figure out how to get setup.py commandline options through

Re: [weewx-development] v4 setup.py removed option --no-prompt

This worked for me: *echo -e "hood river\n700, foot\n45\n-125\nn\nmetric\n3\n" | python3 ./setup.py install* Adding new options to setup.py adds a LOT of complexity. Hence, the decision to get rid of it. -tk On Sat, May 2, 2020 at 5:43 PM Vince Skahan wrote: > On Friday, May 1, 2020 at

Re: [weewx-development] v4 setup.py removed option --no-prompt

On Friday, May 1, 2020 at 6:36:24 PM UTC-7, Tom Keffer wrote: > > echo "hood river\n700,foot\n45\n-125\nmetric\n6\n\n\n" | python ./setup.py > install > > NB: this worked for V3.x. Version 4 asks the user whether s/he wants to > register the station, so you'd have to add that. > >> >> Yeah,

Re: [weewx-development] Re: Version 4.0 is (finally) here!

Thanks, Bob! On Sat, May 2, 2020 at 5:25 PM Bob Weber wrote: > Tom > > I have been trying out the betas of 4.0 for a while running the simulator > driver in a separate qemu/kvm VM. I was pleased to see that you finally > released 4.0. I had 3.7 installed from a Debian package so I had some >

[weewx-development] Re: Version 4.0 is (finally) here!

Tom I have been trying out the betas of 4.0 for a while running the simulator driver in a separate qemu/kvm VM. I was pleased to see that you finally released 4.0. I had 3.7 installed from a Debian package so I had some moving around to do! Having it all under /home/weewx is a lot easier to

Re: [weewx-development] v4 setup.py removed option --no-prompt

Vince, please do report back. I also liked the headless/default install for smoke testing my Docker images. On Friday, May 1, 2020 at 9:40:19 PM UTC-4, Vince Skahan wrote: > > On Friday, May 1, 2020 at 6:36:24 PM UTC-7, Tom Keffer wrote: >> >> What I use is >> >> echo "hood

Re: [weewx-development] WU wind speed and wind gust graph issue with rapidfire - would LOOP2 packet resolve it?

Follow the directions in Adding a new type to the database , except that in place of [DataBindings] [[wx_binding]] database = archive_sqlite table_name = archive manager =

Re: [weewx-development] WU wind speed and wind gust graph issue with rapidfire - would LOOP2 packet resolve it?

Old mail thread. It seems wview_extended.py is used only when database is created. So how do I get the new LOOP2 fields to my existing database? Create a new database and then import old database to new? Is the method documented? On Fri, 23 Aug 2019 at 19:32, Hartmut Schweidler wrote: > Hallo,

Re: [weewx-development] MQTTSubscribe.py installing as service

Hello everybody, There is issue and maybe an improvement that could be done in the driver but I'm not sure to understand correctly. My understanding is that: def __init__(self, **stn_dict): is executed at weewx start while : def genLoopPackets(self): is executed at each packet lookp The