Re: [weewx-user] wee_import date/time specifications

Thanks, Gary! This is admittedly minor, since wee_import clearly (and accurately!) reports what it’s doing. But cleaning up the docs should save others from some head scratching. -Les > On 24 Feb 2021, at 22:22, gjr80 wrote: > > Thanks Les, QC is obviously lacking at weewx.com

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

I don't know, I'm a SSH only person, I am getting out of my depth now. Gary On Thursday, 25 February 2021 at 16:21:11 UTC+10 monmul wrote: > I am using VNC Viewer (and always have) rather than SSHnot sure if > that makes any difference? > > On Thursday, 25 February 2021 at 19:13:29 UTC+13

[weewx-user] Re: wee_import date/time specifications

Thanks Les, QC is obviously lacking at weewx.com at the moment. I have revised the relevant stanzas in the wee_import section of the Utilities Guide and added a brief explanatory note as you suggest. Have also reworked the weeimport.py comments. Issue 652

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

I am using VNC Viewer (and always have) rather than SSHnot sure if that makes any difference? On Thursday, 25 February 2021 at 19:13:29 UTC+13 gjr80 wrote: > Hmm, different to my Davis on my RPi which shows weewxd rather than > screen. I will have to defer to Tom or someone who knows about

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

Hmm, different to my Davis on my RPi which shows weewxd rather than screen. I will have to defer to Tom or someone who knows about screen. Gary On Thursday, 25 February 2021 at 15:58:07 UTC+10 monmul wrote: > pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop > [ ok ] Stopping weewx (via systemctl):

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop [ ok ] Stopping weewx (via systemctl): weewx.service. pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

I thought it was installed by default on RPi OS but seems lt it is not - it works on my RPi, I must have installed it manually. Try: $ sudo apt update $ sudo apt install lsof then try running lsof. Gary On Thursday, 25 February 2021 at 14:19:30 UTC+10 monmul wrote: > pi@WeatherPi:~ $ sudo

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop [ ok ] Stopping weewx (via systemctl): weewx.service. pi@WeatherPi:~ $ lsof /dev/ttyUSB0 bash: lsof: command not found pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 minicom: cannot open /dev/ttyUSB0: Device or resource busy pi@WeatherPi:~ $ lsof

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

Try prefixing lsof with sudo. Gary On Thursday, 25 February 2021 at 14:15:17 UTC+10 monmul wrote: > pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop > [ ok ] Stopping weewx (via systemctl): weewx.service. > pi@WeatherPi:~ $ lsof /dev/ttyUSB0 > bash: lsof: command not found > pi@WeatherPi:~ $

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop [ ok ] Stopping weewx (via systemctl): weewx.service. pi@WeatherPi:~ $ lsof /dev/ttyUSB0 bash: lsof: command not found pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 minicom: cannot open /dev/ttyUSB0: Device or resource busy pi@WeatherPi:~ $ lsof

[weewx-user] Re: Question on heat index

Thanks Gary! I've got some catching up to do it seems On Wednesday, February 24, 2021 at 3:54:21 PM UTC-5 gjr80 wrote: > Pat, > > v4.2.0 saw a new heatindex formula implemented, refer issue 601 > . The new formula gives some > results in some

[weewx-user] Re: Question on heat index

Pat, v4.2.0 saw a new heatindex formula implemented, refer issue 601 . The new formula gives some results in some circumstances that may appear counterintuitive. v4.3.0 added back the ‘old’ heatindex formula and gives the user the ability to choose

[weewx-user] wee_import date/time specifications

