[weewx-user] Re: Running Ecowitt Gateway Driver bith as a driver and a service at the same time?

Ignore that empty queue, I forgot that the console device actively reports to a certain IP... michael.k...@gmx.at schrieb am Samstag, 20. Januar 2024 um 08:52:04 UTC+1: > The empty queue is probably because of running it in WSL and being in a > different IP range than the Console: > 2024-01-19

[weewx-user] Error with weewx-SteelSeries skin

-> https://github.com/gjr80/weewx-steelseries Good morning, I don't understand the reason and why of the error that occurs with my version 4.10.2 of weewx and the 'SteelSeries' Skin. Can anyone help me and tell me what's going on? THANKS Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.chee

[weewx-user] Re: Running Ecowitt Gateway Driver bith as a driver and a service at the same time?

The Gateway driver has supported simultaneous driver/service operation since v0.5.0b5. It is not a configuration I recommend due to the fragility of the configuration (if the driver crashes or the device using the driver fails/locks up data from the service device is also lost) and the ease of

[weewx-user] Re: Error with weewx-SteelSeries skin

Impossible to say with such a small log extract. Please refer to the section How to get a good, useful log on the Help! Posting to weewx user wiki page

[weewx-user] Re: Running Ecowitt Gateway Driver bith as a driver and a service at the same time?

Thank you! I'll see how far I get and I'll consider the mentioned drawbacks. gjr80 schrieb am Samstag, 20. Januar 2024 um 10:47:29 UTC+1: > The Gateway driver has supported simultaneous driver/service operation > since v0.5.0b5. It is not a configuration I recommend due to the fragility > of the

Re: [weewx-user] Re: Error with weewx-SteelSeries skin

Thank-you... Sorry but in the syslog, there is only that... And systematically same error at each packetsloop ! if the option is disabled in weewx.conf obviously no problem. :-( Jan 16 13:56:19 localhost wee_reports[62658] INFO user.alarm_multi: Alarm set for expression 18: "extraTemp3 is not None

[weewx-user] APT upgrade to WeeWX 5.0: Belchertown skin no longer working

Just FYI APT upgraded my installation to WeeWx 5.0 and my Belchertown Skin 1.2 stopped working. Everything else was still working and processing data... What I did to fix it: - Installed the latest Belchertown Skin 1.3.1 using weectl - Upgdated my weewx.conf file to V5.0 Thank you to the WeeWx

Re: [weewx-user] I'm desperate to fix my NOAA reports. Can I please pay someone to help fix my database and recover this data?

Rewording Tom's post to align with one of my professors decades ago, "That will work, but let's do it the right way." Using 'weectl database' (followed by the proper parameters) is the right way. Humidex is now stored in the database, and '$alltime.humidex.max' takes a split second to return th

[weewx-user] Aeris Soil Data Import

Hi there! I am a fairly new user. I currently have my station reporting to multiple services, I have been able to add a few extra temp/humidity sensors, have configured the Belchertown skin and added a few extra graphs for different sensor data, and have imported previous station history from W

Re: [weewx-user] Slow Report Generation after Upgrade from 4.10.2 to 5..0

Richard, you're going to have to give us more information than this. The only reference to "feels like" that I can find in the Belchertown skin has been commented out. Where are you seeing this? On Fri, Jan 19, 2024 at 7:25 PM Richard Whitcombe wrote: > Actually follow up that ive only just noti

Re: [weewx-user] APT upgrade to WeeWX 5.0: Belchertown skin no longer working

Very good to know as I plan on doing the upgrade myself. One question, how do you mean you upgrade the conf file? Did it not upgrade with the rest of the upgrade? On Sat, Jan 20, 2024, 6:39 AM c bosshard wrote: > Just FYI > > APT upgraded my installation to WeeWx 5.0 and my Belchertown Skin 1.2

Re: [weewx-user] Slow Report Generation after Upgrade from 4.10.2 to 5..0

I guess he means this "feels like" which as far as I know is a derived/calculated field in the skin [image: image.png] On Sun, 21 Jan 2024 at 03:13, Tom Keffer wrote: > Richard, you're going to have to give us more information than this. The > only reference to "feels like" that I can find in t

Re: [weewx-user] Slow Report Generation after Upgrade from 4.10.2 to 5..0

In index.html.tmpl.. #if $current.appTemp.has_data $obs.label.feels_like: $current.appTemp #end if So he has no current appTemp value apparently. On Saturday, January 20, 2024 at 9:29:24 AM UTC-8 Colin Larsen wrote: > I guess he means this "feels like"

Re: [weewx-user] APT upgrade to WeeWX 5.0: Belchertown skin no longer working

On Saturday, January 20, 2024 at 11:21:51 AM UTC-5 kevinjc...@gmail.com wrote: Very good to know as I plan on doing the upgrade myself. One question, how do you mean you upgrade the conf file? Did it not upgrade with the rest of the upgrade? the configuration file and the skins are explicitl

[weewx-user] Different time for report generation and sending to website via rsync?

Hello Weewx users. I'd like to know if it is possible to set different time (interval) for generating reports: [StdArchive] archive_interval = 300 and for syncing the files to website by rsync? My station is installed in a place where I have only cellular internet (LTE) with monthly transfer

Re: [weewx-user] Slow Report Generation after Upgrade from 4.10.2 to 5..0

Any’ skin is an over generalization. It depends what the skin is doing with calculated/synthetic observations. On a pi 3B+ and Blaine’s db (seems to be the defacto test data), WeeWX-JAS took approximately 24 minutes to generate charts with appTemp on its first run. On its second run, approximate

[weewx-user] Re: Different time for report generation and sending to website via rsync?

Checkout, http://www.weewx.com/docs/5.0/custom/report-scheduling/ On Saturday 20 January 2024 at 15:37:10 UTC-5 Tomasz Lewicki wrote: > Hello Weewx users. > > I'd like to know if it is possible to set different time (interval) for > generating reports: > > [StdArchive] > archive_interval = 300 >

Re: [weewx-user] Slow Report Generation after Upgrade from 4.10.2 to 5..0

Just woke up so delayed reply but yep thats exactly the case. >From index.html.tmpl: #if $current.appTemp.has_data $obs.label.feels_like: $current.appTemp #end if Previously

Re: [weewx-user] Re: Error with weewx-SteelSeries skin

The error message is very non-specific (as Cheetah errors often are), though the error is likely caused by a required field being None or non-existent. When asking for log extract I was not looking for errors in the log, but rather looking for details of your setup including station type, drive