[weewx-user] Re: weewx forecast

[Damjan Hajsek]

thank you for your help.
I will find someone with some html skils

Dne petek, 21. junij 2019 01.45.07 UTC+2 je oseba gjr80 napisala:
>
> I'm sorry Damian but this is now getting outside my range of skills. 
> Matthew or someone with some html/bootstrap knowledge might be able to help.
>
> Gary
>
> On Wednesday, 19 June 2019 17:55:02 UTC+10, Damjan Hajsek wrote:
>>
>> just one more thing.
>> I tried to add forecast strip at the bottom of page, but what it did is 
>> strech page out of proportion.
>> is it possible to add strip and it will ajust on size of page in web 
>> browser like the rest of page?
>>
>>
>> Dne sreda, 19. junij 2019 09.38.19 UTC+2 je oseba Damjan Hajsek napisala:
>>>
>>> After I post this I remember what I forget to change, now it works. 
>>> Thank you for helping.
>>> If somebody want to use that skin it can, it works.
>>>
>>> Dne sreda, 19. junij 2019 09.35.41 UTC+2 je oseba Damjan Hajsek napisala:
>>>>
>>>> Hi
>>>> Thank you for your willing to help.
>>>> I have installed sofaskin and than add forecast, I am not programmer so 
>>>> I did as I know.
>>>> I have zipped sofaskin so you can look at it. Before it worked with WU 
>>>> but don't know what is differend with OWM.
>>>> If you try and test that skin it should work as it is.
>>>> rar is a bit too large so I have uploaded it here on link.
>>>> https://nextcloud.povej.net/index.php/s/qQPKsZE8dSE7t2q
>>>>
>>>> regards
>>>> Damian
>>>>
>>>>
>>>> Dne sreda, 19. junij 2019 01.13.57 UTC+2 je oseba gjr80 napisala:
>>>>>
>>>>> Damian,
>>>>>
>>>>> Since the forecasting extension example page for your site 
>>>>> <https://vreme.povej.net/forecast/forecast-periods.html> is 
>>>>> displaying OWM data the OWM forecast appears to be working. The issue 
>>>>> will 
>>>>> be with the sofaskin. The solution will depend on the sofaskin author, it 
>>>>> may be a simple case of changing a sofaksin config setting to use the OWM 
>>>>> forecast instead of WU, or it may be that the author has hard coded the 
>>>>> WU 
>>>>> forecast in the skin. Impossible for me to say (or guess) without seeing 
>>>>> the underlying code. I understand the original author no longer supports 
>>>>> the skin and googling 'weewx sofaskin' found many forks. I could not find 
>>>>> any version that had the forecast data included.
>>>>>
>>>>> If you can give me the link to where you downloaded your version of 
>>>>> sofaskin I am happy to have a quick look at the code and see if there is 
>>>>> an 
>>>>> easy fix. Otherwise you may be best served by contacting the author of 
>>>>> your 
>>>>> version of sofaskin.
>>>>>
>>>>> Gary
>>>>>
>>>>> On Wednesday, 19 June 2019 04:11:03 UTC+10, Damjan Hajsek wrote:
>>>>>>
>>>>>> this is what I had for WU and now I change for OWM and doesn't work. 
>>>>>> Is there anything else to setup for OWM or maybe DS?
>>>>>>
>>>>>> [[forecast_table_settings]]
>>>>>> #source = WU
>>>>>> source = OWM
>>>>>> num_days = 7
>>>>>>
>>>>>> [[forecast_strip_settings]]
>>>>>> #   source = WU
>>>>>>source = OWM
>>>>>> num_days = 15
>>>>>> num_periods = 40
>>>>>>
>>>>>>
>>>>>> Dne torek, 18. junij 2019 18.41.04 UTC+2 je oseba Paul McGeorge 
>>>>>> napisala:
>>>>>>>
>>>>>>> Looks like you are receiving the forecast from OWM and I can see it 
>>>>>>> here https://vreme.povej.net/forecast/forecast-periods.html
>>>>>>>
>>>>>>> I don't use the Sofaskin, but it looks like you need to update the 
>>>>>>> template that creates the Forecast table.
>>>>>>>
>>>>>>>
>>>>>>> On Tuesday, June 18, 2019 at 3:27:05 AM UTC-6, Damjan Hajsek wrote:
>>>>>>>>
>>>>>>>> I have tried WU but it looks like WU canceled all APIs than I tried 
>>>>>>&

[weewx-user] Re: weewx forecast

[Damjan Hajsek]

just one more thing.
I tried to add forecast strip at the bottom of page, but what it did is 
strech page out of proportion.
is it possible to add strip and it will ajust on size of page in web 
browser like the rest of page?


Dne sreda, 19. junij 2019 09.38.19 UTC+2 je oseba Damjan Hajsek napisala:
>
> After I post this I remember what I forget to change, now it works. Thank 
> you for helping.
> If somebody want to use that skin it can, it works.
>
> Dne sreda, 19. junij 2019 09.35.41 UTC+2 je oseba Damjan Hajsek napisala:
>>
>> Hi
>> Thank you for your willing to help.
>> I have installed sofaskin and than add forecast, I am not programmer so I 
>> did as I know.
>> I have zipped sofaskin so you can look at it. Before it worked with WU 
>> but don't know what is differend with OWM.
>> If you try and test that skin it should work as it is.
>> rar is a bit too large so I have uploaded it here on link.
>> https://nextcloud.povej.net/index.php/s/qQPKsZE8dSE7t2q
>>
>> regards
>> Damian
>>
>>
>> Dne sreda, 19. junij 2019 01.13.57 UTC+2 je oseba gjr80 napisala:
>>>
>>> Damian,
>>>
>>> Since the forecasting extension example page for your site 
>>> <https://vreme.povej.net/forecast/forecast-periods.html> is displaying 
>>> OWM data the OWM forecast appears to be working. The issue will be with the 
>>> sofaskin. The solution will depend on the sofaskin author, it may be a 
>>> simple case of changing a sofaksin config setting to use the OWM forecast 
>>> instead of WU, or it may be that the author has hard coded the WU forecast 
>>> in the skin. Impossible for me to say (or guess) without seeing the 
>>> underlying code. I understand the original author no longer supports the 
>>> skin and googling 'weewx sofaskin' found many forks. I could not find any 
>>> version that had the forecast data included.
>>>
>>> If you can give me the link to where you downloaded your version of 
>>> sofaskin I am happy to have a quick look at the code and see if there is an 
>>> easy fix. Otherwise you may be best served by contacting the author of your 
>>> version of sofaskin.
>>>
>>> Gary
>>>
>>> On Wednesday, 19 June 2019 04:11:03 UTC+10, Damjan Hajsek wrote:
>>>>
>>>> this is what I had for WU and now I change for OWM and doesn't work. Is 
>>>> there anything else to setup for OWM or maybe DS?
>>>>
>>>> [[forecast_table_settings]]
>>>> #source = WU
>>>> source = OWM
>>>> num_days = 7
>>>>
>>>> [[forecast_strip_settings]]
>>>> #   source = WU
>>>>source = OWM
>>>> num_days = 15
>>>> num_periods = 40
>>>>
>>>>
>>>> Dne torek, 18. junij 2019 18.41.04 UTC+2 je oseba Paul McGeorge 
>>>> napisala:
>>>>>
>>>>> Looks like you are receiving the forecast from OWM and I can see it 
>>>>> here https://vreme.povej.net/forecast/forecast-periods.html
>>>>>
>>>>> I don't use the Sofaskin, but it looks like you need to update the 
>>>>> template that creates the Forecast table.
>>>>>
>>>>>
>>>>> On Tuesday, June 18, 2019 at 3:27:05 AM UTC-6, Damjan Hajsek wrote:
>>>>>>
>>>>>> I have tried WU but it looks like WU canceled all APIs than I tried 
>>>>>> OWM and also doesn't work, no forecast ny my site, after that I try also 
>>>>>> DarkSky, and also doesn't work but I see pooling data from last two 
>>>>>> sites.
>>>>>> Debug = 1 in weewx.conf
>>>>>> I also deleted forecast.sdb and restart weewx
>>>>>> Here is log and wee_debug.
>>>>>>
>>>>>> https://vreme.povej.net
>>>>>>
>>>>>>
>>>>>>
>>>>>> Damian
>>>>>>
>>>>>>
>>>>>> As Gary pointed I will start new topic.
>>>>>>
>>>>>> Might be time for you to start a new thread specifically for your 
>>>>>> forecast problems, I think this one is getting a bit long and you now 
>>>>>> have 
>>>>>> a new issue. 
>>>>>>
>>>>>> You might like to start off by stopping WeeWX, confirming debug = 1 
>>>>>> in weewx.conf, deleting the forecast database forec

[weewx-user] Re: weewx forecast

[Damjan Hajsek]

After I post this I remember what I forget to change, now it works. Thank 
you for helping.
If somebody want to use that skin it can, it works.

Dne sreda, 19. junij 2019 09.35.41 UTC+2 je oseba Damjan Hajsek napisala:
>
> Hi
> Thank you for your willing to help.
> I have installed sofaskin and than add forecast, I am not programmer so I 
> did as I know.
> I have zipped sofaskin so you can look at it. Before it worked with WU but 
> don't know what is differend with OWM.
> If you try and test that skin it should work as it is.
> rar is a bit too large so I have uploaded it here on link.
> https://nextcloud.povej.net/index.php/s/qQPKsZE8dSE7t2q
>
> regards
> Damian
>
>
> Dne sreda, 19. junij 2019 01.13.57 UTC+2 je oseba gjr80 napisala:
>>
>> Damian,
>>
>> Since the forecasting extension example page for your site 
>> <https://vreme.povej.net/forecast/forecast-periods.html> is displaying 
>> OWM data the OWM forecast appears to be working. The issue will be with the 
>> sofaskin. The solution will depend on the sofaskin author, it may be a 
>> simple case of changing a sofaksin config setting to use the OWM forecast 
>> instead of WU, or it may be that the author has hard coded the WU forecast 
>> in the skin. Impossible for me to say (or guess) without seeing the 
>> underlying code. I understand the original author no longer supports the 
>> skin and googling 'weewx sofaskin' found many forks. I could not find any 
>> version that had the forecast data included.
>>
>> If you can give me the link to where you downloaded your version of 
>> sofaskin I am happy to have a quick look at the code and see if there is an 
>> easy fix. Otherwise you may be best served by contacting the author of your 
>> version of sofaskin.
>>
>> Gary
>>
>> On Wednesday, 19 June 2019 04:11:03 UTC+10, Damjan Hajsek wrote:
>>>
>>> this is what I had for WU and now I change for OWM and doesn't work. Is 
>>> there anything else to setup for OWM or maybe DS?
>>>
>>> [[forecast_table_settings]]
>>> #source = WU
>>> source = OWM
>>> num_days = 7
>>>
>>> [[forecast_strip_settings]]
>>> #   source = WU
>>>source = OWM
>>> num_days = 15
>>> num_periods = 40
>>>
>>>
>>> Dne torek, 18. junij 2019 18.41.04 UTC+2 je oseba Paul McGeorge napisala:
>>>>
>>>> Looks like you are receiving the forecast from OWM and I can see it 
>>>> here https://vreme.povej.net/forecast/forecast-periods.html
>>>>
>>>> I don't use the Sofaskin, but it looks like you need to update the 
>>>> template that creates the Forecast table.
>>>>
>>>>
>>>> On Tuesday, June 18, 2019 at 3:27:05 AM UTC-6, Damjan Hajsek wrote:
>>>>>
>>>>> I have tried WU but it looks like WU canceled all APIs than I tried 
>>>>> OWM and also doesn't work, no forecast ny my site, after that I try also 
>>>>> DarkSky, and also doesn't work but I see pooling data from last two sites.
>>>>> Debug = 1 in weewx.conf
>>>>> I also deleted forecast.sdb and restart weewx
>>>>> Here is log and wee_debug.
>>>>>
>>>>> https://vreme.povej.net
>>>>>
>>>>>
>>>>>
>>>>> Damian
>>>>>
>>>>>
>>>>> As Gary pointed I will start new topic.
>>>>>
>>>>> Might be time for you to start a new thread specifically for your 
>>>>> forecast problems, I think this one is getting a bit long and you now 
>>>>> have 
>>>>> a new issue. 
>>>>>
>>>>> You might like to start off by stopping WeeWX, confirming debug = 1 
>>>>> in weewx.conf, deleting the forecast database forecast.sdb and then 
>>>>> restarting WeeWX. Let WeeWX run for 2-3 archive periods and post a log 
>>>>> extract from when WeeWX was restarted until the 2-3 archive periods have 
>>>>> elapsed. Would also help if you posted a wee_debug 
>>>>> <http://www.google.com/url?q=http%3A%2F%2Fweewx.com%2Fdocs%2Futilities.htm%23wee_debug_utility=D=1=AFQjCNFt3CwAONo9qN5etsx4Ap7ZUSRVTw>
>>>>>  
>>>>> report. Make sure before posting the wee_debug report you check the 
>>>>> output for any user names, passwords or other sensitive data and remove 
>>>>> before posting. wee_debug does a good job at doing this but its not 
>>>>> perfect.
>>>>>
>>>>> Gary
>>>>>
>>>>>
>>>>> I 
>>>>>
>>>>

-- 
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/e7a40065-44f2-45d4-8ab0-86bc319bed00%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx forecast

[Damjan Hajsek]

Hi
Thank you for your willing to help.
I have installed sofaskin and than add forecast, I am not programmer so I 
did as I know.
I have zipped sofaskin so you can look at it. Before it worked with WU but 
don't know what is differend with OWM.
If you try and test that skin it should work as it is.
rar is a bit too large so I have uploaded it here on link.
https://nextcloud.povej.net/index.php/s/qQPKsZE8dSE7t2q

regards
Damian


Dne sreda, 19. junij 2019 01.13.57 UTC+2 je oseba gjr80 napisala:
>
> Damian,
>
> Since the forecasting extension example page for your site 
> <https://vreme.povej.net/forecast/forecast-periods.html> is displaying 
> OWM data the OWM forecast appears to be working. The issue will be with the 
> sofaskin. The solution will depend on the sofaskin author, it may be a 
> simple case of changing a sofaksin config setting to use the OWM forecast 
> instead of WU, or it may be that the author has hard coded the WU forecast 
> in the skin. Impossible for me to say (or guess) without seeing the 
> underlying code. I understand the original author no longer supports the 
> skin and googling 'weewx sofaskin' found many forks. I could not find any 
> version that had the forecast data included.
>
> If you can give me the link to where you downloaded your version of 
> sofaskin I am happy to have a quick look at the code and see if there is an 
> easy fix. Otherwise you may be best served by contacting the author of your 
> version of sofaskin.
>
> Gary
>
> On Wednesday, 19 June 2019 04:11:03 UTC+10, Damjan Hajsek wrote:
>>
>> this is what I had for WU and now I change for OWM and doesn't work. Is 
>> there anything else to setup for OWM or maybe DS?
>>
>> [[forecast_table_settings]]
>> #source = WU
>> source = OWM
>> num_days = 7
>>
>> [[forecast_strip_settings]]
>> #   source = WU
>>source = OWM
>> num_days = 15
>> num_periods = 40
>>
>>
>> Dne torek, 18. junij 2019 18.41.04 UTC+2 je oseba Paul McGeorge napisala:
>>>
>>> Looks like you are receiving the forecast from OWM and I can see it here 
>>> https://vreme.povej.net/forecast/forecast-periods.html
>>>
>>> I don't use the Sofaskin, but it looks like you need to update the 
>>> template that creates the Forecast table.
>>>
>>>
>>> On Tuesday, June 18, 2019 at 3:27:05 AM UTC-6, Damjan Hajsek wrote:
>>>>
>>>> I have tried WU but it looks like WU canceled all APIs than I tried OWM 
>>>> and also doesn't work, no forecast ny my site, after that I try also 
>>>> DarkSky, and also doesn't work but I see pooling data from last two sites.
>>>> Debug = 1 in weewx.conf
>>>> I also deleted forecast.sdb and restart weewx
>>>> Here is log and wee_debug.
>>>>
>>>> https://vreme.povej.net
>>>>
>>>>
>>>>
>>>> Damian
>>>>
>>>>
>>>> As Gary pointed I will start new topic.
>>>>
>>>> Might be time for you to start a new thread specifically for your 
>>>> forecast problems, I think this one is getting a bit long and you now have 
>>>> a new issue. 
>>>>
>>>> You might like to start off by stopping WeeWX, confirming debug = 1 in 
>>>> weewx.conf, deleting the forecast database forecast.sdb and then 
>>>> restarting WeeWX. Let WeeWX run for 2-3 archive periods and post a log 
>>>> extract from when WeeWX was restarted until the 2-3 archive periods have 
>>>> elapsed. Would also help if you posted a wee_debug 
>>>> <http://www.google.com/url?q=http%3A%2F%2Fweewx.com%2Fdocs%2Futilities.htm%23wee_debug_utility=D=1=AFQjCNFt3CwAONo9qN5etsx4Ap7ZUSRVTw>
>>>>  
>>>> report. Make sure before posting the wee_debug report you check the 
>>>> output for any user names, passwords or other sensitive data and remove 
>>>> before posting. wee_debug does a good job at doing this but its not 
>>>> perfect.
>>>>
>>>> Gary
>>>>
>>>>
>>>> I 
>>>>
>>>

-- 
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/70b605f8-a243-4549-a517-c354c7b5cb72%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx forecast

[Damjan Hajsek]

this is what I had for WU and now I change for OWM and doesn't work. Is 
there anything else to setup for OWM or maybe DS?

[[forecast_table_settings]]
#source = WU
source = OWM
num_days = 7

[[forecast_strip_settings]]
#   source = WU
   source = OWM
num_days = 15
num_periods = 40


Dne torek, 18. junij 2019 18.41.04 UTC+2 je oseba Paul McGeorge napisala:
>
> Looks like you are receiving the forecast from OWM and I can see it here 
> https://vreme.povej.net/forecast/forecast-periods.html
>
> I don't use the Sofaskin, but it looks like you need to update the 
> template that creates the Forecast table.
>
>
> On Tuesday, June 18, 2019 at 3:27:05 AM UTC-6, Damjan Hajsek wrote:
>>
>> I have tried WU but it looks like WU canceled all APIs than I tried OWM 
>> and also doesn't work, no forecast ny my site, after that I try also 
>> DarkSky, and also doesn't work but I see pooling data from last two sites.
>> Debug = 1 in weewx.conf
>> I also deleted forecast.sdb and restart weewx
>> Here is log and wee_debug.
>>
>> https://vreme.povej.net
>>
>>
>>
>> Damian
>>
>>
>> As Gary pointed I will start new topic.
>>
>> Might be time for you to start a new thread specifically for your 
>> forecast problems, I think this one is getting a bit long and you now have 
>> a new issue. 
>>
>> You might like to start off by stopping WeeWX, confirming debug = 1 in 
>> weewx.conf, deleting the forecast database forecast.sdb and then 
>> restarting WeeWX. Let WeeWX run for 2-3 archive periods and post a log 
>> extract from when WeeWX was restarted until the 2-3 archive periods have 
>> elapsed. Would also help if you posted a wee_debug 
>> <http://www.google.com/url?q=http%3A%2F%2Fweewx.com%2Fdocs%2Futilities.htm%23wee_debug_utility=D=1=AFQjCNFt3CwAONo9qN5etsx4Ap7ZUSRVTw>
>>  
>> report. Make sure before posting the wee_debug report you check the 
>> output for any user names, passwords or other sensitive data and remove 
>> before posting. wee_debug does a good job at doing this but its not 
>> perfect.
>>
>> Gary
>>
>>
>> I 
>>
>

-- 
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/b1ea2e19-651c-4436-a7ae-20ffa0fff928%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] weewx forecast

[Damjan Hajsek]

I have tried WU but it looks like WU canceled all APIs than I tried OWM and 
also doesn't work, no forecast ny my site, after that I try also DarkSky, 
and also doesn't work but I see pooling data from last two sites.
Debug = 1 in weewx.conf
I also deleted forecast.sdb and restart weewx
Here is log and wee_debug.

https://vreme.povej.net



Damian


As Gary pointed I will start new topic.

Might be time for you to start a new thread specifically for your forecast 
problems, I think this one is getting a bit long and you now have a new 
issue. 

You might like to start off by stopping WeeWX, confirming debug = 1 in 
weewx.conf, deleting the forecast database forecast.sdb and then restarting 
WeeWX. Let WeeWX run for 2-3 archive periods and post a log extract from 
when WeeWX was restarted until the 2-3 archive periods have elapsed. Would 
also help if you posted a wee_debug 

 
report. Make sure before posting the wee_debug report you check the output 
for any user names, passwords or other sensitive data and remove before 
posting. wee_debug does a good job at doing this but its not perfect.

Gary


I 

-- 
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/a0380da1-64a0-4c89-bf53-fc4ddc8b29e8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jun 18 11:19:50 povej weewx[24286]: interceptor: MainThread: ignored parameter 
weeklyrain=5.7
Jun 18 11:19:50 povej weewx[24286]: interceptor: MainThread: ignored parameter 
monthlyrain=5.7
Jun 18 11:19:50 povej weewx[24286]: interceptor: MainThread: ignored parameter 
realtime=1
Jun 18 11:19:50 povej weewx[24286]: interceptor: MainThread: ignored parameter 
rtfreq=5
Jun 18 11:19:50 povej weewx[24286]: interceptor: MainThread: ignored parameter 
action=updateraw
Jun 18 11:19:50 povej weewx[24286]: interceptor: MainThread: ignored parameter 
PASSWORD=
Jun 18 11:19:50 povej weewx[24286]: interceptor: MainThread: ignored parameter 
ID=ido10
Jun 18 11:19:50 povej weewx[24286]: interceptor: MainThread: ignored parameter 
softwaretype=WS-1002%20V2.4.6
Jun 18 11:19:50 povej weewx[24286]: interceptor: MainThread: ignored parameter 
relbaro=1013.3
Jun 18 11:19:50 povej weewx[24286]: interceptor: MainThread: raw packet: 
{'humidity_in': 58.0, 'wind_speed': 0.1, 'temperature_in': 25.0, 'windchill': 
25.7, 'dewpoint': 16.8, 'luminosity': 69974.8, 'humidity_out': 58.0, 'uv': 
2733.0, 'radiation': 752.2291, 'rain': 0.0, 'dateTime': 1560849590, 'pressure': 
977.7, 'temperature_out': 25.7, 'wind_dir': 320.0, 'rain_total': 5.7, 
'rain_rate': 0.0, 'usUnits': 16, 'wind_gust': 1.1}
Jun 18 11:19:50 povej weewx[24286]: interceptor: MainThread: mapped packet: 
{'windchill': 25.7, 'dewpoint': 16.8, 'pressure': 977.7, 'outHumidity': 58.0, 
'UV': 2733.0, 'radiation': 752.2291, 'rain': 0.0, 'dateTime': 1560849590, 
'windDir': 320.0, 'outTemp': 25.7, 'windSpeed': 0.1, 'inHumidity': 58.0, 
'inTemp': 25.0, 'windGust': 1.1, 'rainRate': 0.0, 'usUnits': 16}
Jun 18 11:19:57 povej weewx[24286]: interceptor: ServerThread: GET: 
ID=ido10==25.0=25.7=17.1=25.7=58=59=0.0=0.0=84=977.7=1013.3=0.0=2.1=5.7=5.7=5.7=98264.8=3566=2019-6-18%209:19:57=WS-1002%20V2.4.6=updateraw=1=5
Jun 18 11:19:57 povej weewx[24286]: interceptor: MainThread: raw data: 
ID=ido10=np8xkt1j=25.0=25.7=17.1=25.7=58=59=0.0=0.0=84=977.7=1013.3=0.0=2.1=5.7=5.7=5.7=98264.8=3566=2019-6-18%209:19:57=WS-1002%20V2.4.6=updateraw=1=5
Jun 18 11:19:57 povej weewx[24286]: interceptor: MainThread: using rain_total 
5.7 from yearlyrain
Jun 18 11:19:57 povej weewx[24286]: interceptor: MainThread: firmware 
WS-1002%20V2.4.6: baromin is barometer
Jun 18 11:19:57 povej weewx[24286]: interceptor: MainThread: ignored parameter 
weeklyrain=5.7
Jun 18 11:19:57 povej weewx[24286]: interceptor: MainThread: ignored parameter 
monthlyrain=5.7
Jun 18 11:19:57 povej weewx[24286]: interceptor: MainThread: ignored parameter 
realtime=1
Jun 18 11:19:57 povej weewx[24286]: interceptor: MainThread: ignored parameter 
rtfreq=5
Jun 18 11:19:57 povej weewx[24286]: interceptor: MainThread: ignored parameter 
action=updateraw
Jun 18 11:19:57 povej weewx[24286]: interceptor: MainThread: ignored parameter 
PASSWORD=
Jun 18 11:19:57 povej weewx[24286]: interceptor: MainThread: ignored parameter 
ID=ido10
Jun 18 11:19:57 povej weewx[24286]: interceptor: MainThread: ignored parameter 
softwaretype=WS-1002%20V2.4.6
Jun 18 11:19:57 povej weewx[24286]: interceptor: MainThread: ignored parameter 
relbaro=1013.3
Jun 18 11:19:57 povej weewx[24286]: interceptor: MainThread: raw packet: 
{'humidity_in': 58.0, 'wind_speed': 0.0, 'temperature_in': 25.0, 

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

I have manage to make all works except forecast.
WU api doesn't work anymore so I tried OWM, but insted of OWM I get 
No forecast data for WU
And I have setup API key and this is what I have in log

Jun 18 09:32:49 povej weewx[32266]: forecast: MainThread: OWM: last 
forecast issued 2019-06-18 08:55:25 CEST (1560840925), requested 2019-06-18 
08:55:25 CEST (1560840925)
Jun 18 09:32:49 povej weewx[32266]: forecast: MainThread: OWM: 
interval=10800 max_age=604800 api_key=8d95 
location=26.1280,34.6124 fc=5day3hour
Jun 18 09:32:49 povej weewx[32266]: engine: Finished loading service 
user.forecast.OWMForecast



Dne torek, 18. junij 2019 09.30.29 UTC+2 je oseba Damjan Hajsek napisala:
>
>  thank you.
> Yes I remove sofaskin from those, that was just for testing.
>

-- 
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/54814969-eb61-4497-b080-cdf63cdba6aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

 thank you.
Yes I remove sofaskin from those, that was just for testing.

-- 
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/72cf01fb-94a9-4610-a07e-bb194a315add%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

yes that's it.
Thank you, now all works.

Just one question.
All those skins for, mobile, smartphone, etc. can be all enabled?


Dne ponedeljek, 17. junij 2019 21.58.37 UTC+2 je oseba vince napisala:
>
> On Monday, June 17, 2019 at 12:48:28 PM UTC-7, Damjan Hajsek wrote:
>>
>> In version 3.8.0 was only one settings for skin now there are 4.
>> I tried all and always the same error, no matter where I use sofaskin.
>> Now I have disabled all and also tried all now only this is enabled and 
>> doesn't work. below is log, reporting is on 3 minutes.
>> Web page doesn't update. https://vreme.povej.net
>>
>>  
>> Jun 17 21:40:35 povej weewx[4326]: cheetahgenerator: using search list 
>> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
>> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
>> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
>> 'user.forecast.ForecastVariables']
>> Jun 17 21:40:35 povej weewx[4326]: manager: Daily summary version is 2.0
>> Jun 17 21:40:35 povej weewx[4326]: reportengine: Caught unrecoverable 
>> exception in generator 'weewx.cheetahgenerator.CheetahGenerator'
>> Jun 17 21:40:35 povej weewx[4326]:  No module named forecast
>> Jun 17 21:40:35 povej weewx[4326]:  Traceback (most recent 
>> call last):
>> Jun 17 21:40:35 povej weewx[4326]:File 
>> "/usr/share/weewx/weewx/reportengine.py", line 204, in run
>> Jun 17 21:40:35 povej weewx[4326]:  obj.start()
>> Jun 17 21:40:35 povej weewx[4326]:File 
>> "/usr/share/weewx/weewx/reportengine.py", line 300, in start
>> Jun 17 21:40:35 povej weewx[4326]:  self.run()
>> Jun 17 21:40:35 povej weewx[4326]:File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 157, in run
>> Jun 17 21:40:35 povej weewx[4326]:  
>> self.initExtensions(gen_dict[section_name])
>> Jun 17 21:40:35 povej weewx[4326]:File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 199, in initExtensions
>> Jun 17 21:40:35 povej weewx[4326]:  class_ = 
>> weeutil.weeutil._get_object(x)
>> Jun 17 21:40:35 povej weewx[4326]:File 
>> "/usr/share/weewx/weeutil/weeutil.py", line 1130, in _get_object
>> Jun 17 21:40:35 povej weewx[4326]:  mod = 
>> __import__(module)
>> Jun 17 21:40:35 povej weewx[4326]:  ImportError: No module 
>> named forecast
>> Jun 17 21:40:35 povej weewx[4326]:  Generator terminated
>>
>>
> The logs seem to say that you forgot to install the forecast extension.
>
>

