Re: [weewx-user] "yesterday.outTemp" compared to "current.outTemp", et seq, for Yesterday page

[Messy Potamia]

Then is it possible to generate plots that cover the current 48 hours? They 
would end with the current time but would span 2 days.
Thanks
Phil

On Saturday, April 18, 2020 at 1:25:53 AM UTC+2, Thomas Keffer wrote:
>
> Unfortunately, no. The ImageGenerator can only make plots that end with 
> the current time.
>
> -tk
>
> On Fri, Apr 17, 2020 at 8:11 AM Messy Potamia  > wrote:
>
>> Thanks, the tables are great. 
>> - - -
>> Reading through the .tmpls & skin.conf, and 
>> http://www.weewx.com/docs/customizing.htm, I cannot glean how to tell 
>> the plot generator to generate a plot that is from the same time period 24 
>> hours ago. Is there a way to get those?
>> Thanks,
>> Phil
>>
>> On Friday, April 17, 2020 at 4:23:24 PM UTC+2, Messy Potamia wrote:
>>>
>>> Thanks, trying that now...
>>>
>>> On Friday, April 17, 2020 at 4:18:33 PM UTC+2, Thomas Keffer wrote:

 The two tags serve different purposes. The tag $yesterday represents 
 an *aggregation* over the day. The tag $current represents a single 
 record. There is an undocumented feature in v3.9.2 (documented in V4.0) 
 that gets you what you want:

 The temperature 24 hours ago was 
 $current(timestamp=$current.dateTime.raw-86400).outTemp


 -tk

 On Fri, Apr 17, 2020 at 7:01 AM Messy Potamia  
 wrote:

> The high/low table is working, showing but I'd like to get the upper 
> table in yesterday.html.tmpl  to show the data from 86400 seconds 
> ago, or one day ago, $day($days_ago=1), or $yesterday.  This doesn't seem 
> to be working.
> In otherwords, on my Yesterday page, (weewx 3.9.2 Standard skins) I'd 
> like it to show the same data as if you looked at it exactly 24 hrs ago. 
> When I replace the $current.outTemp with $yesterday.outTemp,  it 
> generates an error. 
> Any ideas?   Thanks--
>
> -- 
> You received this message because you are subscribed to the Google 
> Groups "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to weewx...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/571e351c-cbbc-446a-8cc5-e7e96fa95a42%40googlegroups.com
>  
> 
> .
>
 -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/207b4e40-894c-42d2-88bc-9e1b4a31d7eb%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/875a4c41-ee22-48a2-8dfd-59409269ee6a%40googlegroups.com.

Re: [weewx-user] Re: Cannot get Weewx to run on a Raspberry Pi 4

[Glenn McKechnie]

On 18/04/2020, michael form  wrote:
> Thanks again. A little while ago I checked to see if 1-wire was disabled in
>
> raspi-config, as you suggested. I explicitly disabled it anyway and
> rebooted.
>
> The magic of re-booting---Now things seem to be working, at least for my
> test setup. I will see if it can start up again and work and add additional
>
> 1-Wire sensors.I have no definite idea on why
> seems to work now. It would be good, if it hasn't already been done, to
> modify the doc so that no one has to go through the headaches that I did.I
> would do it myself if I knew anything much
> about Linux. :)


The reboot was an easy way to unload the 1-wire kernel module from
memory, if there was a change to make. Under linux, that can be done
from the command line but it's at the risk of introducing errors and
further confusion. A reboot is far simpler.

Sadly, that seems to be the outcome for those who have run into
problems with owfs and Pi4's (or Buster installations).
There's been no real solution except a vague, hand waving reboot.
That's hard to document with a straight face, and certainly with any
authority :-)

Still, it works now, and hopefully it will keep working.

And yes... stay well.

 --

Cheers
 Glenn

rorpi - read only raspberry pi & various weewx addons
https://github.com/glennmckechnie

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAAraAzjkpxrrpPUJJyqc607N2n9Z-RKOqr%3Dux4Z-FHW9ire3_w%40mail.gmail.com.

Re: [weewx-user] Re: Cannot get Weewx to run on a Raspberry Pi 4

[vince]

On Friday, April 17, 2020 at 5:24:59 PM UTC-7, michael form wrote:
>
> The magic of re-booting---Now things seem to be working, at least for my 
> test setup
>

Before you continue your Windows habits, please do 'not' in the habit of 
this on Linux.  It is almost never needed.  Really.

For the future, whenever you start fiddling with all the knobs and dials, 
(a) save yourself a backup of the SD card that you can easily revert to and 
(b) write everything down.  Everything.   It's likely you had multiple 
things tweaked that conflicted.

But glad it's working ! 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8241bc66-81b5-404e-8446-28479762baf4%40googlegroups.com.

Re: [weewx-user] Re: Cannot get Weewx to run on a Raspberry Pi 4

[michael form]

Thanks again. A little while ago I checked to see if 1-wire was disabled in 
raspi-config, as you suggested. I explicitly disabled it anyway and 
rebooted. 

The magic of re-booting---Now things seem to be working, at least for my 
test setup. I will see if it can start up again and work and add additional 
1-Wire sensors.I have no definite idea on why 
seems to work now. It would be good, if it hasn't already been done, to 
modify the doc so that no one has to go through the headaches that I did.I 
would do it myself if I knew anything much
about Linux. :)

Thank you for all of your help. If you were local and restaurants were 
open, I'd take you out for lunch.

Stay well.

Michael

