[weewx-user] Re: Date and time format in the seasons skin

[Peter Gillbrand]

Thanks a lot Gary! The header part worked perfectly. I´ll try the plots 
tomorrow

On Tuesday, May 4, 2021 at 10:44:10 PM UTC+2 gjr80 wrote:

> Hi,
>
> There are a few ways to handle the date-time in the header. Basically the 
> options come down to changing the format used by the tag used to generate 
> that date-time or altering the default format used by date-time tags in all 
> reports or just the Seasons skin. I suspect you probably want the former.
>
> To change the format used by the tag used to generate that date-time you 
> need to edit skins/Seasons/titlebar.inc and change the following line from 
> (untested):
>
> $current.dateTime
>
> to:
>
> $current.dateTime.format(format_string="%Y-%m-%d 
> %H:%M")
>
> Save the file and the change should occur on the next report cycle. For 
> info, the available format codes are listed in the table here 
> 
> .
>
> For the date-time formats used in the plot labels you need to alter 
> settings under the [ImageGenerator] stanza in the Season skin config file 
> (skins/Seasons/skin.conf), specifically the bottom_label_format setting. 
> The ImageGenerator label options are covered here 
>  in the 
> Customization Guide. The format codes used by bottom_label_format are the 
> same as linked earlier in this post. Note also that bottom_label_format is 
> set for each set (day, week, month, year) of plots.
>
> The above changes should be retained across WeeWX upgrades but you may 
> wish to make note of your changes should you need to restore them in the 
> future.
>
> Gary
>
> On Wednesday, 5 May 2021 at 05:41:33 UTC+10 p.gil...@gmail.com wrote:
>
>> This should be a simple config question but I have failed. How can I 
>> change the date and time format from something like 05/04/2021 09:15:00 PM 
>> to 2021-05-04 21:15 in the header of the Seasons skin as well as in the day 
>> plots? 
>> Thanks for any support to solve this minor but irritating issue. 
>>
>>

-- 
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/4333e44e-ed0c-46b1-b5d7-b09ccac22535n%40googlegroups.com.

Re: [weewx-user] Re: possible for weewx to accept data via MQTT devices?

[bell...@gmail.com]

A few additional things to consider.
From, https://tasmota.github.io/docs/BME280/, your json data is ‘nested’. 
Meaning the incoming names in MQTTSubscribe will be BME280_Pressure, 
BME280_Temperature, and BME280_Humidity. 
You will want to use the ‘ignore’ option for PressureUnit and TempUnit.
Due to the way MQTTSubscribe handles date/time data, the Time field is a 
bit more interesting. I would also ‘ignore’ it. This just means that 
MQTTSubscribe will not try to check that the data is in the time interval 
being processed by WeeWX. 
Configuring MQTTSubscribe can be a bit daunting, so just shout with any 
additional questions.
rich

On Tuesday, 4 May 2021 at 15:09:17 UTC-4 eric.k...@gmail.com wrote:

> That does sound similar.  Thank you for that pointer!
>
> I want to get the Tasmota firmware to output MQTT messags containing the 
> barometric pressure. 
> Then, weewx would need to take in that MQTT message and assign the data to 
> the stock 'barometer' variable from the database schema.
>
> On Tuesday, May 4, 2021 at 2:02:41 PM UTC-5 p.gil...@gmail.com wrote:
>
>> I have manage to get a weather station to be the main provider of data to 
>> R-Pi based Weewx installation with add on data into the database coming 
>> from a sensor providing MQTT messages. If that it is similar to what you 
>> are aiming for,  maybe this conversation can provide guidance 
>> https://github.com/bellrichm/WeeWX-MQTTSubscribe/discussions/132
>>
>> On Tuesday, May 4, 2021 at 7:24:13 PM UTC+2 eric.k...@gmail.com wrote:
>>
>>> > DId you read
>>> > https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring
>>>
>>> No, I wanted to make sure MQTT was usable simultaneously with another 
>>> weewx "driver", before I spent a lot of time on it.
>>>
>>> Thanks for the pointer to service vs. driver configuration!
>>> I'll read through it.
>>> On Tuesday, May 4, 2021 at 11:33:07 AM UTC-5 Greg Troxel wrote:
>>>

 Eric Koester  writes: 

 > Thanks for the pointer, Peter. 
 > I looked through the install instructions and I don't see any mention 
 of 
 > the weewx.conf file. 

 DId you read 

 https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring 

 Agreed that it doesn't say that it is talking about the config file. 

 A big point is driver vs service. It seems clear that you want 
 service, where MQTT input is secondary. 



-- 
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/1e14c8b6-c114-47fc-b782-0fc53d649dc2n%40googlegroups.com.

[weewx-user] Re: Date and time format in the seasons skin

[gjr80]

Hi,

There are a few ways to handle the date-time in the header. Basically the 
options come down to changing the format used by the tag used to generate 
that date-time or altering the default format used by date-time tags in all 
reports or just the Seasons skin. I suspect you probably want the former.

To change the format used by the tag used to generate that date-time you 
need to edit skins/Seasons/titlebar.inc and change the following line from 
(untested):

$current.dateTime

to:

$current.dateTime.format(format_string="%Y-%m-%d 
%H:%M")

Save the file and the change should occur on the next report cycle. For 
info, the available format codes are listed in the table here 

.

For the date-time formats used in the plot labels you need to alter 
settings under the [ImageGenerator] stanza in the Season skin config file 
(skins/Seasons/skin.conf), specifically the bottom_label_format setting. 
The ImageGenerator label options are covered here 
 in the 
Customization Guide. The format codes used by bottom_label_format are the 
same as linked earlier in this post. Note also that bottom_label_format is 
set for each set (day, week, month, year) of plots.

The above changes should be retained across WeeWX upgrades but you may wish 
to make note of your changes should you need to restore them in the future.

Gary

On Wednesday, 5 May 2021 at 05:41:33 UTC+10 p.gil...@gmail.com wrote:

> This should be a simple config question but I have failed. How can I 
> change the date and time format from something like 05/04/2021 09:15:00 PM 
> to 2021-05-04 21:15 in the header of the Seasons skin as well as in the day 
> plots? 
> Thanks for any support to solve this minor but irritating issue. 
>
>

-- 
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/0f05fb17-b8cc-4a49-b4a2-4f5c078da4e2n%40googlegroups.com.

[weewx-user] Re: Clean the database(s) before a certain date

[gjr80]

The thread you linked describes the process to (1) have WeeWX use a clean 
database and (2) change the driver from simulator to FineOffsetUSB (fousb). 
Step 3 was all about the latter, it has nothing to do with clearing the 
database. If you simply want to have WeeWX start with a clean database then 
the easiest thing to do is to stop weewx, delete the database file (a 
default install will use database weewx.sdb located in either 
/var/lib/weewx or /home/weewx/archive) and then restart WeeWX. WeeWX will 
automatically create a clean database during startup. Unless you have 
manually changed the structure of your archive this will give you a clean 
database with the same structure (schema) as the original.

Of course if you want to keep the old database/data you should make a copy 
of the database before deleting.

Gary

On Wednesday, 5 May 2021 at 05:14:38 UTC+10 ton...@gmail.com wrote:

> Have started operation of WeeWX with the Simulator.
> Now switched to Tempest, and getting real data.
>
> The thread 
> https://groups.google.com/g/weewx-user/c/NJ_XFLbWrNc/m/fpRqGIBWBQAJ 
> describes a method to transition the database(s) from Simulator to 'Real' 
> sensor by defining completely new database(s).
> But what is the easy way to *wipe *the data in the database(s) *while* 
> maintaining the datastructure?
> In other words:
> can the goal be achieved with less action than redefinition according to 
> steps 2.+3. in the quoted message?
>

-- 
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/53cc57b3-946c-4c63-a03f-be2b443386fdn%40googlegroups.com.

[weewx-user] Date and time format in the seasons skin

[Peter Gillbrand]

This should be a simple config question but I have failed. How can I change 
the date and time format from something like 05/04/2021 09:15:00 PM to 
2021-05-04 21:15 in the header of the Seasons skin as well as in the day 
plots? 
Thanks for any support to solve this minor but irritating issue. 

-- 
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/17ddb591-439f-42ae-ab62-4f16a5ee2e93n%40googlegroups.com.

[weewx-user] Clean the database(s) before a certain date

[Ton vanN]

Have started operation of WeeWX with the Simulator.
Now switched to Tempest, and getting real data.

The thread 
https://groups.google.com/g/weewx-user/c/NJ_XFLbWrNc/m/fpRqGIBWBQAJ 
describes a method to transition the database(s) from Simulator to 'Real' 
sensor by defining completely new database(s).
But what is the easy way to *wipe *the data in the database(s) *while* 
maintaining the datastructure?
In other words:
can the goal be achieved with less action than redefinition according to 
steps 2.+3. in the quoted message?

-- 
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/21250326-e1b4-4ba7-88ff-a35844c0f529n%40googlegroups.com.

Re: [weewx-user] Re: possible for weewx to accept data via MQTT devices?

[Eric Koester]

That does sound similar.  Thank you for that pointer!

I want to get the Tasmota firmware to output MQTT messags containing the 
barometric pressure. 
Then, weewx would need to take in that MQTT message and assign the data to 
the stock 'barometer' variable from the database schema.

On Tuesday, May 4, 2021 at 2:02:41 PM UTC-5 p.gil...@gmail.com wrote:

> I have manage to get a weather station to be the main provider of data to 
> R-Pi based Weewx installation with add on data into the database coming 
> from a sensor providing MQTT messages. If that it is similar to what you 
> are aiming for,  maybe this conversation can provide guidance 
> https://github.com/bellrichm/WeeWX-MQTTSubscribe/discussions/132
>
> On Tuesday, May 4, 2021 at 7:24:13 PM UTC+2 eric.k...@gmail.com wrote:
>
>> > DId you read
>> > https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring
>>
>> No, I wanted to make sure MQTT was usable simultaneously with another 
>> weewx "driver", before I spent a lot of time on it.
>>
>> Thanks for the pointer to service vs. driver configuration!
>> I'll read through it.
>> On Tuesday, May 4, 2021 at 11:33:07 AM UTC-5 Greg Troxel wrote:
>>
>>>
>>> Eric Koester  writes: 
>>>
>>> > Thanks for the pointer, Peter. 
>>> > I looked through the install instructions and I don't see any mention 
>>> of 
>>> > the weewx.conf file. 
>>>
>>> DId you read 
>>>
>>> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring 
>>>
>>> Agreed that it doesn't say that it is talking about the config file. 
>>>
>>> A big point is driver vs service. It seems clear that you want 
>>> service, where MQTT input is secondary. 
>>>
>>>

-- 
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/03662dff-ffb3-439a-af42-c748cee4f29fn%40googlegroups.com.

Re: [weewx-user] Re: possible for weewx to accept data via MQTT devices?

[Peter Gillbrand]

I have manage to get a weather station to be the main provider of data to 
R-Pi based Weewx installation with add on data into the database coming 
from a sensor providing MQTT messages. If that it is similar to what you 
are aiming for,  maybe this conversation can provide 
guidance https://github.com/bellrichm/WeeWX-MQTTSubscribe/discussions/132

On Tuesday, May 4, 2021 at 7:24:13 PM UTC+2 eric.k...@gmail.com wrote:

> > DId you read
> > https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring
>
> No, I wanted to make sure MQTT was usable simultaneously with another 
> weewx "driver", before I spent a lot of time on it.
>
> Thanks for the pointer to service vs. driver configuration!
> I'll read through it.
> On Tuesday, May 4, 2021 at 11:33:07 AM UTC-5 Greg Troxel wrote:
>
>>
>> Eric Koester  writes:
>>
>> > Thanks for the pointer, Peter.
>> > I looked through the install instructions and I don't see any mention 
>> of 
>> > the weewx.conf file.
>>
>> DId you read
>>
>> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring
>>
>> Agreed that it doesn't say that it is talking about the config file.
>>
>> A big point is driver vs service. It seems clear that you want
>> service, where MQTT input is secondary.
>>
>>

-- 
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/11b9113d-aaa7-46a1-9489-c15efceea72fn%40googlegroups.com.

Re: [weewx-user] Re: possible for weewx to accept data via MQTT devices?

[Eric Koester]

> DId you read
> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring

No, I wanted to make sure MQTT was usable simultaneously with another weewx 
"driver", before I spent a lot of time on it.

Thanks for the pointer to service vs. driver configuration!
I'll read through it.
On Tuesday, May 4, 2021 at 11:33:07 AM UTC-5 Greg Troxel wrote:

>
> Eric Koester  writes:
>
> > Thanks for the pointer, Peter.
> > I looked through the install instructions and I don't see any mention of 
> > the weewx.conf file.
>
> DId you read
>
> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring
>
> Agreed that it doesn't say that it is talking about the config file.
>
> A big point is driver vs service. It seems clear that you want
> service, where MQTT input is secondary.
>
>

-- 
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/672f9643-a71f-4fb3-89ef-7c8c140888dan%40googlegroups.com.

Re: [weewx-user] Re: possible for weewx to accept data via MQTT devices?

[Greg Troxel]

Eric Koester  writes:

> Thanks for the pointer, Peter.
> I looked through the install instructions and I don't see any mention of 
> the weewx.conf file.

DId you read

  https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring

Agreed that it doesn't say that it is talking about the config file.

A big point is driver vs service.   It seems clear that you want
service, where MQTT input is secondary.

-- 
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/rmiwnsewjb8.fsf%40s1.lexort.com.


signature.asc
Description: PGP signature

[weewx-user] Re: possible for weewx to accept data via MQTT devices?

[Eric Koester]

Thanks for the pointer, Peter.
I looked through the install instructions and I don't see any mention of 
the weewx.conf file.

Does anyone know:
1. does MQTT need to be declared as a station_type in the weewx.conf file?
2. if so, is it ok to have more than one station_type in the weewx.conf 
file?

Right now, I've got my station_type set to SDR so I can accept weather 
station data via an RTL-SDR and rtl_433.

example:
##
#   This section is for information about the station.
[Station] 
# Set to type of station hardware. There must be a corresponding stanza
# in this file with a 'driver' parameter indicating the driver to be 
used.
station_type = SDR

Thanks for all the info.
Eric

On Tuesday, May 4, 2021 at 5:30:58 AM UTC-5 p.gil...@gmail.com wrote:

> Check this: https://github.com/bellrichm/WeeWX-MQTTSubscribe
>
> On Tuesday, May 4, 2021 at 12:31:55 AM UTC+2 eric.k...@gmail.com wrote:
>
>> I'm currently reading data into weewx using an Acurite Atlas, an RTL-SDR, 
>> rtl_433, and weewx-sdr.
>>
>> I'd like to import barometric pressure sensor data into weewx via MQTT 
>> from a wifi pressure sensor.  Is that possible?  
>> If yes, is it possible to import data via 2 different drivers?
>>
>> The potential plan is to connect an BME280 sensor (via i2c) to a ESP8266 
>> wifi module loaded with Tasmota open-source firmware.
>> see:  https://tasmota.github.io/docs/BME280/
>> Tasmota sends the data a tele/%topic%/SENSOR JSON response.
>>
>> Assuming that weewx can accept data via MQTT, I'm not sure what the 
>> device-facing variable name would be inside of weewx.
>> example of known device-facing variable name:  
>> outTemp = temperature.001.AcuriteAtlaspacket
>>
>

-- 
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/f2f02d20-9306-4b8d-8b8b-f1de7c395307n%40googlegroups.com.

[weewx-user] Re: possible for weewx to accept data via MQTT devices?

[Peter Gillbrand]

Check this: https://github.com/bellrichm/WeeWX-MQTTSubscribe

On Tuesday, May 4, 2021 at 12:31:55 AM UTC+2 eric.k...@gmail.com wrote:

> I'm currently reading data into weewx using an Acurite Atlas, an RTL-SDR, 
> rtl_433, and weewx-sdr.
>
> I'd like to import barometric pressure sensor data into weewx via MQTT 
> from a wifi pressure sensor.  Is that possible?  
> If yes, is it possible to import data via 2 different drivers?
>
> The potential plan is to connect an BME280 sensor (via i2c) to a ESP8266 
> wifi module loaded with Tasmota open-source firmware.
> see:  https://tasmota.github.io/docs/BME280/
> Tasmota sends the data a tele/%topic%/SENSOR JSON response.
>
> Assuming that weewx can accept data via MQTT, I'm not sure what the 
> device-facing variable name would be inside of weewx.
> example of known device-facing variable name:  
> outTemp = temperature.001.AcuriteAtlaspacket
>

-- 
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/5c1d72f7-5af1-4d2c-8daf-f06f0c2f269dn%40googlegroups.com.

Re: [weewx-user] Re: Use of template for generation of uploadfile for HetWeerActueel

[Ton vanN]

New template now running without errors (on WeeWX4.4.0 on 
Raspian_Buster) and the output-file checked to be compatible with the 
serversoftware of HetWeerActueel (version HWA2.0)
Backwards compatibility of this new template with older WeeWX-versions 
(using Python2.x, and now using the 'old' template) *not* checked!

Duplicate posting is not a good idea.
Also because the members of HetWeerActueel are >90% dutch-speaking, 
therefore the resulting solution is described (in  dutch) at 
https://www.hetweeractueel.nl/forum/viewtopic.php?p=73156#p73156

Would like to thank all contributors to my probing & trying:
your hints really assisted to keep me to move forward!

Op maandag 3 mei 2021 om 00:55:23 UTC+2 schreef gjr80:

> It's a bit of python 2v3 and poor coding. The first thing to remember is 
> that in a WeeWX Cheetah template .formatted (now .formatted()) returns a 
> string, .raw returns the raw value; typically an int or a float or None 
> (though it could also be a string if the underlying field is a string but 
> there are none of those in any of the WeeWX shipped schemas).
>
> Under python2 you can compare strings to numerics (int and float) without 
> error, that being said you will not get the correct answer but it won't 
> raise an error. Try doing this:
>
> gary@buster5:~$ python2
> Python 2.7.16 (default, Oct 10 2019, 22:02:15) 
> [GCC 8.3.0] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> "5" > 4
> True
> >>> "3" > 4
> True
> >>> 
>
> Note that the second expression gives and incorrect answer. Python 3 is a 
> little more picky, trying the same under python3 raises an error:
>
> gary@buster5:~$ python3
> Python 3.7.3 (default, Jan 22 2021, 20:04:44) 
> [GCC 8.3.0] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> "5" > 4
>
> Traceback (most recent call last):
>   File "", line 1, in 
> TypeError: '>' not supported between instances of 'str' and 'int'
>
> Then add into the mix the fact that a .raw could return the python value 
> None. Python 2 will happily allow None in a comparison but python3 will 
> not, it will raise a TypeError albeit with a different error message.
>
> So getting back to the original comparison expression in the report. Under 
> python2 it will operate without error, it may give the wrong result under 
> certain conditions but it will not cause an error that will force the 
> template generation to abort. Under python3 the expression will raise an 
> error on every generation and the template will abort. The obvious solution 
> is to change .format to .raw, that will work under most conditions but if 
> $trend.barometer.raw is ever None (quite possible on startup or if there 
> has been an interruption) it will fail. The solution is to either catch the 
> error and deal with it or alter the conditional to check for None, eg 
> (untested):
>
> #if $trend.barometer.raw is not None and $trend.barometer.raw > 0
> #do something
> #end if
>
> Gary
> On Monday, 3 May 2021 at 07:56:41 UTC+10 peterq...@gmail.com wrote:
>
>> Yes. 
>>
>> I can't find the official documentation but See 
>> https://devopedia.org/python-2-vs-3
>> Although Python is strongly typed, Python 2 permits strange comparisons: 
>> None 
>> < 3 < "2"
>>
>> On Sun, May 2, 2021 at 2:47 PM Ton vanN  wrote:
>>
>>> Reason for my speculation:
>>> at the HWA-forum several people already using WeeWx for years with the 
>>> original HWA-template, *probably* started & still operating with 
>>> Python2.x, and never heard complaints about the template.
>>>
>>> That triggers another aspect: 
>>> when issuing for the HWA-Forum this updated version of the template, 
>>> some advice must be given that (backwards) application with Python2.x must 
>>> be checked.
>>> Best to give this template-version and also the older version a related, 
>>> distinguishing name.
>>>
>>> Op zondag 2 mei 2021 om 23:33:32 UTC+2 schreef Ton vanN:
>>>
 Peter, that was the hint required!
 The HWA-template now has become active.

 Speculation, but could this be an aspect of changing from Python2.x to 
 Python3.x?


 Op zondag 2 mei 2021 om 23:06:42 UTC+2 schreef peterq...@gmail.com:

> Looks like that could be it. The .formatted is turning the barometer 
> value into a string and comparing it against zero, which is an int. Might 
> try 
>
> $trend.barometer.raw > 0
>
> I would have thought that Python would have cast the string into an 
> int for you, but apparently not. 
>
> On Sun, May 2, 2021 at 1:45 PM Ton vanN  wrote:
>
>> The error report for the HWA-template is like
>>  
>>May  2 22:20:46 Raspberry8 weewx[2139] ERROR 
>> weewx.cheetahgenerator:  Ignoring template 
>> /home/weewx/skins/Standard/openweerdata.htm.tmpl
>> May  2 22:20:46 Raspberry8 weewx[2139] ERROR 
>> weewx.cheetahgenerator:  Reason: '>' not supported between instances 

[weewx-user] Re: Belchertown hays chart

[Arend]

This is also caused by Toms changes to xtypes.py get_series() in 4.5.1 as 
mentioned here:

https://groups.google.com/g/weewx-user/c/UWSnqt7tY3Q/m/qBjJF22-FAAJ
Op dinsdag 4 mei 2021 om 02:53:42 UTC+2 schreef michael:

> Hi all,
>
> Wondering if anyone has seen this issue before. My hays chart shows the 
> hours til now with time_length = today, so for the full 24 hours the graph 
> is a complete circle of data, and the axis values increase as more time 
> passes, but I want a constant axis with 24 hours and only fill information 
> as it is received.
>
> My configuration is as follows
>
> [[chart3]]
> title = Wind Speed
> time_length = today
> [[[haysChart]]]
> color = "#ff4500"
> yAxis_softMax = 25
>
> I know a lot of people have it working, but something has gone awry for 
> me. Any hints on things to try?
>
> WeeWX version: 4.5.1
> Belchertown Skin Version: 1.3b1
>

-- 
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/c733c1ce-b193-447e-82f6-8904fb73a565n%40googlegroups.com.

Re: [weewx-user] Re: Full day highcharts question

[James Taylor]

Thanks.

What I'm trying to work out is if this is expected / correct behavior of 
weewx now.   Reading Gary's comment back in June 2020 sort of makes sense, 
but I'm still not 100% sure.

James

On Monday, May 3, 2021 at 7:19:03 PM UTC+1 Arend wrote:

> This new behaviour is caused by this WeeWX 4.5.1 commit:
>
>
> https://github.com/weewx/weewx/commit/a6098878562e4a35345051c45ee6aadf31edbdce
>
> for stamp in weeutil.weeutil.intervalgen(startstamp, 
> stopstamp, aggregate_interval):
> # Get the aggregate as a ValueTuple
> agg_vt = get_aggregate(obs_type, stamp, do_aggregate, 
> db_manager)
> *if agg_vt[0] is None:*
> *continue*
> if unit:
> # It's OK if the unit is unknown (=None).
> if agg_vt[1] is not None and (unit != agg_vt[1] or 
> unit_group != agg_vt[2]):
>
> Comment out the text marked as bold in xtypes.py to restore previous 
> behaviour or wait for Pat (or someone else) to create a fix for Belchertown 
> skin.
> Op maandag 3 mei 2021 om 19:48:20 UTC+2 schreef James Taylor:
>
>> Not sure.   Under weewx 4.4.0 my Temperature chart were as follows under 
>> Belchertown
>> [image: IMG_2780.png]
>>
>> Under weewx 4.5.1 it was displaying as the following
>>
>> [image: IMG_2781.png]
>>
>> I made no changes other than upgrade to 4.5.1.
>>
>> # Global Chart Defaults
>> # These are fallback options that charts will use if an option is not 
>> defined.
>> aggregate_type = None
>> time_length = 9 # Last 25 hours
>> type = line
>> colors = "#7cb5ec, #b2df8a, #f7a35c, #8c6bb1, #dd3497, #e4d354, #268bd2, 
>> #f45b5b, #6a3d9a, #33a02c"
>> tooltip_date_format = "LLL"
>>
>> [day]
>> # Chart Timespan Defaults
>> title = "Today since Midnight"
>> show_button = true
>> button_text = "Day"
>> time_length = today
>> tooltip_date_format = "LLL"
>>
>> aggregate_type = max
>> aggregate_interval = 300
>> gapsize = 30 # This should be your archive_interval from 
>> weewx.conf multiplied by 1000 to get milliseconds. Standard is 5 minutes
>>
>> [[chart1]]
>> title = Temperature
>> start_at_midnight = true
>> [[[outTemp]]]
>> zIndex = 1
>> name = Temperature
>> [[[windchill]]]
>> [[[heatindex]]]
>> color = "#f7a35c"
>> [[[dewpoint]]]
>> color = purple
>>
>> Obviously 4.4.0 came out this year so I'm wondering if something has been 
>> changed in Tom's code.
>>
>> James
>>
>> On Friday, April 9, 2021 at 7:08:29 AM UTC+1 grua...@gmail.com wrote:
>>
>>> should this still work with weewx 4.5.1 ?
>>>
>>> i updated and my full day charts are gone
>>>
>>> Manfred Maier schrieb am Montag, 15. Juni 2020 um 11:12:27 UTC+2:
>>>
 Thanks, Gary, for this comprehensive explanation.

 Based on what you wrote I was now able to plot an entire day.

 [image: Bildschirmfoto 2020-06-15 um 11.07.53.png]

 The trick is quite simple: I just had to define an aggregation for the 
 daily charts. I.e. adding the following two lines to the graphs.conf:

 aggregate_type = max

 aggregate_interval = 300





-- 
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/e1cb79c1-15f1-460a-b2eb-31056bef7bb7n%40googlegroups.com.