-- 
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/2aa538f3-a4e3-432d-aad8-d2b186ca61b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

=26408.2=955=2019-6-17
 
7:8:11=WS-1002 V2.4.6=updateraw=1=5
Jun 17 09:08:11 povej weewx[2661]: interceptor: MainThread: using 
rain_total 9.0 from yearlyrain
Jun 17 09:08:11 povej weewx[2661]: interceptor: MainThread: firmware 
WS-1002 V2.4.6: baromin is barometer
Jun 17 09:08:11 povej weewx[2661]: interceptor: MainThread: ignored 
parameter weeklyrain=3.0
Jun 17 09:08:11 povej weewx[2661]: interceptor: MainThread: ignored 
parameter monthlyrain=9.0
Jun 17 09:08:11 povej weewx[2661]: interceptor: MainThread: ignored 
parameter realtime=1
Jun 17 09:08:11 povej weewx[2661]: interceptor: MainThread: ignored 
parameter rtfreq=5
Jun 17 09:08:11 povej weewx[2661]: interceptor: MainThread: ignored 
parameter action=updateraw
Jun 17 09:08:11 povej weewx[2661]: interceptor: MainThread: ignored 
parameter PASSWORD=
Jun 17 09:08:11 povej weewx[2661]: interceptor: MainThread: ignored 
parameter ID=ido10
Jun 17 09:08:11 povej weewx[2661]: interceptor: MainThread: ignored 
parameter softwaretype=WS-1002 V2.4.6
Jun 17 09:08:11 povej weewx[2661]: interceptor: MainThread: ignored 
parameter relbaro=1018.6
Jun 17 09:08:11 povej weewx[2661]: interceptor: MainThread: raw packet: 
{'humidity_in': 59.0, 'wind_speed': 0.0, 'temperature_in': 25.0, 
'windchill': 21.6, 'dewpoint': 20.6, 'luminosity': 26408.2, 'humidity_out': 
94.0, 'uv': 955.0, 'radiation': 283.88815, 'rain': 0.0, 'dateTime': 
1560755291, 'pressure': 979.6, 'temperature_out': 21.6, 'wind_dir': 183.0, 
'rain_total': 9.0, 'rain_rate': 0.0, 'usUnits': 16, 'wind_gust': 0.0}
Jun 17 09:08:11 povej weewx[2661]: interceptor: MainThread: mapped packet: 
{'windchill': 21.6, 'dewpoint': 20.6, 'pressure': 979.6, 'outHumidity': 
94.0, 'UV': 955.0, 'radiation': 283.88815, 'rain': 0.0, 'dateTime': 
1560755291, 'windDir': 183.0, 'outTemp': 21.6, 'windSpeed': 0.0, 
'inHumidity': 59.0, 'inTemp': 25.0, 'windGust': 0.0, 'rainRate': 0.0, 
'usUnits': 16}
Jun 17 09:08:21 povej weewx[2661]: interceptor: MainThread: empty queue
Jun 17 09:08:27 povej weewx[2661]: interceptor: ServerThread: GET: 
ID=ido10==25.0=21.6=20.8=21.6=59=95=0.0=0.0=148=979.6=1018.6=0.0=3.0=3.0=9.0=9.0=26456.5=957=2019-6-17
 
7:8:27=WS-1002 V2.4.6=updateraw=1=5
Jun 17 09:08:27 povej weewx[2661]: interceptor: MainThread: raw data: 
ID=ido10=np8xkt1j=25.0=21.6=20.8=21.6=59=95=0.0=0.0=148=979.6=1018.6=0.0=3.0=3.0=9.0=9.0=26456.5=957=2019-6-17
 
7:8:27=WS-1002 V2.4.6=updateraw=1=5
Jun 17 09:08:27 povej weewx[2661]: interceptor: MainThread: using 
rain_total 9.0 from yearlyrain
Jun 17 09:08:27 povej weewx[2661]: interceptor: MainThread: firmware 
WS-1002 V2.4.6: baromin is barometer
Jun 17 09:08:27 povej weewx[2661]: interceptor: MainThread: ignored 
parameter weeklyrain=3.0
Jun 17 09:08:27 povej weewx[2661]: interceptor: MainThread: ignored 
parameter monthlyrain=9.0
Jun 17 09:08:27 povej weewx[2661]: interceptor: MainThread: ignored 
parameter realtime=1
Jun 17 09:08:27 povej weewx[2661]: interceptor: MainThread: ignored 
parameter rtfreq=5
Jun 17 09:08:27 povej weewx[2661]: interceptor: MainThread: ignored 
parameter action=updateraw
Jun 17 09:08:27 povej weewx[2661]: interceptor: MainThread: ignored 
parameter PASSWORD=
Jun 17 09:08:27 povej weewx[2661]: interceptor: MainThread: ignored 
parameter ID=ido10
Jun 17 09:08:27 povej weewx[2661]: interceptor: MainThread: ignored 
parameter softwaretype=WS-1002 V2.4.6
Jun 17 09:08:27 povej weewx[2661]: interceptor: MainThread: ignored 
parameter relbaro=1018.6
Jun 17 09:08:27 povej weewx[2661]: interceptor: MainThread: raw packet: 
{'humidity_in': 59.0, 'wind_speed': 0.0, 'temperature_in': 25.0, 
'windchill': 21.6, 'dewpoint': 20.8, 'luminosity': 26456.5, 'humidity_out': 
95.0, 'uv': 957.0, 'radiation': 284.407375, 'rain': 0.0, 'dateTime': 
1560755307, 'pressure': 979.6, 'temperature_out': 21.6, 'wind_dir': 148.0, 
'rain_total': 9.0, 'rain_rate': 0.0, 'usUnits': 16, 'wind_gust': 0.0}
Jun 17 09:08:27 povej weewx[2661]: interceptor: MainThread: mapped packet: 
{'windchill': 21.6, 'dewpoint': 20.8, 'pressure': 979.6, 'outHumidity': 
95.0, 'UV': 957.0, 'radiation': 284.407375, 'rain': 0.0, 'dateTime': 
1560755307, 'windDir': 148.0, 'outTemp': 21.6, 'windSpeed': 0.0, 
'inHumidity': 59.0, 'inTemp': 25.0, 'windGust': 0.0, 'rainRate': 0.0, 
'usUnits': 16}



Dne ponedeljek, 17. junij 2019 08.55.37 UTC+2 je oseba Damjan Hajsek 
napisala:
>
> I have copied sofaskin into folder /etc/weewx/skins/sofaskin
>
> end enable it in weewx.conf
>
> #   This section specifies what reports, using which skins, to generate.
>
> [StdReport]
> 
> # Where the skins reside, relative to WEEWX_ROOT
> SKIN_ROOT = /etc/weewx/skins
> 
> # Where the generated reports should go, relative to WEEWX_ROOT
> HTML_ROOT = /var/www/html/weewx
> 
> # The database binding indicates which data should be used in reports.
> data_binding = wx_binding
> 
> # Whether to log a successful operation
> log_

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

I have copied sofaskin into folder /etc/weewx/skins/sofaskin

end enable it in weewx.conf

#   This section specifies what reports, using which skins, to generate.

[StdReport]

# Where the skins reside, relative to WEEWX_ROOT
SKIN_ROOT = /etc/weewx/skins

# Where the generated reports should go, relative to WEEWX_ROOT
HTML_ROOT = /var/www/html/weewx

# The database binding indicates which data should be used in reports.
data_binding = wx_binding

# Whether to log a successful operation
log_success = True

# Whether to log an unsuccessful operation
log_failure = False

# Each of the following subsections defines a report that will be run.
# See the customizing guide to change the units, plot types and line
# colors, modify the fonts, display additional sensor data, and other
# customizations. Many of those changes can be made here by overriding
# parameters, or by modifying templates within the skin itself.

[[SeasonsReport]]
# The SeasonsReport uses the 'Seasons' skin, which contains the
# images, templates and plots for the report.
#skin = Seasons
skin = sofaskin
enable = false

[[SmartphoneReport]]
# The SmartphoneReport uses the 'Smartphone' skin, and the images 
and
# files are placed in a dedicated subdirectory.
#skin = Smartphone
skin = sofaskin
enable = false
HTML_ROOT = /var/www/html/weewx

[[MobileReport]]
# The MobileReport uses the 'Mobile' skin, and the images and files
# are placed in a dedicated subdirectory.
#skin = Mobile
skin = sofaskin
enable = false
HTML_ROOT = /var/www/html/weewx

[[StandardReport]]
# This is the old "Standard" skin. By default, it is not enabled.
#skin = Standard
skin = Sofaskin
enable = true


this is in LOG.
Jun 17 07:59:54 povej weewx[31558]: interceptor: ServerThread: GET: 
ID=IDO10==25.0=19.6=19.5=19.6=59=99=0.0=0.0=242=979.6=1018.6=0.0=3.0=3.0=9.0=9.0=21488.5=704=2019-6-17
 
5:59:54=WS-1002 V2.4.6=updateraw=1=5
Jun 17 07:59:54 povej weewx[31558]: interceptor: MainThread: raw data: 
ID=IDO10=np8xkt1j=25.0=19.6=19.5=19.6=59=99=0.0=0.0=242=979.6=1018.6=0.0=3.0=3.0=9.0=9.0=21488.5=704=2019-6-17
 
5:59:54=WS-1002 V2.4.6=updateraw=1=5
Jun 17 07:59:54 povej weewx[31558]: interceptor: MainThread: using 
rain_total 9.0 from yearlyrain
Jun 17 07:59:54 povej weewx[31558]: interceptor: MainThread: firmware 
WS-1002 V2.4.6: baromin is barometer
Jun 17 07:59:54 povej weewx[31558]: interceptor: MainThread: ignored 
parameter weeklyrain=3.0
Jun 17 07:59:54 povej weewx[31558]: interceptor: MainThread: ignored 
parameter monthlyrain=9.0
Jun 17 07:59:54 povej weewx[31558]: interceptor: MainThread: ignored 
parameter realtime=1
Jun 17 07:59:54 povej weewx[31558]: interceptor: MainThread: ignored 
parameter rtfreq=5
Jun 17 07:59:55 povej weewx[31558]: interceptor: MainThread: ignored 
parameter action=updateraw
Jun 17 07:59:55 povej weewx[31558]: interceptor: MainThread: ignored 
parameter PASSWORD=
Jun 17 07:59:55 povej weewx[31558]: interceptor: MainThread: ignored 
parameter ID=IDO10
Jun 17 07:59:55 povej weewx[31558]: interceptor: MainThread: ignored 
parameter softwaretype=WS-1002 V2.4.6
Jun 17 07:59:55 povej weewx[31558]: interceptor: MainThread: ignored 
parameter relbaro=1018.6
Jun 17 07:59:55 povej weewx[31558]: interceptor: MainThread: raw packet: 
{'humidity_in': 59.0, 'wind_speed': 0.0, 'temperature_in': 25.0, 
'windchill': 19.6, 'dewpoint': 19.5, 'luminosity': 21488.5, 'humidity_out': 
99.0, 'uv': 704.0, 'radiation': 231.0013749997, 'rain': 0.0, 
'dateTime': 1560751194, 'pressure': 979.6, 'temperature_out': 19.6, 
'wind_dir': 242.0, 'rain_total': 9.0, 'rain_rate': 0.0, 'usUnits': 16, 
'wind_gust': 0.0}
Jun 17 07:59:55 povej weewx[31558]: interceptor: MainThread: mapped packet: 
{'windchill': 19.6, 'dewpoint': 19.5, 'pressure': 979.6, 'outHumidity': 
99.0, 'UV': 704.0, 'radiation': 231.0013749997, 'rain': 0.0, 
'dateTime': 1560751194, 'windDir': 242.0, 'outTemp': 19.6, 'windSpeed': 
0.0, 'inHumidity': 59.0, 'inTemp': 25.0, 'windGust': 0.0, 'rainRate': 0.0, 
'usUnits': 16}
Jun 17 08:00:05 povej weewx[31558]: interceptor: MainThread: empty queue
Jun 17 08:00:11 povej weewx[31558]: interceptor: ServerThread: GET: 
ID=IDO10==25.0=19.6=19.5=19.6=59=99=0.0=0.0=248=979.6=1018.6=0.0=3.0=3.0=9.0=9.0=21426.4=705=2019-6-17
 
6:0:10=WS-1002 V2.4.6=updateraw=1=5
Jun 17 08:00:11 povej weewx[31558]: interceptor: MainThread: raw data: 
ID=IDO10=np8xkt1j=25.0=19.6=19.5=19.6=59=99=0.0=0.0=248=979.6=1018.6=0.0=3.0=3.0=9.0=9.0=21426.4=705=2019-6-17
 
6:0:10=WS-1002 V2.4.6=updateraw=1=5
Jun 17 08:00:11 povej weewx[31558]: interceptor: MainThread: using 
rain_total 9.0 from yearlyrain
Jun 17 08:00:11 povej weewx[31558]: interceptor: MainThread: firmware 
WS-1002 V2.4.6: baromin is 

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

I have copied sofaskin into folder /etc/weewx/skins/sofaskin

end enable it in weewx.conf

#   This section specifies what reports, using which skins, to generate.

[StdReport]

# Where the skins reside, relative to WEEWX_ROOT
SKIN_ROOT = /etc/weewx/skins

# Where the generated reports should go, relative to WEEWX_ROOT
HTML_ROOT = /var/www/html/weewx

# The database binding indicates which data should be used in reports.
data_binding = wx_binding

# Whether to log a successful operation
log_success = True

# Whether to log an unsuccessful operation
log_failure = False

# Each of the following subsections defines a report that will be run.
# See the customizing guide to change the units, plot types and line
# colors, modify the fonts, display additional sensor data, and other
# customizations. Many of those changes can be made here by overriding
# parameters, or by modifying templates within the skin itself.

[[SeasonsReport]]
# The SeasonsReport uses the 'Seasons' skin, which contains the
# images, templates and plots for the report.
#skin = Seasons
skin = sofaskin
enable = false

[[SmartphoneReport]]
# The SmartphoneReport uses the 'Smartphone' skin, and the images 
and
# files are placed in a dedicated subdirectory.
#skin = Smartphone
skin = sofaskin
enable = false
HTML_ROOT = /var/www/html/weewx

[[MobileReport]]
# The MobileReport uses the 'Mobile' skin, and the images and files
# are placed in a dedicated subdirectory.
#skin = Mobile
skin = sofaskin
enable = false
HTML_ROOT = /var/www/html/weewx

[[StandardReport]]
# This is the old "Standard" skin. By default, it is not enabled.
#skin = Standard
skin = Sofaskin
enable = true


Dne nedelja, 16. junij 2019 22.17.46 UTC+2 je oseba gjr80 napisala:
>
> You say ‘whatever I do’ - exactly what have have you tried? Have you 
> restarted WeeWX? What does the log show when debug = 1? 
>
> 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/8558cce7-55ee-4fd3-98f4-41e34f1e4266%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

One more thing.
In latest weewx.conf it is changed about skin.
I use sofaskin and whatever I do weewx doesn't want to use that skin.
I have change this line but weewx doesn't change skin.

[[StandardReport]]
# This is the old "Standard" skin. By default, it is not enabled.
#skin = Standard
skin = Sofaskin
enable = true


Dne nedelja, 16. junij 2019 21.40.31 UTC+2 je oseba Damjan Hajsek napisala:
>
> thank you.
> I see data now it works.
>
>
> Dne nedelja, 16. junij 2019 14.21.58 UTC+2 je oseba mwall napisala:
>>
>> On Sunday, June 16, 2019 at 4:53:31 AM UTC-4, Damjan Hajsek wrote:
>>>
>>> I will try to find help with creator of driver. I see they had the same 
>>> problems before
>>>
>>
>> the problem is not the interceptor, it is your configuration.  you are 
>> listening on port 9900, but your station is not sending to that port
>>
>> to diagnose interceptor issues, you must first run the interceptor 
>> directly.  shut down weewx, then try something like this:
>>
>> sudo PYTHONPATH=/usr/share/weewx python 
>> /usr/share/weewx/user/interceptor.py --device=observer --mode=listen 
>> --port=80
>>
>> when you see data from that, put those settings into the [Interceptor] 
>> section of weewx configuration, then run weewx (still in debug mode)
>>
>> [Interceptor]
>> device_type = observer
>> mode = listen
>> port = 80
>>
>> m
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/996fc926-4f68-4d1c-817a-d91eaf0453e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

thank you.
I see data now it works.


Dne nedelja, 16. junij 2019 14.21.58 UTC+2 je oseba mwall napisala:
>
> On Sunday, June 16, 2019 at 4:53:31 AM UTC-4, Damjan Hajsek wrote:
>>
>> I will try to find help with creator of driver. I see they had the same 
>> problems before
>>
>
> the problem is not the interceptor, it is your configuration.  you are 
> listening on port 9900, but your station is not sending to that port
>
> to diagnose interceptor issues, you must first run the interceptor 
> directly.  shut down weewx, then try something like this:
>
> sudo PYTHONPATH=/usr/share/weewx python 
> /usr/share/weewx/user/interceptor.py --device=observer --mode=listen 
> --port=80
>
> when you see data from that, put those settings into the [Interceptor] 
> section of weewx configuration, then run weewx (still in debug mode)
>
> [Interceptor]
> device_type = observer
> mode = listen
> port = 80
>
> m
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b23f0178-ad19-490b-8df8-824d48360bb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

I will try to find help with creator of driver. I see they had the same 
problems before.

Dne nedelja, 16. junij 2019 10.47.32 UTC+2 je oseba Andrew Milner napisala:
>
> HOORAY - now we have real progress and debug messages at last!!
>
> However it now appears your interceptor driver is not receiving any data 
> at all.
>
> I cannot help here - you need an interceptor user but there does appear to 
> be a lot of debug/checking information back in the wiki to try and identify 
> problems when no dta is being received.
>
> Good luck and hope you resolve this finally!
>
>
>
> On Sunday, 16 June 2019 01:18:00 UTC+3, Damjan Hajsek wrote:
>>
>> Thank you.
>> Finally, I thought I was insane, trying everything.
>> I think some update must happend on april 4th when weewx stops to work.
>>
>> Now I have a log and this is all what I have for weewx.
>>
>> Jun 16 00:14:01 povej weewx: Starting weewx: [  V redu  ]
>> Jun 16 00:14:01 povej systemd: Started SYSV: start and stop the weewx 
>> weather system.
>> Jun 16 00:14:01 povej weewx[503]: engine: Using configuration file 
>> /etc/weewx/weewx.conf
>> Jun 16 00:14:01 povej weewx[503]: engine: Debug is 1
>> Jun 16 00:14:01 povej weewx[503]: engine: Initializing engine
>> Jun 16 00:14:01 povej weewx[503]: engine: Loading station type 
>> Interceptor (user.interceptor)
>> Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: driver version 
>> is 0.45
>> Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: device type: 
>> observer
>> Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: sensor map: 
>> None
>> Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: mode is listen
>> Jun 16 00:14:01 povej weewx[503]: interceptor: MainThread: listen on :9900
>> Jun 16 00:14:01 povej weewx[503]: interceptor: ServerThread: start tcp 
>> server
>> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
>> weewx.engine.StdTimeSynch
>> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
>> weewx.engine.StdTimeSynch
>> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
>> weewx.engine.StdConvert
>> Jun 16 00:14:01 povej weewx[503]: engine: StdConvert target unit is 0x1
>> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
>> weewx.engine.StdConvert
>> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
>> weewx.engine.StdCalibrate
>> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
>> weewx.engine.StdCalibrate
>> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
>> weewx.engine.StdQC
>> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
>> weewx.engine.StdQC
>> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
>> weewx.wxservices.StdWXCalculate
>> Jun 16 00:14:01 povej weewx[503]: 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
>> Jun 16 00:14:01 povej weewx[503]: wxcalculate: The following algorithms 
>> will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
>> weewx.wxservices.StdWXCalculate
>> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
>> weewx.engine.StdArchive
>> Jun 16 00:14:01 povej weewx[503]: engine: Archive will use data binding 
>> wx_binding
>> Jun 16 00:14:01 povej weewx[503]: engine: Record generation will be 
>> attempted in 'hardware'
>> Jun 16 00:14:01 povej weewx[503]: engine: Using archive interval of 60 
>> seconds (specified in weewx configuration)
>> Jun 16 00:14:01 povej weewx[503]: engine: Use LOOP data in hi/low 
>> calculations: 1
>> Jun 16 00:14:01 povej weewx[503]: manager: Daily summary version is 2.0
>> Jun 16 00:14:01 povej weewx[503]: engine: Using binding 'wx_binding' to 
>> database 'weewx'
>> Jun 16 00:14:01 povej weewx[503]: manager: Starting backfill of daily 
>> summaries
>> Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
>> weewx.engine.StdArchive
>> Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
>> weewx.restx.StdStationRegistry
>> Jun 16 00:14:01 povej weewx[503]: restx: StationRegistry: Registrat

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

 loading service 
weewx.restx.StdAWEKAS
Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
weewx.engine.StdPrint
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
weewx.engine.StdPrint
Jun 16 00:14:01 povej weewx[503]: engine: Loading service 
weewx.engine.StdReport
Jun 16 00:14:01 povej weewx[503]: engine: Finished loading service 
weewx.engine.StdReport
Jun 16 00:14:01 povej weewx[503]: engine: Starting up weewx version 3.9.1
Jun 16 00:14:01 povej weewx[503]: engine: Station does not support reading 
the time
Jun 16 00:14:01 povej weewx[503]: engine: Starting main packet loop.
Jun 16 00:14:01 povej weewx[503]: manager: Daily summary version is 2.0
Jun 16 00:14:11 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:14:21 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:14:31 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:14:41 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:14:51 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:15:01 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:15:11 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:15:21 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:15:31 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:15:41 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:15:51 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:16:01 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:16:11 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:16:21 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:16:25 povej fail2ban.filter[28122]: INFO [apache-fakegooglebot] 
Ignore 66.249.69.150 by command
Jun 16 00:16:25 povej fail2ban.filter[28122]: INFO [apache-fakegooglebot] 
Ignore 66.249.69.150 by command
Jun 16 00:16:31 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:16:41 povej weewx[503]: interceptor: MainThread: empty queue
Jun 16 00:16:51 povej weewx[503]: interceptor: MainThread: empty queue


Dne sobota, 15. junij 2019 17.09.28 UTC+2 je oseba gjr80 napisala:
>
> Thanks, so if I am reading the centos7.6 /etc/rsyslog.conf correctly only 
> info and above go to /var/log/messages. There is nothing covering debug 
> at all so I expect that is why debug is (effectively) discarded. We could 
> send them to another file but that will make debugging difficult so let's 
> just send debug to /var/log/messages as well.
>
> Damjan. Try the following:
>
> 1. edit /etc/rsyslog.conf and add the following to the bottom of the file 
> (you will need privileged access to edit the file):
>
> # all debug to /var/log/messages
> *.=debug /var/log/messages
>
> 2. restart rsyslog:
>
> $ sudo systemctl restart rsyslog
>
> 3. make sure /etc/weewx/weewx.conf has debug=1
>
> 4. restart WeeWX:
>
> $ sudo systemctl restart weewx
>
> check /var/log/messages and you should see some debug output.
>
> Gary
>
> On Sunday, 16 June 2019 00:36:45 UTC+10, Leon Shaner wrote:
>>
>> Gary, good sleuthing.
>>
>> Could it be that the debug messages simply go to a different file, such 
>> as /var/log/debug?
>>
>> Check to see where the debug logs are pointed in /etc/rsyslog.conf.
>>
>> Also, see here:
>>
>> https://www.the-art-of-web.com/system/rsyslog-config/
>>
>> Regards,
>> \Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPhone)
>>
>> On Jun 15, 2019, at 10:19 AM, gjr80  wrote:
>>
>> I guess the question is where to from here given that it appears you 
>> cannot get any debug output when running under centos7.6. I think we can 
>> assume that your system is running properly (debug issue aside) with the 
>> simulator driver. Troubleshooting the interceptor driver is going to be 
>> difficult without any debug output. One thing I did notice, some time ago 
>> Matthew suggested running WeeWX (with the interceptor driver) directly. You 
>> could try that again, remember what we are seeking when running WeeWX 
>> directly is not the log output but rather the console output, ie what you 
>> see on the screen. I notice you don't appear to have provided the console 
>> output, rather you gave the log output.
>>
>> Gary
>>
>> On Saturday, 15 June 2019 02:28:14 UTC+10, Damjan Hajsek wrote:
>>>
>>> Ok I did logs again I hope this time better.
>>>
>>>
>>> Dne petek, 14. junij 2019 14.44.03 UTC+2 je oseba Andrew Milner napisala:
>>>>
>>>> Not really, no
>>>>
>>>> The first part appears to show normal running with archive records 
>>>> every minute - but no log for th

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Thank you.
I use shorewall on my server and I have locked it on my home IP where 
weather station is.
also fail2ban have my home IP whitelisted