On Friday, April 17, 2020 at 8:11:16 PM UTC-4, Glenn McKechnie wrote:
>
> Forgot to add how to stop the output / command (either one) 
> Use Ctrl-C at the terminal 
>
> On 18/04/2020, Glenn McKechnie > 
> wrote: 
> > On 17/04/2020, Glenn McKechnie > 
> wrote: 
> > 
> >> Do you have the pi's 1-wire interface enabled? If so try disabling it. 
> >> 
> >> sudo raspi-config 
> >>Option 5? Interfacing options 
> >>P7 1-wire  enable or disable. 
> >> (or something like that). You are after the option to enable/disable 
> >> one-wire interface. Disable it. 
> > 
> > I forgot that you answered that one in an earlier reply. And the 
> > answer is that it's off. 
> > 
> > Refreshing my memory further, there have been issues with owserver and 
> > Pi4 on this list, but not quite the same failure. Same outcome though. 
> > https://groups.google.com/d/msg/weewx-user/4EZRDyPoBH8/gN23K0feDAAJ 
> > 
> > We can attempt to see what owserver is actually failing on by running 
> > the following from the terminal. 
> > 
> > sudo /usr/bin/owserver -c /etc/owfs.conf --debug 
> > 
> > and you'll get output to the screen. Hopefully it will be meaningful, 
> > or at least offer a clue. 
> > 
> > You can redirect it to a file and attach that file (/tmp/owdebug.log) 
> > to your next post. 
> > 
> > sudo /usr/bin/owserver -c /etc/owfs.conf --debug > /tmp/owdebug.log 2>&1 
> > 
> > 
> > -- 
> > 
> > 
> > Cheers 
> >  Glenn 
> > 
> > rorpi - read only raspberry pi & various weewx addons 
> > https://github.com/glennmckechnie 
> > 
>
>
> -- 
>
>
> Cheers 
>  Glenn 
>
> rorpi - read only raspberry pi & various weewx addons 
> https://github.com/glennmckechnie 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a82b3079-c3a9-43b2-a7fa-9e7ee018e8c7%40googlegroups.com.

Re: [weewx-user] Re: Cannot get Weewx to run on a Raspberry Pi 4

[Glenn McKechnie]

Forgot to add how to stop the output / command (either one)
Use Ctrl-C at the terminal

On 18/04/2020, Glenn McKechnie  wrote:
> On 17/04/2020, Glenn McKechnie  wrote:
>
>> Do you have the pi's 1-wire interface enabled? If so try disabling it.
>>
>> sudo raspi-config
>>Option 5? Interfacing options
>>P7 1-wire  enable or disable.
>> (or something like that). You are after the option to enable/disable
>> one-wire interface. Disable it.
>
> I forgot that you answered that one in an earlier reply. And the
> answer is that it's off.
>
> Refreshing my memory further, there have been issues with owserver and
> Pi4 on this list, but not quite the same failure. Same outcome though.
> https://groups.google.com/d/msg/weewx-user/4EZRDyPoBH8/gN23K0feDAAJ
>
> We can attempt to see what owserver is actually failing on by running
> the following from the terminal.
>
> sudo /usr/bin/owserver -c /etc/owfs.conf --debug
>
> and you'll get output to the screen. Hopefully it will be meaningful,
> or at least offer a clue.
>
> You can redirect it to a file and attach that file (/tmp/owdebug.log)
> to your next post.
>
> sudo /usr/bin/owserver -c /etc/owfs.conf --debug > /tmp/owdebug.log 2>&1
>
>
> --
>
>
> Cheers
>  Glenn
>
> rorpi - read only raspberry pi & various weewx addons
> https://github.com/glennmckechnie
>


-- 


Cheers
 Glenn

rorpi - read only raspberry pi & various weewx addons
https://github.com/glennmckechnie

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAAraAzixh2qrbs6JcHuyrn1NEpDHL_pNG63Abomm8k%2BuM_HEsg%40mail.gmail.com.

Re: [weewx-user] Re: Cannot get Weewx to run on a Raspberry Pi 4

[Glenn McKechnie]

On 17/04/2020, Glenn McKechnie  wrote:

> Do you have the pi's 1-wire interface enabled? If so try disabling it.
>
> sudo raspi-config
>Option 5? Interfacing options
>P7 1-wire  enable or disable.
> (or something like that). You are after the option to enable/disable
> one-wire interface. Disable it.

I forgot that you answered that one in an earlier reply. And the
answer is that it's off.

Refreshing my memory further, there have been issues with owserver and
Pi4 on this list, but not quite the same failure. Same outcome though.
https://groups.google.com/d/msg/weewx-user/4EZRDyPoBH8/gN23K0feDAAJ

We can attempt to see what owserver is actually failing on by running
the following from the terminal.

sudo /usr/bin/owserver -c /etc/owfs.conf --debug

and you'll get output to the screen. Hopefully it will be meaningful,
or at least offer a clue.

You can redirect it to a file and attach that file (/tmp/owdebug.log)
to your next post.

sudo /usr/bin/owserver -c /etc/owfs.conf --debug > /tmp/owdebug.log 2>&1


-- 


Cheers
 Glenn

rorpi - read only raspberry pi & various weewx addons
https://github.com/glennmckechnie

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAAraAzgNu-pDnM6yaxUOjJztUi-5xj7rUhLGbMByZkDix-%2BCaQ%40mail.gmail.com.

Re: [weewx-user] "yesterday.outTemp" compared to "current.outTemp", et seq, for Yesterday page

[Thomas Keffer]

Unfortunately, no. The ImageGenerator can only make plots that end with the
current time.

-tk

On Fri, Apr 17, 2020 at 8:11 AM Messy Potamia 
wrote:

> Thanks, the tables are great.
> - - -
> Reading through the .tmpls & skin.conf, and
> http://www.weewx.com/docs/customizing.htm, I cannot glean how to tell the
> plot generator to generate a plot that is from the same time period 24
> hours ago. Is there a way to get those?
> Thanks,
> Phil
>
> On Friday, April 17, 2020 at 4:23:24 PM UTC+2, Messy Potamia wrote:
>>
>> Thanks, trying that now...
>>
>> On Friday, April 17, 2020 at 4:18:33 PM UTC+2, Thomas Keffer wrote:
>>>
>>> The two tags serve different purposes. The tag $yesterday represents an
>>> *aggregation* over the day. The tag $current represents a single
>>> record. There is an undocumented feature in v3.9.2 (documented in V4.0)
>>> that gets you what you want:
>>>
>>> The temperature 24 hours ago was
>>> $current(timestamp=$current.dateTime.raw-86400).outTemp
>>>
>>>
>>> -tk
>>>
>>> On Fri, Apr 17, 2020 at 7:01 AM Messy Potamia 
>>> wrote:
>>>
 The high/low table is working, showing but I'd like to get the upper
 table in yesterday.html.tmpl  to show the data from 86400 seconds ago,
 or one day ago, $day($days_ago=1), or $yesterday.  This doesn't seem to be
 working.
 In otherwords, on my Yesterday page, (weewx 3.9.2 Standard skins) I'd
 like it to show the same data as if you looked at it exactly 24 hrs ago.
 When I replace the $current.outTemp with $yesterday.outTemp,  it
 generates an error.
 Any ideas?   Thanks--

 --
 You received this message because you are subscribed to the Google
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to weewx...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/weewx-user/571e351c-cbbc-446a-8cc5-e7e96fa95a42%40googlegroups.com
 
 .

>>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/207b4e40-894c-42d2-88bc-9e1b4a31d7eb%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zECr1e9QFZXR9N%3DGqHZHUN5gOtVCwOY_icxqs7sAhqyXXQ%40mail.gmail.com.

[weewx-user] WeatherUnderground, WunderStation vs PWS

[Xant]

WU continue departure from its original foundation and purspose, where used 
to be a hub for PWSs. 

After transition, WU seems stagnant for years no further development, 
but killing feature and feature (API, weather webcam, etc), which make us 
"wunder" what is it's purpose now.

Might be a while, but just came to my attention that WU recently also 
killed WunderStation, which used to be a nice iPad only app specific for 
PWS monitoring.

WU still list WunderStation on their website, but no longer available in 
the Apple Store.

https://www.wunderground.com/wunderstation

If you used to have the app on your iPad, now it pops-up "retired" msg.

Thanks to have WeeWX... a truly independent WX app for the PWS community.


Xant

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4c20b0ac-bd66-4bad-8aad-c2d4da221d19%40googlegroups.com.

[weewx-user] Re: Datenbank zusammen legen.

[gjr80]

Hallo Günther,

Good to hear you have imported your data and WeeWX is running without error. 
You need WeeWX to recreate all of your NOAA format reports, to do this just 
delete the reports on your WeeWX machine and they will be recreated (including 
your earlier ones) on the next report cycle.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/742f0075-3036-403e-8fb8-80d685eb7435%40googlegroups.com.

[weewx-user] Re: Datenbank zusammen legen.

[Günther Wrana]

Hallo Leute

ich habe es geschafft das ich meine .csv Datei in meine Datenbank 
importiert habe und weewx nach dem Import auch weiter läuft.

Nun würde ich noch gerne Wissen den das habe ich in der ganzen 
Dokumentation von weewx nicht heraus gefunden.
Wie bringe ich weewx dazu die NOAA Datein neu zu erstellen.

Den dann wen ich das richtig verstehe müsste in der neue NOAA Datei vom 
2019-05 ja der 01 Tag ja ach dabei sein weil ich ja nur den 01.05.2019 in 
meine Datenbank dazu importiert haben.
Habe ich da richtig gedacht oder fehlt mir da noch etwas um diese NOAA 
Datei zu vervollständigen?

Danke schön Günther


hi Guys

I have managed to import my .csv file into my database and weewx continues 
to run after the import.

Now I would like to know that I have not found out in the entire weewx 
documentation.
How do I get weewx to recreate the NOAA files.

Then who I understand correctly should be in the new NOAA file from 2019-05 
yes the 01 day yes oh because I only imported the 01.05.2019 into my 
database.
Did I think correctly or am I missing something to complete this NOAA file?

Thank you Günther

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/09f89ec7-9aac-418b-884a-998ccd3f1d0b%40googlegroups.com.

[weewx-user] Re: Belchertown skin 1.1 released!

[Manfred Maier]

Hi Pat,
thanks for all your work!

After upgrading to version 1.1 (from 1.0) I get a weird behavior: Two of my 
sub-pages ("about" and "station") are not generated. The respective folders 
get generated, but the folders are empty and the index.html file is missing.

This is, how my "skin.conf" looks like:

[[ToDate]]

# Reports that show statistics "to date", such as day-to-date,

# week-to-date, month-to-date, etc.

[[[weewx_data]]]

template = json/weewx_data.json.tmpl


[[Belchertown]]

template = js/belchertown.js.tmpl


[[[home]]]

template = index.html.tmpl


[[[about]]]

template = about/index.html.tmpl


[[[graphs]]]

template = graphs/index.html.tmpl


[[[records]]]

template = records/index.html.tmpl


[[[reports]]]

template = reports/index.html.tmpl


[[[station]]]

template = station/index.html.tmpl


[[[webcam]]]

template = webcam/index.html.tmpl


[[[pi]]]

template = pi/index.html.tmpl


[[[manifest]]]

encoding = utf8

template = manifest.json.tmpl
 
