[weewx-user] Re: Weewx stopped running after 4 days

I beg to disagree. I learnt a long time ago to not impose my views on a user's requirements; maybe the user needs to generate a report every minute, maybe they need to record the number of widgets every minute, maybe they just like lots of dots in their plots. At the end of the day it does not

[weewx-user] Re: Weewx stopped running after 4 days

I continue to find it almost impossible to conceive a situation where an archive interval of under 5 minutes serves any useful purpose. As long as a gust value is recorded for the 5 minute period the average speed value/direction over the period is more than sufficient - even for an airfield -

Re: [weewx-user] Re: NOAA reports not available

No insights (to me ) from the files you provided. What's in no.htaccess? I wouldn't have thought there could be anything in there that would prevent weewx from using the contents of NOAA. It's more a webserver control point - but then...? Ownership and permissions seem okay. root.www-data is typ

[weewx-user] Re: Weewx stopped running after 4 days

Yes the NoneType error is certainly due to the realtime clientraw extension not handling a None value correctly, by the looks of it a wind related field so quite possibly brought on by your battery/connectivity issue. That extension was written over 2 years ago and never formally released (and

[weewx-user] Re: Weewx stopped running after 4 days

On Monday, February 4, 2019 at 4:42:52 PM UTC-5, Andy Hudson-Smith wrote: > > Noted the use of skins and mqtt on a pi, i kind of assumed it was up to > the job, i do like the weewx system so may well move up to a more useful > machine - coming from Windows into this world means i know little beyo

Re: [weewx-user] Re: NOAA reports not available

Hey Bob, There is no change, but it confirms that 1.) we are working on the same page (the change has propagated to godaddy) 2.) The [[SummaryByMonth]] and [[SummaryByYear]] sections aren't being picked up and filled. If weewx couldn't find them, it would complain with an error - at least it does

[weewx-user] Re: Weewx stopped running after 4 days

Thanks for the reply Vince - I was not sure what to search for but yep thinking about a quick search for database locked before posting would have been wise. Noted the use of skins and mqtt on a pi, i kind of assumed it was up to the job, i do like the weewx system so may well move up to a more

[weewx-user] Re: Weewx stopped running after 4 days

On Monday, February 4, 2019 at 1:15:51 PM UTC-8, Andy Hudson-Smith wrote: > > Evening - my recent install of Weewx on a Pi listening for UDP data from > Weather Flow and publishing to MQTT suddenly stopped working this evening. > I am new to Weewx so any help would be great as i cant get it to st

[weewx-user] Re: Weewx stopped running after 4 days

On Monday, February 4, 2019 at 1:15:51 PM UTC-8, Andy Hudson-Smith wrote: > > Evening - my recent install of Weewx on a Pi listening for UDP data from > Weather Flow and publishing to MQTT suddenly stopped working this evening. > I am new to Weewx so any help would be great as i cant get it to st

[weewx-user] Weewx stopped running after 4 days

As an update - the main Sky Unit (it sends wind data every seconds) seems to be reporting a low battery and no data is coming through, so this may have led to the error... Andy -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from

[weewx-user] Weewx stopped running after 4 days

Evening - my recent install of Weewx on a Pi listening for UDP data from Weather Flow and publishing to MQTT suddenly stopped working this evening. I am new to Weewx so any help would be great as i cant get it to start reporting again. The recent log file is below if that helps: Andy Feb 4 21

Re: [weewx-user] Re: Second crash after 11 days

It is helpful for figuring out which services WeeWX is loading. Not essential, but useful for when you post a log. -tk On Mon, Feb 4, 2019 at 11:04 AM Steve2Q wrote: > Tom..now that I have a better understanding of the process, I will > implement the change. Before I do that, I note that you ha

[weewx-user] Re: Behaviour when adding a second data source

Hi Gary, thank you for your detailed explanation. Everything's clear for me so far. I think it would be nice to add a sentence concerning this in the customization guide. engolling -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe

[weewx-user] Re: Temperature Value for this time yesterday

It works nice; been running couple hours no problems. If you want the 24 hour difference (trend) just add $trend($time_delta=86400).outTemp. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails

Re: [weewx-user] Re: Second crash after 11 days

