[weewx-user] Re: Solar radiation reading without solar sensor !!!!!???????

[Kike .Asekas]

I just looked but I don't have maxSolarRad in [Calculations]

El martes, 7 de julio de 2020, 13:29:24 (UTC+2), Kike .Asekas escribió:
>
> Ok. Thank you. I understand. It was very intrigating.
>
> El martes, 7 de julio de 2020, 12:16:04 (UTC+2), Jacques Terrettaz 
> escribió:
>>
>> If the name of the mqtt variable is maxSolarRad, it is not a measurement 
>> but the value of the maximal solar radiation expected for your location and 
>> calculated by weewx.
>>
>> If you don't need the value, you can remove the "maxSolarRad line in the 
>> section [StdWXCalculate] [[Calculations]] of weewx.conf.
>>
>> Le mardi 7 juillet 2020 12:00:05 UTC+2, Kike .Asekas a écrit :
>>>
>>> I have weewx with the mqtt extension and sdr driver. I haven't solar 
>>> sensor but if i see the mqtt messages it appear the solar radiation. How is 
>>> it posible? And the data seems correct.Now we are going towards noon 
>>> and the radiation grows
>>>
>>

-- 
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/6e2e6f7a-91d5-42e6-bbfe-3cbd1bde08f7o%40googlegroups.com.

[weewx-user] Re: Solar radiation reading without solar sensor !!!!!???????

[Kike .Asekas]

Ok. Thank you. I understand. It was very intrigating.

El martes, 7 de julio de 2020, 12:16:04 (UTC+2), Jacques Terrettaz escribió:
>
> If the name of the mqtt variable is maxSolarRad, it is not a measurement 
> but the value of the maximal solar radiation expected for your location and 
> calculated by weewx.
>
> If you don't need the value, you can remove the "maxSolarRad line in the 
> section [StdWXCalculate] [[Calculations]] of weewx.conf.
>
> Le mardi 7 juillet 2020 12:00:05 UTC+2, Kike .Asekas a écrit :
>>
>> I have weewx with the mqtt extension and sdr driver. I haven't solar 
>> sensor but if i see the mqtt messages it appear the solar radiation. How is 
>> it posible? And the data seems correct.Now we are going towards noon and 
>> the radiation grows
>>
>

-- 
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/f49f23fd-308c-401d-953e-3232c1ff6960o%40googlegroups.com.

[weewx-user] Solar radiation reading without solar sensor !!!!!???????

[Kike .Asekas]

I have weewx with the mqtt extension and sdr driver. I haven't solar sensor 
but if i see the mqtt messages it appear the solar radiation. How is it 
posible? And the data seems correct.Now we are going towards noon and the 
radiation grows

-- 
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/186c83dd-a354-4529-9a22-4c2f800904f2o%40googlegroups.com.

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

[Kike .Asekas]

Sorry. I didn't see your message. It was that. I change MQTT inputs and now 
the speed is in km/h althought it reports windSpeed_mps
{"noise_dB": "-29.591", "cloudbase_meter": "134.366868777", "outHumidity": 
"96.0", "pressure_mbar": "1004.74", "maxSolarRad": "0.0", "barometer_mbar": 
"1011.6171679", "rainRate_mm_per_hour": "0.0", "dewpoint_C": 
"11.7795292565", "heatindex_C": "12.4", "dayRain_mm": "2.1", "battery": 
"0.0", "altimeter_mbar": "1011.2607317", "windchill_C": "12.4", "snr_dB": 
"29.476", "rain_total": "68.55", "appTemp_C": "12.4773944539", "outTemp_C": 
"12.4", "humidex_C": "14.545643026", "hourRain_mm": "0.0", "windGust_mps": 
"3.67200912966", "rssi_dB": "-0.115", "inTemp_C": "19.5", "usUnits": 
"17.0", "rain_mm": "0.0", "rain24_mm": "3.9", "dateTime": "1574971656.0", 
"windDir": "0.0", "windSpeed_mps": "2.44800608644"}

El miércoles, 27 de noviembre de 2019, 20:12:17 (UTC+1), Greg Troxel 
escribió:
>
> "Kike .Asekas" > writes: 
>
> > I use MQTT y I have configure it with METRICWX. 
> > [[MQTT]] 
> > server_url = mqtt://broker.hivemq.com:1883 
> > topic = estacion/datos 
> > unit_system = METRICWX 
> > binding = loop 
> > ... 
> > When I load the page goes well, but at the time of updating the wind 
> speed 
> > appears in m / s. If I change the lines I told you multiplying x3.6 it 
> goes 
> > well. 
>
> You can tell the mqtt publisher to set the units on each thing to 
> publish.   Probably you should just do that, even if in the background 
> you try to investigate the defaults. 
>
> For example, I have 
>
> [[[inputs]]] 
> barometer 
> name = barometer_hPa 
> units = hPa 
>
> I am really not sure why I needed this, as I have group_pressure set to 
> hPa as a default for all reports, but it was easy to set. 
>
> > This is the output of MQTT. By the way, I don't understand how 
> maxSolarRad 
> > appears without having a solar sensor 
>
> That does not make sense.  Some stations pretend to measure solar 
> radation from an illuminance sensor, but I don't even see that in your 
> output. 
>
> Also, since solar radiation is more or less always in W/m^2 (even in the 
> US we do not use hp/ft^2), the value 7 does not really make sense unless 
> right at dawn.  Even a very dark day will see 50. 
>

-- 
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/a90413e3-59c6-47d3-8ecd-4d1754510750%40googlegroups.com.

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

[Kike .Asekas]

Ok, I already understand. The fail is in MQTT. The skin only show it send 
by mqtt. If mqtt send m/s the skin shows m/s.
Fortunately the mqtt module have options to change the units show to every 
observation.
I change [MQTT] in weewx.conf with this
[[[inputs]]]
windSpeed
units = km_per_hour
windGust
units = km_per_hour

-- 
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/b0033ae9-ef25-4720-83aa-750faf15dfd0%40googlegroups.com.

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

[Kike .Asekas]

If I set US in MQTT the temperature and all data, barometer, cloudbase, etc 
it appears in the US units.
{"noise_dB": "-31.005", "barometer_inHg": "29.7715847252", "outHumidity": 
"92.0", "maxSolarRad": "0.19266621551", "rainRate_mm_per_hour": "0.0", 
"dewpoint_F": "52.2228357071", "rain_in": "0.0", "cloudbase_foot": 
"704.545678119", "heatindex_F": "54.5", "altimeter_inHg": "29.7612660083", 
"dayRain_mm": "0.3", "battery": "0.0", "outTemp_F": "54.5", "appTemp_F": 
"52.2075030114", "snr_dB": "30.881", "rain_total": "68.16", "windchill_F": 
"54.5", "hourRain_in": "0.0", "humidex_F": "57.8664956127", "rssi_dB": 
"-0.124", "windGust_mph": "8.36618332697", "pressure_inHg": 
"29.5692623834", "inTemp_F": "63.5", "usUnits": "1.0", "windSpeed_mph": 
"5.32393484443", "rain24_in": "0.0708661417323", "dateTime": 
"1574873496.0", "windDir": "180.0"}
And if I set METRIC the rain is in cm.

-- 
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/8e4094af-5bbc-42bc-83a7-acb164187226%40googlegroups.com.

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

[Kike .Asekas]

If I set METRIC in MQTT the speed it appears well. But I think now the 
problem is the rain in cm.
This is the output of MQTT
{"noise_dB": "-31.005", "cloudbase_meter": "214.870790215", "outHumidity": 
"92.0", "pressure_mbar": "1001.17", "rain_cm": "0.0", "maxSolarRad": 
"1.45829104758", "barometer_mbar": "1008.01791956", "rainRate_mm_per_hour": 
"0.0", "dewpoint_C": "11.3338998187", "*windGust_kph*": "15.9120395619", 
"heatindex_C": "12.6", "dayRain_mm": "0.3", "battery": "0.0", 
"altimeter_mbar": "1007.67110825", "windchill_C": "12.6", "snr_dB": 
"30.899", "rain_total": "68.16", "appTemp_C": "11.1172772991", "outTemp_C": 
"12.6", "humidex_C": "14.5196613477", "rain24_cm": "0.18", "rssi_dB": 
"-0.106", "hourRain_cm": "0.0", "inTemp_C": "17.5", "*windSpeed_kph*": 
"9.79202434576", "usUnits": "16.0", "dateTime": "1574873016.0", "windDir": 
"135.0"}

-- 
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/2db6db11-8e28-4156-b1ed-99bba5f29005%40googlegroups.com.

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

[Kike .Asekas]

I use MQTT y I have configure it with METRICWX.
[[MQTT]]
server_url = mqtt://broker.hivemq.com:1883
topic = estacion/datos
unit_system = METRICWX
binding = loop
...
When I load the page goes well, but at the time of updating the wind speed 
appears in m / s. If I change the lines I told you multiplying x3.6 it goes 
well. 
This is the output of MQTT. By the way, I don't understand how maxSolarRad 
appears without having a solar sensor
{"noise_dB": "-32.602", "cloudbase_meter": "214.870790215", "outHumidity": 
"92.0", "pressure_mbar": "1001.03", "maxSolarRad": "7.37293576364", 
"barometer_mbar": "1007.87696197", "rainRate_mm_per_hour": "0.0", 
"dewpoint_C": "11.3338998187", "heatindex_C": "12.6", "dayRain_mm": "0.3", 
"battery": "0.0", "altimeter_mbar": "1007.53033843", "windchill_C": "12.6", 
"snr_dB": "32.481", "rain_total": "68.16", "appTemp_C": "11.1172772991", 
"outTemp_C": "12.6", "humidex_C": "14.5196613477", "hourRain_mm": "0.0", 
*"windGust_mps*": "4.08001014407", "rssi_dB": "-0.12", "inTemp_C": "17.5", 
"usUnits": "17.0", "rain_mm": "0.0", "rain24_mm": "1.8", "dateTime": 
"1574872344.0", "windDir": "180.0", "*windSpeed_mps*": "2.72000676271"}
In this case in the web page it appear WindSpeed 2.7 and gust 4.8 Km/h


El miércoles, 27 de noviembre de 2019, 0:39:35 (UTC+1), Pat escribió:
>
> Kike I don't this this is a bug. Are you using MQTT? If so, then you need 
> to configure your MQTT plugin to use metricwx. 
>
> *There is no need to do math like this in the js*. 
>
> Please see this thread on how to update your MQTT settings. 
>
>
> https://github.com/poblabs/weewx-belchertown/issues/23#issuecomment-440529099
>
>
>
> On Tuesday, November 26, 2019 at 4:38:20 PM UTC-5, Kike .Asekas wrote:
>>
>>
>> Pat, I detect a bug in the js. I use the target_unit=metricwx that store 
>> the speed in m/s but i want see the speed in km/h and for that reason i 
>> have the group_speed=km_per_hour. The skin shows the speed in km/s until 
>> update then m/s. I change the lines 879 and 893  multiply x 3.6. Maybe it 
>> also fails to people with us  target unit and metric visualization.
>>
>

-- 
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/24feaa64-54ff-41fb-86a7-d19a62b27b2b%40googlegroups.com.

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

[Kike .Asekas]

Pat, I detect a bug in the js. I use the target_unit=metricwx that store 
the speed in m/s but i want see the speed in km/h and for that reason i 
have the group_speed=km_per_hour. The skin shows the speed in km/s until 
update then m/s. I change the lines 879 and 893  multiply x 3.6. Maybe it 
also fails to people with us  target unit and metric visualization.

-- 
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/1f4d351e-ab4b-4e9a-93fe-baacfc668181%40googlegroups.com.

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

[Kike .Asekas]

Hi Pat. I can't think of anything. The bands are put on belchertown.py and 
the change of theme is in a js. The color of the plotbands should be 
changed in the javascript when the button is pressed.

El sábado, 2 de noviembre de 2019, 22:03:55 (UTC+1), Pat escribió:
>
> Kike, so far so good with my testing in the 1.1 beta release. I have not 
> committed it to my development GitHub branch yet because I still need to 
> work out how to get the dark mode to show the gradients. 
>
> On Friday, October 25, 2019 at 8:18:29 AM UTC-4, Kike .Asekas wrote:
>>
>> You're right. I had not taken into account the light and dark mode. You 
>> have to change the color, at least for the dark mode. As is the 
>> transition is not seen. I put the colors at the beginning of the 
>> run(self) method and in weewx.conf I created 2 new variables, plotDayNight 
>> to enable or disable it and daynight_gradient for the number of bands of 
>> the gradient.
>>
>> El miércoles, 23 de octubre de 2019, 16:05:08 (UTC+2), Pat escribió:
>>>
>>> Looking at it now and it looks great. Quite a bit of work to figure this 
>>> out. 
>>>
>>> I may change the config to be in graphs.conf so there is granular 
>>> control on the plot bands- will think about this. 
>>>
>>> Will the color bands change based on light/dark mode? Or is the selected 
>>> color ok for both site modes?
>>>
>>>
>>> On Wednesday, October 23, 2019 at 8:35:11 AM UTC-4, Kike .Asekas wrote:
>>>>
>>>> I send you the files here. The configuration has two parameters.
>>>> plotDayNight and daynight_gradient. The first is to activate or 
>>>> deactivate it and the second is the number of gradient bands that by 
>>>> default is 20 as in plotgen.py.
>>>> The changes are basically from line 1237 at belchertown.js.tmpl and 
>>>> line 1247 from belchertown.py, although there are other lines.
>>>>
>>>> El martes, 22 de octubre de 2019, 14:58:12 (UTC+2), Pat escribió:
>>>>>
>>>>> Great thanks. You can try the GitHub but if that confuses you then you 
>>>>> can just attach the files here and I can try to figure it out when I have 
>>>>> some time. 
>>>>>
>>>>> On Tuesday, October 22, 2019 at 8:52:37 AM UTC-4, Kike .Asekas wrote:
>>>>>>
>>>>>> What I did was adapt the renderDayNight function of genplot.py to get 
>>>>>> the timestamps of dawn and dusk and with those timestamps write 
>>>>>> plotBands 
>>>>>> (HighCharts function) in xAxis in the json.
>>>>>> The code already has the possibility to activate them or not. It 
>>>>>> takes about a second on the daily chart in a rpi 2b + to paint them.
>>>>>> I am watching the github desktop program so I can send it to you. I 
>>>>>> guess you will have to make some changes, I don't dominate much python 
>>>>>> or 
>>>>>> js.
>>>>>>
>>>>>> El sábado, 19 de octubre de 2019, 22:26:17 (UTC+2), Pat escribió:
>>>>>>>
>>>>>>> Hi Kike, this looks very interesting! Perhaps I can add it as a skin 
>>>>>>> option to enable/disable it. How did you do it?
>>>>>>>
>>>>>>> On Saturday, October 19, 2019 at 4:07:41 PM UTC-4, Kike .Asekas 
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hi, Pat. I wanted to make a contribution to such an impressive 
>>>>>>>> skin, but I don't know very well how to do it. If you are 
>>>>>>>> interested tell me how.
>>>>>>>> They are the transitions between night and day in the graphics.
>>>>>>>>
>>>>>>>> [image: Screenshot_2019-10-19 Areal, Padron Weather 
>>>>>>>> Conditions(1).png]
>>>>>>>>
>>>>>>>> [image: Screenshot_2019-10-19 Areal, Padron Weather 
>>>>>>>> Conditions(2).png]
>>>>>>>>
>>>>>>>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions.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/bfb276d6-a845-44b9-a726-ef90a8cbb432%40googlegroups.com.

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