All the other pages work (e.g. "webcam" that I've also added manually).

Probably I make quite an obvious mistake somewhere, but I cannot figure out 
what it is.
Would you have any idea what I'm doing wrong?

Thanks!
Manfred

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/47a19fc7-5414-48d4-ad3f-dd55449e1324%40googlegroups.com.

[weewx-user] Re: Get average or previous value?

[Messy Potamia]

To measure my lake elevation I use a MaxBotix ultrasonic range finder. In 
my python code, running on the Pi, which every 10 minutes takes a reading 
from the sensor and stores it in a static file on /dev/sda1, I do a simple 
QC check, comparing the previous reading and if the delta is unreasonable I 
set a data-invalid flag and the code leaves the previous reading for the 
weewx service to pickup. It's not perfect but prevents the kind of crazy 
spikes that comes from a bird or otter sitting under the sensor or other 
electronic artifact. 
Phil

On Tuesday, April 7, 2020 at 3:28:02 PM UTC+2, Jens-Jørgen Kjærgaard wrote:
>
> I have been a user for many years, and the software is usually running 
> smoothly.
> Some years back, I added the temperature of my lake as extraTemp1 - also 
> fine.
> Now, I also monitor the water level, by means of ultrasound, using the 
> HC-SR04. I have added this as extraTemp2, and don't min it shows as C in 
> the graphs.
> I have a little problem with that sensor, though. Sometimes it will show a 
> far off reading, which has to be ignored, ie if it is more than 2 cm off 
> the previous reading.
> But I can't figure out how to do that. Is there a way to store the 
> previous reading and use that (temporarily) for comparison? Or the average 
> of the readings up to that point?
>
> Jens-Jørgen Kjærgaard
> Tuenvej 818
> 9870 Sindal
> Denmark
> +45 21204417
> www.jensjk.dk
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/86ecb1ba-a81d-4145-9409-600ffabf9593%40googlegroups.com.

Re: [weewx-user] "yesterday.outTemp" compared to "current.outTemp", et seq, for Yesterday page

[Messy Potamia]

Thanks, the tables are great. 
- - -
Reading through the .tmpls & skin.conf, and 
http://www.weewx.com/docs/customizing.htm, I cannot glean how to tell the 
plot generator to generate a plot that is from the same time period 24 
hours ago. Is there a way to get those?
Thanks,
Phil

On Friday, April 17, 2020 at 4:23:24 PM UTC+2, Messy Potamia wrote:
>
> Thanks, trying that now...
>
> On Friday, April 17, 2020 at 4:18:33 PM UTC+2, Thomas Keffer wrote:
>>
>> The two tags serve different purposes. The tag $yesterday represents an 
>> *aggregation* over the day. The tag $current represents a single record. 
>> There is an undocumented feature in v3.9.2 (documented in V4.0) that gets 
>> you what you want:
>>
>> The temperature 24 hours ago was 
>> $current(timestamp=$current.dateTime.raw-86400).outTemp
>>
>>
>> -tk
>>
>> On Fri, Apr 17, 2020 at 7:01 AM Messy Potamia  
>> wrote:
>>
>>> The high/low table is working, showing but I'd like to get the upper 
>>> table in yesterday.html.tmpl  to show the data from 86400 seconds ago, 
>>> or one day ago, $day($days_ago=1), or $yesterday.  This doesn't seem to be 
>>> working.
>>> In otherwords, on my Yesterday page, (weewx 3.9.2 Standard skins) I'd 
>>> like it to show the same data as if you looked at it exactly 24 hrs ago. 
>>> When I replace the $current.outTemp with $yesterday.outTemp,  it 
>>> generates an error. 
>>> Any ideas?   Thanks--
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/571e351c-cbbc-446a-8cc5-e7e96fa95a42%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/207b4e40-894c-42d2-88bc-9e1b4a31d7eb%40googlegroups.com.

Re: [weewx-user] "yesterday.outTemp" compared to "current.outTemp", et seq, for Yesterday page

[Messy Potamia]

Thanks, trying that now...

On Friday, April 17, 2020 at 4:18:33 PM UTC+2, Thomas Keffer wrote:
>
> The two tags serve different purposes. The tag $yesterday represents an 
> *aggregation* over the day. The tag $current represents a single record. 
> There is an undocumented feature in v3.9.2 (documented in V4.0) that gets 
> you what you want:
>
> The temperature 24 hours ago was 
> $current(timestamp=$current.dateTime.raw-86400).outTemp
>
>
> -tk
>
> On Fri, Apr 17, 2020 at 7:01 AM Messy Potamia  > wrote:
>
>> The high/low table is working, showing but I'd like to get the upper 
>> table in yesterday.html.tmpl  to show the data from 86400 seconds ago, 
>> or one day ago, $day($days_ago=1), or $yesterday.  This doesn't seem to be 
>> working.
>> In otherwords, on my Yesterday page, (weewx 3.9.2 Standard skins) I'd 
>> like it to show the same data as if you looked at it exactly 24 hrs ago. 
>> When I replace the $current.outTemp with $yesterday.outTemp,  it 
>> generates an error. 
>> Any ideas?   Thanks--
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/571e351c-cbbc-446a-8cc5-e7e96fa95a42%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e4aa492f-aaf5-4351-bf9a-693957cd6001%40googlegroups.com.

[weewx-user] Re: "yesterday.outTemp" compared to "current.outTemp", et seq, for Yesterday page

[Messy Potamia]

Correction: it doesn't generate an error, but it doesn't return any data. 
The tabular data fields are blank for the ones which have 
$yesterday.[parameter].
What do you think I'm doing wrong?

On Friday, April 17, 2020 at 4:01:25 PM UTC+2, Messy Potamia wrote:
>
> The high/low table is working, showing but I'd like to get the upper table 
> in yesterday.html.tmpl  to show the data from 86400 seconds ago, or one 
> day ago, $day($days_ago=1), or $yesterday.  This doesn't seem to be working.
> In otherwords, on my Yesterday page, (weewx 3.9.2 Standard skins) I'd like 
> it to show the same data as if you looked at it exactly 24 hrs ago. 
> When I replace the $current.outTemp with $yesterday.outTemp,  it generates 
> an error. 
> Any ideas?   Thanks--
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/de00331b-0079-4565-87a7-7198896706f5%40googlegroups.com.

Re: [weewx-user] "yesterday.outTemp" compared to "current.outTemp", et seq, for Yesterday page

[Thomas Keffer]

The two tags serve different purposes. The tag $yesterday represents an
*aggregation* over the day. The tag $current represents a single record.
There is an undocumented feature in v3.9.2 (documented in V4.0) that gets
you what you want:

The temperature 24 hours ago was
$current(timestamp=$current.dateTime.raw-86400).outTemp


-tk

On Fri, Apr 17, 2020 at 7:01 AM Messy Potamia 
wrote:

> The high/low table is working, showing but I'd like to get the upper table
> in yesterday.html.tmpl  to show the data from 86400 seconds ago, or one
> day ago, $day($days_ago=1), or $yesterday.  This doesn't seem to be working.
> In otherwords, on my Yesterday page, (weewx 3.9.2 Standard skins) I'd like
> it to show the same data as if you looked at it exactly 24 hrs ago.
> When I replace the $current.outTemp with $yesterday.outTemp,  it generates
> an error.
> Any ideas?   Thanks--
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/571e351c-cbbc-446a-8cc5-e7e96fa95a42%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEDKtRv2tsEURbDMMR7_qCitit8pWj7ufi8Qj4W6r60GYA%40mail.gmail.com.

Re: [weewx-user] Re: "Formatting options with [un]expected results" -- using leafTemp1 for non-temperature measurement so trying to remove "°F"

[Messy Potamia]

--- Moving this issue to a new topic, current.tag versus yesterday.tag ---

On Friday, April 17, 2020 at 10:11:52 AM UTC+2, Messy Potamia wrote:
>
> The table data is working fine. As a header to the Yesterday page, I 
> notice 
>Yesterday's Wx Summary
>   $yesterday.dateTime
> .
> the tag yesterday doesn't seem to exist in .dateTime; I was expecting it 
> to give Yesterday's date. Of course :) 
> Also, I'm not sure the image generator is building the images.
> skin.conf excerpt:
> [[yesterday_images]]
> x_label_format = %d 
> bottom_label_format = %x %H:%M
> time_length = 97200# == 27 hours
> 
> [[[yesterdaybarometer]]]
> barometer
> 
> [[[yesterdaytempdew]]]
> outTemp
> dewpoint
> 
> yesterday.html.tmpl excerpt:
> 
>   Yesterday Statistics and Plots
> 
> 
>   
>   
>   
>   
>   
>   
>   
>   #if $week.extraTemp1.has_data
>   
>   #end if
> 
>
> Hope I'm not expecting too much. /var/log/weewx doesn't show any 
> complaints (default debug)
>
> Phil
>
>
>
>
>
> On Wednesday, April 15, 2020 at 11:26:58 PM UTC+2, Messy Potamia wrote:
>>
>> Okay thanks, I'll try that. 
>>
>>
>> On Wednesday, April 15, 2020 at 10:07:44 PM UTC+2, gjr80 wrote:
>>>
>>> Ah, OK, I have some notes for how to make similar changes to Seasons 
>>> that could serve as a simple checklist. Standard should not be too hard, in 
>>> a nutshell you just need to:
>>>
>>> 1. Create a yesterday.html.tmpl. I would base this off week.html.tmpl
>>> 2. Change $week to $yesterday in yesterday.html.tmpl
>>> 3. Change a couple of heading from Week to Yesterday
>>> 4. In skin.conf add yesterday plots
>>> 5. Change yesterday.html.tmpl to use your yesterday plots
>>> 6. You might want to remove the 'This Month' panel, just remove the 
>>> applicable div in its entirety (starts around line 201 in the template)
>>> 6. Add some navigation by adding a 'yesterday' button to each of the 
>>> other .html.tmpl templates in the skin (look at the navbar div in the 
>>> template)
>>> 7. Add yesterday.html.tmpl to skin.conf so it is generated
>>>
>>> Maybe one or two others but they will show up once you get the basic 
>>> page going. If you work through the template looking for week specific 
>>> things and changing them to yesterday you should be 90% there.
>>>
>>> Just remember backup what works.
>>>
>>> Gary
>>>
>>> On Thursday, 16 April 2020 05:30:30 UTC+10, Messy Potamia wrote:

 Standard. I saw it on someone's Seasons page and thought I'd like it 
 but on my Std page here. My other system although it has Seasons will stay 
 without it for now as it's across the ocean.

 PH

 On Wed, Apr 15, 2020, 12:54 gjr80  wrote:

> Which skin, Seasons or Standard?
>
> Gary
>
> -- 
> You received this message because you are subscribed to a topic in the 
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/QoUlovvIZoI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/03c147d6-3ffc-466a-805f-7457c07ead37%40googlegroups.com
> .
>


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ae423f80-840a-482e-ae04-5131b265b421%40googlegroups.com.

[weewx-user] "yesterday.outTemp" compared to "current.outTemp", et seq, for Yesterday page

[Messy Potamia]

The high/low table is working, showing but I'd like to get the upper table 
in yesterday.html.tmpl  to show the data from 86400 seconds ago, or one day 
ago, $day($days_ago=1), or $yesterday.  This doesn't seem to be working.
In otherwords, on my Yesterday page, (weewx 3.9.2 Standard skins) I'd like 
it to show the same data as if you looked at it exactly 24 hrs ago. 
When I replace the $current.outTemp with $yesterday.outTemp,  it generates 
an error. 
Any ideas?   Thanks--

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/571e351c-cbbc-446a-8cc5-e7e96fa95a42%40googlegroups.com.

[weewx-user] Re: Apple buys DarkSky, IBM own TheWeatherChannel and WU, what's the next shoe to drop?

[Messy Potamia]

Regarding next-shoe-to-drop...   let's all hope that IBM or whoever doesn't 
offer Tom enough $ to buy that new thirty-meter ocean cruiser he's been 
wanting, to sell all the rights to weewx for their commercial-only use. 

On Wednesday, April 1, 2020 at 8:07:56 PM UTC+2, Chris Richmond wrote:
>
> Just saw that Apple bought DarkSky, and the API will get disabled end of 
> 2021.  Also noticed that TheWeatherChannel's
> web site is reporting as "by IBM" now.
>
> Chris
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8b5e6d2b-dd17-4821-b93e-e9a20a97445e%40googlegroups.com.

Re: [weewx-user] Re: Cannot get Weewx to run on a Raspberry Pi 4

[Glenn McKechnie]

[...]
>
> pi@raspberrypi:~ $ sudo systemctl status owserver
> ● owserver.service - Backend server for 1-wire control
>Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor
> preset: enabled)
>Active: failed (Result: signal) since Wed 2020-04-15 22:58:23 EDT; 22h
> ago
>  Docs: man:owserver(1)
>   Process: 549 ExecStart=/usr/bin/owserver -c /etc/owfs.conf (code=killed,
> signal=SEGV)
>  Main PID: 549 (code=killed, signal=SEGV)

