RE: [weewx-user] Re: WEEWX-WD and Weewx 4.2 to 4.4

Thanks Gary for the insight and guidance. Sent from Mail for Windows 10 From: gjr80 Sent: Saturday, January 30, 2021 7:58 PM To: weewx-user Subject: [weewx-user] Re: WEEWX-WD and Weewx 4.2 to 4.4 Hi, I wouldn't be using WeeWX-WD from bitbucket, it has not been touched for some years now. WeeW

[weewx-user] Re: WEEWX-WD and Weewx 4.2 to 4.4

Hi, I wouldn't be using WeeWX-WD from bitbucket, it has not been touched for some years now. WeeWX-WD on github is more up to date, the current version is v2.1.2 from November 2020. It should have no problems running on WeeWX v4.x under python 2 or pyth

[weewx-user] WEEWX-WD and Weewx 4.2 to 4.4

Gang, Currently running weewx 4.2 (will be upgrading in the next few days to 4.4) on a Raspberry Pi 4 (32-bit OS) with a Rainwise MK-III and IP-100 providing station data -- everything has been working properly for several weeks and is populating a remote MySQL DB. Once I upgrade weewx, I'd li

[weewx-user] Re: Version 4.4.0

My apologies to user 'edi-x', who was the true author of PR #631 . Thanks to user g-eddy for pointing this out. On Sat, Jan 30, 2021 at 11:06 AM Tom Keffer wrote: > This version fixes a bug that was introduced by fixing yet another bug. It > only affects

[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent

The subscription to the ‘wind’ topic is just some code that needs to be cleaned up. Tracking via #119 . You also need the ‘use_topic_as_fieldname = True’ option. Additional information is here

[weewx-user] Version 4.4.0

This version fixes a bug that was introduced by fixing yet another bug. It only affects vector wind plots. 4.4.0 01/30/2021 StdWXCalculate can now do calculations for only LOOP packets, only archive records, or both. PR #630. Thanks to user g-eddy! Introduced aggregate types "avg_ge" and "avg_le

[weewx-user] Re: interceptor + WH2900C (ecowitt comptible) + freebsd startup script

I couldn't get the provided startup script to work in a freenas jail (even though the provided script run from the command line). Credit to Samuel Tai from the freenas forums for helping me with the enclosed script which solved the problem. On Tuesday, January 26, 2021 at 11:11:37 PM UTC+1 S R

[weewx-user] MQTTSubscribe and topics, that are seldom sent

I want to receive data from MQTT, I tried lots of options by now, but to no success. Special: Data are published to MQTT once in a quarter of an hour, only. When data is published through MQTT and received by the MQTTSubscribe service, the first loop packet after that contains the data. So I g

Re: [weewx-user] Re: SFTP problem

Thanks, Gary and Tom. He seems to have found the problem although I’m not sure what it was. bgrat...@umw.edu On Friday, January 29, 2021 at 7:43:34 PM UTC-5 gjr80 wrote: > Not a sftp user but the typical approach to fault finding ftp/sftp/rsync > generator issues is to see if you can connect t

[weewx-user] Re: forecast WU/OWM, and SteelSeries Gauges not working with latest version

Thank you @gjr80. Your last comment told me what I should have done from the start. I diffed the files, and found that quite a few subtles changes where performed in the template since the original version I had (new variables and renamed variables) So I updated my working file, with the WU fo

Re: [weewx-user] Longitude failing to update.

Ahhh ok :) thank you very much for clearing that up. On Saturday, January 30, 2021 at 2:30:55 PM UTC kk44...@gmail.com wrote: > That's neither WeeWX nor Belchertown skin. There was a thread before, and > that's Windy. It always marks the location of the user (or what it guesses, > where the us

Re: [weewx-user] Longitude failing to update.

That's neither WeeWX nor Belchertown skin. There was a thread before, and that's Windy. It always marks the location of the user (or what it guesses, where the user is located). It does _not_ show the station's location. But the picture is centered to the station's location. tke...@gmail.com sch

Re: [weewx-user] Longitude failing to update.

Hello, Stephen. Maybe I'm missing something, but I'm not seeing what the problem is. You specified latitude, longitude of 51.80, -0.87 in weewx.conf, and that's exactly what you're getting in your reports. Remember that lat/lon is *base 60*. On Sat, Jan 30, 2021 at 5:36 AM Stephen Brookes wrote:

[weewx-user] Longitude failing to update.

Hi All, First time posting in this group!! This is probably something really simple and I've completely missed something but I've had weewx running for a good few months now but noticed that the longitude is incorrect and the latitude is slightly out, so I used the wee_config --reconfigure to

[weewx-user] Re: forecast WU/OWM, and SteelSeries Gauges not working with latest version

Perhaps there is nothing wrong with it. Is that the only change you made to the gauge-data.txt template? If so the following search list extensions are not used and one of them could well cause the failure: user.wdsearchlist.WdTimeSpanTags, user.wdsearchlist.WdWindRunTags, user.wdsearchlist.WdL

[weewx-user] Re: forecast WU/OWM, and SteelSeries Gauges not working with latest version

Hi, It took me a little while, but I reverted by steelserreis folder to what is in the repo, and it works. But I indeed lost my forecast line. To explain, I forgot about it, but when I first customized the steel series for me, changed the zambretti forecast with the WU one. I added the following