[Kike .Asekas]

You're right. I had not taken into account the light and dark mode. You 
have to change the color, at least for the dark mode. As is the transition 
is not seen. I put the colors at the beginning of the run(self) method and 
in weewx.conf I created 2 new variables, plotDayNight to enable or disable 
it and daynight_gradient for the number of bands of the gradient.

El miércoles, 23 de octubre de 2019, 16:05:08 (UTC+2), Pat escribió:
>
> Looking at it now and it looks great. Quite a bit of work to figure this 
> out. 
>
> I may change the config to be in graphs.conf so there is granular control 
> on the plot bands- will think about this. 
>
> Will the color bands change based on light/dark mode? Or is the selected 
> color ok for both site modes?
>
>
> On Wednesday, October 23, 2019 at 8:35:11 AM UTC-4, Kike .Asekas wrote:
>>
>> I send you the files here. The configuration has two parameters.
>> plotDayNight and daynight_gradient. The first is to activate or 
>> deactivate it and the second is the number of gradient bands that by 
>> default is 20 as in plotgen.py.
>> The changes are basically from line 1237 at belchertown.js.tmpl and line 
>> 1247 from belchertown.py, although there are other lines.
>>
>> El martes, 22 de octubre de 2019, 14:58:12 (UTC+2), Pat escribió:
>>>
>>> Great thanks. You can try the GitHub but if that confuses you then you 
>>> can just attach the files here and I can try to figure it out when I have 
>>> some time. 
>>>
>>> On Tuesday, October 22, 2019 at 8:52:37 AM UTC-4, Kike .Asekas wrote:
>>>>
>>>> What I did was adapt the renderDayNight function of genplot.py to get 
>>>> the timestamps of dawn and dusk and with those timestamps write plotBands 
>>>> (HighCharts function) in xAxis in the json.
>>>> The code already has the possibility to activate them or not. It takes 
>>>> about a second on the daily chart in a rpi 2b + to paint them.
>>>> I am watching the github desktop program so I can send it to you. I 
>>>> guess you will have to make some changes, I don't dominate much python or 
>>>> js.
>>>>
>>>> El sábado, 19 de octubre de 2019, 22:26:17 (UTC+2), Pat escribió:
>>>>>
>>>>> Hi Kike, this looks very interesting! Perhaps I can add it as a skin 
>>>>> option to enable/disable it. How did you do it?
>>>>>
>>>>> On Saturday, October 19, 2019 at 4:07:41 PM UTC-4, Kike .Asekas wrote:
>>>>>>
>>>>>> Hi, Pat. I wanted to make a contribution to such an impressive skin, 
>>>>>> but I don't know very well how to do it. If you are interested tell 
>>>>>> me how.
>>>>>> They are the transitions between night and day in the graphics.
>>>>>>
>>>>>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions(1).png]
>>>>>>
>>>>>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions(2).png]
>>>>>>
>>>>>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions.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/d98ce4d8-8d11-4534-b00b-24e0d57911fd%40googlegroups.com.

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

[Kike .Asekas]

What I did was adapt the renderDayNight function of genplot.py to get the 
timestamps of dawn and dusk and with those timestamps write plotBands 
(HighCharts function) in xAxis in the json.
The code already has the possibility to activate them or not. It takes 
about a second on the daily chart in a rpi 2b + to paint them.
I am watching the github desktop program so I can send it to you. I guess 
you will have to make some changes, I don't dominate much python or js.

El sábado, 19 de octubre de 2019, 22:26:17 (UTC+2), Pat escribió:
>
> Hi Kike, this looks very interesting! Perhaps I can add it as a skin 
> option to enable/disable it. How did you do it?
>
> On Saturday, October 19, 2019 at 4:07:41 PM UTC-4, Kike .Asekas wrote:
>>
>> Hi, Pat. I wanted to make a contribution to such an impressive skin, but 
>> I don't know very well how to do it. If you are interested tell me how.
>> They are the transitions between night and day in the graphics.
>>
>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions(1).png]
>>
>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions(2).png]
>>
>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions.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/c953c67e-9052-4c68-b62b-ce525cd7b02b%40googlegroups.com.

Re: [weewx-user] 'ascii' codec can't decode byte 0xc3

[Kike .Asekas]

Thank you. The file have #encoding UTF-8. I remove the seasons folder and 
it copy from github. I change weewx.conf labels to spanish with spanish 
characters and I don't have errors now. I don't know where was the fault.

El martes, 24 de septiembre de 2019, 14:47:45 (UTC+2), Thomas Keffer 
escribió:
>
> The problem is almost surely in the file 
> /etc/weewx/skins/Seasons/index.html.tmpl. Double check that the top of 
> the file include a #encoding directive:
>
> ## Copyright 2009-2018 Tom Keffer, Matthew Wall
> ## Distributed under terms of GPLv3.  See LICENSE.txt for your rights.
> #errorCatcher Echo
> ##
> ## Specifying an encoding of UTF-8 is usually safe:
> #encoding UTF-8
> ##
> 
>
> If it does, send me privately your copy of 
> /etc/weewx/skins/Seasons/index.html.tmpl, 
> /etc/weewx/skins/Seasons/skin.conf, and /etc/weewx/weewx.conf and I will 
> see if I can replicate the error. Obfuscate any passwords in weewx.conf.
>
> -tk (tke...@gmail.com )
>
>
> On Tue, Sep 24, 2019 at 5:09 AM Kike .Asekas  > wrote:
>
>> cheetahgenerator: Generate failed with exception '> 'exceptions.UnicodeDecodeError'>'
>> Sep 24 14:05:27 raspberrypi weewx[27767]: cheetahgenerator:  Ignoring 
>> template /etc/weewx/skins/Seasons/index.html.tmpl
>> Sep 24 14:05:27 raspberrypi weewx[27767]: cheetahgenerator:  Reason: 
>> 'ascii' codec can't decode byte 0xc3 in position 1815: ordinal not in 
>> range(128)
>> Sep 24 14:05:27 raspberrypi weewx[27767]:   Traceback (most recent 
>> call last):
>> Sep 24 14:05:27 raspberrypi weewx[27767]: File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 332, in generate
>> Sep 24 14:05:27 raspberrypi weewx[27767]:   
>> fd.write(str(compiled_template))
>> Sep 24 14:05:27 raspberrypi weewx[27767]: File 
>> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1045, in 
>> __str__
>> Sep 24 14:05:27 raspberrypi weewx[27767]:   rc = getattr(self, 
>> mainMethName)()
>> Sep 24 14:05:27 raspberrypi weewx[27767]: File 
>> "_etc_weewx_skins_Seasons_index_html_tmpl.py", line 216, in respond
>> Sep 24 14:05:27 raspberrypi weewx[27767]: File 
>> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1685, in 
>> _handleCheetahInclude
>> Sep 24 14:05:27 raspberrypi weewx[27767]:   file=file)
>> Sep 24 14:05:27 raspberrypi weewx[27767]: File 
>> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 772, in compile
>> Sep 24 14:05:27 raspberrypi weewx[27767]:   
>> settings=(compilerSettings or {}))
>> Sep 24 14:05:27 raspberrypi weewx[27767]: File 
>> "/usr/lib/python2.7/dist-packages/Cheetah/Compiler.py", line 1708, in 
>> __init__
>> Sep 24 14:05:27 raspberrypi weewx[27767]:   source = 
>> unicode(source)
>> Sep 24 14:05:27 raspberrypi weewx[27767]:   UnicodeDecodeError: 
>> 'ascii' codec can't decode byte 0xc3 in position 1815: ordinal not in 
>> range(128)
>>
>>
>> El martes, 24 de septiembre de 2019, 13:49:13 (UTC+2), Thomas Keffer 
>> escribió:
>>>
>>> It sure would help if you showed us the log...
>>>
>>> On Tue, Sep 24, 2019 at 4:27 AM Kike .Asekas  wrote:
>>>
>>>> I sorry. I don't know where is the problem. I remove all spanish 
>>>> characters from skin.conf, index.html.tmpl and weewx.conf and I remove the 
>>>> template and copy it again from the git repository and the error continues.
>>>>
>>>> El martes, 24 de septiembre de 2019, 12:54:09 (UTC+2), Kike .Asekas 
>>>> escribió:
>>>>>
>>>>> I think is in skin.conf. I remove all spanish characters in the 
>>>>> template and the error continues. The template is index.html.tmpl
>>>>>
>>>>> El lunes, 23 de septiembre de 2019, 23:02:45 (UTC+2), Thomas Keffer 
>>>>> escribió:
>>>>>>
>>>>>> Is there error from a Spanish character in the template, or in 
>>>>>> skin.conf, or weewx.conf?
>>>>>>
>>>>>> Which template?
>>>>>>
>>>>>> Please include the log.
>>>>>>
>>>>>> -tk
>>>>>>
>>>>>> On Mon, Sep 23, 2019 at 10:46 AM Kike .Asekas  
>>>>>> wrote:
>>>>>>
>>>>>>> I get this error when I try using spanish characters (ñ,á,é,í,ó,ú). 
>>>>>>> I have #encoding UTF-8 in each page althougnt I 

Re: [weewx-user] 'ascii' codec can't decode byte 0xc3

[Kike .Asekas]

cheetahgenerator: Generate failed with exception ''
Sep 24 14:05:27 raspberrypi weewx[27767]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Seasons/index.html.tmpl
Sep 24 14:05:27 raspberrypi weewx[27767]: cheetahgenerator:  Reason: 
'ascii' codec can't decode byte 0xc3 in position 1815: ordinal not in 
range(128)
Sep 24 14:05:27 raspberrypi weewx[27767]:   Traceback (most recent call 
last):
Sep 24 14:05:27 raspberrypi weewx[27767]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 332, in generate
Sep 24 14:05:27 raspberrypi weewx[27767]:   
fd.write(str(compiled_template))
Sep 24 14:05:27 raspberrypi weewx[27767]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1045, in 
__str__
Sep 24 14:05:27 raspberrypi weewx[27767]:   rc = getattr(self, 
mainMethName)()
Sep 24 14:05:27 raspberrypi weewx[27767]: File 
"_etc_weewx_skins_Seasons_index_html_tmpl.py", line 216, in respond
Sep 24 14:05:27 raspberrypi weewx[27767]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1685, in 
_handleCheetahInclude
Sep 24 14:05:27 raspberrypi weewx[27767]:   file=file)
Sep 24 14:05:27 raspberrypi weewx[27767]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 772, in compile
Sep 24 14:05:27 raspberrypi weewx[27767]:   
settings=(compilerSettings or {}))
Sep 24 14:05:27 raspberrypi weewx[27767]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Compiler.py", line 1708, in 
__init__
Sep 24 14:05:27 raspberrypi weewx[27767]:   source = unicode(source)
Sep 24 14:05:27 raspberrypi weewx[27767]:   UnicodeDecodeError: 'ascii' 
codec can't decode byte 0xc3 in position 1815: ordinal not in range(128)


El martes, 24 de septiembre de 2019, 13:49:13 (UTC+2), Thomas Keffer 
escribió:
>
> It sure would help if you showed us the log...
>
> On Tue, Sep 24, 2019 at 4:27 AM Kike .Asekas  > wrote:
>
>> I sorry. I don't know where is the problem. I remove all spanish 
>> characters from skin.conf, index.html.tmpl and weewx.conf and I remove the 
>> template and copy it again from the git repository and the error continues.
>>
>> El martes, 24 de septiembre de 2019, 12:54:09 (UTC+2), Kike .Asekas 
>> escribió:
>>>
>>> I think is in skin.conf. I remove all spanish characters in the template 
>>> and the error continues. The template is index.html.tmpl
>>>
>>> El lunes, 23 de septiembre de 2019, 23:02:45 (UTC+2), Thomas Keffer 
>>> escribió:
>>>>
>>>> Is there error from a Spanish character in the template, or in 
>>>> skin.conf, or weewx.conf?
>>>>
>>>> Which template?
>>>>
>>>> Please include the log.
>>>>
>>>> -tk
>>>>
>>>> On Mon, Sep 23, 2019 at 10:46 AM Kike .Asekas  wrote:
>>>>
>>>>> I get this error when I try using spanish characters (ñ,á,é,í,ó,ú). I 
>>>>> have #encoding UTF-8 in each page althougnt I get the error in a page 
>>>>> only 
>>>>> and i have encoding = utf8 in [CheetahGenerator] in skin.conf.
>>>>>
>>>>> -- 
>>>>> 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/1b478f7f-8c11-41f5-93dd-24bee5f39ff0%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/weewx-user/1b478f7f-8c11-41f5-93dd-24bee5f39ff0%40googlegroups.com?utm_medium=email_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/9b51bca4-22ac-4a2e-8525-2ada1ad7537e%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/9b51bca4-22ac-4a2e-8525-2ada1ad7537e%40googlegroups.com?utm_medium=email_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/3d534392-8fea-4c0b-b357-d63126010a1f%40googlegroups.com.

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

[Kike .Asekas]

I have some small gaps in the graphics that I don't know because they 
appear since those records exist in the database.
What can they be due to?