A SEGV is not good.

How did the installation of owserver go? And what's the version?

apt list --installed | grep owserver

> Apr 15 22:58:23 raspberrypi systemd[1]: owserver.service: Service
> RestartSec=100ms expired, scheduling restart.
> Apr 15 22:58:23 raspberrypi systemd[1]: owserver.service: Scheduled restart
>
> job, restart counter is at 5.
> Apr 15 22:58:23 raspberrypi systemd[1]: Stopped Backend server for 1-wire
> control.
> Apr 15 22:58:23 raspberrypi systemd[1]: owserver.service: Start request
> repeated too quickly.
> Apr 15 22:58:23 raspberrypi systemd[1]: owserver.service: Failed with
> result 'signal'.
> Apr 15 22:58:23 raspberrypi systemd[1]: Failed to start Backend server for
> 1-wire control.

[...]
>
> OWFS.CONF  Follows:
>

That appears okay.

[...]

> WEEWX.CONF follows:
>
>  Options for extension 'owfs'
> [OWFS]
> interface = localhost:4304
> driver = user.owfs
> [[sensor_type]]
> [[sensor_map]]
> outTemp = /uncached/28.6E175D04/temperature

And that appears okay as well.

> Again, thank you for all of your help. I really appreciate it. The thing
> that confuses me is that everything works on a PC running Ubuntu but not on