Dne petek, 14. junij 2019 18.52.23 UTC+2 je oseba Leon Shaner napisala:
>
> Damjan,
> A long time ago you mentioned that your troubles all started when you 
> updated some OS pkgs.
> Have you seen this thread?  Since you are using interceptor, which must 
> accept connections from remote, it could be relevant:
>
> https://www.centos.org/forums/viewtopic.php?t=69009
>
> To rule it out, perhaps you could temporarily disable firewalld and 
> fail2ban?
>
> $ sudo systemctl disable firewalld
> $ sudo systemctl stop firewalld
>
> $ sudo systemctl disable fail2ban
> $ sudo systemctl stop fail2ban
>
> If disabling those helps with weewx, then you may need to explicitly add 
> rules for interceptor on 990 to be allowed, that way you can have the 
> benefit of those firewalls without breaking weewx.
>
> In the meantime you probably want to "enable" and "start" them so your 
> system isn't left vulnerable.
>
> Lemme know if disabling those helps and then I can dig out the proper 
> syntax to add a rule to allow interceptor to connect even with firewalld 
> active.   It may still not work, though, depending on the outcome of that 
> thread mentioned far above.  That last comment calls an an issue for people 
> upgrading from CentOS 7.5 to 7.6, but doesn't explicitly say how he got it 
> working again.  :-/
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad)
>
> On Jun 14, 2019, at 12:28 PM, Damjan Hajsek  > wrote:
>
> 
> Ok I did logs again I hope this time better.
>
>
> Dne petek, 14. junij 2019 14.44.03 UTC+2 je oseba Andrew Milner napisala:
>>
>> Not really, no
>>
>> The first part appears to show normal running with archive records every 
>> minute - but no log for the startup process
>>
>> The second part, manual running , shows us the startup but only loop data 
>> - it runs for under a minute so does not give the coverage for two archive 
>> periods (which in your case would be at least 2 minutes)
>>
>> The third part says debug disabled - but there does not appear to be any 
>> section where debug is enabled - so it is not clear if you are enabling 
>> debug correctly or not.
>>
>> it is much better to just attach the logfile directly rather than trying 
>> to extract relevant portions.  you can identify sections by the timestamps 
>> of when you did things
>>
>> we are making slow progress - but have yet to see debug successfully 
>> enabled!!  However, simulator does appear to be OK - and indeed the website 
>> confirms that simulator is running just fine.
>>
>> See if you can get us some log which shows debug enabled at startup!!
>>
>>
>>
>>
>>
>> On Friday, 14 June 2019 15:13:07 UTC+3, Damjan Hajsek wrote:
>>>
>>> here it is.
>>> Is this ok what I attach?
>>> regards
>>>
>>> Dne petek, 14. junij 2019 12.45.41 UTC+2 je oseba Andrew Milner napisala:
>>>>
>>>> Keep running the simulator for a while, but can you now give us the log 
>>>> from startup for at least two archive intervals FOR SIMULATOR so that we 
>>>> can be SURE everything is working as it should be.  Then, if that looks 
>>>> ok, 
>>>> can you stop weewx, set debug = 1, restart weewx and again attach the log 
>>>> from startup until at least two archive intervals.  This should show that 
>>>> all is ok with debug also!!
>>>>
>>>>  
>>>>
>>>> On Friday, 14 June 2019 12:36:32 UTC+3, Damjan Hajsek wrote:
>>>>>
>>>>> https://github.com/matthewwall/weewx-interceptor
>>>>>
>>>>>  this is what I have for interceptor in weewx.conf
>>>>>
>>>>> [Interceptor]
>>>>> # This section is for the network traffic interceptor driver.
>>>>> 
>>>>> # The driver to use:
>>>>> driver = user.interceptor
>>>>> 
>>>>> # Specify the hardware device to capture.  Options include:
>>>>> #   acurite-bridge - acurite internet bridge, smarthub, or access
>>>>> #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
>>>>> #   lw30x - oregon scientific LW301/LW302
>>>>> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
>>>>> #   wu-client - any hardware that uses the weather underground

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Ok I did logs again I hope this time better.


Dne petek, 14. junij 2019 14.44.03 UTC+2 je oseba Andrew Milner napisala:
>
> Not really, no
>
> The first part appears to show normal running with archive records every 
> minute - but no log for the startup process
>
> The second part, manual running , shows us the startup but only loop data 
> - it runs for under a minute so does not give the coverage for two archive 
> periods (which in your case would be at least 2 minutes)
>
> The third part says debug disabled - but there does not appear to be any 
> section where debug is enabled - so it is not clear if you are enabling 
> debug correctly or not.
>
> it is much better to just attach the logfile directly rather than trying 
> to extract relevant portions.  you can identify sections by the timestamps 
> of when you did things
>
> we are making slow progress - but have yet to see debug successfully 
> enabled!!  However, simulator does appear to be OK - and indeed the website 
> confirms that simulator is running just fine.
>
> See if you can get us some log which shows debug enabled at startup!!
>
>
>
>
>
> On Friday, 14 June 2019 15:13:07 UTC+3, Damjan Hajsek wrote:
>>
>> here it is.
>> Is this ok what I attach?
>> regards
>>
>> Dne petek, 14. junij 2019 12.45.41 UTC+2 je oseba Andrew Milner napisala:
>>>
>>> Keep running the simulator for a while, but can you now give us the log 
>>> from startup for at least two archive intervals FOR SIMULATOR so that we 
>>> can be SURE everything is working as it should be.  Then, if that looks ok, 
>>> can you stop weewx, set debug = 1, restart weewx and again attach the log 
>>> from startup until at least two archive intervals.  This should show that 
>>> all is ok with debug also!!
>>>
>>>  
>>>
>>> On Friday, 14 June 2019 12:36:32 UTC+3, Damjan Hajsek wrote:
>>>>
>>>> https://github.com/matthewwall/weewx-interceptor
>>>>
>>>>  this is what I have for interceptor in weewx.conf
>>>>
>>>> [Interceptor]
>>>> # This section is for the network traffic interceptor driver.
>>>> 
>>>> # The driver to use:
>>>> driver = user.interceptor
>>>> 
>>>> # Specify the hardware device to capture.  Options include:
>>>> #   acurite-bridge - acurite internet bridge, smarthub, or access
>>>> #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
>>>> #   lw30x - oregon scientific LW301/LW302
>>>> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
>>>> #   wu-client - any hardware that uses the weather underground 
>>>> protocol
>>>> #device_type = acurite-bridge
>>>> device_type = observer
>>>> port = 990
>>>>
>>>

-- 
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/57255078-0935-48db-b1c3-2ce7813b488a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Debug disabled
# 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

Jun 14 18:12:38 povej weewx: Starting weewx: [  V redu  ]
Jun 14 18:12:38 povej weewx[18473]: engine: Using configuration file 
/etc/weewx/weewx.conf
Jun 14 18:12:38 povej weewx[18473]: engine: Loading station type Simulator 
(weewx.drivers.simulator)
Jun 14 18:12:38 povej weewx[18473]: engine: StdConvert target unit is 0x1
Jun 14 18:12:38 povej weewx[18473]: 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=p

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

here it is.
Is this ok what I attach?
regards

Dne petek, 14. junij 2019 12.45.41 UTC+2 je oseba Andrew Milner napisala:
>
> Keep running the simulator for a while, but can you now give us the log 
> from startup for at least two archive intervals FOR SIMULATOR so that we 
> can be SURE everything is working as it should be.  Then, if that looks ok, 
> can you stop weewx, set debug = 1, restart weewx and again attach the log 
> from startup until at least two archive intervals.  This should show that 
> all is ok with debug also!!
>
>  
>
> On Friday, 14 June 2019 12:36:32 UTC+3, Damjan Hajsek wrote:
>>
>> https://github.com/matthewwall/weewx-interceptor
>>
>>  this is what I have for interceptor in weewx.conf
>>
>> [Interceptor]
>> # This section is for the network traffic interceptor driver.
>> 
>> # The driver to use:
>> driver = user.interceptor
>> 
>> # Specify the hardware device to capture.  Options include:
>> #   acurite-bridge - acurite internet bridge, smarthub, or access
>> #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
>> #   lw30x - oregon scientific LW301/LW302
>> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
>> #   wu-client - any hardware that uses the weather underground 
>> protocol
>> #device_type = acurite-bridge
>> device_type = observer
>> port = 990
>>
>

-- 
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/11fc26fb-7694-4c40-98b7-6eaecc3c6dec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Log 
Jun 14 13:59:15 povej weewx[4536]: manager: Added record 2019-06-14 13:59:00 
CEST (1560513540) to database 'weewx'
Jun 14 13:59:15 povej weewx[4536]: manager: Added record 2019-06-14 13:59:00 
CEST (1560513540) to daily summary in 'weewx'
Jun 14 13:59:15 povej weewx[4536]: restx: Wunderground-PWS: Published record 
2019-06-14 13:59:00 CEST (1560513540)
Jun 14 13:59:16 povej weewx[4536]: cheetahgenerator: Generated 8 files for 
report SeasonsReport in 0.87 seconds
Jun 14 13:59:16 povej weewx[4536]: imagegenerator: Generated 14 images for 
SeasonsReport in 0.49 seconds
Jun 14 13:59:16 povej weewx[4536]: copygenerator: copied 0 files to 
/var/www/html/weewx
Jun 14 14:00:15 povej weewx[4536]: manager: Added record 2019-06-14 14:00:00 
CEST (1560513600) to database 'weewx'
Jun 14 14:00:15 povej weewx[4536]: manager: Added record 2019-06-14 14:00:00 
CEST (1560513600) to daily summary in 'weewx'
Jun 14 14:00:15 povej weewx[4536]: restx: Wunderground-PWS: Published record 
2019-06-14 14:00:00 CEST (1560513600)
Jun 14 14:00:16 povej weewx[4536]: cheetahgenerator: Generated 8 files for 
report SeasonsReport in 1.17 seconds
Jun 14 14:00:18 povej weewx[4536]: imagegenerator: Generated 28 images for 
SeasonsReport in 2.32 seconds
Jun 14 14:00:18 povej weewx[4536]: copygenerator: copied 0 files to 
/var/www/html/weewx

Jun 14 14:01:15 povej weewx[4536]: manager: Added record 2019-06-14 14:01:00 
CEST (1560513660) to database 'weewx'
Jun 14 14:01:15 povej weewx[4536]: manager: Added record 2019-06-14 14:01:00 
CEST (1560513660) to daily summary in 'weewx'
Jun 14 14:01:15 povej weewx[4536]: restx: Wunderground-PWS: Published record 
2019-06-14 14:01:00 CEST (1560513660)
Jun 14 14:01:16 povej weewx[4536]: cheetahgenerator: Generated 8 files for 
report SeasonsReport in 1.05 seconds
Jun 14 14:01:16 povej weewx[4536]: imagegenerator: Generated 14 images for 
SeasonsReport in 0.29 seconds
Jun 14 14:01:16 povej weewx[4536]: copygenerator: copied 0 files to 
/var/www/html/weewx

Jun 14 14:02:15 povej weewx[4536]: manager: Added record 2019-06-14 14:02:00 
CEST (1560513720) to database 'weewx'
Jun 14 14:02:15 povej weewx[4536]: manager: Added record 2019-06-14 14:02:00 
CEST (1560513720) to daily summary in 'weewx'
Jun 14 14:02:15 povej weewx[4536]: restx: Wunderground-PWS: Published record 
2019-06-14 14:02:00 CEST (1560513720)
Jun 14 14:02:16 povej weewx[4536]: cheetahgenerator: Generated 8 files for 
report SeasonsReport in 1.11 seconds
Jun 14 14:02:16 povej weewx[4536]: imagegenerator: Generated 14 images for 
SeasonsReport in 0.45 seconds
Jun 14 14:02:16 povej weewx[4536]: copygenerator: copied 0 files to 
/var/www/html/weewx

Log from manual starting

Jun 14 14:03:49 povej systemd: Stopped SYSV: start and stop the weewx weather 
system.
Jun 14 14:04:00 povej weewx[25422]: engine: Initializing weewx version 3.9.1
Jun 14 14:04:00 povej weewx[25422]: engine: Using Python 2.7.5 (default, Apr  9 
2019, 14:30:50) #012[GCC 4.8.5 20150623 (Red Hat 4.8

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

https://github.com/matthewwall/weewx-interceptor

 this is what I have for interceptor in weewx.conf

[Interceptor]
# This section is for the network traffic interceptor driver.

# The driver to use:
driver = user.interceptor

# Specify the hardware device to capture.  Options include:
#   acurite-bridge - acurite internet bridge, smarthub, or access
#   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
#   lw30x - oregon scientific LW301/LW302
#   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
#   wu-client - any hardware that uses the weather underground protocol
#device_type = acurite-bridge
device_type = observer
port = 990

-- 
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/e8e3cd25-9e0d-4449-989a-6fe4b69acf3a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Yes I did. When I have installed it it worked.
Now I have reconfigure it for simulator driver and it works.
https://vreme.povej.net
so it really is something with driver, what I can do to check what it is?


Dne petek, 14. junij 2019 11.24.55 UTC+2 je oseba gjr80 napisala:
>
> I think people are trying to help, it is just without a debug log it is 
> rather difficult to determine what is going on and therefore what might be 
> wrong. Also, if settings in weewx.conf are being ignored (eg debug=1) it 
> begs the question what else is amiss.
>
> So when you installed WeeWX did you run it first with the simulator to 
> prove you have a properly functioning WeeWX install? If not perhaps you 
> should take a step back and get WeeWX running with the simulator. That at 
> least proves WeeWX is functioning as it should before you move on to a more 
> complex setup.
>
> 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/fbdba08a-c849-4526-8cab-d4c67455fdbb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

First time I have installed weewx manually, just copy tar on server and 
install it.

Now on new server I have downloaded weewx-3.9.1-1.rhel.noarch.rpm 
 and install it.
than install driver interceptor and setup everything.
I even changed port from  to 9900.

I am really desperate, spend alof of hours try to solve this and it was not 
possible, now on new server it is the same.

Have somebody please any idea what I can do???
Delete all and install it again?
what if it is a problem with interceptor driver?
I have myweather station at home and my weewx server is at home, that's why 
I use interceptor.

regards

Dne petek, 14. junij 2019 10.18.32 UTC+2 je oseba Andrew Milner napisala:
>
> as always, my mistake. sorry.
>
> On Friday, 14 June 2019 10:48:31 UTC+3, gjr80 wrote:
>>
>> I agree something is not right, but it is not WEEWX_ROOT.  For an other 
>> than setup.py install WEEWX_ROOT is indeed / - 
>> http://weewx.com/docs/usersguide.htm#Where_to_find_things refers.
>>
>> 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/66c97157-589d-40f2-a0b5-2a163dd9f0b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Sorry all of that I already did on old server.
Below I did this again, no other logs. This is the reason why I had to 
reinstall server again and again not working.
I run manually again fev times and all what I get in log is

# 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

sudo weewxd /etc/weewx/weewx.conf

Jun 14 09:00:23 povej weewx[6760]: engine: Main loop exiting. Shutting 
engine down.
Jun 14 09:00:23 povej weewx[6760]: interceptor: MainThread: shutting down 
server thread
Jun 14 09:00:24 povej weewx[6760]: engine: Keyboard interrupt.
Jun 14 09:00:26 povej weewx[11161]: engine: Initializing weewx version 3.9.1
Jun 14 09:00:26 povej weewx[11161]: engine: Using Python 2.7.5 (default, 
Apr  9 2019, 14:30:50) #012[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]
Jun 14 09:00:26 povej weewx[11161]: engine: Platform 
Linux-3.10.0-957.12.2.el7.x86_64-x86_64-with-centos-7.6.1810-Core
Jun 14 09:00:26 povej weewx[11161]: engine: Locale is 'sl_SI.UTF-8'
Jun 14 09:00:26 povej weewx[11161]: engine: Using configuration file 
/etc/weewx/weewx.conf
Jun 14 09:00:26 povej weewx[11161]: engine: Loading station type 
Interceptor (user.interceptor)
Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: driver version 
is 0.45
Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: device type: 
acurite-bridge
Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: sensor map: 
None
Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: mode is listen
Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: listen on :9900
Jun 14 09:00:26 povej weewx[11161]: engine: StdConvert target unit is 0x1
Jun 14 09:00:26 povej weewx[11161]: 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
Jun 14 09:00:26 povej weewx[11161]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Jun 14 09:00:26 povej weewx[11161]: engine: Archive will use data binding 
wx_binding
Jun 14 09:00:26 povej weewx[11161]: engine: Record generation will be 
attempted in 'hardware'
Jun 14 09:00:26 povej weewx[11161]: engine: Using archive interval of 60 
seconds (specified in weewx configuration)
Jun 14 09:00:26 povej weewx[11161]: engine: Using binding 'wx_binding' to 
database 'weewx'
Jun 14 09:00:26 povej weewx[11161]: manager: Starting backfill of daily 
summaries
Jun 14 09:00:26 povej weewx[11161]: restx: StationRegistry: Registration 
not requested.
Jun 14 09:00:26 povej weewx[11161]: restx: Wunderground-PWS: Data for 
station IDO8 will be posted
Jun 14 09:00:26 povej weewx[11161]: restx: PWSweather: Posting not enabled.
Jun 14 09:00:26 povej weewx[11161]: restx: CWOP: Posting not enabled.
Jun 14 09:00:26 povej weewx[11161]: restx: WOW: Posting not enabled.
Jun 14 09:00:26 povej weewx[11161]: restx: AWEKAS: Posting not enabled.
Jun 14 09:00:26 povej weewx[11161]: engine: Starting up weewx version 3.9.1
Jun 14 09:00:26 povej weewx[11161]: engine: Starting main packet loop.

Dne petek, 14. junij 2019 03.25.32 UTC+2 je oseba Andrew Milner napisala:
>
> Have you done what Matthew asked some time ago and run weewx manually - 
> not as a daemon??
>
> Did you get any LOOP packets logged to the screen when you ran manually??
>
> The log you posted just shows a normal startup - although debug does not 
> appear to be set.  Did you edit the correct weewx,conf file when setting 
> debug=1??
>
>
>
> On Thursday, 13 June 2019 19:52:46 UTC+3, Damjan Hajsek wrote:
>>
>> Sorry I already post log from old centos server and it is the same on new 
>> centos server. All I have in log is only this
>>
>> Jun 13 18:50:56 povej systemd: Started SYSV: start and stop the weewx 
>> weather system.
>> Jun 13 18:50:56 povej weewx[15848]: engine: Using configuration file 
>> /etc/weewx/weewx.conf
>> Jun 13 18:50:56 povej weewx[15848]: engine: Loading station type 
>> Interceptor (user.interceptor)
&

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Sorry I already post log from old centos server and it is the same on new 
centos server. All I have in log is only this

Jun 13 18:50:56 povej systemd: Started SYSV: start and stop the weewx 
weather system.
Jun 13 18:50:56 povej weewx[15848]: engine: Using configuration file 
/etc/weewx/weewx.conf
Jun 13 18:50:56 povej weewx[15848]: engine: Loading station type 
Interceptor (user.interceptor)
Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: driver version 
is 0.45
Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: device type: 
acurite-bridge
Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: sensor map: 
None
Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: mode is listen
Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: listen on :9900
Jun 13 18:50:56 povej weewx[15848]: engine: StdConvert target unit is 0x1
Jun 13 18:50:56 povej weewx[15848]: 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
Jun 13 18:50:56 povej weewx[15848]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Jun 13 18:50:56 povej weewx[15848]: engine: Archive will use data binding 
wx_binding
Jun 13 18:50:56 povej weewx[15848]: engine: Record generation will be 
attempted in 'hardware'
Jun 13 18:50:56 povej weewx[15848]: engine: Using archive interval of 60 
seconds (specified in weewx configuration)
Jun 13 18:50:56 povej weewx[15848]: engine: Using binding 'wx_binding' to 
database 'weewx'
Jun 13 18:50:56 povej weewx[15848]: manager: Starting backfill of daily 
summaries
Jun 13 18:50:56 povej weewx[15848]: restx: StationRegistry: Registration 
not requested.
Jun 13 18:50:56 povej weewx[15848]: restx: Wunderground-PWS: Data for 
station IDOE7 will be posted
Jun 13 18:50:56 povej weewx[15848]: restx: PWSweather: Posting not enabled.
Jun 13 18:50:56 povej weewx[15848]: restx: CWOP: Posting not enabled.
Jun 13 18:50:56 povej weewx[15848]: restx: WOW: Posting not enabled.
Jun 13 18:50:56 povej weewx[15848]: restx: AWEKAS: Posting not enabled.
Jun 13 18:50:56 povej weewx[15848]: engine: Starting up weewx version 3.9.1
Jun 13 18:50:56 povej weewx[15848]: engine: Starting main packet loop.

Dne četrtek, 13. junij 2019 14.02.25 UTC+2 je oseba Andrew Milner napisala:
>
> what does weex say in the log when it is starting??  weewx outputs a lot 
> of information at startup - so you need to locate the log and post the log 
> to this forum then we may be able to help you further
>
>
>
> On Thursday, 13 June 2019 11:11:32 UTC+3, Damjan Hajsek wrote:
>>
>> Any idea how to solve this please?
>>
>> Dne torek, 11. junij 2019 22.24.35 UTC+2 je oseba Damjan Hajsek napisala:
>>>
>>> I have installed fresh new server centos 7.6
>>> also installed fresh installation of weewx 3.9.1
>>> also installed driver interceptor.
>>> And I get the same result as before.
>>> I have checked database doesn't change or fill up.
>>> there is no loop of weewx in logs and debug is 1
>>>
>>>
>>>  sudo strace -d /tmp/weewxd_strace.txt weewxd
>>> strace: ptrace_setoptions = 0x11
>>> strace: new tcb for pid 11807, active tcbs:1
>>> strace: [wait(0x80137f) = 11807] WIFSTOPPED,sig=SIGSTOP,EVENT_STOP (128)
>>> strace: pid 11807 has TCB_STARTUP, initializing it
>>> strace: [wait(0x80057f) = 11807] WIFSTOPPED,sig=SIGTRAP,EVENT_STOP (128)
>>> strace: [wait(0x00127f) = 11807] WIFSTOPPED,sig=SIGCONT
>>> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
>>> execve("/tmp/weewxd_strace.txt", ["/tmp/weewxd_strace.txt", "weewxd"], 
>>> [/* 18 vars */]strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
>>> ) = -1 ENOEXEC (Exec format error)
>>> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
>>> write(2, "strace: exec: Exec format error\n", 32strace: exec: Exec 
>>> format error
>>> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
>>> ) = 32
>>> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
>>> exit_group(1)   = ?
>>> strace: [wait(0x000100) = 11807] WIFEXITED,exitcode=1
>>> +++ exited with 1 +++
>>> strace: dropped tcb for pid 11807, 0 remain
>>>
>>>
>>>
>>> Dne četrtek, 25. april 2019 18.38.58 UTC+2 je oseba Leon Shaner napisala:
>>>>
>>>> Damian,
>&g

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Any idea how to solve this please?

Dne torek, 11. junij 2019 22.24.35 UTC+2 je oseba Damjan Hajsek napisala:
>
> I have installed fresh new server centos 7.6
> also installed fresh installation of weewx 3.9.1
> also installed driver interceptor.
> And I get the same result as before.
> I have checked database doesn't change or fill up.
> there is no loop of weewx in logs and debug is 1
>
>
>  sudo strace -d /tmp/weewxd_strace.txt weewxd
> strace: ptrace_setoptions = 0x11
> strace: new tcb for pid 11807, active tcbs:1
> strace: [wait(0x80137f) = 11807] WIFSTOPPED,sig=SIGSTOP,EVENT_STOP (128)
> strace: pid 11807 has TCB_STARTUP, initializing it
> strace: [wait(0x80057f) = 11807] WIFSTOPPED,sig=SIGTRAP,EVENT_STOP (128)
> strace: [wait(0x00127f) = 11807] WIFSTOPPED,sig=SIGCONT
> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
> execve("/tmp/weewxd_strace.txt", ["/tmp/weewxd_strace.txt", "weewxd"], [/* 
> 18 vars */]strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
> ) = -1 ENOEXEC (Exec format error)
> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
> write(2, "strace: exec: Exec format error\n", 32strace: exec: Exec format 
> error
> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
> ) = 32
> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133
> exit_group(1)   = ?
> strace: [wait(0x000100) = 11807] WIFEXITED,exitcode=1
> +++ exited with 1 +++
> strace: dropped tcb for pid 11807, 0 remain
>
>
>
> Dne četrtek, 25. april 2019 18.38.58 UTC+2 je oseba Leon Shaner napisala:
>>
>> Damian,
>>
>> Still very strange that we do not see debug = 1 echoed in the logs.
>>
>> At this point I am at a loss other than, perhaps you could preface the 
>> command with strace so we can see what is going on.  I expect it gets to a 
>> point where it is just more or less sleeping, doing nothing.
>>
>> I say that based on your previous "ps -elf" output where it showed 
>> 00:00:00 cpu time and was sleeping.   It is normal for the process to sleep 
>> when there is no input, but it should have to be doing at least some work 
>> from time to time.
>>
>> From the ps man page:
>>
>> PROCESS STATE CODES
>>Here are the different values that the s, stat and state output 
>> specifiers (header "STAT" or "S") will display to describe the state of a 
>> process:
>>
>>Duninterruptible sleep (usually IO)
>>Rrunning or runnable (on run queue)
>>Sinterruptible sleep (waiting for an event to complete)
>>Tstopped by job control signal
>>tstopped by debugger during the tracing
>>Wpaging (not valid since the 2.6.xx kernel)
>>Xdead (should never be seen)
>>Zdefunct ("zombie") process, terminated but not reaped 
>> by its parent
>>
>> Here is an example of how to strace the process and get the debug output 
>> into a file:
>>
>> $ sudo strace -o /tmp/weewxd_strace.txt weewxd
>>
>> You can "tail -f /tmp/weewxd_strace.txt" to see what is going on.
>> It will likely get to a point where it is quiet for long periods.  You 
>> can stop the strace after you see those a couple of times.
>>
>> The output could be quite large so you may want to compress it:
>>
>> $ gzip /tmp/weewxd_strace.txt
>>
>> Regards,
>> Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>
>> On Apr 25, 2019, at 10:30 AM, Damjan Hajsek  wrote:
>>
>> Hi
>> I have done this and it is all the same. I created some logs from 
>> manually starting weewx.
>> when I start weewx manually sudo weewxd /etc/weewx/weewx.conf'
>> it didn't crash, I stopped it.
>> here it is.
>>
>> http://zerobin.povej.net/?b06b1ad942bc51a2#34Nj1ed+8odSg7jHbjz7AU+WsqZ3yxPjZDB1EPHyVAk=
>>
>>
>>
>> Dne sreda, 24. april 2019 15.48.25 UTC+2 je oseba Leon Shaner napisala:
>>>
>>> Damian,
>>> You have to give wee_config a command.
>>> From the usage, you want this:
>>>
>>> $ sudo wee_config --reconfigure --config=/etc/weewx/weewx.conf
>>>
>>> (Although you can leave the --config part off, since your conf file is 
>>> located in the default location).
>>>
>>> But do be sure to back up the config file first...
>>>
>>> Regards,
>>> Leon
>>> --
>>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>>
>>

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Hi
What I did is first use some old weewx.conf file from last year and doesn't 
work either.
So I tried to reconfigure it but can't
when I run wee_config --help I get list of help
but when I do this I get
wee_config /etc/weewx/weewx.conf
No command specified.
wee_config --config=/etc/weewx/weewx.conf
No command specified.