[image: Screenshot_2019-09-24 Areal, Padrón Weather Conditions.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/231950ff-48fe-482f-af71-b012c12f4225%40googlegroups.com.

Re: [weewx-user] 'ascii' codec can't decode byte 0xc3

[Kike .Asekas]

I sorry. I don't know where is the problem. I remove all spanish characters 
from skin.conf, index.html.tmpl and weewx.conf and I remove the template 
and copy it again from the git repository and the error continues.

El martes, 24 de septiembre de 2019, 12:54:09 (UTC+2), Kike .Asekas 
escribió:
>
> I think is in skin.conf. I remove all spanish characters in the template 
> and the error continues. The template is index.html.tmpl
>
> El lunes, 23 de septiembre de 2019, 23:02:45 (UTC+2), Thomas Keffer 
> escribió:
>>
>> Is there error from a Spanish character in the template, or in skin.conf, 
>> or weewx.conf?
>>
>> Which template?
>>
>> Please include the log.
>>
>> -tk
>>
>> On Mon, Sep 23, 2019 at 10:46 AM Kike .Asekas  wrote:
>>
>>> I get this error when I try using spanish characters (ñ,á,é,í,ó,ú). I 
>>> have #encoding UTF-8 in each page althougnt I get the error in a page only 
>>> and i have encoding = utf8 in [CheetahGenerator] in skin.conf.
>>>
>>> -- 
>>> 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/1b478f7f-8c11-41f5-93dd-24bee5f39ff0%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/1b478f7f-8c11-41f5-93dd-24bee5f39ff0%40googlegroups.com?utm_medium=email_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/9b51bca4-22ac-4a2e-8525-2ada1ad7537e%40googlegroups.com.

Re: [weewx-user] 'ascii' codec can't decode byte 0xc3

[Kike .Asekas]

I think is in skin.conf. I remove all spanish characters in the template 
and the error continues. The template is index.html.tmpl

El lunes, 23 de septiembre de 2019, 23:02:45 (UTC+2), Thomas Keffer 
escribió:
>
> Is there error from a Spanish character in the template, or in skin.conf, 
> or weewx.conf?
>
> Which template?
>
> Please include the log.
>
> -tk
>
> On Mon, Sep 23, 2019 at 10:46 AM Kike .Asekas  > wrote:
>
>> I get this error when I try using spanish characters (ñ,á,é,í,ó,ú). I 
>> have #encoding UTF-8 in each page althougnt I get the error in a page only 
>> and i have encoding = utf8 in [CheetahGenerator] in skin.conf.
>>
>> -- 
>> 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/1b478f7f-8c11-41f5-93dd-24bee5f39ff0%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/1b478f7f-8c11-41f5-93dd-24bee5f39ff0%40googlegroups.com?utm_medium=email_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/9460682d-1b36-45a5-9ab6-d140aeb61b80%40googlegroups.com.

[weewx-user] 'ascii' codec can't decode byte 0xc3

[Kike .Asekas]

I get this error when I try using spanish characters (ñ,á,é,í,ó,ú). I have 
#encoding UTF-8 in each page althougnt I get the error in a page only and i 
have encoding = utf8 in [CheetahGenerator] in skin.conf.

-- 
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/1b478f7f-8c11-41f5-93dd-24bee5f39ff0%40googlegroups.com.

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

[Kike .Asekas]

For now everything perfect. There was no more database locked.

What I don't get to work is yaxis_minorTicks.


-- 
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/566aab83-49ab-4718-a649-3ef3aa5b9a62%40googlegroups.com.

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

[Kike .Asekas]

A question, can generate be in second level [[..]]  or only in top 
level []?


-- 
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/a44c9c84-1025-4993-b795-f0f8f31276ed%40googlegroups.com.

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

[Kike .Asekas]

Hi. I have been testing the new version for a few hours, for now it seems 
that everything is going perfect but I need more time to know it completely. 
Before 
I did a database lock about once a day. I'll tell you if there is more 
database lock or not.
As now I have the possibility of having more graphics I would like to have 
some graphs of the days that it rains in each month and another with the 
days that the temperature passes 30º but I don't know how to do them if it 
is possible. It would be nice to have that possibility.

El miércoles, 18 de septiembre de 2019, 14:23:28 (UTC+2), Pat escribió:
>
> Kike, how is the generate option working for you? So far in my tested it 
> is working well. 
>
> On Monday, September 16, 2019 at 8:33:10 PM UTC-4, Pat wrote:
>>
>> Kike, I've added my draft of the generate option. You will need to 
>> upgrade to the 1.1 beta skin by downloading it from the Belchertown's 
>> GitHub development branch 
>> .
>>
>> Once you have upgraded, for information on how it works, why it works 
>> like that and how to use it, refer to the wiki's generate option 
>> 
>>  
>> section. 
>>
>

-- 
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/9f224b84-4c40-492d-aba5-fb402d1066e6%40googlegroups.com.

[weewx-user] Re: SDR driver don't kill your last process and it's unable to restart

[Kike .Asekas]

I have made a change to the code. I added
import psutil
and
for proc in psutil.process_iter():
   if any(procstr in proc.name() for procstr in ['rtl_433']):
  loginf("Killing rtl_433")
  proc.kill()
in the class procmanager() in the function startup.
It works.

-- 
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/bde7521b-6d93-48e2-80b6-0643be9721d9%40googlegroups.com.

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

[Kike .Asekas]

I saw the news of this change this morning. What good news. But I still 
couldn't prove it. I hope to try it tomorrow. I will keep you informed. 
Thank you.

El miércoles, 18 de septiembre de 2019, 14:23:28 (UTC+2), Pat escribió:
>
> Kike, how is the generate option working for you? So far in my tested it 
> is working well. 
>
> On Monday, September 16, 2019 at 8:33:10 PM UTC-4, Pat wrote:
>>
>> Kike, I've added my draft of the generate option. You will need to 
>> upgrade to the 1.1 beta skin by downloading it from the Belchertown's 
>> GitHub development branch 
>> .
>>
>> Once you have upgraded, for information on how it works, why it works 
>> like that and how to use it, refer to the wiki's generate option 
>> 
>>  
>> section. 
>>
>

-- 
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/8f5e7e0d-1197-444a-96bf-dbfb2156de98%40googlegroups.com.

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

[Kike .Asekas]

I want to try it. I'm looking at the code but I don't know if I'll be able 
to change it. I'm still getting it.
I have been looking at the documentation of the weewx github wiki and I 
think that in this skin that obtains the data with ajax it is not necessary 
all the weewx page generation infrastructure to generate the same page at 
each turn.
https://github.com/weewx/weewx/wiki/dashboards
Wouldn't it be interesting to have the skin as described in Scenario 3: 
Upload LOOP / REC data to public-facing front-end? Weewx would handle 
calculations, conversion, storage in the bd, publication in wu and others 
and generate the json necessary for the skin but not the generation of web 
pages.

How about? Would it be a lot of change?

-- 
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/bca58328-20a2-44f6-8440-a78e88abb10c%40googlegroups.com.

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

[Kike .Asekas]

Thanks for your answer. I thought of using a new page for that series of 
graphics to put in cheetahgenerator in skin.conf that I generate it every 
month but I think I don't get anything with that because even if it is 
another page the generation is in graphs.conf and they are generated equally in 
every turn.
I hope I can help you, but I don't know if I will have enough knowledge to 
do it.
Greetings


El lunes, 16 de septiembre de 2019, 12:41:01 (UTC+2), Pat escribió:
>
> Hi Kike, I'm glad you're enjoying the skin. You've mentioned this problem 
> of yours before 
> <https://groups.google.com/d/msg/weewx-user/VyVMEfuxClo/n8D_YVjbAQAJ>. I 
> have it written down to look into. I volunteer my time to this project and 
> haven't had enough time to add this feature to development. 
>
> If you implement a way to do this before I can, a pull request is welcomed 
> so it can be added in. It could possibly take the "crontab" approach of 
> "generate = daily" or "generate = hourly" in the graph group. Then 
> belchertown.py would have to translate that to a timestamp and compare that 
> on every run. A lot of testing would have to take place.  
>
> On Monday, September 16, 2019 at 4:30:26 AM UTC-4, Kike .Asekas wrote:
>>
>> This skin allows us to make amazing graphics and this makes us want to 
>> have many.
>> The problem is that when we want to make a graph that compares the 
>> average temperatures of the last 10 years per month and another similar 
>> with the rain, it causes in my rpi 2b + to have blockages in the database 
>> when it coincides that weewx is writing in the database.
>> These graphs do not need to be made at each turn because only the last 
>> query will change minimally and the queries are repeated to obtain data 
>> already calculated and that do not vary. I believe that something would 
>> have to be changed so that only the last query (the last month of the last 
>> year in the example) should be done and take advantage of the previous json 
>> data. I don't know if it's possible or complicated to do this.
>> Another way could be marking some graphs so that they are not generated 
>> every turn.
>> In my case with the rpi in theory I can have amazing graphics but in 
>> practice I have to remove them by having many queries that cause me to have 
>> blockages and data loss.
>>
>

-- 
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/08173a53-f985-4b09-8e6f-aa5001d0c544%40googlegroups.com.

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

[Kike .Asekas]

This skin allows us to make amazing graphics and this makes us want to have 
many.
The problem is that when we want to make a graph that compares the average 
temperatures of the last 10 years per month and another similar with the 
rain, it causes in my rpi 2b + to have blockages in the database when it 
coincides that weewx is writing in the database.
These graphs do not need to be made at each turn because only the last 
query will change minimally and the queries are repeated to obtain data 
already calculated and that do not vary. I believe that something would 
have to be changed so that only the last query (the last month of the last 
year in the example) should be done and take advantage of the previous json 
data. I don't know if it's possible or complicated to do this.
Another way could be marking some graphs so that they are not generated 
every turn.
In my case with the rpi in theory I can have amazing graphics but in 
practice I have to remove them by having many queries that cause me to have 
blockages and data loss.

-- 
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/e258d446-ea7e-4c66-b3b7-00a7f4e5f678%40googlegroups.com.

[weewx-user] SDR driver don't kill your last process and it's unable to restart

[Kike .Asekas]

I am having problems with the sdr driver as a result of having a page with 
many queries that causes after a few hours when weewx writes in the 
database it gives the database is locked error. 
I also don't understand why weewx doesn't wait for the query to finish 
before writing.
When this happens, weewx restart but the sdr driver is unable to boot 
because there is another process rtl_433 running and it gives the error 
usb_claim_interface error -6. 
The driver enters in a loop that does not come out until I stop weewx, kill 
the rtl_433 process and start weewx again
I think the problem is that the previous rtl_433 process was not killed.

Sep 16 00:06:03 raspberrypi weewx[21121]: manager: Added record 2019-09-16 
00:05:00 CEST (1568585100) to database 'weewx.sdb'
Sep 16 00:06:03 raspberrypi weewx[21121]: manager: Added record 2019-09-16 
00:05:00 CEST (1568585100) to daily summary in 'weewx.sdb'
Sep 16 00:06:08 raspberrypi weewx[21121]: engine: Main loop exiting. 
Shutting engine down.
Sep 16 00:06:08 raspberrypi weewx[21121]: engine: Shutting down StdReport 
thread
Sep 16 00:06:09 raspberrypi weewx[21121]: Belchertown Extension: 
Query:SELECT strftime("%m", datetime(dateTime, "unixepoch")) as month, 
IFNULL(sum(rain),0) as obs FROM archive WHERE dateTime >= 1420066800 AND 
dateTime <= 1451602800 GROUP BY month;
Sep 16 00:06:14 raspberrypi weewx[21121]: reportengine: Caught 
unrecoverable exception in generator 
'user.belchertown.HighchartsJsonGenerator'
Sep 16 00:06:14 raspberrypi weewx[21121]:   database is locked
Sep 16 00:06:14 raspberrypi weewx[21121]:   Traceback (most 
recent call last):
Sep 16 00:06:14 raspberrypi weewx[21121]: File 
"/usr/share/weewx/weewx/reportengine.py", line 204, in run
Sep 16 00:06:14 raspberrypi weewx[21121]:   obj.start()
Sep 16 00:06:14 raspberrypi weewx[21121]: File 
"/usr/share/weewx/weewx/reportengine.py", line 300, in start
Sep 16 00:06:14 raspberrypi weewx[21121]:   self.run()
Sep 16 00:06:14 raspberrypi weewx[21121]: File 
"/usr/share/weewx/user/belchertown.py", line 1205, in run
Sep 16 00:06:14 raspberrypi weewx[21121]:   series_data = 
self._getObservationData(binding, archive, observation_type, minstamp, 
maxstamp, aggregate_type, aggregate_interval, time_length, xaxis_groupby, 
xaxis_categories, mirrored_value)
Sep 16 00:06:14 raspberrypi weewx[21121]: File 
"/usr/share/weewx/user/belchertown.py", line 1592, in _getObservationData
Sep 16 00:06:14 raspberrypi weewx[21121]:   for row in 
query:
Sep 16 00:06:14 raspberrypi weewx[21121]: File 
"/usr/share/weewx/weewx/manager.py", line 407, in genSql
Sep 16 00:06:14 raspberrypi weewx[21121]:   for _row in 
_cursor.execute(sql, sqlargs):
Sep 16 00:06:14 raspberrypi weewx[21121]: File 
"/usr/share/weewx/weedb/sqlite.py", line 43, in guarded_fn
Sep 16 00:06:14 raspberrypi weewx[21121]:   raise 
weedb.OperationalError(e)
Sep 16 00:06:14 raspberrypi weewx[21121]:   OperationalError: 
database is locked
Sep 16 00:06:14 raspberrypi weewx[21121]:   Generator terminated
Sep 16 00:06:14 raspberrypi weewx[21121]: sdr: MainThread: shutdown process 
rtl_433 -q -F json -R 32 -M utc -f 868.3M
Sep 16 00:06:24 raspberrypi weewx[21121]: sdr: MainThread: timed out 
waiting for stdout-thread
Sep 16 00:06:34 raspberrypi weewx[21121]: sdr: MainThread: timed out 
waiting for stderr-thread
Sep 16 00:06:34 raspberrypi weewx[21121]: engine: Database OperationalError 
exception: database is locked
Sep 16 00:06:34 raspberrypi weewx[21121]:   Waiting 2 minutes then 
retrying...
Sep 16 00:08:34 raspberrypi weewx[21121]: engine: retrying...
Sep 16 00:08:34 raspberrypi weewx[21121]: engine: Using configuration file 
/etc/weewx/weewx.conf
Sep 16 00:08:34 raspberrypi weewx[21121]: engine: Loading station type SDR 
(user.sdr)
Sep 16 00:08:34 raspberrypi weewx[21121]: sdr: MainThread: driver version 
is 0.64
Sep 16 00:08:34 raspberrypi weewx[21121]: sdr: MainThread: sensor map is 
{'windGust': 'wind_gust.*.FOWHx080Packet', 'windDir': 
'wind_dir.*.FOWHx080Packet', 'windSpeed': 'wind_speed.*.FOWHx080Packet', 
'outTemp': 'temperature.*.FOWHx080Packet', 'outHumidity': 
'humidity.*.FOWHx080Packet', 'rain_total': 'rain_total.*.FOWHx080Packet', 
'battery': 'battery.*.FOWHx080Packet'}
Sep 16 00:08:34 raspberrypi weewx[21121]: sdr: MainThread: deltas is 
{'rain': 'rain_total'}
Sep 16 00:08:34 raspberrypi weewx[21121]: sdr: MainThread: startup process 
'rtl_433 -q -F json -R 32 -M utc -f 868.3M'
...
...
Sep 16 00:08:35 raspberrypi weewx[21121]: engine: Starting main packet loop.
Sep 16 00:08:35 raspberrypi weewx[21121]: sdr: MainThread: err: ['rtl_433 
version unknown inputs file rtl_tcp RTL-SDR\n', 'Trying conf file at 
"rtl_433.conf"...\n', 'Trying conf file at 
"/root/.config/rtl_433/rtl_433.conf"...\n', 'Trying 

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

[Kike .Asekas]

I have found the fault. I had to modify belchertown.js.tmpl and add my page 
to variable pages


-- 
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/d5fb110f-0408-47d7-a608-1a32d15bbbe9%40googlegroups.com.

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

[Kike .Asekas]

Thank you very much, Pat but I don't get it to work. I try to put the 
graphics on the about page and it work but not in my page.
The page appears but not the graphics. I modify skin.conf with
[CheetahGenerator]
   [[ToDate]]
   [[[clima]]]
 template = clima/index.html.tmpl
and
[Labels]
  [[Generic]]
   nav_clima = Clima

In header.html.tmpl I added
   $ obs.label.nav_clima  < / 
a> 

My graphs.conf
[clima]
title = Lluvia por Mes
type = column
time_length=all
[[rainmonthtotals]]
   title = Histórico de Lluvia por Mes
   xaxis_groupby = month
...

And the index.html.tmpl page
#errorCatcher Echo
#encoding UTF-8
#set global $page = "clima"
#include "header.html.tmpl"


https://schema.org/CreativeWork;>
#include "page-header.inc"
showChart("clima");




#include "footer.html.tmpl"
 
I do not find the error. But the graphics do appear on the page about if I 
put
 showChart ("about"); 
and changing in graph.conf
[clima] by [about]
- mostrar texto citado -


El martes, 10 de septiembre de 2019, 14:03:39 (UTC+2), Pat escribió:
>
> Creating a custom page isn't documented but it's not hard. Just copy how 
> the other pages are created:
>
> 1. Create a new folder and create the index.html.tmpl within (copy the 
> file from /about as a starter)
> 2. Then add this new folder to the navigation within header.html.tmpl. 
> 3. Create the graphs you want in graphs.conf as you normally would. 
> 4. Initialize and add the chart to your new page. 
>
>
> Let's use this graphs.conf as an example - it is how I show rx check 
> percent on my about page <http://belchertownweather.com/go/about>. 
>
> [about]
> show_button = false
> time_length = 172800 # 48 hours in seconds
> aggregate_type = last
> aggregate_interval = 300 # 5 min
> gapsize = 30 # 5 min
> 
> [[rxchart]]
> title = ISS Receive Stats
> yaxis_max = 100
> [[[rxCheckPercent]]]
> color = "#268bd2"
> 
> [[rxchartyear]]
> title = ISS Receive Stats Average
> yaxis_max = 100
> xaxis_groupby = month
> xaxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul'
> , 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
> time_length = year
> [[[rxCheckPercent]]]
> aggregate_type = avg
> color = "#268bd2"
>
>
> Then in the content of your new page, you need to add 2 things. 
>
> 1. At the top of the page add:
>  
> showChart("about");
>
> This initializes the graphs.conf group "about". You see this matches the 
> [about] wording in the graph.conf group. 
>
>
> 2. Then where you want to show the graph within the page, add a div with 
> an ID of the observation from the graph group that you want to show:
>
> 
> 
>
>
> You will see how the id= matches the observations within the double 
> brackets. [[rxchart]] and [[rxchartyear]]]
>
> Obviously swap out the graph group and observation names with what you're 
> building and that should do it. 
>
>
>
> On Tuesday, September 10, 2019 at 5:00:11 AM UTC-4, Kike .Asekas wrote:
>>
>> Is there any way to create another graphic page? I mean, a page called 
>> for example climate where it has specific graphics.
>> Where would the graph.conf of that page go?
>>
>

-- 
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/5c176dab-2158-4464-8acd-f78c9f605b8d%40googlegroups.com.

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

[Kike .Asekas]

Thank you very much but I don't get it to work. I try to put the graphics 
on the about page and it work but not in my page.
The page appears but not the graphics. I modify skin.conf with
[CheetahGenerator]
   [[ToDate]]
   [[[clima]]]
 template = clima/index.html.tmpl
and
[Labels]
  [[Generic]]
   nav_clima = Clima

In header.html.tmpl I added
   $ obs.label.nav_clima  < / 
a> 

My graphs.conf
[clima]
title = Lluvia por Mes
type = column
time_length=all
[[rainmonthtotals]]
   title = Histórico de Lluvia por Mes
...

And the index.html.tmpl page
#errorCatcher Echo
#encoding UTF-8
#set global $page = "clima"
#include "header.html.tmpl"


https://schema.org/CreativeWork;>
#include "page-header.inc"
#include "about.inc.example"
showChart("clima");




#include "footer.html.tmpl"

I don´t find the error. 
I do not find the error. But the graphics do appear on the page about if I 
put
 showChart ("about"); 
and changing in graph.conf
[clima] by [about]

El martes, 10 de septiembre de 2019, 14:03:39 (UTC+2), Pat escribió:
>
> Creating a custom page isn't documented but it's not hard. Just copy how 
> the other pages are created:
>
> 1. Create a new folder and create the index.html.tmpl within (copy the 
> file from /about as a starter)
> 2. Then add this new folder to the navigation within header.html.tmpl. 
> 3. Create the graphs you want in graphs.conf as you normally would. 
> 4. Initialize and add the chart to your new page. 
>
>
> Let's use this graphs.conf as an example - it is how I show rx check 
> percent on my about page <http://belchertownweather.com/go/about>. 
>
> [about]
> show_button = false
> time_length = 172800 # 48 hours in seconds
> aggregate_type = last
> aggregate_interval = 300 # 5 min
> gapsize = 30 # 5 min
> 
> [[rxchart]]
> title = ISS Receive Stats
> yaxis_max = 100
> [[[rxCheckPercent]]]
> color = "#268bd2"
> 
> [[rxchartyear]]
> title = ISS Receive Stats Average
> yaxis_max = 100
> xaxis_groupby = month
> xaxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul'
> , 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
> time_length = year
> [[[rxCheckPercent]]]
> aggregate_type = avg
> color = "#268bd2"
>
>
> Then in the content of your new page, you need to add 2 things. 
>
> 1. At the top of the page add:
>  
> showChart("about");
>
> This initializes the graphs.conf group "about". You see this matches the 
> [about] wording in the graph.conf group. 
>
>
> 2. Then where you want to show the graph within the page, add a div with 
> an ID of the observation from the graph group that you want to show:
>
> 
> 
>
>
> You will see how the id= matches the observations within the double 
> brackets. [[rxchart]] and [[rxchartyear]]]
>
> Obviously swap out the graph group and observation names with what you're 
> building and that should do it. 
>
>
>
> On Tuesday, September 10, 2019 at 5:00:11 AM UTC-4, Kike .Asekas wrote:
>>
>> Is there any way to create another graphic page? I mean, a page called 
>> for example climate where it has specific graphics.
>> Where would the graph.conf of that page go?
>>
>