Somethings not right on the Pi, and if the owserver won't start , nor python-ow?

Do you have the pi's 1-wire interface enabled? If so try disabling it.

sudo raspi-config
   Option 5? Interfacing options
   P7 1-wire  enable or disable.
(or something like that). You are after the option to enable/disable
one-wire interface. Disable it.

Then see if owserver starts after you reboot the Pi

--


Cheers
 Glenn

rorpi - read only raspberry pi & various weewx addons
https://github.com/glennmckechnie

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAAraAzg9K%2BATYmD%3DfCsM2heoOo4GahsyEH5ayezD12oNfY_5gw%40mail.gmail.com.

Re: [weewx-user] wee_import CSV interval = 1 vs. archive_interval = 300?

[William Burton]

Hello Thomas,

Thanks for the pointer to the SQL solution. I can see that method as fine 
for a one-time or infrequent interval conversions. The main part that 
groups and averages most columns is straightforward but the part that uses 
trig functions to calculate averages for wind direction and speed was 
completely unexpected. I'm wondering what is an authoritative source for 
these calculations?

For a couple of reasons, I'd prefer a solution in Python. First, the driver 
I'm implementing for the Columbia Weather MicroServer won't initially have 
the ability to automatically catch up missing data by implementing the 
genArchiveRecords() method in the driver so I'll have to manually import 
data from time to time when observations have been missed. Secondly, since 
I have to load 900 files, the CSV importer won't work for me as-is so it 
looks like I'll have to write a custom importer anyways. While I'm at it, I 
may try to implement accumulation logic as part of the import. The classes 
in bin/weewx/accum.py look like they would be very helpful. After that it 
would be a matter of figuring out the row grouping logic.

Thanks,
-Bill

On Thursday, April 16, 2020 at 8:18:08 AM UTC-4, Thomas Keffer wrote:
>
> Hi, Bill. 
>
> 1. WeeWX can handle mixed intervals.
> 2. The time, field dateTime, is indexed, so it does not slow down reports 
> as much as you think. My database is about 1.5 M records and it performs 
> fine on a very slow machine. The exception is queries that 
> involving finding the min and max of the whole database.
> 3. If you decide you want to consolidate into 5 minute intervals, user 
> Cameron came up with a guide that uses some clever SELECT statements to do 
> the job. Find it on the Wiki 
> 
> .
>
> -tk
>
> On Thu, Apr 16, 2020 at 1:47 AM William Burton  > wrote:
>
>> Hello,
>>
>> I've been testing a CSV import configuration with wee_import. The CSV 
>> data is in 1 minute intervals whereas weewx.conf has an archive_interval = 
>> 300 for 5 minutes. my csv.conf has interval = 1 to match the data interval 
>> (which has a few gaps).
>>
>> What I'm finding is the imported data is still in one minute intervals 
>> while data archived from the driver has five minute intervals:
>>
>> sqlite> select interval, count(*) count from archive group by interval;
>> intervalcount
>> --  --
>> 1   51234
>> 5   12259
>>
>>1. Will having mixed intervals in the same database cause any issues 
>>with reporting such as incorrect time scales in graphs?
>>2. Wouldn't archive records with a one minute interval slow down 
>>report generation?
>>3. I calculated that I have around 900 files to import for a total of 
>>almost 1.3 million records. If these records could be averaged to only 
>> one 
>>record per five minutes, then it would be only 260,000 records which 
>> seems 
>>more reasonable.
>>
>> I'm using WeeWX 4.0.0b18.
>>
>> Thanks for any assistance,
>> -Bill
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/0151a436-a259-4c12-be92-c20c5e796711%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/12418dae-97bb-442b-86c5-3f2750349c09%40googlegroups.com.