Dne torek, 23. april 2019 15.17.24 UTC+2 je oseba Leon Shaner napisala:
>
> Damian,
>
> These logs still do not state debug = 1.
> It still could be that the weewx.conf isn't being parsed correctly, and 
> isn't even able to read the debug = 1 setting.
>
> Did you try my suggestions for how to "rebuild" the conf file?
>
> Regards,
> Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPhone)
>
>
>
> On Apr 23, 2019, at 8:45 AM, Damjan Hajsek  > wrote:
>
> Hi
> I have followed your instruction so I did all as described
> first turn off monit
> stop weewx
> debug = 1 was already set
> than I run weewx manually
> here is a log from that
>
>
> http://zerobin.povej.net/?a63b7ac09e222bcc#9Y5+B9WWtxXgUJWTKZWmzElusp9QRgEK5Pde606SvQc=
>
>
> http://zerobin.povej.net/?7d382c267025fd54#0p/b4Z0y5k7U3qFc8T/2Sgl0CbbU8ZkYxdSFCRh/I4I=
>
>
> Dne nedelja, 21. april 2019 15.41.04 UTC+2 je oseba mwall napisala:
>>
>> at this point in the thread it is not clear what is happening or what is 
>> the state of your system.
>>
>> so start over and explain what your configuration looks like now
>>
>> then, to diagnose weewx, do the following:
>>
>> - remove whatever it is that keeps restarting weewx
>> - stop weewx if it is running
>> - set debug=1 in your weewx configuration
>> - run weewx directly, not as a daemon
>> - if weewx crashes, post (1) the log prior to the crash, (2) the stack 
>> trace or other output from the console in which you started it
>>
>> m
>>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx...@googlegroups.com .
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Hi
I have followed your instruction so I did all as described
first turn off monit
stop weewx
debug = 1 was already set
than I run weewx manually
here is a log from that

http://zerobin.povej.net/?a63b7ac09e222bcc#9Y5+B9WWtxXgUJWTKZWmzElusp9QRgEK5Pde606SvQc=

http://zerobin.povej.net/?7d382c267025fd54#0p/b4Z0y5k7U3qFc8T/2Sgl0CbbU8ZkYxdSFCRh/I4I=


Dne nedelja, 21. april 2019 15.41.04 UTC+2 je oseba mwall napisala:
>
> at this point in the thread it is not clear what is happening or what is 
> the state of your system.
>
> so start over and explain what your configuration looks like now
>
> then, to diagnose weewx, do the following:
>
> - remove whatever it is that keeps restarting weewx
> - stop weewx if it is running
> - set debug=1 in your weewx configuration
> - run weewx directly, not as a daemon
> - if weewx crashes, post (1) the log prior to the crash, (2) the stack 
> trace or other output from the console in which you started it
>
> m
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

I have manualls started interceptor, what can I expect from it, because 
nothing changes?
 PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/interceptor.py 
--device=observer --mode=listen --port=

Dne torek, 16. april 2019 11.16.05 UTC+2 je oseba gjr80 napisala:
>
> There have been no changes to the database since 3.8.1, but this is not a 
> database problem. WeeWX is event driven and it relies on loop packets 
> and/or archive records from the driver triggering events which then cause 
> archive records to be created and saved to the database, reports to be 
> generated etc. None of that is happening which makes me think there may be 
> a driver issue given we have ruled out any other obvious issue. You are 
> using the interceptor driver which, due to its nature, is susceptible to 
> changes in your network. Perhaps something has changed on your network? 
> Perhaps you should try running the interceptor driver directly to take 
> WeeWX out of the equation and ensure you can get data from the interceptor 
> driver. Running the driver directly is covered in the interceptor driver 
> wiki entry. <https://github.com/matthewwall/weewx-interceptor>
>
> I would not be re-installing, as someone else here once said 'this is 
> Linux not Windows'.
>
> Gary
>
> On Tuesday, 16 April 2019 17:56:56 UTC+10, Damjan Hajsek wrote:
>>
>> Thank you I did this and no luck.
>> Can you tell me are there any changes in databasebetween version 3.8.1 
>> and the latest version??
>> If not I will install new weewx with rpm and than use old database.
>> regards
>>
>> Dne petek, 12. april 2019 15.34.53 UTC+2 je oseba Leon Shaner napisala:
>>>
>>> Damian,
>>>
>>> The symptoms I mentioned where it seems like weewxd is waiting for input 
>>> could be due to an issue parsing your conf file.  The wee_debug info you 
>>> posted has these lines:
>>>
>>> # This section can adjust data using calibration expressions.
>>>
>>> [1] 
>>>
>>>
>>> That looks like garbage.
>>> And yet way before that you have the typical section:
>>>
>>> #   This section can adjust data using calibration expressions.
>>>
>>> [StdCalibrate]
>>>
>>> [[Corrections]]
>>> # For each type, an arbitrary calibration expression can be 
>>> given.
>>> # It should be in the units defined in the StdConvert section.
>>> # Example:
>>> foo = foo + 0.2
>>>
>>>
>>> ##
>>>
>>>
>>> I suggest you try commenting out that extraneous "[1]" by preceding it 
>>> with # a la:
>>>
>>> #[1]
>>>
>>> Other than that you may need to make a backup of your weewx.conf and run 
>>> wee_config.  It may be confused by your current conf file, just as weewxd 
>>> appears to be.
>>> If all else fails, remove your conf file, run wee_config, and use diff 
>>> against the backup to see what else you need to add back, but with care to 
>>> only put the important parameters and to not reintroduce corruption.
>>>
>>> Regards,
>>> Leon
>>> --
>>> Leon Shaner :: Dearborn, Michigan (iPhone)
>>>
>>> https://twitter.com/AEtherZcythe
>>>
>>> On Apr 12, 2019, at 4:12 AM, Damjan Hajsek  wrote:
>>>
>>> hi
>>> here is my debug log.
>>>
>>> http://zerobin.povej.net/?6a7fc01d0616ffa9#Zj15RUTw5bxNGfoVlibcKTgn5D2oPqPX0Dg+rkHOeR4=
>>> don't know what happend here all what I do on server latelly was to 
>>> uninstall gnome desktop and reinstall it.
>>> Maybe is some part of python deleted or something like that?
>>>
>>> Damian
>>>
>>> Dne petek, 12. april 2019 01.14.27 UTC+2 je oseba gjr80 napisala:
>>>>
>>>> Let's be very clear here, you have logs they are not missing, that is 
>>>> what you have been posting over the last 12 hours. It would seem that once 
>>>> WeeWX has completed its loading/initialisation something is causing it to 
>>>> die or otherwise not do anything. You say that the  last log extract 
>>>> posted 
>>>> was with debug = 1, I don't doubt you but the log extract you provided 
>>>> is not with debug = 1. A log with debug = 1 will include somethign 
>>>> like this:
>>>>
>>>> Apr  5 22:54:29 stretch7 weewx[1012]: Starting weewx weather system: 
>>>> weewx.
>>>

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Thank you I did this and no luck.
Can you tell me are there any changes in databasebetween version 3.8.1 and 
the latest version??
If not I will install new weewx with rpm and than use old database.
regards

Dne petek, 12. april 2019 15.34.53 UTC+2 je oseba Leon Shaner napisala:
>
> Damian,
>
> The symptoms I mentioned where it seems like weewxd is waiting for input 
> could be due to an issue parsing your conf file.  The wee_debug info you 
> posted has these lines:
>
> # This section can adjust data using calibration expressions.
>
> [1] 
>
>
> That looks like garbage.
> And yet way before that you have the typical section:
>
> #   This section can adjust data using calibration expressions.
>
> [StdCalibrate]
>
> [[Corrections]]
> # For each type, an arbitrary calibration expression can be given.
> # It should be in the units defined in the StdConvert section.
> # Example:
> foo = foo + 0.2
>
>
> ##
>
>
> I suggest you try commenting out that extraneous "[1]" by preceding it 
> with # a la:
>
> #[1]
>
> Other than that you may need to make a backup of your weewx.conf and run 
> wee_config.  It may be confused by your current conf file, just as weewxd 
> appears to be.
> If all else fails, remove your conf file, run wee_config, and use diff 
> against the backup to see what else you need to add back, but with care to 
> only put the important parameters and to not reintroduce corruption.
>
> Regards,
> Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPhone)
>
> https://twitter.com/AEtherZcythe
>
> On Apr 12, 2019, at 4:12 AM, Damjan Hajsek  > wrote:
>
> hi
> here is my debug log.
>
> http://zerobin.povej.net/?6a7fc01d0616ffa9#Zj15RUTw5bxNGfoVlibcKTgn5D2oPqPX0Dg+rkHOeR4=
> don't know what happend here all what I do on server latelly was to 
> uninstall gnome desktop and reinstall it.
> Maybe is some part of python deleted or something like that?
>
> Damian
>
> Dne petek, 12. april 2019 01.14.27 UTC+2 je oseba gjr80 napisala:
>>
>> Let's be very clear here, you have logs they are not missing, that is 
>> what you have been posting over the last 12 hours. It would seem that once 
>> WeeWX has completed its loading/initialisation something is causing it to 
>> die or otherwise not do anything. You say that the  last log extract posted 
>> was with debug = 1, I don't doubt you but the log extract you provided 
>> is not with debug = 1. A log with debug = 1 will include somethign like 
>> this:
>>
>> Apr  5 22:54:29 stretch7 weewx[1012]: Starting weewx weather system: 
>> weewx.
>> Apr  5 22:54:29 stretch7 weewx[1024]: engine: Locale is 'en_AU.UTF-8'
>> Apr  5 22:54:29 stretch7 weewx[1024]: engine: pid file is /var/run/weewx.
>> pid
>> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Using configuration file /
>> home/weewx/weewx.conf
>> Apr  5 22:54:29 stretch7 weewx[1028]: engine: debug is 1
>> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Initializing engine
>> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Loading station type 
>> Simulator (weewx.drivers.simulator)
>> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Loading service weewx.
>> engine.StdTimeSynch
>> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Finished loading service 
>> weewx.engine.StdTimeSynch
>>
>> which shows debug is 1 and there is more detail about services being 
>> loaded/initialised.
>>
>> I think it might be a good time to have a look at your weewx.conf. Can 
>> you run the wee_debug utility 
>> <http://weewx.com/docs/utilities.htm#wee_debug_utility> and post its 
>> output. The advantage of running wee_debug is that it will locate the 
>> weewx.conf that WeeWX is using which is handy if you have more than one 
>> weewx.conf on your system. Before you post the wee_debug output just 
>> check the output for sensitive info like usernames, passwords, api keys 
>> etc. wee_debug does a good job at obfuscating such info but it's not 
>> perfect.
>>
>> Gary
>>
>> On Friday, 12 April 2019 02:37:20 UTC+10, Damjan Hajsek wrote:
>>>
>>> Hi
>>>
>>> [image: 2019-04-11 18_34_45-_etc_weewx_weewx.conf - root@194.249.178.190 
>>> - Editor - WinSCP.png]
>>> Yes I really changed debug to 1 in conf file. I am from GMT +2
>>> And I tested, date shows real date and time as it should be
>>> Why there is no logs I don't know, that is all what I get for fev hours 
>>> after starting it manually.
>>>
>>> Dne č

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

hi
here is my debug log.
http://zerobin.povej.net/?6a7fc01d0616ffa9#Zj15RUTw5bxNGfoVlibcKTgn5D2oPqPX0Dg+rkHOeR4=
don't know what happend here all what I do on server latelly was to 
uninstall gnome desktop and reinstall it.
Maybe is some part of python deleted or something like that?

Damian

Dne petek, 12. april 2019 01.14.27 UTC+2 je oseba gjr80 napisala:
>
> Let's be very clear here, you have logs they are not missing, that is what 
> you have been posting over the last 12 hours. It would seem that once WeeWX 
> has completed its loading/initialisation something is causing it to die or 
> otherwise not do anything. You say that the  last log extract posted was 
> with debug = 1, I don't doubt you but the log extract you provided is not 
> with debug = 1. A log with debug = 1 will include somethign like this:
>
> Apr  5 22:54:29 stretch7 weewx[1012]: Starting weewx weather system: weewx
> .
> Apr  5 22:54:29 stretch7 weewx[1024]: engine: Locale is 'en_AU.UTF-8'
> Apr  5 22:54:29 stretch7 weewx[1024]: engine: pid file is /var/run/weewx.
> pid
> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Using configuration file /
> home/weewx/weewx.conf
> Apr  5 22:54:29 stretch7 weewx[1028]: engine: debug is 1
> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Initializing engine
> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Loading station type 
> Simulator (weewx.drivers.simulator)
> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Loading service weewx.engine
> .StdTimeSynch
> Apr  5 22:54:29 stretch7 weewx[1028]: engine: Finished loading service 
> weewx.engine.StdTimeSynch
>
> which shows debug is 1 and there is more detail about services being 
> loaded/initialised.
>
> I think it might be a good time to have a look at your weewx.conf. Can 
> you run the wee_debug utility 
> <http://weewx.com/docs/utilities.htm#wee_debug_utility> and post its 
> output. The advantage of running wee_debug is that it will locate the 
> weewx.conf that WeeWX is using which is handy if you have more than one 
> weewx.conf on your system. Before you post the wee_debug output just 
> check the output for sensitive info like usernames, passwords, api keys 
> etc. wee_debug does a good job at obfuscating such info but it's not 
> perfect.
>
> Gary
>
> On Friday, 12 April 2019 02:37:20 UTC+10, Damjan Hajsek wrote:
>>
>> Hi
>>
>> [image: 2019-04-11 18_34_45-_etc_weewx_weewx.conf - root@194.249.178.190 
>> - Editor - WinSCP.png]
>> Yes I really changed debug to 1 in conf file. I am from GMT +2
>> And I tested, date shows real date and time as it should be
>> Why there is no logs I don't know, that is all what I get for fev hours 
>> after starting it manually.
>>
>> Dne četrtek, 11. april 2019 18.27.31 UTC+2 je oseba Leon Shaner napisala:
>>>
>>> Hi, Damjan,
>>>
>>> I do not see debug output.  Did you change debug = 0 to debug = 1 in the 
>>> conf file?
>>>
>>> Other than that, there is a thread where folks mentioned issues when the 
>>> date is off by too much...
>>> I can't tell what time zone your host is set to, but I would guess UTC 
>>> or GMT, no?
>>> In my case I have the host time zone set to my local time zone and when 
>>> I type "date" it shows the current local time.   Mine works, so it could be 
>>> a factor.
>>>
>>> Other than that, I posted just yesterday about an issue with 
>>> Wunderground-RF (rapid fire) not working unless I also explicitly forced 
>>> Wunderground-PWS on.  The setting to do that is in the Wunderground section 
>>> and you can try adding it right under the rapidfire = True a la:
>>>
>>>  archive_post = True
>>>
>>> I'm on 1.3.9-1 and you're on 1.3.8, so while it is worth a shot, it 
>>> might not be the issue in your case.
>>>
>>> Regards,
>>> Leon
>>> --
>>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>>
>>> On Apr 11, 2019, at 11:35 AM, Damjan Hajsek  wrote:
>>>
>>> Here is log with debug enabled.
>>>
>>>
>>> http://zerobin.povej.net/?18327ca6959d12c6#NusymzsEuAoTuXNt9tVsZL1+VG4jZO28VhSVYjJxwC0=
>>>
>>>
>>> Dne četrtek, 11. april 2019 15.17.35 UTC+2 je oseba gjr80 napisala:
>>>>
>>>> Ok, so you do have logs. The startup log extract you posted looks fine 
>>>> to me. What's happens next in the log? Need to see at least the next 5 
>>>> minutes of log.
>>>>
>>>> Not that it seems to be required but your attempt at running WeeWX 
>>>> directly failed because WeeWX could not find wee

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Hi
I have checked debug and it is only once and it is on 1.
my logs are in /var/log/messages (centos 7)
And I already did that but there was no weewx logs. I also have webmin and 
have filtered out all weewx logs, which you already see it.

[root@localhost ~]# ps -ef | grep weewx | grep -v grep
root 19180 1  0 18:50 ?00:00:00 python /usr/bin/weewxd 
--daemon --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf
regards
Damian