-- 
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/0aeaaa0d-6b6e-4317-8189-8611f5d88787%40googlegroups.com.

[weewx-user] Re: Hang up weewx and strange log

[Kike .Asekas]

Is that. But weewx have the sdr driver that does not query the console. I 
don't know how it appears writing at 7:31 a 1:25 record. And that after 
turning off and on the rpi.
Now I have to find out why the restart of the rpi, I look at the syslog. Any 
advice on where to look?

El martes, 10 de septiembre de 2019, 16:29:05 (UTC+2), vince escribió:
>
> I think your pi rebooted sometime after 01:51 - that explains the time 
> going backwards (it used the last-known time) and the different process id 
> (it 'is' a different process).   The duplicate archive record is possibly 
> due to weewx getting whatever's stored in your station's memory/logger.  I 
> wouldn't worry about that one.
>
>>

-- 
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/99bd465e-13f9-453a-92b2-f1fcc7ae8beb%40googlegroups.com.

[weewx-user] Re: Hang up weewx and strange log

[Kike .Asekas]

Thanks for your answer. I don't have RTC but I've never had that problem 
with the rpi and I've been using it for years.
I had not noticed the PID. And that gave me the clue. I have looked at the 
syslog of the Rpi and there was a restart for some reason. When restarting, 
it did it with the late date. I understand that raspbian consults the time 
as soon as the network is available, so I don't know why it restarted with 
the late time. Soon it hung up (1:23).
In the morning to see that the page was not going and I could not access by 
ssh to the rpi I had to turn it off and on.
What I do not understand is how at 7:32 weewx gives an error when writing a 
record of 1:25. Where it was stored?

El martes, 10 de septiembre de 2019, 10:57:27 (UTC+2), Andrew Milner 
escribió:
>
> I think you have several issues involved here
> 1) when things are running ok - weewx has a PID of 343
> 2) there is no explanation of why a new version of weewx with PID of 326 
> is started - but the clock is wrong - so from this point onwards you will 
> have very mixed results!!  With an RPi you should install a real time clock 
> for consistency as time is vital to correct running of weewx.
> 3) now you start with PID of 326 and 331 and finally the clock updates
>
> The error will relate to records already in the database with the same 
> time as the new record - and the cause will liely be connected to wrong 
> clock times somewhere along the line
>
> In all it looks more like an RPi problem - possibly power supply related 
> or possibly indicating an impending failure of the SD card
>
>
>
>
> On Tuesday, 10 September 2019 10:17:49 UTC+3, Kike .Asekas wrote:
>>
>> This morning I discovered that weewx had stopped tonight. The log:
>> Sep 10 01:51:13 raspberrypi weewx[343]: imagegenerator: Generated 13 
>> images for SeasonsReport in 6.09 seconds
>> Sep 10 01:51:14 raspberrypi weewx[343]: copygenerator: copied 0 files to 
>> /var/www/html/weewx
>> *Sep 10 01:51:14* raspberrypi weewx[343]: imageStackedWindRose: 
>> Generated 1 images for StackedWindRose in 0.46 seconds
>> *Sep 10 01:22:46* raspberrypi weewx[326]: engine: Initializing weewx 
>> version 3.9.1
>> Sep 10 01:22:46 raspberrypi weewx[326]: engine: Using Python 2.7.16 
>> (default, Apr  6 2019, 01:42:57) #012[GCC 8.2.0]
>> Sep 10 01:22:46 raspberrypi weewx[326]: engine: Platform 
>> Linux-4.19.57+-armv6l-with-debian-10.0
>> Sep 10 01:22:46 raspberrypi weewx[326]: engine: Locale is 'es_ES.UTF-8'
>> Sep 10 01:22:46 raspberrypi weewx[326]: engine: pid file is 
>> /var/run/weewx.pid
>> Sep 10 01:22:46 raspberrypi weewx[259]: Starting weewx weather system: 
>> weewx.
>> Sep 10 01:22:47 raspberrypi weewx[331]: engine: Using configuration file 
>> /etc/weewx/weewx.conf
>> Sep 10 01:22:47 raspberrypi weewx[331]: engine: Loading station type SDR 
>> (user.sdr)
>> Sep 10 01:22:47 raspberrypi weewx[331]: sdr: MainThread: driver version 
>> is 0.64
>> Sep 10 01:22:47 raspberrypi weewx[331]: sdr: MainThread: sensor map is 
>> {'windGust': 'wind_gust.*.FOWHx080Packet', 'windDir': 
>> 'wind_dir.*.FOWHx080Packet', 'windSpeed': 'wind_speed.*.FOWHx080Packet', 
>> 'outTemp': 'temperature.*.FOWHx080Packet', 'outHumidity': 
>> 'humidity.*.FOWHx080Packet', 'rain_total': 'rain_total.*.FOWHx080Packet', 
>> 'battery': 'battery.*.FOWHx080Packet'}
>> Sep 10 01:22:47 raspberrypi weewx[331]: sdr: MainThread: deltas is 
>> {'rain': 'rain_total'}
>> Sep 10 01:22:47 raspberrypi weewx[331]: sdr: MainThread: startup process 
>> 'rtl_433 -q -F json -R 32 -M utc -f 868.3M'
>> Sep 10 01:22:47 raspberrypi weewx[331]: engine: StdConvert target unit is 
>> 0x11
>> Sep 10 01:22:48 raspberrypi weewx[331]: 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
>> Sep 10 01:22:48 raspberrypi weewx[331]: wxcalculate: The following 
>> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>> Sep 10 01:22:48 raspberrypi weewx[331]: engine: Archive will use data 
>> binding wx_binding
>> Sep 10 01:22:48 raspberrypi weewx[331]: engine: Record generation will be 
>> attempted in 'software'
>> Sep 10 01:22:48 raspberrypi weewx[331]: engine: Using archive interval of 
>> 300 seconds (software record generation)
>> Sep 10 01:22:49 raspberrypi we

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

[Kike .Asekas]

Is there any way to create another graphic page? I mean, a page called for 
example climate where it has specific graphics.
Where would the graph.conf of that page go?

-- 
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/59601ec1-3d6e-4421-9644-15036717238d%40googlegroups.com.

[weewx-user] Hang up weewx and strange log

[Kike .Asekas]