Re: [weewx-user] Re: Cannot get Weewx to run on a Raspberry Pi 4

[michael form]

Glenn:

Well, some progress (perhaps), but not enough.To make things easier to 
read, responses from a command are in BLUE and configuration files are in 
RED.

I followed your suggestions and "service weewx status" came back with the 
following:

pi@raspberrypi:~ $ service weewx status
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx; generated)
   Active: active (exited) since Thu 2020-04-16 21:30:28 EDT; 1min 38s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 2565 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)

Apr 16 21:30:28 raspberrypi weewx[2580]: owfs: driver version is 0.21
Apr 16 21:30:28 raspberrypi weewx[2580]: owfs: interface is localhost:4304
Apr 16 21:30:28 raspberrypi weewx[2580]: owfs: sensor map is {'outTemp': 
'/uncached/28.6E175D04/temperature'}
Apr 16 21:30:28 raspberrypi weewx[2580]: owfs: sensor type map is {}
Apr 16 21:30:28 raspberrypi weewx[2580]: owfs: polling interval is 10
Apr 16 21:30:28 raspberrypi weewx[2580]: owfs: sensor unit system is metric
Apr 16 21:30:33 raspberrypi OWFS[2580]: DEFAULT: owlib.c:(52) No valid 
1-wire buses found
Apr 16 21:30:33 raspberrypi OWFS[2580]: engine: Import of driver failed:  
()
Apr 16 21:30:33 raspberrypi OWFS[2580]: engine: Unable to load driver:
Apr 16 21:30:33 raspberrypi OWFS[2580]:   Exiting...

This is somewhat better than the previous result (one less error). Still 
cannot find a "valid 1-Wire bus".

RUNNING THE FOLLOWING:

pi@raspberrypi:~ $ sudo systemctl status owserver
● owserver.service - Backend server for 1-wire control
   Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: signal) since Wed 2020-04-15 22:58:23 EDT; 22h 
ago
 Docs: man:owserver(1)
  Process: 549 ExecStart=/usr/bin/owserver -c /etc/owfs.conf (code=killed, 
signal=SEGV)
 Main PID: 549 (code=killed, signal=SEGV)

Apr 15 22:58:23 raspberrypi systemd[1]: owserver.service: Service 
RestartSec=100ms expired, scheduling restart.
Apr 15 22:58:23 raspberrypi systemd[1]: owserver.service: Scheduled restart 
job, restart counter is at 5.
Apr 15 22:58:23 raspberrypi systemd[1]: Stopped Backend server for 1-wire 
control.
Apr 15 22:58:23 raspberrypi systemd[1]: owserver.service: Start request 
repeated too quickly.
Apr 15 22:58:23 raspberrypi systemd[1]: owserver.service: Failed with 
result 'signal'.
Apr 15 22:58:23 raspberrypi systemd[1]: Failed to start Backend server for 
1-wire control.

Throws the error above, Failed to start Backend server for 1-wire control.

I then stopped, enabled and started the owserver.
"Starting" fails as below:

pi@raspberrypi:~ $ sudo systemctl stop owserver

pi@raspberrypi:~ $ sudo systemctl enable owserver
Synchronizing state of owserver.service with SysV service script with 
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable owserver

pi@raspberrypi:~ $ sudo systemctl start owserver
Job for owserver.service failed because a fatal signal was delivered to the 
control process.
See "systemctl status owserver.service" and "journalctl -xe" for details.



OWFS.CONF  Follows:

# Sample configuration file for the OWFS suite for Debian GNU/Linux.
#
#
# This is the main OWFS configuration file. You should read the
# owfs.conf(5) manual page in order to understand the options listed
# here.

 SOURCES 
#
# With this setup, any client (but owserver) uses owserver on the
# local machine...
###! server: server = localhost:4304
#
# ...and owserver uses the real hardware, by default fake devices
# This part must be changed on real installation
## server: FAKE = DS18S20,DS2405
#
 USB device: DS9490
server: usb = all
#
# Serial port: DS9097
#server: device = /dev/ttyS1
#
# owserver tcp address
#server: server = 192.168.10.1:3131
#
# random simulated device
#server: FAKE = DS18S20,DS2405
#
# OWFS ##
#
#mountpoint = /mnt/1wire
#allow_other
#
### OWHTTPD #

###http: port = 2121

### OWFTPD ##

###ftp: port = 2120

### OWSERVER 

#
# OWFS ##
#
#mountpoint = /mnt/1wire
#allow_other
#
### OWHTTPD #

###http: port = 2121

### OWFTPD ##

###ftp: port = 2120

### OWSERVER 

###server: port = localhost:4304

server: port = 4304


WEEWX.CONF follows:

 Options for extension 'owfs'
[OWFS]
interface = localhost:4304
driver = user.owfs
[[sensor_type]]
[[sensor_map]]
outTemp = /uncached/28.6E175D04/temperature


Again, thank you for all of your help. I really appreciate it. The thing 
that confuses me is that everything works on a PC running Ubuntu but not on 
the Pi.

[weewx-user] Re: FTP Error uploading to website

[chris op]

Thanks everyone for the help!

I did play around, it was a simple error and it does work now:

I commented out the port line and changed secure_ftp to false:

secure_ftp = False
# port = 21

Actually, I thought I have tested this before without success. Anyway, 
thanks again!


Am Dienstag, 14. April 2020 18:06:06 UTC+2 schrieb chris op:
>
> Hi! 
>
> All was working fine with uploading the weewx weather data to my website. 
> However, this suddenly stopped a couple of weeks ago. I was realizing one 
> day, that the website was not updated anymore.
>
> Looking into the syslog what happens and I found the following errors:
> Apr 14 17:46:03 raspberrypi weewx[27105]: ftpupload: Attempt #1. Failed 
> uploading /home/www/xyz.de/daywind.png to sxyz.xyzserver.host. Reason: 
> 425 Unable to build data connection: Operation not permitted
> This changes during to process into:
> Apr 14 17:46:13 raspberrypi weewx[27105]: ftpupload: Attempt #3. Failed 
> uploading /home/www/xyz.de/neowx/daywind.png to sxyz.xyzserver.host. 
> Reason: 200 Type set to I
> or
> Apr 14 17:51:20 raspberrypi weewx[27105]: ftpupload: Attempt #1. Failed 
> uploading /home/www/xyz.de/belchertown/graphs/index.html to 
> sxyz.xyzserver.host. Reason: 550 /home/www/xyz.de/belchertown/graphs: 
> File exists
>
> I have tried to play around in the file weewx.conf and changed the 
> parameters there but this only led to other error messages like 550 or 500.
>
> My configuration looks as follows:
> >
> # FTP'ing the results to a webserver is treated as just another report,
> # albeit one with an unusual report generator!
> skin = Ftp
> 
> # If you wish to use FTP, uncomment and fill out the next four 
> lines.
> # Use quotes around passwords to guard against parsing errors.
> user = web83
>
> password = 'xyz'
> server = sxyz.xyzserver.host
> path = /home/www/xyz.de/
> 
> # Set to True for an FTP over TLS (FTPS) connection. Not all 
> servers
> # support this.
>  secure_ftp = True 
> 
> # To upload files from something other than what HTML_ROOT is set
> # to above, specify a different HTML_ROOT here.
> # HTML_ROOT = /var/www/html/weewx
> 
> # Most FTP servers use port 21
> port = 21
> 
> # Set to 1 to use passive mode, zero for active mode
> passive = 1
> >>
>
> Can anyone help? I am a rooky but trying hard to become better with linux 
> and this kind of software and programming.
>
> Thank you!
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6ebc4bcd-2ce0-41b7-981d-0c2a6f1d0589%40googlegroups.com.

Re: [weewx-user] Re: "Formatting options with [un]expected results" -- using leafTemp1 for non-temperature measurement so trying to remove "°F"

[Messy Potamia]

The table data is working fine. As a header to the Yesterday page, I notice 
   Yesterday's Wx Summary
  $yesterday.dateTime
.
the tag yesterday doesn't seem to exist in .dateTime; I was expecting it to 
give Yesterday's date. Of course :) 
Also, I'm not sure the image generator is building the images.
skin.conf excerpt:
[[yesterday_images]]
x_label_format = %d 
bottom_label_format = %x %H:%M
time_length = 97200# == 27 hours

[[[yesterdaybarometer]]]
barometer

[[[yesterdaytempdew]]]
outTemp
dewpoint

yesterday.html.tmpl excerpt:

  Yesterday Statistics and Plots


  
  
  
  
  
  
  
  #if $week.extraTemp1.has_data
  
  #end if


Hope I'm not expecting too much. /var/log/weewx doesn't show any complaints 
(default debug)

Phil





On Wednesday, April 15, 2020 at 11:26:58 PM UTC+2, Messy Potamia wrote:
>
> Okay thanks, I'll try that. 
>
>
> On Wednesday, April 15, 2020 at 10:07:44 PM UTC+2, gjr80 wrote:
>>
>> Ah, OK, I have some notes for how to make similar changes to Seasons that 
>> could serve as a simple checklist. Standard should not be too hard, in a 
>> nutshell you just need to:
>>
>> 1. Create a yesterday.html.tmpl. I would base this off week.html.tmpl
>> 2. Change $week to $yesterday in yesterday.html.tmpl
>> 3. Change a couple of heading from Week to Yesterday
>> 4. In skin.conf add yesterday plots
>> 5. Change yesterday.html.tmpl to use your yesterday plots
>> 6. You might want to remove the 'This Month' panel, just remove the 
>> applicable div in its entirety (starts around line 201 in the template)
>> 6. Add some navigation by adding a 'yesterday' button to each of the 
>> other .html.tmpl templates in the skin (look at the navbar div in the 
>> template)
>> 7. Add yesterday.html.tmpl to skin.conf so it is generated
>>
>> Maybe one or two others but they will show up once you get the basic page 
>> going. If you work through the template looking for week specific things 
>> and changing them to yesterday you should be 90% there.
>>
>> Just remember backup what works.
>>
>> Gary
>>
>> On Thursday, 16 April 2020 05:30:30 UTC+10, Messy Potamia wrote:
>>>
>>> Standard. I saw it on someone's Seasons page and thought I'd like it but 
>>> on my Std page here. My other system although it has Seasons will stay 
>>> without it for now as it's across the ocean.
>>>
>>> PH
>>>
>>> On Wed, Apr 15, 2020, 12:54 gjr80  wrote:
>>>
 Which skin, Seasons or Standard?

 Gary

 -- 
 You received this message because you are subscribed to a topic in the 
 Google Groups "weewx-user" group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/weewx-user/QoUlovvIZoI/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 weewx...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/03c147d6-3ffc-466a-805f-7457c07ead37%40googlegroups.com
 .

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/dfa38211-d423-42ce-867c-82e7e3de5a3f%40googlegroups.com.