Dne četrtek, 11. april 2019 18.44.50 UTC+2 je oseba Leon Shaner napisala:
>
> Hi, Damjan,
>
> Just to rule out whether "debug" appears in the log file more than once 
> you could do this:
>
> $ grep 'debug' /etc/weewx/weewx.conf
>
> If there is a debug = 1 followed later by debug = 0 (and it is not 
> commented out with a preceeding #), then the later one will likely take 
> precedence.
>
> And to see if the daemon is dying somehow unexpectedly, please paste the 
> output from this command:
>
> $ ps -ef | grep weewx | grep -v grep
>
> One more thing.  My logs go to syslog.  Just to rule it out, you could try 
> grep'ing there:
>
> $ grep weewx /var/log/syslog
>
> And to make a copy to share, it would be something like:
>
> $ grep weewx /var/log/syslog > /var/tmp/weewx.log
>
> (And you could upload /var/tmp/weewx.log, but only if it actually has 
> recent log entries).
>
> Regards,
> Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>
> On Apr 11, 2019, at 12:37 PM, Damjan Hajsek  > wrote:
>
> Hi
>
> <2019-04-11 18_34_45-_etc_weewx_weewx.conf - ro...@194.249.178.190 
>  - Editor - WinSCP.png>
> Yes I really changed debug to 1 in conf file. I am from GMT +2
> And I tested, date shows real date and time as it should be
> Why there is no logs I don't know, that is all what I get for fev hours 
> after starting it manually.
>
> Dne četrtek, 11. april 2019 18.27.31 UTC+2 je oseba Leon Shaner napisala:
>>
>> Hi, Damjan,
>>
>> I do not see debug output.  Did you change debug = 0 to debug = 1 in the 
>> conf file?
>>
>> Other than that, there is a thread where folks mentioned issues when the 
>> date is off by too much...
>> I can't tell what time zone your host is set to, but I would guess UTC or 
>> GMT, no?
>> In my case I have the host time zone set to my local time zone and when I 
>> type "date" it shows the current local time.   Mine works, so it could be a 
>> factor.
>>
>> Other than that, I posted just yesterday about an issue with 
>> Wunderground-RF (rapid fire) not working unless I also explicitly forced 
>> Wunderground-PWS on.  The setting to do that is in the Wunderground section 
>> and you can try adding it right under the rapidfire = True a la:
>>
>>  archive_post = True
>>
>> I'm on 1.3.9-1 and you're on 1.3.8, so while it is worth a shot, it might 
>> not be the issue in your case.
>>
>> Regards,
>> Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>>
>> On Apr 11, 2019, at 11:35 AM, Damjan Hajsek  wrote:
>>
>> Here is log with debug enabled.
>>
>>
>> http://zerobin.povej.net/?18327ca6959d12c6#NusymzsEuAoTuXNt9tVsZL1+VG4jZO28VhSVYjJxwC0=
>>
>>
>> Dne četrtek, 11. april 2019 15.17.35 UTC+2 je oseba gjr80 napisala:
>>>
>>> Ok, so you do have logs. The startup log extract you posted looks fine 
>>> to me. What's happens next in the log? Need to see at least the next 5 
>>> minutes of log.
>>>
>>> Not that it seems to be required but your attempt at running WeeWX 
>>> directly failed because WeeWX could not find weewx.conf, you need to 
>>> provide the path to weewx.conf in full eg:
>>>
>>> $ sudo weewxd /etc/weewx/weewx.conf
>>>
>>> Gary
>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com.
>> 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...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout.
>
> <2019-04-11 18_34_45-_etc_weewx_weewx.conf - ro...@194.249.178.190 
>  - Editor - WinSCP.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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Here is log with debug enabled.

http://zerobin.povej.net/?18327ca6959d12c6#NusymzsEuAoTuXNt9tVsZL1+VG4jZO28VhSVYjJxwC0=


Dne četrtek, 11. april 2019 15.17.35 UTC+2 je oseba gjr80 napisala:
>
> Ok, so you do have logs. The startup log extract you posted looks fine to 
> me. What's happens next in the log? Need to see at least the next 5 minutes 
> of log.
>
> Not that it seems to be required but your attempt at running WeeWX 
> directly failed because WeeWX could not find weewx.conf, you need to 
> provide the path to weewx.conf in full eg:
>
> $ sudo weewxd /etc/weewx/weewx.conf
>
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

this log is when I restart weewx
http://zerobin.povej.net/?d31ee849647759be#97lZ+kWzpA/GMSj9XL9BOVz6N9QqRWbm513C1W4Qf+c=

when I start it directly I get this

[root@localhost /]# sudo weewxd weewx.conf
Unable to open configuration file /weewx.confTraceback (most recent call 
last):
  File "/bin/weewxd", line 64, in 
weewx.engine.main(options, args)
  File "/usr/share/weewx/weewx/engine.py", line 846, in main
config_dict = getConfiguration(config_path)
  File "/usr/share/weewx/weewx/engine.py", line 958, in getConfiguration
config_dict = configobj.ConfigObj(config_path, file_error=True)
  File "/usr/lib/python2.7/site-packages/configobj.py", line 1242, in 
__init__
self._load(infile, configspec)
  File "/usr/lib/python2.7/site-packages/configobj.py", line 1254, in _load
raise IOError('Config file not found: "%s".' % self.filename)
IOError: Config file not found: "/weewx.conf".


Dne četrtek, 11. april 2019 12.05.21 UTC+2 je oseba gjr80 napisala:
>
> Whether WeeWX runs properly or not there should be some log output 
> indicating WeeWX tried to start.  No matter. What happens when you try to 
> run WeeWX directly (http://weewx.com/docs/usersguide.htm#Running_directly). 
> Please post all of the screen output, including the command you entered.
>
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

I have posted logs and last logs are from april 1. when weewxwas running 
and latest logs are only when I restart weewx and nothing else. 

Dne četrtek, 11. april 2019 10.48.17 UTC+2 je oseba gjr80 napisala:
>
> I am afraid until you can find where your WeeWX log is being written there 
> is little we can do to help you with WeeWX. Perhaps some Googling or a 
> support forum for your flavour of Linux might be able to help.
>
> Gary
>
> On Wednesday, 10 April 2019 17:00:37 UTC+10, Damjan Hajsek wrote:
>>
>> Any help here please? I am stuck, nothing works.
>>
>> Dne nedelja, 07. april 2019 21.57.30 UTC+2 je oseba Damjan Hajsek 
>> napisala:
>>>
>>> I have set debug = 3
>>> but there is all of log I have, I posted it already.
>>> my console is connected and working.
>>>
>>>
>>> Dne nedelja, 07. april 2019 20.56.17 UTC+2 je oseba vince napisala:
>>>>
>>>> On Sunday, April 7, 2019 at 11:23:59 AM UTC-7, Damjan Hajsek wrote:
>>>>>
>>>>> I have installed with setup.py.
>>>>> Now I am thinking to use rpm and database from old setup.
>>>>> Any idea what I need to do to transfer all what I need?
>>>>>
>>>>>>
>>>>>>
>>>> I think you need to slow down and stop changing things so we can try to 
>>>> help.
>>>>
>>>> I've run weewx on centos6 and centos7 from both rpm and setup.py and it 
>>>> works fine for the Simulator driver.
>>>>
>>>> If it previously worked and you didn't change anything, and it stopped 
>>>> working a few days ago, it is likely that it is not weewx nor the os.  
>>>> It's 
>>>> more likely that you either lost connection to your database server (if it 
>>>> is on a second system) or to your station.   Set debug=1 in weewx.conf and 
>>>> restart weewx and provide more log info if it stops working again.
>>>>
>>>>
>>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Any help here please? I am stuck, nothing works.

Dne nedelja, 07. april 2019 21.57.30 UTC+2 je oseba Damjan Hajsek napisala:
>
> I have set debug = 3
> but there is all of log I have, I posted it already.
> my console is connected and working.
>
>
> Dne nedelja, 07. april 2019 20.56.17 UTC+2 je oseba vince napisala:
>>
>> On Sunday, April 7, 2019 at 11:23:59 AM UTC-7, Damjan Hajsek wrote:
>>>
>>> I have installed with setup.py.
>>> Now I am thinking to use rpm and database from old setup.
>>> Any idea what I need to do to transfer all what I need?
>>>
>>>>
>>>>
>> I think you need to slow down and stop changing things so we can try to 
>> help.
>>
>> I've run weewx on centos6 and centos7 from both rpm and setup.py and it 
>> works fine for the Simulator driver.
>>
>> If it previously worked and you didn't change anything, and it stopped 
>> working a few days ago, it is likely that it is not weewx nor the os.  It's 
>> more likely that you either lost connection to your database server (if it 
>> is on a second system) or to your station.   Set debug=1 in weewx.conf and 
>> restart weewx and provide more log info if it stops working again.
>>
>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

I have set debug = 3
but there is all of log I have, I posted it already.
my console is connected and working.


Dne nedelja, 07. april 2019 20.56.17 UTC+2 je oseba vince napisala:
>
> On Sunday, April 7, 2019 at 11:23:59 AM UTC-7, Damjan Hajsek wrote:
>>
>> I have installed with setup.py.
>> Now I am thinking to use rpm and database from old setup.
>> Any idea what I need to do to transfer all what I need?
>>
>>>
>>>
> I think you need to slow down and stop changing things so we can try to 
> help.
>
> I've run weewx on centos6 and centos7 from both rpm and setup.py and it 
> works fine for the Simulator driver.
>
> If it previously worked and you didn't change anything, and it stopped 
> working a few days ago, it is likely that it is not weewx nor the os.  It's 
> more likely that you either lost connection to your database server (if it 
> is on a second system) or to your station.   Set debug=1 in weewx.conf and 
> restart weewx and provide more log info if it stops working again.
>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

I have installed with setup.py.
Now I am thinking to use rpm and database from old setup.
Any idea what I need to do to transfer all what I need?

Dne nedelja, 07. april 2019 17.35.45 UTC+2 je oseba vince napisala:
>
> On Sunday, April 7, 2019 at 8:25:22 AM UTC-7, Damjan Hajsek wrote:
>>
>> Ok how to do that?
>> I have removed abrt-server and still the same problem.
>>
>>
>> Dne nedelja, 07. april 2019 15.17.01 UTC+2 je oseba jo...@johnkline.com 
>> napisala:
>>>
>>> The problem is in the log:
>>> abrt-server: Package 'weewx' isn't signed with proper key
>>
>>
>
> How did you install weewx ?
> Did you install a rpm or did you run setup.py ?
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

I use default centos logging didn't change anything and this worked fev 
days ago and suddenly stopped.
What about if I install this regullyary with rmp and than use mysql 
database which is already stored?
Now I have manually installed weewx.

Dne nedelja, 07. april 2019 18.29.22 UTC+2 je oseba Thomas Keffer napisala:
>
> Well, it's hard to diagnose much of anything without the log. A Google 
> search shows that some CentOS installations 
> <https://unix.stackexchange.com/a/88745> do not use a traditional logging 
> daemon. For these, you must use the command journalctl. Try that. 
>
> -tk
>
> On Sat, Apr 6, 2019 at 11:13 PM Damjan Hajsek  > wrote:
>
>> Yes it is missing.
>> I have setup debug to 3 and when I start weewx I can see that in log, but 
>> only that and nothing else.
>> I have disabled SElinux and it is the same.
>>
>> Dne nedelja, 07. april 2019 06.14.05 UTC+2 je oseba Thomas Keffer 
>> napisala:
>>>
>>> On CentOS, your log should be in /var/log/messages. Are you saying that 
>>> is missing completely? 
>>>
>>> On Sat, Apr 6, 2019 at 2:08 PM Damjan Hajsek  
>>> wrote:
>>>
>>>> I have done some more test and this is what I found out.
>>>>  detected unhandled Python exception in '/usr/bin/weewxd'
>>>> don't know is this is the reason?
>>>>
>>>> Dne sobota, 06. april 2019 19.45.36 UTC+2 je oseba Damjan Hajsek 
>>>> napisala:
>>>>>
>>>>> I noticed that weewx stop working, so I have checked log and there is 
>>>>> no log. Than I restarted weex and it restart normally but still no logs.
>>>>> Any idea what can be wrong?? It worked for a long time with no problem 
>>>>> but suddenly it stopped
>>>>> It is version 3.8.1 and is installed on centos 7.6. and also use mysql 
>>>>> database for it.
>>>>>
>>>>> -- 
>>>> 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.
>>>> 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...@googlegroups.com .
>> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Ok how to do that?
I have removed abrt-server and still the same problem.


Dne nedelja, 07. april 2019 15.17.01 UTC+2 je oseba jo...@johnkline.com 
napisala:
>
> The problem is in the log:
> abrt-server: Package 'weewx' isn't signed with proper key
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Ok here is log from april 1. there I can see reports from weewx and that 
was last reports.
Than on april 5. and 6. when I restarted weewx fev times, that is all what 
is in log.

I have put it in pastebin because there is alot of log.
http://zerobin.povej.net/?93548ecff653710f#UC94AO2wvBbQS6nOPg5Kic+iqz5qRCU4SiLkCE4Q0c4=


Dne nedelja, 07. april 2019 09.58.41 UTC+2 je oseba gjr80 napisala:
>
> Perhaps it is the language barrier but I for one am a little confused. Is 
> there any log output from WeeWX, anywhere? You said:
>
> I can see that in log
>>
>
> perhaps it is best that you post whatever it is you can see. Otherwise we 
> are just guessing.
>
> Gary
>
> On Sunday, 7 April 2019 16:13:15 UTC+10, Damjan Hajsek wrote:
>>
>> Yes it is missing.
>> I have setup debug to 3 and when I start weewx I can see that in log, but 
>> only that and nothing else.
>> I have disabled SElinux and it is the same.
>>
>> Dne nedelja, 07. april 2019 06.14.05 UTC+2 je oseba Thomas Keffer 
>> napisala:
>>>
>>> On CentOS, your log should be in /var/log/messages. Are you saying that 
>>> is missing completely? 
>>>
>>> On Sat, Apr 6, 2019 at 2:08 PM Damjan Hajsek  
>>> wrote:
>>>
>>>> I have done some more test and this is what I found out.
>>>>  detected unhandled Python exception in '/usr/bin/weewxd'
>>>> don't know is this is the reason?
>>>>
>>>> Dne sobota, 06. april 2019 19.45.36 UTC+2 je oseba Damjan Hajsek 
>>>> napisala:
>>>>>
>>>>> I noticed that weewx stop working, so I have checked log and there is 
>>>>> no log. Than I restarted weex and it restart normally but still no logs.
>>>>> Any idea what can be wrong?? It worked for a long time with no problem 
>>>>> but suddenly it stopped
>>>>> It is version 3.8.1 and is installed on centos 7.6. and also use mysql 
>>>>> database for it.
>>>>>
>>>>> -- 
>>>> 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.
>>>> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working

[Damjan Hajsek]

Yes it is missing.
I have setup debug to 3 and when I start weewx I can see that in log, but 
only that and nothing else.
I have disabled SElinux and it is the same.

Dne nedelja, 07. april 2019 06.14.05 UTC+2 je oseba Thomas Keffer napisala:
>
> On CentOS, your log should be in /var/log/messages. Are you saying that is 
> missing completely? 
>
> On Sat, Apr 6, 2019 at 2:08 PM Damjan Hajsek  > wrote:
>
>> I have done some more test and this is what I found out.
>>  detected unhandled Python exception in '/usr/bin/weewxd'
>> don't know is this is the reason?
>>
>> Dne sobota, 06. april 2019 19.45.36 UTC+2 je oseba Damjan Hajsek napisala:
>>>
>>> I noticed that weewx stop working, so I have checked log and there is no 
>>> log. Than I restarted weex and it restart normally but still no logs.
>>> Any idea what can be wrong?? It worked for a long time with no problem 
>>> but suddenly it stopped
>>> It is version 3.8.1 and is installed on centos 7.6. and also use mysql 
>>> database for it.
>>>
>>> -- 
>> 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 .
>> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx stop working

[Damjan Hajsek]

I have done some more test and this is what I found out.
 detected unhandled Python exception in '/usr/bin/weewxd'
don't know is this is the reason?

Dne sobota, 06. april 2019 19.45.36 UTC+2 je oseba Damjan Hajsek napisala:
>
> I noticed that weewx stop working, so I have checked log and there is no 
> log. Than I restarted weex and it restart normally but still no logs.
> Any idea what can be wrong?? It worked for a long time with no problem but 
> suddenly it stopped
> It is version 3.8.1 and is installed on centos 7.6. and also use mysql 
> database for it.
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] weewx stop working

[Damjan Hajsek]

I noticed that weewx stop working, so I have checked log and there is no 
log. Than I restarted weex and it restart normally but still no logs.
Any idea what can be wrong?? It worked for a long time with no problem but 
suddenly it stopped
It is version 3.8.1 and is installed on centos 7.6. and also use mysql 
database for it.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: inside humidity graph

[Damjan Hajsek]

thank you for notice.
I didn't see that, I have reparied and now work ok.


Dne četrtek, 23. avgust 2018 19.10.44 UTC+2 je oseba Andrew Milner napisala:
>
> Your weekly page has the humidity graph appearing two times.  You need to 
> DELETE the second occurrence from the template, and check monthly and 
> yearly to make sure you only have one graph appearing.
>
>
>
> On Thursday, 23 August 2018 19:59:53 UTC+3, Damjan Hajsek wrote:
>>
>> I found out where problem is, thank you for your help
>> I had to change this lines for week, month and year
>>
>> 
>> 
>>
>>
>> to this and now it works
>>
>>     
>> 
>>
>>
>> Dne četrtek, 23. avgust 2018 18.37.33 UTC+2 je oseba Damjan Hajsek 
>> napisala:
>>>
>>> I use sofaskin template and these are my 3 files
>>>
>>>
>>> Dne četrtek, 23. avgust 2018 18.12.33 UTC+2 je oseba Andrew Milner 
>>> napisala:
>>>>
>>>> …… and sorry Antonis - but you missed these:
>>>>
>>>> also in each of the sections delete the line 3 lines below the yellow 
>>>> line which references …..inhumidity.png because you are not creating that 
>>>> file any more if you put in humidity and out humidity on the same graph
>>>>
>>>>
>>>>
>>>> On Thursday, 23 August 2018 18:36:35 UTC+3, Antonis Katsonis wrote:
>>>>>
>>>>> Andrew has it exactly right.
>>>>>
>>>>>
>>>>> " It won't appear because the name is wrong if you look at the source 
>>>>> code of the weekly page. "
>>>>>
>>>>> To fix the problem follow the next steps:
>>>>>
>>>>> 1)
>>>>> Open and edit the week.html.tmpl
>>>>>
>>>>> and add the yellow line:
>>>>>
>>>>> >>>> class="fa fa-line-chart m-gruen" > Weekly Statistics and Plots   
>>>>>  >>>> alt="temperatures" />>>>> alt="heatchill" />>>>> />   
>>>>>  
>>>>> >>>> src="weekwinddir.png" alt="Hi Wind" />>>>> src="weekinside.png" alt="Inside" />>>>> src="weekinhumidity.png" alt="InHumidity" />>>>> src="weekwindvec.png" alt="Wind Vector" />>>>> src="weekuv.png" alt="UV index" />>>>> src="weekradiation.png" alt="Radiation" />>>>> src="weekuv.png" alt="UV Index" />
>>>>>
>>>>>
>>>>> 2)
>>>>> Open and edit the month.html.tmpl
>>>>>
>>>>> and add the yellow line:
>>>>>
>>>>> >>>> class="fa fa-line-chart m-gruen" > Monthly Statistics and Plots  
>>>>>   >>>> alt="temperatures" />>>>> alt="heatchill" />>>>> />  
>>>>>   
>>>>> 
>>>>>   
>>>>>   
>>>>> >>>> src="monthuv.png" alt="UV Index" />>>>> src="monthradiation.png" alt="Radiation" />>>>> src="monthuv.png" alt="UV Index" />
>>>>>
>>>>>
>>>>> 3)
>>>>> Open and edit the year.html.tmpl
>>>>>
>>>>> and add the yellow line:
>>>>>
>>>>> >>>> class="fa fa-line-chart m-gruen" > Yearly Statistics and Plots   
>>>>>  >>>> alt="temperatures" />>>>> alt="heatchill" />  
>>>>>  
>>>>>  >>>> src="yearbarometer.png" alt="barometer"/>>>>> src="yearhumidity.png" alt="OutHumidity" />>>>> src="yearwinddir.png" alt="Hi Wind" />>>>> src="yearinside.png" alt="Inside" />>>>> src="yearinhumidity.png" alt="InHumidity" />>>>> src="yearwindvec.png" alt="Wind Vector" />>>>> src="yearuv.png" alt="UV Index" />>>>> src="yearradiation.png" alt="Radiation" />>>>> src="yearuv.png" alt="UV Index" />
>>>>>
>>>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: inside humidity graph

[Damjan Hajsek]

I found out where problem is, thank you for your help
I had to change this lines for week, month and year





to this and now it works





Dne četrtek, 23. avgust 2018 18.37.33 UTC+2 je oseba Damjan Hajsek napisala:
>
> I use sofaskin template and these are my 3 files
>
>
> Dne četrtek, 23. avgust 2018 18.12.33 UTC+2 je oseba Andrew Milner 
> napisala:
>>
>> …… and sorry Antonis - but you missed these:
>>
>> also in each of the sections delete the line 3 lines below the yellow 
>> line which references …..inhumidity.png because you are not creating that 
>> file any more if you put in humidity and out humidity on the same graph
>>
>>
>>
>> On Thursday, 23 August 2018 18:36:35 UTC+3, Antonis Katsonis wrote:
>>>
>>> Andrew has it exactly right.
>>>
>>>
>>> " It won't appear because the name is wrong if you look at the source 
>>> code of the weekly page. "
>>>
>>> To fix the problem follow the next steps:
>>>
>>> 1)
>>> Open and edit the week.html.tmpl
>>>
>>> and add the yellow line:
>>>
>>> >> class="fa fa-line-chart m-gruen" > Weekly Statistics and Plots 
>>>>> alt="temperatures" />>> alt="heatchill" /> 
>>>
>>> >> src="weekhumidity.png" alt="OutHumidity" />>> src="weekwinddir.png" alt="Hi Wind" />>> src="weekinside.png" alt="Inside" />>> src="weekinhumidity.png" alt="InHumidity" />>> src="weekwindvec.png" alt="Wind Vector" />>> src="weekuv.png" alt="UV index" />>> src="weekradiation.png" alt="Radiation" />>> src="weekuv.png" alt="UV Index" />
>>>
>>>
>>> 2)
>>> Open and edit the month.html.tmpl
>>>
>>> and add the yellow line:
>>>
>>> >> class="fa fa-line-chart m-gruen" > Monthly Statistics and Plots
>>> >> alt="temperatures" />>> alt="heatchill" />>> />
>>> 
>>> 
>>> 
>>> >> src="monthwindvec.png" alt="Wind Vector" />>> src="monthuv.png" alt="UV Index" />>> src="monthradiation.png" alt="Radiation" />>> src="monthuv.png" alt="UV Index" />
>>>
>>>
>>> 3)
>>> Open and edit the year.html.tmpl
>>>
>>> and add the yellow line:
>>>
>>> >> class="fa fa-line-chart m-gruen" > Yearly Statistics and Plots 
>>>>> alt="temperatures" />>> alt="heatchill" />
>>> 
>>> >> src="yearbarometer.png" alt="barometer"/>>> src="yearhumidity.png" alt="OutHumidity" />>> src="yearwinddir.png" alt="Hi Wind" />>> src="yearinside.png" alt="Inside" />>> src="yearinhumidity.png" alt="InHumidity" />>> src="yearwindvec.png" alt="Wind Vector" />>> src="yearuv.png" alt="UV Index" />>> src="yearradiation.png" alt="Radiation" />>> src="yearuv.png" alt="UV Index" />
>>>
>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: inside humidity graph

[Damjan Hajsek]

I use sofaskin template and these are my 3 files


Dne četrtek, 23. avgust 2018 18.12.33 UTC+2 je oseba Andrew Milner napisala:
>
> …… and sorry Antonis - but you missed these:
>
> also in each of the sections delete the line 3 lines below the yellow line 
> which references …..inhumidity.png because you are not creating that file 
> any more if you put in humidity and out humidity on the same graph
>
>
>
> On Thursday, 23 August 2018 18:36:35 UTC+3, Antonis Katsonis wrote:
>>
>> Andrew has it exactly right.
>>
>>
>> " It won't appear because the name is wrong if you look at the source 
>> code of the weekly page. "
>>
>> To fix the problem follow the next steps:
>>
>> 1)
>> Open and edit the week.html.tmpl
>>
>> and add the yellow line:
>>
>> > class="fa fa-line-chart m-gruen" > Weekly Statistics and Plots  
>>   > alt="temperatures" />> alt="heatchill" />  
>>   
>> > src="weekhumidity.png" alt="OutHumidity" />> src="weekwinddir.png" alt="Hi Wind" />> src="weekinside.png" alt="Inside" />> src="weekinhumidity.png" alt="InHumidity" />> src="weekwindvec.png" alt="Wind Vector" />> src="weekuv.png" alt="UV index" />> src="weekradiation.png" alt="Radiation" />> src="weekuv.png" alt="UV Index" />
>>
>>
>> 2)
>> Open and edit the month.html.tmpl
>>
>> and add the yellow line:
>>
>> > class="fa fa-line-chart m-gruen" > Monthly Statistics and Plots 
>>> alt="temperatures" />> alt="heatchill" /> 
>>
>> 
>> 
>>  
>>> src="monthwindvec.png" alt="Wind Vector" />> src="monthuv.png" alt="UV Index" />> src="monthradiation.png" alt="Radiation" />> src="monthuv.png" alt="UV Index" />
>>
>>
>> 3)
>> Open and edit the year.html.tmpl
>>
>> and add the yellow line:
>>
>> > class="fa fa-line-chart m-gruen" > Yearly Statistics and Plots  
>>   > alt="temperatures" />> alt="heatchill" /> 
>>> src="yearwind.png" alt="wind" />> src="yearbarometer.png" alt="barometer"/>> src="yearhumidity.png" alt="OutHumidity" />> src="yearwinddir.png" alt="Hi Wind" />> src="yearinside.png" alt="Inside" />> src="yearinhumidity.png" alt="InHumidity" />> src="yearwindvec.png" alt="Wind Vector" />> src="yearuv.png" alt="UV Index" />> src="yearradiation.png" alt="Radiation" />> src="yearuv.png" alt="UV Index" />
>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.


month.html.tmpl
Description: Binary data


week.html.tmpl
Description: Binary data


year.html.tmpl
Description: Binary data

[weewx-user] Re: inside humidity graph

[Damjan Hajsek]

show_daynight = false

[[[yearbarometer]]]
barometer

[[[yeartempdew]]]
outTemp
dewpoint

# Daily high/lows:
[[[yearhilow]]]
hi
data_type = outTemp
aggregate_type = max
label = High
low
data_type = outTemp
aggregate_type = min
label = Low Temperature

[[[yearwind]]]
windSpeed
windGust
aggregate_type = max

[[[yeartempchill]]]
windchill
heatindex

[[[yearrain]]]
yscale = None, None, 0.02
plot_type = bar
rain
aggregate_type = sum
# aggregate_interval = 2629800 # Magic number: the length 
of a nominal month
aggregate_interval = 604800# == 1 week
label = Rain (weekly total)

[[[yearpond]]]
yscale = None, None, 0.5
extraTemp1

[[[yearrx]]]
rxCheckPercent

[[[yearinside]]]
inTemp

[[[yearhumidity]]]
inHumidity
   outHumidity


[[[yearwinddir]]]
yscale = 0.0, 360.0, 45.0
windDir

[[[yearwindvec]]]
windvec
plot_type = vector

[[[yearradiation]]]
radiation

[[[yearuv]]]
yscale = 0, 16, 1
UV

###


Dne četrtek, 23. avgust 2018 15.09.51 UTC+2 je oseba Andrew Milner napisala:
>
> there is no catch
>
> did you add the inHumidity to all of the graphs - or only daily??
>
> maybe you should attach the skin you are using to your next post!!  
> Impossible to guess otherwise
>
>
>
> On Thursday, 23 August 2018 15:29:46 UTC+3, Damjan Hajsek wrote:
>>
>> I have tried this but there is no week, month and year graph, only daily 
>> graph works.
>> where is the catch?
>>
>> Dne ponedeljek, 27. januar 2014 14.25.10 UTC+1 je oseba pgeenhuizen 
>> napisala:
>>>
>>> I've been trying to figure out how to create a graph of the inside 
>>> humidity similar to the inside temperature graph,  but for the life of 
>>> me I can't seem to figure out how any of the graphs are created let 
>>> alone a new one. 
>>>
>>> So what's the secret? 
>>>
>>> Pete 
>>>
>>> -- 
>>> Unencumbered by the thought process. 
>>>   -- Click and Clack the Tappet brothers 
>>>
>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: inside humidity graph

[Damjan Hajsek]

I have tried this but there is no week, month and year graph, only daily 
graph works.
where is the catch?

Dne ponedeljek, 27. januar 2014 14.25.10 UTC+1 je oseba pgeenhuizen 
napisala:
>
> I've been trying to figure out how to create a graph of the inside 
> humidity similar to the inside temperature graph,  but for the life of 
> me I can't seem to figure out how any of the graphs are created let 
> alone a new one. 
>
> So what's the secret? 
>
> Pete 
>
> -- 
> Unencumbered by the thought process. 
>   -- Click and Clack the Tappet brothers 
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: UV index

[Damjan Hajsek]

Thank you, I see.
So the only way and most simple was is to use interceptor driver. That 
works for almost all except UV.
So I will make some data logging like it was suggested and than we can do 
something to improve interceptor driver.


Dne sreda, 08. november 2017 09.56.35 UTC+1 je oseba Damjan Hajsek napisala:
>
> What is relation with UV index and radiation?
> Because sometimes radiation is already 0 but UV index is still about 80 or 
> 50.
> Doesn't that be also 0 when radiation is 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: UV index

[Damjan Hajsek]

tried again but the same error.
localhost weewx[21212]: HP1000: Timed out too many times


Dne sreda, 08. november 2017 09.56.35 UTC+1 je oseba Damjan Hajsek napisala:
>
> What is relation with UV index and radiation?
> Because sometimes radiation is already 0 but UV index is still about 80 or 
> 50.
> Doesn't that be also 0 when radiation is 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: UV index

[Damjan Hajsek]

Yes I see now sorry forget to reconfigure.
I also didn't have HP1000 driver so I downloaded it, install it and 
reconfigure it.
but now It doesn't work I get this error.
localhost weewx[21212]: HP1000: Timed out too many times


Dne četrtek, 19. april 2018 04.39.36 UTC+2 je oseba vk3...@gmail.com 
napisala:
>
> That indicates that you have not followed the instructions for installing 
> the driver and configuring the 'weewx.conf' file.
> Susan
>
> On Thursday, April 19, 2018 at 4:38:24 AM UTC+10, Damjan Hajsek wrote:
>>
>> I also tried HP1000 driver as it was suggested by some use, but get this 
>> error.
>>
>> Apr 18 20:31:49 localhost weewx[593]: engine: Caught unrecoverable 
>> exception in engine:
>> Apr 18 20:31:49 localhost weewx[593]:  No module named HP1000
>> Apr 18 20:31:49 localhost weewx[593]:  Traceback (most recent 
>> call last):
>> Apr 18 20:31:49 localhost weewx[593]:File 
>> "/usr/share/weewx/weewx/engine.py", line 865, in main
>> Apr 18 20:31:49 localhost weewx[593]:  engine = 
>> engine_class(config_dict)
>> Apr 18 20:31:49 localhost weewx[593]:File 
>> "/usr/share/weewx/weewx/engine.py", line 71, in __init__
>> Apr 18 20:31:49 localhost weewx[593]:  
>> self.setupStation(config_dict)
>> Apr 18 20:31:49 localhost weewx[593]:File 
>> "/usr/share/weewx/weewx/engine.py", line 95, in setupStation
>> Apr 18 20:31:49 localhost weewx[593]:  __import__(driver)
>> Apr 18 20:31:49 localhost weewx[593]:  ImportError: No module 
>> named HP1000
>> Apr 18 20:31:49 localhost weewx[593]:  Exiting.
>>
>>
>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: UV index

[Damjan Hajsek]

I also tried HP1000 driver as it was suggested by some use, but get this 
error.

Apr 18 20:31:49 localhost weewx[593]: engine: Caught unrecoverable 
exception in engine:
Apr 18 20:31:49 localhost weewx[593]:  No module named HP1000
Apr 18 20:31:49 localhost weewx[593]:  Traceback (most recent call 
last):
Apr 18 20:31:49 localhost weewx[593]:File 
"/usr/share/weewx/weewx/engine.py", line 865, in main
Apr 18 20:31:49 localhost weewx[593]:  engine = 
engine_class(config_dict)
Apr 18 20:31:49 localhost weewx[593]:File 
"/usr/share/weewx/weewx/engine.py", line 71, in __init__
Apr 18 20:31:49 localhost weewx[593]:  
self.setupStation(config_dict)
Apr 18 20:31:49 localhost weewx[593]:File 
"/usr/share/weewx/weewx/engine.py", line 95, in setupStation
Apr 18 20:31:49 localhost weewx[593]:  __import__(driver)
Apr 18 20:31:49 localhost weewx[593]:  ImportError: No module named 
HP1000
Apr 18 20:31:49 localhost weewx[593]:  Exiting.

Dne sreda, 08. november 2017 09.56.35 UTC+1 je oseba Damjan Hajsek napisala:
>
> What is relation with UV index and radiation?
> Because sometimes radiation is already 0 but UV index is still about 80 or 
> 50.
> Doesn't that be also 0 when radiation is 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: UV index

[Damjan Hajsek]

I will do that and post results here