This morning I discovered that weewx had stopped tonight. The log:
Sep 10 01:51:13 raspberrypi weewx[343]: imagegenerator: Generated 13 images 
for SeasonsReport in 6.09 seconds
Sep 10 01:51:14 raspberrypi weewx[343]: copygenerator: copied 0 files to 
/var/www/html/weewx
*Sep 10 01:51:14* raspberrypi weewx[343]: imageStackedWindRose: Generated 1 
images for StackedWindRose in 0.46 seconds
*Sep 10 01:22:46* raspberrypi weewx[326]: engine: Initializing weewx 
version 3.9.1
Sep 10 01:22:46 raspberrypi weewx[326]: engine: Using Python 2.7.16 
(default, Apr  6 2019, 01:42:57) #012[GCC 8.2.0]
Sep 10 01:22:46 raspberrypi weewx[326]: engine: Platform 
Linux-4.19.57+-armv6l-with-debian-10.0
Sep 10 01:22:46 raspberrypi weewx[326]: engine: Locale is 'es_ES.UTF-8'
Sep 10 01:22:46 raspberrypi weewx[326]: engine: pid file is 
/var/run/weewx.pid
Sep 10 01:22:46 raspberrypi weewx[259]: Starting weewx weather system: 
weewx.
Sep 10 01:22:47 raspberrypi weewx[331]: engine: Using configuration file 
/etc/weewx/weewx.conf
Sep 10 01:22:47 raspberrypi weewx[331]: engine: Loading station type SDR 
(user.sdr)
Sep 10 01:22:47 raspberrypi weewx[331]: sdr: MainThread: driver version is 
0.64
Sep 10 01:22:47 raspberrypi weewx[331]: sdr: MainThread: sensor map is 
{'windGust': 'wind_gust.*.FOWHx080Packet', 'windDir': 
'wind_dir.*.FOWHx080Packet', 'windSpeed': 'wind_speed.*.FOWHx080Packet', 
'outTemp': 'temperature.*.FOWHx080Packet', 'outHumidity': 
'humidity.*.FOWHx080Packet', 'rain_total': 'rain_total.*.FOWHx080Packet', 
'battery': 'battery.*.FOWHx080Packet'}
Sep 10 01:22:47 raspberrypi weewx[331]: sdr: MainThread: deltas is {'rain': 
'rain_total'}
Sep 10 01:22:47 raspberrypi weewx[331]: sdr: MainThread: startup process 
'rtl_433 -q -F json -R 32 -M utc -f 868.3M'
Sep 10 01:22:47 raspberrypi weewx[331]: engine: StdConvert target unit is 
0x11
Sep 10 01:22:48 raspberrypi weewx[331]: 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
Sep 10 01:22:48 raspberrypi weewx[331]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Sep 10 01:22:48 raspberrypi weewx[331]: engine: Archive will use data 
binding wx_binding
Sep 10 01:22:48 raspberrypi weewx[331]: engine: Record generation will be 
attempted in 'software'
Sep 10 01:22:48 raspberrypi weewx[331]: engine: Using archive interval of 
300 seconds (software record generation)
Sep 10 01:22:49 raspberrypi weewx[331]: engine: Using binding 'wx_binding' 
to database 'weewx.sdb'
Sep 10 01:22:49 raspberrypi weewx[331]: manager: Starting backfill of daily 
summaries
Sep 10 01:22:49 raspberrypi weewx[331]: restx: StationRegistry: Station 
will be registered.
Sep 10 01:22:49 raspberrypi weewx[331]: restx: Wunderground: Posting not 
enabled.
Sep 10 01:22:49 raspberrypi weewx[331]: restx: PWSweather: Posting not 
enabled.
Sep 10 01:22:49 raspberrypi weewx[331]: restx: CWOP: Posting not enabled.
Sep 10 01:22:49 raspberrypi weewx[331]: restx: WOW: Posting not enabled.
Sep 10 01:22:49 raspberrypi weewx[331]: restx: AWEKAS: Posting not enabled.
Sep 10 01:22:49 raspberrypi weewx[331]: restx: MQTT: service version is 0.19
Sep 10 01:22:49 raspberrypi weewx[331]: restx: MQTT: binding to ['loop', 
'archive']
Sep 10 01:22:49 raspberrypi weewx[331]: restx: MQTT: topic is estacion/datos
Sep 10 01:22:49 raspberrypi weewx[331]: restx: MQTT: desired unit system is 
METRIC
Sep 10 01:22:49 raspberrypi weewx[331]: restx: MQTT: data will be uploaded 
to mqtt://broker.hivemq.com:1883
Sep 10 01:22:49 raspberrypi weewx[331]: engine: Starting up weewx version 
3.9.1
Sep 10 01:22:49 raspberrypi weewx[331]: engine: Starting main packet loop.
Sep 10 01:23:04 raspberrypi weewx[331]: restx: MQTT: Published record 
2019-09-10 01:22:58 CEST (1568071378)
*Sep 10 01:23:04* raspberrypi weewx[331]: restx: MQTT: Published record 
2019-09-10 01:22:58 CEST (1568071378)
*Sep 10 07:32:28* raspberrypi weewx[331]: restx: MQTT: Published record 
2019-09-10 07:32:24 CEST (1568093544)
Sep 10 07:32:29 raspberrypi weewx[331]: manager: *Unable to add record 
2019-09-10 01:25:00 CEST (1568071500) to database 'weewx.sdb': UNIQUE 
constraint failed: archive.dateTime*
Sep 10 07:32:30 raspberrypi weewx[331]: engine: Garbage collected 64 objects
*Sep 10 07:32:30* raspberrypi weewx[331]: restx: *MQTT: Published record 
2019-09-10 01:25:00 CEST (1568071500)*
Sep 10 07:32:31 raspberrypi weewx[331]: restx: StationRegistry: Published 
record 2019-09-10 01:25:00 CEST (1568071500)


At 1:51:14 it stops for some reason(no error) and restart and returns at 
1:22:46 !??. At 7:32 I realize it is stopped and restart weewx and 
in this 

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

[Kike .Asekas]

I know that it is not a problem of the skin, but it is caused by having 
graphics grouped by months with several years (5) in the queries. For some 
reason match the query with weewx writing in the database and skip that 
error.

I will try to help you but I don't have a high level of programming. The 
commits are supervised by you, right?

El domingo, 18 de agosto de 2019, 13:25:09 (UTC+2), Pat escribió:
>
> Database is locked is not a Belchertown skin problem. Did you open the 
> database while weewx was running?
>
> Belchertown is developed when I have spare time. Lately there hasn't been 
> much of that. If you see room for improvement that you can fix, feel free 
> to submit a Pull Request on the skin's GitHub 
> <https://github.com/poblabs/weewx-belchertown> and help me out!
>
>
> On Sunday, August 18, 2019 at 5:08:01 AM UTC-4, Kike .Asekas wrote:
>>
>> I have troubles with graphs with graphics with many queries for being 
>> several years . Graphs like the image. The error is database is locked. 
>> It would not be much of a problem but I use the sdr driver and weewx when 
>> blocking the database it starts from the beginning and when load the driver 
>> it gives an error because there is an instance of rtl_433 running and it is 
>> not able to launch a new instance for not having killed the process 
>> previous.
>> Surely it is a driver error, which does not kill the process well before 
>> leaving but the result is that it stops working.
>>
>> I think the skin should give an option in graphs.conf to configure when 
>> the graphics are generated. Because weather graphs like the one attached 
>> here is not necessary to launch them every round. Maybe just once a 
>> month would be enough.
>> El sábado, 1 de junio de 2019, 18:57:56 (UTC+2), Pat escribió:
>>>
>>> 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/9c0ca245-a116-4132-bdac-08bbcdea2247%40googlegroups.com.

[weewx-user] SDR driver problem.

[Kike .Asekas]

I have a problem with the sdr driver. The problem is that sdr does not kill 
the rtl_433 process and due to some graphs with many queries there are 
times that I get the database is locked error that causes weewx to restart, 
then loading the driver again gives the error and stays in a loop until I 
solve it manually and lose all the data.

Aug 14 02:05:32 raspberrypi weewx[9020]: engine: Main loop exiting. 
Shutting engine down.
Aug 14 02:05:32 raspberrypi weewx[9020]: engine: Shutting down StdReport 
thread
Aug 14 02:05:47 raspberrypi weewx[9020]: reportengine: Caught unrecoverable 
exception in generator 'user.belchertown.HighchartsJsonGenerator'
Aug 14 02:05:47 raspberrypi weewx[9020]:   database is locked
Aug 14 02:05:47 raspberrypi weewx[9020]:   Traceback (most 
recent call last):
Aug 14 02:05:47 raspberrypi weewx[9020]: File 
"/usr/share/weewx/weewx/reportengine.py", line 204, in run
Aug 14 02:05:47 raspberrypi weewx[9020]:   obj.start()
Aug 14 02:05:47 raspberrypi weewx[9020]: File 
"/usr/share/weewx/weewx/reportengine.py", line 300, in start
Aug 14 02:05:47 raspberrypi weewx[9020]:   self.run()
Aug 14 02:05:47 raspberrypi weewx[9020]: File 
"/usr/share/weewx/user/belchertown.py", line 1026, in run
Aug 14 02:05:47 raspberrypi weewx[9020]:   start_ts = 
archive.firstGoodStamp()
Aug 14 02:05:47 raspberrypi weewx[9020]: File 
"/usr/share/weewx/weewx/manager.py", line 215, in firstGoodStamp
Aug 14 02:05:47 raspberrypi weewx[9020]:   _row = 
self.getSql("SELECT MIN(dateTime) FROM %s" % self.table_name)
Aug 14 02:05:47 raspberrypi weewx[9020]: File 
"/usr/share/weewx/weewx/manager.py", line 395, in getSql
Aug 14 02:05:47 raspberrypi weewx[9020]:   
_cursor.execute(sql, sqlargs)
Aug 14 02:05:47 raspberrypi weewx[9020]: File 
"/usr/share/weewx/weedb/sqlite.py", line 43, in guarded_fn
Aug 14 02:05:47 raspberrypi weewx[9020]:   raise 
weedb.OperationalError(e)
Aug 14 02:05:47 raspberrypi weewx[9020]:   OperationalError: 
database is locked
Aug 14 02:05:47 raspberrypi weewx[9020]:   Generator terminated
Aug 14 02:05:47 raspberrypi weewx[9020]: sdr: MainThread: shutdown process 
rtl_433 -q -F json -R 32 -M utc -f 868.3M
Aug 14 02:05:57 raspberrypi weewx[9020]: sdr: MainThread: timed out waiting 
for stdout-thread
Aug 14 02:06:07 raspberrypi weewx[9020]: sdr: MainThread: timed out waiting 
for stderr-thread
Aug 14 02:06:07 raspberrypi weewx[9020]: engine: Database OperationalError 
exception: database is locked
Aug 14 02:06:07 raspberrypi weewx[9020]:   Waiting 2 minutes then 
retrying...
Aug 14 02:08:07 raspberrypi weewx[9020]: engine: retrying...
Aug 14 02:08:07 raspberrypi weewx[9020]: engine: Using configuration file 
/etc/weewx/weewx.conf
Aug 14 02:08:07 raspberrypi weewx[9020]: engine: Loading station type SDR 
(user.sdr)
Aug 14 02:08:07 raspberrypi weewx[9020]: sdr: MainThread: driver version is 
0.64
Aug 14 02:08:07 raspberrypi weewx[9020]: sdr: MainThread: sensor map is 
{'windGust': 'wind_gust.*.FOWHx080Packet', 'windDir': 
'wind_dir.*.FOWHx080Packet', 'windSpeed': 'wind_speed.*.FOWHx080Packet', 
'outTemp': 'temperature.*.FOWHx080Packet', 'outHumidity': 
'humidity.*.FOWHx080Packet', 'rain_total': 'rain_total.*.FOWHx080Packet', 
'battery': 'battery.*.FOWHx080Packet'}
Aug 14 02:08:07 raspberrypi weewx[9020]: sdr: MainThread: deltas is 
{'rain': 'rain_total'}
Aug 14 02:08:07 raspberrypi weewx[9020]: sdr: MainThread: startup process 
'rtl_433 -q -F json -R 32 -M utc -f 868.3M'
Aug 14 02:08:07 raspberrypi weewx[9020]: engine: StdConvert target unit is 
0x11
Aug 14 02:08:07 raspberrypi weewx[9020]: 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
Aug 14 02:08:07 raspberrypi weewx[9020]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Aug 14 02:08:07 raspberrypi weewx[9020]: engine: Archive will use data 
binding wx_binding
Aug 14 02:08:07 raspberrypi weewx[9020]: engine: Record generation will be 
attempted in 'software'
Aug 14 02:08:07 raspberrypi weewx[9020]: engine: Using archive interval of 
300 seconds (software record generation)
Aug 14 02:08:07 raspberrypi weewx[9020]: engine: Using binding 'wx_binding' 
to database 'weewx.sdb'
Aug 14 02:08:07 raspberrypi weewx[9020]: manager: Starting backfill of 
daily summaries
Aug 14 02:08:07 raspberrypi weewx[9020]: restx: StationRegistry: Station 
will be registered.
Aug 14 02:08:07 

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

[Kike .Asekas]

I have troubles with graphs with graphics with many queries for being 
several years . Graphs like the image. The error is database is locked. 
It would not be much of a problem but I use the sdr driver and weewx when 
blocking the database it starts from the beginning and when load the driver 
it gives an error because there is an instance of rtl_433 running and it is 
not able to launch a new instance for not having killed the process 
previous.
Surely it is a driver error, which does not kill the process well before 
leaving but the result is that it stops working.

I think the skin should give an option in graphs.conf to configure when the 
graphics are generated. Because weather graphs like the one attached here 
is not necessary to launch them every round. Maybe just once a month would 
be enough.
El sábado, 1 de junio de 2019, 18:57:56 (UTC+2), Pat escribió:
>
> 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/1f2d808e-76d7-4fa2-9d68-189a90ce31fc%40googlegroups.com.

[weewx-user] Re: WH1080 replacement?

[Kike .Asekas]

I think this is a great deal. Have UV and solar, wifi, works with alexa, 
google assistant, emits directly to weather underground and it's cheap. I 
have a FW1080 like you and this will be my next station
https://www.ambientweather.com/amws2902.html

El viernes, 16 de agosto de 2019, 22:39:02 (UTC+2), PJO escribió:
>
> I've been running WeeWX on a Raspberry Pi with a Fine Offset WH1080 more 
> or less trouble free (apart from random USB port lockups every few months) 
> for about 5 years. Lately I've been having issues more frequently and am 
> thinking about a replacement. Am interested to hear from others who 
> replaced a WH1080 with something else (other than a Davis system):
>
> What did you choose?
> Why?
> Happy with the result?
>
> The only thing I'm committed to is running WeeWX, preferably on a 
> Raspberry Pi. 
>
> Thanks.
>

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

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

