[weewx-user] Re: Time format for Sunrise/Sunset

[gjr80]

Good that you got the outcome you wanted. 

Just to wrap up, your changes to the ‘hour’ time format will have no effect on 
the Seasons main page. I mentioned in my previous post that the format applied 
is context dependent. By this I mean that the default format applied depends on 
the WeeWX tag being used. ‘current’ is applied to $current and $trend tags; 
‘day’ is the most common and is applied to $hour, $day and $span tags; ‘week’ 
is applied to $week tags; ‘month’ is applied to $month tags and ‘year’ is 
applied to $year and $rainyear tags. ‘hour’ is only applied when iterating over 
the hours in a $day tag (eg, ‘hour’ is applied to the $hours tag in for $hours 
in $day). There are a few other special cases I won’t go into.

Bottom line is to change the current date-time and sunrise/sunset time formats 
on the Seasons home page you need to modify the  ‘current’ and ‘ephem_day’ 
format setting respectively.

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/4373d47b-f6bb-4b99-bd41-7efa83fd7de4o%40googlegroups.com.

Re: [weewx-user] Re: Skin Belchertown 1.1

[Didier Decoodt]

Hi Patrick

my station : https://meteo-auffargis.decoodt.eu

How do you do for earthquake info with USGS Api?
Is it possible to have information for France only?

Bonne soirée
Didier

Le jeu. 9 juil. 2020 à 22:52, salinois  a écrit :

