Re: [weewx-user] weewx airlink update

[Meteo Oberwallis]

 
<https://translate.google.com/about/?hl=de>
<https://policies.google.com/?hl=de> 
<https://support.google.com/translate/?hl=de> 
<https://www.google.com/about?hl=de>
Hello Doug
I have a question. It's now been 2 years since my last post. My search 
didn't turn up much worth knowing either. That's why I wanted to ask again 
whether anything has happened in these 2 years regarding the reading of the 
fine dust sensor. The aim would therefore be to write the measured values 
into a separate database. The goal would be to discharge every minute. I 
want to save the weather data, i.e. not reduce the interval to 10 minutes, 
as this has no meaning for this data. 
Greeting

<https://translate.google.com/saved>
<https://translate.google.com/contribute>
Übersetzungsergebnisse verfügbar 
Doug Jenkins schrieb am Sonntag, 14. August 2022 um 13:26:01 UTC+2:

> No problem. I reviewed the airlink proxy code and it is a bit of effort to 
> get setup and configured. I personally do not use the proxy as I am just 
> polling the sensor every 5 minutes.
>
> What I would do for now is just setup the weewx airlink driver with your 
> station and set the archive interval to 60 seconds and see how that goes.
>
> DDJ
>
>
>
> On Sat, Aug 13, 2022 at 9:53 AM  wrote:
>
>> Hello Doug.
>>
>>  
>>
>> Thx for the Help. I've tried to somehow get that with the proxy. But 
>> unfortunately without success. Since I'm not a professional in such things, 
>> for me it's mostly stationery what's written there. Is there a more 
>> detailed guide on how to install this proxy? How can I start it 
>> afterwards and check whether it is running?
>>
>> Excuse my "dummy" question ;-)
>>
>>  
>>
>> Greeting
>>
>>  
>>
>> *Von:* weewx...@googlegroups.com  *Im Auftrag 
>> von *Doug Jenkins
>> *Gesendet:* Freitag, 12. August 2022 20:17
>> *An:* weewx...@googlegroups.com
>> *Betreff:* Re: [weewx-user] weewx airlink update
>>
>>  
>>
>> You can by setting your archive interval to 60 seconds in the weewx conf 
>> file here
>>
>>  
>>
>> [StdArchive]
>>
>> 
>>
>> # If the station hardware supports data logging then the archive 
>> interval
>>
>> # will be downloaded from the station. Otherwise, specify it (in 
>> seconds).
>>
>> archive_interval = 300
>>
>>  
>>
>> Now with the Airlink driver, you may get a timeout from the API if you 
>> poll it all the time. John Kline has another repo that creates a proxy 
>> service for the airlink driver. that repo is here : 
>> chaunceygardiner/airlink-proxy: 
>> Proxy server for Davis AirLink air quality sensor. (github.com) 
>> <https://github.com/chaunceygardiner/airlink-proxy>
>>
>>  
>>
>> DDJ
>>
>>  
>>
>> On Fri, Aug 12, 2022 at 2:10 PM Meteo Oberwallis  
>> wrote:
>>
>> Hello everyone.
>>
>> I use the interval of 10 minutes at Weewx. Now, of course, the fine dust 
>> pollution is only measured at ten-minute intervals. Is there any way to set 
>> this interval to every minute? Then it would also be possible to save the 
>> particulate matter values ​​in a separate SQLite database? Has that 
>> possibly already run someone of you?
>>
>> It`s the original Davis Air Quality Sensor.
>>
>>  
>>
>> I have this -> https://github.com/chaunceygardiner/weewx-airlink
>>
>>  
>>
>> Thank for our Help`s
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/9d580716-93d3-41d4-87c5-54d345e583e8n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/9d580716-93d3-41d4-87c5-54d345e583e8n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> -- 
>> 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/L351f8T97jg/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user

Re: [weewx-user] weewx airlink update

[Meteo Oberwallis]

Hello Doug
I have a question. It's now been 2 years since my last post. My search 
didn't turn up much worth knowing either. That's why I wanted to ask again 
whether anything has happened in these 2 years regarding the reading of the 
fine dust sensor. The aim would therefore be to write the measured values 
into a separate database. The goal would be to discharge every minute. 
Greeting
Doug Jenkins schrieb am Sonntag, 14. August 2022 um 13:26:01 UTC+2:

> No problem. I reviewed the airlink proxy code and it is a bit of effort to 
> get setup and configured. I personally do not use the proxy as I am just 
> polling the sensor every 5 minutes.
>
> What I would do for now is just setup the weewx airlink driver with your 
> station and set the archive interval to 60 seconds and see how that goes.
>
> DDJ
>
>
>
> On Sat, Aug 13, 2022 at 9:53 AM  wrote:
>
>> Hello Doug.
>>
>>  
>>
>> Thx for the Help. I've tried to somehow get that with the proxy. But 
>> unfortunately without success. Since I'm not a professional in such things, 
>> for me it's mostly stationery what's written there. Is there a more 
>> detailed guide on how to install this proxy? How can I start it 
>> afterwards and check whether it is running?
>>
>> Excuse my "dummy" question ;-)
>>
>>  
>>
>> Greeting
>>
>>  
>>
>> *Von:* weewx...@googlegroups.com  *Im Auftrag 
>> von *Doug Jenkins
>> *Gesendet:* Freitag, 12. August 2022 20:17
>> *An:* weewx...@googlegroups.com
>> *Betreff:* Re: [weewx-user] weewx airlink update
>>
>>  
>>
>> You can by setting your archive interval to 60 seconds in the weewx conf 
>> file here
>>
>>  
>>
>> [StdArchive]
>>
>> 
>>
>> # If the station hardware supports data logging then the archive 
>> interval
>>
>> # will be downloaded from the station. Otherwise, specify it (in 
>> seconds).
>>
>> archive_interval = 300
>>
>>  
>>
>> Now with the Airlink driver, you may get a timeout from the API if you 
>> poll it all the time. John Kline has another repo that creates a proxy 
>> service for the airlink driver. that repo is here : 
>> chaunceygardiner/airlink-proxy: 
>> Proxy server for Davis AirLink air quality sensor. (github.com) 
>> <https://github.com/chaunceygardiner/airlink-proxy>
>>
>>  
>>
>> DDJ
>>
>>  
>>
>> On Fri, Aug 12, 2022 at 2:10 PM Meteo Oberwallis  
>> wrote:
>>
>> Hello everyone.
>>
>> I use the interval of 10 minutes at Weewx. Now, of course, the fine dust 
>> pollution is only measured at ten-minute intervals. Is there any way to set 
>> this interval to every minute? Then it would also be possible to save the 
>> particulate matter values ​​in a separate SQLite database? Has that 
>> possibly already run someone of you?
>>
>> It`s the original Davis Air Quality Sensor.
>>
>>  
>>
>> I have this -> https://github.com/chaunceygardiner/weewx-airlink
>>
>>  
>>
>> Thank for our Help`s
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/9d580716-93d3-41d4-87c5-54d345e583e8n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/9d580716-93d3-41d4-87c5-54d345e583e8n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> -- 
>> 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/L351f8T97jg/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/CACC0i0wqNWKiiuHy13-0pSf-4O3CRWYXBDLtbhK3HDWZFcuhLw%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/CACC0i0wqNWKiiuHy13-0pSf-4O3CRWYXBDLtbhK3HDWZFcuhLw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>> -- 
>> 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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/000e01d8af1c%241efe0a60%245cfa1f20%24%40bluewin.ch
>>  
>> <https://groups.google.com/d/msgid/weewx-user/000e01d8af1c%241efe0a60%245cfa1f20%24%40bluewin.ch?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/07c6a8a4-1bde-4f97-86f5-8e23ec4348f3n%40googlegroups.com.

Re: [weewx-user] Display the first date entry in the database

[Meteo Oberwallis]

This works

$alltime.outTemp.firsttime 

This is the Result: 01.02.2017 00:01:00 

@steepleian: Thanks 
Tom Keffer schrieb am Freitag, 16. Februar 2024 um 16:12:14 UTC+1:

> On Fri, Feb 16, 2024 at 6:37 AM Meteo Oberwallis  
> wrote:
>
>> Hello.
>> Thank you for the answers. The $alltime.outTemp.firsttime.raw works. Now 
>> I have to format the whole thing so that I can get it into a “normal date”. 
>> Can anyone else give me help?
>>
>
>
> *$alltime.dateTime.mintime*
>
>
>
>

-- 
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/1de93286-6d9d-4ff7-b507-c5e144ad3170n%40googlegroups.com.

Re: [weewx-user] Display the first date entry in the database

[Meteo Oberwallis]

Hello Tom.

It`s not working

Feb 16 16:14:28 wetterstation wee_reports[11564] ERROR 
weewx.cheetahgenerator:  Ignoring template 
/etc/weewx/skins/Belchertown/about/index.html.tmpl
Feb 16 16:14:28 wetterstation wee_reports[11564] ERROR 
weewx.cheetahgenerator:  Reason: cannot find 'mintime' while searching 
for 'alltime.dateTime.mintime  e'
Feb 16 16:14:28 wetterstation wee_reports[11564] ERROR 
weewx.cheetahgenerator:  To debug, try inserting '#errorCatcher Echo' 
at top of template
Feb 16 16:14:32 wetterstation wee_reports[11564] INFO 
weewx.cheetahgenerator: Generated 11 files for report Belchertown in 13.56 
seconds
Feb 16 16:14:32 wetterstation wee_reports[11564] INFO weewx.reportengine: 
Copied 39 files to /var/www/html/weewx/user


Tom Keffer schrieb am Freitag, 16. Februar 2024 um 16:12:14 UTC+1:

> On Fri, Feb 16, 2024 at 6:37 AM Meteo Oberwallis  
> wrote:
>
>> Hello.
>> Thank you for the answers. The $alltime.outTemp.firsttime.raw works. Now 
>> I have to format the whole thing so that I can get it into a “normal date”. 
>> Can anyone else give me help?
>>
>
>
> *$alltime.dateTime.mintime*
>
>
>
>

-- 
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/930e7c83-39cd-4e8c-aa5d-07090aad8aedn%40googlegroups.com.

Re: [weewx-user] Display the first date entry in the database

[Meteo Oberwallis]

Hello.
Thank you for the answers. The $alltime.outTemp.firsttime.raw works. Now I 
have to format the whole thing so that I can get it into a “normal date”. 
Can anyone else give me help?

steepleian schrieb am Freitag, 16. Februar 2024 um 15:30:43 UTC+1:

> This is what I use which works: -
>
> $alltime.outTemp.firsttime.raw";
>
> Ian
>
> https://claydonsweather.org.uk
>
> On 16 Feb 2024, at 13:43, Tom Keffer  wrote:
>
> 
>
> I haven't tried it, but I don't see why the following wouldn't work:
>
> *$alltime.dateTime.min*
>
> -tk
>
> On Fri, Feb 16, 2024 at 4:59 AM Meteo Oberwallis  
> wrote:
>
>> Hello everyone
>> I would like to display the date of the first entry in the weexs.sdb in 
>> Belchertownskin. The reason for this is that you can see how long the 
>> weather station has been in operation. Since I operate several stations, 
>> this would make my work extremely easier. This could say something like 
>> "Operating since: 10/2023" or something like that. Can someone help me with 
>> that?
>> Thank you and sunny greetings 
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/65e5faa2-2cda-4014-ae79-f236286b312fn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/65e5faa2-2cda-4014-ae79-f236286b312fn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
> -- 
> 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+...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEBdp6zguJhr0awrJ2RQPJUFitTYPWQF20Xnpr%2B_zBhqzw%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEBdp6zguJhr0awrJ2RQPJUFitTYPWQF20Xnpr%2B_zBhqzw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
>

-- 
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/ab3cda47-da42-43a2-98bb-388fc12c70cfn%40googlegroups.com.

[weewx-user] Display the first date entry in the database

[Meteo Oberwallis]

Hello everyone
I would like to display the date of the first entry in the weexs.sdb in 
Belchertownskin. The reason for this is that you can see how long the 
weather station has been in operation. Since I operate several stations, 
this would make my work extremely easier. This could say something like 
"Operating since: 10/2023" or something like that. Can someone help me with 
that?
Thank you and sunny greetings

-- 
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/65e5faa2-2cda-4014-ae79-f236286b312fn%40googlegroups.com.

[weewx-user] Re: xtype tag

[Meteo Oberwallis]

Hello everyone
I have implemented the wetbulp.py file in my weewx. But now I have noticed 
that after creating the column in the database, the value is not saved. 
Could it be that this line is missing in "wetbulb.py"? If so, what would it 
have to look like for it to work?
Thx
bwal...@gmail.com schrieb am Donnerstag, 17. Dezember 2020 um 22:09:09 
UTC+1:

> thank you, i will do this in database.
>
> gjr80 schrieb am Donnerstag, 17. Dezember 2020 um 21:26:28 UTC+1:
>
>> Yes, that will be it. Loading and calculating for a day will be 
>> straightforward, though it will involve a lot of complex calculations being 
>> done each time you call the aggregate (and this will occur each time you 
>> run the report, so potentially every archive interval minutes). On the 
>> other hand, adding wet bulb to the database will involve one complex 
>> calculation every archive interval and any time you use an aggregate it is 
>> a simple hit on the database. In this case I think it may be better to add 
>> wet bulb to the database.
>>
>> Gary
>>
>> On Friday, 18 December 2020 at 06:14:05 UTC+10 bwal...@gmail.com wrote:
>>
>>> No, i just adjustet the vaporpressure.py example.
>>>
>>> But i see what you mean, i have to calculate it by my own, this means i 
>>> have to load all data for a day and calculate it.
>>> im not shure i can do this.
>>> i quess its easyer and better to do this in the database. 
>>>
>>> gjr80 schrieb am Donnerstag, 17. Dezember 2020 um 20:37:57 UTC+1:
>>>
 Hi,

 When you wrote your xtype extension what methods did you implement? Did 
 you implement get_aggregate()?

 Gary

 On Friday, 18 December 2020 at 02:41:34 UTC+10 bwal...@gmail.com wrote:

> Hi
> i made a xtype extension for a wetbulp temperaur. this worsks fine 
> with the $current tag and the image generator.
>
> with tag $day.wetbulp_t.min the chetagenerator rise no error but 
> whrites  $day.wetbulp_t.minin the file...
>
> do i have do add wetbulp_t in database for get this to work?
>


-- 
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/f75db5a1-631b-42b6-ba93-40c6701f2de3n%40googlegroups.com.
#
#Copyright (c) 2020 Tom Keffer 
#
#See the file LICENSE.txt for your full rights.
#
"""This example shows how to extend the XTypes system with a new type, wetbulp_t, the vapor
pressure of water.

REQUIRES WeeWX V4.2 OR LATER!

To use:
1. Stop weewxd
2. Put this file in your user subdirectory.
3. In weewx.conf, subsection [Engine][[Services]], add WetbulptemperureService to the list
"xtype_services". For example, this means changing this

[Engine]
[[Services]]
xtype_services = weewx.wxxtypes.StdWXXTypes, weewx.wxxtypes.StdPressureCooker, weewx.wxxtypes.StdRainRater

to this:

[Engine]
[[Services]]
xtype_services = weewx.wxxtypes.StdWXXTypes, weewx.wxxtypes.StdPressureCooker, weewx.wxxtypes.StdRainRater, user.wetbulp.wetbulpService



4. Restart weewxd

"""
import math

import weewx
import weewx.units
import weewx.xtypes
from weewx.engine import StdService
from weewx.units import ValueTuple


class WetBulp(weewx.xtypes.XType):

def __init__(self, algorithm='simple'):
# Save the algorithm to be used.
self.algorithm = algorithm.lower()

def get_scalar(self, obs_type, record, db_manager):
# We only know how to calculate 'vapor_p'. For everything else, raise an exception UnknownType
if obs_type != 'wetbulp_t':
raise weewx.UnknownType(obs_type)

# We need outTemp in order to do the calculation.
if 'outTemp' not in record or record['outTemp'] is None:
raise weewx.CannotCalculate(obs_type)

# We have everything we need. Start by forming a ValueTuple for the outside temperature.
# To do this, figure out what unit and group the record is in ...
unit_and_group = weewx.units.getStandardUnitType(record['usUnits'], 'outTemp')
# ... then form the ValueTuple.
outTemp_vt = ValueTuple(record['outTemp'], *unit_and_group)

# Both algorithms need temperature in Celsius, so let's make sure our incoming temperature
# is in that unit. Use function convert(). The results will be in the form of a ValueTuple
outTemp_C_vt = weewx.units.convert(outTemp_vt, 'degree_C')
# Get the first element of the ValueTuple. This will be in Celsius:
outTemp_C = outTemp_C_vt[0]



# We need outHumidity in order to do the calculation.
if 'outHumidity' not in record or record['outHumidity'] is None:
raise weewx.CannotCalculate(obs_type)

# We have everything we need. S

[weewx-user] Re: Hard drive power on hours

[Meteo Oberwallis]

Hello Vince.
I have no idea how to solve this? So, better said, how I could then display 
the value in the Belchertown skin under about, for example. It would also 
be interesting if you could display the RPI kernel version there. You can 
read the operating hours of the hard drive with the command in Raspian: 
sudo smartctl --attributes /dev/sda | grep Power_On_Hours. But how do I get 
this value in weewx? It should not be written into the database, but can be 
retrieved every day with a command and then displayed in the Belchertown 
skin. Or are there other ideas?

vince schrieb am Sonntag, 24. September 2023 um 19:08:43 UTC+2:

> I was pointing you to an example as a starting point for 'you' to do the 
> work to add that feature.
>
> On Sunday, September 24, 2023 at 3:34:00 AM UTC-7 Meteo Oberwallis wrote:
>
>> Hey Vince
>>
>> I have cmon and can not find the Hours from the disk. Better, when this 
>> can see z.b under the about Site form Belchertown?
>>
>> vince schrieb am Samstag, 23. September 2023 um 18:55:31 UTC+2:
>>
>>> I would look at extensions like cmon for examples of how to approach 
>>> this.
>>>
>>> On Saturday, September 23, 2023 at 4:51:12 AM UTC-7 Meteo Oberwallis 
>>> wrote:
>>>
>>>> Hello everyone
>>>> I have a Raspberry 3 B+ and an SSD is attached via USB. The operating 
>>>> system (Raspian) and weewx run on it. Now I would like the operating hours 
>>>> of the SSD to be displayed in weewx. This works, if you enter the command 
>>>> "smartctl --attributes "${disk}" | grep Power_On_Hours" via "smartctl", 
>>>> you 
>>>> get the operating hours of the hard drive 
>>>> (https://linuxconfig.org/retrieve-hard-drive 
>>>> -s-age-and-general-health-information-using-linux). Now it would be 
>>>> great if you could display this in weewx. Does anyone have an idea on how 
>>>> this could be implemented? You should be able to save the value of the 
>>>> “operating hours” in weewx?
>>>>
>>>> Kind regards
>>>
>>>

-- 
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/cdc343d5-8298-47e4-92f3-d301deb7fa17n%40googlegroups.com.

[weewx-user] Re: Hard drive power on hours

[Meteo Oberwallis]

Hello Vince.
I have no idea how to solve this? So, better said, how I could then display 
the value in the Belchertown skin under about, for example. It would also 
be interesting if you could display the RPI kernel version there.

vince schrieb am Sonntag, 24. September 2023 um 19:08:43 UTC+2:

> I was pointing you to an example as a starting point for 'you' to do the 
> work to add that feature.
>
> On Sunday, September 24, 2023 at 3:34:00 AM UTC-7 Meteo Oberwallis wrote:
>
>> Hey Vince
>>
>> I have cmon and can not find the Hours from the disk. Better, when this 
>> can see z.b under the about Site form Belchertown?
>>
>> vince schrieb am Samstag, 23. September 2023 um 18:55:31 UTC+2:
>>
>>> I would look at extensions like cmon for examples of how to approach 
>>> this.
>>>
>>> On Saturday, September 23, 2023 at 4:51:12 AM UTC-7 Meteo Oberwallis 
>>> wrote:
>>>
>>>> Hello everyone
>>>> I have a Raspberry 3 B+ and an SSD is attached via USB. The operating 
>>>> system (Raspian) and weewx run on it. Now I would like the operating hours 
>>>> of the SSD to be displayed in weewx. This works, if you enter the command 
>>>> "smartctl --attributes "${disk}" | grep Power_On_Hours" via "smartctl", 
>>>> you 
>>>> get the operating hours of the hard drive 
>>>> (https://linuxconfig.org/retrieve-hard-drive 
>>>> -s-age-and-general-health-information-using-linux). Now it would be 
>>>> great if you could display this in weewx. Does anyone have an idea on how 
>>>> this could be implemented? You should be able to save the value of the 
>>>> “operating hours” in weewx?
>>>>
>>>> Kind regards
>>>
>>>

-- 
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/15334c1d-e4a0-4852-8b4f-73d3907e8123n%40googlegroups.com.

Re: [weewx-user] New Timespan $daylight for the time while sun is up

[Meteo Oberwallis]

Hallo.

Ich habe die:

- Programm version: 4.10.2
- Skin Version: 1.2

Gruss

Karen K schrieb am Sonntag, 15. Oktober 2023 um 11:24:49 UTC+2:

> Welche Belchertown-Version ist es denn? Die Option unit ist, glaube ich, 
> erst irgendwann eingeführt worden.
>
> Funktioniert das mit der Einheit bei anderen Größen? Einfach mal 
> ausprobieren, ob nur die absolute Luftfeuchtigkeit betroffen ist oder auch 
> anderes. Zum Beispiel könnte man in einem Temperaturdiagramm mal testweise 
> nach demselben Prinzip in graphs.conf die Werte in Grad Fahrenheit 
> anzeigen lassen.
>
> Meteo Oberwallis schrieb am Sonntag, 15. Oktober 2023 um 09:40:04 UTC+2:
>
>> Hallo Karen.
>>
>> Genau so habe ich es. Trotzdem habe ich diese dezimalstellenfehler.
>>
>> Gruss
>>
>> Karen K schrieb am Samstag, 14. Oktober 2023 um 14:47:29 UTC+2:
>>
>>> [[humidity]]
>>>
>>> title = "Luftfeuchtigkeit"
>>>
>>> [[[outHumidity]]]
>>>
>>> name = "relativ"
>>>
>>> [[[outHumAbs]]]
>>>
>>>     name = "absolut"
>>>
>>> yAxis = 1
>>>
>>> unit = gram_per_meter_cubed
>>>
>>> numberFormat
>>>
>>> decimals = 1
>>>
>>> Meteo Oberwallis schrieb am Samstag, 14. Oktober 2023 um 12:03:33 UTC+2:
>>>
>>>> Hallo.
>>>> Bei mir wird unter Belchertown bei der Absoluten Luftfeuchtugkeit ein 
>>>> zu grosser Wert angezeigt. Wie kann ich das anpassen?
>>>> [image: 2023_10_14_12_01_34_Clipboard.png]
>>>> Grüsse
>>>>
>>>> Karen K schrieb am Samstag, 30. September 2023 um 08:18:19 UTC+2:
>>>>
>>>>> Yes.
>>>>>
>>>>> Mks Mk schrieb am Samstag, 30. September 2023 um 03:08:55 UTC+2:
>>>>>
>>>>>> when it comes to coding the best we can do is copy and paste,  all we 
>>>>>> wanna know is if this tag (*$daylight*) actually does work within 
>>>>>> NOAA template file.
>>>>>> thank you for your help
>>>>>>
>>>>>> On Friday, September 29, 2023 at 9:13:23 PM UTC+3 Karen K wrote:
>>>>>>
>>>>>>> Mks Mk schrieb am Freitag, 29. September 2023 um 19:09:10 UTC+2:
>>>>>>>
>>>>>>> We want to add below code or similar to its action to the NOAA 
>>>>>>> monthly report file "*NOAA-%Y-%m.txt.tmpl*" but we do not know if 
>>>>>>> it is possible to do so because of the span tags?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Why not trying it?
>>>>>>>
>>>>>>> If you are not sure about the $span tag, you can replace it by 
>>>>>>> something else like $ii
>>>>>>>  
>>>>>>>
>>>>>>

-- 
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/d7c08811-d7a8-4ee4-b558-90eb4344515bn%40googlegroups.com.

Re: [weewx-user] New Timespan $daylight for the time while sun is up

[Meteo Oberwallis]

Hallo Karen.

Genau so habe ich es. Trotzdem habe ich diese dezimalstellenfehler.

Gruss

Karen K schrieb am Samstag, 14. Oktober 2023 um 14:47:29 UTC+2:

> [[humidity]]
>
> title = "Luftfeuchtigkeit"
>
> [[[outHumidity]]]
>
> name = "relativ"
>
> [[[outHumAbs]]]
>
> name = "absolut"
>
> yAxis = 1
>
> unit = gram_per_meter_cubed
>
>     numberFormat
>
> decimals = 1
>
> Meteo Oberwallis schrieb am Samstag, 14. Oktober 2023 um 12:03:33 UTC+2:
>
>> Hallo.
>> Bei mir wird unter Belchertown bei der Absoluten Luftfeuchtugkeit ein zu 
>> grosser Wert angezeigt. Wie kann ich das anpassen?
>> [image: 2023_10_14_12_01_34_Clipboard.png]
>> Grüsse
>>
>> Karen K schrieb am Samstag, 30. September 2023 um 08:18:19 UTC+2:
>>
>>> Yes.
>>>
>>> Mks Mk schrieb am Samstag, 30. September 2023 um 03:08:55 UTC+2:
>>>
>>>> when it comes to coding the best we can do is copy and paste,  all we 
>>>> wanna know is if this tag (*$daylight*) actually does work within NOAA 
>>>> template file.
>>>> thank you for your help
>>>>
>>>> On Friday, September 29, 2023 at 9:13:23 PM UTC+3 Karen K wrote:
>>>>
>>>>> Mks Mk schrieb am Freitag, 29. September 2023 um 19:09:10 UTC+2:
>>>>>
>>>>> We want to add below code or similar to its action to the NOAA monthly 
>>>>> report file "*NOAA-%Y-%m.txt.tmpl*" but we do not know if it is 
>>>>> possible to do so because of the span tags?
>>>>>
>>>>>
>>>>>
>>>>> Why not trying it?
>>>>>
>>>>> If you are not sure about the $span tag, you can replace it by 
>>>>> something else like $ii
>>>>>  
>>>>>
>>>>

-- 
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/af3c9962-0337-40a3-a28d-8a184a15dda5n%40googlegroups.com.

Re: [weewx-user] New Timespan $daylight for the time while sun is up

[Meteo Oberwallis]

Hallo.
Bei mir wird unter Belchertown bei der Absoluten Luftfeuchtugkeit ein zu 
grosser Wert angezeigt. Wie kann ich das anpassen?
[image: 2023_10_14_12_01_34_Clipboard.png]
Grüsse

Karen K schrieb am Samstag, 30. September 2023 um 08:18:19 UTC+2:

> Yes.
>
> Mks Mk schrieb am Samstag, 30. September 2023 um 03:08:55 UTC+2:
>
>> when it comes to coding the best we can do is copy and paste,  all we 
>> wanna know is if this tag (*$daylight*) actually does work within NOAA 
>> template file.
>> thank you for your help
>>
>> On Friday, September 29, 2023 at 9:13:23 PM UTC+3 Karen K wrote:
>>
>>> Mks Mk schrieb am Freitag, 29. September 2023 um 19:09:10 UTC+2:
>>>
>>> We want to add below code or similar to its action to the NOAA monthly 
>>> report file "*NOAA-%Y-%m.txt.tmpl*" but we do not know if it is 
>>> possible to do so because of the span tags?
>>>
>>>
>>>
>>> Why not trying it?
>>>
>>> If you are not sure about the $span tag, you can replace it by something 
>>> else like $ii
>>>  
>>>
>>

-- 
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/b3848de2-a591-4ae0-ae19-4ed0f4a0c0c9n%40googlegroups.com.

[weewx-user] Re: Hard drive power on hours

[Meteo Oberwallis]

Hey Vince

I have cmon and can not find the Hours from the disk. Better, when this can 
see z.b under the about Site form Belchertown?

vince schrieb am Samstag, 23. September 2023 um 18:55:31 UTC+2:

> I would look at extensions like cmon for examples of how to approach this.
>
> On Saturday, September 23, 2023 at 4:51:12 AM UTC-7 Meteo Oberwallis wrote:
>
>> Hello everyone
>> I have a Raspberry 3 B+ and an SSD is attached via USB. The operating 
>> system (Raspian) and weewx run on it. Now I would like the operating hours 
>> of the SSD to be displayed in weewx. This works, if you enter the command 
>> "smartctl --attributes "${disk}" | grep Power_On_Hours" via "smartctl", you 
>> get the operating hours of the hard drive 
>> (https://linuxconfig.org/retrieve-hard-drive 
>> -s-age-and-general-health-information-using-linux). Now it would be 
>> great if you could display this in weewx. Does anyone have an idea on how 
>> this could be implemented? You should be able to save the value of the 
>> “operating hours” in weewx?
>>
>> Kind regards
>
>

-- 
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/61bb6cb1-90af-41ee-93c0-01eca55527c5n%40googlegroups.com.

[weewx-user] Hard drive power on hours

[Meteo Oberwallis]

Hello everyone
I have a Raspberry 3 B+ and an SSD is attached via USB. The operating 
system (Raspian) and weewx run on it. Now I would like the operating hours 
of the SSD to be displayed in weewx. This works, if you enter the command 
"smartctl --attributes "${disk}" | grep Power_On_Hours" via "smartctl", you 
get the operating hours of the hard drive 
(https://linuxconfig.org/retrieve-hard-drive 
-s-age-and-general-health-information-using-linux). Now it would be great 
if you could display this in weewx. Does anyone have an idea on how this 
could be implemented? You should be able to save the value of the 
“operating hours” in weewx?

Kind regards

-- 
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/87c11d62-8120-49eb-a75e-32338ea5b89cn%40googlegroups.com.

[weewx-user] Re: DAVIS Weatherlink Console 6313

[Meteo Oberwallis]

Hello.

Work this with a Davis Envoy and Weatherlink Datalogger Davis 6510 USB?

Thanks
Stefan

Werner Krenn schrieb am Freitag, 1. September 2023 um 20:43:37 UTC+2:

> I made an extension for WeeWx, which can record and display the health 
> data of the DAVIS Weatherlink Console 6313.
>
> https://github.com/WernerKr/weewx-davisconsolehealthapi
>
> Example:
> https://www.pc-wetterstation.de/wetter/weewx/healthc/index.html
>

-- 
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/72ea3888-4b12-43ad-9987-3ba41d75a161n%40googlegroups.com.

[weewx-user] Delay FTP upload

[Meteo Oberwallis]

Hello folks
I wanted to ask if it is possible to delay the FTP upload of the data from 
Weewx a bit? I operate many weather stations and webcams and have often 
noticed that there can be problems with the simultaneous upload. Could this 
be adjusted somehow? Based on sleep?
Thank you for your help

-- 
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/2c72f087-4ef6-4eb5-bd76-8c933b5eb418n%40googlegroups.com.

[weewx-user] weewx airlink update

[Meteo Oberwallis]

Hello everyone.
I use the interval of 10 minutes at Weewx. Now, of course, the fine dust 
pollution is only measured at ten-minute intervals. Is there any way to set 
this interval to every minute? Then it would also be possible to save the 
particulate matter values ​​in a separate SQLite database? Has that 
possibly already run someone of you?
It`s the original Davis Air Quality Sensor.