[Kike .Asekas]

The lines are the same, but there are a shift.

-- 
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/23821004-45b8-4c75-bfbd-3d6a0ac27d03%40googlegroups.com.

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

[Kike .Asekas]

Now it's correct. I don't understand nothing. The graph data matches those 
of NOAA now and not before. day 2-31.1 day 3-30.6 day 4-28.4.



-- 
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/9ef4862a-2ecc-4ca0-8055-330885d67e1f%40googlegroups.com.

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

[Kike .Asekas]

It makes no sense to me. The maximum temperature of August 2 is 31.1 
regardless of the time scale. And in the graph if we put time_length = 
2592000 it is 27.9 and if we put time_length = month it is 31.1 which is 
the correct. Something is wrong.

El miércoles, 14 de agosto de 2019, 15:37:13 (UTC+2), Pat escribió:
>
> This makes sense. The NOAA reports would start on day 1 of the month. The 
> "time_length = month" also starts on day 1 of the month. 
>
> If you use numbers for the time_length, that is the time backwards from 
> right now. So that may go past day 1 of the month. 
>
> On Wednesday, August 14, 2019 at 7:13:50 AM UTC-4, Kike .Asekas wrote:
>>
>> If time_lenght is month instead of 2592000 the results are correct. Perhaps 
>> that is why in the year chart that has time_lenght = year they are also 
>> correct. Maybe if it were 31536000 no, I haven't tried it.
>>
>> El miércoles, 14 de agosto de 2019, 12:09:22 (UTC+2), Kike .Asekas 
>> escribió:
>>>
>>> Pat, I think there is an error in the month chart. The NOAA data does 
>>> not match the chart. Neither the minims nor the maxims. 
>>> You can see with the images that I send that the NOAA data does not 
>>> match the graph.
>>> The section of graph.conf
>>> [month]
>>> # Chart Timespan Defaults
>>> title = "Este Mes"
>>> show_button = true
>>> button_text = "Mes"
>>> type = spline
>>> time_length = 2592000 # Last 30 days
>>> tooltip_date_format = " LL"
>>> aggregate_type = max
>>> aggregate_interval = 86400 # 1 day
>>> gapsize = 8640 # 1 day in milliseconds
>>>
>>> [[chart1]]
>>> title = Temperatura
>>> [[[outTemp]]]
>>> zIndex = 1
>>> name = Max Temperature
>>> color = red
>>> [[[outTemp_min]]]
>>> name = Min Temperature
>>> observation_type = outTemp
>>> aggregate_type = min
>>> color = "#7cb5ec"
>>>
>>>

-- 
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/676e3a81-7b88-4839-841c-862c6c9019f9%40googlegroups.com.

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

[Kike .Asekas]

If time_lenght is month instead of 2592000 the results are correct. Perhaps 
that is why in the year chart that has time_lenght = year they are also 
correct. Maybe if it were 31536000 no, I haven't tried it.

El miércoles, 14 de agosto de 2019, 12:09:22 (UTC+2), Kike .Asekas escribió:
>
> Pat, I think there is an error in the month chart. The NOAA data does not 
> match the chart. Neither the minims nor the maxims. 
> You can see with the images that I send that the NOAA data does not match 
> the graph.
> The section of graph.conf
> [month]
> # Chart Timespan Defaults
> title = "Este Mes"
> show_button = true
> button_text = "Mes"
> type = spline
> time_length = 2592000 # Last 30 days
> tooltip_date_format = " LL"
> aggregate_type = max
> aggregate_interval = 86400 # 1 day
> gapsize = 8640 # 1 day in milliseconds
>
> [[chart1]]
> title = Temperatura
> [[[outTemp]]]
> zIndex = 1
> name = Max Temperature
> color = red
> [[[outTemp_min]]]
> name = Min Temperature
> observation_type = outTemp
> aggregate_type = min
> color = "#7cb5ec"
>
>

-- 
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/99409338-306c-4bbb-834c-c91a60aa17e9%40googlegroups.com.

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

[Kike .Asekas]

Pat, I think there is an error in the month chart. The NOAA data does not 
match the chart. Neither the minims nor the maxims. 
You can see with the images that I send that the NOAA data does not match 
the graph.
The section of graph.conf
[month]
# Chart Timespan Defaults
title = "Este Mes"
show_button = true
button_text = "Mes"
type = spline
time_length = 2592000 # Last 30 days
tooltip_date_format = " LL"
aggregate_type = max
aggregate_interval = 86400 # 1 day
gapsize = 8640 # 1 day in milliseconds

[[chart1]]
title = Temperatura
[[[outTemp]]]
zIndex = 1
name = Max Temperature
color = red
[[[outTemp_min]]]
name = Min Temperature
observation_type = outTemp
aggregate_type = min
color = "#7cb5ec"

-- 
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/6ff621ac-674e-4b60-aba9-86732cfe903d%40googlegroups.com.

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

[Kike .Asekas]

Pat, I have the graphs of each month compared to the historical average of 
that month and that of each year compared to the historical average of all 
the years.
I have modified line 1571 of belchertown.py with 2 queries. 

if observation == 'rainAvg':
  if xaxis_groupby == "year":
sql_lookup = 'SELECT strftime("{0}", datetime(dateTime, 
"unixepoch")) as {1}, (select sum(rain)/count 
(DISTINCT(strftime("%Y",datetime,"unixepoch"))) from archive) as obs from 
archive WHERE dateTime >= {4} AND dateTime <= {5}  GROUP BY {6};'.format( 
strformat, xaxis_groupby, aggregate_type, obs_lookup, start_ts, end_ts, 
xaxis_groupby )
  else:
sql_lookup = 'SELECT strftime("{0}", datetime(dateTime, 
"unixepoch")) as {1}, 
IFNULL({2}({3}),0)/count(DISTINCT(strftime("%Y",datetime,"unixepoch"))) as 
obs from archive WHERE dateTime >= {4} AND dateTime <= {5} GROUP BY 
{6};'.format( strformat, xaxis_groupby, aggregate_type, obs_lookup, 
start_ts, end_ts, xaxis_groupby )
else:
  sql_lookup = 'SELECT strftime("{0}", datetime(dateTime, 
"unixepoch")) as {1}, IFNULL({2}({3}),0) as obs FROM archive WHERE dateTime 
>= {4} AND dateTime <= {5} GROUP BY {6};'.format( strformat, xaxis_groupby, 
aggregate_type, obs_lookup, start_ts, end_ts, xaxis_groupby )
Y los graficos son estos:
   
I think that for this type of graphics you had to put an option to only 
generate them once a week or so because they do not vary anything between 
them and load the raspberry.


-- 
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/ff29a405-adb0-40b9-ae29-ad0e3dcf72e2%40googlegroups.com.

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

[Kike .Asekas]

Forget to put the graph.conf file. And comment that I created a new type 
called rainAvg as I put in the previous post to get the graphics.
[raintotals]
title = Lluvia por Mes
show_button = true
button_text = Totales Lluvia
type = column
time_length=all
[[rainmonthtotals]]
title = Histórico de Lluvia por Mes
subtitle = Lluvia por Mes Desde el Comienzo
xaxis_groupby = month
xaxis_categories = 'Ene', 'Feb', 'Mar', 'Abr', 'May', 'Jun', 'Jul', 
'Ago', 'Sep', 'Oct', 'Nov', 'Dic'
[[[rainAvg]]]
time_length = all
name = Media
[[[rainTotal2015]]]
name = 2015
yaxis_minorTicks = true
time_length = year_specific
year_specific=2015
observation_type = rainTotal
[[[rainTotal2016]]]
name = 2016
yaxis_minorTicks = true
time_length = year_specific
year_specific=2016
observation_type = rainTotal
[[[rainTotal2017]]]
name = 2017
yaxis_minorTicks = true
time_length = year_specific
year_specific=2017
observation_type = rainTotal
[[[rainTotal2018]]]
name = 2018
yaxis_minorTicks = true
time_length = year_specific
year_specific=2018
observation_type = rainTotal
[[[rainTotal2019]]]
name = 2019
yaxis_minorTicks = true
time_length = year_specific
year_specific=2019
observation_type = rainTotal


[[rainyeartotals]]
title = Historicos de Lluvia por Año
xaxis_groupby = year
time_length = all
[[[rainTotal]]]
name = Lluvia Total
[[[rainAvg]]]
xaxis_groupby = year
name= media


-- 
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/f4fb6785-14ce-4ae1-b634-fca807d8eaf1%40googlegroups.com.

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

[Kike .Asekas]

Pat, I have achieved the graphic I wanted. I have created a new variable 
called rainTotalAvg
I changed line 1571 and added:
if observation == 'rainTotalAvg':
 sql_lookup = 'SELECT strftime ("{0}", datetime (dateTime, 