> hello Didier;
>
> you can see my weather station
>
> http://jurassikpat.ddns.net/weewx/belchertown
>
> bonne soirée
>
> Patrick
> Le 09/07/2020 à 12:48, Didier Decoodt a écrit :
>
> See below the modified presentation of records and the corresponding file
> records/index.html.tmpl
> [image: image.png]
>
> Bonne journée
>
> Le dim. 5 juil. 2020 à 15:43, Patrick Tranchant  a
> écrit :
>
>> hello Didier,
>>  I done as you say; it works well
>> thanks
>>
>> bon Dimanche
>>
>> Patrick
>>
>> On Sunday, July 5, 2020 at 2:06:56 PM UTC+2, Patrick Tranchant wrote:
>>>
>>> Hello PAT,
>>>
>>> I just upgraded Weewx to 4.1.1 with Belchertown 1.1 ( already in use
>>> with weewx 3.9.2 )
>>> I want to know to modify the display in "RECORDS",
>>> modify : Barometer Records
>>> remove : Sun Records ( I don't have Sun Probe.
>>>
>>> thanks
>>>
>>> Patrick
>>>
>>> see my files
>>>
>>> --
>> 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/8fdb06b5-6d97-482f-8b20-6c8c82d41793o%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/CAAvt3%3DQ5vPPh2Tn5%3D%3DiVQJvTngJqAanH6bLGPLgoAa9mmrF%3DOg%40mail.gmail.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/7c82495d-dcc9-78de-4ae6-7b97c3fe0db5%40gmail.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/CAAvt3%3DS8EwO_D-1ev7KntA12L2SZZHqBnRjBf6VZBDon2hXckA%40mail.gmail.com.

Re: [weewx-user] Re: Skin Belchertown 1.1

[salinois]

hello Didier;

you can see my weather station

http://jurassikpat.ddns.net/weewx/belchertown

bonne soirée

Patrick

Le 09/07/2020 à 12:48, Didier Decoodt a écrit :
See below the modified presentation of records and the corresponding 
file records/index.html.tmpl

image.png

Bonne journée

Le dim. 5 juil. 2020 à 15:43, Patrick Tranchant > a écrit :


hello Didier,
 I done as you say; it works well
thanks

bon Dimanche

Patrick

On Sunday, July 5, 2020 at 2:06:56 PM UTC+2, Patrick Tranchant wrote:

Hello PAT,

I just upgraded Weewx to 4.1.1 with Belchertown 1.1 ( already
in use with weewx 3.9.2 )
I want to know to modify the display in "RECORDS",
modify : Barometer Records
remove : Sun Records ( I don't have Sun Probe.

thanks

Patrick

see my files

-- 
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/8fdb06b5-6d97-482f-8b20-6c8c82d41793o%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/CAAvt3%3DQ5vPPh2Tn5%3D%3DiVQJvTngJqAanH6bLGPLgoAa9mmrF%3DOg%40mail.gmail.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/7c82495d-dcc9-78de-4ae6-7b97c3fe0db5%40gmail.com.

[weewx-user] Temp images

[J Jones]

I'm probably missing it in the config document. How do you edit to not show 
temp graphs? I would like to remove inside temp and inside humidity. I just 
upgraded to 4.1.1 and inside humidity got added and is not working anyways.


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/85c6a9e1-9a2f-42b4-a59c-d042ea3f94b4o%40googlegroups.com.

[weewx-user] Re: Time format for Sunrise/Sunset

[K1IW]

You are correct about Seasons and Locale.

The one that was in 12 hour had a US locale.  The one that was in 24 hour 
had a GB locale.
When I fixed the locale of the latter, it went to 12-hour.

Note though:  When I changed  "hour ="  to "%I:%M %p", it had no effect.  I 
had to change the locale to get it to work the way I wanted.


Thanks,
Bob


On Wednesday, July 8, 2020 at 10:59:16 PM UTC-4, gjr80 wrote:
>
> Hi,
>
> You haven't said which skin your are using, but since Seasons is the 
> default skin for a new/clean 4.1.1 install I will assume you are using 
> Seasons.
>
> If you have a look in weewx.conf under [StdReport] [[Defaults]] 
> [[[Units]]] you should find a TimeFormats stanza as follows:
>
> # The following section sets the format for each time scale. 
> # The values below will work in every locale, but they may 
> not look 
> # particularly attractive. 
> TimeFormats 
>
> hour = %H:%M 
> day = %X 
> week = %X (%A) 
> month = %x %X 
>
> year = %x %X
> rainyear = %x %X 
>
> current = %x %X 
> ephem_day = %X
> ephem_year = %x %X
>
>
> This stanza defines the default date-time formats used by tags in various 
> contexts. Unless they have been specifically changed the date-time in the 
> Seasons title bar will use the current format and the sunrise/sunset the 
> ephem_day format. The %x and %X formats depend on the system locale, so 
> systems set to a different locale may in fact show different formats for 
> the same date-time data (this was done not to necessarily be correct for 
> all users but to at least give all users readable/sensible output). That 
> being said on a given system under a default install the time component of 
> the current time and sunrise/sunset time should be in the same format (%X) 
> as should the format of the date component of the current time and 
> sunrise/sunset time (%x). were you by chance looking at your system in 
> the morning where the current time would be before midday and the sunset 
> time after midday, this could give the appearance of the current time being 
> in 12 hour format whilst sunrise/sunset is in 24 hour format.
>
> You can of course change the defaults which is quite acceptable and 
> encouraged (these changes will survive a WeeWX upgrade). You can also force 
> the formats used for each tag by specifying the date-time format to be used 
> in the individual tags in the template concerned, again this should be safe 
> across upgrades.
>
> Gary
>
>
> On Thursday, 9 July 2020 11:55:06 UTC+10, K1IW wrote:
>>
>> I've installed weewx at two different locations.  For the HTML page, on 
>> the first, both the current time and sunrise/sunset are displayed in 
>> 12-hour time.
>> On the second, current time is in 12-hour, but sunrise/sunset are in 
>> 24-hour.
>>
>> I'd like them to both be 12-hour.   I looked at the one that already 
>> shows in 12-hour and can't find the string "%I:" in any of the
>> configuration files.  I've also diff'd the config files between the 
>> servers and can't find any differences that can explain this.
>> Granted, there are a LOT of files, so maybe I missed one.
>>
>> What controls the time format of sunrise/sunset?
>>
>> Both are weewx 4.1.1
>>
>>
>> Thanks,
>> Bob
>>
>>

-- 
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/99ec4b1c-e16f-469a-8401-6892588d12f8o%40googlegroups.com.

[weewx-user] Re: Weewx tag to show last time it rained

[didier....@gmail.com]

Hi
I have installed the extension and modify the conf file, but I have not the 
file index-hook-after-station-info.inc, and I don't know how to write it. 
Is it possible to have a copy of this file with the 2 parameters last_rain 
and time_since_last_rain?

Many thanks
Didier
Le lundi 8 juin 2020 à 08:57:14 UTC+2, hoev...@gmail.com a écrit :

> Well, speaking for me, I would like to show this information (last time it 
> rained) using a tag, and put it in index_hook_after_station_info.inc The 
> tag is $time_since_last_rain.
>
> Having done that (putting the tag in that inc-file), it throws an error 
> NameMapper.NotFound while the generator is doing its thing. Looking at the 
> html the skin lastrain produces, it shows the correct last datetime it 
> rained. I guess (in my own words) it's the case that calculated variables 
> in one skin can not be used in another skin? Is this true?
>
> Jun  8 08:53:18 weewx weewx[99172] INFO weewx.cheetahgenerator: Generated 
> 8 files for report SeasonsReport in 1.24 seconds
> Jun  8 08:53:19 weewx weewx[99172] INFO weewx.imagegenerator: Generated 15 
> images for report SeasonsReport in 0.41 seconds
> Jun  8 08:53:19 weewx weewx[99172] INFO weewx.reportengine: Copied 5 files 
> to /var/www/html/weewx
> Jun  8 08:53:19 weewx weewx[99172] INFO weewx.restx: MQTT: Published 
> record 2020-06-08 08:53:19 CEST (1591599199)
> Jun  8 08:53:19 weewx weewx[99172] message repeated 2 times: [ INFO 
> weewx.restx: MQTT: Published record 2020-06-08 08:53:19 CEST (1591599199)]
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator: Generate 
> failed with exception ''
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator:  
> Ignoring template /etc/weewx/skins/Belchertown/index.html.tmpl
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator:  
> Reason: cannot find 'time_since_last_rain'
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator:   
> Traceback (most recent call last):
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator: 
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator:   
> unicode_string = compiled_template.respond()
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator: 
> File "_etc_weewx_skins_Belchertown_index_html_tmpl.py", line 1261, in 
> respond
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator: 
> File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 1708, in 
> _handleCheetahInclude
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator:   
> self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator: 
> File 
> "cheetah__etc_weewx_skins_Belchertown_index_hook_after_station_info_inc_1591599200_376662_26334.py",
>  
> line 90, in respond
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator:   
> NameMapper.NotFound: cannot find 'time_since_last_rain'
> Jun  8 08:53:20 weewx weewx[99172] INFO weewx.restx: MQTT: Published 
> record 2020-06-08 08:53:21 CEST (1591599201)
> Jun  8 08:53:21 weewx weewx[99172] INFO weewx.cheetahgenerator: Generated 
> 10 files for report Belchertown in 1.86 seconds
>
>
> Op woensdag 3 juni 2020 14:11:27 UTC+2 schreef Pat:
>
>> Where on the skin would you display this info? Just curious
>>
>> On Wednesday, June 3, 2020 at 6:59:13 AM UTC-4, NanoG5Kite wrote:
>>>
>>> Got this installed and working too - many thanks for the hint.
>>>
>>>
>>> As Weewx beginner - is there any way to get the two Last Rain Values 
>>> displayed in the Belchertown Homeskin?
>>>
>>> last rain N/A 
>>> time since last rain: N/A 
>>>
>>> Thanks,
>>>
>>> Matthias
>>>
>>> Am Mittwoch, 3. Juni 2020 12:38:05 UTC+2 schrieb Remy Lavabre:

 Yes !
 And it is working perfectly !
>>>
>>>

-- 
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/297fb48e-857d-43ca-843e-b7a6c5f17377n%40googlegroups.com.

Re: [weewx-user] /etc/init.d/weewx not stopping weewx

[Graham Eddy]

fixed! for non-root user running weewx.
i recommend this be updated in util/init.d/weewx.debian (after someone tests it 
for root user…)

start-stop-damon(8) clearly says
-p, --pidfile pid-file
  ...
  Warning:  using  this match option with a world-writable pidfile
  or using it alone with a daemon that writes the  pidfile  as  an
  unprivileged  (non-root)  user  will  be  refused  with an error
  (since version 1.19.3) ...
‘using it alone’ → so i just added another daemon-identifying matching option 
readily to hand, the username

the ‘stop’ request in weewx script becomes
start-stop-daemon --stop --pidfile $WEEWX_PID --user $(echo $WEEWX_USER | sed 
's/:.*$//')
and it works like a charm!

> On 9 Jul 2020, at 3:19 pm, Graham Eddy  wrote:
> 
>  * ’sudo /etc/init.d/weewx stop’ and ’sudo /systemctl stop weewx’ fail to 
> stop weewx; weewx process running happily but systemctl reports it in failed 
> state
> 

-- 
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/3BB9C647-6A39-4E0F-9CE4-6C91A2FD1737%40gmail.com.

[weewx-user] Re: Errors during APT-GET UPDATE

[J Jones]

Now to figure out how to turn off the graphs that don't populate.



On Thursday, July 9, 2020 at 9:53:17 AM UTC-5, J Jones wrote:
>
> I'm getting the following errors during APT-GET UPDATE
> I'm not familiar with this. Can anyone help? Step by step please.
>
>
> E: Repository 'http://weewx.com/apt squeeze InRelease' changed its 
> 'Origin' value from '. squeeze' to 'python2 squeeze'
> E: Repository 'http://weewx.com/apt squeeze InRelease' changed its 
> 'Label' value from '. squeeze' to 'python2 squeeze'
> N: This must be accepted explicitly before updates for this repository can 
> be applied. See apt-secure(8) manpage for details.
>
>

-- 
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/bc75d495-0990-4d44-970a-3c6ec58a10eeo%40googlegroups.com.

[weewx-user] Re: Errors during APT-GET UPDATE

[J Jones]

I think I got it. Apparently I'm using Debian 9. Thanks for the help.




On Thursday, July 9, 2020 at 9:53:17 AM UTC-5, J Jones wrote:
>
> I'm getting the following errors during APT-GET UPDATE
> I'm not familiar with this. Can anyone help? Step by step please.
>
>
> E: Repository 'http://weewx.com/apt squeeze InRelease' changed its 
> 'Origin' value from '. squeeze' to 'python2 squeeze'
> E: Repository 'http://weewx.com/apt squeeze InRelease' changed its 
> 'Label' value from '. squeeze' to 'python2 squeeze'
> N: This must be accepted explicitly before updates for this repository can 
> be applied. See apt-secure(8) manpage for details.
>
>

-- 
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/0b8fdcb5-d0d6-4065-ba64-5f3635df13fao%40googlegroups.com.

Re: [weewx-user] Re: Errors during APT-GET UPDATE

[Tom Keffer]

What operating system are you using? You can tell by using the command
(look at the line "PRETTY_NAME"):

*cat /etc/os-release*

Assuming you are running buster (Debian 10), try building the sources list
again. then do an update, then upgrade


*wget -qO - http://weewx.com/apt/weewx-python3.list
 | sudo tee
/etc/apt/sources.list.d/weewx.list*
*sudo apt update*
*sudo apt upgrade*

-tk

On Thu, Jul 9, 2020 at 8:14 AM J Jones  wrote:

> Now I get the following. I tried sudo apt upgrade and it didn't upgrade
> weewx
>
> weewx/buster 4.1.1-1 all [upgradable from: 3.9.2-1]
> N: There are 3 additional versions. Please use the '-a' switch to see them.
>
>
>
> On Thursday, July 9, 2020 at 9:53:17 AM UTC-5, J Jones wrote:
>>
>> I'm getting the following errors during APT-GET UPDATE
>> I'm not familiar with this. Can anyone help? Step by step please.
>>
>>
>> E: Repository 'http://weewx.com/apt squeeze InRelease' changed its
>> 'Origin' value from '. squeeze' to 'python2 squeeze'
>> E: Repository 'http://weewx.com/apt squeeze InRelease' changed its
>> 'Label' value from '. squeeze' to 'python2 squeeze'
>> N: This must be accepted explicitly before updates for this repository
>> can be applied. See apt-secure(8) manpage for details.
>>
>> --
> 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/bd483f00-b1e5-49ed-96f5-6559079b8c67o%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/CAPq0zEC-YvHhSbygWCnzsa%2B_jbWLTa1httAT71293d_3cj7_HQ%40mail.gmail.com.

[weewx-user] Re: Errors during APT-GET UPDATE

[J Jones]

Now I get the following. I tried sudo apt upgrade and it didn't upgrade 
weewx

weewx/buster 4.1.1-1 all [upgradable from: 3.9.2-1]
N: There are 3 additional versions. Please use the '-a' switch to see them.



On Thursday, July 9, 2020 at 9:53:17 AM UTC-5, J Jones wrote:
>
> I'm getting the following errors during APT-GET UPDATE
> I'm not familiar with this. Can anyone help? Step by step please.
>
>
> E: Repository 'http://weewx.com/apt squeeze InRelease' changed its 
> 'Origin' value from '. squeeze' to 'python2 squeeze'
> E: Repository 'http://weewx.com/apt squeeze InRelease' changed its 
> 'Label' value from '. squeeze' to 'python2 squeeze'
> N: This must be accepted explicitly before updates for this repository can 
> be applied. See apt-secure(8) manpage for details.
>
>

-- 
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/bd483f00-b1e5-49ed-96f5-6559079b8c67o%40googlegroups.com.

Re: [weewx-user] Errors during APT-GET UPDATE

[Tom Keffer]

Try using apt instead lf apt-get

*sudo apt update*

-tk

On Thu, Jul 9, 2020 at 7:53 AM J Jones  wrote:

> I'm getting the following errors during APT-GET UPDATE
> I'm not familiar with this. Can anyone help? Step by step please.
>
>
> E: Repository 'http://weewx.com/apt squeeze InRelease' changed its
> 'Origin' value from '. squeeze' to 'python2 squeeze'
> E: Repository 'http://weewx.com/apt squeeze InRelease' changed its
> 'Label' value from '. squeeze' to 'python2 squeeze'
> N: This must be accepted explicitly before updates for this repository can
> be applied. See apt-secure(8) manpage for details.
>
> --
> 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/d0722409-4353-4f19-8ef3-7c029acbd168o%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/CAPq0zEAY4W5qpHmpykDj6r9PtLSXb367aoHxXE%3DWGe3n7PwMsA%40mail.gmail.com.

[weewx-user] Errors during APT-GET UPDATE

[J Jones]

I'm getting the following errors during APT-GET UPDATE
I'm not familiar with this. Can anyone help? Step by step please.


E: Repository 'http://weewx.com/apt squeeze InRelease' changed its 'Origin' 
value from '. squeeze' to 'python2 squeeze'
E: Repository 'http://weewx.com/apt squeeze InRelease' changed its 'Label' 
value from '. squeeze' to 'python2 squeeze'
N: This must be accepted explicitly before updates for this repository can 
be applied. See apt-secure(8) manpage for details.

-- 
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/d0722409-4353-4f19-8ef3-7c029acbd168o%40googlegroups.com.

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[John Kline]

>> On Jul 9, 2020, at 1:52 AM, geni08...@gmail.com  
>> wrote:
> Question for my understanding:
> If or why is the id = string supplemented with $current, $day or not at all?
> 

In the examples, no IDs is supplemented with current, day or none at all.  Some 
values say $current, which means the current observation.  Some say day, which 
would be for the day and have an aggregator ($day.rain.sum).  In any event, all 
of these values are overwritten every couple of seconds by the javascript.  As 
such, they could be removed.

As for the ids.  They could be anything you wish.  They just are used by the 
JavaScript to look up the element.  As a naming scheme for ids, I chose to to 
name them for the corresponding key in loop-data.txt.

For example, FMT_HI_windGust.  The JavaScript will get lookup the element with 
the id FMT_HI_windGust.  It will then lookup the value in loop-data.txt for the 
key FMT_HI_windGust and set the contents of the HTML tag (innerHTML property) 
to that value.

If the id was foo on this element, the JavaScript would have to find the foo 
element in the DOM.  Of course, it will still need to use the key 
FMT_HI_windGust for looking up the loop-data value.

As for the naming scheme in loop-data.txt:
FMT_HI_windGust
The FMT_ means include the label.
The HI_ means give me today’s high.

FMT_windGust would be for the current observation and would include the label.

windGust would be for the current observation. It would NOT include a label, 
but it would still be formatted.  That is, if wind should have 1 decimal place, 
it be formatted as such (e.g., 4.0).

The README has this info, but to summarize:

If the key is missing an aggregator (HI, LO, AVG, WAVG, SUM, RMS, VEC_AVG, 
VEC_DIR), it is the current observation.  If it has an aggregator prefix, it is 
for the day.  Exceptions are the items I made up 10mMaxGust (which is 10 
minutes) and barometerRate (which is a delta from 3 hours ago) and windRose.

FMT_ includes the label.

UNITS_ is the unit for the observation.

LABEL_ is the label for the observation.

COMPASS_ for windDIr and windGustDir gives compass (text) direction.

DESC_ for barometer rate gives a text description of the rate (and probably 
needs to be internationalized).

T_ is the time of the observation.  For example, T_HI_ would be the time 
today that the high was reached for the observation.

Just to mention the other things you pointed to:
FMT_SUM_rain is today’s rain with a label.  The FMT_ gives the label.  Since 
SUM_ is an aggregator, it is for today.

FMT_rainRate is the current rate of rain (since it is missing an aggregator) 
and it includes a label (FMT_).  FMT_HI_rainRate would be today’s high 
rainRate.  FMT_T_HI_rainRate would be the formatted time when today’s high rain 
rate happened.

Note that the packet time presented in WeatherBoard is not formatted.  It uses 
rainRate.  That time is then localized with toLocaleTimeString in JavaScript.  
In that way, the time presented is local time for the viewer of the web page.
> 
> 
> jo...@johnkline.com schrieb am Mittwoch, 8. Juli 2020 um 20:35:22 UTC+2:
>> 
>> 
 On Jul 8, 2020, at 1:36 AM, geni08...@gmail.com  
 wrote:
>>>  weewx-weatherboard 1.3a the label entries are implemented.
>> 
>>> 
>>> What is the easiest way now
>>> Indoor temperature
>>> barometer
>>> Indoor and outdoor humidity
>>> to show signs on the display?
>> 
>> 
>> To get these readings in loop-data.txt, add the following to the end of the 
>> fields line in the LoopData section of weewx.conf:
>> , FMT_inTemp, FMT_barometer, FMT_inHumidity, FMT_outHumidity
>> 
>> As for adding them to a skin, it would be helpful to know your end goal and 
>> your familiarity with the technologies.
>> 
>> WeatherBoard is designed for display on a tablet sitting on a bookshelf or 
>> hanging on a wall.  It’s meant to be viewed from across the room.  That’s 
>> why there’s a small amount of data in large fonts and why I chose the color 
>> scheme.
>> 
>> Are you trying to have something that looks like WeatherBoard but just these 
>> four extra items on it?  Will you want more after you add these four?  Extra 
>> items will mean smaller fonts.  How will this skin be viewed?  I’m assuming 
>> you are not looking for the across the room viewing that I targeted with 
>> this skin.
>> 
>> Are you looking to write an entirely new skin?
>> 
>> Are you looking to add “update on every loop” capabilities to another skin 
>> that you like?
>> 
>> How comfortable are you working with html, css and JavaScript?
>> 
>> Cheers,
>> John
>> 
>> 
>>> 
>>> jo...@johnkline.com schrieb am Dienstag, 7. Juli 2020 um 20:10:24 UTC+2:
 Most of the WeatherBoard will now use the strings in Defaults, so you 
 should see it in German after you install.  For the custom strings, just 
 update the strings in the WeatherBoard>Labels>Generic section of 
 weewx.conf.
 
>> On Jul 7, 2020, at 6:47 AM, John Kline  wrote:
> 
 
> I’ve created a 

Re: [weewx-user] Re: Skin Belchertown 1.1

[Didier Decoodt]

See below the modified presentation of records and the corresponding file
records/index.html.tmpl
[image: image.png]

Bonne journée

Le dim. 5 juil. 2020 à 15:43, Patrick Tranchant  a
écrit :

> hello Didier,
>  I done as you say; it works well
> thanks
>
> bon Dimanche
>
> Patrick
>
> On Sunday, July 5, 2020 at 2:06:56 PM UTC+2, Patrick Tranchant wrote:
>>
>> Hello PAT,
>>
>> I just upgraded Weewx to 4.1.1 with Belchertown 1.1 ( already in use with
>> weewx 3.9.2 )
>> I want to know to modify the display in "RECORDS",
>> modify : Barometer Records
>> remove : Sun Records ( I don't have Sun Probe.
>>
>> thanks
>>
>> Patrick
>>
>> see my files
>>
>> --
> 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/8fdb06b5-6d97-482f-8b20-6c8c82d41793o%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/CAAvt3%3DQ5vPPh2Tn5%3D%3DiVQJvTngJqAanH6bLGPLgoAa9mmrF%3DOg%40mail.gmail.com.


index.html.tmpl
Description: Binary data

Re: [weewx-user] Re: Belchertown Moonrise and Moonset time format

[Didier Decoodt]

Hi

I have the following parameters, and it's OK for me
   # moment.js default labels formats
time_earthquake = LLL
time_last_updated = "LL, LTS"
time_snapshot_records_today_header = ", LL"
time_snapshot_records_month_header =  
time_sunrise = LT
time_sunset = LT
time_forecast_alert_expires = LLL
time_forecast_date = ddd D/M
time_forecast_last_updated = LLL
time_records_page_full_date = LLL
time_records_page_month_day_year = LL
time_records_page_rainfall_range_begin =  DD
time_records_page_rainfall_range_end = LL
[image: image.png]

Le mer. 8 juil. 2020 à 21:40, HoracioDos  a écrit :

> Hello.
> You can try this in weewx.conf
> time_sunrise = LT
> time_sunset = LT
>
> On Wednesday, July 8, 2020 at 4:50:28 AM UTC-3 eric9...@gmail.com wrote:
>
>> [image: soleil]
>>
>> Le mercredi 8 juillet 2020 à 09:32:27 UTC+2, eric9...@gmail.com a écrit :
>>
>>> Hi,
>>>
>>> I managed to add the moonrise and Moonset times to the Sun & Moon
>>> module. But it appears in HH:MM:SS format.I would want HH:MM only like sun .
>>>
>>> How should I do. I don't find what to do.
>>>
>>> --
> 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/b2e053cc-3b0d-420a-96b7-52efdf19c0a0n%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/CAAvt3%3DS6eVazdku5NH_zou-TzVMshEXJfBqQ%2BW-phBb8x6g5gg%40mail.gmail.com.

Re: [weewx-user] StdWXCalculate: beaufort = prefer_hardware

[Vetti52]

The tags are derived from the listing of Paul VE1DX (@WindnFog), which he 
presented in the thread mentioned in my post above. I expanded it to treat 
with gust also, by evaluating $current.windGust.raw the same way and put it 
all together into skins/seasons/current.inc where it finally is displayed.

Am Mittwoch, 8. Juli 2020 21:56:28 UTC+2 schrieb Tom Keffer:
>
> I am not familiar with the tag $current_beaufort. Is that part of some 
> extension skin?
>
> Unfortunately, a wind gust in beaufort would not work that way. To do that 
> would require extending the unit system, to allow beaufort to be used as a 
> new unit type, which is not a bad idea. Unfortunately, it's a bit 
> problematic, because wind speed expressed in Beaufort no longer takes a 
> unit label (such as m/s), so would require some code changes to make sure 
> that didn't happen.
>
> I'll have to think about all this.
>
> -tk
>
>  

-- 
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/23ed023b-17ad-48d1-8556-23ea37645c91o%40googlegroups.com.

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[geni08...@gmail.com]

Question for my understanding:
If or why is the id = string supplemented with $current, $day or not at all?
[image: loop1.jpg]

jo...@johnkline.com schrieb am Mittwoch, 8. Juli 2020 um 20:35:22 UTC+2:

>
>
> On Jul 8, 2020, at 1:36 AM, geni08...@gmail.com  
> wrote:
>
>  weewx-weatherboard 1.3a the label entries are implemented.
>
>
> What is the easiest way now
> Indoor temperature
> barometer
> Indoor and outdoor humidity
> to show signs on the display?
>
>
>
> To get these readings in loop-data.txt, add the following to the end of 
> the fields line in the LoopData section of weewx.conf:
> , FMT_inTemp, FMT_barometer, FMT_inHumidity, FMT_outHumidity
>
> As for adding them to a skin, it would be helpful to know your end goal 
> and your familiarity with the technologies.
>
> WeatherBoard is designed for display on a tablet sitting on a bookshelf or 
> hanging on a wall.  It’s meant to be viewed from across the room.  That’s 
> why there’s a small amount of data in large fonts and why I chose the color 
> scheme.
>
> Are you trying to have something that looks like WeatherBoard but just 
> these four extra items on it?  Will you want more after you add these four? 
>  Extra items will mean smaller fonts.  How will this skin be viewed?  I’m 
> assuming you are not looking for the across the room viewing that I 
> targeted with this skin.
>
> Are you looking to write an entirely new skin?
>
> Are you looking to add “update on every loop” capabilities to another skin 
> that you like?
>
> How comfortable are you working with html, css and JavaScript?
>
> Cheers,
> John
>
>
> jo...@johnkline.com schrieb am Dienstag, 7. Juli 2020 um 20:10:24 UTC+2:
>
>> Most of the WeatherBoard will now use the strings in Defaults, so you 
>> should see it in German after you install.  For the custom strings, just 
>> update the strings in the WeatherBoard>Labels>Generic section of weewx.conf.
>>
>> On Jul 7, 2020, at 6:47 AM, John Kline  wrote:
>>
>> 
>>
>> I’ve created a branch of WeatherBoard that substitutes appTemp for 
>> dewpoint.
>>
>> It is here:
>> https://github.com/chaunceygardiner/weewx-weatherboard/tree/appTemp
>>
>> On Jul 7, 2020, at 12:09 AM, John Kline  wrote:
>>
>> 
>> There was a subtle difference in how I was creating the next day 
>> accumulator vs. how WeeWX proper is doing it.  I’ve changed that.  Please 
>> install 1.3.15 and let me know how it goes at midnight.
>>
>> On Jul 6, 2020, at 10:44 PM, geni08...@gmail.com  
>> wrote:
>>
>> Jul  7 00:00:01 Wetter-Raspi rsyslogd:  [origin software="rsyslogd" 
>> swVersion="8.1901.0" x-pid="295" x-info="https://www.rsyslog.com;] 
>> rsyslogd was HUPed
>> Jul  7 00:00:01 Wetter-Raspi systemd[1]: logrotate.service: Succeeded.
>> Jul  7 00:00:01 Wetter-Raspi systemd[1]: Started Rotate log files.
>> Jul  7 00:00:02 Wetter-Raspi systemd[1]: man-db.service: Succeeded.
>> Jul  7 00:00:02 Wetter-Raspi systemd[1]: Started Daily man-db 
>> regeneration.
>> Jul  7 00:00:15 Wetter-Raspi weewx[18476] INFO weewx.manager: Added 
>> record 2020-07-07 00:00:00 CEST (1594072800) to database 'weewx'
>> Jul  7 00:00:15 Wetter-Raspi weewx[18476] INFO weewx.manager: Added 
>> record 2020-07-07 00:00:00 CEST (1594072800) to daily summary in 'weewx'
>>
>>
>> geni08...@gmail.com schrieb am Dienstag, 7. Juli 2020 um 07:39:52 UTC+2:
>>
>>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>>   Traceback (most recent call last):
>>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>> File "/usr/share/weewx/user/loopdata.py", line 365, in process_queue
>>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>>   self.day_accum.addRecord(pkt)
>>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>> File "/usr/share/weewx/weewx/accum.py", line 423, in addRecord
>>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>>   % (record['dateTime'], self.timespan))
>>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>>   weewx.accum.OutOfSpan: Attempt to add out-of-interval record 
>>> (1594072801) to timespan ([2020-07-06 00:00:00 CEST (1593986400) -> 
>>> 2020-07-07 00:00:00 CEST (1594072800)])
>>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>>   
>>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>>   During handling of the above exception, another exception occurred:
>>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>>   
>>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>>   Traceback (most recent call last):
>>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>> File "/usr/share/weewx/user/loopdata.py", line 370, in process_queue
>>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>>   self.day_accum.addRecord(pkt)
>>> Jul  7 

[weewx-user] [Belchertown] Daily/Monthly Snapshots Not Working

[Andre]

After I tried to correct a too high rainRate value, the daily and monthly 
snapshot is no longer updated. You could see it here 
www.wetter-norderstedt.de.
My HighCharts seems to be working fine. Maybe there is a connection to this 
forum post 

@Pat: If you are reading this, maybe you have an idea to solve the 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/c8838444-6c81-4220-9a22-42265384565do%40googlegroups.com.