The documentation for wee_import says that the --from and --to date/times are inclusive and exclusive, respectively. But what is reported when an import is run, and what the code actually implements, is the other way around: the --from is exclusive and the --to is inclusive. (To further the

[weewx-user] Question on heat index

I thought heat index wasn't calculated unless the temperature was over 80F? Today it's about 49 F and I'm seeing heat index in my charts (which is reporting lower than temperature - I thought that was wind chill?). I don't recall seeing it before at this temperature range. I just want to make

[weewx-user] Belchertown skin & AerisWeather correction

Hi folks, if you're using the Belchertown skin: I was contacted by AerisWeather today and they asked for me to update the company name in the skin to AerisWeather (one word, no space, capital A, capital W). If you have a mis-spelling of their company name in your skin under your credits

Re: [weewx-user] Bootstrap skin update preview

Ok, what's happening here: in the templates there are references to history table that weren't part of the skins default configuration You need either to delete the section in the template: $BootstrapLabels.history_tables.max_wind $max_wind_table or, and thats my sugesstion, add the

Re: [weewx-user] Bootstrap skin update preview

Hi Michael, thank you for the MQTT explanation. I saw when editing the skin.conf that ws and wss are preconfigured. But I didn't think anything of it and was under the misapprehension that mqtt would also work... Since the weather page will only run locally for me, I'll stick with my config

Re: [weewx-user] Bootstrap skin update preview

Hi, the MQTT config for the skin is for the JavaScript MQTT client that is running in the browser window. This client needs a websocket connection, so it will only work with a websocket enabled MQTT server. This MQTT client configuration is totally independent from the one that is publishing

Re: [weewx-user] Bootstrap skin update preview

A working MQTT environment already exists. The MQTT configuration was a bit bumpy because I wanted to use the following connection: broker_connection = mqtt://192.168.178.15:1883 Only the following setting brought success: broker_connection = ws://192.168.178.15:9001 Afterwards I adjusted the

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

Make sure you stop weewx first before trying minicom. There cannot be anything else using the port. To see what devices are using a port: *lsof /dev/ttyUSB0* On Tue, Feb 23, 2021 at 9:19 PM monmul wrote: > No change in USB port. > > pi@WeatherPi:~ $ > pi@WeatherPi:~ $ minicom -b 19200 -D

Re: [weewx-user] Bootstrap skin update preview

There is still some things to configure to get everything working and there is not too much documentation now. It would be very helpful if you could make notes for everything you had to do - it will help us to start a documentation. Do you have MQTT already working? It is needed for live data.

Re: [weewx-user] Bootstrap skin update preview

Great, now it works :) Thanks for your fast help and the very nice skin. Now I can take a closer look at everything. michael.k...@gmx.at schrieb am Mittwoch, 24. Februar 2021 um 13:05:14 UTC+1: > Fixed - next one :D > > Michael schrieb am Mittwoch, 24. Februar 2021 um 12:59:58 UTC+1: > >>

Re: [weewx-user] Bootstrap skin update preview

Fixed - next one :D Michael schrieb am Mittwoch, 24. Februar 2021 um 12:59:58 UTC+1: > and here is the next one ;) > > Traceback (most recent call last): > File "/home/weewx/bin/wee_extension", line 88, in > main() > File "/home/weewx/bin/wee_extension", line 80, in main >

Re: [weewx-user] Bootstrap skin update preview

and here is the next one ;) Traceback (most recent call last): File "/home/weewx/bin/wee_extension", line 88, in main() File "/home/weewx/bin/wee_extension", line 80, in main ext.install_extension(options.install) File "/home/weewx/bin/weecfg/extension.py", line 125, in install_extension

Re: [weewx-user] Bootstrap skin update preview

I've just fixed that. I didn't test the installer yet. Sorry for the mess and thank you for participating :) We'll get this working, I hope there aren't too many flaws to go... Michael schrieb am Mittwoch, 24. Februar 2021 um 12:33:44 UTC+1: > thanks, but now I got this Error: > > Traceback

Re: [weewx-user] Bootstrap skin update preview

thanks, but now I got this Error: Traceback (most recent call last): File "/home/weewx/bin/wee_extension", line 88, in main() File "/home/weewx/bin/wee_extension", line 80, in main ext.install_extension(options.install) File "/home/weewx/bin/weecfg/extension.py", line 125, in

Re: [weewx-user] Bootstrap skin update preview

Please try again, you need to download the latest package again. michael.k...@gmx.at schrieb am Mittwoch, 24. Februar 2021 um 11:32:10 UTC+1: > No, this is an installer issue. I'll check and fix that. > > Michael schrieb am Mittwoch, 24. Februar 2021 um 08:27:25 UTC+1: > >> The installation of

Re: [weewx-user] Bootstrap skin update preview

No, this is an installer issue. I'll check and fix that. Michael schrieb am Mittwoch, 24. Februar 2021 um 08:27:25 UTC+1: > The installation of fuzzy-archer-liveCharts.zip works without error > message. > But when generating the reports, the following appears: > > Feb 24 08:22:21 weewx-test