Dne sreda, 18. april 2018 15.22.25 UTC+2 je oseba Greg Troxel napisala:
>
> Damjan Hajsek <hajsek...@gmail.com > writes: 
>
> > So we can't do nothing to make UV index show right value, because with 
> > calibrating I can not get real data? 
>
> This can probably be solved, but "calibration" is very likely not the 
> approach. 
>
> Let me try to summarize what we know. 
>
>   Your station seems to show reasonable UV values on the console. 
>
>   Your station reports some encoded values that a weewx driver reads. 
>
>   Currently, the bits for UV are extracted in some straightforward way 
>   and assumed to be the UV index.  This is leading to values that are 
>   not even close to correct. 
>
>   "Calibration", in weewx and generally, is a mechanism that makes small 
>   changes to values to make them closer to the correct values. 
>   Calibration is by definition a very minor change, like subtracting 0.7 
>   hPa of pressure, or adding 0.5 C of temperature.  Or perhaps 2 C, but 
>   not 20 C.  Calibration as a concept depends on having a close-to-right 
>   value with a simple relationship, so that "V = R + c" holds fairly 
>   closely for readings R, and calibration value c, and true value V. 
>
>   So far, we have no reason to believe that attempting something like 
>   calibration above with the values being read by weewx for your station 
>   will give reasonably correct answers. 
>
> And then making assumptions: 
>
>   Probably, the way the weather station sends UV index to the computer 
>   is not just an integer in a field.  We don't understand how that is 
>   done yet. 
>
> So the path forward is, more or less: 
>
>   1) Ensure (assume, and retry if not, because absent the manufacturer 
>   documenting it, and documenting it correctly, we have to assume) that 
>   the UV field really is the UV field. 
>
>   2) Ensure that the path from bits in the UV field to the number that is 
>   recorded is straightforward and reversible. 
>
>   3) Keep records of pairs of displayed UV value and 
>   reported/recorded-in-weewx UV values.  A simple chart with two columns 
>   would be fine (but I might add date/time in case it is useful). 
>
>   4) Put this chart in a spreadsheet or csv format 
>
>   5) Make a scatter plot of console vs weewx values, where each point is 
> an 
>   observation pair, with console on x axis and weewx-read value on y 
>   axis. 
>
>   6) Figure out if there is a clear relationship and what it is.  Try to 
>   come up with a formula, especially one that we can explain after we 
>   create it how it works. 
>
>   Change the driver to use the formula. 
>
> I am guessing these steps seem too complicated, but I expect others can 
> help. 
>
> So I would suggest that you do steps 3 and 4, for at least several days 
> and preferably a week, at night, and at various points during the day, 
> both sunny and cloudy days, and post a link to the spreadsheet, or 
> preferably mail csv format to the list. 
>
> Without steps 3 and 4, then I don't see a way to make progress. 
>
> Greg 
>
> 
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx index page out of borders on phone

[Damjan Hajsek]

and here is my index.html.tpl

Dne sreda, 18. april 2018 08.41.57 UTC+2 je oseba Damjan Hajsek napisala:
>
> Can someone helps me to get my index page in borders? on my web page when 
> I use PC it is OK, but on phone it streach and shows bottom data out of web 
> page, is it possible to repair that?
> here is web site. http://vreme.povej.net
> and below is a screenshot on my phone.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.


index.html.tmpl
Description: Binary data

[weewx-user] Re: UV index

[Damjan Hajsek]

So we can't do nothing to make UV index show right value, because with 
calibrating I can not get real data?

Dne nedelja, 15. april 2018 11.15.20 UTC+2 je oseba Damjan Hajsek napisala:
>
> Today I get this from company which sells this weather station I think 
> this doesn't esplain much.
>
> · Outdoor temperature range  ---  -40.0°C to + 65.0°C (-40°F to 
> +149°F)
>
> · Indoor temperature range  ---  0°C to + 50.0°C (32°F to +122°F)
>
> · Humidity range  ---  10% to 99% (1% resolution)
>
> · Rain volume display  ---  0 to mm, resolution 0.3mm (if 
> rain volume < 1000mm) or 1mm (if rain volume > 1000mm)
>
> · Wind speed  ---  0 to 160 km/h
>
> · Barometric pressure  ---  300hPa to 1,100hPA (inHg, mmHG or 
> hPa) with 0.1hPa resolution
>
> · Light  ---  0 to 400k Lux
>
> · UV Index  ---  1 to 12
>
> · Transmission range  ---  up to 100m (330 feet) line of site
>
> · Power consumption  ---  receiver  3 x AA batteries, transmitter 
> 2 x AA batteries
>
> · Transmission frequency  ---  433MHz
>
> · Data storage capacity  ---  2 weeks at 5 min intervals up to 3 
> months at 30min intervals
>
> · Alarm duration  ---  120 sec
>
>
> Dne nedelja, 15. april 2018 09.19.45 UTC+2 je oseba Damjan Hajsek napisala:
>>
>> I also checked Wunderground, there shows UV like it is on console but on 
>> Weewx I get instead of UV 1 I get UV 518
>>
>> Dne sreda, 08. november 2017 09.56.35 UTC+1 je oseba Damjan Hajsek 
>> napisala:
>>>
>>> What is relation with UV index and radiation?
>>> Because sometimes radiation is already 0 but UV index is still about 80 
>>> or 50.
>>> Doesn't that be also 0 when radiation is 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: UV index

[Damjan Hajsek]

Today I get this from company which sells this weather station I think this 
doesn't esplain much.

· Outdoor temperature range  ---  -40.0°C to + 65.0°C (-40°F to 
+149°F)

· Indoor temperature range  ---  0°C to + 50.0°C (32°F to +122°F)

· Humidity range  ---  10% to 99% (1% resolution)

· Rain volume display  ---  0 to mm, resolution 0.3mm (if rain 
volume < 1000mm) or 1mm (if rain volume > 1000mm)

· Wind speed  ---  0 to 160 km/h

· Barometric pressure  ---  300hPa to 1,100hPA (inHg, mmHG or hPa) 
with 0.1hPa resolution

· Light  ---  0 to 400k Lux

· UV Index  ---  1 to 12

· Transmission range  ---  up to 100m (330 feet) line of site

· Power consumption  ---  receiver  3 x AA batteries, transmitter 2 
x AA batteries

· Transmission frequency  ---  433MHz

· Data storage capacity  ---  2 weeks at 5 min intervals up to 3 
months at 30min intervals

· Alarm duration  ---  120 sec


Dne nedelja, 15. april 2018 09.19.45 UTC+2 je oseba Damjan Hajsek napisala:
>
> I also checked Wunderground, there shows UV like it is on console but on 
> Weewx I get instead of UV 1 I get UV 518
>
> Dne sreda, 08. november 2017 09.56.35 UTC+1 je oseba Damjan Hajsek 
> napisala:
>>
>> What is relation with UV index and radiation?
>> Because sometimes radiation is already 0 but UV index is still about 80 
>> or 50.
>> Doesn't that be also 0 when radiation is 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: UV index

[Damjan Hajsek]

I also checked Wunderground, there shows UV like it is on console but on 
Weewx I get instead of UV 1 I get UV 518

Dne sreda, 08. november 2017 09.56.35 UTC+1 je oseba Damjan Hajsek napisala:
>
> What is relation with UV index and radiation?
> Because sometimes radiation is already 0 but UV index is still about 80 or 
> 50.
> Doesn't that be also 0 when radiation is 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: UV index

[Damjan Hajsek]

I also checked Wunderground, there shows UV like it is on console but on 
Weewx I get instead of UV 1 I get UV 518

Dne sreda, 08. november 2017 09.56.35 UTC+1 je oseba Damjan Hajsek napisala:
>
> What is relation with UV index and radiation?
> Because sometimes radiation is already 0 but UV index is still about 80 or 
> 50.
> Doesn't that be also 0 when radiation is 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: UV index

[Damjan Hajsek]

I also checked Wunderground, there shows UV like it is on console but on 
Weewx I get instead of UV 1 I get UV 518

Dne sreda, 08. november 2017 09.56.35 UTC+1 je oseba Damjan Hajsek napisala:
>
> What is relation with UV index and radiation?
> Because sometimes radiation is already 0 but UV index is still about 80 or 
> 50.
> Doesn't that be also 0 when radiation is 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: UV index

[Damjan Hajsek]

I also checked Wunderground, there shows UV like it is on console but on 
Weewx I get instead of UV 1 I get UV 518

Dne sreda, 08. november 2017 09.56.35 UTC+1 je oseba Damjan Hajsek napisala:
>
> What is relation with UV index and radiation?
> Because sometimes radiation is already 0 but UV index is still about 80 or 
> 50.
> Doesn't that be also 0 when radiation is 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: UV index

[Damjan Hajsek]

my altitude is 296m and here is firmware 
https://ambientweather.wikispaces.com/ws1002-wifi

I will ask company to give me exact data about sensors, when I get it I 
will post it here.



Dne sobota, 14. april 2018 20.50.25 UTC+2 je oseba mwall napisala:
>
>
>
> On Saturday, April 14, 2018 at 2:11:29 PM UTC-4, Damjan Hajsek wrote:
>>
>>
>> <https://lh3.googleusercontent.com/-AJtbnnw7UJc/WtJEQGnGcfI/AaE/zJAL0eYB_AcgP2_1ujrILfg5cL1heqdlACLcBGAs/s1600/2018-04-14%2B20_09_09-For%2Bbasic%2Bsettings%2Bthe%2Bfollowing%2Bmenu%2Bis%2Bstarted%2Bby%2Btouching%2Bthe%2Btouch-screen%2Bin.png>
>> Ok I checked in manuals. Is this enough, if not I will contact company 
>> which makes this seather station to send me exctly which sensors are build 
>> in.
>>>
>>>
>>>
> that looks like luminosity ("light sensor") and uv ("UV sensor")
>
> so your radiation adjustment is probably ok (are you at a fairly high 
> altitude?)
>
> i have no idea what the uv would read.
>
> i think you are correct to do this in the StdCalibrate.  if we had 
> definitive specifications for the hardware, and we had definitive 
> specifications for the wu protocol, and we had definitive specifications 
> for how the station emits data for wu, and we had definitive specifications 
> for how those values vary from one firmware version to another, then i 
> might be able to encode the conversions in the interceptor driver.
>
> in lieu of that, use StdCalibrate.
>
> m
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: UV index

[Damjan Hajsek]

<https://lh3.googleusercontent.com/-AJtbnnw7UJc/WtJEQGnGcfI/AaE/zJAL0eYB_AcgP2_1ujrILfg5cL1heqdlACLcBGAs/s1600/2018-04-14%2B20_09_09-For%2Bbasic%2Bsettings%2Bthe%2Bfollowing%2Bmenu%2Bis%2Bstarted%2Bby%2Btouching%2Bthe%2Btouch-screen%2Bin.png>
Ok I checked in manuals. Is this enough, if not I will contact company 
which makes this seather station to send me exctly which sensors are build 
in.



Dne sobota, 14. april 2018 18.02.32 UTC+2 je oseba mwall napisala:
>
> On Saturday, April 14, 2018 at 4:53:18 AM UTC-4, Damjan Hajsek wrote:
>>
>> No UV and radiation are not the same value.
>>
>
> UV, radiation, and illuminance are three different things.  some stations 
> measure illuminance, then convert to radiation.  some measure radiation. 
>  measuring uv requires a different sensor.
>
> there are conversion factors to go between illuminance and radiation, but 
> those are gross approximations.
>
> uv index is arbitrary.  davis hardware uses a 0-16 integer scale. 
>  rainwise uses something else.  ukmet uses something else.
>
>  
>
>> radiation = radiation * 0.731
>>
>
> your hardware might be reporting luminance, not radiation.
>
> check the hardware specs to see exactly what kinds of sensors it has. 
>  does it have just illuminance, then it is fabricating a UV index and a 
> radiation value?  or does it actually measure UV?
>
> once you know exactly what the hardware is capable of doing, then we can 
> see how that maps to the packets that the interceptor driver is receiving 
> from it.
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: UV index

[Damjan Hajsek]

No UV and radiation are not the same value.
UV values are in bold because I made it bold to see it better.
Yes I am soure my station report the same value as it is on console I 
checked that many times.
Here is my calibration section.

[[Corrections]]

# For each type, an arbitrary calibration expression can be given. 
# It should be in the units defined in the StdConvert section.
# Example:
# foo = foo + 0.2
radiation = radiation * 0.731
rainRate = rainRate * 0.1
#barometer = barometer * 10.0025
pressure = pressure * 1.0035
  UV = UV * 0.003
#windSpeed = windSpeed * 4.5

Dne sobota, 14. april 2018 09.44.14 UTC+2 je oseba Andrew Milner napisala:
>
> If you do not have your calibration statement are you saying that UV and 
> radiation are the same value??
>
> What is your calibration??  You just said it is very high.
>
> Why are some UV values in bold print in the loop and rec packets??
>
> Are you sure that your weather station actually outputs the same index 
> value which you see on the weather station console??  So far all the 
> evidence seems to imply that it does not provide the UV index in the same 
> form that you see it on the console.
>
>
>
> On Saturday, 14 April 2018 10:10:39 UTC+3, Damjan Hajsek wrote:
>
>> Yes I hope we can solve that, because I use now verry high factor for 
>> calibration to see aproximatelly the same result as on console.
>>
>> Dne sobota, 14. april 2018 02.35.05 UTC+2 je oseba gjr80 napisala:
>>>
>>> Unlikely to be anything to do with units, UV and radiation use the same 
>>> units irrespective of the unit system in use. From the loop/archive data 
>>> last shown I would hazard a guess that the driver is (now) doing its thing 
>>> correctly and presenting weeWX with credible UV and radiation values. If 
>>> these values correspond with what is displayed on the console then I don't 
>>> think there is any issue with the driver. In that case perhaps we need some 
>>> elaboration on 'weewx doesn't read it right'.
>>>
>>> Gary
>>>
>>> On Saturday, 14 April 2018 10:13:24 UTC+10, Andrew Milner wrote:
>>>>
>>>> Damjan
>>>>
>>>> I do not think you are telling us everything which you are 
>>>> doing/changing!!  When you first posted to this thread the loop records 
>>>> were in US units, and UV values appeared to be very high.  Your latest 
>>>> posting has loop records in metric, and UV values appear to be more like 
>>>> UV 
>>>> index values.
>>>>
>>>> So, do you still have a problem?  If you have been changing your 
>>>> database units then your database could well contsin a mixture of imperial 
>>>> and metric values - with very unpredictable results.
>>>>
>>>>
>>>>
>>>> On Saturday, 14 April 2018 02:49:33 UTC+3, Greg Troxel wrote:
>>>>
>>>>> Andrew Milner <andrew.s...@gmail.com> writes: 
>>>>>
>>>>> > matthew has already said tha weewx does not calculate uv index - it 
>>>>> merely 
>>>>> > uses the data provided by the station 
>>>>>
>>>>> But if there is some hardware that provides bits in a UV field, then a 
>>>>> driver for that hardware should be translating the bits into an index 
>>>>> value according to the encoding used.  I don't think we should be 
>>>>> using 
>>>>> calibration notions as a substitute for a well-understood 
>>>>> representation.  But maybe I'm missing something here. 
>>>>>
>>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: UV index

[Damjan Hajsek]

Yes I hope we can solve that, because I use now verry high factor for 
calibration to see aproximatelly the same result as on console.

Dne sobota, 14. april 2018 02.35.05 UTC+2 je oseba gjr80 napisala:
>
> Unlikely to be anything to do with units, UV and radiation use the same 
> units irrespective of the unit system in use. From the loop/archive data 
> last shown I would hazard a guess that the driver is (now) doing its thing 
> correctly and presenting weeWX with credible UV and radiation values. If 
> these values correspond with what is displayed on the console then I don't 
> think there is any issue with the driver. In that case perhaps we need some 
> elaboration on 'weewx doesn't read it right'.
>
> Gary
>
> On Saturday, 14 April 2018 10:13:24 UTC+10, Andrew Milner wrote:
>>
>> Damjan
>>
>> I do not think you are telling us everything which you are 
>> doing/changing!!  When you first posted to this thread the loop records 
>> were in US units, and UV values appeared to be very high.  Your latest 
>> posting has loop records in metric, and UV values appear to be more like UV 
>> index values.
>>
>> So, do you still have a problem?  If you have been changing your database 
>> units then your database could well contsin a mixture of imperial and 
>> metric values - with very unpredictable results.
>>
>>
>>
>> On Saturday, 14 April 2018 02:49:33 UTC+3, Greg Troxel wrote:
>>
>>> Andrew Milner  writes: 
>>>
>>> > matthew has already said tha weewx does not calculate uv index - it 
>>> merely 
>>> > uses the data provided by the station 
>>>
>>> But if there is some hardware that provides bits in a UV field, then a 
>>> driver for that hardware should be translating the bits into an index 
>>> value according to the encoding used.  I don't think we should be using 
>>> calibration notions as a substitute for a well-understood 
>>> representation.  But maybe I'm missing something here. 
>>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: UV index

[Damjan Hajsek]

Hi
Yes I changed units because I am from europe and units should be all in 
metric system and I did that because I noticed that wind on console shows 
10km/h and in weewx that was abot 5 times less, like 2 km/h. So I still 
didn resolve that too.
And problem with UV still persist, I solved it for now with calibration. I 
have deleted database after that and started all over again, because weewx 
even didn't work.
So now it is like fresh installation.

Dne sobota, 14. april 2018 02.13.24 UTC+2 je oseba Andrew Milner napisala:
>
> Damjan
>
> I do not think you are telling us everything which you are 
> doing/changing!!  When you first posted to this thread the loop records 
> were in US units, and UV values appeared to be very high.  Your latest 
> posting has loop records in metric, and UV values appear to be more like UV 
> index values.
>
> So, do you still have a problem?  If you have been changing your database 
> units then your database could well contsin a mixture of imperial and 
> metric values - with very unpredictable results.
>
>
>
> On Saturday, 14 April 2018 02:49:33 UTC+3, Greg Troxel wrote:
>
>> Andrew Milner  writes: 
>>
>> > matthew has already said tha weewx does not calculate uv index - it 
>> merely 
>> > uses the data provided by the station 
>>
>> But if there is some hardware that provides bits in a UV field, then a 
>> driver for that hardware should be translating the bits into an index 
>> value according to the encoding used.  I don't think we should be using 
>> calibration notions as a substitute for a well-understood 
>> representation.  But maybe I'm missing something here. 
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx crash engine: Caught unrecoverable exception in engine:

[Damjan Hajsek]

thank you, yes I cheked And I should also have hPa

Dne petek, 13. april 2018 14.34.13 UTC+2 je oseba gjr80 napisala:
>
> Ok, I understand. You can use what ever you want. You can use inHg or mbar 
> or hPa or mmHq. The key point for minmax entries is that the numbers have 
> to make sense with the units you use. I am comfortable with hPa here in 
> Australia so I might use use something like:
>
> barometer = 900, 1000, hPa 
>
> even though my database may use inHg for pressure. The numbers you have 
> seem to be in the range for inHg, definitely not mbar or hPa.
>
> One thing to remember; the units are optional for a minmax entry, but if 
> you omit them then the numbers are assumed to be in the units used in your 
> database. That can get a bit tricky for some, that is why I prefer to 
> specify minmax entries in units that I am familiar with.
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: UV index

[Damjan Hajsek]

, maxSolarRad: 
None, outHumidity: 49.0, outTemp: 18.6, pressure: 979.8174, radiation: 
616.57243985, rain: 0.0, rainRate: 0.0, usUnits: 17, *UV: 1.695*, 
windchill: 18.6, windDir: 228.0, windGust: 0.62630511, windSpeed: 
0.51243145



Dne sreda, 08. november 2017 09.56.35 UTC+1 je oseba Damjan Hajsek napisala:
>
> What is relation with UV index and radiation?
> Because sometimes radiation is already 0 but UV index is still about 80 or 
> 50.
> Doesn't that be also 0 when radiation is 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx crash engine: Caught unrecoverable exception in engine:

[Damjan Hajsek]

Ok than what to use instad of inHg for europe? I thought mbar is not right
for these two values.

barometer = 26, 32.5, inHg

pressure = 24, 34.5, inHg


Dne petek, 13. april 2018 14.16.19 UTC+2 je oseba gjr80 napisala:
>
> I am not sure what you mean by 'is a mbar proper value for inHg?'. inHg 
> and mbar are quite different, mbar and hPa are the same. The weeWX MetricWX 
> and Metric unit systems both use mbar, the US unit system uses inHg.
>
> I suspect I have not answered your question though.
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx crash engine: Caught unrecoverable exception in engine:

[Damjan Hajsek]

thank you quick response I found error I have accidentally put a ' 
target_unit = 'METRICWX
I checked conf 10 times and didn't see it until I use compareit, original 
and my conf file side by side.
One more question is a mbar proper value for inHg?

Dne petek, 13. april 2018 13.53.12 UTC+2 je oseba gjr80 napisala:
>
> Hi,
>
> That error relates to the StdConvert service not StdQC. Pllease post the 
> contents of [StdConvert] or better still a sanitised (passwords and 
> sensitive info removed) copy of weewx.conf.
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] weewx crash engine: Caught unrecoverable exception in engine:

[Damjan Hajsek]

Can someone help me please with this error.
I have changed today this values and after that weewx crashes all the time.
I set this to european values. now I get this error.

#   This section is for quality control checks. If units are not specified,
#   values must be in the units defined in the StdConvert section.

[StdQC]

[[MinMax]]
barometer = 800, 1170, mbar
outTemp = -30, 38, degree_C
inTemp = 5, 35, degree_C
outHumidity = 0, 100
inHumidity = 0, 100
windSpeed = 0, 250, km_per_hour
pressure = 800, 1170, mbar


Apr 13 13:38:10 localhost weewx[25853]: interceptor: MainThread: driver 
version is 0.36
Apr 13 13:38:10 localhost weewx[25853]: interceptor: MainThread: device 
type: observer
Apr 13 13:38:10 localhost weewx[25853]: interceptor: MainThread: sensor 
map: None
Apr 13 13:38:10 localhost weewx[25853]: interceptor: MainThread: mode is 
listen
Apr 13 13:38:10 localhost weewx[25853]: interceptor: MainThread: listen on 
:
Apr 13 13:38:10 localhost weewx[25853]: interceptor: MainThread: shutting 
down server thread
Apr 13 13:38:10 localhost weewx[25853]: engine: Caught unrecoverable 
exception in engine:
Apr 13 13:38:10 localhost weewx[25853]:  'list' object has no 
attribute 'upper'
Apr 13 13:38:10 localhost weewx[25853]:  Traceback (most recent 
call last):
Apr 13 13:38:10 localhost weewx[25853]:File 
"/usr/share/weewx/weewx/engine.py", line 865, in main
Apr 13 13:38:10 localhost weewx[25853]:  engine = 
engine_class(config_dict)
Apr 13 13:38:10 localhost weewx[25853]:File 
"/usr/share/weewx/weewx/engine.py", line 77, in __init__
Apr 13 13:38:10 localhost weewx[25853]:  
self.loadServices(config_dict)
Apr 13 13:38:10 localhost weewx[25853]:File 
"/usr/share/weewx/weewx/engine.py", line 141, in loadServices
Apr 13 13:38:10 localhost weewx[25853]:  
self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
Apr 13 13:38:10 localhost weewx[25853]:File 
"/usr/share/weewx/weewx/engine.py", line 305, in __init__
Apr 13 13:38:10 localhost weewx[25853]:  self.target_unit = 
weewx.units.unit_constants[target_unit_nickname.upper()]
Apr 13 13:38:10 localhost weewx[25853]:  AttributeError: 'list' 
object has no attribute 'upper'
Apr 13 13:38:10 localhost weewx[25853]:  Exiting.
Apr 13 13:38:10 localhost python: detected unhandled Python exception in 
'/usr/bin/weewxd'
Apr 13 13:38:10 localhost abrt-server: Not saving repeating crash in 
'/usr/bin/weewxd'

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: UV index

[Damjan Hajsek]

I have this weather station
https://www.ambientweather.com/amws1000wifi.html
I will try to make more loop packages and see what station send.

Dne sreda, 11. april 2018 18.42.13 UTC+2 je oseba Greg Troxel napisala:
>
>
> I did misunderstand, sort of.  I think you are in a situation where 
> either 
>
>   your station is behaving strangely 
>
>   the interceptor driver fo fine offset station does not have support 
>   for decoding UV index, and is just reporting byte values until that's 
>   figured out 
>
>   something else :-) 
>
> So I would recommend recording displayed values vs LOOP packet values, 
> and creating a scatter plot.  I also recommend reading the driver source 
> code to see what it thinks it is doing now.  With any luck the 
> relationship will be clear and reliable, and you can contribute 
> new/improved support to the driver. 
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: UV index

[Damjan Hajsek]

Maybe we didn't understand right.
Station show real value of UV index on my terminal at home.
But not on my web page by weewx. So it is settings in weewx

Dne sreda, 11. april 2018 15.08.09 UTC+2 je oseba Greg Troxel napisala:
>
> Damjan Hajsek <hajsek...@gmail.com > writes: 
>
> > Anyone know what to use in 
> > [StdCalibrate] 
> > 
> > [[Corrections]] 
> > 
> > to correct UV index? Because now at night it is UV = 15 
>
> (I don't have any actual experience here, either with weewx calibration 
> or with UV sensors that ever show 15.) 
>
> Typically, "calibration" involves minor adjustments to a sensor that is 
> basically working ok, like adding 0.7 hPA to pressure.  There is an 
> underlying assumption that the sensor has the right slope but just a 
> small offset. 
>
> A UV sensor that reports a UV index of 15 at night sounds so seriously 
> off that it seems more likely that something is catastrophically wrong 
> which cannot reasonably be resolved with calibration.  I have not 
> checked calibration on my UV sensor, but it reliably shows 0 at night 
> and patterns that appear to corrrelate well with sunny vs not and sun 
> angle.  I would not be shocked if it reads 3.8 when it should read 4.0; 
> I would have to be far more thorough to figure that out, vs eyeballing 
> graphs and not being suspicious. 
>
> I would recommend looking at all other ways of observing the sensor 
> value (console?), and see if there are any setup errors. 
>
> Finally, I would log the data without calibration for a while, and graph 
> that in a scatter plot against UV data from some nearby station that you 
> believe is working ok.  If that turns out to be a line with slope 1 and 
> offset 15, then subtracting 15 is good strategy.  But until you know 
> that such a relationship holds, the assumption that there is a single 
> linear offset seems unwarranted. 
>
> Greg 
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Confused about how to install Weewx-forecast

[Damjan Hajsek]

I have manage to solve it by myself problem was icons, so I changed apache 
settings and disabled autoindex.conf

Dne sreda, 11. april 2018 11.11.17 UTC+2 je oseba Damjan Hajsek napisala:
>
> Hi
> I have the same problem but I am lost at the end, still doesn't get 
> anything on my index page.
> I have attached my index.html.tmpl file. Can someone help me?
>
>
> Dne torek, 06. februar 2018 10.01.38 UTC+1 je oseba Cycle London napisala:
>>
>> There is one thing that strikes me.  On the temperature scale, the degree 
>> sign and 'C' appears three times.  I'm assuming that this represents a 
>> high, low and actual prediction?   It's not - I think - anything to do with 
>> my installation, as if I check out the 'MIT Sailing Pavillon' live example, 
>> they have it too.. 
>>
>> http://sailing.mit.edu/weather/forecast.html
>>
>> is there a way to include high and low?  
>>
>> And is it possible to limit the number of days forward that the forecast 
>> reaches?  
>>
>> Is there actually a page where the options for the strip are detailed?  
>> So far, I've only seen the HOWTO on the wiki. 
>>
>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Confused about how to install Weewx-forecast