"unixepoch")) as {1}, IFNULL ({2} ({3}), 0) / count (DISTINCT (strftime ("% 
Y" , datetime, "unixepoch"))) as obs from archive WHERE dateTime> = {4} AND 
dateTime <= {5} GROUP BY {6}; '. format (strformat, xaxis_groupby, 
aggregate_type, obs_lookup, start_ts, end_ts, xaxis_groupby )
else:
sql_lookup = 'SELECT strftime ("{0}", datetime (dateTime, "unixepoch")) 
as {1}, IFNULL ({2} ({3}), 0) as obs FROM archive WHERE dateTime> = {4} AND 
dateTime <= {5} GROUP BY {6}; '. Format (strformat, xaxis_groupby, 
aggregate_type, obs_lookup, start_ts, end_ts, xaxis_groupby)
 
Then modify lines 1138, 1191 and 1524 by adding 'or observation_type == 
"rainTotalAvg"'
The chart:
The blue column is the average of  other 3 or 2 from September.


-- 
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/0430cb1a-5e5d-4216-ab4d-2b3a45560a2d%40googlegroups.com.

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

[Kike .Asekas]

I thought that maybe I should do it with rain and not with rainTotal. I did 
a graph with:
[raintotals]
title = Lluvia por Mes
show_button = true
button_text = Media Lluvia
type = column
time_length=all
aggregate_type = avg
aggregate_interval = 2592000 # 1 week
[[rainmonthtotals]]
title = Histórico de Lluvia por Mes
subtitle = Lluvia por Mes Desde el Comienzo
xaxis_groupby = month
xaxis_categories = 'Ene', 'Feb', 'Mar', 'Abr', 'May', 'Jun', 'Jul', 
'Ago', 'Sep', 'Oct', 'Nov', 'Dic'
[[[rain]]]
name = Media
yaxis_minorTicks = true

and got something else, I thought it would be the average per day, but no.

I don't understand the aggregate_inteval parameter and its relationship 
with xasis_groupby. Maybe only one is necessary.
Ah! and I'm sorry, but the yaxis_minorticks parameter doesn't work.
The problem of to map graph.conf to highcharts maybe you could use the 
highcharts options as is and translate whatever is different as the equal 
for two points or whatever in graph.conf so that highcharts accept it as 
your options. I don't know if I understand the problem
Regards

El sábado, 1 de junio de 2019, 18:57:56 (UTC+2), Pat escribió:
>
> 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/1de2867e-9a9f-4203-8592-c5b84b228a47%40googlegroups.com.

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

[Kike .Asekas]

My graph is like you show. The blue column is the sum of 2017,2018 and 2019 
and I want the average of that years, the average of sum 2017,2018 and 2019 
but I try put agregate_type=avg for all columns and now i have the 3 years 
and the title of the blue column only.
I hope you understand me, I want the sum of rain in each year compared to 
the average in those years.
Regards.


El sábado, 10 de agosto de 2019, 15:12:46 (UTC+2), Pat escribió:
>
> I'm confused on the graph you're looking to create. Can you link me to a 
> graph that you saw somewhere as an example?
>
> Or is this what you're looking for?
>
>
> [raintotals]
> title = Rain Totals by Month
> show_button = true
> button_text = Rain Totals
> type = column
> time_length = all
> aggregate_type = max
> aggregate_interval = 86400 # 1 day
>
>
> [[rainmonthtotals]]
> title = Historico de Lluvia por Mes
> subtitle = Lluvia por Mes Desde el Comienzo
> xaxis_groupby = month
> xaxis_categories = 'Ene', 'Feb', 'Mar', 'Abr', 'May', 'Jun', 'Jul'
> , 'Ago', 'Sep', 'Oct', 'Nov', 'Dic'
> [[[rainTotal]]]
> name = Lluvia Total
> yaxis_minorTicks = true
> aggregate_type = avg
> [[[rainTotal2017]]]
> name = 2017
> time_length = year_specific
> year_specific = 2017
> observation_type=rainTotal
> [[[rainTotal2018]]]
> name = 2018
> time_length = year_specific
> year_specific = 2018
> observation_type=rainTotal 
> [[[rainTotal2019]]]
> name = 2019
> time_length=year_specific
> year_specific = 2019
> observation_type=rainTotal
>
>
>
>
> On Saturday, August 10, 2019 at 8:48:20 AM UTC-4, Kike .Asekas wrote:
>>
>> It works. Thank you very much.
>> But I just realized that in the chart the blue column is the sum of all 
>> years in database and I want to compare the average ofevery year with the 
>> sum of this year or any other. 
>> I tried it with aggregate_type = avg and maybe rainTotal doesn't admit it 
>> but the result is the same. My graph.conf file is:
>> [raintotals]
>> title = Lluvia por Mes
>> show_button = true
>> button_text = Totales Lluvia
>> type = column
>> time_length = all
>> aggregate_interval = 86400 # 1 day
>> [[rainmonthtotals]]
>> title = Historico de Lluvia por Mes
>> subtitle = Lluvia por Mes Desde el Comienzo
>> aggregate_type = avg
>> xaxis_groupby = month
>> xaxis_categories = 'Ene', 'Feb', 'Mar', 'Abr', 'May', 'Jun', 
>> 'Jul', 'Ago', 'Sep', 'Oct', 'Nov', 'Dic'
>> [[[rainTotal]]]
>> name = Lluvia Total
>> yaxis_minorTicks = true
>> [[[rainTotal2017]]]
>> name = 2017
>> time_length = year_specific
>> year_specific = 2017
>> observation_type=rainTotal
>> zIndex = 3
>> [[[rainTotal2018]]]
>> name = 2018
>> time_length = year_specific
>> year_specific = 2018
>> observation_type=rainTotal
>> zIndex = 4
>> [[[rainTotal2019]]]
>> name = 2019
>> time_length=year_specific
>> year_specific = 2019
>> observation_type=rainTotal
>> zIndex = 5
>>
>>
>> [[rainyeartotals]]
>> title = Historicos de Lluvia por Año
>> xaxis_groupby = year
>> [[[rainTotal]]]
>> name = Lluvia Total
>>
>> [[rain2018totals]]
>> title = Lluvia en 2018
>> xaxis_groupby = month
>> xaxis_categories = 'Ene', 'Feb', 'Mar', 'Abr', 'May', 'Jun', 
>> 'Jul', 'Ago', 'Sep', 'Oct', 'Nov', 'Dic'
>> time_length = year_specific
>> year_specific = 2019
>> [[[rainTotal]]]
>> name = Lluvia Total
>> 
>> [[rainyearstotals]]
>> title = Lluvia por Años
>> xaxis_groupby = month
>> xaxis_categories = 'Ene', 'Feb', 'Mar', 'Abr', 'May', 'Jun', 
>> 'Jul', 'Ago', 'Sep', 'Oct', 'Nov', 'Dic'
>> time_length = year_specific
>> [[[rainTotal2017]]]
>> year_specific = 2017
>> observation_type=rainTotal
>> name = 2017
>> [[[rainTotal2018]]]
>>   

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

[Kike .Asekas]

s data from the database during Archive time, not 
>> every option is available for all time. Currently I have to map a 
>> graphs.conf option to a Highcharts option. Maintaining this duplicate 
>> mapping system isn't ideal. So something like minorticks aren't implemented 
>> yet because nobody has asked for it (until now). You can read some of 
>> the thoughts here 
>> <https://github.com/poblabs/weewx-belchertown/issues/185>, and if you 
>> know of a way to pass graphs.conf options direct to belchertown.js.tmpl and 
>> Highcharts without maintaining a mapping, please submit a PR!
>>
>> Custom charts like what you're describing I don't think will work either. 
>> Each chart is for a specific time span. I don't think multiple timespans 
>> per chart will work. Some testing and debugging will need to be done here 
>> to see what can be done. 
>>
>>
>>
>> On Friday, August 9, 2019 at 8:13:31 AM UTC-4, Kike .Asekas wrote:
>>>
>>> Hello. Magnificent skin. I am triying to have a graph that compares the 
>>> historical rainfall per month with this year. This is my graphs.conf.
>>> [raintotals]
>>> title = Lluvia por Mes
>>> show_button = true
>>> button_text = Totales Lluvia
>>> type = column
>>> time_length = all
>>> aggregate_type = max
>>> 
>>> aggregate_interval = 86400 # 1 day
>>>
>>> [[rainmonthtotals]]
>>> title = Historico de Lluvia por Mes
>>> subtitle = Lluvia por Mes Desde el Comienzo
>>> xaxis_groupby = month
>>> xaxis_categories = 'Ene', 'Feb', 'Mar', 'Abr', 'May', 'Jun', 
>>> 'Jul', 'Ago', 'Sep', 'Oct', 'Nov', 'Dic'
>>> [[[rainTotal]]]
>>> name = Lluvia Total
>>> [[[rainTotal2019]]]
>>> name = 2019
>>> time_length = year_specific
>>> year_specific = 2019
>>> observation_type = rainTotal
>>> zIndex = 2
>>> color = "#fc0404"
>>> But I get two bars with the same height, the alltime totals. It is 
>>> posible this graph?
>>> And I want to add minorTicks to yaxis. It's a hicharts option but does 
>>> nothing. The skin only accept hicharts series options?
>>>
>>> El sábado, 1 de junio de 2019, 18:57:56 (UTC+2), Pat escribió:
>>>>
>>>> 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/dd075b86-b4a0-4432-9068-2d4f2d8ae816%40googlegroups.com.

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

[Kike .Asekas]

Hello. Magnificent skin. I am triying to have a graph that compares the 
historical rainfall per month with this year. This is my graphs.conf.
[raintotals]
title = Lluvia por Mes
show_button = true
button_text = Totales Lluvia
type = column
time_length = all
aggregate_type = max

aggregate_interval = 86400 # 1 day

[[rainmonthtotals]]
title = Historico de Lluvia por Mes
subtitle = Lluvia por Mes Desde el Comienzo
xaxis_groupby = month
xaxis_categories = 'Ene', 'Feb', 'Mar', 'Abr', 'May', 'Jun', 'Jul', 
'Ago', 'Sep', 'Oct', 'Nov', 'Dic'
[[[rainTotal]]]
name = Lluvia Total
[[[rainTotal2019]]]
name = 2019
time_length = year_specific
year_specific = 2019
observation_type = rainTotal
zIndex = 2
color = "#fc0404"
But I get two bars with the same height, the alltime totals. It is posible 
this graph?
And I want to add minorTicks to yaxis. It's a hicharts option but does 
nothing. The skin only accept hicharts series options?

El sábado, 1 de junio de 2019, 18:57:56 (UTC+2), Pat escribió:
>
> 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/2f73c7ce-dcba-430d-b229-67aee6c1532f%40googlegroups.com.

[weewx-user] Re: strange behavior with outtemp

[Kike .Asekas]

Thank you very much

El sábado, 3 de agosto de 2019, 16:04:29 (UTC+2), gjr80 escribió:
>
> I cannot add anything further, since the issue was with a day minimum the 
> problem almost certainly lay in the daily summaries. The fact the rebuild 
> fixed it confirms this. Perhaps there was some obscure problem that a 
> complete rebuild fixed but a day rebuild did not. At least it is working as 
> intended now.
>
> 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/daf707b3-8764-41a7-871b-72d07e1d3057%40googlegroups.com.

[weewx-user] Re: strange behavior with outtemp

[Kike .Asekas]

I did rebuid-daily without --today. Maybe it was necessary to use sudo? 
Although 
the owner of the file weewx.sdb is my user. All this happened to me before 
nightfall on day 8/1, and when I check the table archive_day_outtemp the 
max datetime was 7/31 22:00. I'm in GMT+2. 
In the archive table there was also no row with that temperature (0.0) and 
the graph did not reflect it. It was only in the section min temp of the 
day where that value continued to appear.
Hence my strangeness, because I didn't see that value either in archive or 
in archive_data_outtemp.I don't know where that data came from, but with 
drop_daily and rebuild_daily it was fixed.
El viernes, 2 de agosto de 2019, 8:22:17 (UTC+2), gjr80 escribió:
>
> When you say “it didn’t work for you” do you mean using —rebuild-daily 
> only (ie no —drop-daily first) or using —today? I don’t know why, 
> rebuilding just the affected day(s) is useful for retaining loop high/low 
> value and time stamps for unaffected days. Also, sometimes the daily 
> summary tables need to be dropped first (using —drop-daily) before you 
> rebuild them. 
>
> The daily summary tables are named ‘archive_day_’ where  is an 
> observation field in the archive table schema. So the outTemp daily summary 
> table is archive_day_outTemp. Each table consists of a single row per day, 
> the dateTime field for each row holds the midnight (local time) timestamp. 
> If I read your post correctly you mention the max outTemp timestamp for 1 
> August 2019 is midnight. That could be the case (unlikely but possible for 
> a day in the past also possible for the current day if you view the data 
> before sunrise). If you have concerns about the integrity of your data in 
> the daily summary the best approach is to check the archive table data for 
> that observation for that day and see whether the daily summary entry is 
> consistent with the archive data (eg when was the outTemp max on 1 August 
> according to the archive). During a rebuild the daily summary data is 
> derived from the archive so there should be no disagreement. 
>
> 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/cf983e58-3955-4e5a-a092-b9d5226a5f79%40googlegroups.com.

[weewx-user] Re: strange behavior with outtemp

[Kike .Asekas]

Thank you but It did not work for me. I did wee_database --drop-daily and 
rebuild-daily and now it works.
But i don't understand, I check archive_daily_outtemp and the max timestamp 
is from today at midnight(8-1-2109 0:00). Are the summaries not the ones on 
the daily tables?

El jueves, 1 de agosto de 2019, 22:12:23 (UTC+2), gjr80 escribió:
>
> Hi, 
>
> High/low data for days, weeks, months etc usually comes from the daily 
> summaries. If you modify the archive to remove/fix erroneous data you need 
> to rebuild the daily summaries using wee_database with the —rebuild-daily 
> option (http://weewx.com/docs/utilities.htm#Action_--rebuild-daily). In 
> your case I would rebuild just the day containing the erroneous data. 
>
> 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/bc345ec6-879e-43ba-8ea5-6d7adc5f3df2%40googlegroups.com.

[weewx-user] strange behavior with outtemp

[Kike .Asekas]

This morning I import data in the database with wee_import and put an 
incorrect data on the database. A temperature of 0.0ºC today. A peak 
appeared in the graph. I remove the bad data manually, it was a row only 
and restart weewx. In the following cycles the graph was correct but in hi 
lo still appearing 0.0 as a minimum temperature of the day. Delete all 
files in the web server and I waited for a new cycle and the minimum 
temperature was still 0.0. I check the database and there are no 0.0 
temperature today. I look at the file hilo.inc and the line is 
$archive[1].outTemp.min.format(add_label=False). 
I don't understand where that data comes from. In the database is not. 
What does it mean archive[1]?
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/85609657-ec88-4698-8892-d0eb05e68ef4%40googlegroups.com.

Re: [weewx-user] rain 10x

[Kike .Asekas]

   # The host where the database is located
host = localhost
# The user name for logging in to the host
user = weewx
# The password for the user name (quotes guard against parsing 
errors)
password = weewx

##

#   This section configures the internal weewx engine.

[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.extra_sensors_service.ExtraSensorsService,
process_services = weewx.engine.StdConvert, 
weewx.engine.StdCalibrate, weewx.engine.StdQC, 
weewx.wxservices.StdWXCalculate
archive_services = weewx.engine.StdArchive
restful_services = weewx.restx.StdStationRegistry, 
weewx.restx.StdWunderground, weewx.restx.StdPWSweather, 
weewx.restx.StdCWOP, weewx.restx.StdWOW, weewx.restx.StdAWEKAS, 
user.mqtt.MQTT
report_services = weewx.engine.StdPrint, weewx.engine.StdReport


El jueves, 25 de julio de 2019, 0:45:19 (UTC+2), Jardi Martínez escribió:
>
> On Wed, Jul 24, 2019, 1:18 PM Kike .Asekas > 
> wrote:
>
>> I have my weewx configured with METRICWX. In my station console indicates 
>> 0,9 mm of rain, but in weewx i have 9 mm. Where can the fault be?
>> Thank you.
>>
>> -- 
>>
> What station and driver are you using?
> Can you post your weewx.conf file?
>
> If all you want is for the reports to be in certain unit, you can do that 
> at in the reports section of your weewx.conf file. You don't need to change 
> the target unit for the observations stored in the database.
>
> Jardi.
>

-- 
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/b9e43729-9ec3-48b3-9f30-fdad9887c09d%40googlegroups.com.

[weewx-user] Re: rain 10x

[Kike .Asekas]

My weewx.conf
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2019 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 1

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 3.9.1

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = "Areal, Padrón"

# Latitude and longitude in decimal degrees
latitude = 42.8002
longitude = -8.63527

# Altitude of the station, with unit it is in. This is downloaded from
# from the station if the hardware supports it.
altitude = 57, meter

# Set to type of station hardware. There must be a corresponding stanza
# in this file with a 'driver' parameter indicating the driver to be 
used.
station_type = SDR

# If you have a website, you may specify an URL
#station_url = http://www.example.com

# The start of the rain year (1=January; 10=October, etc.). This is
# downloaded from the station if the hardware supports it.
rain_year_start = 1

# Start of week (0=Monday, 6=Sunday)
week_start = 6

##

[FineOffsetUSB]
# This section is for the Fine Offset series of weather stations.

# The station model, e.g., WH1080, WS1090, WS2080, WH3081
model = WS2080

# How often to poll the station for data, in seconds
polling_interval = 60

# The driver to use:
driver = weewx.drivers.fousb

##

[SDR]
driver = user.sdr
cmd = rtl_433 -q -F json -R 32 -M utc -f 868.3M
path = /usr/local/bin
#ld_library_path = /usr/local/lib:/opt/rtl-sdr/lib
[[sensor_map]]
windDir = wind_dir.*.FOWHx080Packet
windSpeed = wind_speed.*.FOWHx080Packet
outTemp = temperature.*.FOWHx080Packet
outHumidity = humidity.*.FOWHx080Packet
rain_total = rain_total.*.FOWHx080Packet
#inTemp = temperature.*.FOWHx080Packet
#inHumidity = humidity.*.FOWHx080Packet
[[deltas]]
rain = rain_total # derive rain from difference betrween successive 
rain_total   

##


#   This section is for uploading data to Internet sites

[StdRESTful]

[[StationRegistry]]
# To register this weather station with weewx, set this to true
register_this_station = true

[[AWEKAS]]
# This section is for configuring posts to AWEKAS.

# If you wish to do this, set the option 'enable' to true,
# and specify a username and password.
# To guard against parsing errors, put the password in quotes.
enable = false
username = replace_me
password = replace_me

[[CWOP]]
# This section is for configuring posts to CWOP.

# If you wish to do this, set the option 'enable' to true,
# and specify the station ID (e.g., CW1234).
enable = false
station = replace_me

# If this is an APRS (radio amateur) station, uncomment
# the following and replace with a passcode (e.g., 12345).
#passcode = replace_me (APRS stations only)

[[PWSweather]]
# This section is for configuring posts to PWSweather.com.

# If you wish to do this, set the option 'enable' to true,
# and specify a station and password.
# To guard against parsing errors, put the password in quotes.
enable = false
station = replace_me
password = replace_me

[[WOW]]
# This section is for configuring posts to WOW.

# If you wish to do this, set the option 'enable' to true,
# and specify a station and password.
# To guard against parsing errors, put the password in quotes.
enable = false
station = replace_me
password = replace_me

[[Wunderground]]
# This section is for configuring posts to the Weather Underground.

# If you wish to do this, set the option 'enable' to true,
# and specify a station (e.g., 'KORHOODR3') and password.
# To guard against parsing errors, put the password in quotes.
enable = false
station = replace_me

[weewx-user] rain 10x

[Kike .Asekas]

I have my weewx configured with METRICWX. In my station console indicates 
0,9 mm of rain, but in weewx i have 9 mm. Where can the fault be?
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/b53fd027-c6ac-4850-a63f-ac632085dae8%40googlegroups.com.

[weewx-user] Re: Incorrect time in reports

[Kike .Asekas]

Well. The problem was here. The SDR driver was not in utc.I put the 
parameter and all go well now. Thanks
Closed

El lunes, 15 de julio de 2019, 16:24:43 (UTC+2), Andrew Milner escribió:
>
> I suspect you should not be using the dateTime field in the SDR packet as 
> that appears to be a local time and not UTC time - this results in other 
> parts of weewx looking for dates in the future - which of course will not 
> be found.
>
>
>
> On Monday, 15 July 2019 17:17:03 UTC+3, Kike .Asekas wrote:
>>
>> The problem looks like is in current object in the datetime function I 
>> think. Where is the code of current object?
>>
>>
>>

-- 
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/bb2f08b0-a57f-4ccf-9626-abfd50cf1958%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Incorrect time in reports

[Kike .Asekas]

Well, the time in my database is in local time. Why?

El lunes, 15 de julio de 2019, 16:12:44 (UTC+2), Andrew Milner escribió:
>
> The dateTime in the database should be epoch time == UTC time, not local 
> time.
>
>
>
> On Monday, 15 July 2019 17:03:59 UTC+3, Kike .Asekas wrote:
>>
>>
>>
>> I delete the database. I see "cannot find start time" in the templates of 
>> the webpages.
>> The log:
>> Jul 15 15:55:51 raspberrypi weewx[11746]: Starting weewx weather system: 
>> weewx.
>> Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Using configuration 
>> file /etc/weewx/weewx.conf
>> Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Debug is 1
>> Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Initializing engine
>> Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Loading station type 
>> SDR (user.sdr)
>> Jul 15 15:55:52 raspberrypi weewx[11768]: sdr: MainThread: driver version 
>> is 0.64
>> Jul 15 15:55:52 raspberrypi weewx[11768]: sdr: MainThread: sensor map is 
>> {'windDir': 'wind_dir.*.FOWHx080Packet', 'windSpeed': 
>> 'wind_speed.*.FOWHx080Packet', 'outTemp': 'temperature.*.FOWHx080Packet', 
>> 'outHumidity': 'humidity.*.FOWHx080Packet', 'rain_total': 
>> 'rain_total.*.FOWHx080Packet', 'inTemp': 'temperature.*.FOWHx080Packet', 
>> 'inHumidity': 'humidity.*.FOWHx080Packet'}
>> Jul 15 15:55:52 raspberrypi weewx[11768]: sdr: MainThread: deltas is 
>> {'strikes': 'strikes_total', 'rain': 'rain_total'}
>> Jul 15 15:55:52 raspberrypi weewx[11768]: sdr: MainThread: startup 
>> process 'rtl_433 -q -F json -R 32 -f 868.3M'
>> Jul 15 15:55:52 raspberrypi weewx[11768]: sdr: stdout-thread: start async 
>> reader for stdout-thread
>> Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Loading service 
>> weewx.engine.StdTimeSynch
>> Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Finished loading 
>> service weewx.engine.StdTimeSynch
>> Jul 15 15:55:52 raspberrypi weewx[11768]: sdr: stderr-thread: start async 
>> reader for stderr-thread
>> Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Loading service 
>> user.extra_sensors_service.ExtraSensorsService
>> Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Finished loading 
>> service user.extra_sensors_service.ExtraSensorsService
>> Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Loading service 
>> weewx.engine.StdConvert
>> Jul 15 15:55:52 raspberrypi weewx[11768]: engine: StdConvert target unit 
>> is 0x11
>> Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Finished loading 
>> service weewx.engine.StdConvert
>> Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Loading service 
>> weewx.engine.StdCalibrate
>> Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Finished loading 
>> service weewx.engine.StdCalibrate
>> Jul 15 15:55:53 raspberrypi weewx[11768]: engine: Loading service 
>> weewx.engine.StdQC
>> Jul 15 15:55:53 raspberrypi weewx[11768]: engine: Finished loading 
>> service weewx.engine.StdQC
>> Jul 15 15:55:53 raspberrypi weewx[11768]: engine: Loading service 
>> weewx.wxservices.StdWXCalculate
>> Jul 15 15:55:53 raspberrypi weewx[11768]: 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
>> Jul 15 15:55:53 raspberrypi weewx[11768]: wxcalculate: The following 
>> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>> Jul 15 15:55:53 raspberrypi weewx[11768]: engine: Finished loading 
>> service weewx.wxservices.StdWXCalculate
>> Jul 15 15:55:53 raspberrypi weewx[11768]: engine: Loading service 
>> weewx.engine.StdArchive
>> Jul 15 15:55:53 raspberrypi weewx[11768]: engine: Archive will use data 
>> binding wx_binding
>> Jul 15 15:55:53 raspberrypi weewx[11768]: engine: Record generation will 
>> be attempted in 'software'
>> Jul 15 15:55:53 raspberrypi weewx[11768]: engine: Using archive interval 
>> of 300 seconds (software record generation)
>> Jul 15 15:55:53 raspberrypi weewx[11768]: engine: Use LOOP data in hi/low 
>> calculations: 1
>> Jul 15 15:55:53 raspberrypi weewx[11768]: manager: Created and 
>> initialized table 'archive' in database 'weewx.sdb'
>> Jul 15 15:55:54 raspberrypi weewx[11768]: m

[weewx-user] Re: Incorrect time in reports

[Kike .Asekas]

The problem looks like is in current object in the datetime function I 
think. Where is the code of current object?


-- 
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/e6cab7f9-09cb-454a-996c-3755800abfbc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Incorrect time in reports

[Kike .Asekas]

I delete the database. I see "cannot find start time" in the templates of 
the webpages.
The log:
Jul 15 15:55:51 raspberrypi weewx[11746]: Starting weewx weather system: 
weewx.
Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Using configuration file 
/etc/weewx/weewx.conf
Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Debug is 1
Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Initializing engine
Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Loading station type SDR 
(user.sdr)
Jul 15 15:55:52 raspberrypi weewx[11768]: sdr: MainThread: driver version 
is 0.64
Jul 15 15:55:52 raspberrypi weewx[11768]: sdr: MainThread: sensor map is 
{'windDir': 'wind_dir.*.FOWHx080Packet', 'windSpeed': 
'wind_speed.*.FOWHx080Packet', 'outTemp': 'temperature.*.FOWHx080Packet', 
'outHumidity': 'humidity.*.FOWHx080Packet', 'rain_total': 
'rain_total.*.FOWHx080Packet', 'inTemp': 'temperature.*.FOWHx080Packet', 
'inHumidity': 'humidity.*.FOWHx080Packet'}
Jul 15 15:55:52 raspberrypi weewx[11768]: sdr: MainThread: deltas is 
{'strikes': 'strikes_total', 'rain': 'rain_total'}
Jul 15 15:55:52 raspberrypi weewx[11768]: sdr: MainThread: startup process 
'rtl_433 -q -F json -R 32 -f 868.3M'
Jul 15 15:55:52 raspberrypi weewx[11768]: sdr: stdout-thread: start async 
reader for stdout-thread
Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Loading service 
weewx.engine.StdTimeSynch
Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Jul 15 15:55:52 raspberrypi weewx[11768]: sdr: stderr-thread: start async 
reader for stderr-thread
Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Loading service 
user.extra_sensors_service.ExtraSensorsService
Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Finished loading service 
user.extra_sensors_service.ExtraSensorsService
Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Loading service 
weewx.engine.StdConvert
Jul 15 15:55:52 raspberrypi weewx[11768]: engine: StdConvert target unit is 
0x11
Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Finished loading service 
weewx.engine.StdConvert
Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Loading service 
weewx.engine.StdCalibrate
Jul 15 15:55:52 raspberrypi weewx[11768]: engine: Finished loading service 
weewx.engine.StdCalibrate
Jul 15 15:55:53 raspberrypi weewx[11768]: engine: Loading service 
weewx.engine.StdQC
Jul 15 15:55:53 raspberrypi weewx[11768]: engine: Finished loading service 
weewx.engine.StdQC
Jul 15 15:55:53 raspberrypi weewx[11768]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Jul 15 15:55:53 raspberrypi weewx[11768]: 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
Jul 15 15:55:53 raspberrypi weewx[11768]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Jul 15 15:55:53 raspberrypi weewx[11768]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate
Jul 15 15:55:53 raspberrypi weewx[11768]: engine: Loading service 
weewx.engine.StdArchive
Jul 15 15:55:53 raspberrypi weewx[11768]: engine: Archive will use data 
binding wx_binding
Jul 15 15:55:53 raspberrypi weewx[11768]: engine: Record generation will be 
attempted in 'software'
Jul 15 15:55:53 raspberrypi weewx[11768]: engine: Using archive interval of 
300 seconds (software record generation)
Jul 15 15:55:53 raspberrypi weewx[11768]: engine: Use LOOP data in hi/low 
calculations: 1
Jul 15 15:55:53 raspberrypi weewx[11768]: manager: Created and initialized 
table 'archive' in database 'weewx.sdb'
Jul 15 15:55:54 raspberrypi weewx[11768]: manager: Created daily summary 
tables
Jul 15 15:55:54 raspberrypi weewx[11768]: manager: Daily summary version is 
2.0
Jul 15 15:55:54 raspberrypi weewx[11768]: engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Jul 15 15:55:54 raspberrypi weewx[11768]: manager: Starting backfill of 
daily summaries
Jul 15 15:55:54 raspberrypi weewx[11768]: engine: Finished loading service 
weewx.engine.StdArchive
Jul 15 15:55:54 raspberrypi weewx[11768]: engine: Loading service 
weewx.restx.StdStationRegistry
Jul 15 15:55:54 raspberrypi weewx[11768]: restx: StationRegistry: 
Registration not requested.
Jul 15 15:55:54 raspberrypi weewx[11768]: engine: Finished loading service 
weewx.restx.StdStationRegistry
Jul 15 15:55:54 raspberrypi weewx[11768]: engine: Loading service 
weewx.restx.StdWunderground
Jul 15 15:55:54 raspberrypi weewx[11768]: restx: Wunderground: Posting not 
enabled.
Jul 15 15:55:54 raspberrypi weewx[11768]: engine: Finished loading service 
weewx.restx.StdWunderground
Jul 15 15:55:54 raspberrypi weewx[11768]: engine: Loading 

[weewx-user] Re: Incorrect time in reports

[Kike .Asekas]

But in the database the datetime is in UTC timezone or in local timezone?. 
I datetime field in my database reflects the local time. I think sum the +2 
of my timezone later.

El lunes, 15 de julio de 2019, 13:56:37 (UTC+2), Kike .Asekas escribió:
>
> Hello. I have a raspberry pi with raspbian. It have CEST+0200 timezone as 
> reported by date +"%Z %z". If I type 'date' my local time is reported 
> correctly, but in the reports of weewx the time is 2 hours later.  I mean 
> if it's 10:00 the webpages say 12:00.
> In python 
> datetime.datetime.now() gives the current local time correctly
> and 
> datetime.datetime.utcnow()gives 2 hours before correctly too.
> The database have the correct local time too.
>
>

-- 
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/485e8e20-9397-4194-9363-e0e90234138e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Incorrect time in reports

[Kike .Asekas]

2 hours later.

El lunes, 15 de julio de 2019, 15:22:17 (UTC+2), Andrew Milner escribió:
>
> how is the date being put on the webpages?
>
>
>
> On Monday, 15 July 2019 16:12:30 UTC+3, Kike .Asekas wrote:
>>
>> The current local time correctly.
>>
>> El lunes, 15 de julio de 2019, 15:07:45 (UTC+2), Thomas Keffer escribió:
>>>
>>> What do you get if you try
>>>
>>> python -c "import time; print time.strftime('%x %X')"
>>>
>>> -tk
>>>
>>> On Mon, Jul 15, 2019 at 4:56 AM Kike .Asekas  wrote:
>>>
>>>> Hello. I have a raspberry pi with raspbian. It have CEST+0200 timezone 
>>>> as reported by date +"%Z %z". If I type 'date' my local time is reported 
>>>> correctly, but in the reports of weewx the time is 2 hours later.  I 
>>>> mean if it's 10:00 the webpages say 12:00.
>>>> In python 
>>>> datetime.datetime.now() gives the current local time correctly
>>>> and 
>>>> datetime.datetime.utcnow()gives 2 hours before correctly too.
>>>> The database have the correct local time too.
>>>>
>>>> -- 
>>>> 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/649312fb-f97d-484e-9815-7b4f814a9e75%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/649312fb-f97d-484e-9815-7b4f814a9e75%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>

-- 
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/56b5fce2-ecc3-439b-95b2-4209833e8e4f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Incorrect time in reports

[Kike .Asekas]

The driver I use is SDR. I have debug enabled and I see the packets created 
by sdr and in the field datetime in Unix epoch format it's correct too.


-- 
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/bd31dd3b-3bb5-4db7-83c9-56ad7921b883%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Incorrect time in reports

[Kike .Asekas]

The current local time correctly.

El lunes, 15 de julio de 2019, 15:07:45 (UTC+2), Thomas Keffer escribió:
>
> What do you get if you try
>
> python -c "import time; print time.strftime('%x %X')"
>
> -tk
>
> On Mon, Jul 15, 2019 at 4:56 AM Kike .Asekas  > wrote:
>
>> Hello. I have a raspberry pi with raspbian. It have CEST+0200 timezone as 
>> reported by date +"%Z %z". If I type 'date' my local time is reported 
>> correctly, but in the reports of weewx the time is 2 hours later.  I 
>> mean if it's 10:00 the webpages say 12:00.
>> In python 
>> datetime.datetime.now() gives the current local time correctly
>> and 
>> datetime.datetime.utcnow()gives 2 hours before correctly too.
>> The database have the correct local time too.
>>
>> -- 
>> 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/649312fb-f97d-484e-9815-7b4f814a9e75%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/649312fb-f97d-484e-9815-7b4f814a9e75%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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/2973beaf-baee-4682-b370-98b204c4e77e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Incorrect time in reports

[Kike .Asekas]

Hello. I have a raspberry pi with raspbian. It have CEST+0200 timezone as 
reported by date +"%Z %z". If I type 'date' my local time is reported 
correctly, but in the reports of weewx the time is 2 hours later.  I mean 
if it's 10:00 the webpages say 12:00.
In python 
datetime.datetime.now() gives the current local time correctly
and 
datetime.datetime.utcnow()gives 2 hours before correctly too.
The database have the correct local time too.

-- 
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/649312fb-f97d-484e-9815-7b4f814a9e75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.