Tom..now that I have a better understanding of the process, I will implement the change. Before I do that, I note that you have debug = 1 in weewx_mem.conf, while in my weewx.conf debug is not set. Should I set it to 1 in my weewx.conf? -- You received this message because you are subscribed

Re: [weewx-user] Is more than one station_type possible in a single instance of WeeWX?

Wow, didn't expect an answer that quickly; nice to know this is such an active community! Thanks very much for your guidance; I'll read into the links asap. Much appreciated! On Mon, Feb 4, 2019 at 12:56 PM Thomas Keffer wrote: > You cannot have two drivers, but you can add a service that adds

Re: [weewx-user] Re: Second crash after 11 days

Yes, the memory would increase for the WeeWX instance running the Ultimeter. Nothing changes there. What we are trying to see is if the same thing happens with the simulator. That would point to whether or not it has anything to do with the hardware, driver, and serial interface. You can, of cour

Re: [weewx-user] Is more than one station_type possible in a single instance of WeeWX?

You cannot have two drivers, but you can add a service that adds data from the second data source. One approach is to create a service that runs a second thread , which communicates with the second source. Another approach is to emit dat

Re: [weewx-user] Re: NOAA reports not available

Glenn, Your files are loaded now. Haven't seen any difference. I upgraded from 3.7.0 to 3.8.2 several months ago. Could there be a problem with cheetah? Is it possible to reinstall cheetah without messing up the configuration? I've also been trying to install WX-HWS, with only partial luck, as it

[weewx-user] Is more than one station_type possible in a single instance of WeeWX?

Pardon what may be an obvious question, but I could only find one relevant post and it was from a few years ago. I have WeeWX up and running with my Acurite 5in1 but I also have a Bloomsky Sky1. I discovered there was a driver for the Bloomsky and was wondering if there was a way to add it int

Re: [weewx-user] Re: Second crash after 11 days

Tom: I am not sure how this would work. If I am running both the Ultimeter and the Simulator simultaneously, wouldn't I get the same memory increase as data from the Ultimeter would still be coming in? Steve -- You received this message because you are subscribed to the Google Groups "weewx

Re: [weewx-user] Re: Second crash after 11 days

Good idea. You don't even need to shut down your Ultimeter. Just run a second instance of weewx, using the attached configuration file weewx_mem.conf. It will put the database in subdirectory /home/weewx/archive2, and the generated reports in /home/weewx/public_html2. Put it in /home/weewx, then

Re: [weewx-user] Re: Second crash after 11 days

Tom and Vince. It appears that using the serial connections on the Pi is a relatively easy thing to do. I just need the proper adapter and then have to make a few changes in the software for the pi and Weewx. I am going to order one, do the change and see what happens. Steve -- You received

Re: [weewx-user] Re: Second crash after 11 days

Kevin..thats what I am doing now until a resolution is found. On Sun, Feb 3, 2019 at 9:01 AM Kevin Hedgepeth wrote: > I ran into a problem with my pi randomly shutting down. I set CRON to > restart my pi every night and have not had a problem since. The only > adverse effect is that the braggin

Re: [weewx-user] Re: Temperature Value for this time yesterday

We will make sure the capability does not go away, although I can't promise the syntax won't change. My biggest area of concern is actually around specifying the database. Right now, you do something like $current(data_binding='mybinding').outTemp I've never liked how this mixes database binding

Re: [weewx-user] Temperature Value for this time yesterday

Many thanks Tom, Perfect just what I needed and it work as expected. While it may be undocumented it is a nice feature. All the best. Peter On Monday, 4 February 2019 13:37:50 UTC, Thomas Keffer wrote: > > The $current object has an undocumented feature that allows a timestamp to > be speci

Re: [weewx-user] Re: Second crash after 11 days

On Monday, February 4, 2019 at 6:37:14 AM UTC-8, Thomas Keffer wrote: > Steve, I'm at a loss. You are running a simple system, on a well-known > platform, yet experiencing memory growth. > > Tom - the only thing I can think of is to take the driver and usb stuff out of the equation temporarily

[weewx-user] Re: Integrate data from separate device into weewx