I have this -> https://github.com/chaunceygardiner/weewx-airlink

Thank for our Help`s

-- 
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/9d580716-93d3-41d4-87c5-54d345e583e8n%40googlegroups.com.

Re: [weewx-user] Sunshine Database

[Meteo Oberwallis]

Hello
Thx for Help. I have the new Code in my sunduration.py and i have this 
fault:

Aug  6 20:59:46 Wetter weewx[11829] DEBUG weewx.engine: Loading service 
user.sunduration.SunshineDuration
Aug  6 20:59:46 Wetter weewx[11829] CRITICAL __main__: Caught unrecoverable 
exception:
Aug  6 20:59:46 Wetter weewx[11829] CRITICAL __main__:   invalid 
syntax (sunduration.py, line 101)
Aug  6 20:59:46 Wetter weewx[11829] CRITICAL __main__:   Traceback 
(most recent call last):
Aug  6 20:59:46 Wetter weewx[11829] CRITICAL __main__: File 
"/usr/share/weewx/weewxd", line 147, in main
Aug  6 20:59:46 Wetter weewx[11829] CRITICAL __main__:   engine 
= weewx.engine.StdEngine(config_dict)
Aug  6 20:59:46 Wetter weewx[11829] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 93, in __init__
Aug  6 20:59:46 Wetter weewx[11829] CRITICAL __main__:  
 self.loadServices(config_dict)
Aug  6 20:59:46 Wetter weewx[11829] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 161, in loadServices
Aug  6 20:59:46 Wetter weewx[11829] CRITICAL __main__:   obj = 
weeutil.weeutil.get_object(svc)(self, config_dict)
Aug  6 20:59:46 Wetter weewx[11829] CRITICAL __main__: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1150, in get_object
Aug  6 20:59:46 Wetter weewx[11829] CRITICAL __main__:   mod = 
__import__(module)
Aug  6 20:59:46 Wetter weewx[11829] CRITICAL __main__: File 
"/usr/share/weewx/user/sunduration.py", line 101
Aug  6 20:59:46 Wetter weewx[11829] CRITICAL __main__:  
 self.sunshineSeconds = 0
Aug  6 20:59:46 Wetter weewx[11829] CRITICAL __main__:  ^
Aug  6 20:59:46 Wetter weewx[11829] CRITICAL __main__:  
 SyntaxError: invalid syntax
Aug  6 20:59:46 Wetter weewx[11829] CRITICAL __main__:   Exiting.

jterr...@gmail.com schrieb am Sonntag, 31. Juli 2022 um 08:16:44 UTC+2:

> Hello,
>
> It seems that radiation values are missing for some archive records.   
> Line 92 of sunduration.py had a wrong indentation.  This is now corrected 
> in my Github repository.
>
> Le 31 juil. 2022 à 06:45, Meteo Oberwallis  a écrit :
>
> Hello. 
>
> I have a Problem, wenn weewx stop an ih restart, can not read the 
> Datalogger from Update to weewx. I have this for logging the sunshine time 
> -> https://github.com/Jterrettaz/sunduration/blob/master/sunduration.py
> I have the Version weewx 4.8.0 
>
> Jul 31 06:31:03 Wetter systemd[1]: Started LSB: weewx weather system.
> Jul 31 06:31:07 Wetter weewx[5077] DEBUG weewx.drivers.vantage: Retry #0 
> failed
> Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.drivers.vantage: Gentle 
> wake up of console successful
> Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.drivers.vantage: Hardware 
> type is 16
> Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.drivers.vantage: ISS ID is 1
> Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.drivers.vantage: Hardware 
> name: Vantage Pro2
> Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
> weewx.engine.StdTimeSynch
> Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdTimeSynch
> Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
> user.cputemp.AddCpuTemp
> Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
> service user.cputemp.AddCpuTemp
> Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
> user.sunduration.SunshineDuration
> Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
> service user.sunduration.SunshineDuration
> Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
> weewx.engine.StdConvert
> Jul 31 06:31:09 Wetter weewx[5077] INFO weewx.engine: StdConvert target 
> unit is 0x1
> Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdConvert
> Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
> weewx.engine.StdCalibrate
> Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdCalibrate
> Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
> weewx.engine.StdQC
> Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdQC
> Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
> weewx.wxservices.StdWXCalculate
> Jul 31 06:31:09 Wetter weewx[5077] INFO weewx.wxservices: StdWXCalculate 
> will use data binding wx_binding
> Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.manager: Daily summary 
> version is 4.0
> Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished 

Re: [weewx-user] Re: Datenbank zusammen legen.

[Meteo Oberwallis]

Hallo.

Ich möchte die Sonnenscheinzeit meiner Wetterstation vom Jahr 2006 ab 
nachführen in weewx. In der weewx.sdb befindet sich die Spalte 
"sunshine_time". Nun habe ich probiert, die Daten hoch zu laden über 
folgenden Code:
[[FieldMap]]
dateTime= Zeit, unix_epoch
usUnits =
interval=
barometer   = Luftdruck, hPa
pressure=
altimeter   =
inTemp  =
outTemp = Temp. A., degree_C
inHumidity  =
outHumidity = Feuchte A., percent
windSpeed   = Wind, km_per_hour
windDir = Richtung, degree_compass
windGust= Windboe, km_per_hour
windGustDir =
rainRate=
rain= Regen, mm
dewpoint=
windchill   =
heatindex   =
ET  =
radiation   = Solar, watt_per_meter_squared
UV  = UV, uv_index
sunshine_time = Sonnenschein, hour

Leider ergibt dies immer einen Fehler:
/home/technik# sudo wee_import --import-config=/var/tmp/csv.conf 
Using WeeWX configuration file /etc/weewx/weewx.conf
Starting wee_import...
A CSV import from source file 
'/home/technik/Schreibtisch/Grächen/EXP_2006.CSV' has been requested.
Using database binding 'wx_binding', which is bound to database 'weewx.sdb'
Destination table 'archive' unit system is '0x01' (US).
Missing derived observations will be calculated.
All WeeWX UV fields will be set to None.
Starting import ...
Warning: Import field 'UV' is mapped to WeeWX field 'UV' but the
 import field 'UV' could not be found in one or more records.
 WeeWX field 'UV' will be set to 'None' in these records.
Traceback (most recent call last):
  File "/usr/share/weewx/wee_import", line 899, in 
main()
  File "/usr/share/weewx/wee_import", line 829, in main
source_obj.run()
  File "/usr/share/weewx/weeimport/weeimport.py", line 410, in run
_mapped_data = self.mapRawData(_raw_data, self.archive_unit_sys)
  File "/usr/share/weewx/weeimport/weeimport.py", line 941, in mapRawData
weewx.units.obs_group_dict[_field])
  File "/usr/share/weewx/weeutil/weeutil.py", line 1501, in __getitem__
return self.__missing__(key)
  File "/usr/share/weewx/weeutil/weeutil.py", line 1493, in __missing__
raise KeyError(key)
KeyError: u'sunshine_time'

Woran könnte das liegen?

Danke für eure Hilfe
Meteo Oberwallis schrieb am Montag, 18. April 2022 um 11:28:04 UTC+2:

> Hallo zusammen.
> Ich probiere nun schon seit geraumer Zeit, die weewx.sdb der Version 3.9.0 
> mit der neuen weewx.sdb der aktuellen Version 4.7.0 zusammen zu legen. Dies 
> klappte bis anhin leider nicht. Nun vermute ich aber, das dies daran liegt, 
> das ab der Version 4.7 ein anderes Shema benutzt wird? Interessanterweise 
> konnte ich die alte weewx.sdb mit wee_database weewx.conf --reconfigure in 
> das richtige format bringen. Nun aber fehlen mit die "sunshine_hours". Die 
> neuste Version von weewx hat ja ebenfalls ein neues "sunshine_time" format. 
> Nun wollte die mittels "rename" einfach die Tabllenespalte anpassen. Dies 
> blieb aber erfolglos. Kann ich die "sunshine_hours" über einen anderen weg 
> ind die neue weewx.sdb in dessen "sunshine_time" spalte kopieren?
> Ich weiss wirklich nicht mehr weiter und würde mich über Hilfen freuen. 
> Vielen Dank
>
> Der Fehler bei der Datenbank zusammenführung:
> Error: near line 333827: table archive has 114 columns but 53 values were 
> supplied
> Error: near line 333828: table archive has 114 columns but 53 values were 
> supplied
> Error: near line 333829: table archive has 114 columns but 53 values were 
> supplied
> Error: near line 333830: table archive has 114 columns but 53 values were 
> supplied
> Error: near line 333831: table archive has 114 columns but 53 values were 
> supplied
> Error: near line 333832: table archive has 114 columns but 53 values were 
> supplied
> Error: near line 333833: table archive has 114 columns but 53 values were 
> supplied
> Error: near line 333834: table archive has 114 columns but 53 values were 
> supplied
> Error: near line 333835: table archive has 114 columns but 53 values were 
> supplied
> Error: near line 333836: table archive has 114 columns but 53 values were 
> supplied
> Error: near line 333837: table archive has 114 columns but 53 values were 
> supplied
> Error: near line 333838: table archive has 114 columns but 53 values were 
> supplied
> Error: near line 333839: table archive has 114 columns but 53 values were 
> supplied
> Error: near line 333840: table archive has 114 columns but 53 values were 
> supplied
> Error: near l

Re: [weewx-user] Sunshine Database

[Meteo Oberwallis]

 Hello. 
I have a Problem, wenn weewx stop an ih restart, can not read the 
Datalogger from Update to weewx. I have this for logging the sunshine time 
-> https://github.com/Jterrettaz/sunduration/blob/master/sunduration.py
I have the Version weewx 4.8.0 

Jul 31 06:31:03 Wetter systemd[1]: Started LSB: weewx weather system.
Jul 31 06:31:07 Wetter weewx[5077] DEBUG weewx.drivers.vantage: Retry #0 
failed
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.drivers.vantage: Gentle wake 
up of console successful
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.drivers.vantage: Hardware 
type is 16
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.drivers.vantage: ISS ID is 1
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.drivers.vantage: Hardware 
name: Vantage Pro2
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.engine.StdTimeSynch
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdTimeSynch
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
user.cputemp.AddCpuTemp
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service user.cputemp.AddCpuTemp
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
user.sunduration.SunshineDuration
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service user.sunduration.SunshineDuration
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.engine.StdConvert
Jul 31 06:31:09 Wetter weewx[5077] INFO weewx.engine: StdConvert target 
unit is 0x1
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdConvert
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.engine.StdCalibrate
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdCalibrate
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.engine.StdQC
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdQC
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.wxservices.StdWXCalculate
Jul 31 06:31:09 Wetter weewx[5077] INFO weewx.wxservices: StdWXCalculate 
will use data binding wx_binding
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.manager: Daily summary 
version is 4.0
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.wxservices.StdWXCalculate
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdWXXTypes
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdWXXTypes
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdPressureCooker
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdPressureCooker
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdRainRater
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdRainRater
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdDelta
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdDelta
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.engine.StdArchive
Jul 31 06:31:09 Wetter weewx[5077] INFO weewx.engine: Archive will use data 
binding wx_binding
Jul 31 06:31:09 Wetter weewx[5077] INFO weewx.engine: Record generation 
will be attempted in 'hardware'
Jul 31 06:31:09 Wetter weewx[5077] ERROR weewx.engine: The archive interval 
in the configuration file (300) does not match the station hardware 
interval (600).
Jul 31 06:31:09 Wetter weewx[5077] INFO weewx.engine: Using archive 
interval of 600 seconds (specified by hardware)
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Use LOOP data in 
hi/low calculations: 1
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdArchive
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.restx.StdStationRegistry
Jul 31 06:31:09 Wetter weewx[5077] INFO weewx.restx: StationRegistry: 
Registration not requested.
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdStationRegistry
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.restx.StdWunderground
Jul 31 06:31:09 Wetter weewx[5077] INFO weewx.restx: Wunderground: Posting 
not enabled.
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdWunderground
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.restx.StdPWSweather
Jul 31 06:31:09 Wetter weewx[5077] INFO weewx.restx: PWSweather: Posting 
not enabled.
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdPWSweather

Re: [weewx-user] Sunshine Database

[Meteo Oberwallis]

Hello. 
I have a Problem, wenn weewx stop an ih restart, can not read the 
Datalogger from Update to weewx. I have this for logging the sunshine time 
-> https://github.com/Jterrettaz/sunduration/blob/master/sunduration.py
I have the Version weewx 4.8.0 

Jul 31 06:31:03 Wetter systemd[1]: Started LSB: weewx weather system.
Jul 31 06:31:07 Wetter weewx[5077] DEBUG weewx.drivers.vantage: Retry #0 
failed
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.drivers.vantage: Gentle wake 
up of console successful
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.drivers.vantage: Hardware 
type is 16
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.drivers.vantage: ISS ID is 1
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.drivers.vantage: Hardware 
name: Vantage Pro2
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.engine.StdTimeSynch
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdTimeSynch
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
user.cputemp.AddCpuTemp
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service user.cputemp.AddCpuTemp
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
user.sunduration.SunshineDuration
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service user.sunduration.SunshineDuration
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.engine.StdConvert
Jul 31 06:31:09 Wetter weewx[5077] INFO weewx.engine: StdConvert target 
unit is 0x1
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdConvert
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.engine.StdCalibrate
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdCalibrate
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.engine.StdQC
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdQC
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.wxservices.StdWXCalculate
Jul 31 06:31:09 Wetter weewx[5077] INFO weewx.wxservices: StdWXCalculate 
will use data binding wx_binding
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.manager: Daily summary 
version is 4.0
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.wxservices.StdWXCalculate
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdWXXTypes
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdWXXTypes
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdPressureCooker
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdPressureCooker
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdRainRater
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdRainRater
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdDelta
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdDelta
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.engine.StdArchive
Jul 31 06:31:09 Wetter weewx[5077] INFO weewx.engine: Archive will use data 
binding wx_binding
Jul 31 06:31:09 Wetter weewx[5077] INFO weewx.engine: Record generation 
will be attempted in 'hardware'
Jul 31 06:31:09 Wetter weewx[5077] ERROR weewx.engine: The archive interval 
in the configuration file (300) does not match the station hardware 
interval (600).
Jul 31 06:31:09 Wetter weewx[5077] INFO weewx.engine: Using archive 
interval of 600 seconds (specified by hardware)
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Use LOOP data in 
hi/low calculations: 1
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdArchive
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.restx.StdStationRegistry
Jul 31 06:31:09 Wetter weewx[5077] INFO weewx.restx: StationRegistry: 
Registration not requested.
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdStationRegistry
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.restx.StdWunderground
Jul 31 06:31:09 Wetter weewx[5077] INFO weewx.restx: Wunderground: Posting 
not enabled.
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdWunderground
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Loading service 
weewx.restx.StdPWSweather
Jul 31 06:31:09 Wetter weewx[5077] INFO weewx.restx: PWSweather: Posting 
not enabled.
Jul 31 06:31:09 Wetter weewx[5077] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdPWSweather

Re: [weewx-user] Sunshine Database

[Meteo Oberwallis]

)
>
> # Start intercepting events:
> self.bind(weewx.NEW_ARCHIVE_RECORD, self.newArchiveRecord)
>
> def newArchiveRecord(self, event):
> global cum_sunshine, cum_time, last_stormRain
> event.record['stormRain'] = last_stormRain
> # for various reasons cum_sunshine does not necessarily contain 
> exactly  seconds of data
> if cum_time > 0: # do not divide by zero!
> event.record['sunshine_time'] = cum_sunshine / cum_time * 
> event.record['interval'] # converted to minutes of sunshine
> else:
> event.record['sunshine_time'] = 0
> cum_sunshine = 0
> cum_time = 0
>
> syslog.syslog(syslog.LOG_DEBUG, "Calculated sunshine_time = %f" % 
> event.record['sunshine_time'])
> ​
> On Saturday, July 16, 2022 at 6:18:05 AM UTC-4 Meteo Oberwallis wrote:
>
>> Hello, everyone.
>> I eagerly await your experiences. It's very interesting what you can do. 
>> Now I wanted to ask you if there is already a finished code that you can 
>> use? Did I understand correctly that with these calculations you can 
>> measure the hours of sunshine by minutes and not just by the interval of 
>> the data logger?
>> Can you use it to fill up past values? So e.g. from the year 2019 or 
>> something?
>>
>> Best regards
>> Stefan
>>
>> Peter Fletcher schrieb am Freitag, 1. Juli 2022 um 19:37:54 UTC+2:
>>
>>> I'm sure you are right about the triggering circumstances. The code in 
>>> my weewx User routines was correct (using the Meteo France limit), but I 
>>> had put in some modifications around the hauteur_soleil test in connection 
>>> with the method I am using to average and 'normalize' the observations for 
>>> the archive reports. I suspect that, in taking out those modifications for 
>>> the archive update code, I inadvertently also removed the original test.
>>>
>>> On Friday, July 1, 2022 at 10:47:43 AM UTC-4 jterr...@gmail.com wrote:
>>>
>>>> OK. 
>>>> The variable "hauteur_soleil is the elevation of the sun, in degree.
>>>> From sunset to sunrise, this value will be negative (i.e. sun below the 
>>>> horizon).  
>>>> The formula developed by Metro France was validated to be effective 
>>>> only if sun elevation is > 3°.
>>>>
>>>> In my own implantation of this algorithm, I decided to start the 
>>>> calculation of the sun threshold as soon as the sun elevation was > 0° 
>>>> *and* that the global radiation as measured by the Davis pyranometer 
>>>> was greeter than 20 W/m2.
>>>>
>>>> I suspect that the few dateTime that trigger your  errors were in a 
>>>> situation in which sun elevation was just below zero and that the measured 
>>>> radiation was just higher than 20 W/m2
>>>>
>>>> Le 1 juil. 2022 à 16:19, 'Peter Fletcher' via weewx-user <
>>>> weewx...@googlegroups.com> a écrit :
>>>>
>>>> Something like that is obviously needed. I don't know how my copy of 
>>>> the code omitted the test for hauteur_soleil being > 0. There are a number 
>>>> of sources from which I may have copied it, and I didn't keep links to all 
>>>> of them, but I can't imagine why I would have deleted the test if my 
>>>> source 
>>>> had included it. I will obviously add it to my working code.
>>>>
>>>> On Friday, July 1, 2022 at 2:45:42 AM UTC-4 jterr...@gmail.com wrote:
>>>>
>>>>> OK.  What I don't understand is that my code had always a test 
>>>>>
>>>>> if hauteur_soleil > 3:  (according to Météo France)
>>>>>
>>>>> or more recently
>>>>>
>>>>>  if hauteur_soleil > 0: 
>>>>>
>>>>> in the function, and this test is not on your function.
>>>>>
>>>>> It should be :
>>>>>
>>>>>  hauteur_soleil = asin(sin((pi / 180) * latitude) * sin((pi / 180) * 
>>>>> declinaison) + cos(
>>>>> (pi / 180) * latitude) * cos((pi / 180) * declinaison) * 
>>>>> cos((pi / 180) * angle_horaire)) * (180 / pi)
>>>>>  If hauteur_soleil > 0:
>>>>>
>>>>>   seuil = (0.73 + 0.06 * cos((pi / 180) * 360 * dayofyear / 365)) * 
>>>>> 1080 * pow(
>>>>>  (sin(pi / 

Re: [weewx-user] Sunshine Database

[Meteo Oberwallis]

gt;> [backfill.py]
>>>>>>> import sqlite3
>>>>>>> from datetime import datetime
>>>>>>> import time
>>>>>>> from math import sin, cos, pi, asin
>>>>>>>
>>>>>>> def sunshineThreshold(mydatetime):
>>>>>>> coeff = 0.9  # change to calibrate with your sensor
>>>>>>> utcdate = datetime.utcfromtimestamp(mydatetime)
>>>>>>> dayofyear = int(time.strftime("%j", time.gmtime(mydatetime)))
>>>>>>> theta = 360 * dayofyear / 365
>>>>>>> equatemps = 0.0172 + 0.4281 * cos((pi / 180) * theta) - 7.3515 
>>>>>>> * sin(
>>>>>>> (pi / 180) * theta) - 3.3495 * cos(2 * (pi / 180) * theta) 
>>>>>>> - 9.3619 * sin(
>>>>>>> 2 * (pi / 180) * theta)
>>>>>>>
>>>>>>> latitude = 43.0346213
>>>>>>> longitude = -78.689362
>>>>>>>
>>>>>>> corrtemps = longitude * 4
>>>>>>> declinaison = asin(0.006918 - 0.399912 * cos((pi / 180) * 
>>>>>>> theta) + 0.070257 * sin(
>>>>>>> (pi / 180) * theta) - 0.006758 * cos(2 * (pi / 180) * 
>>>>>>> theta) + 0.000908 * sin(
>>>>>>> 2 * (pi / 180) * theta)) * (180 / pi)
>>>>>>> minutesjour = utcdate.hour * 60 + utcdate.minute
>>>>>>> tempsolaire = (minutesjour + corrtemps + equatemps) / 60
>>>>>>> angle_horaire = (tempsolaire - 12) * 15
>>>>>>> hauteur_soleil = asin(sin((pi / 180) * latitude) * sin((pi / 
>>>>>>> 180) * declinaison) + cos(
>>>>>>> (pi / 180) * latitude) * cos((pi / 180) * declinaison) * 
>>>>>>> cos((pi / 180) * angle_horaire)) * (180 / pi)
>>>>>>> seuil = (0.73 + 0.06 * cos((pi / 180) * 360 * dayofyear / 365)) 
>>>>>>> * 1080 * pow(
>>>>>>> (sin(pi / 180) * hauteur_soleil), 1.25) * coeff
>>>>>>> return seuil
>>>>>>>
>>>>>>>
>>>>>>> database = 'weewx.sdb'
>>>>>>>
>>>>>>> maxThreshold=0
>>>>>>> count=0
>>>>>>> conn=sqlite3.connect(database)
>>>>>>> cur=conn.execute("SELECT dateTime, Radiation from archive")
>>>>>>> for row in cur:
>>>>>>> count += 1
>>>>>>> if (row[1] is not None) and (row[1] > 20):
>>>>>>> threshold = sunshineThreshold(row[0])
>>>>>>> if threshold > maxThreshold:
>>>>>>> maxThreshold = threshold
>>>>>>> if row[1] > threshold:
>>>>>>> conn.execute("UPDATE archive set SunshineTime = 5 WHERE 
>>>>>>> dateTime = " + str(row[0]))
>>>>>>> if count % 1000 == 0:
>>>>>>> print(count, 'Max Threshold', maxThreshold)
>>>>>>> conn.close
>>>>>>> [/backfill.py]
>>>>>>>
>>>>>>> On Friday, June 10, 2022 at 3:29:40 AM UTC-4 jterr...@gmail.com 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> On my side, I have looked at the CPU utilization on my raspberry Pi 
>>>>>>>> 3B+. I have the mqtt  service service installed, so at each loop all 
>>>>>>>> data 
>>>>>>>> of the packet are sent to the mqtt broker.
>>>>>>>>
>>>>>>>> With mqtt and when calculations of the sunshine threshold is done 
>>>>>>>> for each loop packet, the total CPU utilization of python3 is about 
>>>>>>>> 0.75%
>>>>>>>> With mqtt and without calculation of sunshine threshold : 0.5% of 
>>>>>>>> total CPU.
>>>>>>>>
>>>>>>>> So one can estimate that 0.25 % of total CPU is needed for the 
>>>>>>>> calculation of the threshold value for each LOOP packet.
>>>>>>>>
>>>>>>>>
>>>>>>>> Le 9 juin 2022 à 22:26, 'Peter Fletcher' via weewx-user >>>>>>> googlegroups.com> a 

[weewx-user] Belchertown Charts Color

[Meteo Oberwallis]

Good Morning.

I have a Problem with the Chart Color. The Charts Line is away. See here:
[image: Unbenannt.JPG]
I have weewx Version: 
- Programm version: 3.9.2
- Skin Version: 1.0.1
Can i help me? This all happened a few days ago without making any changes.

Thx for Help

-- 
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/6ca12f82-7c97-427f-836e-b62906742029n%40googlegroups.com.

Re: [weewx-user] Sunshine Database

[Meteo Oberwallis]

Hello folks.

I don't know if you understood me properly. With the help of the solar 
sensor of the Davis, the possibility of sunshine can be determined via 
script and the coordinates. That works fine so far.
But what I would like to do is, if the interval of Weewx and the data 
logger is set to 10 minutes, I would have liked to read the value of the 
solar sensor every minute and then write it into a separate .sdb database 
as possible sunshine. With this you can prevent that you can not measure 
the sunshine in the interval of 10 minutes, but every minute. That would be 
my goal. Since the data logger of the Davis is full within 8 days with an 
interval of 5 minutes, an increase to a 10-minute storage interval could 
increase it to a whopping 16 days. But if I set the interval to 10 minutes, 
then the possible sunshine is only recorded every 10 minutes. Not 
everything in between. If the solar value is then high enough at the 
measuring point, the full 10 minutes are registered as sunshine. With a 
minute interval, this could be obtained even more precisely

Thank you for your feedback

Peter Fletcher schrieb am Donnerstag, 2. Juni 2022 um 23:54:11 UTC+2:

> Well, sort of! I had been wanting to look at sunshine hours for a while, 
> but it is decidedly non-trivial unless you actually have a sensor that can 
> tell when the sun is out (they exist, and use the fact that the sun casts 
> shadows when it is out, but they are very expensive). The approach used by 
> the OP looks promising as a good approximation if you only have the 
> standard VP 2 sensors. What I am doing with it is averaging the LOOP 
> radiation readings over 30 seconds (15 LOOP packets), running the average 
> through the algorithm he uses to get a binary indication of the sun being 
> out during that period, and adding 30 (seconds) to a local variable for 
> 'sun' and 0 for 'no sun'. The archive interval process simply stores the 
> contents of the local variable in the appropriate archive record and then 
> clears the local variable. I still have to work on summarizing and 
> displaying the data.
>
> On Thursday, June 2, 2022 at 11:57:13 AM UTC-4 tke...@gmail.com wrote:
>
>> That would make sense.
>>
>> I've had this same problem with pulse counters. Assuming that the sensor 
>> returns 0 or 1, one resolution is to use an accumulator that extracts the 
>> sum of values (rather than the default average). Then at the end of the 
>> archive interval, multiply the sum by the loop interval. The result will be 
>> the amount of time the sensor returned 1 during the archive interval, which 
>> should be the amount of time the sun was out.
>>
>>
>>
>> On Thu, Jun 2, 2022 at 6:27 AM 'Peter Fletcher' via weewx-user <
>> weewx...@googlegroups.com> wrote:
>>
>>> I think that this is a sensor issue. If the sensor returns only a binary 
>>> (sun/no sun) value, which appears to be the case for this computed 
>>> 'sensor', then sampling it every 10 minutes will give results with a 
>>> granularity of 10 minutes, as the OP describes; if the sensor returns the 
>>> minutes (or seconds) of sunshine within the archive interval (similarly to 
>>> the way the Vantage Rain sensor works), then it doesn't matter (within 
>>> reason) how frequently or infrequently you sample it - the total will be 
>>> valid. For a Davis setup and this sort of computed 'sensor', the 'sensor' 
>>> will probably need to be sampled for each LOOP packet and the results 
>>> accumulated internally and the totals saved in each archive record.
>>>
>>> On Wednesday, June 1, 2022 at 9:50:47 AM UTC-4 tke...@gmail.com wrote:
>>>
>>>> My apologies, but I don't fully understand the problem. If the type you 
>>>> are trying to record is literally the amount of time the sun was out 
>>>> during 
>>>> the archive interval, then, in your example, why would no sunshine be 
>>>> recorded for the full 10 minutes? Wouldn't it be something less, but 
>>>> greater than zero. Say 8 minutes of sunshine?
>>>>
>>>> What, exactly, is the type that you are trying to put in the database? 
>>>> There is no type 'sunshine' within WeeWX. 
>>>>
>>>>
>>>>
>>>> On Wed, Jun 1, 2022 at 5:33 AM Meteo Oberwallis  
>>>> wrote:
>>>>
>>>>> Hello, everyone.
>>>>> I have a question. Would it be possible to create a separate database 
>>>>> for sunshine time? The reason is actually that if the recording interval 
>>>>> is 
>>>>&g

[weewx-user] Sunshine Database

[Meteo Oberwallis]

Hello, everyone.
I have a question. Would it be possible to create a separate database for 
sunshine time? The reason is actually that if the recording interval is set 
to 10 minutes, the hours of sunshine are then only recorded at intervals of 
10 minutes. More precisely, if the solar value is too low in minute 10 or 
20 etc., but the value was higher during 8 minutes, then it automatically 
takes the whole 10 minutes as no sunshine. But if you query the solar value 
every minute via weewx and compare it with the "Sunshine Time", you would 
have a much better record. If there was a separate sql for the sunshine 
time, like e.g. the air quality sensor. In order to make the whole thing 
even gentler, one could solve it in such a way that the "automation" only 
becomes active as soon as the solar sensor delivers a value. Is there any 
of that already? The graphics etc. can then be uploaded normally every 5 or 
10 minutes. But I would just like to have my own .sql for the hours of 
sunshine, which reads the value every minute. The script "
https://github.com/Jterrettaz/sunduration"; already exists.

Thank you for your feedback

-- 
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/8ba76e85-40d0-4e20-84ea-a33b38120e3bn%40googlegroups.com.

[weewx-user] Re: Belchertown Skin Beaufort Category Missing

[Meteo Oberwallis]

Hello.

I have the same Problem. I have activatet the Option in 
Belchertown/skin.conf

# Show Beaufort wind scale category under wind table
beaufort_category = 1
and i can not see the Beaufort text.

In the weewx.conf have it this:

[[Belchertown]]
HTML_ROOT = /var/www/html/weewx/user
skin = Belchertown
[[[Extras]]]
belchertown_root_url = 
https://www.meteo-oberwallis.ch/wetter//x
beaufort_category = 1

What have i for a mistake?

[image: Unbenannt.PNG]

Alan Bryant schrieb am Mittwoch, 21. April 2021 um 19:30:27 UTC+2:

>
> I just did a fresh installation of the Belchertown skin, which I love, 
> thank you Pat, and everything is working so far except for the 
> beaufort_category.
>
> I had this working earlier today, but I was having other intermittent 
> issues, so I did a fresh installation. This time, the intermittent issues 
> are gone, but the beaufort category is not displaying.
>
> I have enabled debug in the Belchertown skin, but I am not seeing anything 
> obvious. Any help would be greatly appreciated!
>
> My website is https://weather.bryantgeeks.com/.
>
> Here is the Belchertown config from weewx.conf:
>
> [[Belchertown]]
> skin = Belchertown
> HTML_ROOT = /var/www/html/weewx
> enable = true
> [[[Labels]]]
>
> Generic
>
> #--- Common Titles under Labels Section to Change ---
> home_page_header = "Pocket Farm Road Weather Conditions"
> # graphs_page_header = "Weather Observation Graphs"
> # reports_page_header = "Weather Observation Reports"
> # records_page_header = "Weather Observation Records"
> # about_page_header = "About This Site"
> powered_by = 'Observations are powered by an  href="/about" target="_blank">Ecowitt Personal Weather Station'
> footer_copyright_text = "Pocket Farm Road Weather"
> # footer_disclaimer_text = "Never make important decisions 
> based on info from this website."
>
> [[[Extras]]]
>
> # For help refer to the docs at 
> https://github.com/poblabs/weewx-belchertown
>
> #--- General Options ---
> belchertown_debug = 1
> belchertown_locale = "auto"
> theme = auto
> theme_toggle_enabled = 1
> logo_image = "
> https://weather.bryantgeeks.com/images/baysidelogo.png";
> # logo_image_dark = ""
> site_title = "Pocket Farm Road Weather"
> station_observations = 
> "barometer","dewpoint","outHumidity","rainWithRainRate","cloudbase","visibility","windrun"
> beaufort_categoty = 1
> manifest_name = "Pocket Farm Road Weather"
> manifest_short_name = "PFRW"
> # aeris_map = 0
> radar_html = 'https://embed.windy.com/embed2.html?lat=28.04291&lon=-97.226451&detailLat=28.04291&detailLon=-97.226451&width=650&height=360&zoom=11&level=surface&overlay=radar&product=radar&menu=&message=true&marker=&calendar=now&pressure=&type=map&location=coordinates&detail=&metricWind=mph&metricTemp=%C2%B0F&radarRange=-1";
>  
> frameborder="0">'   #  (default seems to center on your lat/lon)
> # radar_html_dark = None
> # radar_zoom = 8
> radar_marker = 1
> # almanac_extras = 1
> # highcharts_enabled = 1
> # graph_page_show_all_button = 1
> # graph_page_default_graphgroup = "day"
> # highcharts_homepage_graphgroup = "day"
> # highcharts_decimal = "auto"
> # highcharts_thousands = "auto"
> # googleAnalyticsId = ""
> # pi_kiosk_bold = "false"
> # pi_theme = "auto"
> # webpage_autorefresh = 0
> reload_hook_images = 1
> # reload_images_radar = 300
> # reload_images_hook_asi = -1
> # reload_images_hook_af = -1
> # reload_images_hook_as = -1
> # reload_images_hook_ac = -1
> # show_last_updated_alert = 0
> # last_updated_alert_threshold = 1800
>
> #--- MQTT Websockets (for Real Time Streaming) Options ---
> mqtt_websockets_enabled = 1
> mqtt_websockets_host = "weather.bryantgeeks.com"
> mqtt_websockets_port = 9001
> mqtt_websockets_ssl = 1
> mqtt_websockets_topic = "weather/loop"
> # disconnect_live_website_visitor = 180
>
> #--- Forecast Options ---
> forecast_enabled = 1
> # forecast_provider = "aeris"
> forecast_api_id = ""
> forecast_api_secret = 
> "x"
> # forecast_units = "us"
> # forecast_lang = "en"
> # forecast_stale = 3540
> # forecast_aeris_u

Re: [weewx-user] Re: Merge database failed

[Meteo Oberwallis]

 I have a question. 
Is it possible to use the solar data to create the hours of sunshine 
retrospectively with weewx? 

Meteo Oberwallis schrieb am Dienstag, 3. Mai 2022 um 12:40:02 UTC+2:

> Hello, everyone
>
> Maybe I can help the whole thing along a bit. I installed the Weewx system 
> on a Raspberry and also installed the Davis fine dust sensor extension. 
> After that I made a backup of the whole system so I can use it for my other 
> weather stations. Since the old database (weewx.sdb) now lacks the fields 
> of qm2.5 etc, I reconfigured the database with the new weewx schema. After 
> that I was missing all "sunshine_hours" entries. I use this "
> https://github.com/Jterrettaz/sunduration"; to track the hours of 
> sunshine. But for this to work, I had to set the schema to "schema = 
> user.sunduration.schema_with_sunshine_time". But if you do this with the 
> latest weewx version, the particulate matter sensor no longer works. That 
> means the columns in weewx.sdb are missing. I have had hours of sunshine 
> since 2017, but unfortunately they are missing now. I had to reconfigure 
> the scheme again after "wview-extended". I'm probably making a 
> misconception. Tom is right. I was able to copy and start the old weewx.sdb 
> without any problems. However, the particulate matter sensor then stopped 
> working.
>
> Greeting
> Stefan
>
> tke...@gmail.com schrieb am Montag, 2. Mai 2022 um 16:01:43 UTC+2:
>
>> My apologies, but I'm just not following this.
>>
>> There is no "upgrading" of the database. They are all the same. You can 
>> take a database from wview 15 years ago, and run it on a modern WeeWX with 
>> no changes.
>>
>> Now it's true that the *default* schema for WeeWX changed in V4.0 from 
>> the "wview" schema to the "wview-extended" schema, but old schemas will run 
>> without change.   Simply move the old database into place --- no need to 
>> "import" it.
>>
>> Perhaps I'm missing some subtlety here, but I keep seeing this. 
>>
>> *There is no need to "upgrade" your database!* Just use it.
>>
>> On Mon, May 2, 2022 at 6:33 AM Burns Fisher  wrote:
>>
>>> I've been a WeeWX user since late 2013.  At first I ported it to a 
>>> BeagleBone Black but  I moved it to a Raspberry Pi somewhere around late 
>>> 2018.  The point of all this is that I have been running it for years--last 
>>> version was 3.8.0, I think, but just this weekend I actually upgraded the 
>>> whole Pi to the latest Raspbian as well as WeeWX 4.8.  I appreciate that 
>>> WeeWX can upgrade the database files automagically, but just like the 
>>> original poster here, I am stuck with an old database that I'd like to 
>>> import.  
>>>
>>> The Raspberry Pi folks have a tendency to say "Yes, you can upgrade 
>>> Raspbian, but it is much easier to just install the new version fresh" (and 
>>> this is my experience in other cases too!).  This precludes upgrading WeeWX 
>>> and thus the database does not automatically get upgraded.  I found this 
>>> post after I had already installed the new system and it had been running 
>>> for a day or so (without any old data).  It turns out that the 
>>> "reconfigure" above was just what I needed.  I stopped WeeWX, made a copy 
>>> of the day-old database and replaced it with the old one.  Then ran 
>>> re-configure and rebuilt the daily summaries (must use "sudo"!)  and 
>>> started up WeeWX.  Interestingly, WeeWX must have had to rebuild some more 
>>> because it was not till I looked this morning that a whole year's worth of 
>>> data was showing under "Year".  But the other interesting thing is that it 
>>> apparently re-downloaded data from my Vantage's buffer so it seems to have 
>>> all the data from the past couple days and I don't have to merge in the 
>>> "new" database.
>>>
>>> Anyway, besides giving my experience, I'd like to suggest that idea that 
>>> an upgrade on Raspberry Pi might often consist of a complete new system be 
>>> included in the documentation.  Then also mention 'reconfigure'.  The only 
>>> hard part about this was finding the information!  Thanks to everyone for 
>>> it being here at all!
>>>
>>> Thanks for listening...
>>>
>>> Burns
>>>
>>> On Monday, April 25, 2022 at 5:30:05 AM UTC-4 Meteo Oberwallis wrote:
>>>
>>>> The old schema was 
>>&g

Re: [weewx-user] Re: Merge database failed

[Meteo Oberwallis]

Hello, everyone

Maybe I can help the whole thing along a bit. I installed the Weewx system 
on a Raspberry and also installed the Davis fine dust sensor extension. 
After that I made a backup of the whole system so I can use it for my other 
weather stations. Since the old database (weewx.sdb) now lacks the fields 
of qm2.5 etc, I reconfigured the database with the new weewx schema. After 
that I was missing all "sunshine_hours" entries. I use this 
"https://github.com/Jterrettaz/sunduration"; to track the hours of sunshine. 
But for this to work, I had to set the schema to "schema = 
user.sunduration.schema_with_sunshine_time". But if you do this with the 
latest weewx version, the particulate matter sensor no longer works. That 
means the columns in weewx.sdb are missing. I have had hours of sunshine 
since 2017, but unfortunately they are missing now. I had to reconfigure 
the scheme again after "wview-extended". I'm probably making a 
misconception. Tom is right. I was able to copy and start the old weewx.sdb 
without any problems. However, the particulate matter sensor then stopped 
working.

Greeting
Stefan

tke...@gmail.com schrieb am Montag, 2. Mai 2022 um 16:01:43 UTC+2:

> My apologies, but I'm just not following this.
>
> There is no "upgrading" of the database. They are all the same. You can 
> take a database from wview 15 years ago, and run it on a modern WeeWX with 
> no changes.
>
> Now it's true that the *default* schema for WeeWX changed in V4.0 from 
> the "wview" schema to the "wview-extended" schema, but old schemas will run 
> without change.   Simply move the old database into place --- no need to 
> "import" it.
>
> Perhaps I'm missing some subtlety here, but I keep seeing this. 
>
> *There is no need to "upgrade" your database!* Just use it.
>
> On Mon, May 2, 2022 at 6:33 AM Burns Fisher  wrote:
>
>> I've been a WeeWX user since late 2013.  At first I ported it to a 
>> BeagleBone Black but  I moved it to a Raspberry Pi somewhere around late 
>> 2018.  The point of all this is that I have been running it for years--last 
>> version was 3.8.0, I think, but just this weekend I actually upgraded the 
>> whole Pi to the latest Raspbian as well as WeeWX 4.8.  I appreciate that 
>> WeeWX can upgrade the database files automagically, but just like the 
>> original poster here, I am stuck with an old database that I'd like to 
>> import.  
>>
>> The Raspberry Pi folks have a tendency to say "Yes, you can upgrade 
>> Raspbian, but it is much easier to just install the new version fresh" (and 
>> this is my experience in other cases too!).  This precludes upgrading WeeWX 
>> and thus the database does not automatically get upgraded.  I found this 
>> post after I had already installed the new system and it had been running 
>> for a day or so (without any old data).  It turns out that the 
>> "reconfigure" above was just what I needed.  I stopped WeeWX, made a copy 
>> of the day-old database and replaced it with the old one.  Then ran 
>> re-configure and rebuilt the daily summaries (must use "sudo"!)  and 
>> started up WeeWX.  Interestingly, WeeWX must have had to rebuild some more 
>> because it was not till I looked this morning that a whole year's worth of 
>> data was showing under "Year".  But the other interesting thing is that it 
>> apparently re-downloaded data from my Vantage's buffer so it seems to have 
>> all the data from the past couple days and I don't have to merge in the 
>> "new" database.
>>
>> Anyway, besides giving my experience, I'd like to suggest that idea that 
>> an upgrade on Raspberry Pi might often consist of a complete new system be 
>> included in the documentation.  Then also mention 'reconfigure'.  The only 
>> hard part about this was finding the information!  Thanks to everyone for 
>> it being here at all!
>>
>> Thanks for listening...
>>
>> Burns
>>
>> On Monday, April 25, 2022 at 5:30:05 AM UTC-4 Meteo Oberwallis wrote:
>>
>>> The old schema was 
>>> "schema=user.radiationhours.schema_with_sunshine_hours". If I load my old 
>>> weewx.sdb and then configure it with "wee_database weewx.conf 
>>> --reconfigure" then this deletes the "sunshine_hours" column. All other 
>>> data will be accepted. I'll try your instructions to see if it works.
>>> Thanks very much
>>>
>>> vince schrieb am Sonntag, 24. April 2022 um 21:55:37 UTC+2:
>>>
>>>> I have no 

Re: [weewx-user] Re: Merge database failed

[Meteo Oberwallis]

The old schema was "schema=user.radiationhours.schema_with_sunshine_hours". 
If I load my old weewx.sdb and then configure it with "wee_database 
weewx.conf --reconfigure" then this deletes the "sunshine_hours" column. 
All other data will be accepted. I'll try your instructions to see if it 
works.
Thanks very much

vince schrieb am Sonntag, 24. April 2022 um 21:55:37 UTC+2:

> I have no idea where sunshine_hours comes from.  Did you add it to your 
> old weewx schema ?   If so you'd need to similarly add it to the new schema 
> probably before doing your conversion and see if wee_database is smart 
> enough to do the right thing.
>
> (untested - but give it a try.  This is why you always work off copies of 
> your data..).
>
> On Sunday, April 24, 2022 at 12:29:04 PM UTC-7 Meteo Oberwallis wrote:
>
>> Hello Vince Many thanks for your response. I moved my old weewx.sdb to 
>> the new weewx version and then created it in the new format with 
>> "wee_database weewx.conf --reconfigure". Unfortunately, the 
>> "sunshine_hours" was deleted in the process. Can I somehow transfer these 
>> to the new scheme? Greeting
>>
>

-- 
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/3bac7ec3-a2fc-4e69-a35d-67208b097757n%40googlegroups.com.

[weewx-user] Merge database failed

[Meteo Oberwallis]

Hello, everyone.
I wanted to merge my old weewx.sbd (Version 3.9.2) with the new version of 
weewx 4.8.0. I did this via:
Dump the db1.sdb database to a file:

$sqlite3 /path/to/db1.sdb
sqlite> .output /var/tmp/db1.dump
sqlite> .dump
sqlite> .quit

Now import the dumped data into the final database weewx.sdb:

$ sqlite3 /home/weewx/archive/weewx.sdb
sqlite> .read /var/tmp/db1.dump
sqlite> .quit

now I get the following error:

Error: near line 333827: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333828: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333829: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333830: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333831: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333832: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333833: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333834: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333835: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333836: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333837: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333838: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333839: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333840: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333841: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333842: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333843: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333844: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333845: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333846: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333847: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333848: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333849: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333850: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333851: table archive has 114 columns but 53 values ​​were 
supplied
Error: near line 333852: table archive has 114 columns but 53 values ​​were 
supplied

Why could that be. The database was previously with
[data bindings]

[[wx_binding]]
# The database must match one of the sections in [Databases].
# This is likely to be the only option you would want to change.
database = archive_sqlite
# The name of the table within the database
table_name = archive
# The manager handles aggregation of data for historical summaries
manager = weewx.wxmanager.WXDaySummaryManager
# The schema defines the structure of the database.
# It is *only* used when the database is created.
#schema = schemas.wview.schema
schema = user.radiationhours.schema_with_sunshine_hours

thank you for your help

-- 
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/af520b1a-83b8-4fa1-9073-6ad50a3da507n%40googlegroups.com.

Re: [weewx-user] Re: Datenbank zusammen legen.

[Meteo Oberwallis]

Hallo zusammen.
Ich probiere nun schon seit geraumer Zeit, die weewx.sdb der Version 3.9.0 
mit der neuen weewx.sdb der aktuellen Version 4.7.0 zusammen zu legen. Dies 
klappte bis anhin leider nicht. Nun vermute ich aber, das dies daran liegt, 
das ab der Version 4.7 ein anderes Shema benutzt wird? Interessanterweise 
konnte ich die alte weewx.sdb mit wee_database weewx.conf --reconfigure in 
das richtige format bringen. Nun aber fehlen mit die "sunshine_hours". Die 
neuste Version von weewx hat ja ebenfalls ein neues "sunshine_time" format. 
Nun wollte die mittels "rename" einfach die Tabllenespalte anpassen. Dies 
blieb aber erfolglos. Kann ich die "sunshine_hours" über einen anderen weg 
ind die neue weewx.sdb in dessen "sunshine_time" spalte kopieren?
Ich weiss wirklich nicht mehr weiter und würde mich über Hilfen freuen. 
Vielen Dank

Der Fehler bei der Datenbank zusammenführung:
Error: near line 333827: table archive has 114 columns but 53 values were 
supplied
Error: near line 333828: table archive has 114 columns but 53 values were 
supplied
Error: near line 333829: table archive has 114 columns but 53 values were 
supplied
Error: near line 333830: table archive has 114 columns but 53 values were 
supplied
Error: near line 333831: table archive has 114 columns but 53 values were 
supplied
Error: near line 333832: table archive has 114 columns but 53 values were 
supplied
Error: near line 333833: table archive has 114 columns but 53 values were 
supplied
Error: near line 333834: table archive has 114 columns but 53 values were 
supplied
Error: near line 333835: table archive has 114 columns but 53 values were 
supplied
Error: near line 333836: table archive has 114 columns but 53 values were 
supplied
Error: near line 333837: table archive has 114 columns but 53 values were 
supplied
Error: near line 333838: table archive has 114 columns but 53 values were 
supplied
Error: near line 333839: table archive has 114 columns but 53 values were 
supplied
Error: near line 333840: table archive has 114 columns but 53 values were 
supplied
Error: near line 333841: table archive has 114 columns but 53 values were 
supplied
Error: near line 333842: table archive has 114 columns but 53 values were 
supplied
Error: near line 333843: table archive has 114 columns but 53 values were 
supplied
Error: near line 333844: table archive has 114 columns but 53 values were 
supplied
Error: near line 333845: table archive has 114 columns but 53 values were 
supplied
Error: near line 333846: table archive has 114 columns but 53 values were 
supplied
Error: near line 333847: table archive has 114 columns but 53 values were 
supplied
Error: near line 333848: table archive has 114 columns but 53 values were 
supplied
Error: near line 333849: table archive has 114 columns but 53 values were 
supplied
Error: near line 333850: table archive has 114 columns but 53 values were 
supplied
Error: near line 333851: table archive has 114 columns but 53 values were 
supplied
Error: near line 333852: table archive has 114 columns but 53 values were 
supplied


Hello, everyone.
For some time now I've been trying to merge the weewx.sdb of version 3.9.0 
with the new weewx.sdb of the current version 4.7.0. Unfortunately, this 
has not worked so far. But now I assume that this is due to the fact that a 
different shema is used from version 4.7 onwards? Interestingly, I was able 
to get the old weewx.sdb into the right format with wee_database weewx.conf 
--reconfigure. But now I'm missing the "sunshine_hours". The latest version 
of weewx also has a new "sunshine_time" format. Now she just wanted to 
adjust the table column using "rename". But this was unsuccessful. Can I 
use another way to copy the "sunshine_hours" into the new weewx.sdb in its 
"sunshine_time" column?
I really don't know what to do and would appreciate any help. Thanks very 
much

Meteo Oberwallis schrieb am Donnerstag, 31. März 2022 um 11:35:55 UTC+2:

> Hello, everyone.
>
> The error really seems to be with the database, i.e. SQLite, since the 
> "user.sunduration.schema_with_sunshine_time" will have a different 
> structure. But what can I do now so that I can use my old database from the 
> previous weewx version again with the latest version and thus overwrite the 
> sunshine hours (old name in the old weewx.sdb) in the new one?
>
> Many thanks for your help
>
> Meteo Oberwallis schrieb am Montag, 28. März 2022 um 19:39:22 UTC+2:
>
>> Hey Tom.
>>
>>  
>>
>> Thx for your Help. 
>>
>> In the new weewx version, "schema = schemas.wview_extended.schema" is 
>> used with the table. In the previous version of weewx, however, this was 
>> "schema = user.radiationhours.schema_with_sunshine_hours". What exactly do 
>> I have to do if I tr

Re: [weewx-user] Re: Datenbank zusammen legen.

[Meteo Oberwallis]

Hello, everyone.
For some time now I've been trying to merge the weewx.sdb of version 3.9.0 
with the new weewx.sdb of the current version 4.7.0. Unfortunately, this 
has not worked so far. But now I assume that this is due to the fact that a 
different shema is used from version 4.7 onwards? Interestingly, I was able 
to get the old weewx.sdb into the right format with wee_database weewx.conf 
--reconfigure. But now I'm missing the "sunshine_hours". The latest version 
of weewx also has a new "sunshine_time" format. Now she just wanted to 
adjust the table column using "rename". But this was unsuccessful. Can I 
use another way to copy the "sunshine_hours" into the new weewx.sdb in its 
"sunshine_time" column?
I really don't know what to do and would appreciate any help. 
Thanks very much

Meteo Oberwallis schrieb am Donnerstag, 31. März 2022 um 11:35:55 UTC+2:

> Hello, everyone.
>
> The error really seems to be with the database, i.e. SQLite, since the 
> "user.sunduration.schema_with_sunshine_time" will have a different 
> structure. But what can I do now so that I can use my old database from the 
> previous weewx version again with the latest version and thus overwrite the 
> sunshine hours (old name in the old weewx.sdb) in the new one?
>
> Many thanks for your help
>
> Meteo Oberwallis schrieb am Montag, 28. März 2022 um 19:39:22 UTC+2:
>
>> Hey Tom.
>>
>>  
>>
>> Thx for your Help. 
>>
>> In the new weewx version, "schema = schemas.wview_extended.schema" is 
>> used with the table. In the previous version of weewx, however, this was 
>> "schema = user.radiationhours.schema_with_sunshine_hours". What exactly do 
>> I have to do if I transfer my old weewx.sdb to the program? Do I then have 
>> to adapt these with sudo wee_database weewx.conf --reconfigure to the 
>> ""schema = schemas.wview_extended.schema"? I think that's where my problem 
>> lies.
>>
>>  
>>
>> Currently I did the following: Old weewx.sdb in the /var/lib/weewx/ 
>> folder. Then adjust the column names with "wee_database 
>> --rename-column=sunshine_hours --to-name=sunshine_time" and finally adjust 
>> the new Shmea from weewx with sudo wee_database weewx.conf --reconfigure. 
>> After I did that, the "sunshine_time" column was gone. Only after "sudo 
>> wee_database --add-column=sunshine_time" is it back, but unfortunately 
>> without all the data from the last few years.
>>
>>  
>>
>> Where is my mistake?
>>
>>  
>>
>> *Von:* weewx...@googlegroups.com  *Im Auftrag 
>> von *Tom Keffer
>> *Gesendet:* Montag, 28. März 2022 13:51
>> *An:* weewx-user 
>> *Betreff:* Re: [weewx-user] Re: Datenbank zusammen legen.
>>
>>  
>>
>> If I understand correctly, you're trying to rename a database type from 
>> sunshine_hours to sunshine_time.
>>
>>  
>>
>> If so, use the utility wee_database with the --rename-column 
>> <http://www.weewx.com/docs/utilities.htm#Action_--rename-column> option:
>>
>>  
>>
>> *wee_database --rename-column=sunshine_hours --to-name=sunshine_time*
>>
>>  
>>
>> Make a backup first.
>>
>>  
>>
>> On Mon, Mar 28, 2022 at 12:14 AM Meteo Oberwallis  
>> wrote:
>>
>> Good Morning
>>
>>  
>>
>> I have a question regarding the SQLite database. I updated weewx and now 
>> use sunshine_time instead of sunshine_hours. Now of course the problem is 
>> that the old sunshine times are in the sunshine_hours column and not in the 
>> sunshine_time. How can I fix the fact that the old sunshine_hours data is 
>> now being sent to the sunshine_time splate?
>>
>> Thanks and Greetings
>>
>> kawa...@gmail.com schrieb am Sonntag, 19. April 2020 um 19:30:30 UTC+2:
>>
>> Hallo
>>
>>  
>>
>> wenn du die Standard Installation hast ist das 
>> /home/weewx/public_html/NOAA oder /var/www/html/weewx/NOAA so wie es 
>> Gary geschrieben hat.
>>
>>  
>>
>> Grüße
>>
>>  
>>
>>  
>>
>> Hello
>>
>>  
>>
>> if you have the standard installation this is 
>> /home/weewx/public_html/NOAA or /var/www/html/weewx/NOAA as Gary wrote it.
>>
>>  
>>
>> greetings
>>
>>  
>>
>>  
>>
>>  
>>
>>
>> Am Sonntag, 19. April 2020 13:58:05 UTC+2 schrieb Meteo Oberwallis:
>>
>> Hallo Günther
>>
>>  
>>
>> Nun. Das 

Re: [weewx-user] Re: Datenbank zusammen legen.

[Meteo Oberwallis]

Hello, everyone.

The error really seems to be with the database, i.e. SQLite, since the 
"user.sunduration.schema_with_sunshine_time" will have a different 
structure. But what can I do now so that I can use my old database from the 
previous weewx version again with the latest version and thus overwrite the 
sunshine hours (old name in the old weewx.sdb) in the new one?

Many thanks for your help

Meteo Oberwallis schrieb am Montag, 28. März 2022 um 19:39:22 UTC+2:

> Hey Tom.
>
>  
>
> Thx for your Help. 
>
> In the new weewx version, "schema = schemas.wview_extended.schema" is used 
> with the table. In the previous version of weewx, however, this was "schema 
> = user.radiationhours.schema_with_sunshine_hours". What exactly do I have 
> to do if I transfer my old weewx.sdb to the program? Do I then have to 
> adapt these with sudo wee_database weewx.conf --reconfigure to the ""schema 
> = schemas.wview_extended.schema"? I think that's where my problem lies.
>
>  
>
> Currently I did the following: Old weewx.sdb in the /var/lib/weewx/ 
> folder. Then adjust the column names with "wee_database 
> --rename-column=sunshine_hours --to-name=sunshine_time" and finally adjust 
> the new Shmea from weewx with sudo wee_database weewx.conf --reconfigure. 
> After I did that, the "sunshine_time" column was gone. Only after "sudo 
> wee_database --add-column=sunshine_time" is it back, but unfortunately 
> without all the data from the last few years.
>
>  
>
> Where is my mistake?
>
>  
>
> *Von:* weewx...@googlegroups.com  *Im Auftrag 
> von *Tom Keffer
> *Gesendet:* Montag, 28. März 2022 13:51
> *An:* weewx-user 
> *Betreff:* Re: [weewx-user] Re: Datenbank zusammen legen.
>
>  
>
> If I understand correctly, you're trying to rename a database type from 
> sunshine_hours to sunshine_time.
>
>  
>
> If so, use the utility wee_database with the --rename-column 
> <http://www.weewx.com/docs/utilities.htm#Action_--rename-column> option:
>
>  
>
> *wee_database --rename-column=sunshine_hours --to-name=sunshine_time*
>
>  
>
> Make a backup first.
>
>  
>
> On Mon, Mar 28, 2022 at 12:14 AM Meteo Oberwallis  
> wrote:
>
> Good Morning
>
>  
>
> I have a question regarding the SQLite database. I updated weewx and now 
> use sunshine_time instead of sunshine_hours. Now of course the problem is 
> that the old sunshine times are in the sunshine_hours column and not in the 
> sunshine_time. How can I fix the fact that the old sunshine_hours data is 
> now being sent to the sunshine_time splate?
>
> Thanks and Greetings
>
> kawa...@gmail.com schrieb am Sonntag, 19. April 2020 um 19:30:30 UTC+2:
>
> Hallo
>
>  
>
> wenn du die Standard Installation hast ist das 
> /home/weewx/public_html/NOAA oder /var/www/html/weewx/NOAA so wie es Gary 
> geschrieben hat.
>
>  
>
> Grüße
>
>  
>
>  
>
> Hello
>
>  
>
> if you have the standard installation this is /home/weewx/public_html/NOAA 
> or /var/www/html/weewx/NOAA as Gary wrote it.
>
>  
>
> greetings
>
>  
>
>  
>
>  
>
>
> Am Sonntag, 19. April 2020 13:58:05 UTC+2 schrieb Meteo Oberwallis:
>
> Hallo Günther
>
>  
>
> Nun. Das finde ich so nirgends in meinem weewx Ordner. Ist das der Ordner, 
> bevor es via FTP hochgeladen wird?
>
>  
>
> Gruss
>
>  
>
> *Von:* weewx...@googlegroups.com  *Im Auftrag 
> von *Günther Wrana
> *Gesendet:* Sonntag, 19. April 2020 08:32
> *An:* weewx-user 
> *Betreff:* Re: [weewx-user] Re: Datenbank zusammen legen.
>
>  
>
> Hallo
>
>  
>
> Ich habe die Dateien im /var/weewx/reports/NOAA gelöscht aber ich habe 
> diesen Pfad bei mir vorher so geändert damit diese Dateien nicht auf die 
> SD-Karte sondern in den RAM Speicher geschrieben werden.
>
>  
>
> Grüße Günther
>
> Hello
>
>  
>
> I deleted the files in /var/weewx/reports/NOAA but I changed this path for 
> me beforehand so that these files are not written to the SD card but to the 
> RAM memory.
>
>  
>
> Regards Günther
>
>  
>
>  
>
> Am Samstag, 18. April 2020 17:45:24 UTC+2 schrieb Meteo Oberwallis:
>
> Hallo Günther
>
>  
>
> In welchem Ordner hast du das gelöscht? 
>
>  
>
>  
>
> On Sat, Apr 18, 2020 at 5:34 PM +0200, "Günther Wrana"  
> wrote:
>
> Hello
>
> I deleted the file NOAA-2019-05.txt, NOAA-2019.txt and it worked 
> perfectly. For me is now the 01.05.2015 that I imported. The fact that 
> there is nothing inside has happened to me even though I have only de

Re: [weewx-user] Re: Datenbank zusammen legen.

[Meteo Oberwallis]

Good Morning

I have a question regarding the SQLite database. I updated weewx and now 
use sunshine_time instead of sunshine_hours. Now of course the problem is 
that the old sunshine times are in the sunshine_hours column and not in the 
sunshine_time. How can I fix the fact that the old sunshine_hours data is 
now being sent to the sunshine_time splate?

Thanks and Greetings

kawa...@gmail.com schrieb am Sonntag, 19. April 2020 um 19:30:30 UTC+2:

> Hallo
>
> wenn du die Standard Installation hast ist das 
> /home/weewx/public_html/NOAA oder /var/www/html/weewx/NOAA so wie es Gary 
> geschrieben hat.
>
> Grüße
>
>
> Hello
>
> if you have the standard installation this is /home/weewx/public_html/NOAA 
> or /var/www/html/weewx/NOAA as Gary wrote it.
>
> greetings
>
>
>
>
> Am Sonntag, 19. April 2020 13:58:05 UTC+2 schrieb Meteo Oberwallis:
>
>> Hallo Günther
>>
>>  
>>
>> Nun. Das finde ich so nirgends in meinem weewx Ordner. Ist das der 
>> Ordner, bevor es via FTP hochgeladen wird?
>>
>>  
>>
>> Gruss
>>
>>  
>>
>> *Von:* weewx...@googlegroups.com  *Im Auftrag 
>> von *Günther Wrana
>> *Gesendet:* Sonntag, 19. April 2020 08:32
>> *An:* weewx-user 
>> *Betreff:* Re: [weewx-user] Re: Datenbank zusammen legen.
>>
>>  
>>
>> Hallo
>>
>>  
>>
>> Ich habe die Dateien im /var/weewx/reports/NOAA gelöscht aber ich habe 
>> diesen Pfad bei mir vorher so geändert damit diese Dateien nicht auf die 
>> SD-Karte sondern in den RAM Speicher geschrieben werden.
>>
>>  
>>
>> Grüße Günther
>>
>> Hello
>>
>>  
>>
>> I deleted the files in /var/weewx/reports/NOAA but I changed this path 
>> for me beforehand so that these files are not written to the SD card but to 
>> the RAM memory.
>>
>>  
>>
>> Regards Günther
>>
>>  
>>
>>  
>>
>> Am Samstag, 18. April 2020 17:45:24 UTC+2 schrieb Meteo Oberwallis:
>>
>> Hallo Günther
>>
>>  
>>
>> In welchem Ordner hast du das gelöscht? 
>>
>>  
>>
>>
>>
>> On Sat, Apr 18, 2020 at 5:34 PM +0200, "Günther Wrana"  
>> wrote:
>>
>> Hello
>>
>> I deleted the file NOAA-2019-05.txt, NOAA-2019.txt and it worked 
>> perfectly. For me is now the 01.05.2015 that I imported. The fact that 
>> there is nothing inside has happened to me even though I have only deleted 
>> the NOAA.txt. Maybe you have to restart or reload weewx.
>>
>>  
>>
>> Günther
>>
>>
>> Am Samstag, 18. April 2020 14:56:21 UTC+2 schrieb Meteo Oberwallis:
>>
>> Hello.
>>
>> I have now deleted the data in the folder "/var/www/html/weewx/NOAA/". These 
>> came again after the next interval. Unfortunately without data. Do I have to 
>> delete it anywhere else?
>>
>> Thank you for your top help
>>
>>
>>
>> Am Freitag, 17. April 2020 23:42:39 UTC+2 schrieb 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...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/8fc609f0-224a-4205-98d4-410a7acc759f%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/8fc609f0-224a-4205-98d4-410a7acc759f%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> -- 
>> 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/f02b56bc-8550-45f7-95ae-3e58054284d5%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/f02b56bc-8550-45f7-95ae-3e58054284d5%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/f7df793b-6e6b-43f8-95e8-799af2218b3en%40googlegroups.com.

Re: [weewx-user] Sunshine Duration

[Meteo Oberwallis]

Hello.

I have a problem. I'm using https://github.com/Jterrettaz/sunduration and 
that works so far. I can also set the value via $current.sunshine_time and 
then get 5.0 minutes. However, the whole thing doesn't work for the daytime 
sunshine time with $day.sunshine_time. I built this for my XML file. This 
looks like this: 


 
 
 
 
 


Now I get an error that the day.sunshine_time cannot be read. Anyone have 
an idea why?

Thanks very much 

tke...@gmail.com schrieb am Donnerstag, 24. März 2022 um 22:15:05 UTC+1:

> You definitely don't want sunshine_hours (or sunshineHours) because that 
> implies a unit. I would suggest "daylight".
>
> As for which unit group, the almanac uses group_deltatime for length of 
> day. It's normally measured in seconds.
>
> On Thu, Mar 24, 2022 at 10:54 AM Karen K  wrote:
>
>> I bought a sunshine duration sensor from Weerhuisje. When integrating it 
>> in WeeWX I wondered how to call the observation type. There is nothing 
>> appropriate in the standard schema. I found 2 extensions regarding sunshine 
>> duration. One of them calls the observation type "sunshine_hours", the 
>> other one "sunshine_time". 
>>
>> I would guess it is not generally a good idea to include an underscore in 
>> the observation type name, as the underscore is used to separate the unit 
>> from the observation type in the widely used MQTT extension.
>>
>> And I guess it would be better to have the same name irrespective of the 
>> data source, which extension or hardware is used.
>>
>> Another thing is the unit group. I would allocate the sunshine duration 
>> to group_deltatime, as the output would be something like "8 hours, 45 
>> minutes, 10 seconds" or so. group_interval would be less appropriate, as 
>> sunshine duration is not exactly an interval but rather a time period.
>>
>> After all I am not sure.
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/e8adff2f-8552-4c1e-8cdd-74d2c15dd514n%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/50cf4bba-f773-42f6-876f-a98c1ea35157n%40googlegroups.com.

[weewx-user] Re: Extending weewx - collecting processor and OS statistics and graphing the data

[Meteo Oberwallis]

 Good Morning.

Is it possible to adjust the sizes? As you can see in the picture, the 
resolution is displayed much too large. For example, if you could display 
the kB in MB? You can see in my graphic that there is no space for the axis 
to display everything.

[image: Unbenannt.PNG]
Many thanks for your help

Greetings
Stefan


Meteo Oberwallis schrieb am Montag, 21. März 2022 um 19:50:43 UTC+1:

> Hello.
>
> Thank you. i have this Problem:
> pi@Wetterstation:~ $ sudo wee_reports
> Using configuration file /etc/weewx/weewx.conf
> Generating for all time
>
> Traceback (most recent call last):
>   File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
> obj.start()
>   File "/usr/share/weewx/weewx/reportengine.py", line 378, in start
> self.run()
>   File "/usr/share/weewx/weewx/imagegenerator.py", line 42, in run
> self.gen_images(self.gen_ts)
>   File "/usr/share/weewx/weewx/imagegenerator.py", line 107, in gen_images
> plot = self.gen_plot(plotgen_ts,
>   File "/usr/share/weewx/weewx/imagegenerator.py", line 270, in gen_plot
> new_data_vec_t = self.converter.convert(data_vec_t)
>   File "/usr/share/weewx/weewx/units.py", line 872, in convert
> new_unit_type = self.group_unit_dict.get(val_t[2], USUnits[val_t[2]])
>   File "/usr/lib/python3.9/collections/__init__.py", line 941, in 
> __getitem__
> return self.__missing__(key)# support subclasses that 
> define __missing__
>   File "/usr/lib/python3.9/collections/__init__.py", line 933, in 
> __missing__
> raise KeyError(key)
> KeyError: 'group_cpu_temp'
>
> Can you Help me?
>
> Thx
>
> vince schrieb am Montag, 21. März 2022 um 18:01:31 UTC+1:
>
>> Given this is really ancient dead code, I'd suggest you look into using 
>> https://github.com/weewx/weewx/wiki/cmon which is in the weewx core 
>> repos.
>>
>> On Monday, March 21, 2022 at 6:57:19 AM UTC-7 Meteo Oberwallis wrote:
>>
>>> Hello. 
>>> I know it's been a while since this thread, but it's still interesting 
>>> to me. Hence my question. Does this still work with the current weewx 
>>> version? I would like to expand this, but I keep getting an error 
>>> message. What I also don't quite understand is what "decide which 
>>> fields you want to record, and add them to the schemas.py file, following 
>>> the instructions in the "customizing weewx" documentation, section 5.1, 
>>> "Adding a new observation type" means. Can someone please explain to me 
>>> what exactly I should do to make it work? 
>>> Thanks and Greetings
>>> wbph...@gmail.com schrieb am Dienstag, 7. Mai 2013 um 19:13:25 UTC+2:
>>>
>>>> I am running weewx on a Raspberry Pi, and geek that I am, I wanted to 
>>>> collect some performance data. I read the doc and decided to add an 
>>>> extension to do this. Others may find this useful so I'm posting it here.
>>>>
>>>> I am currently collecting the following (field name, contents):
>>>>  "cpuUsagePercent" - OS Usage Percent - sum of all states except idle
>>>>  "cpuWaitPercent" - OS Wait Percent - time spent in wait
>>>>  "cpuLoadFactor" - OS Load Factor
>>>>  "cpuTemperature" - R-Pi Processor temperature
>>>>  "logErrors" - Log file errors
>>>>  "logOPErrors" - Log file Operational errors
>>>>  "logFTPErrors" - Log file FTP errors
>>>>  "logRFErrors" - Log file Restful errors
>>>>
>>>> With the exception of processor temperature (specific to the Raspberry 
>>>> Pi) the code should work on any hardware.
>>>>
>>>> The OS usage data comes from /proc/stat - see 
>>>> http://www.linuxhowtos.org/System/procstat.htm for an explanation.
>>>>
>>>> To install this extension:
>>>> 1) shutdown weewx
>>>> 2) decide which fields you want to record, and add them to the 
>>>> schemas.py file, following the instructions in the "customizing weewx" 
>>>> documentation, section 5.1, "Adding a new observation type"
>>>> 3) copy "cpustats.py" and "procstat.py" to your weewx bin/user folder 
>>>> and modify as needed
>>>> 4) edit your "weewx.conf" file and add "user.cpustats.CpuStats" to the 
>>>> front of the list of services - unless you've added other services, 
>>>> "

[weewx-user] Re: Extending weewx - collecting processor and OS statistics and graphing the data

[Meteo Oberwallis]

Good Morning.

Is it possible to adjust the sizes? As you can see in the picture, the 
resolution is displayed much too large. For example, if you could display 
the kB in MB? You can see in my graphic that there is no space for the axis 
to display everything.
Many thanks for your help

Greetings
Stefan
Meteo Oberwallis schrieb am Montag, 21. März 2022 um 19:50:43 UTC+1:

> Hello.
>
> Thank you. i have this Problem:
> pi@Wetterstation:~ $ sudo wee_reports
> Using configuration file /etc/weewx/weewx.conf
> Generating for all time
>
> Traceback (most recent call last):
>   File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
> obj.start()
>   File "/usr/share/weewx/weewx/reportengine.py", line 378, in start
> self.run()
>   File "/usr/share/weewx/weewx/imagegenerator.py", line 42, in run
> self.gen_images(self.gen_ts)
>   File "/usr/share/weewx/weewx/imagegenerator.py", line 107, in gen_images
> plot = self.gen_plot(plotgen_ts,
>   File "/usr/share/weewx/weewx/imagegenerator.py", line 270, in gen_plot
> new_data_vec_t = self.converter.convert(data_vec_t)
>   File "/usr/share/weewx/weewx/units.py", line 872, in convert
> new_unit_type = self.group_unit_dict.get(val_t[2], USUnits[val_t[2]])
>   File "/usr/lib/python3.9/collections/__init__.py", line 941, in 
> __getitem__
> return self.__missing__(key)# support subclasses that 
> define __missing__
>   File "/usr/lib/python3.9/collections/__init__.py", line 933, in 
> __missing__
> raise KeyError(key)
> KeyError: 'group_cpu_temp'
>
> Can you Help me?
>
> Thx
>
> vince schrieb am Montag, 21. März 2022 um 18:01:31 UTC+1:
>
>> Given this is really ancient dead code, I'd suggest you look into using 
>> https://github.com/weewx/weewx/wiki/cmon which is in the weewx core 
>> repos.
>>
>> On Monday, March 21, 2022 at 6:57:19 AM UTC-7 Meteo Oberwallis wrote:
>>
>>> Hello. 
>>> I know it's been a while since this thread, but it's still interesting 
>>> to me. Hence my question. Does this still work with the current weewx 
>>> version? I would like to expand this, but I keep getting an error 
>>> message. What I also don't quite understand is what "decide which 
>>> fields you want to record, and add them to the schemas.py file, following 
>>> the instructions in the "customizing weewx" documentation, section 5.1, 
>>> "Adding a new observation type" means. Can someone please explain to me 
>>> what exactly I should do to make it work? 
>>> Thanks and Greetings
>>> wbph...@gmail.com schrieb am Dienstag, 7. Mai 2013 um 19:13:25 UTC+2:
>>>
>>>> I am running weewx on a Raspberry Pi, and geek that I am, I wanted to 
>>>> collect some performance data. I read the doc and decided to add an 
>>>> extension to do this. Others may find this useful so I'm posting it here.
>>>>
>>>> I am currently collecting the following (field name, contents):
>>>>  "cpuUsagePercent" - OS Usage Percent - sum of all states except idle
>>>>  "cpuWaitPercent" - OS Wait Percent - time spent in wait
>>>>  "cpuLoadFactor" - OS Load Factor
>>>>  "cpuTemperature" - R-Pi Processor temperature
>>>>  "logErrors" - Log file errors
>>>>  "logOPErrors" - Log file Operational errors
>>>>  "logFTPErrors" - Log file FTP errors
>>>>  "logRFErrors" - Log file Restful errors
>>>>
>>>> With the exception of processor temperature (specific to the Raspberry 
>>>> Pi) the code should work on any hardware.
>>>>
>>>> The OS usage data comes from /proc/stat - see 
>>>> http://www.linuxhowtos.org/System/procstat.htm for an explanation.
>>>>
>>>> To install this extension:
>>>> 1) shutdown weewx
>>>> 2) decide which fields you want to record, and add them to the 
>>>> schemas.py file, following the instructions in the "customizing weewx" 
>>>> documentation, section 5.1, "Adding a new observation type"
>>>> 3) copy "cpustats.py" and "procstat.py" to your weewx bin/user folder 
>>>> and modify as needed
>>>> 4) edit your "weewx.conf" file and add "user.cpustats.CpuStats" to the 
>>>> front of the list of services - unless you've added other services, 
>>>> "service_list" should loo

[weewx-user] Re: Extending weewx - collecting processor and OS statistics and graphing the data

[Meteo Oberwallis]

Hello.

Thank you. i have this Problem:
pi@Wetterstation:~ $ sudo wee_reports
Using configuration file /etc/weewx/weewx.conf
Generating for all time
Traceback (most recent call last):
  File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
obj.start()
  File "/usr/share/weewx/weewx/reportengine.py", line 378, in start
self.run()
  File "/usr/share/weewx/weewx/imagegenerator.py", line 42, in run
self.gen_images(self.gen_ts)
  File "/usr/share/weewx/weewx/imagegenerator.py", line 107, in gen_images
plot = self.gen_plot(plotgen_ts,
  File "/usr/share/weewx/weewx/imagegenerator.py", line 270, in gen_plot
new_data_vec_t = self.converter.convert(data_vec_t)
  File "/usr/share/weewx/weewx/units.py", line 872, in convert
new_unit_type = self.group_unit_dict.get(val_t[2], USUnits[val_t[2]])
  File "/usr/lib/python3.9/collections/__init__.py", line 941, in 
__getitem__
return self.__missing__(key)# support subclasses that 
define __missing__
  File "/usr/lib/python3.9/collections/__init__.py", line 933, in 
__missing__
raise KeyError(key)
KeyError: 'group_cpu_temp'

Can you Help me?

Thx

vince schrieb am Montag, 21. März 2022 um 18:01:31 UTC+1:

> Given this is really ancient dead code, I'd suggest you look into using 
> https://github.com/weewx/weewx/wiki/cmon which is in the weewx core repos.
>
> On Monday, March 21, 2022 at 6:57:19 AM UTC-7 Meteo Oberwallis wrote:
>
>> Hello. 
>> I know it's been a while since this thread, but it's still interesting to 
>> me. Hence my question. Does this still work with the current weewx 
>> version? I would like to expand this, but I keep getting an error 
>> message. What I also don't quite understand is what "decide which fields 
>> you want to record, and add them to the schemas.py file, following the 
>> instructions in the "customizing weewx" documentation, section 5.1, "Adding 
>> a new observation type" means. Can someone please explain to me what 
>> exactly I should do to make it work? 
>> Thanks and Greetings
>> wbph...@gmail.com schrieb am Dienstag, 7. Mai 2013 um 19:13:25 UTC+2:
>>
>>> I am running weewx on a Raspberry Pi, and geek that I am, I wanted to 
>>> collect some performance data. I read the doc and decided to add an 
>>> extension to do this. Others may find this useful so I'm posting it here.
>>>
>>> I am currently collecting the following (field name, contents):
>>>  "cpuUsagePercent" - OS Usage Percent - sum of all states except idle
>>>  "cpuWaitPercent" - OS Wait Percent - time spent in wait
>>>  "cpuLoadFactor" - OS Load Factor
>>>  "cpuTemperature" - R-Pi Processor temperature
>>>  "logErrors" - Log file errors
>>>  "logOPErrors" - Log file Operational errors
>>>  "logFTPErrors" - Log file FTP errors
>>>  "logRFErrors" - Log file Restful errors
>>>
>>> With the exception of processor temperature (specific to the Raspberry 
>>> Pi) the code should work on any hardware.
>>>
>>> The OS usage data comes from /proc/stat - see 
>>> http://www.linuxhowtos.org/System/procstat.htm for an explanation.
>>>
>>> To install this extension:
>>> 1) shutdown weewx
>>> 2) decide which fields you want to record, and add them to the 
>>> schemas.py file, following the instructions in the "customizing weewx" 
>>> documentation, section 5.1, "Adding a new observation type"
>>> 3) copy "cpustats.py" and "procstat.py" to your weewx bin/user folder 
>>> and modify as needed
>>> 4) edit your "weewx.conf" file and add "user.cpustats.CpuStats" to the 
>>> front of the list of services - unless you've added other services, 
>>> "service_list" should look like this
>>> service_list = user.cpustats.CpuStats, 
>>> weewx.wxengine.StdConvert, weewx.wxengine.StdCalibrate, 
>>> weewx.wxengine.StdQC, weewx.wxengine.StdArchive, 
>>> weewx.wxengine.StdTimeSynch, 
>>> weewx.wxengine.StdPrint, weewx.wxengine.StdRESTful, weewx.wxengine.StdReport
>>> 5) restart weewx
>>>
>>> Once you've got it running and the data is being collected, the next 
>>> step is to add graphs in your skin.conf file. I can post examples of how to 
>>> do this if people want.
>>>
>>> You can see actual live data at http://www.meier-phelps.com/weather and 
>>> http://www.meier-phelps.com/OhloneFarm .
>>>
>>> I have found this to be very helpful in monitoring and tuning these 2 
>>> systems. In particular the IO Wait percent is a good indicator of SD card 
>>> health on the R-Pi.
>>>
>>> William
>>>
>>

-- 
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/061bb7fa-f4cb-4109-96fa-19b4ce0c5841n%40googlegroups.com.

[weewx-user] Re: Extending weewx - collecting processor and OS statistics and graphing the data

[Meteo Oberwallis]

Hello. 
I know it's been a while since this thread, but it's still interesting to 
me. Hence my question. Does this still work with the current weewx version? I 
would like to expand this, but I keep getting an error message. What I also 
don't quite understand is what "decide which fields you want to record, and 
add them to the schemas.py file, following the instructions in the 
"customizing weewx" documentation, section 5.1, "Adding a new observation 
type" means. Can someone please explain to me what exactly I should do to 
make it work? 
Thanks and Greetings
wbph...@gmail.com schrieb am Dienstag, 7. Mai 2013 um 19:13:25 UTC+2:

> I am running weewx on a Raspberry Pi, and geek that I am, I wanted to 
> collect some performance data. I read the doc and decided to add an 
> extension to do this. Others may find this useful so I'm posting it here.
>
> I am currently collecting the following (field name, contents):
>  "cpuUsagePercent" - OS Usage Percent - sum of all states except idle
>  "cpuWaitPercent" - OS Wait Percent - time spent in wait
>  "cpuLoadFactor" - OS Load Factor
>  "cpuTemperature" - R-Pi Processor temperature
>  "logErrors" - Log file errors
>  "logOPErrors" - Log file Operational errors
>  "logFTPErrors" - Log file FTP errors
>  "logRFErrors" - Log file Restful errors
>
> With the exception of processor temperature (specific to the Raspberry Pi) 
> the code should work on any hardware.
>
> The OS usage data comes from /proc/stat - see 
> http://www.linuxhowtos.org/System/procstat.htm for an explanation.
>
> To install this extension:
> 1) shutdown weewx
> 2) decide which fields you want to record, and add them to the schemas.py 
> file, following the instructions in the "customizing weewx" documentation, 
> section 5.1, "Adding a new observation type"
> 3) copy "cpustats.py" and "procstat.py" to your weewx bin/user folder and 
> modify as needed
> 4) edit your "weewx.conf" file and add "user.cpustats.CpuStats" to the 
> front of the list of services - unless you've added other services, 
> "service_list" should look like this
> service_list = user.cpustats.CpuStats, weewx.wxengine.StdConvert, 
> weewx.wxengine.StdCalibrate, weewx.wxengine.StdQC, 
> weewx.wxengine.StdArchive, weewx.wxengine.StdTimeSynch, 
> weewx.wxengine.StdPrint, weewx.wxengine.StdRESTful, weewx.wxengine.StdReport
> 5) restart weewx
>
> Once you've got it running and the data is being collected, the next step 
> is to add graphs in your skin.conf file. I can post examples of how to do 
> this if people want.
>
> You can see actual live data at http://www.meier-phelps.com/weather and 
> http://www.meier-phelps.com/OhloneFarm .
>
> I have found this to be very helpful in monitoring and tuning these 2 
> systems. In particular the IO Wait percent is a good indicator of SD card 
> health on the R-Pi.
>
> William
>

-- 
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/b7e96c1f-a855-4431-90bb-6a2ab4617e9dn%40googlegroups.com.

Re: [weewx-user] StdTimeSynch

[Meteo Oberwallis]

 Hello Tom 
Apparently that doesn't work for me. I did the following test. At 2:30 
p.m., the Raspi took the network away and restarted it. It starts up and 
then sets its time for the Vantage console, which was around 30 minutes 
before, i.e. 2:00 p.m. This of course also makes the data in the data 
logger unusable, since when the Raspi has the network and restarts, the 
console also sets the current time again. Maybe there is a problem with my 
weewx file because it still sets the time anew, even though it is in the 
past? 

tke...@gmail.com schrieb am Montag, 20. September 2021 um 16:23:55 UTC+2:

> Right now, weewxd sleeps until the clock time is greater than the 
> timestamp of its Python file. Is this not working for you?
>
> Perhaps a log demonstrating the problem?
>
> On Mon, Sep 20, 2021 at 6:49 AM Meteo Oberwallis  
> wrote:
>
>>
>> Hello, everyone. I have a question about time synchronization in Weewx. I 
>> use a Raspberry and the sync integration with my Vantage also works well. 
>> There's 
>> just one problem. If the Raspberry reaches an incorrect or no NTP, it 
>> also incorrectly adjusts the Vantage console, which then leads to a loss of 
>> data in the data logger. Couldn't a kind of back door be installed in 
>> the weewx.conf in the [StdTimeSynch] section? So that's how I make it up:
>>
>> [StdTimeSynch]
>>
>> # How often to check the weather station clock for drift (in seconds)
>> clock_check = 14400
>>
>> # How much it can drift before we will correct it (in seconds)
>> max_drift = 5
>> 
>> # Controll Date is Upper than
>>  date_controll > 2020
>>
>> By default, the date is set to 01.01.1970 if the Raspi does not reach the 
>> NTP. But if weewx now checks whether the date is higher than e.g. 2020, 
>> then you could prevent synchronization with the console. The reason for 
>> me is as follows. I have a watchdog running on the Raspi, which always 
>> checks whether a network connection is available. If this fails for a 
>> longer period of time, it restarts the Raspi. If, of course, the 
>> internet signal is not available, the Raspi starts with the standard date 
>> of 01/01/1970 and then sends this to the Davis console. This means that 
>> the recorded data in the data logger can no longer be used. Is this 
>> possible?
>>
>> Thanks
>> Stefan
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/03fb5587-b7ec-4134-9403-976685dafc70n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/03fb5587-b7ec-4134-9403-976685dafc70n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/1a993626-684e-40a1-8495-9ad16b24f8afn%40googlegroups.com.

[weewx-user] StdTimeSynch

[Meteo Oberwallis]

Hello, everyone. I have a question about time synchronization in Weewx. I 
use a Raspberry and the sync integration with my Vantage also works well. 
There's 
just one problem. If the Raspberry reaches an incorrect or no NTP, it also 
incorrectly adjusts the Vantage console, which then leads to a loss of data 
in the data logger. Couldn't a kind of back door be installed in the 
weewx.conf in the [StdTimeSynch] section? So that's how I make it up:

[StdTimeSynch]

# How often to check the weather station clock for drift (in seconds)
clock_check = 14400

# How much it can drift before we will correct it (in seconds)
max_drift = 5

# Controll Date is Upper than
 date_controll > 2020

By default, the date is set to 01.01.1970 if the Raspi does not reach the 
NTP. But if weewx now checks whether the date is higher than e.g. 2020, 
then you could prevent synchronization with the console. The reason for me 
is as follows. I have a watchdog running on the Raspi, which always checks 
whether a network connection is available. If this fails for a longer 
period of time, it restarts the Raspi. If, of course, the internet signal 
is not available, the Raspi starts with the standard date of 01/01/1970 and 
then sends this to the Davis console. This means that the recorded data in 
the data logger can no longer be used. Is this possible?

Thanks
Stefan

-- 
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/03fb5587-b7ec-4134-9403-976685dafc70n%40googlegroups.com.

[weewx-user] Sunshine Hours convert in hours

[Meteo Oberwallis]

 Hi Guys. I'm just adjusting my climate values. Now I wanted to display the 
hours of sunshine there as well. But since these are required in minutes, 
this is beyond the scope of the graphic. Couldn't the value of the sunshine 
duration be mathematically converted to hours and then displayed in the 
graphic? Or is there another option? thank you for your Help.

My Code:

[[Klima2020]]
title = "Jahr 2020"
type = spline
time_length = year_specific
year_specific = 2020
aggregate_type = max
aggregate_interval = 86400 # 1 day
gapsize = 8640
xaxis_groupby = month
xaxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 
'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
[[[outTemp]]]
zIndex = 2
name = Max Temperatur
color = "#fc0404"
marker
enabled = true
radius = 4
[[[outTemp_min]]]
name = Min Temperatur
observation_type = outTemp
aggregate_type = min
zIndex = 2
color = "#173c6a"
marker
enabled = true
radius = 4
[[[rainTotal]]]
name = Total Regen
type = column
yAxis = 1
zIndex = 0
color = "#438bd6"
[[[sunshine_hours]]]
type = column
yAxis = 1
zIndex = 0
aggregate_type = sum
color = "#e4d354"
name = Sunshine Hours

[image: Unbenannt.PNG]

-- 
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/9819a10d-1f70-40da-a8cb-0b13d6bcd0d3n%40googlegroups.com.

Re: [weewx-user] Re: Problem with Davis VP2 (Data logger or Konsole)?

[Meteo Oberwallis]

The error has now disappeared and I have also found out why this happens. 
If the console lost the connection to the outside, then the expansion had a 
problem because there was no value. That is why weewx was stopped.

Now it runs even after the data logger has been deleted and no data from the 
outdoor station is available.
What is the value 15 for? What does this mean?



Am Freitag, 15. Mai 2020 16:23:20 UTC+2 schrieb Tom Keffer:
>
> No, it is not good. But, the VP2 driver is used by hundreds, maybe 
> thousands of users. I'm sure it can be made to work.
>
> What happened after putting in the fix for the extension radiationhours?
>
> -tk
>
> On Fri, May 15, 2020 at 7:21 AM Meteo Oberwallis  > wrote:
>
>> Thx Tom. I hope, this failure its away. Its not good, when i must clear 
>> the Logger every Day.
>>
>> Am Freitag, 15. Mai 2020 16:10:26 UTC+2 schrieb Tom Keffer:
>>>
>>> Or, even simpler,
>>>
>>> tempe = event.record.get('outTemp', 15.0)
>>>
>>> -tk
>>>
>>> On Fri, May 15, 2020 at 7:04 AM Jacques Terrettaz  
>>> wrote:
>>>
>>>> Hi Meteo Oberwallis,
>>>>
>>>> Try to modify the script /usr/share/weewx/user/radiationhours.py as 
>>>> follow :
>>>>
>>>> Replace (in line 20 ?) :
>>>>
>>>> tempe = float(event.record.get('outTemp'))
>>>>
>>>> by
>>>>
>>>> tempe = event.record.get('outTemp')
>>>> if tempe is None:
>>>> tempe=15
>>>> -- 
>>>> 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/e23b1667-2355-4cfa-b554-55d8d0e9cd01%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/e23b1667-2355-4cfa-b554-55d8d0e9cd01%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> -- 
>> 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/6e52ed1a-ba10-49c1-a6eb-0492eccd664b%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/6e52ed1a-ba10-49c1-a6eb-0492eccd664b%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/7fe29475-b8a6-4832-b0ff-6d830c793a86%40googlegroups.com.

Re: [weewx-user] Re: Problem with Davis VP2 (Data logger or Konsole)?

[Meteo Oberwallis]

Thx Tom. I hope, this failure its away. Its not good, when i must clear the 
Logger every Day.

Am Freitag, 15. Mai 2020 16:10:26 UTC+2 schrieb Tom Keffer:
>
> Or, even simpler,
>
> tempe = event.record.get('outTemp', 15.0)
>
> -tk
>
> On Fri, May 15, 2020 at 7:04 AM Jacques Terrettaz  > wrote:
>
>> Hi Meteo Oberwallis,
>>
>> Try to modify the script /usr/share/weewx/user/radiationhours.py as 
>> follow :
>>
>> Replace (in line 20 ?) :
>>
>> tempe = float(event.record.get('outTemp'))
>>
>> by
>>
>> tempe = event.record.get('outTemp')
>> if tempe is None:
>> tempe=15
>>
>> -- 
>> 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/e23b1667-2355-4cfa-b554-55d8d0e9cd01%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/e23b1667-2355-4cfa-b554-55d8d0e9cd01%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/6e52ed1a-ba10-49c1-a6eb-0492eccd664b%40googlegroups.com.

[weewx-user] Re: Problem with Davis VP2 (Data logger or Konsole)?

[Meteo Oberwallis]

Hello Jacques

Ok. Its Work! Thank you. I will test this. 

def newArchiveRecord(self, event):
"""Gets called on a new archive record event."""
seuil = 0
tempe = event.record.get('outTemp')
if tempe is None: tempe=15
radiation = event.record.get('radiation')
event.record['sunshine_hours'] = 0.0
if radiation is not None:
utcdate = 
datetime.utcfromtimestamp(event.record.get('dateTime'))
dayofyear = 
int(time.strftime("%j",time.gmtime(event.record.get('dateTime'
theta = 360 * dayofyear / 365
equatemps = 0.0172 + 0.4281 * cos((pi / 180) * theta) - 7.3515 
* sin(
(pi / 180) * theta) - 3.3495 * cos(2 * (pi / 180) * theta) 
- 9.3619 * sin(
2 * (pi / 180) * theta)


Am Freitag, 15. Mai 2020 16:04:21 UTC+2 schrieb Jacques Terrettaz:
>
> Hi Meteo Oberwallis,
>
> Try to modify the script /usr/share/weewx/user/radiationhours.py as follow 
> :
>
> Replace (in line 20 ?) :
>
> tempe = float(event.record.get('outTemp'))
>
> by
>
> tempe = event.record.get('outTemp')
> if tempe is None:
> tempe=15
>

-- 
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/832aa004-abda-489a-824a-780599d9e61a%40googlegroups.com.

Re: [weewx-user] Problem with Davis VP2 (Data logger or Konsole)?

[Meteo Oberwallis]

Hello.

I have the problem that the reading stops at once. If I then check, this 
message always comes. As soon as I delete the archive memory from the data 
logger, weewx can be started again. I can rule out that the data logger is 
defective. After this procedure everything works again.

Am Freitag, 15. Mai 2020 14:13:35 UTC+2 schrieb Tom Keffer:
>
> It looks like your extension 'radationhours' is not prepared for the case 
> where outTemp is either missing from a record, or has a value of None. You 
> must check for these cases.
>
> Also, it should not be necessary to cast the value as a float: it's 
> already either a float, or None.
>
> As for why outTemp would be missing from the record, or have a value of 
> None, that's hard to say. It would depend on what processing has occurred 
> earlier in the engine pipeline.
>
> -tk
>
> On Thu, May 14, 2020 at 11:54 PM Meteo Oberwallis  > wrote:
>
>> Hello everbody.
>>
>> I have the following problem. The data readout of the Vantage Pro2 console 
>> worked without problems for a long time. But I've had this problem for a few 
>> weeks now. The solution then seems to be to delete the data logger (with 
>> wee_device --clear-memory) and restart weewx. 
>> Then it works for a while until this error occurs again. What could this be? 
>> If I understand that correctly, can't he read the data record from the 
>> logger?
>>
>>
>> May 15 08:43:16 raspberrypi systemd[1]: Starting LSB: weewx weather 
>> system...
>> May 15 08:43:27 raspberrypi weewx[4653]: engine: Initializing weewx 
>> version 3.9.1
>> May 15 08:43:27 raspberrypi weewx[4653]: engine: Using Python 2.7.13 
>> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
>> May 15 08:43:27 raspberrypi weewx[4653]: engine: Platform 
>> Linux-4.19.42-v7+-armv7l-with-debian-9.9
>> May 15 08:43:27 raspberrypi weewx[4653]: engine: Locale is 'de_CH.UTF-8'
>> May 15 08:43:27 raspberrypi weewx[4653]: engine: pid file is 
>> /var/run/weewx.pid
>> May 15 08:43:27 raspberrypi weewx[4639]: Starting weewx weather system: 
>> weewx.
>> May 15 08:43:27 raspberrypi systemd[1]: Started LSB: weewx weather system.
>> May 15 08:43:27 raspberrypi weewx[4657]: engine: Using configuration file 
>> /etc/weewx/weewx.conf
>> May 15 08:43:27 raspberrypi weewx[4657]: engine: Debug is 1
>> May 15 08:43:27 raspberrypi weewx[4657]: engine: Initializing engine
>> May 15 08:43:27 raspberrypi weewx[4657]: engine: Loading station type 
>> Vantage (weewx.drivers.vantage)
>> May 15 08:43:27 raspberrypi weewx[4657]: vantage: Driver version is 3.1.1
>> May 15 08:43:27 raspberrypi weewx[4657]: vantage: Opened up serial port 
>> /dev/ttyUSB0; baud 19200; timeout 4.00
>> May 15 08:43:27 raspberrypi weewx[4657]: vantage: Gentle wake up of 
>> console successful
>> May 15 08:43:27 raspberrypi weewx[4657]: vantage: Hardware type is 16
>> May 15 08:43:27 raspberrypi weewx[4657]: vantage: ISS ID is 1
>> May 15 08:43:27 raspberrypi weewx[4657]: vantage: Hardware name: Vantage 
>> Pro2
>> May 15 08:43:27 raspberrypi weewx[4657]: engine: Loading service 
>> weewx.engine.StdTimeSynch
>> May 15 08:43:27 raspberrypi weewx[4657]: engine: Finished loading service 
>> weewx.engine.StdTimeSynch
>> May 15 08:43:27 raspberrypi weewx[4657]: engine: Loading service 
>> user.cputemp.AddCpuTemp
>> May 15 08:43:27 raspberrypi weewx[4657]: engine: Finished loading service 
>> user.cputemp.AddCpuTemp
>> May 15 08:43:27 raspberrypi weewx[4657]: engine: Loading service 
>> user.radiationhours.RadiationHours
>> May 15 08:43:27 raspberrypi weewx[4657]: engine: Finished loading service 
>> user.radiationhours.RadiationHours
>> May 15 08:43:27 raspberrypi weewx[4657]: engine: Loading service 
>> weewx.engine.StdConvert
>> May 15 08:43:27 raspberrypi weewx[4657]: engine: StdConvert target unit 
>> is 0x1
>> May 15 08:43:27 raspberrypi weewx[4657]: engine: Finished loading service 
>> weewx.engine.StdConvert
>> May 15 08:43:27 raspberrypi weewx[4657]: engine: Loading service 
>> weewx.engine.StdCalibrate
>> May 15 08:43:27 raspberrypi weewx[4657]: engine: Finished loading service 
>> weewx.engine.StdCalibrate
>> May 15 08:43:27 raspberrypi weewx[4657]: engine: Loading service 
>> weewx.engine.StdQC
>> May 15 08:43:27 raspberrypi weewx[4657]: engine: Finished loading service 
>> weewx.engine.StdQC
>> May 15 08:43:27 raspberrypi weewx[4657]: engine: Loading service 
>> weewx.wxservices.StdWXCalculate
>> May 15 08:43:27 raspberrypi weewx[4657]: wxcalculate: The following 
>> values

[weewx-user] Problem with Davis VP2 (Data logger or Konsole)?

[Meteo Oberwallis]

Hello everbody.

I have the following problem. The data readout of the Vantage Pro2 console 
worked without problems for a long time. But I've had this problem for a few 
weeks now. The solution then seems to be to delete the data logger (with 
wee_device --clear-memory) and restart weewx. 
Then it works for a while until this error occurs again. What could this be? If 
I understand that correctly, can't he read the data record from the logger?


May 15 08:43:16 raspberrypi systemd[1]: Starting LSB: weewx weather 
system...
May 15 08:43:27 raspberrypi weewx[4653]: engine: Initializing weewx version 
3.9.1
May 15 08:43:27 raspberrypi weewx[4653]: engine: Using Python 2.7.13 
(default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
May 15 08:43:27 raspberrypi weewx[4653]: engine: Platform 
Linux-4.19.42-v7+-armv7l-with-debian-9.9
May 15 08:43:27 raspberrypi weewx[4653]: engine: Locale is 'de_CH.UTF-8'
May 15 08:43:27 raspberrypi weewx[4653]: engine: pid file is 
/var/run/weewx.pid
May 15 08:43:27 raspberrypi weewx[4639]: Starting weewx weather system: 
weewx.
May 15 08:43:27 raspberrypi systemd[1]: Started LSB: weewx weather system.
May 15 08:43:27 raspberrypi weewx[4657]: engine: Using configuration file 
/etc/weewx/weewx.conf
May 15 08:43:27 raspberrypi weewx[4657]: engine: Debug is 1
May 15 08:43:27 raspberrypi weewx[4657]: engine: Initializing engine
May 15 08:43:27 raspberrypi weewx[4657]: engine: Loading station type 
Vantage (weewx.drivers.vantage)
May 15 08:43:27 raspberrypi weewx[4657]: vantage: Driver version is 3.1.1
May 15 08:43:27 raspberrypi weewx[4657]: vantage: Opened up serial port 
/dev/ttyUSB0; baud 19200; timeout 4.00
May 15 08:43:27 raspberrypi weewx[4657]: vantage: Gentle wake up of console 
successful
May 15 08:43:27 raspberrypi weewx[4657]: vantage: Hardware type is 16
May 15 08:43:27 raspberrypi weewx[4657]: vantage: ISS ID is 1
May 15 08:43:27 raspberrypi weewx[4657]: vantage: Hardware name: Vantage 
Pro2
May 15 08:43:27 raspberrypi weewx[4657]: engine: Loading service 
weewx.engine.StdTimeSynch
May 15 08:43:27 raspberrypi weewx[4657]: engine: Finished loading service 
weewx.engine.StdTimeSynch
May 15 08:43:27 raspberrypi weewx[4657]: engine: Loading service 
user.cputemp.AddCpuTemp
May 15 08:43:27 raspberrypi weewx[4657]: engine: Finished loading service 
user.cputemp.AddCpuTemp
May 15 08:43:27 raspberrypi weewx[4657]: engine: Loading service 
user.radiationhours.RadiationHours
May 15 08:43:27 raspberrypi weewx[4657]: engine: Finished loading service 
user.radiationhours.RadiationHours
May 15 08:43:27 raspberrypi weewx[4657]: engine: Loading service 
weewx.engine.StdConvert
May 15 08:43:27 raspberrypi weewx[4657]: engine: StdConvert target unit is 
0x1
May 15 08:43:27 raspberrypi weewx[4657]: engine: Finished loading service 
weewx.engine.StdConvert
May 15 08:43:27 raspberrypi weewx[4657]: engine: Loading service 
weewx.engine.StdCalibrate
May 15 08:43:27 raspberrypi weewx[4657]: engine: Finished loading service 
weewx.engine.StdCalibrate
May 15 08:43:27 raspberrypi weewx[4657]: engine: Loading service 
weewx.engine.StdQC
May 15 08:43:27 raspberrypi weewx[4657]: engine: Finished loading service 
weewx.engine.StdQC
May 15 08:43:27 raspberrypi weewx[4657]: engine: Loading service 
weewx.wxservices.StdWXCalculate
May 15 08:43:27 raspberrypi weewx[4657]: wxcalculate: The following values 
will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
May 15 08:43:27 raspberrypi weewx[4657]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
May 15 08:43:27 raspberrypi weewx[4657]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate
May 15 08:43:27 raspberrypi weewx[4657]: engine: Loading service 
weewx.engine.StdArchive
May 15 08:43:27 raspberrypi weewx[4657]: engine: Archive will use data 
binding wx_binding
May 15 08:43:27 raspberrypi weewx[4657]: engine: Record generation will be 
attempted in 'hardware'
May 15 08:43:27 raspberrypi weewx[4657]: engine: Using archive interval of 
300 seconds (specified by hardware)
May 15 08:43:27 raspberrypi weewx[4657]: engine: Use LOOP data in hi/low 
calculations: 1
May 15 08:43:27 raspberrypi weewx[4657]: manager: Daily summary version is 
2.0
May 15 08:43:27 raspberrypi weewx[4657]: engine: Using binding 'wx_binding' 
to database 'weewx.sdb_new'
May 15 08:43:27 raspberrypi weewx[4657]: manager: Starting backfill of 
daily summaries
May 15 08:43:27 raspberrypi weewx[4657]: engine: Finished loading service 
weewx.engine.StdArchive
May 15 08:43:27 raspberrypi weewx[4657]: engine: Loading service 
weewx.restx.StdStationRegistry
May 15 08:43:27 raspberrypi weewx[

Re: [weewx-user] Re: sds011 install

[Meteo Oberwallis]

Thanks. Ist Work! I have another Question. How i can create an Graph with 
data. I must this new create?

Am Montag, 27. April 2020 10:38:45 UTC+2 schrieb steeple ian:
>
> Here is the logged issue: -
>
> https://github.com/matthewwall/weewx-sds011/issues/1
>
> On Mon, 27 Apr 2020 at 09:35, steeple ian  > wrote:
>
>> Hi,
>>
>> From memory that's on line 179. Just comment it out.
>> I have logged it as an issue.
>>
>> Ian
>>
>> On Mon, 27 Apr 2020 at 09:29, Meteo Oberwallis > > wrote:
>>
>>> Hello.
>>>
>>> I have the SDS011 install on weewx. Ist ok. But i have this false: Port 
>>> is already open. Can i help me? See the attachment.
>>>
>>> Thanks
>>> Stefan
>>>
>>>
>>>
>>> Am Donnerstag, 27. Juni 2019 06:21:14 UTC+2 schrieb mwall:
>>>>
>>>>
>>>>
>>>> On Wednesday, June 26, 2019 at 6:02:53 PM UTC-4, vigilancewx wrote:
>>>>>
>>>>> Do I make the install.py executable and run it 
>>>>>
>>>> no
>>>>
>>>>  
>>>>
>>>>> How do I complete the install
>>>>>
>>>>
>>>> in the weewx configuration file, add a 'driver' line to the SDS011 
>>>> stanza:
>>>>
>>>> [SDS011]
>>>> model = NovaPM
>>>> port = /dev/ttyUSB01
>>>> poll_interval = 10
>>>> driver = user.sds011
>>>>
>>>> you might have to modify the port, depending on how your device is 
>>>> connected.  optionally modify the model to match the branding of your 
>>>> sds011 hardware.
>>>>
>>>> the installer was not written correctly - it incorrectly cleared the 
>>>> SDS011 stanza after prompting for the information.  i have updated the 
>>>> sds011 package to 0.2 to fix this mistake.
>>>>
>>>> m 
>>>>
>>> -- 
>>> 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/fc8464c7-5ad6-469f-8508-acdbc74c8477%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/fc8464c7-5ad6-469f-8508-acdbc74c8477%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
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/8237f5f1-e9a3-4101-97a2-1a15b725fb64%40googlegroups.com.

[weewx-user] Re: sds011 install

[Meteo Oberwallis]

Hello.

I have the SDS011 install on weewx. Ist ok. But i have this false: Port is 
already open. Can i help me? See the attachment.

Thanks
Stefan



Am Donnerstag, 27. Juni 2019 06:21:14 UTC+2 schrieb mwall:
>
>
>
> On Wednesday, June 26, 2019 at 6:02:53 PM UTC-4, vigilancewx wrote:
>>
>> Do I make the install.py executable and run it 
>>
> no
>
>  
>
>> How do I complete the install
>>
>
> in the weewx configuration file, add a 'driver' line to the SDS011 stanza:
>
> [SDS011]
> model = NovaPM
> port = /dev/ttyUSB01
> poll_interval = 10
> driver = user.sds011
>
> you might have to modify the port, depending on how your device is 
> connected.  optionally modify the model to match the branding of your 
> sds011 hardware.
>
> the installer was not written correctly - it incorrectly cleared the 
> SDS011 stanza after prompting for the information.  i have updated the 
> sds011 package to 0.2 to fix this mistake.
>
> m 
>

-- 
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/fc8464c7-5ad6-469f-8508-acdbc74c8477%40googlegroups.com.

[weewx-user] Re: Force weewx to generate old monthly reports?

[Meteo Oberwallis]

I have found a mistake. I hadn't run the chain "wee_database --drop-daily" and 
"wee_database --rebuild-daily", and delete the data in the folder and 
subsequently "wee_reports". 
Delete the files in /var/www/html/weewx/folder Belchertown/NOAA/ and 
/var/www/html/weewx/NOAA/
That Works

Thx for Helping!



Am Sonntag, 19. April 2020 16:15:29 UTC+2 schrieb Andrew Milner:
>
> and what data is in the daily summary table eg archive_day_outTemp  for 
> dates in say december 2017 ???
> select * from archive_day_outTemp where dateTime < 1514764799; or 
> something like that
>
>
>
> On Sunday, 19 April 2020 16:58:26 UTC+3, Meteo Oberwallis wrote:
>>
>> Yes it was all newly created. Years 2017 - 2020 are available. But based on 
>> the kb size you can see that the files are empty
>>
>>
>>
>> Am Sonntag, 19. April 2020 15:55:32 UTC+2 schrieb Andrew Milner:
>>>
>>> The extract you showed was only for 2019 and 2020
>>>
>>> are there also new files for the other years / months, or are they 
>>> missing from the directory.
>>>
>>>
>>>
>>> On Sunday, 19 April 2020 16:38:13 UTC+3, Meteo Oberwallis wrote:
>>>>
>>>> Yes. The Data in the Folder are new (Screenshot)
>>>>
>>>> Am Sonntag, 19. April 2020 15:28:19 UTC+2 schrieb Andrew Milner:
>>>>>
>>>>> can you confirm that the noaa files beng displayed are the regenerated 
>>>>> files?  Do a directory listing and check the creation date of the files.
>>>>>
>>>>> did you dropped daily and rebuilt the daily tables?
>>>>>
>>>>> do the daily tables appear to contain the correct data (not the main 
>>>>> archive table but the daily summary tables)?
>>>>>
>>>>>
>>>>>
>>>>> On Sunday, 19 April 2020 16:16:41 UTC+3, Meteo Oberwallis wrote:
>>>>>>
>>>>>> Thx for the Answer. I've tried it a few times now. However, this 
>>>>>> does not work. The columns remain empty and no data is displayed
>>>>>>
>>>>>> You can see here: 
>>>>>> https://www.meteo-oberwallis.ch/wetter/bettmeralp/user/reports/
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Am Sonntag, 19. April 2020 15:13:10 UTC+2 schrieb Andrew Milner:
>>>>>>>
>>>>>>> if you delete the NOAA reports in /home/weewx/public_html/NOAA(or 
>>>>>>> /var/www/html/NOAA) they will be regenerated on the next report cycle.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sunday, 19 April 2020 16:02:02 UTC+3, Meteo Oberwallis wrote:
>>>>>>>>
>>>>>>>> Hello.
>>>>>>>>
>>>>>>>> Who i can found the Reports? Folder?
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> Am Samstag, 26. Mai 2018 16:00:58 UTC+2 schrieb bdf0506:
>>>>>>>>>
>>>>>>>>> I just imported about a year's worth of data from 
>>>>>>>>> WeatherUnderground into my database. Now, I would like to show the 
>>>>>>>>> reports.
>>>>>>>>>
>>>>>>>>> I ran "wee_database --drop-daily" and "wee_database 
>>>>>>>>> --rebuild-daily", followed by "wee_reports" in an attempt to generate 
>>>>>>>>> everything.
>>>>>>>>>
>>>>>>>>> At this point, the daily, weekly reports are fine. The monthly 
>>>>>>>>> report for May is fine. The yearly report for 2018 is fine.
>>>>>>>>>
>>>>>>>>> I am missing:
>>>>>>>>> All months other than May 2018
>>>>>>>>> The year 2017.
>>>>>>>>>
>>>>>>>>> I know that I have data in my database for these, but it seems 
>>>>>>>>> like I need to force these reports to be generated. How can I go 
>>>>>>>>> about this?
>>>>>>>>>
>>>>>>>>

-- 
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/b050ce51-7c15-4984-aea5-db8834cf3bec%40googlegroups.com.

[weewx-user] Re: Force weewx to generate old monthly reports?

[Meteo Oberwallis]

Yes it was all newly created. Years 2017 - 2020 are available. But based on the 
kb size you can see that the files are empty



Am Sonntag, 19. April 2020 15:55:32 UTC+2 schrieb Andrew Milner:
>
> The extract you showed was only for 2019 and 2020
>
> are there also new files for the other years / months, or are they missing 
> from the directory.
>
>
>
> On Sunday, 19 April 2020 16:38:13 UTC+3, Meteo Oberwallis wrote:
>>
>> Yes. The Data in the Folder are new (Screenshot)
>>
>> Am Sonntag, 19. April 2020 15:28:19 UTC+2 schrieb Andrew Milner:
>>>
>>> can you confirm that the noaa files beng displayed are the regenerated 
>>> files?  Do a directory listing and check the creation date of the files.
>>>
>>> did you dropped daily and rebuilt the daily tables?
>>>
>>> do the daily tables appear to contain the correct data (not the main 
>>> archive table but the daily summary tables)?
>>>
>>>
>>>
>>> On Sunday, 19 April 2020 16:16:41 UTC+3, Meteo Oberwallis wrote:
>>>>
>>>> Thx for the Answer. I've tried it a few times now. However, this does 
>>>> not work. The columns remain empty and no data is displayed
>>>>
>>>> You can see here: 
>>>> https://www.meteo-oberwallis.ch/wetter/bettmeralp/user/reports/
>>>>
>>>>
>>>>
>>>>
>>>> Am Sonntag, 19. April 2020 15:13:10 UTC+2 schrieb Andrew Milner:
>>>>>
>>>>> if you delete the NOAA reports in /home/weewx/public_html/NOAA(or 
>>>>> /var/www/html/NOAA) they will be regenerated on the next report cycle.
>>>>>
>>>>>
>>>>>
>>>>> On Sunday, 19 April 2020 16:02:02 UTC+3, Meteo Oberwallis wrote:
>>>>>>
>>>>>> Hello.
>>>>>>
>>>>>> Who i can found the Reports? Folder?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Am Samstag, 26. Mai 2018 16:00:58 UTC+2 schrieb bdf0506:
>>>>>>>
>>>>>>> I just imported about a year's worth of data from WeatherUnderground 
>>>>>>> into my database. Now, I would like to show the reports.
>>>>>>>
>>>>>>> I ran "wee_database --drop-daily" and "wee_database 
>>>>>>> --rebuild-daily", followed by "wee_reports" in an attempt to generate 
>>>>>>> everything.
>>>>>>>
>>>>>>> At this point, the daily, weekly reports are fine. The monthly 
>>>>>>> report for May is fine. The yearly report for 2018 is fine.
>>>>>>>
>>>>>>> I am missing:
>>>>>>> All months other than May 2018
>>>>>>> The year 2017.
>>>>>>>
>>>>>>> I know that I have data in my database for these, but it seems like 
>>>>>>> I need to force these reports to be generated. How can I go about this?
>>>>>>>
>>>>>>

-- 
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/6205fed6-833e-400a-8721-389205848090%40googlegroups.com.

[weewx-user] Re: Force weewx to generate old monthly reports?

[Meteo Oberwallis]

Yes. The Data in the Folder are new (Screenshot)

Am Sonntag, 19. April 2020 15:28:19 UTC+2 schrieb Andrew Milner:
>
> can you confirm that the noaa files beng displayed are the regenerated 
> files?  Do a directory listing and check the creation date of the files.
>
> did you dropped daily and rebuilt the daily tables?
>
> do the daily tables appear to contain the correct data (not the main 
> archive table but the daily summary tables)?
>
>
>
> On Sunday, 19 April 2020 16:16:41 UTC+3, Meteo Oberwallis wrote:
>>
>> Thx for the Answer. I've tried it a few times now. However, this does 
>> not work. The columns remain empty and no data is displayed
>>
>> You can see here: 
>> https://www.meteo-oberwallis.ch/wetter/bettmeralp/user/reports/
>>
>>
>>
>>
>> Am Sonntag, 19. April 2020 15:13:10 UTC+2 schrieb Andrew Milner:
>>>
>>> if you delete the NOAA reports in /home/weewx/public_html/NOAA(or 
>>> /var/www/html/NOAA) they will be regenerated on the next report cycle.
>>>
>>>
>>>
>>> On Sunday, 19 April 2020 16:02:02 UTC+3, Meteo Oberwallis wrote:
>>>>
>>>> Hello.
>>>>
>>>> Who i can found the Reports? Folder?
>>>>
>>>> Thanks
>>>>
>>>> Am Samstag, 26. Mai 2018 16:00:58 UTC+2 schrieb bdf0506:
>>>>>
>>>>> I just imported about a year's worth of data from WeatherUnderground 
>>>>> into my database. Now, I would like to show the reports.
>>>>>
>>>>> I ran "wee_database --drop-daily" and "wee_database --rebuild-daily", 
>>>>> followed by "wee_reports" in an attempt to generate everything.
>>>>>
>>>>> At this point, the daily, weekly reports are fine. The monthly report 
>>>>> for May is fine. The yearly report for 2018 is fine.
>>>>>
>>>>> I am missing:
>>>>> All months other than May 2018
>>>>> The year 2017.
>>>>>
>>>>> I know that I have data in my database for these, but it seems like I 
>>>>> need to force these reports to be generated. How can I go about this?
>>>>>
>>>>

-- 
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/83ab675e-e099-46c4-baf5-a84bcbbff68c%40googlegroups.com.

[weewx-user] Re: Force weewx to generate old monthly reports?

[Meteo Oberwallis]

Thx for the Answer. I've tried it a few times now. However, this does not 
work. The columns remain empty and no data is displayed

You can see here: 
https://www.meteo-oberwallis.ch/wetter/bettmeralp/user/reports/




Am Sonntag, 19. April 2020 15:13:10 UTC+2 schrieb Andrew Milner:
>
> if you delete the NOAA reports in /home/weewx/public_html/NOAA(or 
> /var/www/html/NOAA) they will be regenerated on the next report cycle.
>
>
>
> On Sunday, 19 April 2020 16:02:02 UTC+3, Meteo Oberwallis wrote:
>>
>> Hello.
>>
>> Who i can found the Reports? Folder?
>>
>> Thanks
>>
>> Am Samstag, 26. Mai 2018 16:00:58 UTC+2 schrieb bdf0506:
>>>
>>> I just imported about a year's worth of data from WeatherUnderground 
>>> into my database. Now, I would like to show the reports.
>>>
>>> I ran "wee_database --drop-daily" and "wee_database --rebuild-daily", 
>>> followed by "wee_reports" in an attempt to generate everything.
>>>
>>> At this point, the daily, weekly reports are fine. The monthly report 
>>> for May is fine. The yearly report for 2018 is fine.
>>>
>>> I am missing:
>>> All months other than May 2018
>>> The year 2017.
>>>
>>> I know that I have data in my database for these, but it seems like I 
>>> need to force these reports to be generated. How can I go about this?
>>>
>>

-- 
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/9966be63-bc8a-4061-b921-86406465134a%40googlegroups.com.

[weewx-user] Re: Force weewx to generate old monthly reports?

[Meteo Oberwallis]

Hello.

Who i can found the Reports? Folder?

Thanks

Am Samstag, 26. Mai 2018 16:00:58 UTC+2 schrieb bdf0506:
>
> I just imported about a year's worth of data from WeatherUnderground into 
> my database. Now, I would like to show the reports.
>
> I ran "wee_database --drop-daily" and "wee_database --rebuild-daily", 
> followed by "wee_reports" in an attempt to generate everything.
>
> At this point, the daily, weekly reports are fine. The monthly report for 
> May is fine. The yearly report for 2018 is fine.
>
> I am missing:
> All months other than May 2018
> The year 2017.
>
> I know that I have data in my database for these, but it seems like I need 
> to force these reports to be generated. How can I go about this?
>

-- 
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/aa4fd564-480d-410c-a295-ec4821e34090%40googlegroups.com.

[weewx-user] Re: Datenbank zusammen legen.

[Meteo Oberwallis]

Hello.
I have now deleted the data in the folder "/var/www/html/weewx/NOAA/". These 
came again after the next interval. Unfortunately without data. Do I have to 
delete it anywhere else?
Thank you for your top help



Am Freitag, 17. April 2020 23:42:39 UTC+2 schrieb 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/51a377a9-90e0-4bc6-81cf-997c1664c90a%40googlegroups.com.

[weewx-user] Re: Datenbank zusammen legen.

[Meteo Oberwallis]

Hallo Günther.

Hast du mal probiert, in der csv.conf die Oprion "conf" anstatt der Option 
"derive" zu nehmen. Das hat bei mir die Lösung gebracht. Auch habe ich 
bemerkt, das man nicht mehr Daten als ein halbes Jahr am Stück hochladen 
sollte. 6 Monate ergeben ca. 23 MB. Das hält das System noch aus. Alles was 
länger ist kann zu Problemen führen. Ich habe 45 Systeme am laufen. 4 sind 
jetzt Offline. Leider. Ich habe überall den Teamviewer am laufen. Das 
erleichtert die Sachen zum hin und her schieben.

Gruss
Stefan

Am Donnerstag, 16. April 2020 14:04:55 UTC+2 schrieb Günther Wrana:
>
> Hello Gary
>
> Yes, it is displayed, but with these two it stops.
>
> Checking record: 41000; Timestamp: 2019-11-09 12:50:00 CET (1573300200))
>
> Thanks Günther
>
> Am Donnerstag, 16. April 2020 13:52:05 UTC+2 schrieb gjr80:
>>
>> Hallo Günther, 
>>
>> So there are definitely some to fix. —fix-strings will work through every 
>> archive record and then every column in each record so it may take while. 
>> Many factors affect how long it will take. You should see a progress 
>> message on screen saying how many records have been checked and what 
>> timestamp —fix-strings is up to. This message updates every 1000 records 
>> processed. Does that update message not appear? 
>>
>> 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/3e166bdc-ab38-40dc-87ed-c8beb34909ca%40googlegroups.com.

[weewx-user] Re: Datenbank zusammen legen.

[Meteo Oberwallis]

Hallo.

Ich mache mittlerweile Jahres Daten und lade das so hoch. Dies klappt, 
dauert aber rund 3-4 Stunden pro Jahr. Die csv hat dann bei mir rund 24 MB. 
Leider muss man eine neue Spalte "timestamp" machen, da es sonst nicht 
klappt.

Gruss Stefan

Am Mittwoch, 15. April 2020 13:18:55 UTC+2 schrieb Günther Wrana:
>
> Hallo
>
> hast du die ganze 2MB csv auf einmal in die Datenbank gespielt?
> Mit all den Daten und in der Konfiguration?
>
> Grüße Günther
>
> Am Mittwoch, 15. April 2020 07:02:07 UTC+2 schrieb Meteo Oberwallis:
>>
>> Hello.
>>
>> I was now able to retroactively import my data into weewx. It worked 
>> wonderfully. Now I have another question. 
>> After I have written the data into the database, I have to execute another 
>> command so that it is also on the homepage, so. e.g. in Belchertown under 
>> "Reports"? So far nothing is there, not even after midnight.
>>
>> Thanks
>>
>>
>>
>> Am Dienstag, 14. April 2020 20:44:55 UTC+2 schrieb William Burton:
>>>
>>> Hallo Günther,
>>>
>>> Gary and many others have much more experience with this than myself but 
>>> since I saw a few issues, thought I would reply before it becomes too late 
>>> for you.
>>>
>>> It looks like you changed the CSV file to use the Meteo export file 
>>> instead of the raw data file which is a good idea. I tried to find where it 
>>> was documented but was not successful.
>>>
>>>
>>>

-- 
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/c8757003-b504-489a-8107-b72ac22ac536%40googlegroups.com.

[weewx-user] Re: Datenbank zusammen legen.

[Meteo Oberwallis]

Hello.

I was now able to retroactively import my data into weewx. It worked 
wonderfully. Now I have another question. 
After I have written the data into the database, I have to execute another 
command so that it is also on the homepage, so. e.g. in Belchertown under 
"Reports"? So far nothing is there, not even after midnight.

Thanks



Am Dienstag, 14. April 2020 20:44:55 UTC+2 schrieb William Burton:
>
> Hallo Günther,
>
> Gary and many others have much more experience with this than myself but 
> since I saw a few issues, thought I would reply before it becomes too late 
> for you.
>
> It looks like you changed the CSV file to use the Meteo export file 
> instead of the raw data file which is a good idea. I tried to find where it 
> was documented but was not successful.
>
>
>

-- 
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/ebf5a617-660b-4854-a028-1b55c782261c%40googlegroups.com.

[weewx-user] Re: Datenbank zusammen legen.

[Meteo Oberwallis]

Hello Andrew.

Thank you for your message. What do you mean exactly? Sorry for the question, 
but this is completely new.
What exactly do I have to do and where do I have to adjust it?

Thank you for your help



Am Montag, 13. April 2020 15:16:59 UTC+2 schrieb Andrew Milner:
>
> Your csv file does not contain a field call timestamp, which your .conf 
> file says should be imported to dateTime.  You need to combine Datum and 
> Zeit into a field called timestamp, and then tell wee_import the format of 
> that field.
>
>
>
> On Monday, 13 April 2020 14:28:58 UTC+3, Meteo Oberwallis wrote:
>>
>> Hello.
>>
>> I have now worked exactly according to the instructions. Unfortunately I 
>> always get the same error message when importing the data. I have the 
>> relevant data as an attachment here.
>>
>> wee_import --import-config=/var/tmp/csv.conf --dry-run
>> Starting wee_import...
>> A CSV import from source file '/home/pi/Desktop/EXP09_17.csv' has been 
>> requested.
>> Using database binding 'wx_binding', which is bound to database 
>> 'weewx.sdb_new'
>> Destination table 'archive' unit system is '0x01' (US).
>> Missing derived observations will be calculated.
>> This is a dry run, imported data will not be saved to archive.
>>  Unable to map source data.
>>  Field 'timestamp' not found in source data.
>>  Nothing done, exiting.
>>
>> Can someone help me please?
>> Thx
>>
>>
>>
>> Am Montag, 13. April 2020 01:36:35 UTC+2 schrieb gjr80:
>>>
>>> Hallo Günther,
>>>
>>> Now I have to know something else. you talk about adapting the 
>>>> wee_import? How does that work? 
>>>>
>>>
>>> How wee_import processes/interprets your data is controlled by the 
>>> import config file. As Bill points out there is a template CSV import 
>>> config file provided with WeeWX, you will find it at 
>>> /home/weewx/util/import/csv-example.conf or 
>>> /etc/weewx/import/csv-example.conf depending on your WeeWX install type.
>>>
>>> I also wanted to ask because I didn't quite understand it with rain. 
>>>> WeeWX needs the cumulative amount of rain. Wouldn't it be easier if I 
>>>> simply deleted all other rain data from the table? 
>>>>
>>>
>>> You can certainly delete the other rain columns in your import data if 
>>> you want but there is no need, wee_import will only import data in the 
>>> columns included in the field map ([[FieldMap]] stanza in the import 
>>> config file) and all other columns are ignored (there is likely a small 
>>> processing overhead for having the extra unused columns included but I 
>>> expect this overhead would be negligible). 
>>>  
>>>
>>>> And the last question. You wrote that (--dry-run) can be used to test 
>>>> whether everything is ok. How should I do that?
>>>>
>>>
>>> When you run wee_import you can add the --dry-run option to the command 
>>> line to run the import but any saves to your archive are skipped, so in 
>>> effect the import runs as normal (as configured in you import config file) 
>>> but your database is left untouched. Have a read of Option --dry-run 
>>> <http://weewx.com/docs/utilities.htm#Option_--dry-run> in the Utilities 
>>> Guide.
>>>  
>>>
>>>> Sorry for the many questions. But is not quite clear ;-)
>>>>
>>>
>>> No problems, most of what you want to know is covered in the wee_import 
>>> section <http://weewx.com/docs/utilities.htm#wee_import_utility> of the 
>>> Utilities Guide. You are interested in a CSV import whereas the 
>>> wee_import section of the Utilities Guide covers imports from other 
>>> sources (Weatherunderground, Cumulus etc) as well. You can skip these 
>>> sections paying attention only to the Actions and options section 
>>> <http://weewx.com/docs/utilities.htm#Actions_and_options31> and the CSV 
>>> specific sections here <http://weewx.com/docs/utilities.htm#General> 
>>> and here <http://weewx.com/docs/utilities.htm#Importing_from_CSV_files>.
>>>  
>>> If language is a problem or you just don't follow, let me know and I 
>>> will put together a suitable import config file for you.
>>>
>>> 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/929212a2-9153-4f78-b265-494930c244a4%40googlegroups.com.

[weewx-user] Re: Datenbank zusammen legen.

[Meteo Oberwallis]

Hello Gary.

First of all, thank you for exploring the cvs file. Sounds good that you 
can import and save them. Now I have to know something else. you talk about 
adapting the wee_import? How does that work? I also wanted to ask because I 
didn't quite understand it with rain. Weewx needs the cumulative amount of 
rain. Wouldn't it be easier if I simply deleted all other rain data from 
the table? And the last question. You wrote that (--dry-run) can be used to 
test whether everything is ok. How should I do that? Sorry for the many 
questions. But is not quite clear ;-)

Many thanks and best regards

Am Sonntag, 12. April 2020 01:12:08 UTC+2 schrieb gjr80:
>
> Hallo Günther,
>
> A few observations on your data:
>
> 1. The column names can be whatever you want, the only requirements are 
> they are unique and you can enter them in the [[FieldMap]] 
>  portion of the import 
> config file. In theory, your German field names should work but all we need 
> is some sort of unicode failure somewhere in the processing chain and the 
> import will fail. If it were me I would remove the units in brackets and 
> try the import with your fields names via a dry run (using --dry-run). 
> That will show you if it will fail without affecting your WeeWX data.
>
> 2. You will need to remove the 'M' from the Intervall field.
>
> 3. WeeWX records rain on a per-interval basis whereas your rain data is 
> cumulative. That is fine, wee_import can do the calculations but you need 
> to tell wee_import your rain data is cumulative and you need to select 
> one of the rain fields to use (you have five). I would use the longest 
> period rain field, in your case Gesamter Niederschlag. So in your import 
> config file you will need (untested):
>
> rain = cumulative
>
> and in your field map:
>
> rain = 'Gesamter Niederschlag', mm
>
> 4. Your Zeit (date-time) field format is fine, no need for a unix epoch 
> timestamp, wee_import will do that provided you come up with a suitable 
> date-time format string that wee_import can use to recognise the 
> different portions of the date-time. This is covered by the 
> raw_datetime_format setting in the import config file, the wee_import 
> section  of 
> the Utilities Guide explains it's use. in your case I suspect that 
> '%d.%m.%Y  %H:%M:%S' will do the job (untested). Again the dry run should 
> be used to check.
>
> Gary
>
> On Saturday, 11 April 2020 16:57:00 UTC+10, Günther Wrana wrote:
>>
>> Hello,
>>
>> I would have my .csv file here that I would like to import. How should it 
>> look like? Do I have to insert the column names listed in the documentation 
>> in the header?
>>
>> Time,Temp,Dewpoint,Press,WindDir,WindSpeed,WindGust,Hum,dailyrain,SolarRad
>>
>> Date and time are in one column, do they also have to have this UNIX date 
>> format?
>>
>> 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/78603ea8-8144-4fb6-8977-f10fb00ea057%40googlegroups.com.

[weewx-user] Re: Datenbank zusammen legen.

[Meteo Oberwallis]

Hallo Günther.

Darf ich dich fragen, ob du vorher auch mal WsWin benutzt hast? Ich habe 
wetterdaten seit 2005, welche aber natürlich jetzt in weewx fehlen. Es 
müsste doch möglich sein, die von WsWin erstellten Monatsdateien, also .csv 
in die weewx Datenbank zu implementieren? Das wäre natürlich genial. 
anonsten verliere ich die ganzen jahre.

Gruss und danke für eure Hilfe

Am Freitag, 10. April 2020 08:25:51 UTC+2 schrieb Günther Wrana:
>
> Hallo
>
> bei mir hat das dann funktioniert nach dem ich die alte Datenbank so wie 
> oben beschrieben in eine .sql Datenbank umgewandelt habe.
>
> *sqlite3 db3.sdb*
> sqlite> *.output db3.sql*
> sqlite> *.dump archive*
> sqlite> *.quit*
>
> und danach haben sich die beiden Datenbanken zusammmen legen lassen.
>
> Fehlermeldungen sind auch bei mir gekommen nur wenn man am Schluss die 
> Datenbank mit dem checkt.
>
> *sqlite3 db3.sdb*
> sqlite> *pragma integrity_check;*
>
> und es O.K ausgibt dann passt das.
>
> Grüße Günther 
>
>
>
> Am Donnerstag, 9. April 2020 11:14:57 UTC+2 schrieb Meteo Oberwallis:
>>
>> Hallo zusammen.
>>
>> Ich wollte ebenfalls meine beiden .sdb Datenbanken zusammenlegen. Sie 
>> stammen beide aus weewx. Nun bekomme ich immer diese Fehlermeldung:
>>
>> root@raspberrypi:~# sqlite3 weewx.sdb_new_new
>> SQLite version 3.16.2 2017-01-06 16:32:41
>> Enter ".help" for usage hints.
>> sqlite> .read weewx.sdb_new
>> Error: cannot open "weewx.sdb_new"
>> sqlite> .read /home/pi/Desktop/weewx.sdb_new
>> Error: near line 1: near "SQLite": syntax error
>> Error: near line 403: unrecognized token: " "
>> Error: near line 5261: near "@n�": syntax error
>> Error: near line 5337: unrecognized token: " "
>> Error: near line 6332: unrecognized token: " "
>> Error: near line 6793: unrecognized token: " "
>> Error: near line 7575: near "@rH": syntax error
>> Error: near line 7831: near "@n�": syntax error
>> sqlite> 
>>
>> Hatte das jemand auch?
>> Am Samstag, 4. Januar 2020 23:41:23 UTC+1 schrieb gjr80:
>>>
>>> Hallo Günther,
>>>
>>> Ihr Englisch ist wahrscheinlich besser als mein Deutsch, aber lassen Sie 
>>> uns sehen, wie wir gehen. Ich habe sowohl Englische als auch 
>>> Google-Deutsche Wörter eingefügt.
>>>
>>> Wenn ich das richtig verstehe, haben Sie zwei WeeWX SQLite-Datenbanken, 
>>> die Sie zusammenführen möchten. Leider gibt es im Utilities Guide nichts, 
>>> was Ihnen das leicht machen könnte. Dies ist ein paar Mal vorgekommen und 
>>> wenn Sie das Forum nach Beiträgen mit "merge sqlite datbase" durchsuchen, 
>>> werden Sie einige Beiträge finden, die Ihnen helfen werden. Ich würde 
>>> dieses versuchen (
>>> https://groups.google.com/d/msg/weewx-user/T2VuiIkcAEM/wZzemNzWknQJ) 
>>> und das ist das, was ich als Basis für das verwendet habe:
>>>
>>> 1. Erstellen Sie eine Sicherungskopie Ihrer beiden Datenbanken
>>>
>>> 2. Installieren Sie das Dienstprogramm sqlite3, falls es noch nicht 
>>> installiert ist:
>>>
>>> $ sudo apt-get install sqlite3
>>>
>>> 3. Wählen Sie eine Ihrer Datenbanken als endgültige Datenbank aus und 
>>> benennen Sie die andere in db1.sdb um. Sie sollten jetzt zwei Datenbanken 
>>> haben, eine mit dem Namen weewx.sdb und eine andere mit dem Namen db1.sdb. 
>>> Um die Dinge später zu vereinfachen, stellen Sie sicher, dass sich 
>>> weewx.sdb in dem Verzeichnis befindet, in dem Sie Ihre WeeWX-Datenbank 
>>> dauerhaft speichern möchten (die Standardverzeichnisse sind 
>>> /home/weewx/archive für eine setup.py-Installation oder /var/lib/weewx für 
>>> alle andere installiert). Ich werde /home/weewx/archive in dieser Anleitung 
>>> verwenden
>>>
>>> 4. Kopieren Sie die Datenbank db1.sdb in eine Datei:
>>>
>>> $ sqlite3 /path/to/db1.sdb
>>> sqlite> .output /var/tmp/db1.dump
>>> sqlite> .dump
>>> sqlite> .quit
>>>
>>> 5. Importieren Sie nun die gedumpten Daten in die endgültige Datenbank 
>>> weewx.sdb:
>>>
>>> $ sqlite3 /home/weewx/archive/weewx.sdb
>>> sqlite> .read /var/tmp/db1.dump
>>>
>>> Sie werden wahrscheinlich Beschwerden über 'existing tables' oder 
>>> 'unique constraint failed' sehen. Diese können ignoriert werden. Es muss 
>>> jedoch etwas Ernsthafteres betrachtet werden.
>>>
>>> sqlite> 

[weewx-user] Re: Datenbank zusammen legen.

[Meteo Oberwallis]

Hallo zusammen.

Ich wollte ebenfalls meine beiden .sdb Datenbanken zusammenlegen. Sie 
stammen beide aus weewx. Nun bekomme ich immer diese Fehlermeldung:

root@raspberrypi:~# sqlite3 weewx.sdb_new_new
SQLite version 3.16.2 2017-01-06 16:32:41
Enter ".help" for usage hints.
sqlite> .read weewx.sdb_new
Error: cannot open "weewx.sdb_new"
sqlite> .read /home/pi/Desktop/weewx.sdb_new
Error: near line 1: near "SQLite": syntax error
Error: near line 403: unrecognized token: " "
Error: near line 5261: near "@n�": syntax error
Error: near line 5337: unrecognized token: " "
Error: near line 6332: unrecognized token: " "
Error: near line 6793: unrecognized token: " "
Error: near line 7575: near "@rH": syntax error
Error: near line 7831: near "@n�": syntax error
sqlite> 

Hatte das jemand auch?
Am Samstag, 4. Januar 2020 23:41:23 UTC+1 schrieb gjr80:
>
> Hallo Günther,
>
> Ihr Englisch ist wahrscheinlich besser als mein Deutsch, aber lassen Sie 
> uns sehen, wie wir gehen. Ich habe sowohl Englische als auch 
> Google-Deutsche Wörter eingefügt.
>
> Wenn ich das richtig verstehe, haben Sie zwei WeeWX SQLite-Datenbanken, 
> die Sie zusammenführen möchten. Leider gibt es im Utilities Guide nichts, 
> was Ihnen das leicht machen könnte. Dies ist ein paar Mal vorgekommen und 
> wenn Sie das Forum nach Beiträgen mit "merge sqlite datbase" durchsuchen, 
> werden Sie einige Beiträge finden, die Ihnen helfen werden. Ich würde 
> dieses versuchen (
> https://groups.google.com/d/msg/weewx-user/T2VuiIkcAEM/wZzemNzWknQJ) und 
> das ist das, was ich als Basis für das verwendet habe:
>
> 1. Erstellen Sie eine Sicherungskopie Ihrer beiden Datenbanken
>
> 2. Installieren Sie das Dienstprogramm sqlite3, falls es noch nicht 
> installiert ist:
>
> $ sudo apt-get install sqlite3
>
> 3. Wählen Sie eine Ihrer Datenbanken als endgültige Datenbank aus und 
> benennen Sie die andere in db1.sdb um. Sie sollten jetzt zwei Datenbanken 
> haben, eine mit dem Namen weewx.sdb und eine andere mit dem Namen db1.sdb. 
> Um die Dinge später zu vereinfachen, stellen Sie sicher, dass sich 
> weewx.sdb in dem Verzeichnis befindet, in dem Sie Ihre WeeWX-Datenbank 
> dauerhaft speichern möchten (die Standardverzeichnisse sind 
> /home/weewx/archive für eine setup.py-Installation oder /var/lib/weewx für 
> alle andere installiert). Ich werde /home/weewx/archive in dieser Anleitung 
> verwenden
>
> 4. Kopieren Sie die Datenbank db1.sdb in eine Datei:
>
> $ sqlite3 /path/to/db1.sdb
> sqlite> .output /var/tmp/db1.dump
> sqlite> .dump
> sqlite> .quit
>
> 5. Importieren Sie nun die gedumpten Daten in die endgültige Datenbank 
> weewx.sdb:
>
> $ sqlite3 /home/weewx/archive/weewx.sdb
> sqlite> .read /var/tmp/db1.dump
>
> Sie werden wahrscheinlich Beschwerden über 'existing tables' oder 'unique 
> constraint failed' sehen. Diese können ignoriert werden. Es muss jedoch 
> etwas Ernsthafteres betrachtet werden.
>
> sqlite> .quit
>
> 6. Der nächste Schritt besteht darin, die täglichen Zusammenfassungen neu 
> zu erstellen. Dies erfolgt mit dem Dienstprogramm wee_database und 
> erfordert, dass Sie eine WeeWX-Datenbindung konfigurieren, um die jetzt 
> konsolidierte Datenbank weewx.sdb zu verwenden. Bearbeiten Sie die Datei 
> weewx.conf und suchen Sie die Zeilengruppe [Databases]. Überprüfen Sie, ob 
> Sie einen Datenbankeintrag für weewx.sdb haben. Dieser sollte ungefähr so 
> ​​aussehen:
>
> [Databases]
>
> # A SQLite database is simply a single file
> [[archive_sqlite]]
> database_name = weewx.sdb
> database_type = SQLite
>
> Wenn sich weewx.sdb in den Verzeichnissen home/weewx/archive oder 
> /var/lib/weewx befindet, ist das oben Genannte in Ordnung. Beachten Sie den 
> Eintrag in [[ ]], in diesem Fall archive_sqlite.
>
> Überprüfen Sie nun die Zeilengruppe [DataBindings] in der Datei weewx.conf.
>
> [DataBindings]
>
> [[wx_binding]]
> # The database must match one of the sections in [Databases].
> # This is likely to be the only option you would want to change.
> database = archive_sqlite
> # The name of the table within the database
> table_name = archive
> # The manager handles aggregation of data for historical summaries
> manager = weewx.wxmanager.WXDaySummaryManager
> # The schema defines the structure of the database.
> # It is *only* used when the database is created.
> schema = schemas.wview.schema
>
> Sie müssen überprüfen, ob die Datenbankeinstellung in der Zeilengruppe 
> [[wx_binding]] den Eintrag aus der Zeilengruppe [[ ]] verwendet, den wir 
> zuvor in der Zeilengruppe [Databases] notiert haben, in diesem Fall 
> archive_sqlite.
>
> Sie können nun mit wee_database die täglichen Zusammenfassungen löschen 
> und neu erstellen.
>
> 7. Legen Sie die täglichen Zusammenfassungen ab und erstellen Sie sie neu:
>
> $ wee_database --drop-daily
> $ wee_database --rebuild-daily
>
> Beantworten Sie die Aufforderungen nach Bedarf
>
> 8. Ihre konsolidierte D

[weewx-user] Re: Sunshine Time

[Meteo Oberwallis]

I have another question. Is it possible that the entire database can now be run 
once in order to have the hours of sun generated by the past? The graphics are 
not up to date right now because the 5min sun was displayed as 0.8 before 
renewal.



Am Freitag, 27. März 2020 13:17:34 UTC+1 schrieb Jacques Terrettaz:
>
> May be :
>
> #set minutes = int($day.sunshine_hours.sum.raw - ($hours*60))
>
>
>
> Le vendredi 27 mars 2020 13:14:05 UTC+1, Meteo Oberwallis a écrit :
>>
>> Hello.
>>
>> Thx. Thats Work! I have another Problem. 
>>
>> A coming point now appears at the minutes, which should not be there. How 
>> can I remove it?
>>
>>
>> 
>> 
>>
>> Thank you
>>
>> Am Freitag, 27. März 2020 12:49:17 UTC+1 schrieb Jacques Terrettaz:
>>>
>>>
>>> Hi,
>>> With this extension, the sunshine time is recorded as minutes.
>>>
>>> So in your case, to have the number of hours, you should divide the sum 
>>> by 60:
>>>
>>>  
>>> #set hours = int($day.sunshine_hours.sum.raw*/60*)  
>>> #set minutes = $day.sunshine_hours.sum.raw - ($hours*60)
>>>
>>> With a daily sum of 135 minutes , this give:
>>> hours = int(135/60) = 2
>>> minutes = 135-(2*60)= 15
>>>
>>> So 
>>>   should give now 2 h 15 m
>>>
>>>
>>>  
>>>
>>>

-- 
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/17329197-ab15-44b0-b122-d8a46a49792e%40googlegroups.com.

[weewx-user] Re: Sunshine Time

[Meteo Oberwallis]

Great. That’s it. thank you very much

Am Freitag, 27. März 2020 13:17:34 UTC+1 schrieb Jacques Terrettaz:
>
> May be :
>
> #set minutes = int($day.sunshine_hours.sum.raw - ($hours*60))
>
>
>
> Le vendredi 27 mars 2020 13:14:05 UTC+1, Meteo Oberwallis a écrit :
>>
>> Hello.
>>
>> Thx. Thats Work! I have another Problem. 
>>
>> A coming point now appears at the minutes, which should not be there. How 
>> can I remove it?
>>
>>
>> 
>> 
>>
>> Thank you
>>
>> Am Freitag, 27. März 2020 12:49:17 UTC+1 schrieb Jacques Terrettaz:
>>>
>>>
>>> Hi,
>>> With this extension, the sunshine time is recorded as minutes.
>>>
>>> So in your case, to have the number of hours, you should divide the sum 
>>> by 60:
>>>
>>>  
>>> #set hours = int($day.sunshine_hours.sum.raw*/60*)  
>>> #set minutes = $day.sunshine_hours.sum.raw - ($hours*60)
>>>
>>> With a daily sum of 135 minutes , this give:
>>> hours = int(135/60) = 2
>>> minutes = 135-(2*60)= 15
>>>
>>> So 
>>>   should give now 2 h 15 m
>>>
>>>
>>>  
>>>
>>>

-- 
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/57dea60c-91c0-4413-bfe4-4c988859fa1e%40googlegroups.com.

[weewx-user] Re: Sunshine Time

[Meteo Oberwallis]

Hello.

Thx. Thats Work! I have another Problem. 

A coming point now appears at the minutes, which should not be there. How can I 
remove it?





Thank you

Am Freitag, 27. März 2020 12:49:17 UTC+1 schrieb Jacques Terrettaz:
>
>
> Hi,
> With this extension, the sunshine time is recorded as minutes.
>
> So in your case, to have the number of hours, you should divide the sum by 
> 60:
>
>  
> #set hours = int($day.sunshine_hours.sum.raw*/60*)  
> #set minutes = $day.sunshine_hours.sum.raw - ($hours*60)
>
> With a daily sum of 135 minutes , this give:
> hours = int(135/60) = 2
> minutes = 135-(2*60)= 15
>
> So 
>   should give now 2 h 15 m
>
>
>  
>
>

-- 
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/e0178a79-ae3d-42e7-912d-b852da4669c4%40googlegroups.com.

[weewx-user] Re: Sunshine Time

[Meteo Oberwallis]

Hi there.
I have recently taken the template for the hours of sunshine from the example 
under. Now I have noticed that my sunshine time in the xml is no longer 
correct. I think it's because of the conversion?

The Result:








The Code:




#set hours = int($day.sunshine_hours.sum.raw)
#set minutes = int(($day.sunshine_hours.sum.raw - $hours)*60 + 0.5)


It is also said to divide the 130 minutes into hours and minutes. That means 
doing it with the existing code, but unfortunately it doesn't work anymore. Can 
someone help me?



Am Donnerstag, 14. November 2019 13:34:16 UTC+1 schrieb Jacques Terrettaz:
>
> I agree with peter's comment.
> The Davis solar radiation sensor, or any comparable sensor, is measuring a 
> global radiation ( direct + diffuse) and the surface of the sensor is 
> parallel to the ground.  A fixed threshold, such as 120 W/m2, can be used 
> only with sensors measuring direct radiation and that have their surface 
> always pointing to the sun (i.e surface of sensor is always perpendicular 
> to the axis sun-sensor).
> With a Davis solar sensor, applying a fixed threshold to estimate sunshine 
> duration give innacurate values. Why?  A simple example, taken from the 
> measurements of my Davis solar sensor, will make you understand:
> - On December 20, at 9:30, the sun was shining, and my solar sensor, in 
> full sun, measured 105 W / m2.
> - On June 11, at 10 am, the sky was cloudy, and my solar probe measured 
> 301 W / m2.
> How to choose a fixed threshold so that the sun of December with 105 W / 
> m2 is considered as sunny and that a radiation of 301W / m2 under a cloudy 
> sky of end of June is not considered as sunny?
> A measurement of the global solar radiation on a plane parallel to the 
> ground is very dependent on the elevation of the sun. This elevation 
> changes according to the time of day and according to the seasons.
> So with this type of solar sensors, a valid calculation of the sunshine 
> duration  can only be done with methods taking into account the elevation 
> of the sun at the time of the measurement, calculated according to the 
> latitude, longitude, date and the time of observation.
>
> Here is the weewx extension I am using, that I  modified from 
> https://github.com/brewster76/util-archer/blob/master/user/radiationhours.py 
>  by applying a formula developed by MeteoFrance to estimate sunshine 
> duration from Davis sensors. (
> https://forums.infoclimat.fr/f/topic/17151-calcul-duree-ensoleillement/?do=findComment&comment=1216053).
>  
>  The idea is to determine at each measurements a  threshold value that is 
> calculated depending on the date, time and geographic location (latitude 
> and longitude) of the sensor. If the measured solar radiation is higher 
> than the calculated threshold, the sunshine duration for this measurement 
> will be equal to the archive interval, otherwise it will be 0.
>
> """
> Adds a new observation field to weewx: [sunshine_time]
> Installation:
> 1. Save this file to your user customisations directory (which is often 
> /usr/share/weewx/user)
> 2. Enable this service in weewx.conf by adding 
> user.sunduration.SunshineDuration to the process_services list.
> [Engine]
> [[Services]]
> # This section specifies the services that should be run. 
> They are
> # grouped by type, and the order of services within each group
> # determines the order in which the services will be run.
> prep_services = weewx.engine.StdTimeSynch
> process_services = user.sunduration.SunshineDuration, 
> weewx.engine.StdConvert, weewx.engine.StdCalibrate, weewx.engine.StdQC, 
> weewx.wxservices.StdWXCalculate
> 3. Add [sunshine_time] to the database schema so tables include this new 
> observation field.
>In weewx.conf, change the wx_binding schema from schemas.wview.schema 
> to user.sunduration.schema_with_sunshine_time
> [DataBindings]
> [[wx_binding]]
> # The database must match one of the sections in [Databases].
> # This is likely to be the only option you would want to 
> change.
> database = archive_sqlite
> # The name of the table within the database
> table_name = archive
> # The manager handles aggregation of data for historical 
> summaries
> manager = weewx.wxmanager.WXDaySummaryManager
> # The schema defines the structure of the database.
> # It is *only* used when the database is created.
> #schema = schemas.wview.schema
> schema = user.sunduration.schema_with_sunshine_time
> 4. Shutdown Weewx and update your database to bring in the new field.
>wee_database weewx.conf --reconfigure
>Make sure you know what you're doing at this point, you can

[weewx-user] Re: how to insert additional data (cpu temp) into skins?

[Meteo Oberwallis]

Am Donnerstag, 26. März 2020 17:42:14 UTC+1 schrieb Mike Revitt:
> O have worked out how to get the CPU frequency which sort of helps, but would 
> need to look into this
> 
> On Thursday, March 26, 2020 at 4:09:05 PM UTC, Meteo Oberwallis wrote:Hello.
> Is it also possible to read out the CPU load from the Raspberry and write it 
> to the database?

Sounds good ;-) 

-- 
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/31b231b1-1b76-4660-adb3-f1c9e62c64d4%40googlegroups.com.

[weewx-user] Re: how to insert additional data (cpu temp) into skins?

[Meteo Oberwallis]

Hello.
Is it also possible to read out the CPU load from the Raspberry and write it to 
the database?

-- 
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/d724ca81-fd6e-49e9-8ba3-6ed1ab9ffa98%40googlegroups.com.

[weewx-user] Re: Sunshine Time

[Meteo Oberwallis]

Hello everbody

Unfortunately I haven't been able to solve the problem yet. I still have the 
problem that I want to include the sunshine time in my solar graphics. The 
value 0.08 is always given instead of 5min. How can you adjust that?


Am Mittwoch, 1. Januar 2020 13:22:36 UTC+1 schrieb Meteo Oberwallis:
>
>
> Hello everybody
> I have a question about graphic design. I would like to include the sunshine 
> time in the graphics. Currently the value of 0.08 in sunshine always appears 
> there. This is my current code in use.
> [[chart6]]
> title = Sonnenschein
> # Make sure the y-axis increment is at least 0.02 for the sun plot
> yscale = 0.0, 1.0, 0.1
> type = column
> [[[sunshine_hours]]]
> aggregate_type = sum
> aggregate_interval = 300
> color = "#e4d354"
> name = Sonnenschein in Minuten
>
> [image: Unbenannt.PNG]
>
>
>
> I would like to do this now, because the interval 300s is 5min as sunshine. 
> Can one make it like this?
>
> Many thanks for your help
>
>
>
>
> Am Montag, 22. Juli 2019 11:50:28 UTC+2 schrieb Stefan:
>>
>> Hello everybody.
>>
>> I have found this link (
>> https://github.com/brewster76/util-archer/blob/master/user/radiationhours.py)
>>  
>> where is described how to display the sunshine time. Now I would like to 
>> show this value in numbers (eg 4:15 h). Is that possible?
>>
>> 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/493de799-750f-4763-92b2-262110d83052%40googlegroups.com.

[weewx-user] Re: how to insert additional data (cpu temp) into skins?

[Meteo Oberwallis]

Hello Gary.

Thx. Its Work :-D

Am Donnerstag, 26. März 2020 09:48:50 UTC+1 schrieb gjr80:
>
> Hi,
>
> Your python file needs to be named cputemp.py not cputemp.AddCpuTemp.py
>
> 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/281f07e1-790e-4092-9439-9145680f9dce%40googlegroups.com.

[weewx-user] Re: how to insert additional data (cpu temp) into skins?

[Meteo Oberwallis]

Hello.

Since this is very interesting, I tried it right away. I created a python file 
called cputemp.AddCpuTemp.py with the content:

import  weewx
fromweewx.engineimport  StdService
fromgpiozeroimport  CPUTemperature

class AddCpuTemp(StdService):

def __init__(self, engine, config_dict):

  # Initialize my superclass first:
  super(AddCpuTemp, self).__init__(engine, config_dict)

  # Bind to any new archive record events:
  self.bind(weewx.NEW_ARCHIVE_RECORD, self.new_archive_record)

def new_archive_record(self, event):

cpu = CPUTemperature()

event.record['extraTemp1'] = ( cpu.temperature * 1.8 ) + 32

and save this under /usr/share/weewx/user/

In the weewx.conf have it the Service: data_services = user.cputemp.AddCpuTemp

Now this error message appears to me:


Mar 26 09:34:29 raspberrypi weewx[1412]: engine: Loading service 
weewx.engine.StdTimeSynch
Mar 26 09:34:29 raspberrypi weewx[1412]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Mar 26 09:34:29 raspberrypi weewx[1412]: engine: Loading service 
user.cputemp.AddCpuTemp
Mar 26 09:34:29 raspberrypi weewx[1412]: engine: Caught unrecoverable 
exception in engine:
Mar 26 09:34:29 raspberrypi weewx[1412]:   No module named cputemp
Mar 26 09:34:29 raspberrypi weewx[1412]:   Traceback (most recent 
call last):
Mar 26 09:34:29 raspberrypi weewx[1412]: File 
"/usr/share/weewx/weewx/engine.py", line 888, in main
Mar 26 09:34:29 raspberrypi weewx[1412]:   engine = 
engine_class(config_dict)
Mar 26 09:34:29 raspberrypi weewx[1412]: File 
"/usr/share/weewx/weewx/engine.py", line 78, in __init__
Mar 26 09:34:29 raspberrypi weewx[1412]:   
self.loadServices(config_dict)
Mar 26 09:34:29 raspberrypi weewx[1412]: File 
"/usr/share/weewx/weewx/engine.py", line 142, in loadServices
Mar 26 09:34:29 raspberrypi weewx[1412]:   
self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
Mar 26 09:34:29 raspberrypi weewx[1412]: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1107, in _get_object
Mar 26 09:34:29 raspberrypi weewx[1412]:   mod = 
__import__(module)
Mar 26 09:34:29 raspberrypi weewx[1412]:   ImportError: No module 
named cputemp
Mar 26 09:34:29 raspberrypi weewx[1412]:   Exiting.

Did I forget something there?

Thanks for Help


Am Mittwoch, 18. März 2020 14:34:41 UTC+1 schrieb Mike Revitt:
>
> Not sure if you are still looking for solutions, but I liked you idea so 
> had a look at implementing it in Python.
>
> Turns out it was easier than I thought.
>
> 1) create a python file and put it into the bin/user directory, this file 
> gets the CPU temperature, coverts it to Fahrenheit and puts it into the 
> extraTemp1 column in the database
>
> import  weewx
> fromweewx.engineimport  StdService
> fromgpiozeroimport  CPUTemperature
>
> class AddCpuTemp(StdService):
>
> def __init__(self, engine, config_dict):
>
>   # Initialize my superclass first:
>   super(AddCpuTemp, self).__init__(engine, config_dict)
>
>   # Bind to any new archive record events:
>   self.bind(weewx.NEW_ARCHIVE_RECORD, self.new_archive_record)
>
> def new_archive_record(self, event):
>
> cpu = CPUTemperature()
>
> event.record['extraTemp1'] = ( cpu.temperature * 1.8 ) + 32
>
>
> 2) modify weewx.conf to call the new file
> [Engine]
> 
> [[Services]]
> # This section specifies the services that should be run. They are
> # grouped by type, and the order of services within each group
> # determines the order in which the services will be run.
> prep_services = weewx.engine.StdTimeSynch
> data_services = user.cputemp.AddCpuTemp
>
>
> Now the value can be obtained anywhere you want by 
> referencing $current.extraTemp1
> I modified about.inc in the seasons skin with the following
>
> 
>   Server uptime
>   $station.os_uptime
> 
> 
>   Server CPU Temp
>   $current.extraTemp1
> 
> 
>   WeeWX uptime
>   $station.uptime
> 
>
>
> Also you can now access the dayTemp graph to see the plots over time
>
> On Thursday, February 20, 2020 at 4:55:00 PM UTC, Vetti52 wrote:
>>
>> Sorry for being too dumb for python...
>>
>> I want to show the actual cpu temperature in the "About this weather 
>> station" section. On my Raspberry Pi I get the result: 
>>
>> $ vcgencmd measure_temp
>> temp=53.0'C
>>
>> However, I do not know, how to enter this into a skin file. 
>> I gave a first try to
>>
>> > echo exec('vcgencmd measure_temp|sed "s/'/ °/"');
>> ?>
>>
>> resulting in
>> VCHI initialization failed
>>
>> I have added www-data to the video group, but this did not help. But, may 
>> be, it is much easier to realize. Please help!
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To

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

[Meteo Oberwallis]

Hi there.

It should look like the first (1.JPG) graphic. The second does not represent 
the months, but the days (2.JPG).



Am Dienstag, 24. März 2020 08:30:57 UTC+1 schrieb Gert Andersen:
>
> Hi
>
> Please explain what you think is wrong?
>
> Gert
>
> On Tuesday, March 24, 2020 at 7:30:31 AM UTC+1, Meteo Oberwallis wrote:
>>
>>
>> Hello Pat.
>>
>> Thank you very much. But now it looks like this to me. Why is that?
>>
>> Thanks for you Help!
>>
>>
>> Am Montag, 23. März 2020 17:58:24 UTC+1 schrieb Pat:
>>>
>>> Place the code I've pasted to you beneath the Solarstrahlung chart 
>>> you've created. 
>>>
>>>[[avgclimatethisyear]]
>>> title = "Average Climatological Values for This Year"
>>> type = spline
>>> time_length = year
>>> aggregate_type = max
>>> aggregate_interval = 86400 # 1 day
>>> gapsize = 8640
>>> xAxis_groupby = month
>>> xAxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 
>>> 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
>>> [[[outTemp]]]
>>> zIndex = 2
>>> name = Max Temperature
>>> color = red
>>> [[[outTemp_min]]]
>>> name = Min Temperature
>>> observation_type = outTemp
>>> aggregate_type = min
>>> zIndex = 2
>>> [[[rainTotal]]]
>>> name = Rain Total
>>> type = column
>>> yAxis = 1
>>> zIndex = 0
>>> color = "#268bd2"
>>>
>>>
>>>

-- 
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/ceaccbea-8663-46a2-a72c-97d8606636a3%40googlegroups.com.

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

[Meteo Oberwallis]

Hi there. 
Sorry for the stupid question. That would be under the "tab" homepage. If I use 
this now, then weewx gives an error message.

[homepage]
# Chart Timespan Defaults
title = "Homepage"
show_button = true
button_text = "Homepage"
time_length = today
tooltip_date_format = "LLL"
gapsize = 30 # This should be your archive_interval from weewx.conf 
multiplied by 1000 to get milliseconds. Standard is 5 minutes

[[chart1]]
title = Temperatur
[[[outTemp]]]
zIndex = 1
name = Temperatur
color = lightblue
[[[dewpoint]]]
color = purple
title = Temperatur
[[[outHumidity]]]
yAxis = 1
color = "#ffc83f"
time_length = today
tooltip_date_format = "LLL"
gapsize = 30 # This should be your archive_interval from weewx.conf 
multiplied by 1000 to get milliseconds. Standard is 5 minutes

[[chart1]]
title = Temperatur
[[[outTemp]]]
zIndex = 1
name = Temperatur
color = lightblue
[[[dewpoint]]]
color = purple
title = Temperatur
[[[outHumidity]]]
yAxis = 1
color = "#ffc83f"


It should be inserted here now?

Thx for Help



Am Sonntag, 22. März 2020 18:39:19 UTC+1 schrieb Pat:
>
> Yes, place it under the section you have defined for 
> highcharts_homepage_graphgroup 
>
> <https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/skin.conf#L30>
>
> On Sunday, March 22, 2020 at 1:36:18 PM UTC-4, Meteo Oberwallis wrote:
>>
>> Ok thanks.
>>
>> Can I install the current graphics on the Belchertown homepage? What code? I 
>> have to replace the [day]? Or how does it work?
>>
>> thanks
>>
>>
>> Am Sonntag, 22. März 2020 18:15:19 UTC+1 schrieb Pat:
>>>
>>> This is exactly how I have it in my graphs.conf. Which is the same as 
>>> the wiki and the example.
>>>
>>> [day]
>>> title = Today since Midnight
>>> show_button = true
>>> button_text = Today
>>> time_length = today
>>> gapsize = 30
>>>
>>>
>>> [[avgclimatethisyear]]
>>> title = "Average Climatological Values for This Year"
>>> type = spline
>>> time_length = year
>>> aggregate_type = max
>>> aggregate_interval = 86400 # 1 day
>>> gapsize = 8640
>>> xAxis_groupby = month
>>> xAxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 
>>> 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
>>> [[[outTemp]]]
>>>     zIndex = 2
>>> name = Max Temperature
>>> color = red
>>> [[[outTemp_min]]]
>>> name = Min Temperature
>>> observation_type = outTemp
>>> aggregate_type = min
>>> zIndex = 2
>>> [[[rainTotal]]]
>>> name = Rain Total
>>> type = column
>>> yAxis = 1
>>> zIndex = 0
>>> color = "#268bd2"
>>>
>>>
>>>
>>> On Sunday, March 22, 2020 at 1:12:43 PM UTC-4, Meteo Oberwallis wrote:
>>>>
>>>> Hello
>>>>
>>>> It should appear that way
>>>>
>>>>
>>>> Am Sonntag, 22. März 2020 18:08:26 UTC+1 schrieb p q:
>>>>>
>>>>> The problem with your graph isn't obvious to me. What's wrong with it?
>>>>>
>>>>> On Sun, Mar 22, 2020 at 9:57 AM Meteo Oberwallis  
>>>>> wrote:
>>>>>
>>>>>> Hello everybody.
>>>>>>
>>>>>> Can someone please help me with this problem? Why is this graphic not 
>>>>>> displayed correctly?
>>>>>>
>>>>>> Thanks for Help
>>>>>>
>>>>>>
>>>>>>
>>>>>> Am Dienstag, 17. März 2020 11:18:53 UTC+1 schrieb Meteo Oberwallis:
>>>>>>>
>>>>>>> Hello Pat.
>>>>>>>
>>>>>>> I have this in my Code under the Option [day]:
>>>>>>>
>>>>>>> [[avgclimatethisyear]] 
>>>>>>>
>>>>>&g

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

[Meteo Oberwallis]

Ok thanks.

Can I install the current graphics on the Belchertown homepage? What code? I 
have to replace the [day]? Or how does it work?

thanks


Am Sonntag, 22. März 2020 18:15:19 UTC+1 schrieb Pat:
>
> This is exactly how I have it in my graphs.conf. Which is the same as the 
> wiki and the example.
>
> [day]
> title = Today since Midnight
> show_button = true
> button_text = Today
> time_length = today
> gapsize = 30
>
>
> [[avgclimatethisyear]]
> title = "Average Climatological Values for This Year"
> type = spline
> time_length = year
> aggregate_type = max
> aggregate_interval = 86400 # 1 day
> gapsize = 8640
> xAxis_groupby = month
> xAxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul'
> , 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
> [[[outTemp]]]
> zIndex = 2
> name = Max Temperature
> color = red
> [[[outTemp_min]]]
> name = Min Temperature
> observation_type = outTemp
> aggregate_type = min
> zIndex = 2
> [[[rainTotal]]]
> name = Rain Total
> type = column
> yAxis = 1
> zIndex = 0
> color = "#268bd2"
>
>
>
> On Sunday, March 22, 2020 at 1:12:43 PM UTC-4, Meteo Oberwallis wrote:
>>
>> Hello
>>
>> It should appear that way
>>
>>
>> Am Sonntag, 22. März 2020 18:08:26 UTC+1 schrieb p q:
>>>
>>> The problem with your graph isn't obvious to me. What's wrong with it?
>>>
>>> On Sun, Mar 22, 2020 at 9:57 AM Meteo Oberwallis  
>>> wrote:
>>>
>>>> Hello everybody.
>>>>
>>>> Can someone please help me with this problem? Why is this graphic not 
>>>> displayed correctly?
>>>>
>>>> Thanks for Help
>>>>
>>>>
>>>>
>>>> Am Dienstag, 17. März 2020 11:18:53 UTC+1 schrieb Meteo Oberwallis:
>>>>>
>>>>> Hello Pat.
>>>>>
>>>>> I have this in my Code under the Option [day]:
>>>>>
>>>>> [[avgclimatethisyear]] 
>>>>>
>>>>> title = "Average Climatological Values for This Year"
>>>>> type = spline
>>>>> time_length = year
>>>>> aggregate_type = max
>>>>> aggregate_interval = 86400 # 1 day
>>>>> gapsize = 8640
>>>>> xAxis_groupby = month
>>>>> xAxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 
>>>>> 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
>>>>> [[[outTemp]]]
>>>>> zIndex = 2
>>>>> name = Max Temperature
>>>>> color = red
>>>>> [[[outTemp_min]]]
>>>>> name = Min Temperature
>>>>> observation_type = outTemp
>>>>> aggregate_type = min
>>>>> zIndex = 2
>>>>> [[[rainTotal]]]
>>>>> name = Rain Total
>>>>> type = column
>>>>> yAxis = 1
>>>>> zIndex = 0
>>>>> color = "#268bd2"
>>>>>
>>>>> This is the result:
>>>>>
>>>>> [image: Unbenannt.JPG]
>>>>>
>>>>> Its not right? Who is my Problem? Can i more this graphs from Year 
>>>>> 2019, 2018 etc. under this graphs?
>>>>>
>>>>>
>>>>> Thanks for Help
>>>>>
>>>>>
>>>>>
>>>>> Am Freitag, 13. März 2020 13:59:01 UTC+1 schrieb Pat:
>>>>>>
>>>>>> Examples like this and many others are in the Belchertown Charts Wiki 
>>>>>> <https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation>.
>>>>>>  
>>>>>> Just go to the Examples section. 
>>>>>>
>>>>>> On Friday, March 13, 2020 at 2:27:54 AM UTC-4, Meteo Oberwallis wrote:
>>>>>>>
&g

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

[Meteo Oberwallis]

Hello

It should appear that way


Am Sonntag, 22. März 2020 18:08:26 UTC+1 schrieb p q:
>
> The problem with your graph isn't obvious to me. What's wrong with it?
>
> On Sun, Mar 22, 2020 at 9:57 AM Meteo Oberwallis  > wrote:
>
>> Hello everybody.
>>
>> Can someone please help me with this problem? Why is this graphic not 
>> displayed correctly?
>>
>> Thanks for Help
>>
>>
>>
>> Am Dienstag, 17. März 2020 11:18:53 UTC+1 schrieb Meteo Oberwallis:
>>>
>>> Hello Pat.
>>>
>>> I have this in my Code under the Option [day]:
>>>
>>> [[avgclimatethisyear]] 
>>>
>>> title = "Average Climatological Values for This Year"
>>> type = spline
>>> time_length = year
>>> aggregate_type = max
>>> aggregate_interval = 86400 # 1 day
>>> gapsize = 8640
>>> xAxis_groupby = month
>>> xAxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 
>>> 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
>>> [[[outTemp]]]
>>> zIndex = 2
>>> name = Max Temperature
>>> color = red
>>> [[[outTemp_min]]]
>>> name = Min Temperature
>>> observation_type = outTemp
>>> aggregate_type = min
>>> zIndex = 2
>>> [[[rainTotal]]]
>>> name = Rain Total
>>> type = column
>>> yAxis = 1
>>> zIndex = 0
>>> color = "#268bd2"
>>>
>>> This is the result:
>>>
>>> [image: Unbenannt.JPG]
>>>
>>> Its not right? Who is my Problem? Can i more this graphs from Year 2019, 
>>> 2018 etc. under this graphs?
>>>
>>>
>>> Thanks for Help
>>>
>>>
>>>
>>> Am Freitag, 13. März 2020 13:59:01 UTC+1 schrieb Pat:
>>>>
>>>> Examples like this and many others are in the Belchertown Charts Wiki 
>>>> <https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation>.
>>>>  
>>>> Just go to the Examples section. 
>>>>
>>>> On Friday, March 13, 2020 at 2:27:54 AM UTC-4, Meteo Oberwallis wrote:
>>>>>
>>>>> Hi there.
>>>>> I have seen this page and I like it very much. Now I wanted to ask how to 
>>>>> create this page "Climate" so that I can display all past years there.
>>>>> Ich habe bereits schon eine "Climate" Seite, dort wird aber immer nur 
>>>>> eine Grafik angezeigt.
>>>>>
>>>>>
>>>>>
>>>>> Am Samstag, 1. Juni 2019 18:57:56 UTC+2 schrieb Pat:
>>>>>>
>>>>>> Belchertown skin 1.0 is released!
>>>>>>
>>>>>> This update contains a lot of updates and changes including *an 
>>>>>> entire rewrite of the Highcharts system* which allows you to make 
>>>>>> almost any graph you want for almost any time span you want. You can see 
>>>>>> some examples of the charts you can make on the BelchertownWeather.com 
>>>>>> website graphs page 
>>>>>> <https://belchertownweather.com/graphs/?graph=all>.
>>>>>>
>>>>>> You can add/remove/change/reorder any chart, change colors, add 
>>>>>> observation plots, categorize for all time. Almost anything you want to 
>>>>>> do 
>>>>>> is available! The skin comes with the standard 4 charts ready to go, but 
>>>>>> there's extensive Belchertown Charts Documentation 
>>>>>> <https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation>
>>>>>>  
>>>>>> which can help you get started. 
>>>>>>
>>>>>> In addition to the Charts there's now a dark mode (which has an 
>>>>>> auto-switching mode based on sunset/sunrise), more flexibility for 
>>>>>> translations, user customized station observation table which is updated 
>>>>>> in 
>>>>>> real time if the MQTT Websockets are enabled, and a lot more. Check the 
>>>>>> release notes for all the details! 
>>

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

[Meteo Oberwallis]

Hello everybody.

Can someone please help me with this problem? Why is this graphic not displayed 
correctly?

Thanks for Help



Am Dienstag, 17. März 2020 11:18:53 UTC+1 schrieb Meteo Oberwallis:
>
> Hello Pat.
>
> I have this in my Code under the Option [day]:
>
> [[avgclimatethisyear]] 
>
> title = "Average Climatological Values for This Year"
> type = spline
> time_length = year
> aggregate_type = max
> aggregate_interval = 86400 # 1 day
> gapsize = 8640
> xAxis_groupby = month
> xAxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 
> 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
> [[[outTemp]]]
> zIndex = 2
> name = Max Temperature
> color = red
> [[[outTemp_min]]]
> name = Min Temperature
> observation_type = outTemp
> aggregate_type = min
> zIndex = 2
> [[[rainTotal]]]
> name = Rain Total
> type = column
> yAxis = 1
> zIndex = 0
> color = "#268bd2"
>
> This is the result:
>
> [image: Unbenannt.JPG]
>
> Its not right? Who is my Problem? Can i more this graphs from Year 2019, 
> 2018 etc. under this graphs?
>
>
> Thanks for Help
>
>
>
> Am Freitag, 13. März 2020 13:59:01 UTC+1 schrieb Pat:
>>
>> Examples like this and many others are in the Belchertown Charts Wiki 
>> <https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation>.
>>  
>> Just go to the Examples section. 
>>
>> On Friday, March 13, 2020 at 2:27:54 AM UTC-4, Meteo Oberwallis wrote:
>>>
>>> Hi there.
>>> I have seen this page and I like it very much. Now I wanted to ask how to 
>>> create this page "Climate" so that I can display all past years there.
>>> Ich habe bereits schon eine "Climate" Seite, dort wird aber immer nur eine 
>>> Grafik angezeigt.
>>>
>>>
>>>
>>> Am Samstag, 1. Juni 2019 18:57:56 UTC+2 schrieb Pat:
>>>>
>>>> Belchertown skin 1.0 is released!
>>>>
>>>> This update contains a lot of updates and changes including *an entire 
>>>> rewrite of the Highcharts system* which allows you to make almost any 
>>>> graph you want for almost any time span you want. You can see some 
>>>> examples 
>>>> of the charts you can make on the BelchertownWeather.com website 
>>>> graphs page <https://belchertownweather.com/graphs/?graph=all>.
>>>>
>>>> You can add/remove/change/reorder any chart, change colors, add 
>>>> observation plots, categorize for all time. Almost anything you want to do 
>>>> is available! The skin comes with the standard 4 charts ready to go, but 
>>>> there's extensive Belchertown Charts Documentation 
>>>> <https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation>
>>>>  
>>>> which can help you get started. 
>>>>
>>>> In addition to the Charts there's now a dark mode (which has an 
>>>> auto-switching mode based on sunset/sunrise), more flexibility for 
>>>> translations, user customized station observation table which is updated 
>>>> in 
>>>> real time if the MQTT Websockets are enabled, and a lot more. Check the 
>>>> release notes for all the details! 
>>>>
>>>> You can download the latest release here 
>>>> <https://github.com/poblabs/weewx-belchertown/releases/download/weewx-belchertown-1.0/weewx-belchertown-release-1.0.tar.gz>,
>>>>  
>>>> and read all of the details on the changes here: 
>>>> https://github.com/poblabs/weewx-belchertown/releases
>>>>
>>>> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must 
>>>> uninstall everything and reinstall new. This is due to the Chart system 
>>>> being fully rewritten and the potential for conflicts. Please read 
>>>> this upgrade guide if you are upgrading from an older version of 
>>>> Belchertown skin 
>>>> <https://github.com/poblabs/weewx-belchertown/wiki/Upgrading-to-Belchertown-skin-1.0>
>>>> . 
>>>>
>>>> Thanks to all the beta testers and translators over the last couple of 
>>>> months help me iron out all the kinks and shape the skin in a way that can 
>>>> be translated a little easier! 
>>>>
>>>> Attached are some examples of the charts that can be made. If you find 
>>>> any issues, you can reply here or open an issue on the Belchertown 
>>>> skin GitHub page <https://github.com/poblabs/weewx-belchertown>. 
>>>>
>>>

-- 
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/c2496443-c2c4-447a-8c24-e9384874547e%40googlegroups.com.

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

[Meteo Oberwallis]

Hello Pat.

I have this in my Code under the Option [day]:

[[avgclimatethisyear]] 

title = "Average Climatological Values for This Year"
type = spline
time_length = year
aggregate_type = max
aggregate_interval = 86400 # 1 day
gapsize = 8640
xAxis_groupby = month
xAxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 
'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
[[[outTemp]]]
zIndex = 2
name = Max Temperature
color = red
[[[outTemp_min]]]
name = Min Temperature
observation_type = outTemp
aggregate_type = min
zIndex = 2
[[[rainTotal]]]
name = Rain Total
type = column
yAxis = 1
zIndex = 0
color = "#268bd2"

This is the result:

[image: Unbenannt.JPG]

Its not right? Who is my Problem? Can i more this graphs from Year 2019, 
2018 etc. under this graphs?


Thanks for Help



Am Freitag, 13. März 2020 13:59:01 UTC+1 schrieb Pat:
>
> Examples like this and many others are in the Belchertown Charts Wiki 
> <https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation>.
>  
> Just go to the Examples section. 
>
> On Friday, March 13, 2020 at 2:27:54 AM UTC-4, Meteo Oberwallis wrote:
>>
>> Hi there.
>> I have seen this page and I like it very much. Now I wanted to ask how to 
>> create this page "Climate" so that I can display all past years there.
>> Ich habe bereits schon eine "Climate" Seite, dort wird aber immer nur eine 
>> Grafik angezeigt.
>>
>>
>>
>> Am Samstag, 1. Juni 2019 18:57:56 UTC+2 schrieb Pat:
>>>
>>> Belchertown skin 1.0 is released!
>>>
>>> This update contains a lot of updates and changes including *an entire 
>>> rewrite of the Highcharts system* which allows you to make almost any 
>>> graph you want for almost any time span you want. You can see some examples 
>>> of the charts you can make on the BelchertownWeather.com website graphs 
>>> page <https://belchertownweather.com/graphs/?graph=all>.
>>>
>>> You can add/remove/change/reorder any chart, change colors, add 
>>> observation plots, categorize for all time. Almost anything you want to do 
>>> is available! The skin comes with the standard 4 charts ready to go, but 
>>> there's extensive Belchertown Charts Documentation 
>>> <https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation>
>>>  
>>> which can help you get started. 
>>>
>>> In addition to the Charts there's now a dark mode (which has an 
>>> auto-switching mode based on sunset/sunrise), more flexibility for 
>>> translations, user customized station observation table which is updated in 
>>> real time if the MQTT Websockets are enabled, and a lot more. Check the 
>>> release notes for all the details! 
>>>
>>> You can download the latest release here 
>>> <https://github.com/poblabs/weewx-belchertown/releases/download/weewx-belchertown-1.0/weewx-belchertown-release-1.0.tar.gz>,
>>>  
>>> and read all of the details on the changes here: 
>>> https://github.com/poblabs/weewx-belchertown/releases
>>>
>>> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must 
>>> uninstall everything and reinstall new. This is due to the Chart system 
>>> being fully rewritten and the potential for conflicts. Please read this 
>>> upgrade guide if you are upgrading from an older version of Belchertown 
>>> skin 
>>> <https://github.com/poblabs/weewx-belchertown/wiki/Upgrading-to-Belchertown-skin-1.0>
>>> . 
>>>
>>> Thanks to all the beta testers and translators over the last couple of 
>>> months help me iron out all the kinks and shape the skin in a way that can 
>>> be translated a little easier! 
>>>
>>> Attached are some examples of the charts that can be made. If you find 
>>> any issues, you can reply here or open an issue on the Belchertown skin 
>>> GitHub page <https://github.com/poblabs/weewx-belchertown>. 
>>>
>>

-- 
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/1a124482-d95f-47fa-b7e4-16b896143457%40googlegroups.com.

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

[Meteo Oberwallis]

Hi there.
I have seen this page and I like it very much. Now I wanted to ask how to 
create this page "Climate" so that I can display all past years there.
Ich habe bereits schon eine "Climate" Seite, dort wird aber immer nur eine 
Grafik angezeigt.



Am Samstag, 1. Juni 2019 18:57:56 UTC+2 schrieb Pat:
>
> Belchertown skin 1.0 is released!
>
> This update contains a lot of updates and changes including *an entire 
> rewrite of the Highcharts system* which allows you to make almost any 
> graph you want for almost any time span you want. You can see some examples 
> of the charts you can make on the BelchertownWeather.com website graphs 
> page .
>
> You can add/remove/change/reorder any chart, change colors, add 
> observation plots, categorize for all time. Almost anything you want to do 
> is available! The skin comes with the standard 4 charts ready to go, but 
> there's extensive Belchertown Charts Documentation 
> 
>  
> which can help you get started. 
>
> In addition to the Charts there's now a dark mode (which has an 
> auto-switching mode based on sunset/sunrise), more flexibility for 
> translations, user customized station observation table which is updated in 
> real time if the MQTT Websockets are enabled, and a lot more. Check the 
> release notes for all the details! 
>
> You can download the latest release here 
> ,
>  
> and read all of the details on the changes here: 
> https://github.com/poblabs/weewx-belchertown/releases
>
> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must 
> uninstall everything and reinstall new. This is due to the Chart system 
> being fully rewritten and the potential for conflicts. Please read this 
> upgrade guide if you are upgrading from an older version of Belchertown skin 
> 
> . 
>
> Thanks to all the beta testers and translators over the last couple of 
> months help me iron out all the kinks and shape the skin in a way that can 
> be translated a little easier! 
>
> Attached are some examples of the charts that can be made. If you find any 
> issues, you can reply here or open an issue on the Belchertown skin 
> GitHub page . 
>

-- 
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/bebe1845-3dcd-4bd1-9a97-779c43fb42df%40googlegroups.com.

Re: [weewx-user] Graphs with command in the Bottom Label

[Meteo Oberwallis]

Thank you Thomas.

Am Samstag, 7. März 2020 17:58:18 UTC+1 schrieb Thomas Keffer:
>
> Unfortunately, no. The Cheetah template engine is not used for graph 
> labels, only to generate files.
>
> On Sat, Mar 7, 2020 at 7:18 AM Meteo Oberwallis  > wrote:
>
>>
>> Hi there.Is it possible to insert the station and the height in the graphic 
>> based on these variables? Then the template could also be used for other 
>> stations without having to adjust everything every time.
>>
>>
>> [image: daywindgust.png]
>>
>>
>> Thx for Help
>> Stefan
>>
>> -- 
>> 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/bd3a2592-a090-43da-a357-437a62a5fc3c%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/bd3a2592-a090-43da-a357-437a62a5fc3c%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/22b39485-39dc-490d-be22-1db8c78b9656%40googlegroups.com.

[weewx-user] Graphs with command in the Bottom Label

[Meteo Oberwallis]

Hi there.Is it possible to insert the station and the height in the graphic 
based on these variables? Then the template could also be used for other 
stations without having to adjust everything every time.


[image: daywindgust.png]


Thx for Help
Stefan

-- 
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/bd3a2592-a090-43da-a357-437a62a5fc3c%40googlegroups.com.

Re: [weewx-user] Re: **** Expected to read 99 chars; got 0 instead

[Meteo Oberwallis]

Hey Thomas

1. Yes the station ran flawlessly. Suddenly it started with this mistake
2. Yes see all data on the console
3. I still have to test
4. Connection is OK

Am Montag, 24. Februar 2020 13:47:12 UTC+1 schrieb Thomas Keffer:
>
> Hello, Stefan
>
> 1. Has your station every worked? Or, has it always been like this?
>
> 2. Could we see the output of wee_device --info?
>
> 3. Try reseat your logger: pull it out, then put it back in.
>
> 4. Also, check your USB connection. Make sure it is fully seated.
>
> -tk
>
>
> On Sun, Feb 23, 2020 at 10:52 PM Stefan > 
> wrote:
>
>> Hello.
>>
>> I have this Problem
>>
>> Feb 24 07:45:19 raspberrypi systemd[1]: Starting LSB: weewx weather 
>> system...
>> Feb 24 07:45:20 raspberrypi weewx[669]: engine: Initializing weewx 
>> version 3.9.2
>> Feb 24 07:45:20 raspberrypi weewx[669]: engine: Using Python 2.7.16 
>> (default, Oct 10 2019, 22:02:15) #012[GCC 8.3.0]
>> Feb 24 07:45:20 raspberrypi weewx[669]: engine: Platform 
>> Linux-4.19.97-v7+-armv7l-with-debian-10.3
>> Feb 24 07:45:20 raspberrypi weewx[669]: engine: Locale is 'de_CH.UTF-8'
>> Feb 24 07:45:20 raspberrypi weewx[669]: engine: pid file is 
>> /var/run/weewx.pid
>> Feb 24 07:45:20 raspberrypi weewx[658]: Starting weewx weather system: 
>> weewx.
>> Feb 24 07:45:20 raspberrypi systemd[1]: Started LSB: weewx weather system.
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Using configuration file 
>> /etc/weewx/weewx.conf
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Debug is 1
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Initializing engine
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading station type 
>> Vantage (weewx.drivers.vantage)
>> Feb 24 07:45:20 raspberrypi weewx[673]: vantage: Driver version is 3.1.1
>> Feb 24 07:45:20 raspberrypi weewx[673]: vantage: Opened up serial port 
>> /dev/ttyUSB0; baud 19200; timeout 4.00
>> Feb 24 07:45:20 raspberrypi weewx[673]: vantage: Gentle wake up of 
>> console successful
>> Feb 24 07:45:20 raspberrypi weewx[673]: vantage: Hardware type is 16
>> Feb 24 07:45:20 raspberrypi weewx[673]: vantage: ISS ID is 1
>> Feb 24 07:45:20 raspberrypi weewx[673]: vantage: Hardware name: Vantage 
>> Pro2
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
>> weewx.engine.StdTimeSynch
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
>> weewx.engine.StdTimeSynch
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
>> weewx.engine.StdConvert
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: StdConvert target unit is 
>> 0x1
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
>> weewx.engine.StdConvert
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
>> weewx.engine.StdCalibrate
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
>> weewx.engine.StdCalibrate
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
>> weewx.engine.StdQC
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
>> weewx.engine.StdQC
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
>> weewx.wxservices.StdWXCalculate
>> Feb 24 07:45:20 raspberrypi weewx[673]: wxcalculate: The following values 
>> will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
>> dewpoint=prefer_hardware, appTemp=prefer_hardware, 
>> rainRate=prefer_hardware, windrun=prefer_hardware, 
>> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
>> humidex=prefer_hardware, pressure=prefer_hardware, 
>> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
>> cloudbase=prefer_hardware
>> Feb 24 07:45:20 raspberrypi weewx[673]: wxcalculate: The following 
>> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
>> weewx.wxservices.StdWXCalculate
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
>> user.radiationhours.RadiationHours
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
>> user.radiationhours.RadiationHours
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
>> weewx.engine.StdArchive
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Archive will use data 
>> binding wx_binding
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Record generation will be 
>> attempted in 'hardware'
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Using archive interval of 
>> 300 seconds (specified by hardware)
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Use LOOP data in hi/low 
>> calculations: 1
>> Feb 24 07:45:20 raspberrypi weewx[673]: manager: Daily summary version is 
>> 2.0
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Using binding 
>> 'wx_binding' to database 'weewx.sdb_new'
>> Feb 24 07:45:20 raspberrypi weewx[673]: manager: Starting backfill of 
>> daily summaries
>> Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finishe