[Damjan Hajsek]

Hi
I have the same problem but I am lost at the end, still doesn't get 
anything on my index page.
I have attached my index.html.tmpl file. Can someone help me?


Dne torek, 06. februar 2018 10.01.38 UTC+1 je oseba Cycle London napisala:
>
> There is one thing that strikes me.  On the temperature scale, the degree 
> sign and 'C' appears three times.  I'm assuming that this represents a 
> high, low and actual prediction?   It's not - I think - anything to do with 
> my installation, as if I check out the 'MIT Sailing Pavillon' live example, 
> they have it too.. 
>
> http://sailing.mit.edu/weather/forecast.html
>
> is there a way to include high and low?  
>
> And is it possible to limit the number of days forward that the forecast 
> reaches?  
>
> Is there actually a page where the options for the strip are detailed?  So 
> far, I've only seen the HOWTO on the wiki. 
>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.


index.html.tmpl
Description: Binary data

[weewx-user] Re: UV index

[Damjan Hajsek]

Thank you I already tried that but didn't use capital letters for UV i use 
uv and weewx complain when I restarted it, now I will chck console and 
create formula to get right value.

Dne sreda, 11. april 2018 09.34.18 UTC+2 je oseba Andrew Milner napisala:
>
> I doubt if it can be done by a simple change as it appears to depend on 
> ozone thickness, cloud thickness, time of year and station elevation.
>
> However, if you know what it should read then provided it is a value sent 
> raw from the station, and is not derived within weewx, you can just say UV 
> = UV - 15 (if you want to just subtract 15 from the value supplied) or UV = 
> UV / 15 if you want to divide the value by 15 - going to your original post 
> maybe it should be UV = UV / 256 - which would probably give 0 at night (if 
> weewx is reporting 15)
>
>
> Guess you should give some examples of UV on console and UV in weewx to be 
> able to derive a calibration formula
>
>
>
> On Wednesday, 11 April 2018 10:04:26 UTC+3, Damjan Hajsek wrote:
>
>> Anyone know what to use in
>> [StdCalibrate]
>> 
>> [[Corrections]]
>>
>> to correct UV index? Because now at night it is UV = 15
>>
>>
>>
>> Dne sreda, 08. november 2017 09.56.35 UTC+1 je oseba Damjan Hajsek 
>> napisala:
>>>
>>> What is relation with UV index and radiation?
>>> Because sometimes radiation is already 0 but UV index is still about 80 
>>> or 50.
>>> Doesn't that be also 0 when radiation is 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: UV index

[Damjan Hajsek]

Anyone know what to use in
[StdCalibrate]

[[Corrections]]

to correct UV index? Because now at night it is UV = 15



Dne sreda, 08. november 2017 09.56.35 UTC+1 je oseba Damjan Hajsek napisala:
>
> What is relation with UV index and radiation?
> Because sometimes radiation is already 0 but UV index is still about 80 or 
> 50.
> Doesn't that be also 0 when radiation is 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: UV index

[Damjan Hajsek]

will increase network traffic volume
loop_delay = 15

# Number of times to try to access the network
max_retry = 3

# Number of seconds to wait between attempts to access the network
retry_wait = 5

# The driver to use:
driver = user.HP1000
##

[Forecast]
data_binding = forecast_binding
[[WU]]
api_key = XXX obfuscated by wee_debug XXX# specify a weather 
underground api_key

wee_debug report successfully generated


Dne nedelja, 12. november 2017 15.10.07 UTC+1 je oseba mwall napisala:
>
> On Sunday, November 12, 2017 at 9:02:20 AM UTC-5, Damjan Hajsek wrote:
>>
>> It is aercus weather ranger and it is the same as ambient weather WS 1002
>> and on console I have UV index 1 on weewx it is 256.
>>
>
> what driver are you using?
>
> please post log output with debug=1
>
> please post some LOOP and REC data when running weewx directly
>
> m
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: UV index

[Damjan Hajsek]

It is aercus weather ranger and it is the same as ambient weather WS 1002
and on console I have UV index 1 on weewx it is 256.


Dne sreda, 08. november 2017 13.05.27 UTC+1 je oseba mwall napisala:
>
> On Wednesday, November 8, 2017 at 3:56:35 AM UTC-5, Damjan Hajsek wrote:
>>
>> What is relation with UV index and radiation?
>> Because sometimes radiation is already 0 but UV index is still about 80 
>> or 50.
>> Doesn't that be also 0 when radiation is 0?
>>
>
> what kind of weather station is this?
>
> weewx does not calculate uv index - it just reports whatever it gets from 
> the station
>
> m 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] UV index

[Damjan Hajsek]

What is relation with UV index and radiation?
Because sometimes radiation is already 0 but UV index is still about 80 or 
50.
Doesn't that be also 0 when radiation is 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx report

[Damjan Hajsek]

THANK YOU both of you.
I get alot of infos and it will help me alot.


Dne sobota, 07. oktober 2017 03.49.30 UTC+2 je oseba Andrew Milner napisala:
>
> An alternative approach is to install 
> cwxn to create cumulus wxnow.txt - bind it to archive if you do not want 
> it updated every loop
> or
> the csv service and create .csv file 
> or
> publish the data to wunderground and tell your friend to get the data from 
> there
>
> see the wiki https://github.com/weewx/weewx/wiki for the skins and 
> services available as standard
>
> If you are not a programmer, I assume the friend who has the website is 
> more capable/confident - so they should have no problem creating the .tmpl 
> file as outlined by Gary if the above suggestions are of no interest
>
>
> On Saturday, 7 October 2017 02:59:07 UTC+3, gjr80 wrote:
>
>> Hi,
>>
>> Creating (and putting to use) a new template file (.tmpl) is a pretty 
>> straight forward process in itself, though depending on how sophisticated 
>> your content it can be quite involved. The easiest approach is to create a 
>> new .tmpl file and add it to an existing skin. You can create a new .tmpl 
>> file and have it run as part of the Standard skin as follows:
>>
>> - Create a new file, newfile.txt.tmpl, on your weeWX machine in the 
>> /home/weewx/skins/Standard directory (this is for a setup.py install, if 
>> you installed using a different method you probably want the 
>> /etc/weewx/skins/Standard directory). This will ultimately result in a 
>> file newfile.txt being generated. How you create/edit the file will 
>> depend on your setup and what you are comfortable using, you might use vi 
>> or nano if workign from the linux command line, you might use a graphical 
>> editor on the linux or windows desktop. Whatever you do use a text editor 
>> and not a word processor, using a word processor will only lead to grief.
>>
>> - Enter whatever text and tags you want in the file. Tags start with a 
>> dollar sign eg $current.outTemp. You can find more details on the 
>> available tags in the Tags section 
>> <http://weewx.com/docs/customizing.htm#Tags> of the Customization Guide 
>> <http://weewx.com/docs/customizing.htm>. Any text in the file not 
>> preceded with a $ will be displayed as is in the resulting file. So to have 
>> our file display 'The temperature is ' where  is the current 
>> temperature with default units we might use the following line in 
>> newfile.txt.tmpl:
>>
>> The temperature is $current.outTemp
>>
>> - Once you are happy with your template save the file. Note it might be 
>> easier to start out small and build to your final template content - much 
>> easier to troubleshoot.
>>
>> - To have your template generate a file you need to include it in the 
>> [CheetahGenerator] stanza of a skin.conf, in this case we have used the 
>> Standard skin so we need to 'add' our template to the the 
>> [CheetahGenerator] stanza of skin.conf in the /home/weewx/skins/Standard 
>> (or /etc/weewx/skins/Standard) directory. Edit skin.conf and locate the 
>> [CheetahGenerator] stanza. You should find a [[ToDate]] stanza under 
>> this. We need to add a new [[[]]] stanza, something like the following 
>> should do:
>>
>> [[[new]]]
>> template = newfile.txt.tmpl
>> 
>> - The name in the [[[]]] can be anything you like, just don't use 
>> something that is already in use.
>>
>> - Save skin.conf. If weeWX is running then during the next report cycle 
>> you should see a file newfile.txt appear in the same directory as you 
>> other Standard skin files.
>>
>> - If it is not there have a look in your weeWX log for errors, if there 
>> are errors let us know what they are or fix them yourself. If no errors and 
>> no file then in weewx.conf set debug=1, stop/start weeWX and then have a 
>> look in the log.
>>
>> That is a fairly basic run through of creating a simple template and have 
>> it generate some output, where you take it from here is up to you; you can 
>> create a new skin, add extra tags, format the tag output, create custom 
>> tags, change the destination of the created file. Reading through the 
>> Customization Guide, especially the Customizing Reports 
>> <http://weewx.com/docs/customizing.htm#customizing_reports> and The 
>> Standard skin.conf <http://weewx.com/docs/customizing.htm#standard_skin> 
>> sections are your best friends.
>>
>> Gary
>>
>>
>> On Saturday, 7 October 2017 07:20:51 UTC+10, Damjan Hajsek wrote:
>>&g

[weewx-user] Re: Weewx report

[Damjan Hajsek]

Sorry don't know how to make tpl file or what to put in that file. I am not 
a programmer so have no clue what to do.

Dne petek, 06. oktober 2017 23.05.43 UTC+2 je oseba vince napisala:
>
> On Friday, October 6, 2017 at 12:25:56 PM UTC-7, Damjan Hajsek wrote:
>>
>> I am trying to do ordinarry text file with data so he can pull out 
>> whatever he want, temperature, preassure, etc? So he can put that on his wb 
>> site.
>> Have you any advice how to do this easiest way?
>> Is there some instructions how to create txt.tmpl file?
>>
>>
>>
> same way you create an anything_else.tmpl file
>  
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx report

[Damjan Hajsek]

I am trying to do ordinarry text file with data so he can pull out whatever 
he want, temperature, preassure, etc? So he can put that on his wb site.
Have you any advice how to do this easiest way?
Is there some instructions how to create txt.tmpl file?


Dne četrtek, 05. oktober 2017 19.10.50 UTC+2 je oseba Andrew Milner 
napisala:
>
> you can create a .txt file by creating a .txt.tmpl file and then you can 
> put whatever you want into it!!
>
> what format file are you trying to create to share with your friend??
>
>
>
> On Thursday, 5 October 2017 20:05:40 UTC+3, Damjan Hajsek wrote:
>
>> Can anyone plese tell me if there is possible to have a weather report in 
>> one file.
>> I like to share weather station report with my friend in txt file, but 
>> don't know how to do it.
>> Weewx can copy over ftp but that are htmls, so how can create just one 
>> txt file?
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Weewx report

[Damjan Hajsek]

Can anyone plese tell me if there is possible to have a weather report in 
one file.
I like to share weather station report with my friend in txt file, but 
don't know how to do it.
Weewx can copy over ftp but that are htmls, so how can create just one txt 
file?

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Forecast plugin error

[Damjan Hajsek]

No it doesn't work, it is too complicated so I just added link to page, 
that works withouth messing a page.
Maybe because sofaskin is differend than one with weewx.

Dne petek, 29. september 2017 17.57.39 UTC+2 je oseba mwall napisala:
>
> On Friday, September 29, 2017 at 11:53:29 AM UTC-4, Andrew Milner wrote:
>>
>> Have fun with the formatting then - especially if you have more than one 
>> detailed forecast!!
>>
>
> it should be pretty easy.  and you can control the detail of the tables 
> and other views using the per-display parameters.
>
> for example, if you include the forecast_table.inc, everything goes inside 
> a div.  same for iconic, compact, or strip formats.
>
> the next release of forecast encapsulates all of the css into div-based 
> namespaces, so there are no conflicts there either.
>
> as long as you don't do anything stupid in your css it should work pretty 
> well.
>
> m
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Forecast plugin error

[Damjan Hajsek]

I also noticed that forecast is in Farenheit, how to set to get forecast in 
Celsius?


Dne petek, 29. september 2017 17.57.39 UTC+2 je oseba mwall napisala:
>
> On Friday, September 29, 2017 at 11:53:29 AM UTC-4, Andrew Milner wrote:
>>
>> Have fun with the formatting then - especially if you have more than one 
>> detailed forecast!!
>>
>
> it should be pretty easy.  and you can control the detail of the tables 
> and other views using the per-display parameters.
>
> for example, if you include the forecast_table.inc, everything goes inside 
> a div.  same for iconic, compact, or strip formats.
>
> the next release of forecast encapsulates all of the css into div-based 
> namespaces, so there are no conflicts there either.
>
> as long as you don't do anything stupid in your css it should work pretty 
> well.
>
> m
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Forecast plugin error

[Damjan Hajsek]

Thank you, I know that, but still looks better if a forecast is on the same 
page.

Dne petek, 29. september 2017 16.38.44 UTC+2 je oseba Andrew Milner 
napisala:
>
> You could always just keep the forecast page separately, and have a link 
> to forecast on he main index page, and add a link back to index on the 
> forecast page.if it proves too hard to merge the code for forecast onto the 
> index page.
>
>
>
>
> On Friday, 29 September 2017 17:00:23 UTC+3, Damjan Hajsek wrote:
>
>> Thank you, it works now, I just need to combine code from multiple tables 
>> into index.html.tpl so page will look normal, now all is messed.
>>
>>
>>
>> 
>> 
>> 
>> 
>> 
>>  Current 
>> Conditions
>> 
>> Outside 
>> Temperature$current.outTemp
>> Wind 
>> Chill$current.windchill
>> Heat 
>> Index$current.heatindex
>> 
>> Dewpoint$current.dewpoint
>> 
>> Humidity$current.outHumidity
>> 
>> Barometer$current.barometer
>> Barometer Trend 
>> ($trend.time_delta.hour.format("%.0f"))$trend.barometer
>> Wind$current.windSpeed 
>> $current.windDir.ordinal_compass ($current.windDir)
>> Rain 
>> Rate$current.rainRate
>> Inside 
>> Temperature$current.inTemp
>> #if $day.extraTemp1.has_data
>> Pond 
>> Temperature$current.extraTemp1
>> #end if
>> #if $day.UV.has_data
>> UV$current.UV
>> #end if
>> #if $day.ET.has_data and $day.ET.sum.raw > 0.0
>> ET$current.ET
>> #end if
>> #if $day.radiation.has_data
>> Solar 
>> Radiation$current.radiation
>> #end if
>>
>> 
>> 
>>
>>
>> 
>>   
>> Forecast Table
>> 
>> Display forecast data in multiple tables, one table for each forecast 
>> source.
>> 
>>
>> #set global $forecast_table_settings = dict()
>> #set global $forecast_table_settings['num_periods'] = 300
>> #set global $forecast_table_settings['show_legend'] = 1
>> #set global $forecast_table_settings['show_hourly'] = 1
>> #set global $forecast_table_settings['show_day'] = 1
>> #set global $forecast_table_settings['show_date'] = 1
>> #set global $forecast_table_settings['show_outlook'] = 1
>> #set global $forecast_table_settings['show_temp'] = 1
>> #set global $forecast_table_settings['show_dewpoint'] = 1
>> #set global $forecast_table_settings['show_wind'] = 1
>> #set global $forecast_table_settings['show_tides'] = 1
>> #set global $forecast_table_settings['show_sun'] = 1
>> #set global $forecast_table_settings['show_moon'] = 1
>> #set global $forecast_table_settings['show_pop'] = 1
>> #set global $forecast_table_settings['show_precip'] = 1
>> #set global $forecast_table_settings['show_obvis'] = 1
>>
>> Weather Underground
>> #set global $forecast_table_settings['source'] = 'WU'
>> #include "forecast_table.inc"
>>
>>
>>
>> 
>> 
>>
>> 
>>  Since 
>> Midnight
>> 
>> High 
>> Temperature$day.outTemp.max$day.outTemp.maxtime
>> Low 
>> Temperature$day.outTemp.min$day.outTemp.mintime
>> High Heat 
>> Index$day.heatindex.max$day.heatindex.maxtime
>> Low Wind 
>> Chill$day.windchill.min$day.windchill.mintime
>> High 
>> Dewpoint$day.dewpoint.max$day.dewpoint.maxtime
>> Low 
>> Dewpoint$day.dewpoint.min$day.dewpoint.mintime
>> High 
>> Humidity$day.outHumidity.max$day.outHumidity.maxtime
>> Low 
>> Humidity$day.outHumidity.min$day.outHumidity.mintime
>> High 
>> Barometer$day.barometer.max$day.barometer.maxtime
>> Low 
>> Barometer$day.barometer.min$day.barometer.mint

[weewx-user] Re: Forecast plugin error

[Damjan Hajsek]

  #end if



Dne petek, 29. september 2017 14.50.14 UTC+2 je oseba mwall napisala:
>
>
>
> On Friday, September 29, 2017 at 8:35:19 AM UTC-4, Damjan Hajsek wrote:
>>
>> Thank you.
>> I have tested forecast skin and it works.
>> Can someone help me implenet this to my skin?
>> http://vreme.povej.net/multiple-tables.html
>>>
>>>
>>>
> 1) add the ForecastVariables search list extension to the skin.conf for 
> your report:
>
> [CheetahGenerator]
> search_list_extensions = user.forecast.ForecastVariables
> ...
>
> 2) include the tables in the template file (typically a file ending in 
> .html.tmpl in your report):
>
> #set global $forecast_table_settings = dict()
>
> #set global $forecast_table_settings['source'] = 'WU'
>
> #include "forecast_table.inc"
>
> #set global $forecast_table_settings['source'] = 'NWS'
>
> #include "forecast_table.inc"
>
> #set global $forecast_table_settings['source'] = 'Aeris'
>
> #include "forecast_table.inc"
>
>
> that is all!
>
> of course, you will not see NWS or aeris data until you add the 
> credentials/locations for those services in the [Forecast] section of 
> weewx.conf
>
> look at the contents of multiple-tables.html.tmpl for more options.  read 
> the comments in forecast_table.inc for more details.  read the comments in 
> forecast.py for even more details.
>
> m
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Forecast plugin error

[Damjan Hajsek]

Thank you. I have raised updating interwal.
I have tested forecast skin and it works.
Can someone help me implenet this to my skin?
http://vreme.povej.net/multiple-tables.html
>
> Thank you. I have raised updating interwal.
> I have tested forecast skin and it works.
> Can someone help me implenet this to my skin?
> http://vreme.povej.net/multiple-tables.html
>
>
>
> Dne petek, 29. september 2017 13.34.04 UTC+2 je oseba mwall napisala:
>>
>> On Friday, September 29, 2017 at 4:30:24 AM UTC-4, Damjan Hajsek wrote:
>>>
>>> Thank you for your time and really good explanation I understand what 
>>> you are saying.
>>> About 60 second period this is just temporarily, because I need to test 
>>> and to calibrate preassure and rainfall, this two are not as it is on 
>>> console. After all will work as it should I will go back on 5 minutes.
>>>
>>
>> as gary pointed out, you will cause yourself more problems by using a 60 
>> second archive interval.  just use 5 minutes, especially while you are 
>> learning the system.
>>
>>  
>>
>>> About forecast, problem is because I don't know where to put this line 
>>> and make weewx to work withouth errors. I tested alot and everytime I get 
>>> error when weewx makes report. So now is withouth this.
>>>
>>> [CheetahGenerator]
>>> search_list_extension = user.forecast.ForecastVariables
>>>
>>>
>> this must be in each report that will use the forecast.
>>
>>  
>>
>>> I also don't understand what to do with this below. Where to put it.
>>>
>>
>> if you follow the instructions for the forecast extension, you should end 
>> up with a skin called "forecast" that just works.
>>
>> do that before you try anything else.
>>
>> after you have verified that works, then you can start adding forecasts 
>> to other skins or customizing the forecast output.
>>
>> m 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Forecast plugin error

[Damjan Hajsek]

Thank you.
I have tested forecast skin and it works.
Can someone help me implenet this to my skin?
http://vreme.povej.net/multiple-tables.html



Dne petek, 29. september 2017 13.34.04 UTC+2 je oseba mwall napisala:
>
> On Friday, September 29, 2017 at 4:30:24 AM UTC-4, Damjan Hajsek wrote:
>>
>> Thank you for your time and really good explanation I understand what you 
>> are saying.
>> About 60 second period this is just temporarily, because I need to test 
>> and to calibrate preassure and rainfall, this two are not as it is on 
>> console. After all will work as it should I will go back on 5 minutes.
>>
>
> as gary pointed out, you will cause yourself more problems by using a 60 
> second archive interval.  just use 5 minutes, especially while you are 
> learning the system.
>
>  
>
>> About forecast, problem is because I don't know where to put this line 
>> and make weewx to work withouth errors. I tested alot and everytime I get 
>> error when weewx makes report. So now is withouth this.
>>
>> [CheetahGenerator]
>> search_list_extension = user.forecast.ForecastVariables
>>
>>
> this must be in each report that will use the forecast.
>
>  
>
>> I also don't understand what to do with this below. Where to put it.
>>
>
> if you follow the instructions for the forecast extension, you should end 
> up with a skin called "forecast" that just works.
>
> do that before you try anything else.
>
> after you have verified that works, then you can start adding forecasts to 
> other skins or customizing the forecast output.
>
> m 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Forecast plugin error

[Damjan Hajsek]

Thank you for your time and really good explanation I understand what you 
are saying.
About 60 second period this is just temporarily, because I need to test and 
to calibrate preassure and rainfall, this two are not as it is on console. 
After all will work as it should I will go back on 5 minutes.
About forecast, problem is because I don't know where to put this line and 
make weewx to work withouth errors. I tested alot and everytime I get error 
when weewx makes report. So now is withouth this.

[CheetahGenerator]
search_list_extension = user.forecast.ForecastVariables

I also don't understand what to do with this below. Where to put it.
Maybe it will be better if that is already builded in weewx but disabled so 
if anyone like to use ti and I think most of us like to use it, it can 
simply enable it.

Forecast variables 

Here is an example of one way to use the $forecast variable in a template.

First query the database for the forecast events:

#set $periods = $forecast.weather_periods('WU', max_events=6)

The first argument is the forecast source, such as 'WU', 'WWO', or 'NWS'. 
Optionally specify the maximum number of events you are interested in. If 
not specified, the query will return every possible event for the indicated 
source.

Each period contains forecast data such as temperature, sky cover, chance 
of precipitation, and obstructions to visibility. Each period also contains 
a timestamp and location.

For example, this would display the time, temperature, and sky cover for 
each period:

#for $period in $periods
$period.event_ts $period.temp $forecast.label('Weather', $period.clouds)
#end for

For details about how to use the $forecast variables, see the comments at 
the beginning of forecast.py.
<https://github.com/weewx/weewx/wiki/forecasting#forecast-icons>Forecast 
icons 

The forecasts include many icons, which must be copied to any skin that 
will use the forecast. For example, if you want to embed the forecast in 
the Standard skin, first copy the icons:

cp -rp skins/forecast/icons skins/Standard

Then include the icons in the list of files that should be copied by the 
CopyGenerator. Append the icons directory to the copy_once parameter in the 
CopyGenerator configuration in skins/Standard/skin.conf:

[CopyGenerator]
copy_once = ..., icons/*.png




Dne petek, 29. september 2017 06.07.58 UTC+2 je oseba gjr80 napisala:
>
> Whilst it is true there apears to be no errors in the log we have not yet 
> seen a portion of the log that includes successful download/processing of a 
> WU forecast, we have seen the forecast report being generated but not the 
> actuall download (the forecast downloads were all creating errors in the 
> first log extract). I suggest you have a look at either the generated 
> forecast report and see if it is correctly populated with forecast data or 
> have a look at the log to ensure that the WU forecast was downloaded and 
> processed error free. Note that on a default install the WU forecast is 
> downloaded/updated every 3 hours.
>
> One other point of note. You are running a very short archive interval of 
> 60 seconds. There is nothing wrong with this in itself, but it means that 
> your reports must be generated in less than 60 seconds or you will end up 
> with the runaway situation where report thread bank up and the system slows 
> to a halt. This occurs when reports for a given archive record take longer 
> than 60 seconds and the set of reports for the next archive record are 
> started. This slows down the previous lot of reports and if these two sets 
> of reports are not complete when the next archive record is received you 
> have another set of reports being run as well. Such a situation can very 
> quickly grind a system to a halt or cause weeWX to be unresponsive/behave 
> in seemingly odd ways. You do not appear to be in that situation now (your 
> reports are executed quickly) but the forecast extension can take a lot of 
> time to produce lengthy forecast reports (particularly 10 day hourly 
> forecasts) and when coupled with the user adding additional reports/skins 
> to the system it is easy to fall into this trap. Using 300seconds (5 
> minutes) as an archive period is pretty standard, it gives a good bit of 
> headroom if you are running numerous or intensive reports. Running a 5 
> minute archive period does not result in any less granulaity of your 
> recorded statistics, it merely alters how often data is stored to archive 
> and how frequently reports can be run. If you are concerned with how often 
> your displayed data is updated then there are other options for near 
> realtime display of data. Some food for thought for you.
>
> Gary
>
> On Friday, 29 September 2017 03:51:10 UTC+10, Damjan Hajsek wrote:
>
> I hope this will do.
>
>
> Sep 28 19:00:20  weewx[3088]: manager: Added record

[weewx-user] Re: Forecast plugin error

[Damjan Hajsek]

No I didn't have any errors at all.

Dne petek, 29. september 2017 04.19.25 UTC+2 je oseba Andrew Milner 
napisala:
>
> So, the log from 1900 - 1939 does not show any errors or issues.
>
> Did you have any problems with weewx during that time period?
>
>
>
> On Thursday, 28 September 2017 20:51:10 UTC+3, Damjan Hajsek wrote:
>
> I hope this will do.
>
>
> Sep 28 19:00:20  weewx[3088]: manager: Added record 2017-09-28 19:00:00 
> CEST (1506618000) to database 'weewx'
> Sep 28 19:00:20  weewx[3088]: manager: Added record 2017-09-28 19:00:00 
> CEST (1506618000) to daily summary in 'weewx'
> Sep 28 19:00:20  weewx[3088]: cheetahgenerator: Generated 7 files for 
> report StandardReport in 0.35 seconds
> Sep 28 19:00:21  weewx[3088]: imagegenerator: Generated 24 images for 
> StandardReport in 1.25 seconds
> Sep 28 19:00:21  weewx[3088]: copygenerator: copied 0 files to 
> /var/www/html/weewx
> Sep 28 19:00:23  weewx[3088]: cheetahgenerator: Generated 10 files for 
> report forecast in 1.13 seconds
> Sep 28 19:00:23  weewx[3088]: copygenerator: copied 0 files to 
> /var/www/html/weewx/forecast
> Sep 28 19:00:45  systemd: Stopping SYSV: start and stop the weewx weather 
> system...
> Sep 28 19:00:45  weewx[3088]: engine: Shutting down StdReport thread
> Sep 28 19:00:45  weewx[3088]: interceptor: MainThread: shutting down 
> server thread
> Sep 28 19:00:46  weewx[3088]: engine: Terminating weewx version 3.7.1
> Sep 28 19:00:46  python: detected unhandled Python exception in 
> '/usr/bin/weewxd'
> Sep 28 19:00:46  weewx: Shutting down weewx: [  V redu  ]
> Sep 28 19:00:46  systemd: Starting SYSV: start and stop the weewx weather 
> system...
> Sep 28 19:00:47  weewx[4743]: engine: Initializing weewx version 3.7.1
> Sep 28 19:00:47  weewx[4743]: engine: Using Python 2.7.5 (default, Nov  6 
> 2016, 00:28:07) #012[GCC 4.8.5 20150623 (Red Hat 4.8.5-11)]
> Sep 28 19:00:47  weewx[4743]: engine: Platform 
> Linux-3.10.0-514.26.2.el7.x86_64-x86_64-with-centos-7.3.1611-Core
> Sep 28 19:00:47  weewx[4743]: engine: Locale is 'sl_SI.UTF-8'
> Sep 28 19:00:47  weewx[4743]: engine: pid file is /var/run/weewx.pid
> Sep 28 19:00:47  weewx[4747]: engine: Using configuration file 
> /etc/weewx/weewx.conf
> Sep 28 19:00:47  weewx[4747]: engine: Loading station type Interceptor 
> (user.interceptor)
> Sep 28 19:00:47  weewx: Starting weewx: [  V redu  ]
> Sep 28 19:00:47  systemd: Started SYSV: start and stop the weewx weather 
> system.
> Sep 28 19:00:47  weewx[4747]: interceptor: MainThread: driver version is 
> 0.36
> Sep 28 19:00:47  weewx[4747]: interceptor: MainThread: device type: 
> observer
> Sep 28 19:00:47  weewx[4747]: interceptor: MainThread: sensor map: None
> Sep 28 19:00:47  weewx[4747]: interceptor: MainThread: mode is listen
> Sep 28 19:00:47  weewx[4747]: interceptor: MainThread: listen on :
> Sep 28 19:00:47  weewx[4747]: engine: StdConvert target unit is 0x1
> Sep 28 19:00:47  weewx[4747]: 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 28 19:00:47  weewx[4747]: wxcalculate: The following algorithms will 
> be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
> Sep 28 19:00:47  weewx[4747]: engine: Archive will use data binding 
> wx_binding
> Sep 28 19:00:47  weewx[4747]: engine: Record generation will be attempted 
> in 'software'
> Sep 28 19:00:47  weewx[4747]: engine: Using archive interval of 60 seconds 
> (specified in weewx configuration)
> Sep 28 19:00:47  weewx[4747]: engine: Using binding 'wx_binding' to 
> database 'weewx'
> Sep 28 19:00:47  weewx[4747]: manager: Starting backfill of daily summaries
> Sep 28 19:00:47  weewx[4747]: forecast: MainThread: Zambretti: forecast 
> version 3.2.17
> Sep 28 19:00:47  weewx[4747]: forecast: MainThread: Zambretti: 
> interval=600 max_age=604800 winddir_period=1800 pressure_period=10800 
> hemisphere=NORTH lower_pressure=950.0 upper_pressure=1050.0
> Sep 28 19:00:47  weewx[4747]: forecast: MainThread: NWS: forecast version 
> 3.2.17
> Sep 28 19:00:47  weewx[4747]: forecast: MainThread: NWS: location ID (lid) 
> is not specified
> Sep 28 19:00:47  weewx[4747]: forecast: MainThread: NWS: forecast office 
> ID (foid) is not specified
> Sep 28 19:00:47  weewx[4747]: forecast: MainThread: NWS: forecast will not 
> be run
> Sep 28 19:00:47  weewx[4747]: forecast: MainThread: WU: forecast version 
&

[weewx-user] Re: Forecast plugin error

[Damjan Hajsek]

 28 19:34:50  weewx[4747]: manager: Added record 2017-09-28 19:34:00 
CEST (1506620040) to database 'weewx'
Sep 28 19:34:50  weewx[4747]: manager: Added record 2017-09-28 19:34:00 
CEST (1506620040) to daily summary in 'weewx'
Sep 28 19:34:51  weewx[4747]: cheetahgenerator: Generated 7 files for 
report StandardReport in 0.36 seconds
Sep 28 19:34:51  weewx[4747]: imagegenerator: Generated 12 images for 
StandardReport in 0.38 seconds
Sep 28 19:34:51  weewx[4747]: copygenerator: copied 0 files to 
/var/www/html/weewx
Sep 28 19:34:52  weewx[4747]: cheetahgenerator: Generated 10 files for 
report forecast in 1.12 seconds
Sep 28 19:34:52  weewx[4747]: copygenerator: copied 0 files to 
/var/www/html/weewx/forecast
Sep 28 19:35:16  weewx[4747]: manager: Added record 2017-09-28 19:35:00 
CEST (1506620100) to database 'weewx'
Sep 28 19:35:16  weewx[4747]: manager: Added record 2017-09-28 19:35:00 
CEST (1506620100) to daily summary in 'weewx'
Sep 28 19:35:17  weewx[4747]: cheetahgenerator: Generated 7 files for 
report StandardReport in 0.35 seconds
Sep 28 19:35:17  weewx[4747]: imagegenerator: Generated 12 images for 
StandardReport in 0.34 seconds
Sep 28 19:35:17  weewx[4747]: copygenerator: copied 0 files to 
/var/www/html/weewx
Sep 28 19:35:18  weewx[4747]: cheetahgenerator: Generated 10 files for 
report forecast in 1.31 seconds
Sep 28 19:35:18  weewx[4747]: copygenerator: copied 0 files to 
/var/www/html/weewx/forecast
Sep 28 19:36:20  weewx[4747]: manager: Added record 2017-09-28 19:36:00 
CEST (1506620160) to database 'weewx'
Sep 28 19:36:20  weewx[4747]: manager: Added record 2017-09-28 19:36:00 
CEST (1506620160) to daily summary in 'weewx'
Sep 28 19:36:20  weewx[4747]: cheetahgenerator: Generated 7 files for 
report StandardReport in 0.33 seconds
Sep 28 19:36:20  weewx[4747]: imagegenerator: Generated 12 images for 
StandardReport in 0.35 seconds
Sep 28 19:36:20  weewx[4747]: copygenerator: copied 0 files to 
/var/www/html/weewx
Sep 28 19:36:22  weewx[4747]: cheetahgenerator: Generated 10 files for 
report forecast in 1.11 seconds
Sep 28 19:36:22  weewx[4747]: copygenerator: copied 0 files to 
/var/www/html/weewx/forecast
Sep 28 19:37:24  weewx[4747]: manager: Added record 2017-09-28 19:37:00 
CEST (1506620220) to database 'weewx'
Sep 28 19:37:24  weewx[4747]: manager: Added record 2017-09-28 19:37:00 
CEST (1506620220) to daily summary in 'weewx'
Sep 28 19:37:25  weewx[4747]: cheetahgenerator: Generated 7 files for 
report StandardReport in 0.35 seconds
Sep 28 19:37:25  weewx[4747]: imagegenerator: Generated 12 images for 
StandardReport in 0.34 seconds
Sep 28 19:37:25  weewx[4747]: copygenerator: copied 0 files to 
/var/www/html/weewx
Sep 28 19:37:26  weewx[4747]: cheetahgenerator: Generated 10 files for 
report forecast in 1.12 seconds
Sep 28 19:37:26  weewx[4747]: copygenerator: copied 0 files to 
/var/www/html/weewx/forecast
Sep 28 19:38:44  weewx[4747]: manager: Added record 2017-09-28 19:38:00 
CEST (1506620280) to database 'weewx'
Sep 28 19:38:44  weewx[4747]: manager: Added record 2017-09-28 19:38:00 
CEST (1506620280) to daily summary in 'weewx'
Sep 28 19:38:44  weewx[4747]: cheetahgenerator: Generated 7 files for 
report StandardReport in 0.37 seconds
Sep 28 19:38:45  weewx[4747]: imagegenerator: Generated 12 images for 
StandardReport in 0.35 seconds
Sep 28 19:38:45  weewx[4747]: copygenerator: copied 0 files to 
/var/www/html/weewx
Sep 28 19:38:46  weewx[4747]: cheetahgenerator: Generated 10 files for 
report forecast in 1.31 seconds
Sep 28 19:38:46  weewx[4747]: copygenerator: copied 0 files to 
/var/www/html/weewx/forecast
Sep 28 19:39:16  weewx[4747]: manager: Added record 2017-09-28 19:39:00 
CEST (1506620340) to database 'weewx'
Sep 28 19:39:16  weewx[4747]: manager: Added record 2017-09-28 19:39:00 
CEST (1506620340) to daily summary in 'weewx'
Sep 28 19:39:17  weewx[4747]: cheetahgenerator: Generated 7 files for 
report StandardReport in 0.36 seconds
Sep 28 19:39:17  weewx[4747]: imagegenerator: Generated 12 images for 
StandardReport in 0.34 seconds
Sep 28 19:39:17  weewx[4747]: copygenerator: copied 0 files to 
/var/www/html/weewx
Sep 28 19:39:18  weewx[4747]: cheetahgenerator: Generated 10 files for 
report forecast in 1.33 seconds
Sep 28 19:39:18  weewx[4747]: copygenerator: copied 0 files to 
/var/www/html/weewx/forecast


Dne četrtek, 28. september 2017 18.59.52 UTC+2 je oseba Andrew Milner 
napisala:
>
> well that looks all ok until the end of the log - which ws just when it 
> would have started to generate the reports I suspect - you seem to have cut 
> off the log too early - you should send the log for say 10-15 minutes from 
> startup (covering say two archive intervals)
>
> On Thursday, 28 September 2017 19:46:03 UTC+3, Damjan Hajsek wrote:
>
>> Thank you for explaining.
>> Here is conf file, I have deleted out weather sites whic I don't have api 
>> key and leave only WU.
>>
>> # WEEWX CONFIGURATION FILE
>>

[weewx-user] Re: Forecast plugin error

[Damjan Hajsek]

Thank you for explaining.
Here is conf file, I have deleted out weather sites whic I don't have api 
key and leave only WU.

# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2015 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 = /

# 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.7.1

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = Slovenia - Domzale

# Latitude and longitude in decimal degrees
latitude = 45.1299910
longitude = 13.6003179

# Altitude of the station, with unit it is in. This is downloaded from
# from the station if the hardware supports it.
altitude = 293, meter# Choose 'foot' or 'meter' for unit

# 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 = Interceptor

# 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 = 0

# If you have a website, you may specify an URL
station_url = http://vreme.povej.net

##

[AcuRite]
# This section is for AcuRite weather stations.

# The station model, e.g., 'AcuRite 01025' or 'AcuRite 02032C'
model = AcuRite 01035

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

##

[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

##

[Simulator]
# This section is for the weewx weather station simulator

# The time (in seconds) between LOOP packets.
loop_interval = 2.5

# The simulator mode can be either 'simulator' or 'generator'.
# Real-time simulator. Sleep between each LOOP packet.
mode = simulator
# Generator.  Emit LOOP packets as fast as possible (useful for 
testing).
#mode = generator

# The start time. If not specified, the default is to use the present 
time.
#start = 2011-01-01 00:00

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

##

[WS1]
# This section is for the ADS WS1 series of weather stations.

# Driver mode - tcp, udp, or serial
mode = tcp

# If serial, specify the serial port device. (ex. /dev/ttyS0, 
/dev/ttyUSB0,
# or /dev/cuaU0)
# If TCP, specify the IP address and port number. (ex. 
192.168.36.25:3000)
port = 192.168.1.200

# The amount of time, in seconds, before the connection fails if there 
is
# no response
timeout = 3

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

##

#   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 = false

[[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.
enable = false
username = replace_me
# To guard against parsing errors, put your password in quotes:
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 

[weewx-user] Re: Forecast plugin error

[Damjan Hajsek]

Hi, thank you for detailed explanation.

Yes forecast.py is in /usr/share/weewx/user
And forecast plugins looks like it works.
Problem is because I didn't find right place to put this string in
search_list_extensions = user.forecast.ForecastVariables

Where I placed it it makes error and weewx doesn't work.

here is log, withouth that string 
search_list_extensions = user.forecast.ForecastVariables

http://zerobin.povej.net/?a146f77edf4092d0#21RhXJeUSxn7HfIbYl/2UFdepSxDBbWbH49FYMtsevw=



Dne sreda, 27. september 2017 10.36.23 UTC+2 je oseba gjr80 napisala:
>
> Hi,
>
> Let's start with the obvious, is forecast.py actually in 
> /home/weewx/bin/user (for a setup.py install) or /usr/share/weewx/user 
> (for .deb, .rpm etc install)? If not, the forecst extension was not 
> installed correctly - go back and install again, preferably using the 
> wee_extension utility, taking note of any errors etc during installation. 
> If forecast.py is where it should be then I suggest you edit weewx.conf, 
> set debug = 1, stop then start weeWX and post a log extract from weeWX 
> start until a couple of archive periods have passed. This will give us some 
> context for your error. For future info, in 9 out of 10 cases posting a log 
> extract rather than a single error message will make it easier for us (and 
> you) to track down and fix the issue.
>
> Gary
>
> On Wednesday, 27 September 2017 17:47:15 UTC+10, Damjan Hajsek wrote:
>>
>> I have installed forecast plugin and get this error  
>> https://github.com/weewx/weewx/wiki/forecasting
>>
>>
>> forecast_iconic: forecast search list extension is not installed
>>
>>
>> And I have this in skin.conf search_list_extensions = 
>> user.forecast.ForecastVariables
>>
>> [CheetahGenerator]
>> # This section is used by the generator CheetahGenerator, and 
>> specifies
>> # which files are to be generated from which template.
>> # Possible encodings are 'html_entities', 'utf8', or 'strict_ascii'
>> encoding = html_entities
>> search_list_extensions = user.forecast.ForecastVariables
>> [[SummaryByMonth]]
>> # Reports that summarize "by month"
>> [[[NOAA_month]]]
>> encoding = utf8
>> template = NOAA/NOAA--MM.txt.tmpl
>>
>> [[SummaryByYear]]
>> # Reports that summarize "by year"
>> [[[NOAA_year]]]
>> encoding = utf8
>> template = NOAA/NOAA-.txt.tmpl
>> 
>> [[ToDate]]
>> # Reports that show statistics "to date", such as day-to-date,
>> # week-to-date, month-to-date, etc.
>> [[[day]]]
>> template = index.html.tmpl
>> 
>> [[[week]]]
>> template = week.html.tmpl
>> 
>> [[[month]]]
>> template = month.html.tmpl
>> 
>> [[[year]]]
>> template = year.html.tmpl
>> 
>> [[[RSS]]]
>> template = RSS/weewx_rss.xml.tmpl
>>
>>
>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] weewx not starting after reboot (manual intervention necessary)

[Damjan Hajsek]

I suggest you to use ping script which starts at startup and when it pings 
than it start weewx, you can also use it if connection is lost than it 
reboot.

Dne sobota, 23. september 2017 14.23.43 UTC+2 je oseba Dave Harper napisala:
>
>
>
> On Friday, September 22, 2017 at 11:42:32 PM UTC-5, Andrew Milner wrote:
>>
>> I think it has started when wifi network was up rather than Ethernet 
>> network.  Did you set wait for network in raspi-config - which is the RPi 
>> method of ensuring network is available while booting.
>>
>>>
>>> Thanks for the suggestion - I was unaware of this option.  However, I 
> tried it (independently from the suggestion Tom made) and for some reason 
> it didn't work (which surprised me as it sounded like an obvious solution). 
>  Looking at the syslog after the boot showed almost exactly the same 
> situation as shown in the syslog1 file I attached in the original post - 
> weewx still started up before networking was up.  After the boot I went 
> back in to raspi-config and verified that it was set to wait and it was. 
>  As for wifi, that is turned off.  The Pi is physically located next to the 
> Vantage Pro2 console which already required wired Ethernet for uploading so 
> I went wired for the Pi too.
>
> Dave 
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Forecast plugin error

[Damjan Hajsek]

I have installed forecast plugin and get this error  
https://github.com/weewx/weewx/wiki/forecasting


forecast_iconic: forecast search list extension is not installed


And I have this in skin.conf search_list_extensions = 
user.forecast.ForecastVariables

[CheetahGenerator]
# This section is used by the generator CheetahGenerator, and specifies
# which files are to be generated from which template.
# Possible encodings are 'html_entities', 'utf8', or 'strict_ascii'
encoding = html_entities
search_list_extensions = user.forecast.ForecastVariables
[[SummaryByMonth]]
# Reports that summarize "by month"
[[[NOAA_month]]]
encoding = utf8
template = NOAA/NOAA--MM.txt.tmpl

[[SummaryByYear]]
# Reports that summarize "by year"
[[[NOAA_year]]]
encoding = utf8
template = NOAA/NOAA-.txt.tmpl

[[ToDate]]
# Reports that show statistics "to date", such as day-to-date,
# week-to-date, month-to-date, etc.
[[[day]]]
template = index.html.tmpl

[[[week]]]
template = week.html.tmpl

[[[month]]]
template = month.html.tmpl

[[[year]]]
template = year.html.tmpl

[[[RSS]]]
template = RSS/weewx_rss.xml.tmpl



-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: problems with pressure on WeatherRanger

[Damjan Hajsek]

here are loop packets again, before I forget to disable calibration

http://zerobin.povej.net/?170843575d112ab6#m8n6suRJmh/WbTp9FTuSxwETZKDodPNnJQbQ4R4h4bw=

Dne ponedeljek, 25. september 2017 21.54.07 UTC+2 je oseba Damjan Hajsek 
napisala:
>
> Here are packet I hope this time I get right packets.
>
>
> http://zerobin.povej.net/?617f993cae15cb3f#c/uDiL2ZHhGvTFQQ8sZgY0ILHUuhFKcBVsB/rFdxdE8=
>
>
>
> Dne petek, 22. september 2017 13.55.41 UTC+2 je oseba Andrew Milner 
> napisala:
>>
>> Where are the LOOP and REC packets??  They are not in the file you 
>> posted. 
>>
>>
>>
>> On Friday, 22 September 2017 14:28:02 UTC+3, Damjan Hajsek wrote:
>>
>>> Here is a link for values I write both preassure and rain rate and below 
>>> data from weewx.
>>> When I manually start weewx I get some errors so half is with manually 
>>> starting weewx and half when restart weewx.
>>>
>>>
>>> http://zerobin.povej.net/?2b67951062395755#msXGtrC6ARHSBTBUCDj5qdeV920nG2FzZbloR3nozAI=
>>>
>>>
>>>
>>> Dne četrtek, 21. september 2017 19.43.59 UTC+2 je oseba mwall napisala:
>>>>
>>>> On Tuesday, September 19, 2017 at 7:54:35 AM UTC-4, Damjan Hajsek wrote:
>>>>>
>>>>> About preassure,  I use absolute preassure which is higher than sea 
>>>>> level preassure, my altitude is 293m (I have this setting in weewx.conf). 
>>>>> When I checked my absolute preassure it was about 1008mbar until sea 
>>>>> level 
>>>>> was I think about 995mbar. But I have always set to absoulte preassure 
>>>>> and 
>>>>> when is absoulte preassure 1010mbar weewx shows 1008 mbar.
>>>>>
>>>>> Dne torek, 19. september 2017 13.38.51 UTC+2 je oseba mwall napisala:
>>>>>>
>>>>>>
>>>>>> regarding pressure, are you comparing apples to apples?  is the 
>>>>>> console reporting gauge pressure or sea level pressure?  what is the 
>>>>>> station altitude?
>>>>>>
>>>>>
>>>> run weewx directly.
>>>>
>>>> post the output from a few LOOP packets, not the log output.  for each 
>>>> LOOP packet you post, also post the value for pressure that was displayed 
>>>> on the console at the time of that LOOP packet.
>>>>
>>>> m
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: problems with pressure on WeatherRanger

[Damjan Hajsek]

Here are packet I hope this time I get right packets.

http://zerobin.povej.net/?617f993cae15cb3f#c/uDiL2ZHhGvTFQQ8sZgY0ILHUuhFKcBVsB/rFdxdE8=



Dne petek, 22. september 2017 13.55.41 UTC+2 je oseba Andrew Milner 
napisala:
>
> Where are the LOOP and REC packets??  They are not in the file you posted. 
>
>
>
> On Friday, 22 September 2017 14:28:02 UTC+3, Damjan Hajsek wrote:
>
>> Here is a link for values I write both preassure and rain rate and below 
>> data from weewx.
>> When I manually start weewx I get some errors so half is with manually 
>> starting weewx and half when restart weewx.
>>
>>
>> http://zerobin.povej.net/?2b67951062395755#msXGtrC6ARHSBTBUCDj5qdeV920nG2FzZbloR3nozAI=
>>
>>
>>
>> Dne četrtek, 21. september 2017 19.43.59 UTC+2 je oseba mwall napisala:
>>>
>>> On Tuesday, September 19, 2017 at 7:54:35 AM UTC-4, Damjan Hajsek wrote:
>>>>
>>>> About preassure,  I use absolute preassure which is higher than sea 
>>>> level preassure, my altitude is 293m (I have this setting in weewx.conf). 
>>>> When I checked my absolute preassure it was about 1008mbar until sea level 
>>>> was I think about 995mbar. But I have always set to absoulte preassure and 
>>>> when is absoulte preassure 1010mbar weewx shows 1008 mbar.
>>>>
>>>> Dne torek, 19. september 2017 13.38.51 UTC+2 je oseba mwall napisala:
>>>>>
>>>>>
>>>>> regarding pressure, are you comparing apples to apples?  is the 
>>>>> console reporting gauge pressure or sea level pressure?  what is the 
>>>>> station altitude?
>>>>>
>>>>
>>> run weewx directly.
>>>
>>> post the output from a few LOOP packets, not the log output.  for each 
>>> LOOP packet you post, also post the value for pressure that was displayed 
>>> on the console at the time of that LOOP packet.
>>>
>>> m
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: problems with pressure on WeatherRanger

[Damjan Hajsek]

I did this, first half of report is maded like that but obvously something 
was wrong.
I stopped weewx service and did that manually.
I will do it again and report.

Dne petek, 22. september 2017 13.52.11 UTC+2 je oseba mwall napisala:
>
> On Friday, September 22, 2017 at 7:28:02 AM UTC-4, Damjan Hajsek wrote:
>>
>> Here is a link for values I write both preassure and rain rate and below 
>> data from weewx.
>> When I manually start weewx I get some errors so half is with manually 
>> starting weewx and half when restart weewx.
>>
>>
>> http://zerobin.povej.net/?2b67951062395755#msXGtrC6ARHSBTBUCDj5qdeV920nG2FzZbloR3nozAI=
>>
>
>
> damjan,
>
> by now it should be obvious that you cannot run two instances of weewx at 
> the same time when they both try listen on port ; you must stop any 
> weewx daemon before you run weewx directly.
>
> in order to diagnose values from sensors, we need to see LOOP (and 
> possibly REC) values.  to do this you must run weewx directly, i.e., not as 
> a daemon:
>
> http://weewx.com/docs/usersguide.htm#Running_directly
>
> when you run weewx directly it display sensor values as soon as it 
> receives them from the hardware.
>
> while weewx is running, you must look at the weather station console and 
> write down the values you see at the time of each LOOP packet.
>
> then post the LOOP output and the values you wrote down from the console.
>
> it would also help if you would explain what you expect to see, otherwise 
> we don't know whether there is a problem with weewx or an 'education' 
> problem.
>
> m 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Use template for Ftp

[Damjan Hajsek]

I have checked customization of weewx found this but can't find where you 
specify to create another report in txt file and in folder which I choose.

[StdReport]

# Where the skins reside, relative to WEEWX_ROOT
SKIN_ROOT = skins

# Where the generated reports should go, relative to WEEWX_ROOT
HTML_ROOT = public_html

# The database binding indicates which data should be used in reports.
data_binding = wx_binding

# Report timing parameter
report_timing = 0 * * * *

# Each of the following subsections defines a report that will be run.

[[AReport]]
skin = SomeSkin

[[AnotherReport]]
skin = SomeOtherSkin
report_timing = */10 * * * *



Dne petek, 22. september 2017 13.35.26 UTC+2 je oseba Juan Antonio Mosquera 
napisala:
>
> Yes, is possible.
>
> Read instructions of mwall.
>
> Greetings.
>
> El viernes, 22 de septiembre de 2017, 13:33:51 (UTC+2), Damjan Hajsek 
> escribió:
>>
>> Is it possible to have a report in one file readable like txt, because I 
>> like to share that report on my web page?
>>
>>
>> Dne četrtek, 21. september 2017 18.39.40 UTC+2 je oseba mwall napisala:
>>>
>>> On Thursday, September 21, 2017 at 12:14:52 PM UTC-4, Juan Antonio 
>>> Mosquera wrote:
>>>>
>>>> Ok...  pero el problema es que yo solo quiero subir un tmpl a FTP y 
>>>> todos los ficheros a Rsync.
>>>>
>>>>>
>>>>>
>>> the rsync and ftp 'reports' do not work that way.  they only work on a 
>>> directory of files, not individual files.
>>>
>>> but of course you have options.  here are a few:
>>>
>>> 1) create another report that only generates the one file that you want 
>>> to transfer using ftp.  use ftp for that report, and rsync for the 'full' 
>>> report.
>>>
>>> 2) make the report put the file that you want to ftp into a 
>>> subdirectory, then configure HTML_ROOT for ftp to be that directory instead 
>>> of the report's HTML_ROOT
>>>
>>> 3) in python, write a new ftp report generator that can be configured to 
>>> transfer individual files, not just a single directory.  pull requests for 
>>> changes to the ftp generator are welcome, or just write your own that is 
>>> derived from the ftp generator.
>>>
>>> m
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.