I think I've understood the point of your posting but stll need a little bit of an input, since I don't really understand what a REC event is, how to configure one an how to bind it. Is this all pointed out in the user/customisation guide? Where can I find further explanation? Am Montag, 4. Feb

Re: [weewx-user] Temperature Value for this time yesterday

sounds much better to say recorded or listed undocumented features!!! On Monday, 4 February 2019 16:27:02 UTC+2, Thomas Keffer wrote: > > Sounds like an oxymoron: documented undocumented features. > > -tk > > On Mon, Feb 4, 2019 at 6:25 AM Andrew Milner > wrote: > >> Tom >> It would be lovely t

[weewx-user] Re: NOAA Reports Belchertown Skin

Thanks guys, I am travelling and will be away from my pi until Thursday, I will try the suggested changes then and report back. Thanks! On Sunday, February 3, 2019 at 10:47:42 PM UTC-6, gjr80 wrote: > > I agree with Pat that some changes are needed to [StdReport]. I don't > expect the Belcherto

[weewx-user] Re: Temperature Value for this time yesterday

I just tried this, Tom, and it works as you describe - with the 600 delta qualifier, which certainly is good enough. Two questions: (1) In light of your caution that "it's also likely to change at some future point", would you think that's somewhat likely or highly likely. It's a nice feature

Re: [weewx-user] Re: Second crash after 11 days

I've been running WeeWX on an RPi with stretch for a day now. I don't have an Ultimeter, so I used a VPro2 console, which also has a serial interface. Memory use is VIRT=48416, RES=33500 and seems to be steady. I'm using kernel Linux-4.14.79-v7+-armv7l-with-debian-9.6, which is a slightly older

Re: [weewx-user] Temperature Value for this time yesterday

Sounds like an oxymoron: documented undocumented features. -tk On Mon, Feb 4, 2019 at 6:25 AM Andrew Milner wrote: > Tom > It would be lovely to have all the undocumented, unsupported, untested > gems gathered together somewhere - so that at least they are recorded in > one place! > > > > O

Re: [weewx-user] Temperature Value for this time yesterday

Tom It would be lovely to have all the undocumented, unsupported, untested gems gathered together somewhere - so that at least they are recorded in one place! On Monday, 4 February 2019 15:37:50 UTC+2, Thomas Keffer wrote: > > The $current object has an undocumented feature that allows a t

[weewx-user] Re: Integrate data from separate device into weewx

You could have your task create a text file and have a service that binds to a REC event, reads the text file and adds the radiation to the archive record. Weewx would then take care of the daily stats in archive_day_radiation for you. Alternatively your service could still bind to the REC, but

Re: [weewx-user] Temperature Value for this time yesterday

The $current object has an undocumented feature that allows a timestamp to be specified. It looks something like this (NOT TESTED): #set $yesterday=$current.dateTime.raw - 86400 The temperature 24 hours ago was $current(timestamp=$yesterday).outTemp Because a timestamp 24 hours ago may not fall

[weewx-user] Temperature Value for this time yesterday

Hi, I am new here and this is my first post. I am using a modified version of the NeoWx skin, I would like to show Temperature at this time yesterday. I can see there are methods for showing aggregation of values min, max etc in the past. But I can only see how to get down to a resol

[weewx-user] Integrate data from separate device into weewx

Hi, I run weewx on a raspberryPi with a WS28xx station. I also have a 3kW peak solar panel on the roof of my house. The solar power inverter logs a lot of data which can be read over a JSON API. So what I am doing right now is running a cron job every 5min that looks into the weewx database for

Re: [weewx-user] Re: NOAA reports not available

Bugger - wrong file. Use this one. On 04/02/2019, Glenn McKechnie wrote: > Hi Bob, > > The simplest explanation would be that CheetahGenerator is not finding > the NOAA templates to generate the html links - and that it's not > throwing an error in the process. > > Attached is a version of your

Re: [weewx-user] Re: NOAA reports not available

Hi Bob, The simplest explanation would be that CheetahGenerator is not finding the NOAA templates to generate the html links - and that it's not throwing an error in the process. Attached is a version of your index.html.tmpl that will display the NOAA filenames it finds. If it finds any (I don't