Re: [weewx-user] weewx no longer starts after restart, reinstallation stops

[J. H.]

please delete the entire thread, thanks-I'll make a new one

J. H. schrieb am Mittwoch, 24. April 2024 um 08:10:01 UTC+2:

> other installations also hang
>
> J. H. schrieb am Mittwoch, 24. April 2024 um 06:36:00 UTC+2:
>
>> from my point of view, there is a problem with the operating system, i.e. 
>> some parts are destroyed or damaged. how can you find out?
>>
>>
>>

-- 
You received this message because you are 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/05369f3f-a8fe-47cf-bcff-27ee5caa1da6n%40googlegroups.com.

Re: [weewx-user] weewx no longer starts after restart, reinstallation stops

[J. H.]

other installations also hang

J. H. schrieb am Mittwoch, 24. April 2024 um 06:36:00 UTC+2:

> from my point of view, there is a problem with the operating system, i.e. 
> some parts are destroyed or damaged. how can you find out?
>
>
>

-- 
You received this message because you are 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/05d3520d-970a-4601-815d-70554863395bn%40googlegroups.com.

Re: [weewx-user] weewx no longer starts after restart, reinstallation stops

[J. H.]

from my point of view, there is a problem with the operating system, i.e. 
some parts are destroyed or damaged. how can you find out?


-- 
You received this message because you are 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/baf8dc3f-444e-464e-8114-25341cd5da23n%40googlegroups.com.

Re: [weewx-user] weewx no longer starts after restart, reinstallation stops

[J. H.]

Exactly, the log shows nothing and the installation hangs or the start does 
not work.

Tom Keffer schrieb am Dienstag, 23. April 2024 um 16:35:26 UTC+2:

> I am not sure what we're looking at here. Did the installation hang, and 
> not proceed, at this point?
>
> What is in the log?
>
> On Tue, Apr 23, 2024 at 2:00 AM J. H.  wrote:
>
>> Linux s2 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31) x86_64 
>> GNU/Linux
>>
>>
>>
>> 1 nicht vollständig installiert oder entfernt.
>> Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
>> Möchten Sie fortfahren? [J/n] j
>> weewx (5.0.2-1) wird eingerichtet ...
>> Using weewx:weewx as user:group
>> Saving old defaults to /etc/default/weewx-20240423105229
>> Creating /etc/default/weewx
>> Using configuration file /etc/weewx/weewx.conf
>> Processing configuration file /etc/weewx/weewx.conf
>> Saving configuration file /etc/weewx/weewx.conf
>> User r7598 is already in group weewx
>> Installing systemd units
>> Installing udev rules
>> Configuring database directory /var/lib/weewx
>> Configuring reporting directory /var/www/html/weewx
>> Setting permissions weewx:weewx on /etc/weewx
>> Enabling startup using systemd
>> Starting weewxd using systemd
>>
>> Fortschritt: [ 33%] 
>> [##... 
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/98dfefb0-a0e8-4d4c-92d0-ad4a727109cen%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/98dfefb0-a0e8-4d4c-92d0-ad4a727109cen%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e97cf2ba-9e2d-47ee-ae97-b855af650673n%40googlegroups.com.

[weewx-user] weewx no longer starts after restart, reinstallation stops

[J. H.]

Linux s2 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31) x86_64 
GNU/Linux



1 nicht vollständig installiert oder entfernt.
Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n] j
weewx (5.0.2-1) wird eingerichtet ...
Using weewx:weewx as user:group
Saving old defaults to /etc/default/weewx-20240423105229
Creating /etc/default/weewx
Using configuration file /etc/weewx/weewx.conf
Processing configuration file /etc/weewx/weewx.conf
Saving configuration file /etc/weewx/weewx.conf
User r7598 is already in group weewx
Installing systemd units
Installing udev rules
Configuring database directory /var/lib/weewx
Configuring reporting directory /var/www/html/weewx
Setting permissions weewx:weewx on /etc/weewx
Enabling startup using systemd
Starting weewxd using systemd

Fortschritt: [ 33%] 
[##...

-- 
You received this message because you are 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/98dfefb0-a0e8-4d4c-92d0-ad4a727109cen%40googlegroups.com.

Re: [weewx-user] Wunderground uploads using wunderfixer

[J Jones]

This still works for me. My server was down for almost a month. I was able 
to backfill the 7 or so days that was logged in the data logger.

On Monday, March 25, 2024 at 12:48:26 PM UTC-5 Tom Keffer wrote:

> If someone wants to take it on as a project, we could put it in its own 
> repository.
>
> On Mon, Mar 25, 2024 at 10:47 AM 'Andy Peterman' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> Actually, I've had this work for entries even older.  I just had it 
>> update entries from the previous day and it seems to have worked.  
>>
>> Let's keep wunderfixer around!
>>
>
>> On Friday, March 22, 2024 at 5:52:04 AM UTC-7 Tom Keffer wrote:
>>
>>> Good to know! So, it appears the WU will allow postdating of up to 4 
>>> hours.
>>>
>>> On Thu, Mar 21, 2024 at 7:42 PM 'Andy Peterman' via weewx-user <
>>> weewx...@googlegroups.com> wrote:
>>>
 Strange, I'm still running 4.10.2 and just used wunderfixer 
 successfully.  Our Internet was down for about 3 hours, I ran wunderfixer, 
 and it filled in the entire period.  Also, last weekend weewx hung right 
 after the time change (not sure why, but that's another problem) and when 
 I 
 got it going again, I had about a 4 hour gap.  Once again, I ran 
 wunderfixer and it filled in the 20+ entries that were missing.  It was a 
 while before the data showed up, but I checked and it's definitely there.

 Are you sure that Weather Underground has removed this feature?

 On Tuesday, October 10, 2023 at 5:33:19 PM UTC-7 Tom Keffer wrote:

> Thanks for verifying what we've always suspected. I'm actually 
> surprised they responded at all!
>
> For just this reason we've dropped wunderfixer from V5.
>
> On Tue, Oct 10, 2023 at 2:16 PM Ernest Jillson  
> wrote:
>
>> Good afternoon group.
>>  
>> I emailed Weather Underground support yesterday about backfilling 
>> observations after having no internet for two days. Here was the 
>> response:
>>  
>> "Thank you for being so kind as to want to backfill your station's 
>> data.  But because of the quality control process we have in place, data 
>> that is more than an hour old is discarded.  So the upload is a success, 
>> but it will never appear on the site.
>>
>> Please let me know if you have any additional questions.  Thank you 
>> for being part of the Weather Underground community!
>>
>> --Victoria"
>>  
>> While I did reply back and ask if that feature would be restored at 
>> any time in the future, I think we can call this process dead. It sounds 
>> like wunderfixer will still work, though, for data less than 1 hour old.
>>  
>> Ernie
>>
>> -- 
>> You received this message because you are subscribed to the Google 
>> Groups "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, 
>> send an email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/CAC5oUmOeLccyR-Jng%2BZCQBXbfixHNnZCevPJd_0CrwK4GjF%3DRw%40mail.gmail.com
>>  
>> 
>> .
>>
> -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to weewx-user+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/b4276305-cc25-4271-a7ce-0762b1d8c2c5n%40googlegroups.com
  
 
 .

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/caa70ba6-93a0-4471-a13d-143b97dbbc22n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/814bf076-5c96-413c-ac23-3de68c1b817dn%40googlegroups.com.

[weewx-user] Re: Weectl import

['J O' via weewx-user]

Hi Gary,
thanks for your quick response. I'm afraid that I should have done that, 
but now I already have two databases because the new installation started 
and the old has been stopped. So I will need to import in the one or the 
other direction anyway. Or, alternatively, I will loose the data during the 
overlap time (1+ week).
Jens

gjr80 schrieb am Freitag, 8. März 2024 um 22:48:16 UTC+1:

> I am not sure why you are exporting data from your old WeeWX database and 
> then importing the data into a new installation. The WeeWX database is 
> compatible across all WeeWX versions so you can just use it without change 
> in your new WeeWX installation. Your existing WeeWX database may use the 
> old 'wview' database schema rather than the new 'view_extended' database 
> schema, but there is no particular need to upgrade to the 'view_extended' 
> database schema unless you need the additional fields. In any case, you can 
> upgrade an existing WeeWX installation that uses the old 'wview' database 
> schema to the new 'view_extended' database schema by following the 
> instructions at the Switching to the new wview_extended schema 
> 
>  
> wiki page.
>
> I would suggest you just copy your old WeeWX database to your new install 
> and if required later update to the 'wview_extended' database schema.
>
> Gary
> On Saturday 9 March 2024 at 07:09:23 UTC+10 ott...@googlemail.com wrote:
>
>> Dear community,
>> I try to import the database of my old weewx installation to the new 
>> system (newly installed + new hardware) by exporting CSV file from the old 
>> weewx.sdb and import with weectl import onto the new.
>> The process interrupts and I receive error messages as long as I have 
>> NULL values in the CSV (NULL represented by comma separators without any 
>> value ",,"). When I remove the NULLs e.g. by "0" the process completes 
>> successfully.
>> Does anybody have an idea, because I do not want to fill up the NULLs 
>> with "0" because this is not accurate.
>> Thank you for support
>> JO
>> Here ist the errorlog from weectl import:
>>
>> Using database binding 'wx_binding', which is bound to database 
>> 'weewx.sdb'
>> Destination table 'archive' unit system is '0x01' (US).
>> Missing derived observations will be calculated.
>> All WeeWX UV fields will be set to None.
>> All WeeWX radiation fields will be set to None.
>> This is a dry run, imported data will not be saved to archive.
>> Starting dry run import ...
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/weeimport/weeimport.py", line 849, in 
>> map_raw_data
>> _value = float(_row[self.map[_field]['source_field']].strip())
>> ValueError: could not convert string to float: ''
>>
>> During handling of the above exception, another exception occurred:
>>
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/weectl.py", line 74, in 
>> main()
>>   File "/usr/share/weewx/weectl.py", line 66, in main
>> namespace.func(namespace)
>>   File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
>> namespace.action_func(config_dict, namespace)
>>   File "/usr/share/weewx/weectllib/import_cmd.py", line 82, in import_func
>> weectllib.import_actions.obs_import(config_dict,
>>   File "/usr/share/weewx/weectllib/import_actions.py", line 58, in 
>> obs_import
>> source_obj.run()
>>   File "/usr/share/weewx/weeimport/weeimport.py", line 405, in run
>> _mapped_data = self.map_raw_data(_raw_data, self.archive_unit_sys)
>>   File "/usr/share/weewx/weeimport/weeimport.py", line 897, in 
>> map_raw_data
>> self.map[_field]['unit'] == 'degree_compass':
>>   File "/usr/lib/python3/dist-packages/configobj.py", line 554, in 
>> __getitem__
>> val = dict.__getitem__(self, key)
>> KeyError: 'unit'
>>
>

-- 
You received this message because you are 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/48cb62a2-dc8a-4887-acd8-80f525a22a0an%40googlegroups.com.

[weewx-user] Weectl import

['J O' via weewx-user]

Dear community,
I try to import the database of my old weewx installation to the new system 
(newly installed + new hardware) by exporting CSV file from the old 
weewx.sdb and import with weectl import onto the new.
The process interrupts and I receive error messages as long as I have NULL 
values in the CSV (NULL represented by comma separators without any value 
",,"). When I remove the NULLs e.g. by "0" the process completes 
successfully.
Does anybody have an idea, because I do not want to fill up the NULLs with 
"0" because this is not accurate.
Thank you for support
JO
Here ist the errorlog from weectl import:

Using database binding 'wx_binding', which is bound to database 'weewx.sdb'
Destination table 'archive' unit system is '0x01' (US).
Missing derived observations will be calculated.
All WeeWX UV fields will be set to None.
All WeeWX radiation fields will be set to None.
This is a dry run, imported data will not be saved to archive.
Starting dry run import ...
Traceback (most recent call last):
  File "/usr/share/weewx/weeimport/weeimport.py", line 849, in map_raw_data
_value = float(_row[self.map[_field]['source_field']].strip())
ValueError: could not convert string to float: ''

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/share/weewx/weectl.py", line 74, in 
main()
  File "/usr/share/weewx/weectl.py", line 66, in main
namespace.func(namespace)
  File "/usr/share/weewx/weectllib/__init__.py", line 121, in dispatch
namespace.action_func(config_dict, namespace)
  File "/usr/share/weewx/weectllib/import_cmd.py", line 82, in import_func
weectllib.import_actions.obs_import(config_dict,
  File "/usr/share/weewx/weectllib/import_actions.py", line 58, in 
obs_import
source_obj.run()
  File "/usr/share/weewx/weeimport/weeimport.py", line 405, in run
_mapped_data = self.map_raw_data(_raw_data, self.archive_unit_sys)
  File "/usr/share/weewx/weeimport/weeimport.py", line 897, in map_raw_data
self.map[_field]['unit'] == 'degree_compass':
  File "/usr/lib/python3/dist-packages/configobj.py", line 554, in 
__getitem__
val = dict.__getitem__(self, key)
KeyError: 'unit'

-- 
You received this message because you are 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/c8668eb4-d0ad-4d92-98ed-e707d6b43025n%40googlegroups.com.

[weewx-user] Re: Failed publish report by weewx-owm

[Tomasz J]

weewx ecowitt gw2000

sobota, 24 lutego 2024 o 02:15:48 UTC+1 vince napisał(a):

> Which precise driver are you using ? 
>
>
> On Friday, February 23, 2024 at 1:37:42 PM UTC-8 Tomasz J wrote:
>
>> Hi
>> Anyone had a similar problem? 
>>
>> *ERROR weewx.restx: OWM: Failed to publish record 2024-02-23 21:10:00 CET 
>> (1708719000): Failed upload after 3 tries*
>>
>> WeeWX works without any problems, no errors, weewx.conf owm data 
>> generated yesterday 
>
>

-- 
You received this message because you are 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/85f3c0c1-d182-4a04-b2ce-76b5af5ea924n%40googlegroups.com.

[weewx-user] Failed publish report by weewx-owm

[Tomasz J]

 Hi
Anyone had a similar problem? 

*ERROR weewx.restx: OWM: Failed to publish record 2024-02-23 21:10:00 CET 
(1708719000): Failed upload after 3 tries*

WeeWX works without any problems, no errors, weewx.conf owm data generated 
yesterday 

-- 
You received this message because you are 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/35cbed7a-8066-4697-a5d2-fcb82e06ce2en%40googlegroups.com.

Re: [weewx-user] Edit index after update

[J Jones]

I hadn't updated the skins in a long time. It might have just been a really 
old one. Figured I'd ask just incase of a typo. I've been using the seasons 
skin since the beginning.

On Sunday, May 1, 2022 at 5:47:58 PM UTC-5 tke...@gmail.com wrote:

> It's been dayUV, etc., since we parameterized the plots. However, some of 
> the other skins use dayuv. Perhaps they got mixed up?
>
> On Sun, May 1, 2022 at 7:49 AM J Jones  wrote:
>
>> I updated a few days ago and had to edit the  index.html.tmpl to get the 
>> UV images to update. Just wondering if it was a typo or if something 
>> changed. I updated to 4.8.0 and installed the new skins package because I 
>> was missing most of the current conditions. 
>>
>> I changed - dayuv.png to dayUV.png
>> Same for week, month, and year.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/46bd49f0-80b1-41e5-a691-ce6c85929a72n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/46bd49f0-80b1-41e5-a691-ce6c85929a72n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2032d547-a697-4f68-9374-ce4163296758n%40googlegroups.com.

[weewx-user] Edit index after update

[J Jones]

I updated a few days ago and had to edit the  index.html.tmpl to get the UV 
images to update. Just wondering if it was a typo or if something changed. 
I updated to 4.8.0 and installed the new skins package because I was 
missing most of the current conditions. 

I changed - dayuv.png to dayUV.png
Same for week, month, and year.

-- 
You received this message because you are 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/46bd49f0-80b1-41e5-a691-ce6c85929a72n%40googlegroups.com.

Re: [weewx-user] Wind Chill/Heat index

[J Jones]

I guess I'm just not used to the new format. It shows a chill on the left 
of 25 and  the graph shows roughly 35.

On Sunday, December 19, 2021 at 5:11:51 PM UTC-6 tke...@gmail.com wrote:

> But, you didn't have any wind! It's the wind that counts, not wind gusts. 
> Your wind was less than 2 mph. Wind chill doesn't kick in until the wind is 
> greater than 3 mph.
>
> https://www.weather.gov/safety/cold-wind-chill-chart
>
> On Sun, Dec 19, 2021 at 1:47 PM J Jones  wrote:
>
>>
>> Hi it's me again. It doesn't look like wind chill is on the graph. We had 
>> a low wind chill of 25 today and its not showing on graph.
>>
>>
>> On Tuesday, November 30, 2021 at 4:53:04 PM UTC-6 J Jones wrote:
>>
>>> Thanks! it hasn't been that cold here since the beginning of the year. I 
>>> was thinking they were reversed.
>>>
>>> On Sunday, November 28, 2021 at 7:50:11 AM UTC-6 tke...@gmail.com wrote:
>>>
>>>> I would also call your attention to option "algorithm". It allows you 
>>>> to use the "old" algorithm, which many people prefer (including myself).
>>>>
>>>> http://www.weewx.com/docs/usersguide.htm#[[[heatindex]]]
>>>>
>>>> [StdWXCalculate]
>>>>   [[WXXTypes]]
>>>> [[[heatindex]]]
>>>>   algorithm = old
>>>>
>>>>
>>>>
>>>> On Sat, Nov 27, 2021 at 8:57 AM p q  wrote:
>>>>
>>>>> see discussion here: https://github.com/weewx/weewx/issues/601 
>>>>>
>>>>> On Sat, Nov 27, 2021 at 8:33 AM J Jones  wrote:
>>>>>
>>>>>> I was just wondering if the wind chill is working correctly. I have 
>>>>>> never had heat index lower than wind chill.
>>>>>> Version 4.5.1
>>>>>>
>>>>>> [image: Screenshot 2021-11-27 103015.jpg]
>>>>>>
>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "weewx-user" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>> send an email to weewx-user+...@googlegroups.com.
>>>>>> To view this discussion on the web visit 
>>>>>> https://groups.google.com/d/msgid/weewx-user/82282faa-f271-4e4c-a2c1-4496c2e5e18en%40googlegroups.com
>>>>>>  
>>>>>> <https://groups.google.com/d/msgid/weewx-user/82282faa-f271-4e4c-a2c1-4496c2e5e18en%40googlegroups.com?utm_medium=email_source=footer>
>>>>>> .
>>>>>>
>>>>>
>>>>>
>>>>> -- 
>>>>> Peter Quinn
>>>>> (415)794-2264 <(415)%20794-2264>
>>>>>
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google 
>>>>> Groups "weewx-user" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>> an email to weewx-user+...@googlegroups.com.
>>>>>
>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/weewx-user/CAA1SM22276t3Ec3apSYXJxSb9Fxbv_xoKJM_Wubr_d3VQ0gJqg%40mail.gmail.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/weewx-user/CAA1SM22276t3Ec3apSYXJxSb9Fxbv_xoKJM_Wubr_d3VQ0gJqg%40mail.gmail.com?utm_medium=email_source=footer>
>>>>> .
>>>>>
>>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/9e32807e-95bf-4e30-bfb9-6134da201c12n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/9e32807e-95bf-4e30-bfb9-6134da201c12n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/52cf797d-3812-499d-9f4a-117093323ff6n%40googlegroups.com.

Re: [weewx-user] Wind Chill/Heat index

[J Jones]

Thanks! it hasn't been that cold here since the beginning of the year. I 
was thinking they were reversed.

On Sunday, November 28, 2021 at 7:50:11 AM UTC-6 tke...@gmail.com wrote:

> I would also call your attention to option "algorithm". It allows you to 
> use the "old" algorithm, which many people prefer (including myself).
>
> http://www.weewx.com/docs/usersguide.htm#[[[heatindex]]]
>
> [StdWXCalculate]
>   [[WXXTypes]]
> [[[heatindex]]]
>   algorithm = old
>
>
>
> On Sat, Nov 27, 2021 at 8:57 AM p q  wrote:
>
>> see discussion here: https://github.com/weewx/weewx/issues/601 
>>
>> On Sat, Nov 27, 2021 at 8:33 AM J Jones  wrote:
>>
>>> I was just wondering if the wind chill is working correctly. I have 
>>> never had heat index lower than wind chill.
>>> Version 4.5.1
>>>
>>> [image: Screenshot 2021-11-27 103015.jpg]
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/82282faa-f271-4e4c-a2c1-4496c2e5e18en%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/82282faa-f271-4e4c-a2c1-4496c2e5e18en%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> -- 
>> Peter Quinn
>> (415)794-2264 <(415)%20794-2264>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/CAA1SM22276t3Ec3apSYXJxSb9Fxbv_xoKJM_Wubr_d3VQ0gJqg%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/CAA1SM22276t3Ec3apSYXJxSb9Fxbv_xoKJM_Wubr_d3VQ0gJqg%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7c8018c0-54ae-45cc-8d3a-e2a0f912adf4n%40googlegroups.com.

[weewx-user] Wind Chill/Heat index

[J Jones]

I was just wondering if the wind chill is working correctly. I have never 
had heat index lower than wind chill.
Version 4.5.1

[image: Screenshot 2021-11-27 103015.jpg]

-- 
You received this message because you are 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/82282faa-f271-4e4c-a2c1-4496c2e5e18en%40googlegroups.com.

Re: [weewx-user] Re: weewx stopped for no apparent reason

[Christopher J. Shaker]

Jay:

I tried 'sudo service weewx restart', and it did NOT fix the problem. I 
rebooted the machine, and it worked
great. Hopefully, now that I've got debug enabled, if it happens again, 
I can debug it.


Thank you for sharing your WMII driver for Python 3!

Chris Shaker

On 6/9/2021 11:20 AM, Jay Jaeger wrote:
@Chris:  Version 3 weewx with my wmII was rock solid.  I didn't run 
the wmII more than a day under version 4, so I can't speak to that.  I 
had no issues restarting weewx - didn't need a reboot.


NOTE:  systemd behavior, being what it is, if a service crashes, it 
still is not STOPPED, and it won't start a service that it thinks is 
still running.  Instead, you have to stop it (service weewx stop) 
before you can start it (or, you could do a "service weewx restart" 
which does a stop first.)


JRJ

On Wednesday, June 9, 2021 at 12:09:08 PM UTC-5 cjsh...@gmail.com wrote:

JRJ:

Are you saying that weewx stopped generating reports? My weewx
stopped generating reports, with no error messages, at 4:00 AM.
Restarting service weewx did not fix it. Rebooting my raspberry pi
DID fix it. So, I added a crontab entry to reboot my raspberry pi
each morning:
5 4 * * * /sbin/shutdown -r now

So far, it has not happened again. I'm using a WMII, with serial
port connection, using Python3 and the latest version of the
driver from JayJaeger

Chris Shaker

On Wednesday, June 9, 2021 at 5:46:52 AM UTC-7 cub...@gmail.com wrote:

@michael:  It should not be related to the SCP upload, which
continues even after weewx has gone "night night".  It is
running from a cron, not under weewx.  It merely copies the
generated HTML/graphics up to another machine.  It runs  every
17 minutes.  If it were, say, locking up a file and causing a
report to fail there ought to be a message from Python about
that, and there are no such messages.  This same SCP was
running with weewx version 3 for many months without issues -
originally every 15 minutes, I changed it from 15 to 17
yesterday to put it out of sync from the report generation a
bit it after the second failure, just in case.

[It did occur to me to add a little mod akin to the RSYNC
present in weewx itself, or to cut over to using then RSYNC
under weewx after the rest of this gets straightened out.]

I also verified that all of the files and directories are
owned by and have the same group as the weewx process, and
they are, so it should not be an issue of file permissions
during report generation, either.

Regarding the dev release driver, sure, I'll give that a try,
and turn on more logging later today.

JRJ

On Wednesday, June 9, 2021 at 1:40:52 AM UTC-5
michael.s...@gmail.com wrote:

Nah, the logging level change doesn't matter, I've
published a dev release a few days ago making exactly that
change.

I'd suggest you to try the new driver version anyway since
I also made some changes regarding the HTTP interaction
with the WLL. You should also enable debug logging so we
get a more exhaustive look into what's going on.

My suspicion is that something's wrong with the report
generation or the SCP upload. Was the last iteration of
the report actually uploaded correctly?



vince schrieb am Mittwoch, 9. Juni 2021 um 06:10:01 UTC+2:

On Tuesday, June 8, 2021 at 12:43:44 PM UTC-7
cub...@gmail.com wrote:

(Note: I did "tweaked" the WLL driver code to
suppress the "Emitting poll/(broadcast) messages
by changing those two log calls to "log.debug"). 



I'd suggest running the unaltered driver and
especially in this case so you get the maximum logging
so the author can help you.

If you start changing his code, eventually it'll be
"you changed it, you own the results good or bad" when
he can't recreate the issue because your code has
diverged from the authoritative version.

--
You received this message because you are subscribed to a topic in the 
Google Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/GYnuZbTdhuM/unsubscribe 
.
To unsubscribe from this group and all its topics, 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/868ff588-eed6-4cee-b94b-61143e0cfa85n%40googlegroups.com 

Re: [weewx-user] Live weather on iOS

[Martin J]

Thank you for producing this app and allowing the specification of topic.  
It works fine for me, for a number of variables.  However, I use METRICWX 
in weewx, with rain in mm and wind in m/s.  We haven't had any rain yet to 
test this, but my wind and gust speeds are both permanently zero.  Do you 
have any plans to support METRICWX or to allow choice of units by some 
other means?  Also, is there any way of displaying my radiation and UV data?

Thanks.

On Wednesday, 9 December 2020 at 16:39:23 UTC bell...@gmail.com wrote:

> I did. Since then I have tried the following.
> 1. Publish as metric and change the application configuration back to 
> metric.
> 2. Only publish outTemp_C and configure only an ‘Outside Temperature’ 
> gauge.
> I’m sure I’m missing something obvious. I’ll keep experimenting. 
> rich
>
> On Wednesday, 9 December 2020 at 05:54:49 UTC-5 sama...@gmail.com wrote:
>
>> In the application configuration have you turned your station units to 
>> imperial? (I think they default to metric) 
>>
>> That would make a difference between looking for example between 
>> heatindex_F and headindex_C which is part of the whole topic string
>>
>>
>> Thanks
>>
>> On Tue, Dec 8, 2020 at 7:44 PM bell...@gmail.com  
>> wrote:
>>
>>>
>>> Interesting. The first time I clicked on the link it only installed 
>>> TestFlight.  But I digress. I must be doing something wrong. I get the 
>>> green dot, so I think I am connected. I entered weather/individual as my 
>>> topic.
>>> Here is some output from some test code
>>> Connected with result code 0
>>> Connected flags {'session present': 0}
>>> Subscribing to weather/individual/# has a mid 1 and rc 0
>>> Subscribed to topic mid: 1 is size 1 has a QOS of 0
>>> topic: weather/individual/monthET
>>> payload: b'"0.11"'
>>> topic: weather/individual/heatindex_F
>>> payload: b'"22.5"'
>>> topic: weather/individual/outHumidity
>>> payload: b'"86.0"'
>>> topic: weather/individual/dayET
>>> payload: b'"0.006"'
>>> topic: weather/individual/maxSolarRad_Wpm2
>>> payload: b'"0.0"'
>>> topic: weather/individual/consBatteryVoltage_volt
>>> payload: b'"4.54"'
>>> topic: weather/individual/monthRain_in
>>> payload: b'"0.14"'
>>> topic: weather/individual/insideAlarm
>>> payload: b'"0.0"'
>>> topic: weather/individual/barometer_inHg
>>> payload: b'"29.282"'
>>> topic: weather/individual/dayRain_in
>>> payload: b'"0.0"'
>>> topic: weather/individual/stormRain_in
>>> payload: b'"0.0"'
>>> topic: weather/individual/sunrise
>>> payload: b'"1607429520.0"'
>>> topic: weather/individual/windchill_F
>>> payload: b'"22.5"'
>>> topic: weather/individual/dewpoint_F
>>> payload: b'"18.9577377882"'
>>> topic: weather/individual/outsideAlarm1
>>> payload: b'"0.0"'
>>> topic: weather/individual/soilLeafAlarm2
>>> payload: b'"0.0"'
>>> topic: weather/individual/outsideAlarm2
>>> payload: b'"0.0"'
>>> topic: weather/individual/radiation_Wpm2
>>> payload: b'"0.0"'
>>> topic: weather/individual/forecastRule
>>> payload: b'"192.0"'
>>> topic: weather/individual/rainAlarm
>>> payload: b'"0.0"'
>>> topic: weather/individual/inTemp_F
>>> payload: b'"67.4"'
>>> topic: weather/individual/inHumidity
>>> payload: b'"38.0"'
>>> topic: weather/individual/windSpeed10_mph
>>> payload: b'"0.0"'
>>> topic: weather/individual/yearRain_in
>>> payload: b'"23.37"'
>>> topic: weather/individual/inDewpoint_F
>>> payload: b'"40.9048059523 <(904)%20805-9523>"'
>>> topic: weather/individual/extraAlarm1
>>> payload: b'"0.0"'
>>> topic: weather/individual/extraAlarm2
>>> payload: b'"0.0"'
>>> topic: weather/individual/extraAlarm3
>>> payload: b'"0.0"'
>>> topic: weather/individual/extraAlarm4
>>> payload: b'"0.0"'
>>> topic: weather/individual/extraAlarm5
>>> payload: b'"0.0"'
>>> topic: weather/individual/extraAlarm6
>>> payload: b'"0.0"'
>>> topic: weather/individual/extraAlarm7
>>> payload: b'"0.0"'
>>> topic: weather/individual/extraAlarm8
>>> payload: b'"0.0"'
>>> topic: weather/individual/rainRate_inch_per_hour
>>> payload: b'"0.0"'
>>> topic: weather/individual/rain_in
>>> payload: b'"0.0"'
>>> topic: weather/individual/humidex_F
>>> payload: b'"22.5"'
>>> topic: weather/individual/forecastIcon
>>> payload: b'"18.0"'
>>> topic: weather/individual/pressure_inHg
>>> payload: b'"28.7311013367"'
>>> topic: weather/individual/soilLeafAlarm4
>>> payload: b'"0.0"'
>>> topic: weather/individual/trendIcon
>>> payload: b'"0.0"'
>>> topic: weather/individual/altimeter_inHg
>>> payload: b'"29.2387383925"'
>>> topic: weather/individual/soilLeafAlarm3
>>> payload: b'"0.0"'
>>> topic: weather/individual/usUnits
>>> payload: b'"1.0"'
>>> topic: weather/individual/soilLeafAlarm1
>>> payload: b'"0.0"'
>>> topic: weather/individual/leafWet4
>>> payload: b'"0.0"'
>>> topic: weather/individual/yearET
>>> payload: b'"25.01"'
>>> topic: weather/individual/txBatteryStatus
>>> payload: b'"0.0"'
>>> topic: weather/individual/appTemp_F
>>> payload: b'"17.4069618021 <(406)%20961-8021>"'
>>> topic: weather/individual/UV
>>> payload: b'"0.0"'

Re: [weewx-user] Live weather on iOS

[Martin J]

Thatnk you for producing this app and allowing the specification of topic.  
It works fine for me, for a number of variables.  However, I use METRICWX 
in weewx, with rain in mm and wind in m/s.  We haven't had any rain yet to 
test this, but my wind and gust speeds are both permanently zero.  Do you 
have any plans to support METRICWX or to allow choice of units by some 
other means?  Also, is there any way of displaying my radiation and UV data?

Thanks.
On Wednesday, 9 December 2020 at 16:39:23 UTC bell...@gmail.com wrote:

> I did. Since then I have tried the following.
> 1. Publish as metric and change the application configuration back to 
> metric.
> 2. Only publish outTemp_C and configure only an ‘Outside Temperature’ 
> gauge.
> I’m sure I’m missing something obvious. I’ll keep experimenting. 
> rich
>
> On Wednesday, 9 December 2020 at 05:54:49 UTC-5 sama...@gmail.com wrote:
>
>> In the application configuration have you turned your station units to 
>> imperial? (I think they default to metric) 
>>
>> That would make a difference between looking for example between 
>> heatindex_F and headindex_C which is part of the whole topic string
>>
>>
>> Thanks
>>
>> On Tue, Dec 8, 2020 at 7:44 PM bell...@gmail.com  
>> wrote:
>>
>>>
>>> Interesting. The first time I clicked on the link it only installed 
>>> TestFlight.  But I digress. I must be doing something wrong. I get the 
>>> green dot, so I think I am connected. I entered weather/individual as my 
>>> topic.
>>> Here is some output from some test code
>>> Connected with result code 0
>>> Connected flags {'session present': 0}
>>> Subscribing to weather/individual/# has a mid 1 and rc 0
>>> Subscribed to topic mid: 1 is size 1 has a QOS of 0
>>> topic: weather/individual/monthET
>>> payload: b'"0.11"'
>>> topic: weather/individual/heatindex_F
>>> payload: b'"22.5"'
>>> topic: weather/individual/outHumidity
>>> payload: b'"86.0"'
>>> topic: weather/individual/dayET
>>> payload: b'"0.006"'
>>> topic: weather/individual/maxSolarRad_Wpm2
>>> payload: b'"0.0"'
>>> topic: weather/individual/consBatteryVoltage_volt
>>> payload: b'"4.54"'
>>> topic: weather/individual/monthRain_in
>>> payload: b'"0.14"'
>>> topic: weather/individual/insideAlarm
>>> payload: b'"0.0"'
>>> topic: weather/individual/barometer_inHg
>>> payload: b'"29.282"'
>>> topic: weather/individual/dayRain_in
>>> payload: b'"0.0"'
>>> topic: weather/individual/stormRain_in
>>> payload: b'"0.0"'
>>> topic: weather/individual/sunrise
>>> payload: b'"1607429520.0"'
>>> topic: weather/individual/windchill_F
>>> payload: b'"22.5"'
>>> topic: weather/individual/dewpoint_F
>>> payload: b'"18.9577377882"'
>>> topic: weather/individual/outsideAlarm1
>>> payload: b'"0.0"'
>>> topic: weather/individual/soilLeafAlarm2
>>> payload: b'"0.0"'
>>> topic: weather/individual/outsideAlarm2
>>> payload: b'"0.0"'
>>> topic: weather/individual/radiation_Wpm2
>>> payload: b'"0.0"'
>>> topic: weather/individual/forecastRule
>>> payload: b'"192.0"'
>>> topic: weather/individual/rainAlarm
>>> payload: b'"0.0"'
>>> topic: weather/individual/inTemp_F
>>> payload: b'"67.4"'
>>> topic: weather/individual/inHumidity
>>> payload: b'"38.0"'
>>> topic: weather/individual/windSpeed10_mph
>>> payload: b'"0.0"'
>>> topic: weather/individual/yearRain_in
>>> payload: b'"23.37"'
>>> topic: weather/individual/inDewpoint_F
>>> payload: b'"40.9048059523 <(904)%20805-9523>"'
>>> topic: weather/individual/extraAlarm1
>>> payload: b'"0.0"'
>>> topic: weather/individual/extraAlarm2
>>> payload: b'"0.0"'
>>> topic: weather/individual/extraAlarm3
>>> payload: b'"0.0"'
>>> topic: weather/individual/extraAlarm4
>>> payload: b'"0.0"'
>>> topic: weather/individual/extraAlarm5
>>> payload: b'"0.0"'
>>> topic: weather/individual/extraAlarm6
>>> payload: b'"0.0"'
>>> topic: weather/individual/extraAlarm7
>>> payload: b'"0.0"'
>>> topic: weather/individual/extraAlarm8
>>> payload: b'"0.0"'
>>> topic: weather/individual/rainRate_inch_per_hour
>>> payload: b'"0.0"'
>>> topic: weather/individual/rain_in
>>> payload: b'"0.0"'
>>> topic: weather/individual/humidex_F
>>> payload: b'"22.5"'
>>> topic: weather/individual/forecastIcon
>>> payload: b'"18.0"'
>>> topic: weather/individual/pressure_inHg
>>> payload: b'"28.7311013367"'
>>> topic: weather/individual/soilLeafAlarm4
>>> payload: b'"0.0"'
>>> topic: weather/individual/trendIcon
>>> payload: b'"0.0"'
>>> topic: weather/individual/altimeter_inHg
>>> payload: b'"29.2387383925"'
>>> topic: weather/individual/soilLeafAlarm3
>>> payload: b'"0.0"'
>>> topic: weather/individual/usUnits
>>> payload: b'"1.0"'
>>> topic: weather/individual/soilLeafAlarm1
>>> payload: b'"0.0"'
>>> topic: weather/individual/leafWet4
>>> payload: b'"0.0"'
>>> topic: weather/individual/yearET
>>> payload: b'"25.01"'
>>> topic: weather/individual/txBatteryStatus
>>> payload: b'"0.0"'
>>> topic: weather/individual/appTemp_F
>>> payload: b'"17.4069618021 <(406)%20961-8021>"'
>>> topic: weather/individual/UV
>>> payload: b'"0.0"'

[weewx-user] Re: weewx-Weather34 easyW34skinSetup runs Other PHP Run, index.php Does Not

[J D]

Hi,
Open an issue on the repository for w34 template and post the file 
archivedata.php which will be found in the weather34 directory


On Friday, September 11, 2020 at 6:56:52 PM UTC-7, G Hammer wrote:
>
> Running Pop!_OS PHP 7.4.3 Apache 2.4 Python 3.8.2 setup.py method.
>
> I have an identical test server and installed weewx and this template 
> there a few days ago. Working well.
> So, today I installed to my online server.
> Does not run.
> I have checked and double checked the install, the permissions, etc. I'm 
> probably blind to whatever the issue is by now.
>
> I can run any php from the folder the template is installed in, except for 
> the index.php.
> The easyW34skinSetup.php runs and writes the settings file.
> WeeWX is creating the w34realtime.txt
>
>
> I get 500 error when I try the site. weather.ghammer.net or 
> weather.ghammer.net/index.php
> Apache error logs show nothing.
> Apache access logs only show that a 500 happened.
> I have monitored the syslog with no hints.
>
> I can use these URLs that are served from the same folder to get info on 
> the system/software installed.
>
> https://weather.ghammer.net/check-fetch-times.php
>
> This one is very detailed on the entire apache and PHP environment.
> https://weather.ghammer.net/php_test.php
>
> https://weather.ghammer.net/test.php
>
> Then there is the setup page. Of course, you don't have a password, but it 
> shows that it works.
>
> https://weather.ghammer.net/easyW34skinSetup.php
>
> Any ideas?
>
>

-- 
You received this message because you are 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/2dbc4609-fa78-4132-afa7-1cb4f2f17451o%40googlegroups.com.

[weewx-user] Re: Images

[J Jones]

This worked. Thanks for the help. I was also able to rearrange some if the 
images the way I like them.

On Friday, September 4, 2020 at 1:27:19 PM UTC-5 J Jones wrote:

> Thank you. I was in the directory but only saw the skins.conf file. Giving 
> it a shot now.
>
> On Thursday, September 3, 2020 at 8:19:24 PM UTC-5 gjr80 wrote:
>
>> I will assume you are referring to the Seasons skin. You need to edit 
>> /etc/weewx/skins/Seasons/index.html.tmpl (or it maybe 
>> /home/weewx/skins/Seasons/index.html.tmpl depending on your WeeWX install 
>> type) and:
>>
>> 1. locate and delete the following lines (circa line 61):
>>
>> #if $day.inTemp.has_data
>> 
>> #end if
>>
>> 2.continue searching through the file and locate and delete the 
>> corresponding week, month and year lines. The 'week' lines look like:
>>
>> #if $week.inTemp.has_data
>> 
>> #end if
>>
>> 3. repeat steps 1 to 2 but this time for inHumidity. The 'day' inHumidity 
>> lines are:
>>
>> #if $day.inHumidity.has_data
>> 
>> #end if
>>
>> 4. save index.html.tmpl and on the next report cycle it will be 
>> regenerated without the inTemp and inHumidity plots.
>>
>> Whilst index.html will no longer display the plots WeeWX will continue 
>> generating them (or attempting to generate them). If you want to stop WeeWX 
>> generating the plots you need to edit /etc/weewx/skins/Seasons/skin.conf 
>> (or /home/weewx/skins/Seasons/skin.conf) and locate the [ImageGenerator] 
>> stanza. Then under [[day_images]], [[week_images]], [[month_images]] and 
>> [[year_images]]delete the [[[xxxtempin]]] and [[[xxxhumin]]] stanzas in 
>> toto where xxx is day, week, month and year. Save skin.conf and WeeWX will 
>> no longer attempt to generate the inTemp and inHumidity plots.
>>
>> Gary
>>
>> On Friday, 4 September 2020 at 10:50:07 UTC+10 J Jones wrote:
>>
>>> I would like to remove these two images from Day, Week, Month, and Year. 
>>> As you can see the inside humidity doesn't work.
>>>
>>> On Thursday, September 3, 2020 at 3:55:00 PM UTC-5 gjr80 wrote:
>>>
>>>> Hi,
>>>>
>>>> Remove from what? Remove from the Seasons skin or something else?
>>>>
>>>> Gary
>>>>
>>>> On Friday, 4 September 2020 at 06:44:00 UTC+10 J Jones wrote:
>>>>
>>>>> Can someone help me remove a  few temp images? I would like to remove 
>>>>> the inside temp and humidity. The humility one doesn't work anyways i  
>>>>> just 
>>>>> get an error icon.
>>>>
>>>>

-- 
You received this message because you are 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/b658c0ec-8ca0-4021-8ccb-a833a8312387n%40googlegroups.com.

[weewx-user] Re: Images

[J Jones]

Thank you. I was in the directory but only saw the skins.conf file. Giving 
it a shot now.

On Thursday, September 3, 2020 at 8:19:24 PM UTC-5 gjr80 wrote:

> I will assume you are referring to the Seasons skin. You need to edit 
> /etc/weewx/skins/Seasons/index.html.tmpl (or it maybe 
> /home/weewx/skins/Seasons/index.html.tmpl depending on your WeeWX install 
> type) and:
>
> 1. locate and delete the following lines (circa line 61):
>
> #if $day.inTemp.has_data
> 
> #end if
>
> 2.continue searching through the file and locate and delete the 
> corresponding week, month and year lines. The 'week' lines look like:
>
> #if $week.inTemp.has_data
> 
> #end if
>
> 3. repeat steps 1 to 2 but this time for inHumidity. The 'day' inHumidity 
> lines are:
>
> #if $day.inHumidity.has_data
> 
> #end if
>
> 4. save index.html.tmpl and on the next report cycle it will be 
> regenerated without the inTemp and inHumidity plots.
>
> Whilst index.html will no longer display the plots WeeWX will continue 
> generating them (or attempting to generate them). If you want to stop WeeWX 
> generating the plots you need to edit /etc/weewx/skins/Seasons/skin.conf 
> (or /home/weewx/skins/Seasons/skin.conf) and locate the [ImageGenerator] 
> stanza. Then under [[day_images]], [[week_images]], [[month_images]] and 
> [[year_images]]delete the [[[xxxtempin]]] and [[[xxxhumin]]] stanzas in 
> toto where xxx is day, week, month and year. Save skin.conf and WeeWX will 
> no longer attempt to generate the inTemp and inHumidity plots.
>
> Gary
>
> On Friday, 4 September 2020 at 10:50:07 UTC+10 J Jones wrote:
>
>> I would like to remove these two images from Day, Week, Month, and Year. 
>> As you can see the inside humidity doesn't work.
>>
>> On Thursday, September 3, 2020 at 3:55:00 PM UTC-5 gjr80 wrote:
>>
>>> Hi,
>>>
>>> Remove from what? Remove from the Seasons skin or something else?
>>>
>>> Gary
>>>
>>> On Friday, 4 September 2020 at 06:44:00 UTC+10 J Jones wrote:
>>>
>>>> Can someone help me remove a  few temp images? I would like to remove 
>>>> the inside temp and humidity. The humility one doesn't work anyways i  
>>>> just 
>>>> get an error icon.
>>>
>>>

-- 
You received this message because you are 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/8232e1f7-fc1f-4101-aaa4-d54b383ae5f0n%40googlegroups.com.

[weewx-user] Re: Images

[J Jones]

I would like to remove these two images from Day, Week, Month, and Year. As 
you can see the inside humidity doesn't work.

On Thursday, September 3, 2020 at 3:55:00 PM UTC-5 gjr80 wrote:

> Hi,
>
> Remove from what? Remove from the Seasons skin or something else?
>
> Gary
>
> On Friday, 4 September 2020 at 06:44:00 UTC+10 J Jones wrote:
>
>> Can someone help me remove a  few temp images? I would like to remove the 
>> inside temp and humidity. The humility one doesn't work anyways i  just get 
>> an error icon.
>
>

-- 
You received this message because you are 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/9a2cc866-a9ab-4d45-9679-5632f3f760d1n%40googlegroups.com.

[weewx-user] Images

[J Jones]

Can someone help me remove a  few temp images? I would like to remove the 
inside temp and humidity. The humility one doesn't work anyways i  just get 
an error icon.

-- 
You received this message because you are 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/62118ca4-f1f6-4524-92ce-963cf0b9487cn%40googlegroups.com.

[weewx-user] Re: Module Error

[J D]

This is not a weewx issue or a python path issue. The file is in the 
correct location, but the troubleshooting guide must be done to find out 
why there is an error.

On Tuesday, August 11, 2020 at 3:27:16 PM UTC-7, Mauro De Lauretis wrote:
>
> Hi all!
> I'm running the last version of weewx with python3 on my Raspberry Pi.
> As skin I use the weather34 weewx version (
> https://github.com/steepleian/weewx-Weather34)
>
> There are also incorporated highcharts that are created live from the 
> database when selecting on the website.
> However, a part of them won't work with my setup and this Is the message I 
> get:
>
>
> root@raspberrypi:~# sudo python3 
> /var/www/html/weewx/weather34/w34highcharts/wee_reports_w34
>
> Traceback (most recent call last):
>
>   File "/var/www/html/weewx/weather34/w34highcharts/wee_reports_w34", line 
> 8, in 
>
> import weewx
>
> ModuleNotFoundError: No module named 'weewx'
>
>
>
>
> Do you have any ideas what the issue could be?
>
>
> Thanks
>
>
> Mauro
>

-- 
You received this message because you are 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/ca782342-2160-4630-aee3-438d53a85c50o%40googlegroups.com.

[weewx-user] Re: Module Error

[J D]

Need a lot more info to figure out what is wrong. The repository for 
weather34 template has a troubleshooting guide.
Collect the required info and open an issue on the repository and post the 
info.

On Tuesday, August 11, 2020 at 3:27:16 PM UTC-7, Mauro De Lauretis wrote:
>
> Hi all!
> I'm running the last version of weewx with python3 on my Raspberry Pi.
> As skin I use the weather34 weewx version (
> https://github.com/steepleian/weewx-Weather34)
>
> There are also incorporated highcharts that are created live from the 
> database when selecting on the website.
> However, a part of them won't work with my setup and this Is the message I 
> get:
>
>
> root@raspberrypi:~# sudo python3 
> /var/www/html/weewx/weather34/w34highcharts/wee_reports_w34
>
> Traceback (most recent call last):
>
>   File "/var/www/html/weewx/weather34/w34highcharts/wee_reports_w34", line 
> 8, in 
>
> import weewx
>
> ModuleNotFoundError: No module named 'weewx'
>
>
>
>
> Do you have any ideas what the issue could be?
>
>
> Thanks
>
>
> Mauro
>

-- 
You received this message because you are 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/bb73aef6-f6ca-4b93-99a2-29ab9d6c9c29o%40googlegroups.com.

[weewx-user] Re: Converting data from HW that is in metric to display in US

[J D]

To disable weather34 webservices you can do either of the following

In weewx.conf
set filename to nothing in the following section
[Weather34WebServices]
filename = 

OR

In the weather34 directory edit file settings1.php
 set $services to nothing
$services = ;

restart weewx

On Wednesday, August 5, 2020 at 9:21:43 AM UTC-7, Randy wrote:
>
> I am new to weewx.  I have data coming in from my device is coming in as 
> metric (specifically, temp is C).  I want to display that data as US, F.  
> The default weewx skin is showing the data as metric values like 20F which 
> is actually 20C whereas it should be 68F.  Where does this conversion 
> happen or where do I chance the configuration?
>
> Thank you
> Randy 
>

-- 
You received this message because you are 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/c3617c77-8acc-43f7-a7ee-3a7802ae0854o%40googlegroups.com.

[weewx-user] Temp images

[J Jones]

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


Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/85c6a9e1-9a2f-42b4-a59c-d042ea3f94b4o%40googlegroups.com.

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

[J Jones]

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



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

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/bc75d495-0990-4d44-970a-3c6ec58a10eeo%40googlegroups.com.

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

[J Jones]

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




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

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

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

[J Jones]

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

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



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

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/bd483f00-b1e5-49ed-96f5-6559079b8c67o%40googlegroups.com.

[weewx-user] Errors during APT-GET UPDATE

[J Jones]

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d0722409-4353-4f19-8ef3-7c029acbd168o%40googlegroups.com.

[weewx-user] Re: wee_import

[J W]

This sounds correct - I have docker on Synology and Ubuntu platforms. They 
appear to implement logging in different ways.

On Tuesday, 19 May 2020 18:59:40 UTC+10, gjr80 wrote:
>
> Hi,
>
> Sounds like a problem with WeeWX logging and docker rather than a 
> wee_import problem per se. You might want to check out this thread in 
> weewx-development - 
> https://groups.google.com/d/topic/weewx-development/Xx-1k6zxwVY/discussion
>
> 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/2c43df6e-f0c9-44a1-9cd3-5153733cb68ao%40googlegroups.com.

[weewx-user] Re: weather34 !!!!NO DATA FOUND in database. Please choose another date!!!! bar_rain_week.json

[J D]

Hi,
The functionality that is not working is getting data from the weewx 
database in realtime and storing it in the json_day directory. Since you 
are hosting the template on a different machine than your weewx machine you 
must setup the remote web server section of weewx.conf called 
Weather34RemoteWebServer. If you do not have this section in your 
weewx.conf then the version of the template you are running does not 
support it. You then would need to contact Ian to get the latest version of 
the template that supports the remote web server. The is also a config 
setting in settings1.php that also needs to be setup. Finally you will need 
to have ssh keys setup between the two machines so rsync can be run. 

On Tuesday, June 16, 2020 at 2:01:31 PM UTC-7, Simon Davies wrote:
>
> *"NO DATA FOUND in database. Please choose another date 
> bar_rain_week.json"*
> I get this error each time I change the date range for rain, wind or 
> temperature charts on my weather34 site.  
> http://nobledrive.weather-station.co.uk/ 
>   
>
>
> looking in the folder .../json_day/  no files exist.  I  tried creating an 
> empty one but still the same error.
>
> I do have a weather34 site which is co-located with weewx and this works 
> fine, however the public site is  a copy using FTP and gives this error .  
>
> Any ideas what could cause this problem?
>

-- 
You received this message because you are 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/37931f8d-df82-47ec-83c4-bdc76631d53bo%40googlegroups.com.

Re: [weewx-user] Weather34 UV Index displays UV Solar Radiation

[J D]

Hi,
Are you sure UV in the loop is correct? 

Using Ian data's for UV was a 7.0 and you stated that was working 
correctly.  

Your last post has UV 753.0 That does not look correct.

On Friday, May 29, 2020 at 8:55:30 AM UTC-7, Simon Davies wrote:
>
> LOOP data looks fine
>
> LOOP:   2020-05-29 16:50:59 BST (1590767459) altimeter: 29.9018046207, 
> barometer: 29.8979821835, dateTime: 1590767459, dewpoint: 46.58, heatindex: 
> 76.1, inDewpoint: 42.3766863757, inHumidity: 33.0, inTemp: 73.22, 
> outHumidity: 35.0, outTemp: 76.1, pressure: 29.8636763587, radiation: 
> 613.9626, rain: 0.0, rainRate: 0.0, usUnits: 1, *UV: 753.0*, windchill: 
> 76.1, windDir: 143.0, windGust: 4.92127207427, windSpeed: 2.68433022233
>
>
>
> On Friday, May 29, 2020 at 4:38:54 PM UTC+1, J D wrote:
>>
>> Hi,
>> The layout looks fine. The issue is the loop data.  The UV field in the 
>> realtime data is just a copy of the "UV" field in the loop data. I would 
>> stop weewx and then run weewx at the command line and look at the loop data 
>> output.
>>
>> On Friday, May 29, 2020 at 8:27:50 AM UTC-7, Simon Davies wrote:
>>>
>>> using your data it works perfectly.  I don't know why I have a different 
>>> file layout.
>>> position 39 is cumulus version,  which is 4.0.0 in mine and 4.1.0 in 
>>> yours,  do you know if there are any changes to the layout.
>>>
>>> On Friday, May 29, 2020 at 1:40:41 PM UTC+1, steeple ian wrote:
>>>>
>>>> Hi Simon,
>>>> I have never seen that happen before. Below is my w34realtime.txt file 
>>>> content a few minutes ago. Stop WeeWX and do a quick cut and paste into 
>>>> your own file and see what happens. It should indicate where the problem 
>>>> is.
>>>>
>>>> 29/05/20 13:34:53 22.5 28 3.1 1.3 1.3 325 0.0 0.0 1020.3 NW 1 m/s C mb 
>>>> mm 25.7 -2.0 1.0 1.0 0.0 22.4 38 22.5 3.7 22.2 13:30 4.6 05:05 2.2 12:55 
>>>> 5.6 12:15 1024.5 00:05 1020.6 13:30 4.1.0 0 5.1 22.5 22.5 7.0 0.1 768 268 
>>>> 0.0 0 1 0 W 2504 m 20.1 8.7 882.8 NULL NULL NULL NULL NULL
>>>>
>>>> Thanks,
>>>> Ian
>>>>
>>>> On Fri, 29 May 2020 at 13:04, 'Simon Davies' via weewx-user <
>>>> weewx...@googlegroups.com> wrote:
>>>>
>>>>> Weather34 is displaying the Solar radiation reading instead of the UV 
>>>>> index.  Any idea how to correct this?
>>>>>
>>>>> I've installed this version a few weeks ago and its been a problem 
>>>>> since then. WX-HC20-IHVN-1.0.0 WeeWX-(4.0.0) Ambient Weather WS-1000 
>>>>> http://cawston.weather-station.co.uk/
>>>>>
>>>>> w34realtime.txt : 29/05/20 12:12:34 22.0 33 5.0 0.5 0.2 77 0.0 0.0 
>>>>> 1015.5 ENE 0 m/s C mb mm 9.3 -0.7 0.0 109.2 0.0 25.3 23 22.0 3.8 22.0 
>>>>> 12:11 
>>>>> 11.0 05:35 2.0 11:21 4.4 09:49 1017.9 00:10 1015.2 11:36 4.0.0 0 3.3 22.0 
>>>>> NULL 3054.0 NULL 630 188 0.0 0 1 0 S NULL m NULL 7.4 NULL 0
>>>>>
>>>>> 44th value is 3054.0 and is displayed as the UVI.
>>>>>
>>>>> I don't have a definition for the w34realtime.txt,  
>>>>> https://cumuluswiki.org/a/Realtime.txt has the definition for 
>>>>> "realtime.txt",  i'm unsure is this is the same.  
>>>>>
>>>>> If the definition is correct then it looks like my solar radiation is 
>>>>> in the wrong place.  Any idea how to fix.
>>>>>
>>>>> weewx config:
>>>>>
>>>>> [Weather34RealTime]
>>>>> binding = loop
>>>>> exclude_fields = rain
>>>>> filename = /var/www/html/weewx/weather34/w34realtime.txt
>>>>> unit_system = METRICWX
>>>>> "# cache_enable" = False
>>>>> cache_stale_time = 900
>>>>> cache_directory = /tmp
>>>>>
>>>>>
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google 
>>>>> Groups "weewx-user" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>> an email to weewx...@googlegroups.com.
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/weewx-user/da42a7a6-caeb-4d5f-a452-025ee9222afc%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/weewx-user/da42a7a6-caeb-4d5f-a452-025ee9222afc%40googlegroups.com?utm_medium=email_source=footer>
>>>>> .
>>>>>
>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a83f9bcb-ed69-4e81-8168-d1514fbf422c%40googlegroups.com.

Re: [weewx-user] Weather34 UV Index displays UV Solar Radiation

[J D]

Hi,
The layout looks fine. The issue is the loop data.  The UV field in the 
realtime data is just a copy of the "UV" field in the loop data. I would 
stop weewx and then run weewx at the command line and look at the loop data 
output.

On Friday, May 29, 2020 at 8:27:50 AM UTC-7, Simon Davies wrote:
>
> using your data it works perfectly.  I don't know why I have a different 
> file layout.
> position 39 is cumulus version,  which is 4.0.0 in mine and 4.1.0 in 
> yours,  do you know if there are any changes to the layout.
>
> On Friday, May 29, 2020 at 1:40:41 PM UTC+1, steeple ian wrote:
>>
>> Hi Simon,
>> I have never seen that happen before. Below is my w34realtime.txt file 
>> content a few minutes ago. Stop WeeWX and do a quick cut and paste into 
>> your own file and see what happens. It should indicate where the problem is.
>>
>> 29/05/20 13:34:53 22.5 28 3.1 1.3 1.3 325 0.0 0.0 1020.3 NW 1 m/s C mb mm 
>> 25.7 -2.0 1.0 1.0 0.0 22.4 38 22.5 3.7 22.2 13:30 4.6 05:05 2.2 12:55 5.6 
>> 12:15 1024.5 00:05 1020.6 13:30 4.1.0 0 5.1 22.5 22.5 7.0 0.1 768 268 0.0 0 
>> 1 0 W 2504 m 20.1 8.7 882.8 NULL NULL NULL NULL NULL
>>
>> Thanks,
>> Ian
>>
>> On Fri, 29 May 2020 at 13:04, 'Simon Davies' via weewx-user <
>> weewx...@googlegroups.com> wrote:
>>
>>> Weather34 is displaying the Solar radiation reading instead of the UV 
>>> index.  Any idea how to correct this?
>>>
>>> I've installed this version a few weeks ago and its been a problem since 
>>> then. WX-HC20-IHVN-1.0.0 WeeWX-(4.0.0) Ambient Weather WS-1000 
>>> http://cawston.weather-station.co.uk/
>>>
>>> w34realtime.txt : 29/05/20 12:12:34 22.0 33 5.0 0.5 0.2 77 0.0 0.0 
>>> 1015.5 ENE 0 m/s C mb mm 9.3 -0.7 0.0 109.2 0.0 25.3 23 22.0 3.8 22.0 12:11 
>>> 11.0 05:35 2.0 11:21 4.4 09:49 1017.9 00:10 1015.2 11:36 4.0.0 0 3.3 22.0 
>>> NULL 3054.0 NULL 630 188 0.0 0 1 0 S NULL m NULL 7.4 NULL 0
>>>
>>> 44th value is 3054.0 and is displayed as the UVI.
>>>
>>> I don't have a definition for the w34realtime.txt,  
>>> https://cumuluswiki.org/a/Realtime.txt has the definition for 
>>> "realtime.txt",  i'm unsure is this is the same.  
>>>
>>> If the definition is correct then it looks like my solar radiation is in 
>>> the wrong place.  Any idea how to fix.
>>>
>>> weewx config:
>>>
>>> [Weather34RealTime]
>>> binding = loop
>>> exclude_fields = rain
>>> filename = /var/www/html/weewx/weather34/w34realtime.txt
>>> unit_system = METRICWX
>>> "# cache_enable" = False
>>> cache_stale_time = 900
>>> cache_directory = /tmp
>>>
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/da42a7a6-caeb-4d5f-a452-025ee9222afc%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e359e6d9-1f70-4e58-91c2-f3bb3fd13ca0%40googlegroups.com.

[weewx-user] Re: today vs yesterday plot?

[J D]

Hi,
This is possible with Weather34 skin.

https://github.com/steepleian/weewx-Weather34



On Tuesday, May 19, 2020 at 7:13:26 AM UTC-7, Andrea Cecilia wrote:
>
> Hi there,
> is it possible to plot, in daily graphs, today and yesterday temperature?
> I mean, a plot which has time on x axis, and two lines, one with today and 
> another with yesterday temperature. It is a way to compare these 
> temperatures at same time but at different days.
> Thank you
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/672499db-de3c-47be-8b23-4bb15be2d557%40googlegroups.com.

[weewx-user] wee_import

[J W]

When using docker (multiple setups), I get the following type of errors 
when trying to run wee_import:

Message: 'Starting wee_import...'   


 

Arguments: ()   

A CSV import from source file '/etc/weewx/extra/Rain19.csv' has been request
ed. 
--- Logging error ---   

Traceback (most recent call last):  

  File "/usr/lib/python3.7/logging/handlers.py", line 933, in emit  

self.socket.send(msg)   

OSError: [Errno 9] Bad file descriptor  
 
During handling of the above exception, another exception occurred: 
  
Traceback (most recent call last):  

  File "/usr/lib/python3.7/logging/handlers.py", line 854, in _connect_unixs
ocket   
self.socket.connect(address) 

FileNotFoundError: [Errno 2] No such file or directory


  However, if I install weewx direclyt in the OS it works (same files etc)
Is there a missing library or package?

-- 
You received this message because you are 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/f6c1f1db-8d19-47ee-8e36-c6968dc19295%40googlegroups.com.

Re: [weewx-user] Issue with weewx-meteotemplate after upgradeing weewx v4

[J Stargazer]

Thanks Tom.

I have update the extension and it is working great now.

On Saturday, May 9, 2020 at 12:40:41 AM UTC+12, Tom Keffer wrote:
>
> Try this version: 
> https://raw.githubusercontent.com/tkeffer/weewx-meteotemplate/master/bin/user/meteotemplate.py
>
> On Fri, May 8, 2020 at 4:52 AM Tom Keffer > 
> wrote:
>
>> Matthew and I are working on converting all of the uploaders. I'm working 
>> on meteotemplate, and expect to have something later today.
>>
>> On Fri, May 8, 2020 at 4:19 AM Tom > 
>> wrote:
>>
>>> I have the same issues.  Thanks to Google I was able to correct the "except 
>>> KeyError, e:" error but then other error messages appeared.  I sent 
>>> Matthew, the owner of the extension, an email earlier but have not heard 
>>> back from him.
>>>
>>> Tom 
>>>
>>> -- Original Message --
>>> From: "J Stargazer" >
>>> To: "weewx-user" >
>>> Sent: 5/8/2020 1:23:08 AM
>>> Subject: [weewx-user] Issue with weewx-meteotemplate after upgradeing 
>>> weewx v4
>>>
>>> Hi all.
>>>
>>> I'm having a bit of an issue with installing the weewx-meteotemplate 
>>> extension.
>>> I had few other issues as well, but have resolved most of those by 
>>> uninstalling the extensions and reinstalling them.
>>>
>>> The error I am getting is;
>>>
>>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: Caught 
>>> unrecoverable exception:
>>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   invalid 
>>> syntax (meteotemplate.py, line 106)
>>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   
>>> Traceback (most recent call last):
>>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
>>> "/usr/share/weewx/weewxd", line 148, in main
>>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   
>>> engine = weewx.engine.StdEngine(config_dict)
>>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
>>> "/usr/share/weewx/weewx/engine.py", line 75, in __init__
>>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   
>>> self.loadServices(config_dict)
>>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
>>> "/usr/share/weewx/weewx/engine.py", line 138, in loadServices
>>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   obj 
>>> = weeutil.weeutil.get_object(svc)(self,config_dict)
>>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
>>> "/usr/share/weewx/weeutil/weeutil.py", line 1093, in get_object
>>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   mod 
>>> = __import__(module)
>>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
>>> "/usr/share/weewx/user/meteotemplate.py", line 106
>>> May  8 14:21:02 jupiter weewx[2718] CRITICAL __main__:   
>>> except KeyError, e:
>>> May  8 14:21:02 jupiter weewx[2718] CRITICAL __main__: 
>>>  ^
>>> May  8 14:21:02 jupiter weewx[2718] CRITICAL __main__:   
>>> SyntaxError: invalid syntax
>>> May  8 14:21:02 jupiter weewx[2718] CRITICAL __main__:   Exiting.
>>> May  8 14:21:35 jupiter weewx[2764]: Stopping weewx weather system: 
>>> weewx not running
>>>
>>> I followed the error to - File "/usr/share/weewx/user/meteotemplate.py", 
>>> line 106
>>> Line 106 shows (highlighted yellow);
>>>
>>>super(Meteotemplate, self).__init__(engine, cfg_dict)
>>> loginf("service version is %s" % VERSION)
>>> try:
>>> site_dict = cfg_dict['StdRESTful']['Meteotemplate']
>>> site_dict = accumulateLeaves(site_dict, max_level=1)
>>> site_dict['password']
>>> except KeyError, e:
>>> logerr("Data will not be uploaded: Missing option %s" % e)
>>> return
>>>
>>> Unfortunately I have no idea what this is telling me.
>>>
>>> Any help would be really appreciated.
>>>
>>> Thanks,
>>> Jono
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from t

[weewx-user] Re: Issue with weewx-meteotemplate after upgradeing weewx v4

[J Stargazer]

Thanks JD.
Unfortunately when I upgraded my system python was up dated to version 3.
And I'm no programmer convert the code is probably not going to work for me.

On Friday, May 8, 2020 at 6:29:26 PM UTC+12, J D wrote:
>
> Hi,
> Three choices run under Python 2.7 or find a python 3 version of the code 
> or convert the code from python2 to python3.
>
> On Thursday, May 7, 2020 at 11:23:08 PM UTC-7, J Stargazer wrote:
>>
>> Hi all.
>>
>> I'm having a bit of an issue with installing the weewx-meteotemplate 
>> extension.
>> I had few other issues as well, but have resolved most of those by 
>> uninstalling the extensions and reinstalling them.
>>
>> The error I am getting is;
>>
>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: Caught 
>> unrecoverable exception:
>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   invalid 
>> syntax (meteotemplate.py, line 106)
>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   
>> Traceback (most recent call last):
>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
>> "/usr/share/weewx/weewxd", line 148, in main
>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   
>> engine = weewx.engine.StdEngine(config_dict)
>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 75, in __init__
>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   
>> self.loadServices(config_dict)
>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 138, in loadServices
>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   obj 
>> = weeutil.weeutil.get_object(svc)(self,config_dict)
>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
>> "/usr/share/weewx/weeutil/weeutil.py", line 1093, in get_object
>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   mod 
>> = __import__(module)
>> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
>> "/usr/share/weewx/user/meteotemplate.py", line 106
>> May  8 14:21:02 jupiter weewx[2718] CRITICAL __main__:   
>> except KeyError, e:
>> May  8 14:21:02 jupiter weewx[2718] CRITICAL __main__: 
>>  ^
>> May  8 14:21:02 jupiter weewx[2718] CRITICAL __main__:   
>> SyntaxError: invalid syntax
>> May  8 14:21:02 jupiter weewx[2718] CRITICAL __main__:   Exiting.
>> May  8 14:21:35 jupiter weewx[2764]: Stopping weewx weather system: weewx 
>> not running
>>
>> I followed the error to - File "/usr/share/weewx/user/meteotemplate.py", 
>> line 106
>> Line 106 shows (highlighted yellow);
>>
>>super(Meteotemplate, self).__init__(engine, cfg_dict)
>> loginf("service version is %s" % VERSION)
>> try:
>> site_dict = cfg_dict['StdRESTful']['Meteotemplate']
>> site_dict = accumulateLeaves(site_dict, max_level=1)
>> site_dict['password']
>> except KeyError, e:
>> logerr("Data will not be uploaded: Missing option %s" % e)
>> return
>>
>> Unfortunately I have no idea what this is telling me.
>>
>> Any help would be really appreciated.
>>
>> Thanks,
>> Jono
>>
>

-- 
You received this message because you are 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/9be88c30-dd44-41bc-ad47-77e50b435508%40googlegroups.com.

[weewx-user] Re: Issue with weewx-meteotemplate after upgradeing weewx v4

[J D]

Hi,
Three choices run under Python 2.7 or find a python 3 version of the code 
or convert the code from python2 to python3.

On Thursday, May 7, 2020 at 11:23:08 PM UTC-7, J Stargazer wrote:
>
> Hi all.
>
> I'm having a bit of an issue with installing the weewx-meteotemplate 
> extension.
> I had few other issues as well, but have resolved most of those by 
> uninstalling the extensions and reinstalling them.
>
> The error I am getting is;
>
> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: Caught 
> unrecoverable exception:
> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   invalid 
> syntax (meteotemplate.py, line 106)
> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   Traceback 
> (most recent call last):
> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
> "/usr/share/weewx/weewxd", line 148, in main
> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   
> engine = weewx.engine.StdEngine(config_dict)
> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 75, in __init__
> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   
> self.loadServices(config_dict)
> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 138, in loadServices
> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   obj = 
> weeutil.weeutil.get_object(svc)(self,config_dict)
> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
> "/usr/share/weewx/weeutil/weeutil.py", line 1093, in get_object
> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   mod = 
> __import__(module)
> May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
> "/usr/share/weewx/user/meteotemplate.py", line 106
> May  8 14:21:02 jupiter weewx[2718] CRITICAL __main__:   
> except KeyError, e:
> May  8 14:21:02 jupiter weewx[2718] CRITICAL __main__: 
>  ^
> May  8 14:21:02 jupiter weewx[2718] CRITICAL __main__:   
> SyntaxError: invalid syntax
> May  8 14:21:02 jupiter weewx[2718] CRITICAL __main__:   Exiting.
> May  8 14:21:35 jupiter weewx[2764]: Stopping weewx weather system: weewx 
> not running
>
> I followed the error to - File "/usr/share/weewx/user/meteotemplate.py", 
> line 106
> Line 106 shows (highlighted yellow);
>
>super(Meteotemplate, self).__init__(engine, cfg_dict)
> loginf("service version is %s" % VERSION)
> try:
> site_dict = cfg_dict['StdRESTful']['Meteotemplate']
> site_dict = accumulateLeaves(site_dict, max_level=1)
> site_dict['password']
> except KeyError, e:
> logerr("Data will not be uploaded: Missing option %s" % e)
> return
>
> Unfortunately I have no idea what this is telling me.
>
> Any help would be really appreciated.
>
> Thanks,
> Jono
>

-- 
You received this message because you are 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/82e0c510-e03d-4d08-9c29-97d017f8e47d%40googlegroups.com.

[weewx-user] Issue with weewx-meteotemplate after upgradeing weewx v4

[J Stargazer]

Hi all.

I'm having a bit of an issue with installing the weewx-meteotemplate 
extension.
I had few other issues as well, but have resolved most of those by 
uninstalling the extensions and reinstalling them.

The error I am getting is;

May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: Caught unrecoverable 
exception:
May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   invalid 
syntax (meteotemplate.py, line 106)
May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   Traceback 
(most recent call last):
May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
"/usr/share/weewx/weewxd", line 148, in main
May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   engine 
= weewx.engine.StdEngine(config_dict)
May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 75, in __init__
May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   
self.loadServices(config_dict)
May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 138, in loadServices
May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   obj = 
weeutil.weeutil.get_object(svc)(self,config_dict)
May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1093, in get_object
May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__:   mod = 
__import__(module)
May  8 14:21:01 jupiter weewx[2718] CRITICAL __main__: File 
"/usr/share/weewx/user/meteotemplate.py", line 106
May  8 14:21:02 jupiter weewx[2718] CRITICAL __main__:   except 
KeyError, e:
May  8 14:21:02 jupiter weewx[2718] CRITICAL __main__: 
 ^
May  8 14:21:02 jupiter weewx[2718] CRITICAL __main__:   
SyntaxError: invalid syntax
May  8 14:21:02 jupiter weewx[2718] CRITICAL __main__:   Exiting.
May  8 14:21:35 jupiter weewx[2764]: Stopping weewx weather system: weewx 
not running

I followed the error to - File "/usr/share/weewx/user/meteotemplate.py", 
line 106
Line 106 shows (highlighted yellow);

   super(Meteotemplate, self).__init__(engine, cfg_dict)
loginf("service version is %s" % VERSION)
try:
site_dict = cfg_dict['StdRESTful']['Meteotemplate']
site_dict = accumulateLeaves(site_dict, max_level=1)
site_dict['password']
except KeyError, e:
logerr("Data will not be uploaded: Missing option %s" % e)
return

Unfortunately I have no idea what this is telling me.

Any help would be really appreciated.

Thanks,
Jono

-- 
You received this message because you are 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/e4cbb0f2-d650-4fe7-a9f7-21c77008780a%40googlegroups.com.

[weewx-user] Re: PM2_5 no such column errors on weather34

[J D]

Hi,
Ian is the owner of this so I just emailed him. When he gets online later 
he will help with this.
I am curious where you got the archivedata.php.tmpl file since the one I am 
using does not have these fields.?
You can always make a copy of the file and delete the missing fields from 
the tmpl file since they really should not be there.

On Sunday, April 26, 2020 at 9:43:14 PM UTC-7, Chris Alemany wrote:
>
> Hi all,
>
> I just updated to a new version of the weather34 skin and am having a 
> problem with the database schema.  I have a purple air station and it is 
> hooked in with the purpleair extension which displays fine in the regular 
> skin here:
> https://www.alberniweather.ca/index.html
>
> However weather34 is complaining of a missing column which is preventing 
> the archivedata.php file from being generated.
>
> default   21:35:26.641849-0700Python  manager: Added record 
> 2020-04-26 21:35:00 PDT (1587962100) to daily summary in 'weewx.sdb'
> error 21:35:32.756817-0700 Python no such column: pm2_5 in "SELECT 
> avg(pm2_5) FROM archive WHERE dateTime > 1587875700 AND dateTime <= 
> 1587962100 AND pm2_5 IS NOT NULL"
> default 21:35:32.756968-0700 Python cheetahgenerator: Generate failed 
> with exception ''
> default 21:35:32.757054-0700 Python cheetahgenerator:  Ignoring 
> template /Users/Shared/weewx/skins/Weather34/archivedata.php.tmpl
> default 21:35:32.757129-0700 Python cheetahgenerator:  Reason: no 
> such column: pm2_5
> error 21:35:32.860069-0700 Python no such column: uva in "SELECT 
> dateTime, uva, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> error 21:35:32.860202-0700 Python no such column: uvb in "SELECT 
> dateTime, uvb, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> error 21:35:32.860348-0700 Python no such column: uvaWm in "SELECT 
> dateTime, uvaWm, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> error 21:35:32.860419-0700 Python no such column: uvbWm in "SELECT 
> dateTime, uvbWm, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> error 21:35:32.860481-0700 Python no such column: full_spectrum in 
> "SELECT dateTime, full_spectrum, usUnits, `interval` FROM archive WHERE 
> dateTime >= ? AND dateTime <= ?"
> error 21:35:32.860543-0700 Python no such column: lux in "SELECT 
> dateTime, lux, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> error 21:35:32.860624-0700 Python no such column: infrared in "SELECT 
> dateTime, infrared, usUnits, `interval` FROM archive WHERE dateTime >= ? 
> AND dateTime <= ?"
> error 21:35:32.860687-0700 Python no such column: pm2_5 in "SELECT 
> dateTime, pm2_5, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
> error 21:35:32.860830-0700 Python no such column: pm10_0 in "SELECT 
> dateTime, pm10_0, usUnits, `interval` FROM archive WHERE dateTime >= ? AND 
> dateTime <= ?"
>
> I've tried temperarily removing mention of pm2.5 from the skin file but it 
> isn't helping.
>
> Any suggestions greatly appreciated!
> Cheers
> Chris
>

-- 
You received this message because you are 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/a6ae8964-054f-48c8-b9fb-bcebc487cf0c%40googlegroups.com.

[weewx-user] Re: Need help with error message

[J D]

Hi,
Have you google WeatherLink in this group. There is a lot of topics on 
getting it connected,

On Tuesday, April 21, 2020 at 1:24:29 PM UTC-7, Peter Ten Eyck wrote:
>
> I have installed WeeWX on an updated Raspberry Pi and trying to start 
> weewx and getting this error:
>
> Apr 21 16:16:58 Weatherpi weewx[1056]: engine: Initializing engine 
> Apr 21 16:16:58 Weatherpi weewx[1056]: engine: Loading station type 
> Vantage (weewx.drivers.vantage) 
> Apr 21 16:16:58 Weatherpi weewx[1056]: vantage: Driver version is 3.1.1 
> Apr 21 16:16:58 Weatherpi systemd[1]: Started LSB: weewx weather system. 
> Apr 21 16:16:58 Weatherpi weewx[1056]: vantage: Socket error while opening 
> port 2 to ethernet host WeeWX. 
> Apr 21 16:16:58 Weatherpi weewx[1056]: engine: Import of driver failed: 
> [Errno 111] Connection refused () 
> Apr 21 16:16:58 Weatherpi weewx[1056]: engine: Unable to load driver: 
> [Errno 111] Connection refused 
> Apr 21 16:16:58 Weatherpi weewx[1056]:   Exiting...
>
> Any suggestions on how to fix?
>

-- 
You received this message because you are 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/11e36a75-eb5d-431d-b67d-51a4f685e3e7%40googlegroups.com.

[weewx-user] Re: Import weather data generated as Json

[J D]

Hi,
Google search in this group.

https://groups.google.com/forum/?hl=en#!searchin/weewx-user/import$20json|sort:date/weewx-user/x1P9BX6_blQ/t1sPbL2BCwAJ

On Sunday, April 19, 2020 at 9:32:26 AM UTC-7, Matt Pitts wrote:
>
> Hi There, 
>
> I have a basic weather station which publishes its data using Rest in a 
> JSON format.  
> http://www.switchdoc.com/2016/06/ourweather-rest-interface-interface-raspberry-pi/
>  
>
> Does anyone know if it's possible and relatively straight forward to get 
> this data flowing into WeeWX?  
>
> I'd really appreciate if someone could point me in the right direction?
>
> Cheers
>
> Matt
>

-- 
You received this message because you are 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/f3a669a3-0a6d-4541-b192-98b806d2379e%40googlegroups.com.

[weewx-user] Re: Highcharts on Weewx v4

[J D]

Hi,
Run withPython2.7 or get a version of highcharts search for python3

On Saturday, April 18, 2020 at 11:48:17 AM UTC-7, Phil Owers wrote:
>
> Hi Guys
>
> Loaded highcharts onto my weewx v4 machine and it failed
> averagesSearchX.py line 105 which is 
>  except Exception, e:
>
> Just wondered if this was a known problem
>
> Cheers Phil
>

-- 
You received this message because you are 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/c1562dc0-07d2-4f6b-84fe-be0f22d34ab4%40googlegroups.com.

[weewx-user] Re: Weather34 on ramdisk

[J D]

you have an issue either your apache config file or the permissions used to 
start apache. Google the error.

On Monday, March 9, 2020 at 4:41:50 PM UTC-7, Bill Arthur wrote:
>
> I'm putting together a remote weather station using WeeWx and ARPS radio. 
> It's a bit of a drive so reliability is very important to me. For that 
> reason I've installed the ramdisk according to the WeeWx manual. But I'm 
> having problems because I also want to use Weather34 on my home station.
>
> I installed WeeWx, PHP, Apache and Weather34. Everything is working, the 
> default WeeWx html page and the Weather34 html & PHP page.
>
> Then I installed the ramdisk. I confirmed the path was correct in the 
> weewx and apache configs. The WeeWx default page works great.
> The weather34 files are in the correct location 
> /var/weewx/reports/weather34. I can bring up stationinfo.php and 
> easyW34SkinSetup.php OK.
> But /var/weewx/reports/weather34/index.php has write permission problems. 
> I get:
>
> *Unable to write to the website's folder. Make sure the root of the 
> website is writable by your webserver.*
> *If you're using Apache on linux, Apache should be running as user 
> 'www-data' and group 'www-data'. If so, run these commands or adjust them 
> for Apache's user:group*
> *find . -type d -exec sudo chown www-data:www-data {} \; -exec sudo chmod 
> 2775 {} \;*
> *and*
> *find . -type f -exec sudo chown www-data:www-data {} \; -exec sudo chmod 
> 664 {} \;*
> *from within the root of your website's folder, probably located in 
> '/var/www/example.com/html/pws .'*
> *or, do yourself a huge favor and navigate into your 'html' folder and use 
> these 3 commands to automatically set the permissions on all files and 
> folders created inside it:*
> *chmod g+s .*
> *setfacl -d -m g::rwx .*
> *setfacl -d -m o::rx .*
>
>
>
>
>
>
>
>
>
>
>
> *After trying the first two commands (2775&664) I then got  a sad face and 
> error 500So I rebooted and tried the last three. Done inside the reports 
> folder I got the "Unable to write" screen again.I did the three commands in 
> the weather34 directory and had the same resultsSo I guess I need help 
> getting write premissions correct so that weather34's index.php is 
> happy.then I'm going to need a chron event to apply that to files after 
> they are created, 10 minutes after bootup.Thanks,Bill*
>

-- 
You received this message because you are 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/8bb42bf1-5da2-4571-8b3d-f1f0e32d7af2%40googlegroups.com.

[weewx-user] Re: Weather34 on ramdisk

[J D]

The full path is 
/var/www/html/weewx/Weather34

the url is 
http://192.168.0.21:88/weewx/Weather34/?units=us 


On Monday, March 9, 2020 at 4:41:50 PM UTC-7, Bill Arthur wrote:
>
> I'm putting together a remote weather station using WeeWx and ARPS radio. 
> It's a bit of a drive so reliability is very important to me. For that 
> reason I've installed the ramdisk according to the WeeWx manual. But I'm 
> having problems because I also want to use Weather34 on my home station.
>
> I installed WeeWx, PHP, Apache and Weather34. Everything is working, the 
> default WeeWx html page and the Weather34 html & PHP page.
>
> Then I installed the ramdisk. I confirmed the path was correct in the 
> weewx and apache configs. The WeeWx default page works great.
> The weather34 files are in the correct location 
> /var/weewx/reports/weather34. I can bring up stationinfo.php and 
> easyW34SkinSetup.php OK.
> But /var/weewx/reports/weather34/index.php has write permission problems. 
> I get:
>
> *Unable to write to the website's folder. Make sure the root of the 
> website is writable by your webserver.*
> *If you're using Apache on linux, Apache should be running as user 
> 'www-data' and group 'www-data'. If so, run these commands or adjust them 
> for Apache's user:group*
> *find . -type d -exec sudo chown www-data:www-data {} \; -exec sudo chmod 
> 2775 {} \;*
> *and*
> *find . -type f -exec sudo chown www-data:www-data {} \; -exec sudo chmod 
> 664 {} \;*
> *from within the root of your website's folder, probably located in 
> '/var/www/example.com/html/pws .'*
> *or, do yourself a huge favor and navigate into your 'html' folder and use 
> these 3 commands to automatically set the permissions on all files and 
> folders created inside it:*
> *chmod g+s .*
> *setfacl -d -m g::rwx .*
> *setfacl -d -m o::rx .*
>
>
>
>
>
>
>
>
>
>
>
> *After trying the first two commands (2775&664) I then got  a sad face and 
> error 500So I rebooted and tried the last three. Done inside the reports 
> folder I got the "Unable to write" screen again.I did the three commands in 
> the weather34 directory and had the same resultsSo I guess I need help 
> getting write premissions correct so that weather34's index.php is 
> happy.then I'm going to need a chron event to apply that to files after 
> they are created, 10 minutes after bootup.Thanks,Bill*
>

-- 
You received this message because you are 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/b9a2b072-150d-45a7-a588-0ba7567ff0b9%40googlegroups.com.

[weewx-user] Re: Weather34 on ramdisk

[J D]

Hi,
Here is what I have done on my setup. sudo chown www-data for all files in 
Weather34 including Weather34 directory. Then sudo chgrp www-data for the 
same set of files and directories. In my case my Weather34 directory exists 
in the weewx.

On Monday, March 9, 2020 at 4:41:50 PM UTC-7, Bill Arthur wrote:
>
> I'm putting together a remote weather station using WeeWx and ARPS radio. 
> It's a bit of a drive so reliability is very important to me. For that 
> reason I've installed the ramdisk according to the WeeWx manual. But I'm 
> having problems because I also want to use Weather34 on my home station.
>
> I installed WeeWx, PHP, Apache and Weather34. Everything is working, the 
> default WeeWx html page and the Weather34 html & PHP page.
>
> Then I installed the ramdisk. I confirmed the path was correct in the 
> weewx and apache configs. The WeeWx default page works great.
> The weather34 files are in the correct location 
> /var/weewx/reports/weather34. I can bring up stationinfo.php and 
> easyW34SkinSetup.php OK.
> But /var/weewx/reports/weather34/index.php has write permission problems. 
> I get:
>
> *Unable to write to the website's folder. Make sure the root of the 
> website is writable by your webserver.*
> *If you're using Apache on linux, Apache should be running as user 
> 'www-data' and group 'www-data'. If so, run these commands or adjust them 
> for Apache's user:group*
> *find . -type d -exec sudo chown www-data:www-data {} \; -exec sudo chmod 
> 2775 {} \;*
> *and*
> *find . -type f -exec sudo chown www-data:www-data {} \; -exec sudo chmod 
> 664 {} \;*
> *from within the root of your website's folder, probably located in 
> '/var/www/example.com/html/pws .'*
> *or, do yourself a huge favor and navigate into your 'html' folder and use 
> these 3 commands to automatically set the permissions on all files and 
> folders created inside it:*
> *chmod g+s .*
> *setfacl -d -m g::rwx .*
> *setfacl -d -m o::rx .*
>
>
>
>
>
>
>
>
>
>
>
> *After trying the first two commands (2775&664) I then got  a sad face and 
> error 500So I rebooted and tried the last three. Done inside the reports 
> folder I got the "Unable to write" screen again.I did the three commands in 
> the weather34 directory and had the same resultsSo I guess I need help 
> getting write premissions correct so that weather34's index.php is 
> happy.then I'm going to need a chron event to apply that to files after 
> they are created, 10 minutes after bootup.Thanks,Bill*
>

-- 
You received this message because you are 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/0c3a1717-f551-435e-ab9b-fd2fd08bde1a%40googlegroups.com.

[weewx-user] Re: Weather34 on ramdisk

[J D]

Make sure  the Weather34 directory has the correct permissions and 
ownership also.

On Monday, March 9, 2020 at 4:41:50 PM UTC-7, Bill Arthur wrote:
>
> I'm putting together a remote weather station using WeeWx and ARPS radio. 
> It's a bit of a drive so reliability is very important to me. For that 
> reason I've installed the ramdisk according to the WeeWx manual. But I'm 
> having problems because I also want to use Weather34 on my home station.
>
> I installed WeeWx, PHP, Apache and Weather34. Everything is working, the 
> default WeeWx html page and the Weather34 html & PHP page.
>
> Then I installed the ramdisk. I confirmed the path was correct in the 
> weewx and apache configs. The WeeWx default page works great.
> The weather34 files are in the correct location 
> /var/weewx/reports/weather34. I can bring up stationinfo.php and 
> easyW34SkinSetup.php OK.
> But /var/weewx/reports/weather34/index.php has write permission problems. 
> I get:
>
> *Unable to write to the website's folder. Make sure the root of the 
> website is writable by your webserver.*
> *If you're using Apache on linux, Apache should be running as user 
> 'www-data' and group 'www-data'. If so, run these commands or adjust them 
> for Apache's user:group*
> *find . -type d -exec sudo chown www-data:www-data {} \; -exec sudo chmod 
> 2775 {} \;*
> *and*
> *find . -type f -exec sudo chown www-data:www-data {} \; -exec sudo chmod 
> 664 {} \;*
> *from within the root of your website's folder, probably located in 
> '/var/www/example.com/html/pws .'*
> *or, do yourself a huge favor and navigate into your 'html' folder and use 
> these 3 commands to automatically set the permissions on all files and 
> folders created inside it:*
> *chmod g+s .*
> *setfacl -d -m g::rwx .*
> *setfacl -d -m o::rx .*
>
>
>
>
>
>
>
>
>
>
>
> *After trying the first two commands (2775&664) I then got  a sad face and 
> error 500So I rebooted and tried the last three. Done inside the reports 
> folder I got the "Unable to write" screen again.I did the three commands in 
> the weather34 directory and had the same resultsSo I guess I need help 
> getting write premissions correct so that weather34's index.php is 
> happy.then I'm going to need a chron event to apply that to files after 
> they are created, 10 minutes after bootup.Thanks,Bill*
>

-- 
You received this message because you are 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/e2e41bcc-f7af-403e-b186-202c34ee6261%40googlegroups.com.

[weewx-user] Re: wee_database: ImportError

[J D]

Hi,
Did you do both commands that were indicated.?
 
sudo apt-get install mysql-client
*sudo apt-get install python-mysqldb*

The second install is also needed.
Jerry

On Tuesday, February 25, 2020 at 12:30:31 PM UTC-7, Eric Gammeter wrote:
>
>
> Hmm  .  
> FYI:  The mysql-client has been replaced with the mariadb-client-10.0.
> Still not working.  
>
> wee_database --transfer --dest-binding=dest_binding
> Using configuration file /etc/weewx/weewx.conf
> Using database binding 'wx_binding', which is bound to database 
> 'archive_sqlite'
> Transfer 9187 records from source database 'weewx.sdb' to destination 
> database 'weewx' (y/n)? y
> Error accessing destination database 'weewx'.
> Maybe it does not exist (MySQL) or is incorrectly defined in weewx.conf?
> Nothing done. Aborting.
>
>
> On Tuesday, February 25, 2020 at 9:11:40 AM UTC-5, Eric Gammeter wrote:
>>
>>
>> Goal:
>> Wanting to switch from sqlite to MySql database. 
>>
>> I am consulting the github /weewx/wiki "Usingwee_database".
>>
>> The --dry-run doesn't show any error.  
>>
>>
>> pi@raspberrypi:~ $ wee_database --transfer --dest-binding=dest_binding 
>> --dry-run
>> Using configuration file /etc/weewx/weewx.conf
>> Using database binding 'wx_binding', which is bound to database 
>> 'archive_sqlite'
>> Transfer 9177 records from source database 'weewx.sdb' to destination 
>> database 'weewx'.
>> Dry run, nothing done.
>> pi@raspberrypi:~ $ wee_database --transfer --dest-binding=dest_binding
>> Using configuration file /etc/weewx/weewx.conf
>> Using database binding 'wx_binding', which is bound to database 
>> 'archive_sqlite'
>> Transfer 9177 records from source database 'weewx.sdb' to destination 
>> database 'weewx' (y/n)? y
>> Error accessing destination database 'weewx'.
>> Nothing done. Aborting.
>> Traceback (most recent call last):
>>   File "/usr/bin/wee_database", line 794, in 
>> main()
>>   File "/usr/bin/wee_database", line 159, in main
>> transferDatabase(config_dict, db_binding, options)
>>   File "/usr/bin/wee_database", line 410, in transferDatabase
>> schema=dest_manager_dict['schema']) as dest_manager:
>>   File "/usr/share/weewx/weewx/manager.py", line 128, in open_with_create
>> connection = weedb.connect(database_dict)
>>   File "/usr/share/weewx/weedb/__init__.py", line 86, in connect
>> __import__(db_dict['driver'])
>>   File "/usr/share/weewx/weedb/mysql.py", line 10, in 
>> import MySQLdb
>> ImportError: No module named MySQLdb
>>
>>

-- 
You received this message because you are 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/3793b0ca-a43c-43e9-bdbb-ab5603241ec0%40googlegroups.com.

Re: [weewx-user] Re: WeeWX v4 I Need an Extension Verified/Checked

[J D]

Hi,
For what it is worth. The file is not corrupt it just has tabs set to 8 
spaces for indentation and space indentation set to 4 spaces. So if you 
replace the tabs with 8 spaces and leave the spaces along the file should 
indent correctly. If you use an Eclipse editor with a python plugin you can 
easily see this.
Thanks

On Friday, February 21, 2020 at 3:37:45 PM UTC-7, G Hammer wrote:
>
> Perhaps, but it is working on my production system at the moment under 
> python 2.7
>
> On Fri, Feb 21, 2020, 5:34 PM vince > 
> wrote:
>
>> On Friday, February 21, 2020 at 2:27:34 PM UTC-8, J D wrote:
>>>
>>> Sorry to tell you but what you posted has indentation problems in many 
>>> places. I would spend some time reading the link I sent you about python 
>>> indentation and try it again.
>>>
>>>>
>>>>
>> The file you are starting with is hosed on the github side.  No way it 
>> works as-is with weewx of any version.
>>
>> There are 39 places on 32 lines.   Simply substituting 4-spaces for 1-tab 
>> globally doesn't do it, as it results in hosed space-based indenting that 
>> needs hand-fixing to add/delete spaces so the actual code works.
>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/wlufg8AdT0E/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/7fc0a424-79d3-4c43-b01e-65d83d858a4b%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/7fc0a424-79d3-4c43-b01e-65d83d858a4b%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e2a02ce0-514d-4d27-9310-91fba364c386%40googlegroups.com.

[weewx-user] Re: WeeWX v4 I Need an Extension Verified/Checked

[J D]

Hi,
Sorry to tell you but what you posted has indentation problems in many 
places. I would spend some time reading the link I sent you about python 
indentation and try it again.
Thanks

On Saturday, January 18, 2020 at 7:46:16 PM UTC-7, G Hammer wrote:
>
> I'd like to run v4 when I upgrade hardware this week.
> Seems to be doing fine for the devices and skin I use.
> With one exception, a RainMachine extension.
> There is one that was written by someone at RainMachine, but I think he 
> has moved on.
> I've asked there and raised an issue on the github page for the extension 
> with no response.
>
> How, besides installing v4 and the extension, can I determine if it will 
> run under v4?
>
> The extension is located at https://github.com/sprinkler/rainmachine-weewx 
> and 
> referenced at https://github.com/weewx/weewx/wiki/RainMachine
>
> With this functionality confirmed, I can make the change, without it I'll 
> need to stay with v3
>
>
>

-- 
You received this message because you are 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/c5f85afb-dec6-4f6f-9aed-8c04e53a4dab%40googlegroups.com.

[weewx-user] Re: WeeWX v4 I Need an Extension Verified/Checked

[J D]

Hi,
So your edits for the tabs messed up the python indentation. I would go 
back to a previous version and make sure that for each tab you find that 
you put in the correct number of spaces so the code still lines up after 
you replace the tabs as it did before. This is why I need to see the actual 
file.
Thanks

On Saturday, January 18, 2020 at 7:46:16 PM UTC-7, G Hammer wrote:
>
> I'd like to run v4 when I upgrade hardware this week.
> Seems to be doing fine for the devices and skin I use.
> With one exception, a RainMachine extension.
> There is one that was written by someone at RainMachine, but I think he 
> has moved on.
> I've asked there and raised an issue on the github page for the extension 
> with no response.
>
> How, besides installing v4 and the extension, can I determine if it will 
> run under v4?
>
> The extension is located at https://github.com/sprinkler/rainmachine-weewx 
> and 
> referenced at https://github.com/weewx/weewx/wiki/RainMachine
>
> With this functionality confirmed, I can make the change, without it I'll 
> need to stay with v3
>
>
>

-- 
You received this message because you are 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/90af4946-02e1-421c-b1c8-55a504b63b2e%40googlegroups.com.

[weewx-user] Re: WeeWX v4 I Need an Extension Verified/Checked

[J D]

Hi,
Need to see the actual file creating the error since you have been changing 
it based on your previous posts.
Thanks

On Saturday, January 18, 2020 at 7:46:16 PM UTC-7, G Hammer wrote:
>
> I'd like to run v4 when I upgrade hardware this week.
> Seems to be doing fine for the devices and skin I use.
> With one exception, a RainMachine extension.
> There is one that was written by someone at RainMachine, but I think he 
> has moved on.
> I've asked there and raised an issue on the github page for the extension 
> with no response.
>
> How, besides installing v4 and the extension, can I determine if it will 
> run under v4?
>
> The extension is located at https://github.com/sprinkler/rainmachine-weewx 
> and 
> referenced at https://github.com/weewx/weewx/wiki/RainMachine
>
> With this functionality confirmed, I can make the change, without it I'll 
> need to stay with v3
>
>
>

-- 
You received this message because you are 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/ef7130ef-24a1-44fb-b413-080cacf91fe1%40googlegroups.com.

[weewx-user] Re: WeeWX v4 I Need an Extension Verified/Checked

[J D]

Hi,
You need to post the actual code that produced this error if you want 
additional help.
Thanks

On Saturday, January 18, 2020 at 7:46:16 PM UTC-7, G Hammer wrote:
>
> I'd like to run v4 when I upgrade hardware this week.
> Seems to be doing fine for the devices and skin I use.
> With one exception, a RainMachine extension.
> There is one that was written by someone at RainMachine, but I think he 
> has moved on.
> I've asked there and raised an issue on the github page for the extension 
> with no response.
>
> How, besides installing v4 and the extension, can I determine if it will 
> run under v4?
>
> The extension is located at https://github.com/sprinkler/rainmachine-weewx 
> and 
> referenced at https://github.com/weewx/weewx/wiki/RainMachine
>
> With this functionality confirmed, I can make the change, without it I'll 
> need to stay with v3
>
>
>

-- 
You received this message because you are 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/af5f5f67-1241-40f0-a0d6-a28ca4efd370%40googlegroups.com.

[weewx-user] Re: WeeWX v4 I Need an Extension Verified/Checked

[J D]

Hi,
Python 3 does not allow tabs and spaces to be mixed. See 
https://www.python.org/dev/peps/pep-0008/ 
Most people just use an editor and replace the tabs with correct amount of 
spaces when they see this error.
Thanks Jerry

On Saturday, January 18, 2020 at 7:46:16 PM UTC-7, G Hammer wrote:
>
> I'd like to run v4 when I upgrade hardware this week.
> Seems to be doing fine for the devices and skin I use.
> With one exception, a RainMachine extension.
> There is one that was written by someone at RainMachine, but I think he 
> has moved on.
> I've asked there and raised an issue on the github page for the extension 
> with no response.
>
> How, besides installing v4 and the extension, can I determine if it will 
> run under v4?
>
> The extension is located at https://github.com/sprinkler/rainmachine-weewx 
> and 
> referenced at https://github.com/weewx/weewx/wiki/RainMachine
>
> With this functionality confirmed, I can make the change, without it I'll 
> need to stay with v3
>
>
>

-- 
You received this message because you are 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/c6b4487d-4325-4b04-a450-0118869ab97a%40googlegroups.com.

[weewx-user] Re: Mismatch Between Hardware and weeWX Data

[J D]

Hi,
I am using the ws23xx driver on ws2316 hardware and this driver sends 
absolute pressure to weewx in the packet as "pressure" ..
The ws28xx hardware sends relative pressure and the ws28xx driver also 
sends the reading to weewx in the packet as pressure. See below

packet['*pressure*']= get_datum_diff(data._PressureRelative_hPa,
   CWeatherTraits.PressureNP(),
   CWeatherTraits.PressureOFL())

I suspect the code should read.
packet['*barometer*']= get_datum_diff(data._PressureRelative_hPa,
   CWeatherTraits.PressureNP(),
   CWeatherTraits.PressureOFL())
Or you could just change the altitude of the station as Andrew suggest.

Jerry

On Sunday, February 9, 2020 at 4:36:51 PM UTC-7, Dan Blanchard wrote:
>
> I've been running my weather station on weeWX for 2 days now after 
> switching from a PC based solution for the past several years.  I noticed 
> this problem after noticing that my station is no longer showing on the 
> WeatherUnderground (WU) maps.  The data is still showing for my site on WU 
> though (https://www.wunderground.com/dashboard/pws/KIDPOSTF43)
>
> Everything has been going fine except I am currently having a problem with 
> data inaccuracies.  All the data seems correct except the barometer 
> reading.  The reading on my hardware is currently 30.30 and weeWX is 
> showing 33.093 which is what is reporting to WU.
>
> Can anyone please shed some light on this issue?  I've attached the syslog 
> for reference.  Please let me know if there is anything else I can provide 
> to help with this situation. If the solution requires changes in the 
> configuration file, please be specific as I am still learning the Linux 
> stuff.
>
> Thanks,
>
> Dan
>
>
> Hardware: Lacrosse WS-2813
>
>

-- 
You received this message because you are 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/808ad0bc-3181-405f-827f-823372544045%40googlegroups.com.

[weewx-user] Re: Gravity AS3935 lightning detector

[J D]

Hi,
FYI this is not a weewx error since weewx has nothing to do with an 
extension.
Also a 121 error usually means that the device did not receive the data in 
the "format" or order it was expecting. 
This assumes all the connections are done correctly, which they seem to be 
based on the debug output.
I would start by looking at the protocol of the DFrobot and see if it any 
different than what was coded in the extension. I have used a number of 
these devices and have not seen any differences yet but I have not used 
this one. It could be the first. I also would check to make sure the device 
is getting the startup commands in the order it expects. I have seem 
devices that were very picky out this.
Thanks


On Sunday, February 2, 2020 at 4:25:07 AM UTC-7, Giuseppe Saia wrote:
>
> Good morning and good Sunday to everyone
> I recently purchased the DFrobot gravity detection sensor. after having 
> connected it correctly to the raspberry pi 3b + and having verified the 
> correct operation with the command sudo i2cdetect -y 1 I would like to 
> implement on weewx the fields lightning_strikes and avg_distance to each 
> archive record.
>

-- 
You received this message because you are 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/9a6bec8b-6ac9-4874-8791-3f430d05737f%40googlegroups.com.

Re: [weewx-user] Re: rtupdate.wunderground.com certificate error

[J B]

Thanks for the update.

I'm not really sure what he means about embedded device controllers...most 
of us are running RaspberryPis that are sending data using Python. I'm 
pretty sure it can handle host names fine.

On Wednesday, February 5, 2020 at 12:40:31 PM UTC-8, Dave McCreath wrote:
>
> Leon
>
> The text below was posted by Tim Roche (WU IT) on the WeatherUndergound 
> FaceBook page 17 hours ago:
>
> *Quick update: We have some answers for why many of the stations are not 
> sending data. It appears that many of the embedded device controllers don't 
> behave very well with host names, and are sending data to us in a way that 
> is not expected.*
>
> *We love that enthusiasts building cool stuff send data to Weather 
> Underground, so while we asses how to fix these issues, we have temporarily 
> rolled back to our legacy system.*
>
> *We will be testing over the next week to see how to fix these problems, 
> and will ask for help from some of you.*
>
> *I would like to personally apologize for this issue, we felt our testing 
> was robust, but obviously there were gaps. We're still working on a plan 
> and I will try to keep you updated here.*
>
>
> Tim is a regular poster on the site and it's a good source of what's going 
> on.
>
>
> I think the time coincides with everything correcting itself on your system
>
>
> Regards
>
>
> Dave
>
> On Wednesday, 5 February 2020 16:42:53 UTC, Leon Shaner wrote:
>>
>> FWIW, I haven't seen any 404's since around these times from last night:
>>
>> Feb  4 20:43:52 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: 
>> Not Found
>> Feb  4 20:43:52 Wunderground-RF: Failed to publish record 2020-02-04 
>> 20:43:53 EST (1580867033): Failed upload after 1 tries
>> Feb  4 20:49:10 Wunderground-RF: Failed upload attempt 1: > _ssl.c:1039: The handshake operation timed out>
>> Feb  4 20:49:10 Wunderground-RF: Failed to publish record 2020-02-04 
>> 20:48:49 EST (1580867329): Failed upload after 1 tries
>> Feb  4 20:49:45 Wunderground-RF: Failed upload attempt 1: > timed out>
>> Feb  4 20:49:45 Wunderground-RF: Failed to publish record 2020-02-04 
>> 20:49:15 EST (1580867355): Failed upload after 1 tries
>> Feb  4 20:50:19 Wunderground-RF: Failed upload attempt 1: > timed out>
>> Feb  4 20:50:19 Wunderground-RF: Failed to publish record 2020-02-04 
>> 20:49:49 EST (1580867389): Failed upload after 1 tries
>> Feb  4 21:04:41 Wunderground-RF: Failed upload attempt 1: > [Errno 104] Connection reset by peer>
>> Feb  4 21:04:41 Wunderground-RF: Failed to publish record 2020-02-04 
>> 21:04:41 EST (1580868281): Failed upload after 1 tries
>> Feb  4 21:04:44 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: 
>> Not Found
>>
>>
>> Regards,
>> \Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad)
>>
>>
>>>

-- 
You received this message because you are 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/b2f3448a-dc34-4fa6-a938-2264197c25af%40googlegroups.com.

[weewx-user] Re: rtupdate.wunderground.com certificate error

[J B]

I should mention that I'm assuming that this workaround doesn't turn off 
certificate validation system-wide but I'm not well-versed enough in how 
this works to know for sure. Since the daemons are managed by root I guess 
it's possible.

On Sunday, February 2, 2020 at 9:14:24 PM UTC-8, J B wrote:
>
> Like some of you I'm still getting intermittent errors that stop weewx 
> 3.9.2 from uploading until I restart. Someone over at 
> https://apicommunity.wunderground.com/ posted this creative 
> workaround that seems to be working so far. It lowers the security of 
> python but it's better than sending everything over http.
>
> tmarschner 
> <https://apicommunity.wunderground.com/weatherapi/people/tmarschner>
>
>- 2 Posts 
>-  0 Reply Likes
>
> Hi there,
>
> Here's an alternative workaround that doesn't require you to send your 
> Wunderground credentials in clear text. It turns off certificate validation 
> for python. I've tested this on weewx 3.9.2 on a Raspberry Pi (v. 9 
> Stretch) running python 2.7.13.
>
> Modify the weewx startup script /etc/init.d/weewx.
>
> Find the start-stop-daemon line that starts up weewx (the do_start 
> routine) and insert "/usr/bin/env PYTHONHTTPSVERIFY=0" into the --exec 
> parameter as shown below:
>
> start-stop-daemon --start --chuid $WEEWX_USER --pidfile $PIDFILE --exec 
> /usr/bin/env PYTHONHTTPSVERIFY=0 $DAEMON -- $DAEMON_ARGS || return 2
>
> Cheers,
> Tom
>

-- 
You received this message because you are 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/0b003603-6086-4d16-8612-ddb526efa1b9%40googlegroups.com.

[weewx-user] Re: rtupdate.wunderground.com certificate error

[J B]

Like some of you I'm still getting intermittent errors that stop weewx 
3.9.2 from uploading until I restart. Someone over at 
https://apicommunity.wunderground.com/ posted this creative workaround that 
seems to be working so far. It lowers the security of python but it's 
better than sending everything over http.

tmarschner 


   - 2 Posts 
   -  0 Reply Likes

Hi there,

Here's an alternative workaround that doesn't require you to send your 
Wunderground credentials in clear text. It turns off certificate validation 
for python. I've tested this on weewx 3.9.2 on a Raspberry Pi (v. 9 
Stretch) running python 2.7.13.

Modify the weewx startup script /etc/init.d/weewx.

Find the start-stop-daemon line that starts up weewx (the do_start routine) 
and insert "/usr/bin/env PYTHONHTTPSVERIFY=0" into the --exec parameter as 
shown below:

start-stop-daemon --start --chuid $WEEWX_USER --pidfile $PIDFILE --exec 
/usr/bin/env PYTHONHTTPSVERIFY=0 $DAEMON -- $DAEMON_ARGS || return 2

Cheers,
Tom

-- 
You received this message because you are 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/98106b14-546a-481b-a49c-c8cf3ec19d7c%40googlegroups.com.

Re: [weewx-user] Re: rtupdate.wunderground.com certificate error

[J B]

Working here too. I had to restart Weewx.

On Friday, January 31, 2020 at 11:34:19 AM UTC-8, Brice Ruth wrote:
>
> Looking like it's working to me, too.
>
> Brice Ruth, FCD
> Software Engineer, Madison WI
>
>
> On Fri, Jan 31, 2020 at 1:31 PM Travis Bully  > wrote:
>
>> Agreed.  Seems like I still get one cert error every now and then.  
>> Likely still propagating changes through their infrastructure?
>>
>> Jan 31 14:29:25 homeauto03 weewx[3784]: restx: Wunderground-RF: Published 
>> record 2020-01-31 14:29:24 EST (1580498964)
>> Jan 31 14:29:26 homeauto03 weewx[3784]: restx: Wunderground-RF: Failed 
>> upload attempt 1: > certificate verify failed (_ssl.c:727)>
>> Jan 31 14:29:31 homeauto03 weewx[3784]: restx: Wunderground-RF: Failed to 
>> publish record 2020-01-31 14:29:26 EST (1580498966): Failed upload after 1 
>> tries
>> Jan 31 14:29:31 homeauto03 weewx[3784]: restx: Wunderground-RF: Published 
>> record 2020-01-31 14:29:30 EST (1580498970)
>>
>> On Fri, Jan 31, 2020 at 2:30 PM Denny Page > > wrote:
>>
>>> It's fixed now.
>>>
>>>
>>> On Friday, January 31, 2020 at 8:54:02 AM UTC-8, Denny Page wrote:

 Wunderground just posted a note about the intermediate certificate 
 issue. Hopefully they will fix it shortly.

>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/weewx-user/mYhw6CSKHHg/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> weewx...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/f5e5741a-e5f8-419b-9c0d-df1972fe5ced%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/CAF_%2Bh57S88%3DZOX1mXK8oZBx-_KEHvDPFP%3Dvtd4u3_1qg7994yg%40mail.gmail.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/80045ee1-d48d-47ed-95fd-19af175783f0%40googlegroups.com.

[weewx-user] Re: rtupdate.wunderground.com certificate error

[J B]

I just tried running the request that Weewx attempts manually via curl and 
it still gives me a certificate error:

curl: (60) SSL certificate problem: unable to get local issuer certificate


Maybe there's some caching involved?

On Thursday, January 30, 2020 at 1:51:28 PM UTC-8, Denny Page wrote:
>
> I received an email from Wunderground "Yes, there was a problem that has 
> been resolved."
>
> While the certificate error has been resolved, it appears that the https 
> head still is not accepting updates. The http head appears fully 
> functional. I've reported the secondary problem to them.
>

-- 
You received this message because you are 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/6595b863-76fd-40fc-a625-c93da3c7f012%40googlegroups.com.

[weewx-user] Re: rtupdate.wunderground.com certificate error

[J B]

Same problem here. Thanks for posting the response from WU.

-- 
You received this message because you are 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/f6336e3e-00f0-4d47-88ee-a51b4e2c3ef7%40googlegroups.com.

[weewx-user] Wunderground Upload fails with SSL error started last night

[J B]

Hi,
I've had a PWS uploading to Wunderground with Weewx 3.9.2 on a Raspberry Pi 
for several months. Yesterday the station randomly stopped uploading to WU 
although my local database is still being updated. Checking the log shows 
the following:

restx: Wunderground-PWS: Failed upload attempt 1: 

Elsewhere in the log I found the actual URL that is being queried by weewx 
and when I run that manually with curl I get the following:

user@host:~$ curl -L 
"https://weatherstation.wunderground.com/weatherstation/updateweatherstation.php?action=updateraw;"
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.


I've tried this on 2 other systems (another RPi and a CentOS VM) with the 
same result. I'm not that familiar with SSL certificates but when I check 
the one for weatherstation.wunderground.com one in my browser it says 
"valid".

Is anyone else having this problem? How can I fix this issue?

Thanks in advance.

-- 
You received this message because you are 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/b444ed31-e887-45bf-9c06-ad995ea53494%40googlegroups.com.

[weewx-user] Re: Image backup vs database

[J D]

You can backup a sd card while the raspberry pi is running all you need is 
a usb reader/writer for the new sd card and the program "SD Card Copier." 
Which you can get with sudo apt-get.
I use it on all my 10 running pi's.
Jerry

On Friday, January 10, 2020 at 11:23:31 AM UTC-7, Keimpe Bleeker wrote:
>
> Hi Weewx users,
>
> Rather new to Raspberry, supernew to Weewx (to replace my Windows 
> WeatherDisplay system, based on Davis Vantage Pro2 [https://oentsjerk.eu];). 
> My Weewx [https:oentsjerk.eu/wwx/] will come to life after version Weewx 
> 4.# is available and I am able to import my historical data from 
> Wunderground. So there is some time to tune.
>
> I'm running a script in a cronjob once a day, to backup the advised Weewx 
> files to my NAS. It's working nice in backup as well for the (manual) 
> restore. I also should like to backup an image of the SDcard once a week. 
> Is it necessary to shut down Weewx before the image backup is running, to 
> be safe the database will not will be affected by the backup process?
>  
>

-- 
You received this message because you are 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/5e7b8ee5-5dfc-47c3-aabc-c5b9606f8bdc%40googlegroups.com.

[weewx-user] Re: wanted: users with ecowitt gw1000 wifi bridge

[J D]

FYI your passkey is in the response. I would delete the response and 
re-post without the passkey


On Sunday, December 29, 2019 at 9:59:56 PM UTC-7, mwall wrote:
>
> the weewx-interceptor driver has been updated with explicit support for 
> the gw1000 wifi bridge, as well as support for weewx4/python3.
>
> instructions are at the weewx wiki:
>
> https://github.com/weewx/weewx/wiki/gw1000-recipe
>
> i would especially appreciate feedback from anyone with full sensor arrays 
> (wind, rain, uv), particulate sensors, soil moisture sensors, and any other 
> extended sensors offered by ecowitt.
>
> although the interceptor will now understand the extended weather 
> underground protocol, the 'fineoffset-bridge' type uses the ecowitt 
> protocol and a direct-to-weewx configuration (no dns hijack or sniffing or 
> other shenanigans required).  it does require a recent firmware on the 
> gw1000 (testing with 1.5.5)
>
> 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/50b10ce2-61ec-46be-b01c-7bb5d9e3841c%40googlegroups.com.

[weewx-user] Re: History graphs being updated only for Today[ weekly/monthly/yearly not updated since 2/21/2019

[J D]

HI,
When you post a question, please remember to:

   1. *Post the relevant portion of the system log*
   - The log is essential to diagnosing any problem.
  - It helps to turn on the "debug" flag (set debug=1 in the 
  configuration file weewx.conf), then run again.
  2. *Post the relevant portion of the weewx configuration file and/or 
   skin configuration file;*
   3. *Specify the type of weather station hardware you are using;*
   4. *Tell us how you installed weewx.*

For more information about what makes a good post, see the guidelines *Help! 
Posting to weewx user! 
* in the 
wiki.
Thanks

On Saturday, December 21, 2019 at 7:51:15 AM UTC-7, Robert Anthony Pitera 
wrote:
>
> Not sure what is going wrong, but only my daily graphs are being updated. 
> The week/month/year all show the same date of 2/21/2019.
>
> On the same page though, the historical highs and lows ARE up to date.
>
> [image: graphs.jpg]
>
>
>
> I've tried manually running wee_reports and looking through some long logs 
> but I'm not seeing anything obvious and running out of ideas.  Anyone have 
> a clue about what is going on?  It was working fine at one time - likely 
> before 2/21/19 would be my guess - but I can't remember any configuration 
> changes done at that time.  That may be the date I last updated to the 
> latest version of WeeWX but it's so long ago I am not sure.  It seems like 
> if I changed something in the report generator then it wouldn't be updating 
> the daily graphs either.  It seems obvious to me that the data is there (as 
> demonstrated from the textual representation on the right) but somehow the 
> reports that produce the graphs for the other periods are never being run.
>
>
> Any help you could give or point me to would be appreciated; I've done 
> research here, on the web and in the docs and can't seem to find anything 
> related to my problem.
>

-- 
You received this message because you are 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/afd263d9-88b2-4fa8-9c95-391b8de038f7%40googlegroups.com.

[weewx-user] Re: WeeWX et WS-2300

[J D]

Hi,
I use WS23xx driver on a pi  but you need to be careful about your serial 
to usb converter.  This is stated in the driver file

With a USB-serial converter one can connect the station to a computer with
only USB ports, but not every converter will work properly.  Perhaps the two
most common converters are based on the Prolific and FTDI chipsets.  Many
people report better luck with the FTDI-based converters.  Some converters
that use the Prolific chipset (PL2303) will work, but not all of them.

Known to work: ATEN UC-232A

I use the ATEN converter and it does work without any issues. 
Also here is what I see in my dmesg

[3.784359] usbserial: USB Serial support registered for generic
[3.804690] usbserial: USB Serial support registered for FTDI USB Serial 
Device
[3.805247] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
[3.837746] usb 1-1.2: FTDI USB Serial Device converter now attached to 
ttyUSB0
[3.838010] ftdi_sio 1-1.2:1.1: FTDI USB Serial Device converter detected
[3.841931] usb 1-1.2: FTDI USB Serial Device converter now attached to 
ttyUSB1

I would look at getting a different converter or a different pi since this 
looks like a hardware issue.
Thanks Jerry


On Friday, December 6, 2019 at 7:24:07 AM UTC-7, Olivier Garnier wrote:
>
> Hi,
>
>
> I used to use WS2300 with wview (RIP).
> Now i try to configure weewx with ws2300 on Raspberry and it does not work 
> ...
> i installed it with apt-get.
>
> dmesg :
> [1.623394] usb 1-1.4: New USB device found, idVendor=0403, idProduct=
> 6001, bcdDevice= 4.00
> [1.623410] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=0
> [1.623423] usb 1-1.4: Product: USB <-> Serial
> [1.623434] usb 1-1.4: Manufacturer: FTDI
>
> #modprobe ftdi_sio
> #ls /dev/ttyUSB*
> /dev/ttyUSB0
>
>
> weewx.conf :
> ...
>
> [Station]
>
> # Description of the station location
> location = ""
>
> # Latitude and longitude in decimal degrees
> latitude = 50.000
> longitude = 1.000
>
> # Altitude of the station, with unit it is in. This is downloaded from
> # from the station if the hardware supports it.
> altitude = 100, meter
>
> # Set to type of station hardware. There must be a corresponding 
> stanza
> # in this file with a 'driver' parameter indicating the driver to be 
> used.
> station_type = WS23xx
>
> # If you have a website, you may specify an URL
> #station_url = http://www.example.com
>
> # The start of the rain year (1=January; 10=October, etc.). This is
> # downloaded from the station if the hardware supports it.
> rain_year_start = 1
>
> # Start of week (0=Monday, 6=Sunday)
> week_start = 0
>
>
> ##
>
> [WS23xx]
> # This section is for the La Crosse WS-2300 series of weather 
> stations.
>
> # Serial port such as /dev/ttyS0, /dev/ttyUSB0, or /dev/cuaU0
> port = /dev/ttyUSB0
>
> # The station model, e.g., 'LaCrosse WS2317' or 'TFA Primus'
> model = LaCrosse WS-2300
>
> # The driver to use:
> driver = weewx.drivers.ws23xx
>
>
> ##
> ...
>
>
>
> and when i ask wee_device --current
> Using configuration file /etc/weewx/weewx.conf
> Using WS23xx driver version 0.27 (weewx.drivers.ws23xx)
> Querying the station for current weather data...
> Traceback (most recent call last):
>   File "/usr/bin/wee_device", line 66, in 
> main()
>   File "/usr/bin/wee_device", line 62, in main
> device.configure(config_dict)
>   File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
> self.do_options(options, parser, config_dict, prompt)
>   File "/usr/share/weewx/weewx/drivers/ws23xx.py", line 313, in do_options
> self.show_current()
>   File "/usr/share/weewx/weewx/drivers/ws23xx.py", line 339, in 
> show_current
> for packet in self.station.genLoopPackets():
>   File "/usr/share/weewx/weewx/drivers/ws23xx.py", line 502, in 
> genLoopPackets
> raise weewx.RetriesExceeded(msg)
> weewx.RetriesExceeded: Max retries (5) exceeded for LOOP data
>
> Does anyone has an idéa ?
>
>
>

-- 
You received this message because you are 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/8d6ac1a7-bc71-4b07-b0df-31f569a8dad8%40googlegroups.com.

[weewx-user] Re: bootstrap history page

[J D]

Here is the line for easy find

 colours =   "#0029E5", "#0186E7", "#02E3EA", "#04EC97", *"#05EF3D2,* 
"#2BF207", 


On Thursday, November 12, 2015 at 6:09:10 AM UTC-7, Robin wrote:
>
> I really like the bootstrap history page as seen at
>
> http://www.dajda.net/history.html
>
> I am pretty happy with my current skin, and was wondering if it is 
> possible to add a page like this without a full install of the bootstrap 
> skin? I would not be using the gauges and can edit the templates.
>
> Any advice would be most welcome.
>
> Robin
>

-- 
You received this message because you are 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/fe7e58a9-093d-4b37-bff9-12dd447e84db%40googlegroups.com.

[weewx-user] Re: Datenbank zusammen legen.

[J D]

Hi,

Yes you can merge two databases I have done it a number of times. You need 
to use SQLite commands. At a high level you attached to the two databases 
and then use the update command. If you google merge sqlite databases you 
can find a number of ways to do it.
Jerry 

On Sunday, November 24, 2019 at 2:52:27 AM UTC-7, Günther Wrana wrote:
>
> Hallo
>
> ich möchte Versuchen zwei Datenbanken von weewx.sdb zusammen zu fügen.
>
> Ich habe einen Rechner mit Ubuntu und kann die Datenbank mit DB Browser 
> for SQLite öffnen.
>
> Die beiden Datenbanken beginnen und enden zu folgenden Zeiten.
>
> 1573144800 07.11.2019 17:40:00
> 1573149300 07.11.2019 18:55:00
>
> 1573249500 08.11.2019 22:45:00
> 1574009700 17.11.2019 17:55:00
>
> Nun habe ich noch nicht herausgefunden wie ich das mit DB Browser for 
> SQLite mache.
> Ich weis auch nicht ob das das Richtige Programm für mein Vorhaben ist.
>
> Darum hoffe ich das Ihr mir sagen könnt wie oder mit welchem Programm ich 
> das tun soll.
> Das ganze ist einmal ein Versuch danach würde ich dann gerne meine alten 
> Wetterdaten die ich seit November 2014 aufgezeichnet habe auch noch 
> einfügen.
>
> Für alle Tipps bin ich dankbar also dann
>
> Grüße Günther
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ae66f6c9-93ad-491c-8f24-afa56c40e4b6%40googlegroups.com.

Re: [weewx-user] Re: Weewx 3.9.2 and WMR200 crash: Non-positive value for record field 'interval': 0

[Patrick J]

Hi,

I am testing the new driver for almost 2 weeks now, and I am still getting 
frequent crashes, so this is not the solution to this problem.

On Tuesday, September 24, 2019 at 7:58:09 AM UTC+2, Björn Torkelsson wrote:
>
> Hi Thomas,
>
> I have the same problem as Patrick. Though I had no luck with the new 
> driver version you suggested him to try with. I get: 
>
> Sep 24 07:13:57 ripslinger weewx[17315]: engine: Starting up weewx version 
> 3.9.2
> Sep 24 07:13:59 ripslinger weewx[17315]: wmr200: MainThread: I 
> genStartup() Delaying archive packet processing until live packet received
> Sep 24 07:13:59 ripslinger weewx[17315]: wmr200: MainThread: I Time drift 
> between host and console in seconds:-361
> Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: MainThread: I 
> genStartup() Still receiving archive packets cnt:0 len:1
> Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: MainThread: I Using pc 
> time adjusting archive record time by -361 sec 2019-09-21 13:08:00 CEST 
> (1569064080) => 2019-09-21 13:01:59 CEST (1569063719)
> Sep 24 07:14:00 ripslinger weewx[17315]: engine: Main loop exiting. 
> Shutting engine down.
> Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: Thread-2: I USB polling 
> device thread exiting
> Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: MainThread: I USB polling 
> thread expired
> Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: Thread-1: I Watchdog 
> received shutdown
> Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: Thread-1: I Watchdog 
> thread exiting
> Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: MainThread: I Watchdog 
> thread expired
> Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: MainThread: I Received 
> packet count live:1 archive:1 control:1
> Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: MainThread: I Received 
> bytes:600 sent bytes:40
> Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: MainThread: I Packet 
> archive queue len:0 live queue len:1
> Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: MainThread: W Exiting 
> with packets still in live queue cnt:1
> Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: MainThread: I Driver 
> gracefully exiting
> Sep 24 07:14:00 ripslinger weewx[17315]: engine: Caught unrecoverable 
> exception in engine:
> Sep 24 07:14:00 ripslinger weewx[17315]:   'WMR200' object has no 
> attribute 'wmr200'
> Sep 24 07:14:00 ripslinger weewx[17315]:   Traceback (most recent 
> call last):
> Sep 24 07:14:00 ripslinger weewx[17315]: File 
> "/usr/share/weewx/weewx/engine.py", line 894, in main
> Sep 24 07:14:00 ripslinger weewx[17315]:   engine.run()
> Sep 24 07:14:00 ripslinger weewx[17315]: File 
> "/usr/share/weewx/weewx/engine.py", line 160, in run
> Sep 24 07:14:00 ripslinger weewx[17315]:   
> self.dispatchEvent(weewx.Event(weewx.STARTUP))
> Sep 24 07:14:00 ripslinger weewx[17315]: File 
> "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
> Sep 24 07:14:00 ripslinger weewx[17315]:   callback(event)
> Sep 24 07:14:00 ripslinger weewx[17315]: File 
> "/usr/share/weewx/weewx/engine.py", line 520, in startup
> Sep 24 07:14:00 ripslinger weewx[17315]:   
> self._catchup(self.engine.console.genStartupRecords)
> Sep 24 07:14:00 ripslinger weewx[17315]: File 
> "/usr/share/weewx/weewx/engine.py", line 632, in _catchup
> Sep 24 07:14:00 ripslinger weewx[17315]:   for record in 
> generator(lastgood_ts):
> Sep 24 07:14:00 ripslinger weewx[17315]: File 
> "/usr/share/weewx/weewx/drivers/wmr200.py", line 1940, in genStartupRecords
> Sep 24 07:14:00 ripslinger weewx[17315]:   
> timestamp_packet_previous += self.wmr200.time_drift
> Sep 24 07:14:00 ripslinger weewx[17315]:   AttributeError: 
> 'WMR200' object has no attribute 'wmr200'
> Sep 24 07:14:00 ripslinger weewx[17315]:   Exiting.
>
> Den torsdag 12 september 2019 kl. 14:40:52 UTC+2 skrev Thomas Keffer:
>>
>> Hello, Patrick
>>
>> Can you try this version 
>> <https://raw.githubusercontent.com/cmanton/weewx/47800a0a622b7931898faf5aa6b254cac943557a/bin/weewx/drivers/wmr200.py>
>>  
>> of the driver?
>>
>> On Tue, Sep 10, 2019 at 9:43 PM Patrick J  wrote:
>>
>>> Hi,
>>>
>>> Last night, weewx crashed again, exactly the same scenario. Any help 
>>> would be greatly appreciated.
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it,

[weewx-user] Re: AS3935 Lightening Detector

[J D]

Hi Dan,
I greatly modified the python code that I got from here
https://github.com/pcfens/RaspberryPi-AS3935/tree/8f624b1588ba54977a596c1409800a286ea445b0
I also think it is the basics for the weewx extension.
I do not use the weewx extension since I wrote my own program to control 
the detectors since I run three of the them. But IMHO if I was using the 
weewx extension I would comment out the code in the interrupt handler for 
changing the noise setting and just log that it happen or write code that 
lowers the setting after a couple of minutes. I also would comment out the 
code for setting the disturber mask and again just log them when they 
happen. In my code I actually just log every 10 disturber interrupts to cut 
down on the log entries. The device real weakness is disturbers and 
handling them makes all the difference in how well the device will work. 
For tuning I looked at a "c" program but then wrote my own in python that 
tries to handle dealing with measuring timing using a RP and python and the 
device.  Also when I talk about heat swings i mean from 70 to 130 degrees 
since my system has direct sun on it.
Thanks Jerry

On Thursday, September 19, 2019 at 4:50:22 AM UTC-7, dan Forster wrote:
>
> Jerry,
>
> Sorry for not coming back sooner, I have been traveling with work.
>
> Many thanks for your comments. You are far ahead of me with regards to 
> working these little lightning detector boards out and getting the best 
> from them.
>
> A quick question, what code do you use/alter to cause a re-tune and 
> disable the noise threshold (like squelch I suppose in amateur radio)? I 
> noticed the board does get warm and slightly deaf due to the 500Khz tuning 
> cap being affected by this heat.
>
> Cheers,
>
> Dan
>
>
>
> On Saturday, 14 September 2019 14:16:14 UTC-4, J D wrote:
>>
>> Hi Dan,
>> Nice write up of your work.
>>
>> Here are a couple items to help with the correctness of the device.
>> If you are using the very common python code found on the net there are a 
>> number of issues with it.
>> The big one is the disturber mask part.  In the specs when a disturber is 
>> detected the device turns off for a 1.5 seconds. It also sends the 
>> interrupt. If you are using the python code the interrupt handler turns on 
>> the mask interrupt bit in the device. So now no more interrupts but the 
>> device still turns off and this is bad. Also to make things worse very far 
>> away lightning is sometimes detected as a disturber. So IMHO I would 
>> disable the setting of the mask bit and if you are having a lot of issues 
>> with disturbers either move the device or change the Watchdog setting, or 
>> the AFE setting or the Spike setting or the Noise setting to reduce the 
>> number of disturbers. This is not a perfect solution since changing the 
>> settings reduces the device sensitivity but at least it does not turn it 
>> off for a 1.5 seconds.
>> The next problem is the Noise threshold part of the python code. The 
>> problem here is noise can come and go but the code only raises the Noise 
>> Threshold there is no code for lowering it. Again IMHO I found that it is 
>> best to disable this code and if the noise is truly an issue manually raise 
>> the Noise threshold or put in timer code that lowers it to see if the noise 
>> is still high.
>> Another code issue is that there is no auto calibrate of the tune cap. 
>> There does exist a "c" version for auto tune and I have written my own 
>> python version of auto tune. Auto tune IMHO is only needed if you have the 
>> device outside where there are large temp swings. I have found that as the 
>> devices get hot the tune cap value needs to go higher to keep it as close 
>> as possible to 500khz. The specs state that the other oscillators are temp 
>> compensated but nothing about the 500khz oscillator.  Usually the change is 
>> just one or two steps up or down. So I run the auto-tune 3 times a day 
>> (morning, noon,night) and if the device is detecting lightning then I skip 
>> the auto-tune for that time.
>> Thanks Jerry
>>
>>
>> On Saturday, September 14, 2019 at 8:21:02 AM UTC-7, dan Forster wrote:
>>>
>>>
>>>
>>>
>>>
>>> Sorry I have not been about and replying to board messages. Started some 
>>> DIY project which turned out larger than expected...
>>>
>>> This is how I got my AS3935 to work in Weewx. It may not bee 100% 
>>> correct, but it is now working on two pi's really well. Note if you think 
>>> you are going to run this on 6" pieces of cable, so its close to the pi, 
>>> indoors, next to all your gizz

[weewx-user] Re: AS3935 Lightening Detector

[J D]

Hi Dan,
Nice write up of your work.

Here are a couple items to help with the correctness of the device.
If you are using the very common python code found on the net there are a 
number of issues with it.
The big one is the disturber mask part.  In the specs when a disturber is 
detected the device turns off for a 1.5 seconds. It also sends the 
interrupt. If you are using the python code the interrupt handler turns on 
the mask interrupt bit in the device. So now no more interrupts but the 
device still turns off and this is bad. Also to make things worse very far 
away lightning is sometimes detected as a disturber. So IMHO I would 
disable the setting of the mask bit and if you are having a lot of issues 
with disturbers either move the device or change the Watchdog setting, or 
the AFE setting or the Spike setting or the Noise setting to reduce the 
number of disturbers. This is not a perfect solution since changing the 
settings reduces the device sensitivity but at least it does not turn it 
off for a 1.5 seconds.
The next problem is the Noise threshold part of the python code. The 
problem here is noise can come and go but the code only raises the Noise 
Threshold there is no code for lowering it. Again IMHO I found that it is 
best to disable this code and if the noise is truly an issue manually raise 
the Noise threshold or put in timer code that lowers it to see if the noise 
is still high.
Another code issue is that there is no auto calibrate of the tune cap. 
There does exist a "c" version for auto tune and I have written my own 
python version of auto tune. Auto tune IMHO is only needed if you have the 
device outside where there are large temp swings. I have found that as the 
devices get hot the tune cap value needs to go higher to keep it as close 
as possible to 500khz. The specs state that the other oscillators are temp 
compensated but nothing about the 500khz oscillator.  Usually the change is 
just one or two steps up or down. So I run the auto-tune 3 times a day 
(morning, noon,night) and if the device is detecting lightning then I skip 
the auto-tune for that time.
Thanks Jerry


On Saturday, September 14, 2019 at 8:21:02 AM UTC-7, dan Forster wrote:
>
>
>
>
>
> Sorry I have not been about and replying to board messages. Started some 
> DIY project which turned out larger than expected...
>
> This is how I got my AS3935 to work in Weewx. It may not bee 100% correct, 
> but it is now working on two pi's really well. Note if you think you are 
> going to run this on 6" pieces of cable, so its close to the pi, indoors, 
> next to all your gizzmos, the lightning will bite your bum for this thing 
> sees it. Its best run in a low noise environment (away from power supplies, 
> cheap LED lights, computer screens, etc). From what I can gather, its a 
> 500khz receiver and some clever logic, so like any radio, it likes to be 
> able to see the sky. I will start from scratch so you can get going from a 
> new pi sdcard/AS3935 board
>
> This is the detection board I use - 
> https://www.ebay.co.uk/itm/AS3935-Lightning-Strike-Storm-Distances-Detector-I2C-SPI-Sensor-Programmable/333265065400?_trkparms=ispr%3D1=item4d982555b8:g:VWUAAOSw1NNdKCt2=AQAEAAAB4BPxNw%2BVj6nta7CKEs3N0qX6knsPaWu2HyFk9u1VHKBpz81ghsTUEAWuMAkGOyv6nDm%2FfHF6ZNRVWUmyw6fMizGZ%2BYp4db2m9KpEC601RxylniwLIMm1Yna7V1VtB3WNTdeLsrOFmUXb8ykzBxZK2B3hLzfgKkhHP80k%2BXuEpKA7AgDyaSN%2FJluRWLSOUQ88THmlkf3DW0W6wL2mUZW5Sp9gkMFWxvt2OpppfyNs2YHI%2B2C%2Ftbi5YMd%2BCv5q6K300H7lsatLWwQEkE6kv1YXLLis4zt4NUw58qFrTss5O%2B%2FnahobycDwpibwG%2B%2Bj8LZ5Hn3HJgTc8sQFNyhu%2Bm6M2RUolopnAvcJu%2BWCVgM%2Fz3fr0O7l1u%2FZ1cd64SuOKVm%2FvCNIDddFrgZNW0gbMjAVxwlS11mmQuiIowAqFlf6d16f7t1yrCXjHYPZyTEqdNhTNpycb1IGseu6FoaXpJquvoB4nZrnPvn0qe7P1xPdyHVfNXh224r8jd4NDdC0jCDVDJlJD8ilWZKXe6%2Fb5sNQIoJqw5tWlPbv5gbq%2FC%2BdpTM%2BJMKdeeAPfLpHN%2FpirKMAKcbKuW6wydhGa7aa%2BRk6SnCsySeIvixE2%2Fet4FPn%2BRvEQVFVNg2M1L4tkPkpFW6bdA%3D%3D=333265065400e9f0e246d5364032ab0e55b879590ef8
>  
> - they seem fairly tough little things to be honest and can seemingly 
> withstand lots of abuse - (I must have changed every wire ((not power pins 
> of course)) in my experimentation's).
>
>
> Using RPi 3 board - using this image 
> https://downloads.raspberrypi.org/raspbian/images/raspbian-2018-11-15/. 
> Its not the latest - I prefer something tried and tested and sort of bug 
> free. NOTE - once the image is burnt to sdcard (
> https://www.balena.io/etcher/ makes prepping sdcards a cup of tea - DONT 
> buy cheap sdcards, they will make the system crawl like a snail), eject 
> card, then reinsert to the same MAC/WIN PC you just prepped card on, then 
> add a little file called ssh (make with a text editor) with no extension 
> (so thats no full stop after ssh file name - just a file called ssh) to the 
> bootable partition (the partition you see when you insert this rpi OS ready 
> sdcard into a MAC/WIN machine). This enables ssh access as default. I dont 
> use a desktop on the pi, just ssh.
>
> Put new 

Re: [weewx-user] Re: Weewx 3.9.2 and WMR200 crash: Non-positive value for record field 'interval': 0

[Patrick J]

Hi Thomas,

Thank you for the updated driver. I just installed it, and will monitor 
this closely.
Can I also draw your attention to the second bug I described in my initial 
post? It was about live packets being queued but never processed while the 
archive records were retrieved from the station. This one seems to be on 
the engine side rather than the driver.

Regards,
P.

On Thursday, September 12, 2019 at 2:40:52 PM UTC+2, Thomas Keffer wrote:
>
> Hello, Patrick
>
> Can you try this version 
> <https://raw.githubusercontent.com/cmanton/weewx/47800a0a622b7931898faf5aa6b254cac943557a/bin/weewx/drivers/wmr200.py>
>  
> of the driver?
>
> On Tue, Sep 10, 2019 at 9:43 PM Patrick J  > wrote:
>
>> Hi,
>>
>> Last night, weewx crashed again, exactly the same scenario. Any help 
>> would be greatly appreciated.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/f6b0c669-5b12-48c8-bd7b-f3abc5c6b5b3%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/f6b0c669-5b12-48c8-bd7b-f3abc5c6b5b3%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

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

[weewx-user] Re: Weewx 3.9.2 and WMR200 crash: Non-positive value for record field 'interval': 0

[Patrick J]

Hi,

Last night, weewx crashed again, exactly the same scenario. Any help would 
be greatly appreciated.

-- 
You received this message because you are 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/f6b0c669-5b12-48c8-bd7b-f3abc5c6b5b3%40googlegroups.com.

Re: [weewx-user] weewx stopped with

[J D]

Hi,
Looks like when you added your new data you have a nan (not a number) being 
put into the database. 
Check your changes to see to see if the large number is too large.
Need to see your changes to understand more.
Jerry

On Saturday, September 7, 2019 at 2:14:35 AM UTC-7, Steve Shuff wrote:
>
> Cancel
> On Sat, 7 Sep 2019, 09:11 peter, > wrote:
>
>> weewx stopped this morning with an error I don't understand. I also 
>> doesn't want to start either.
>>
>> Can some please advise what would be the cause?
>> I have Davis Vantage Vue + few other inputs from text files I log into 
>> database. This week I added logging of a big integer values into 'hail' 
>> field.
>>
>> This is the status:
>> sep 07 10:00:55 weather weewx[447]: File 
>> "/usr/share/weewx/weewx/manager.py", line 1216, in _addSingleRecord
>> sep 07 10:00:55 weather weewx[447]:   _day_summary.addRecord(
>> record, weight=_weight)
>> sep 07 10:00:55 weather weewx[447]: File 
>> "/usr/share/weewx/weewx/accum.py", line 260, in addRecord
>> sep 07 10:00:55 weather weewx[447]:   func(self, record, 
>> obs_type, add_hilo, weight)
>> sep 07 10:00:55 weather weewx[447]: File 
>> "/usr/share/weewx/weewx/accum.py", line 318, in add_value
>> sep 07 10:00:55 weather weewx[447]:   self[obs_type].addHiLo(
>> val, record['dateTime'])
>> sep 07 10:00:55 weather weewx[447]: File 
>> "/usr/share/weewx/weewx/accum.py", line 78, in addHiLo
>> sep 07 10:00:55 weather weewx[447]:   "got type '%s' ('%s')" 
>> % (type(val), val))
>> sep 07 10:00:55 weather weewx[447]:   ValueError: accum: 
>> ScalarStats.addHiLo expected float or int, got type '' (
>> 'nan')
>> sep 07 10:00:55 weather weewx[447]:   Exiting.
>>
>> Thanks!
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/75ebceae-9bb1-40f8-8ef5-96b1cedaf1d0%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/25eade25-f426-4dd6-ac32-13834ad34494%40googlegroups.com.

[weewx-user] Re: AS3935 Lightening Detector

[J D]

Hi,
They are really all the same. I have a number of them. The two I am 
currently using together are
https://www.playingwithfusion.com/productview.php?pdid=22
https://www.mikroe.com/thunder-click

And a third one standalone as a control on its own pi.
https://shop.switchdoc.com/products/the-thunder-board-i2c-lightning-detector-grove-connectors

If your's works most of the time then making the code change would be the 
easiest. Also note some of the I2C devices do not play well with other I2C 
devices. That is why I am using the thunder-click since it uses the SPI 
bus. I had to modify the python code to support SPI bus since all I found 
was I2C bus code.
Good Luck
Jerry

On Thursday, September 5, 2019 at 6:02:54 AM UTC-7, Mikael Fredriksson 
wrote:
>
> Hi Jerry!
>
> Thank you for your answer.
> I've tried changing all wires and looked for any bad connections. But no 
> success.
> I guess it's a faulty sensor so I will buy another one and see if i'm 
> lucky with that.
> The sensor I used is a CJMCU AS3935.
> Is there another recommended sensor to use with Weewx? Or are they almost 
> all the same?
>
> /Mikael
>
> Den söndag 1 september 2019 kl. 17:21:07 UTC+2 skrev J D:
>>
>> Hi,
>> I have seen this a number of times with these sensors, what I have done 
>> is the following to make it less of an issue
>> Checking for loose wires or wires not making good contact at either the 
>> GPIO pins or the device..
>> Power cycle the system.
>> Replacing the device.
>> Making sure there are no other devices with the same bus and address 
>> being used
>> Putting a while loop with a fixed loop count and a try except around the 
>> i2cbus read and sleeping for a second or two before trying the read again.. 
>> (This is the best solution and if it is still failing after 10-20 seconds 
>> of trying then there is probably a hardware failure most likely the device 
>> or a loose connection.
>> Thanks Jerry
>>
>> On Sunday, September 1, 2019 at 4:24:17 AM UTC-7, Mikael Fredriksson 
>> wrote:
>>>
>>> Hi!
>>>
>>> Got a new issue with my as3935.
>>> Running weewx 3.9.1
>>>
>>>
>>> Got this in my log when starting weewx:
>>>
>>> Sep  1 11:42:05 raspberrypi weewx[570]: engine: Debug is 1
>>> Sep  1 11:42:05 raspberrypi weewx[570]: engine: Initializing engine
>>> Sep  1 11:42:05 raspberrypi weewx[570]: engine: Loading station type 
>>> FineOffsetUSB (weewx.drivers.fousb)
>>> Sep  1 11:42:05 raspberrypi weewx[570]: fousb: driver version is 1.9
>>> Sep  1 11:42:05 raspberrypi weewx[570]: fousb: polling mode is PERIODIC
>>> Sep  1 11:42:05 raspberrypi weewx[570]: fousb: polling interval is 60
>>> Sep  1 11:42:05 raspberrypi weewx[570]: fousb: found station on USB bus= 
>>> device=
>>> Sep  1 11:42:05 raspberrypi weewx[570]: engine: Loading service 
>>> weewx.engine.StdTimeSynch
>>> Sep  1 11:42:05 raspberrypi weewx[570]: engine: Finished loading service 
>>> weewx.engine.StdTimeSynch
>>> Sep  1 11:42:05 raspberrypi weewx[570]: engine: Loading service 
>>> user.as3935.AS3935
>>> Sep  1 11:42:05 raspberrypi weewx[570]: as3935: service version is 0.6
>>> Sep  1 11:42:05 raspberrypi weewx[570]: as3935: address=0x03
>>> Sep  1 11:42:05 raspberrypi weewx[570]: as3935: bus=1
>>> Sep  1 11:42:05 raspberrypi weewx[570]: as3935: indoors=False
>>> Sep  1 11:42:05 raspberrypi weewx[570]: as3935: noise_floor=0
>>> Sep  1 11:42:05 raspberrypi weewx[570]: as3935: calibration=0x06
>>> Sep  1 11:42:05 raspberrypi weewx[570]: as3935: pin=17
>>> Sep  1 11:42:05 raspberrypi weewx[570]: as3935: data_binding=None
>>> Sep  1 11:42:05 raspberrypi weewx[570]: as3935: binding=archive
>>> Sep  1 11:42:05 raspberrypi weewx[570]: engine: Caught unrecoverable 
>>> exception in engine:
>>> Sep  1 11:42:05 raspberrypi weewx[570]:   [Errno 121] I/O-fel på 
>>> fjärrmaskin
>>> Sep  1 11:42:05 raspberrypi weewx[570]:   Traceback (most recent 
>>> call last):
>>> Sep  1 11:42:05 raspberrypi weewx[570]: File 
>>> "/usr/share/weewx/weewx/engine.py", line 884, in main
>>> Sep  1 11:42:05 raspberrypi weewx[570]:   engine = 
>>> engine_class(config_dict)
>>> Sep  1 11:42:05 raspberrypi weewx[570]: File 
>>> "/usr/share/weewx/weewx/engine.py", line 78, in __init__
>>> Sep  1 11:42:05 raspberrypi weewx[570]:   
>>> self.loadServices(config_dict)
>>> Sep  1 11:42:05 raspberrypi weewx[570]: Fi

[weewx-user] Re: AS3935 Lightening Detector

[J D]

Hi,
I have seen this a number of times with these sensors, what I have done is 
the following to make it less of an issue
Checking for loose wires or wires not making good contact at either the 
GPIO pins or the device..
Power cycle the system.
Replacing the device.
Making sure there are no other devices with the same bus and address being 
used
Putting a while loop with a fixed loop count and a try except around the 
i2cbus read and sleeping for a second or two before trying the read again.. 
(This is the best solution and if it is still failing after 10-20 seconds 
of trying then there is probably a hardware failure most likely the device 
or a loose connection.
Thanks Jerry

On Sunday, September 1, 2019 at 4:24:17 AM UTC-7, Mikael Fredriksson wrote:
>
> Hi!
>
> Got a new issue with my as3935.
> Running weewx 3.9.1
>
>
> Got this in my log when starting weewx:
>
> Sep  1 11:42:05 raspberrypi weewx[570]: engine: Debug is 1
> Sep  1 11:42:05 raspberrypi weewx[570]: engine: Initializing engine
> Sep  1 11:42:05 raspberrypi weewx[570]: engine: Loading station type 
> FineOffsetUSB (weewx.drivers.fousb)
> Sep  1 11:42:05 raspberrypi weewx[570]: fousb: driver version is 1.9
> Sep  1 11:42:05 raspberrypi weewx[570]: fousb: polling mode is PERIODIC
> Sep  1 11:42:05 raspberrypi weewx[570]: fousb: polling interval is 60
> Sep  1 11:42:05 raspberrypi weewx[570]: fousb: found station on USB bus= 
> device=
> Sep  1 11:42:05 raspberrypi weewx[570]: engine: Loading service 
> weewx.engine.StdTimeSynch
> Sep  1 11:42:05 raspberrypi weewx[570]: engine: Finished loading service 
> weewx.engine.StdTimeSynch
> Sep  1 11:42:05 raspberrypi weewx[570]: engine: Loading service 
> user.as3935.AS3935
> Sep  1 11:42:05 raspberrypi weewx[570]: as3935: service version is 0.6
> Sep  1 11:42:05 raspberrypi weewx[570]: as3935: address=0x03
> Sep  1 11:42:05 raspberrypi weewx[570]: as3935: bus=1
> Sep  1 11:42:05 raspberrypi weewx[570]: as3935: indoors=False
> Sep  1 11:42:05 raspberrypi weewx[570]: as3935: noise_floor=0
> Sep  1 11:42:05 raspberrypi weewx[570]: as3935: calibration=0x06
> Sep  1 11:42:05 raspberrypi weewx[570]: as3935: pin=17
> Sep  1 11:42:05 raspberrypi weewx[570]: as3935: data_binding=None
> Sep  1 11:42:05 raspberrypi weewx[570]: as3935: binding=archive
> Sep  1 11:42:05 raspberrypi weewx[570]: engine: Caught unrecoverable 
> exception in engine:
> Sep  1 11:42:05 raspberrypi weewx[570]:   [Errno 121] I/O-fel på 
> fjärrmaskin
> Sep  1 11:42:05 raspberrypi weewx[570]:   Traceback (most recent 
> call last):
> Sep  1 11:42:05 raspberrypi weewx[570]: File 
> "/usr/share/weewx/weewx/engine.py", line 884, in main
> Sep  1 11:42:05 raspberrypi weewx[570]:   engine = 
> engine_class(config_dict)
> Sep  1 11:42:05 raspberrypi weewx[570]: File 
> "/usr/share/weewx/weewx/engine.py", line 78, in __init__
> Sep  1 11:42:05 raspberrypi weewx[570]:   
> self.loadServices(config_dict)
> Sep  1 11:42:05 raspberrypi weewx[570]: File 
> "/usr/share/weewx/weewx/engine.py", line 142, in loadServices
> Sep  1 11:42:05 raspberrypi weewx[570]:   
> self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
> Sep  1 11:42:05 raspberrypi weewx[570]: File 
> "/usr/share/weewx/user/as3935.py", line 154, in __init__
> Sep  1 11:42:05 raspberrypi weewx[570]:   
> self.sensor.set_indoors(indoors)
> Sep  1 11:42:05 raspberrypi weewx[570]: File 
> "/usr/local/lib/python2.7/dist-packages/RPi_AS3935/RPi_AS3935.py", line 
> 162, in set_indoors
> Sep  1 11:42:05 raspberrypi weewx[570]:   self.read_data()
> Sep  1 11:42:05 raspberrypi weewx[570]: File 
> "/usr/local/lib/python2.7/dist-packages/RPi_AS3935/RPi_AS3935.py", line 
> 234, in read_data
> Sep  1 11:42:05 raspberrypi weewx[570]:   self.registers = 
> self.i2cbus.read_i2c_block_data(self.address, 0x00)
> Sep  1 11:42:05 raspberrypi weewx[570]:   IOError: [Errno 121] 
> I/O-fel på fjärrmaskin
> Sep  1 11:42:05 raspberrypi weewx[570]:   Exiting.
> Sep  1 11:44:34 raspberrypi systemd[1]: Stopping LSB: weewx weather 
> system...
>
> Haven´t changed anything and suddenly I got an I/O error on the machine.
>
> If I run "sudo i2cdetect -y 1" several times in a row I sometimes get 0x03 
> but every other time I just get --.
>
>
> Any clue what this could be or how to debug?
>
> Got it connected to my raspberry pi like this:
>
>   VCC -> 3.3V
> GND -> GND
> SCL -> PIN 5
> MOSI -> PIN 3
> SI -> 3.3V
> IRQ -> PIN 11
> A0 -> 3.3V
> A1 -> 3.3V
>
>
> /Mikael
>
> Den måndag 8 juli 2019 kl. 10:48:22 UTC+2 skrev dan Forster:
>>
>> Hi,
>>
>> I bought one of these from eBay  - *MA5532 AS3935 2.4V to 5.5V Lightning 
>> Fulmine Sensor Breakout SPI/I2C Antenna*. I have connected it all up and 
>> have it working fine, confirmed by using the demo script and install 

[weewx-user] Re: Not exactly a problem, but copygenerator: copied 0 files to

[J D]

HI,
This is normal. Nothing to worry about.
Please read http://www.weewx.com/docs/customizing.htm#[CopyGenerator]
Thanks Jerry

On Saturday, August 31, 2019 at 7:17:53 PM UTC-7, Chris Richmond wrote:
>
> Hi,
>
>   I'm watching /var/log/messages, and noticed this:
>
> Aug 31 18:45:16 pivue weewx[27341]: manager: Added record 2019-08-31 
> 18:45:00 PDT (1567302300) to database 'weewx.sdb'
> Aug 31 18:45:16 pivue weewx[27341]: manager: Added record 2019-08-31 
> 18:45:00 PDT (1567302300) to daily summary in 'weewx.sdb'
> Aug 31 18:45:32 pivue weewx[27341]: cheetahgenerator: Generated 8 files 
> for report SeasonsReport in 15.16 seconds
> Aug 31 18:45:40 pivue weewx[27341]: imagegenerator: Generated 14 images 
> for SeasonsReport in 8.08 seconds
> Aug 31 18:45:40 pivue weewx[27341]: copygenerator: copied 0 files to 
> /home/weewx/public_html.vue
>
> While at the same time, the right number of files have new timestamps.  I 
> looked at the code where the message is coming from, and
> it only comes from here:./bin/weewx/reportengine.py:
> syslog.syslog(syslog.LOG_INFO, "copygenerator: "
> so it doesn't make sense the files are updated, but the one count is 
> zero.  That message always shows 0 files copied,
> but clearly, files are getting copied.  This is with weewx 3.9.1
>
> > ls -ltr /home/weewx/public_html.vue
> -rw-r--r-- 1 weewx 13515 Aug 31 18:01 monthvolt.png
> drwxr-sr-x 2 weewx  4096 Aug 31 18:45 NOAA/
> -rw-r--r-- 1 weewx 19780 Aug 31 18:45 index.html
> -rw-r--r-- 1 weewx  2246 Aug 31 18:45 celestial.html
> -rw-r--r-- 1 weewx  3874 Aug 31 18:45 telemetry.html
> -rw-r--r-- 1 weewx  1407 Aug 31 18:45 tabular.html
> -rw-r--r-- 1 weewx 13276 Aug 31 18:45 statistics.html
> -rw-r--r-- 1 weewx  6308 Aug 31 18:45 rss.xml
> -rw-r--r-- 1 weewx  9074 Aug 31 18:45 daybarometer.png
> -rw-r--r-- 1 weewx  9685 Aug 31 18:45 daytempdew.png
> -rw-r--r-- 1 weewx  7782 Aug 31 18:45 daytempfeel.png
> -rw-r--r-- 1 weewx  7387 Aug 31 18:45 daytempin.png
> -rw-r--r-- 1 weewx  8370 Aug 31 18:45 daytemp.png
> -rw-r--r-- 1 weewx  7318 Aug 31 18:45 dayhum.png
> -rw-r--r-- 1 weewx  6375 Aug 31 18:45 dayrain.png
> -rw-r--r-- 1 weewx  8812 Aug 31 18:45 daywind.png
> -rw-r--r-- 1 weewx  7186 Aug 31 18:45 daywinddir.png
> -rw-r--r-- 1 weewx  8562 Aug 31 18:45 daywindvec.png
> -rw-r--r-- 1 weewx  6282 Aug 31 18:45 dayradiation.png
> -rw-r--r-- 1 weewx  5547 Aug 31 18:45 dayuv.png
> -rw-r--r-- 1 weewx  6628 Aug 31 18:45 dayrx.png
> -rw-r--r-- 1 weewx 13080 Aug 31 18:45 dayvolt.png
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/15356219-66fe-45cc-aa4c-275c71516e08%40googlegroups.com.

[weewx-user] Re: AS3935 Lightening Detector

[J D]

Hi,
I have this one and I know many others also do. They all "work" about the 
same, biggest difference is the Tune Cap value.  For the most part these 
devices are "toys" meaning that I would not tie any critical responses to 
what these sensors report. Also there is plenty of software for using these 
sensors but even there are a number of "flaws" in what the software does 
and what the data sheets try to explain. I use multiple sensors from 
different vendors so I can cross check the responses and decrease the 
number of incorrect responses. Also the Tune Cap changes with temperature 
so if you are using them outside then is best you auto tune them at 
different times of the day.
Thanks Jerry

On Saturday, August 24, 2019 at 10:02:37 AM UTC-7, Steve2Q wrote:
>
> Dan..do you think that this one works the same? 
> https://www.ebay.com/itm/AS3935-Digital-Lightning-Sensor-Breakout-3V-5V-Arduino-RPi-compatible-/233228596198
>
> Thanks
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6813e387-6ebf-46d7-9838-9e799e73fe66%40googlegroups.com.

[weewx-user] Re: weewxaverage extension

[J D]

Hi Phil,
If you right click on the page using Chrome you can inspect the page. Then 
under console it will show you that you have a javascript 404 error. The 
file missing is json/averages.json.
I would start by check the server to see if that file is there and in the 
correct directory.
Thanks Jerry

On Friday, July 19, 2019 at 12:30:30 PM UTC-7, Phil Owers wrote:
>
> Hi All
>
> I had trouble with the average extension back end of last year and thanks 
> to Gary he put me right. I'm changing over to a new server and I'm having 
> trouble again
>
> The old is on http://www.sheringhamweather.org.uk/averages.html  and 
> works.
>
> The new looks to be set up the same but the graph is empty.  Ive look 
> through VIEW SOURCE on edge or View Page Source on Firefox and admittedly 
> my understanding of it is limited but it looks similar as the files look 
> the same.  
> You can look at this at 
> http://www.sheringhamukweather.org.uk/averages.html   
>
> The problem is the same what ever browser I use and I have deleted the 
> browsing history as Ive had problems with that especially if I change an 
> icon on the forecast.
>
> Any help would be appreciated Thanks Phil
>

-- 
You received this message because you are 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/ea26fbd9-7bba-42a1-9cdc-1af406a76641%40googlegroups.com.

Re: [weewx-user] w34 skin issues

[J D]

Hi Sean,
The best way is to have w34skins one directory up in the skins directory 
not in the Standard skin directory like you have it. Need to also be aware 
of file permissions, meaning does the files and directory have write 
permissions that match the user running weewx.
Thanks Jerry

On Monday, July 1, 2019 at 8:29:32 AM UTC-7, Sean Lane wrote:
>
> [image: skinfolder.png]
>
> IS this the right layout for the config 
>
>
> On Mon, Jul 1, 2019 at 11:58 AM Sean Lane > 
> wrote:
>
>> Hey Thanks for the response.. The folder structure exists however i dont 
>> see the result.csv.. i am tinkering at it today so i hope to resolve it. 
>>
>> On Mon, Jul 1, 2019 at 1:04 AM J D > 
>> wrote:
>>
>>> Hi Sean,
>>>
>>> Does the following directory exists
>>>  template = result.csv.tmpl
>>> HTML_ROOT =* /var/www/html/mbcharts* 
>>>
>>> The charts are not working because the report generator cannot find the 
>>> result.csv file.
>>> Usually the paths look like this
>>>
>>>   [[[DAILYCHARTS]]]
>>> encoding = strict_ascii
>>> template = result.csv.tmpl
>>> HTML_ROOT = /var/www/html/pws/mbcharts
>>>
>>> # Charts that plot "by month"
>>> [[[MONTHLYCHARTS]]]
>>> encoding = strict_ascii
>>> template = MM.csv.tmpl
>>> HTML_ROOT = /var/www/html/pws/mbcharts/chartdata
>>>
>>> # Charts that plot "by year"
>>> [[[YEARLYCHARTS]]]
>>> encoding = strict_ascii
>>> template = .csv.tmpl
>>> HTML_ROOT = /var/www/html/pws/mbcharts/chartdata
>>>
>>> Thanks Jerry
>>>
>>> 7, Sean Lane wrote:
>>>>
>>>> please see below :
>>>>
>>>>
>>>> ###
>>>> # W34SKIN SKIN CONFIGURATION FILE   
>>>>   #
>>>> # Copyright (c) 2018 Tom Keffer  and Matthew Wall   
>>>>#
>>>> # See the file LICENSE.txt for your rights. 
>>>>   #
>>>>
>>>> ###
>>>>
>>>> skin_semantics = 2
>>>>
>>>>
>>>> ###
>>>>
>>>> [Defaults]
>>>> 
>>>> [[Units]]
>>>> 
>>>> # The following section sets what unit to use for each unit 
>>>> group.
>>>> # NB: The unit is always in the singular. I.e., 
>>>> 'mile_per_hour',
>>>> # NOT 'miles_per_hour'
>>>> [[[Groups]]]
>>>> 
>>>> group_altitude = meter# Options are 'foot' or 
>>>> 'meter'
>>>> group_degree_day = degree_C_day# Options are 
>>>> 'degree_F_day' or 'degree_C_day'
>>>> group_pressure = hPa# Options are 'inHg', 'mmHg', 
>>>> 'mbar', or 'hPa'
>>>> group_rain = mm# Options are 'inch', 'cm', or 'mm'
>>>> group_rainrate = mm_per_hour# Options are 
>>>> 'inch_per_hour', 'cm_per_hour', or 'mm_per_hour'
>>>> group_speed = km_per_hour# Options are 
>>>> 'mile_per_hour', 'km_per_hour', 'knot', or 'meter_per_second'
>>>> group_speed2 = km_per_hour2# Options are 
>>>> 'mile_per_hour2', 'km_per_hour2', 'knot2', or 'meter_per_second2'
>>>> group_temperature = degree_C# Options are 
>>>> 'degree_F' or 'degree_C'
>>>> mbar = "mb"
>>>> hPa = "hPa"
>>>> inHg = "in"
>>>> mm_per_hour = "mm"
>>>> cm_per_hour = "cm"
>>>> inch_per_hour = "in"
>>>> km_per_hour = "km/h"
>>>> knot = "kts"
>>>> meter_per_second ="m/s"
>>>> mile_per_hour ="mph"
>>

Re: [weewx-user] w34 skin issues

[J D]

Hi Sean,

Does the following directory exists
 template = result.csv.tmpl
HTML_ROOT =* /var/www/html/mbcharts* 

The charts are not working because the report generator cannot find the 
result.csv file.
Usually the paths look like this

  [[[DAILYCHARTS]]]
encoding = strict_ascii
template = result.csv.tmpl
HTML_ROOT = /var/www/html/pws/mbcharts

# Charts that plot "by month"
[[[MONTHLYCHARTS]]]
encoding = strict_ascii
template = MM.csv.tmpl
HTML_ROOT = /var/www/html/pws/mbcharts/chartdata

# Charts that plot "by year"
[[[YEARLYCHARTS]]]
encoding = strict_ascii
template = .csv.tmpl
HTML_ROOT = /var/www/html/pws/mbcharts/chartdata

Thanks Jerry

7, Sean Lane wrote:
>
> please see below :
>
>
> ###
> # W34SKIN SKIN CONFIGURATION FILE 
> #
> # Copyright (c) 2018 Tom Keffer > and 
> Matthew Wall  #
> # See the file LICENSE.txt for your rights.   
> #
>
> ###
>
> skin_semantics = 2
>
>
> ###
>
> [Defaults]
> 
> [[Units]]
> 
> # The following section sets what unit to use for each unit 
> group.
> # NB: The unit is always in the singular. I.e., 
> 'mile_per_hour',
> # NOT 'miles_per_hour'
> [[[Groups]]]
> 
> group_altitude = meter# Options are 'foot' or 'meter'
> group_degree_day = degree_C_day# Options are 
> 'degree_F_day' or 'degree_C_day'
> group_pressure = hPa# Options are 'inHg', 'mmHg', 
> 'mbar', or 'hPa'
> group_rain = mm# Options are 'inch', 'cm', or 'mm'
> group_rainrate = mm_per_hour# Options are 
> 'inch_per_hour', 'cm_per_hour', or 'mm_per_hour'
> group_speed = km_per_hour# Options are 
> 'mile_per_hour', 'km_per_hour', 'knot', or 'meter_per_second'
> group_speed2 = km_per_hour2# Options are 
> 'mile_per_hour2', 'km_per_hour2', 'knot2', or 'meter_per_second2'
> group_temperature = degree_C# Options are 'degree_F' 
> or 'degree_C'
> mbar = "mb"
> hPa = "hPa"
> inHg = "in"
> mm_per_hour = "mm"
> cm_per_hour = "cm"
> inch_per_hour = "in"
> km_per_hour = "km/h"
> knot = "kts"
> meter_per_second ="m/s"
> mile_per_hour ="mph"
>
>
>
> [[Labels]]
> 
> day = " day", " days"
> hour = " hour", " hours"
> minute = " minute", " minutes"
> second = " second", " seconds"
> NONE = ""
>
> # Override some labels. No need to identify these as a "Battery"
> # or "Voltage", because that is included in the template.
> [[Generic]]
> txBatteryStatus  = Transmitter
> windBatteryStatus= Wind
> rainBatteryStatus= Rain
> outTempBatteryStatus = Outside Temperature
> inTempBatteryStatus  = Inside Temperature
> consBatteryVoltage   = Console
> heatingVoltage   = Heating
> supplyVoltage= Supply
> referenceVoltage = Reference
>
> # Some specialized labels
> rain_today   = Rain Today
> wind = Wind
>
>
>
> ###
>
> # The CheetahGenerator creates files from templates.  This section
> # specifies which files will be generated from which template.
>
> [CheetahGenerator]
>
> # Possible encodings are 'html_entities', 'utf8', or 'strict_ascii'
> encoding = html_entities
> search_list_extensions = user.stats.MyStats, user.lastrain.lastRainTags
>
> 
> [[WXCHARTDATA]]
>
> 
> # Charts that plot "by day"
>[[[DAILYCHARTS]]]
> encoding = strict_ascii 
> template = result.csv.tmpl
> HTML_ROOT = /var/www/html/mbcharts
>
> # Charts that plot "by month"
> [[[MONTHLYCHARTS]]]
> encoding = strict_ascii
> template = MM.csv.tmpl
> HTML_ROOT = /var/www/html/mbcharts/chartdata
> 
>   
>
> # Charts that plot "by year"
> [[[YEARLYCHARTS]]]
> encoding = strict_ascii
> template = .csv.tmpl
> HTML_ROOT = /var/www/html/mbcharts/chartdata
>  

Re: [weewx-user] Re: w34 skin issues

[J D]

Hi Sean,
So now you have to start looking at weewx conf file, your skin conf file 
and the syslog for answers. This assumes you have not changed anything to 
cause it. Is it possible your charts have been not working since may? If 
the directory is there is the file there and what permissions does it have 
and  what is the owner and group?
Thanks Jerry

On Monday, June 24, 2019 at 11:45:26 AM UTC-7, Sean Lane wrote:
>
> No the file structure is there but the last update was may... 
>
>
> On 6/24/19, J D > wrote: 
> > HI Sean, 
> > There is a 404 for your data 
> >  /wxcharts/wxchartdata/24062019.csv?_=1561401356109:1 Failed to load 
> > resource: the server responded with a status of 404 (Not Found) 
> > 
> > Did you change your directory structure? 
> > Thanks Jerry 
> > 
> > On Monday, June 24, 2019 at 11:15:14 AM UTC-7, Sean Lane wrote: 
> >> 
> >> I have having issues with the stats / archive of data. As you can see 
> by 
> >> my page https://weather.thelanes.ca/ there is data missing. 
> >> 
> >> Anyone? 
> >> 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "weewx-user" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to weewx...@googlegroups.com . 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/weewx-user/78865933-59d5-44fc-9958-78054f24d7d4%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c27889a0-ae60-4353-8d5c-8b848d2d2068%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: w34 skin issues

[J D]

HI Sean,
There is a 404 for your data
 /wxcharts/wxchartdata/24062019.csv?_=1561401356109:1 Failed to load 
resource: the server responded with a status of 404 (Not Found)

Did you change your directory structure?
Thanks Jerry

On Monday, June 24, 2019 at 11:15:14 AM UTC-7, Sean Lane wrote:
>
> I have having issues with the stats / archive of data. As you can see by 
> my page https://weather.thelanes.ca/ there is data missing.
>
> Anyone?
>

-- 
You received this message because you are 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/78865933-59d5-44fc-9958-78054f24d7d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Using Temporal Analysis for Temperature QC?

[J D]

Hi,
Funny you suggested a running mean value. I have done that by making 
changes the qc python code ( it was easier than creating a service for me ) 
and then added a couple fields to the weewx config file under the qc 
section to adjust what my threshold values are and also giving me a way to 
turn it off if needed. Yes I know modifying base code is a maint issue but 
I wanted a quick way to fix my issues with my station and the qc module 
seem to be a perfect place for this.  I did find the service tread when I 
was thinking of this and that approach was way more than I wanted to do.
Just my 2 cents. Jerry

On Sunday, June 23, 2019 at 7:37:50 PM UTC-7, Graham Eddy wrote:
>
> could do something like a highly simplified 1st pass filter i.e. have a 
> running mean value and reject items that deviate more than a tolerance in a 
> single interval - this is really QCing something like the first 
> differential (dx/dt) to filter spikes, even if the spikes are within the 
> [min,max] range of the variable
> 
> *Graham Eddy*
>
> On 24 Jun 2019, at 7:14 am, Thomas Keffer > 
> wrote:
>
> Unfortunately, StdQC can only reject values that are outside of a [min, 
> max] range.
>
> However, this would not be a very hard service to write. Something like 
> (NOT TESTED):
>
>
>

-- 
You received this message because you are 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/9d0bfb2f-b7ba-47f9-9b83-58e908ae116d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: W34 skin - mixed data

[J D]

Hi,
In you weewx conf file you you have your reports set up for metric or us. 
They need to be metric.
Can you post your weewx.conf file. Hide any info you do not want to seen by 
everyone.
Thanks Jerry

On Thursday, June 20, 2019 at 1:31:23 AM UTC-7, Radoslav Drdla wrote:
>
> "No, it does it for all units that are in the "English" database, eg 
> temperature ° C and ° F, speed km / h and mph, air pressure hPa and inHg."
> I explained it wrongly, thinking that the values DISPLAYED in metric units 
> actually correspond to the values that are stored in the database (that is, 
> US), and it applies to everyone that is different from each other, not 
> both. For example, the time is the same in the US and SI, but the speed is 
> in US in mph, in SI in km / h and therefore it is wise to convert, which is 
> not happening here and the value from the database (mph) is not converted 
> to km / h. Ex. the database is 10 mph and displayed as 10 km / h. (instead 
> of the correct 16 km / h).
>
> Dne čtvrtek 20. června 2019 10:19:27 UTC+2 Radoslav Drdla napsal(a):
>>
>> Sorry. I don't know much English and I translate everything using google. 
>> This probably caused a translation error.
>> My database is US (default)
>>
>>
>> Dne čtvrtek 20. června 2019 10:11:35 UTC+2 Andrew Milner napsal(a):
>>>
>>> weewx databases do not use 'english'
>>>
>>> weewx database units are metric or us (which is what you call english) 
>>> or metricwx (a variation of metric)
>>>
>>> so in the weewx database your temperatures will be EITHER Celsius OR 
>>> Farenheit but not both
>>>
>>> Is your database US (the default) or metric?
>>>
>>> the skin should convert from database values to display values as 
>>> required.
>>>
>>>
>>>
>>> On Thursday, 20 June 2019 10:11:43 UTC+3, Radoslav Drdla wrote:

 Hi
 No, it does it for all units that are in the "English" database, eg 
 temperature ° C and ° F, speed km / h and mph, air pressure hPa and inHg. 
 It is well visible on the charts. And when I switch units (with the button 
 at the top right), the page recalculates it, but because the values under 
 which it is based are bad, the result is even worse, such as 170 ° F and 
 so 
 on.
 Simply: in the weewx database, the values are in English units (eg, 
 rainfall is in ing) and weewx converts it to mm before displaying it, but 
 w34 displays it as it is in the database, just changing the label. As a 
 result, only 2.44 mm is displayed in the graph instead of 62 mm, etc. And 
 by changing the units directly on the page, the values are recalculated 
 and 
 the situation gets worse - this time this results in 0.096 inch.
 I set something wrong, but I can't figure out what.
 I attach settings.php files (I didn't edit them), settings1.php, and 
 two screenshots with graphs.

 Dne úterý 18. června 2019 19:27:25 UTC+2 Radoslav Drdla napsal(a):
>
> Hi, I have weewx 3.9.1 installed and I added W34 skin. I had a few 
> problems I solved, but with one I don't know how to go on. The thing is 
> that the data from weewx database is in Imperial units (recommended) and 
> templates are converted to metric. But the W34skin data from 
> "realtime.txt" 
> is displayed correctly, but leaves the data it receives directly from the 
> database in its original units and then the skin displays nonsense. E.g. 
> the current temperature is 25.1 ° C, but the Max / min temperatures are 
> 81.7 ° C / 59.9 ° C (which are actually temperatures in ° F), similarly 
> the 
> wind speed is in km / h, but the values correspond to mph etc.
> My database has data since 2013 and I don't want to lose data or 
> convert it to a metric system. Is it possible to solve it or is W34 skin 
> unusable for me?
>
> You can see here: http://www.pocasi-kucerov.cz/w34/index.php
>
>

-- 
You received this message because you are 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/709ff0da-5550-4c1e-9ee9-7ad38083696e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: W34 skin - mixed data

[J D]

Hi,
Will also need two additional files post here. In the pws directory you 
will find settings1.php and settings.php please post them here.
Thanks Jerry

On Wednesday, June 19, 2019 at 2:51:31 PM UTC-7, J D wrote:
>
> Hi,
> Looking at your data you sent Ian and your website it looks like only a 
> couple of readings are in the wrong units.
> I saw max and min and avg temp for the day, max and min barometer for the 
> day.
> Do you have anymore that I have missed?
> Thanks Jerry
>
> On Wednesday, June 19, 2019 at 1:39:22 AM UTC-7, Radoslav Drdla wrote:
>>
>> Hi Ion
>>
>> Since you have not received attachments in the e-mail, I give them here.
>>
>>
>> Dne úterý 18. června 2019 19:27:25 UTC+2 Radoslav Drdla napsal(a):
>>>
>>> Hi, I have weewx 3.9.1 installed and I added W34 skin. I had a few 
>>> problems I solved, but with one I don't know how to go on. The thing is 
>>> that the data from weewx database is in Imperial units (recommended) and 
>>> templates are converted to metric. But the W34skin data from "realtime.txt" 
>>> is displayed correctly, but leaves the data it receives directly from the 
>>> database in its original units and then the skin displays nonsense. E.g. 
>>> the current temperature is 25.1 ° C, but the Max / min temperatures are 
>>> 81.7 ° C / 59.9 ° C (which are actually temperatures in ° F), similarly the 
>>> wind speed is in km / h, but the values correspond to mph etc.
>>> My database has data since 2013 and I don't want to lose data or convert 
>>> it to a metric system. Is it possible to solve it or is W34 skin unusable 
>>> for me?
>>>
>>> You can see here: http://www.pocasi-kucerov.cz/w34/index.php
>>>
>>>

-- 
You received this message because you are 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/0d986801-d6d1-491c-980a-7c70be807d2e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: W34 skin - mixed data

[J D]

Hi,
Looking at your data you sent Ian and your website it looks like only a 
couple of readings are in the wrong units.
I saw max and min and avg temp for the day, max and min barometer for the 
day.
Do you have anymore that I have missed?
Thanks Jerry

On Wednesday, June 19, 2019 at 1:39:22 AM UTC-7, Radoslav Drdla wrote:
>
> Hi Ion
>
> Since you have not received attachments in the e-mail, I give them here.
>
>
> Dne úterý 18. června 2019 19:27:25 UTC+2 Radoslav Drdla napsal(a):
>>
>> Hi, I have weewx 3.9.1 installed and I added W34 skin. I had a few 
>> problems I solved, but with one I don't know how to go on. The thing is 
>> that the data from weewx database is in Imperial units (recommended) and 
>> templates are converted to metric. But the W34skin data from "realtime.txt" 
>> is displayed correctly, but leaves the data it receives directly from the 
>> database in its original units and then the skin displays nonsense. E.g. 
>> the current temperature is 25.1 ° C, but the Max / min temperatures are 
>> 81.7 ° C / 59.9 ° C (which are actually temperatures in ° F), similarly the 
>> wind speed is in km / h, but the values correspond to mph etc.
>> My database has data since 2013 and I don't want to lose data or convert 
>> it to a metric system. Is it possible to solve it or is W34 skin unusable 
>> for me?
>>
>> You can see here: http://www.pocasi-kucerov.cz/w34/index.php
>>
>>

-- 
You received this message because you are 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/249083c6-25cb-4204-bd2c-5b3607805213%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx Highcharts and yearly dewpoint

[J D]

Hi Gary,
Thanks for the info. 
No need to worry about it. I was going to create new extension anyway since 
I have a number of other charts to add. Will use what you have there as a 
base for extension. Thanks for the great start.
Jerry

On Tuesday, June 18, 2019 at 1:45:29 AM UTC-7, gjr80 wrote:
>
> Hi Jerry,
>
> I presume when you mention 'highcharts extension and notice in the 3.9.1 
> release' you mean the latest release of my weewx-highcharts extension 
> (v0.2.2) running under WeeWX v3.9.1.
>
> Short answer is I don't know, likely I became fixated on a single 
> observation per candlestick plot and just forgot. I guess you have found 
> adding it in is fairly much a case of following the pattern used by the 
> other obs. I do intend reworking the weewx-highcharts extension to be more 
> efficient in its operation and more user friendly in its use. Unfortunately 
> this rework and any changes are going to have to wait until late this year 
> as shortly I will not have any free time for WeeWX for the next few months.
>
> Gary
>
> On Tuesday, 18 June 2019 04:34:57 UTC+10, J D wrote:
>>
>> Hi Gary,
>>
>> Working on using weewx highcharts extension and notice in the 3.9.1 
>> release there is no yearly dewpoint code in highchartsSearchX.py and was 
>> wondering if there is a reason for that.
>> I have added the yearly dewpoint code to my version and it is working 
>> just fine. So would be nice to get this into weewx but not sure if it is in 
>> a later release or what.
>> Thanks Jerry
>>
>

-- 
You received this message because you are 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/e8cdeee2-8206-4196-a091-9cb35a86d72d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Weewx Highcharts and yearly dewpoint

[J D]

Hi Gary,

Working on using weewx highcharts extension and notice in the 3.9.1 release 
there is no yearly dewpoint code in highchartsSearchX.py and was wondering 
if there is a reason for that.
I have added the yearly dewpoint code to my version and it is working just 
fine. So would be nice to get this into weewx but not sure if it is in a 
later release or what.
Thanks Jerry

-- 
You received this message because you are 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/0d96b886-d007-4ec6-a0af-1c9c936320eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Highcharts and weewx changes

[J D]

Hi Gary,
I update the issue with the files. 
If you are ok with moving forward I will then create a pull request with 
fork in your weewx-highcharts repo to put the files in for a review.
Thanks for your time.
Jerry

On Thursday, June 6, 2019 at 2:03:43 AM UTC-7, gjr80 wrote:
>
> Jerry,
>
> I see you have also raised an issue on the weewx-highcharts repo. You can 
> always raise a pull request on my repo with your changes, though if its 
> only a couple of lines that might be more effort than its worth. Happy to 
> look at just the extra lines or a modified file, just include the lines or 
> attach the modified file through the issue you raised.
>
> Gary
>
> On Thursday, 6 June 2019 12:00:31 UTC+10, J D wrote:
>>
>> Hi Gary,
>> I have some enhancements I would like to make to plots.js to have a 
>> DatePicker for the range selector and to send in the units for display and 
>> to handle clicking on a graph point. What is the best way to go with this?
>> Thanks Jerry
>>
>

-- 
You received this message because you are 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/11ff89af-5eba-464c-b907-f92d3d4d1270%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Highcharts and weewx changes

[J D]

Hi Gary,
I have some enhancements I would like to make to plots.js to have a 
DatePicker for the range selector and to send in the units for display and 
to handle clicking on a graph point. What is the best way to go with this?
Thanks Jerry

-- 
You received this message because you are 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/4d855c70-7ec1-4a3d-967c-54e6e61932dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] WMR200: rain is always zero

[Patrick J]

Hi,

I connected a RaspBerry PI to my WMR200 weather station. I am using the 
latest version of weewx, with version 3.3.4 of driver for WMR200.

I let the system run for a couple of weeks, and noticed that the field rain 
in the archive table is always at 0 or null, even though we had a lot of 
rain. But the field rainRate has different values. As per the user guide, I 
ran weewx directly to see the packets that come out of the station, and 
here is the outcome:

pi@raspberrypi:/usr/share/weewx $ sudo weewxd /etc/weewx/weewx.conf
REC:2018-04-27 16:10:54 UTC (1524845454) altimeter: 29.5299875, 
appTemp: 63.3209288277, barometer: 29.5608564278, cloudbase: 7892.47484776, 
dateTime: 1524845454.0, dewpoint: 36.7002569534, ET: None, forecastIcon: 1, 
heatindex: None, hourRain: 0.0, humidex: 68.54, inDewpoint: 46.1216028652, 
inHeatindex: None, inHumidity: 43, inTemp: 69.62, interval: 1, maxSolarRad: 
None, outHumidity: 31, outTemp: 68.54, pressure: 28.880327775, rain: 0.0, 
rain24: 1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, 
windchill: None, windDir: 292.5, windGust: 5.59235462985, windrun: 
33.7987000882, windSpeed: 4.25018951868
REC:2018-04-27 16:11:54 UTC (1524845514) altimeter: 29.5299875, 
appTemp: 63.7582794974, barometer: 29.5610911259, cloudbase: 7704.13634321, 
dateTime: 1524845514.0, dewpoint: 37.3489463735, ET: None, forecastIcon: 1, 
heatindex: None, hourRain: 0.0, humidex: 68.36, inDewpoint: 46.2838848687, 
inHeatindex: None, inHumidity: 43, inTemp: 69.8, interval: 1, maxSolarRad: 
None, outHumidity: 32, outTemp: 68.36, pressure: 28.880327775, rain: 0.0, 
rain24: 
1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, windchill: 
None, windDir: 202.5, windGust: 4.25018951868, windrun: 33.8695365802, 
windSpeed: 3.35541277791
REC:2018-04-27 16:12:54 UTC (1524845574) altimeter: 29.5299875, 
appTemp: 63.0022794974, barometer: 29.5610911259, cloudbase: 7704.13634321, 
dateTime: 1524845574.0, dewpoint: 37.3489463735, ET: None, forecastIcon: 1, 
heatindex: None, hourRain: 0.0, humidex: 68.36, inDewpoint: 46.2838848687, 
inHeatindex: None, inHumidity: 43, inTemp: 69.8, interval: 1, maxSolarRad: 
None, outHumidity: 32, outTemp: 68.36, pressure: 28.880327775, rain: 0.0, 
rain24: 1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, 
windchill: None, windDir: 157.5, windGust: None, windGustDir: None, 
windrun: 33.9254601265, windSpeed: 4.69757788907
REC:2018-04-27 16:13:54 UTC (1524845634) altimeter: 29.5299875, 
appTemp: 63.2542794974, barometer: 29.5610911259, cloudbase: 7704.13634321, 
dateTime: 1524845634.0, dewpoint: 37.3489463735, ET: None, forecastIcon: 1, 
heatindex: None, hourRain: 0.0, humidex: 68.36, inDewpoint: 46.2838848687, 
inHeatindex: None, inHumidity: 43, inTemp: 69.8, interval: 1, maxSolarRad: 
None, outHumidity: 32, outTemp: 68.36, pressure: 28.880327775, rain: 0.0, 
rain24: 1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, 
windchill: None, windDir: 202.5, windGust: 5.81604881504, windrun: 
34.0037530913, windSpeed: 4.25018951868
REC:2018-04-27 16:14:54 UTC (1524845694) altimeter: 29.5299875, 
appTemp: 62.4982794974, barometer: 29.5610911259, cloudbase: 7704.13634321, 
dateTime: 1524845694.0, dewpoint: 37.3489463735, ET: None, forecastIcon: 1, 
heatindex: None, hourRain: 0.0, humidex: 68.36, inDewpoint: 46.2838848687, 
inHeatindex: None, inHumidity: 43, inTemp: 69.8, interval: 1, maxSolarRad: 
None, outHumidity: 32, outTemp: 68.36, pressure: 28.880327775, rain: 0.0, 
rain24: 1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, 
windchill: None, windDir: 202.5, windGust: None, windGustDir: None, 
windrun: 34.0745895833, windSpeed: 5.59235462985
REC:2018-04-27 16:15:54 UTC (1524845754) altimeter: 29.5299875, 
appTemp: 62.6242794974, barometer: 29.5610911259, cloudbase: 7704.13634321, 
dateTime: 1524845754.0, dewpoint: 37.3489463735, ET: None, forecastIcon: 1, 
heatindex: None, hourRain: 0.0, humidex: 68.36, inDewpoint: 46.2838848687, 
inHeatindex: None, inHumidity: 43, inTemp: 69.8, interval: 1, maxSolarRad: 
None, outHumidity: 32, outTemp: 68.36, pressure: 28.880327775, rain: 0.0, 
rain24: 1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, 
windchill: None, windDir: 202.5, windGust: 6.7108282, windrun: 
34.1677954938, windSpeed: 5.36866044465
REC:2018-04-27 16:16:54 UTC (1524845814) altimeter: 29.5299875, 
appTemp: 62.6242794974, barometer: 29.5610911259, cloudbase: 7704.13634321, 
dateTime: 1524845814.0, dewpoint: 37.3489463735, ET: None, forecastIcon: 1, 
heatindex: None, hourRain: 0.0, humidex: 68.36, inDewpoint: 46.2838848687, 
inHeatindex: None, inHumidity: 43, inTemp: 69.8, interval: 1, maxSolarRad: 
None, outHumidity: 32, outTemp: 68.36, pressure: 28.880327775, rain: 0.0, 
rain24: 1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, 
windchill: None, windDir: 202.5, windGust: 6.7108282, windrun: 
34.2572731679, windSpeed: 5.36866044465
REC:2018-04-27 

[weewx-user] Re: Oregon WMR200 initial load issues

[Patrick J]

Hi,

I just tried the new driver you attached, and it is working much better, as 
the archive records are now stored in the database :-)

However, there is still an issue, as you can see in this log extract:

Apr 27 07:23:31 raspiMeteo weewx[4406]: wmr200: MainThread: I Time drift 
between host and console in seconds:32

Apr 27 07:24:03 raspiMeteo weewx[4406]: wmr200: MainThread: I genStartup() 
Still receiving archive packets cnt:0 len:1

Apr 27 07:24:03 raspiMeteo weewx[4406]: wmr200: MainThread: I Using pc time 
adjusting archive record time by 32 sec 2017-04-27 09:18:00 CEST 
(1493277480) => 2017-04-27 09:18:32 CEST (1493277512)

Apr 27 07:24:03 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 
09:18:32 CEST (1493277512) to database 'weewx.sdb'

Apr 27 07:24:04 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 
09:18:32 CEST (1493277512) to daily summary in 'weewx.sdb'

Apr 27 07:24:06 raspiMeteo weewx[4406]: wmr200: MainThread: I genStartup() 
Still receiving archive packets cnt:1 len:1

Apr 27 07:24:06 raspiMeteo weewx[4406]: wmr200: MainThread: I Using pc time 
adjusting archive record time by 32 sec 2017-04-27 09:19:00 CEST 
(1493277540) => 2017-04-27 09:19:32 CEST (1493277572)

Apr 27 07:24:06 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 
09:19:32 CEST (1493277572) to database 'weewx.sdb'

Apr 27 07:24:06 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 
09:19:32 CEST (1493277572) to daily summary in 'weewx.sdb'

Apr 27 07:24:08 raspiMeteo weewx[4406]: wmr200: MainThread: I genStartup() 
Still receiving archive packets cnt:2 len:1

Apr 27 07:24:08 raspiMeteo weewx[4406]: wmr200: MainThread: I Using pc time 
adjusting archive record time by 32 sec 2017-04-27 09:20:00 CEST 
(1493277600) => 2017-04-27 09:20:32 CEST (1493277632)

Apr 27 07:24:08 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 
09:20:32 CEST (1493277632) to database 'weewx.sdb'

Apr 27 07:24:08 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 
09:20:32 CEST (1493277632) to daily summary in 'weewx.sdb'

Apr 27 07:24:11 raspiMeteo weewx[4406]: wmr200: MainThread: I genStartup() 
Still receiving archive packets cnt:3 len:1

Apr 27 07:24:11 raspiMeteo weewx[4406]: wmr200: MainThread: I Using pc time 
adjusting archive record time by 32 sec 2017-04-27 09:21:00 CEST 
(1493277660) => 2017-04-27 09:21:32 CEST (1493277692)

Apr 27 07:24:11 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 
09:21:32 CEST (1493277692) to database 'weewx.sdb'

Apr 27 07:24:12 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 
09:21:32 CEST (1493277692) to daily summary in 'weewx.sdb'

Apr 27 07:24:13 raspiMeteo weewx[4406]: wmr200: MainThread: I genStartup() 
Still receiving archive packets cnt:4 len:1

Apr 27 07:24:13 raspiMeteo weewx[4406]: wmr200: MainThread: I Using pc time 
adjusting archive record time by 32 sec 2017-04-27 09:22:00 CEST 
(1493277720) => 2017-04-27 09:22:32 CEST (1493277752)

Apr 27 07:24:13 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 
09:22:32 CEST (1493277752) to database 'weewx.sdb'

Apr 27 07:24:13 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 
09:22:32 CEST (1493277752) to daily summary in 'weewx.sdb'

Apr 27 07:24:15 raspiMeteo weewx[4406]: wmr200: MainThread: I genStartup() 
Still receiving archive packets cnt:5 len:1

Apr 27 07:24:15 raspiMeteo weewx[4406]: wmr200: MainThread: I Using pc time 
adjusting archive record time by 32 sec 2017-04-27 09:23:00 CEST 
(1493277780) => 2017-04-27 09:23:32 CEST (1493277812)

Apr 27 07:24:15 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 
09:23:32 CEST (1493277812) to database 'weewx.sdb'

Apr 27 07:24:15 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 
09:23:32 CEST (1493277812) to daily summary in 'weewx.sdb'

Apr 27 07:26:16 raspiMeteo weewx[4406]: wmr200: MainThread: I genStartup() 
phase exiting since looks like all archive packets have been retrieved 
after 120 sec cnt:6

Apr 27 07:26:16 raspiMeteo rsyslogd-2007: action 'action 17' suspended, 
next retry is Thu Apr 27 07:27:46 2017 [try http://www.rsyslog.com/e/2007 ]

Apr 27 07:26:16 raspiMeteo weewx[4406]: wmr200: MainThread: I genStartup() 
Yielded 6 packets in 300 sec  between these dates 2017-04-27 09:18:32 CEST 
(1493277512) ==> 2017-04-27 09:23:32 CEST (1493277812)

Apr 27 07:26:16 raspiMeteo weewx[4406]: wmr200: MainThread: I genStartup() 
Average packets per minute:1.20

Apr 27 07:26:16 raspiMeteo weewx[4406]: engine: Starting main packet loop.

Apr 27 07:27:16 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 
09:27:00 CEST (1493278020) to database 'weewx.sdb'

Apr 27 07:27:16 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 
09:27:00 CEST (1493278020) to daily summary in 'weewx.sdb'

Apr 27 07:27:46 raspiMeteo weewx[4406]: cheetahgenerator: Generated 14 
files for report StandardReport in 28.25 seconds

Apr 27 07:27:46 raspiMeteo rsyslogd-2007: action 'action 17' suspended, 
next retry is Thu Apr 27 

[weewx-user] Re: Oregon WMR200 initial load issues

[Patrick J]

Some news: as mentioned in my previous post, I decided to reinstall WeeWX 
with the Debian package. But this didn't change anything to my issue, 
archive records are rejected because of this NOT NULL constraint on 
archive.interval.

I decided to clear the data log on the WMR200. I first stopped WeeWX, 
cleared the log, and restarted the service. One archive record, generated 
between the clear and the restart was then rejected, but then WeeWX started 
on process the live records, and these ones finally made their way into the 
database! 

This is a step forward, but I still wanted to see what happened if WeeWX 
was not catching the records on the fly. So I stopped the service for 15 
minutes, and then restarted it. Unfortunately, the archive records recorded 
during this period were also rejected:

Apr 26 12:28:51 raspiMeteo weewx[2490]: wmr200: MainThread: I genStartup() 
Still receiving archive packets cnt:7 len:1

Apr 26 12:28:51 raspiMeteo weewx[2490]: wmr200: MainThread: I Using pc time 
adjusting archive record time by 14 sec 2017-04-26 14:26:00 CEST 
(1493209560) => 2017-04-26 14:26:14 CEST (1493209574)

Apr 26 12:28:51 raspiMeteo weewx[2490]: manager: Unable to add record 
2017-04-26 14:26:14 CEST (1493209574) to database 'weewx.sdb': NOT NULL 
constraint failed: archive.interval

Apr 26 12:28:54 raspiMeteo weewx[2490]: wmr200: MainThread: I genStartup() 
Still receiving archive packets cnt:8 len:1

Apr 26 12:28:54 raspiMeteo weewx[2490]: wmr200: MainThread: I Using pc time 
adjusting archive record time by 14 sec 2017-04-26 14:27:00 CEST 
(1493209620) => 2017-04-26 14:27:14 CEST (1493209634)

Apr 26 12:28:54 raspiMeteo weewx[2490]: manager: Unable to add record 
2017-04-26 14:27:14 CEST (1493209634) to database 'weewx.sdb': NOT NULL 
constraint failed: archive.interval

Apr 26 12:30:55 raspiMeteo weewx[2490]: wmr200: MainThread: I genStartup() 
phase exiting since looks like all archive packets have been retrieved 
after 120 sec cnt:9

Apr 26 12:30:55 raspiMeteo rsyslogd-2007: action 'action 17' suspended, 
next retry is Wed Apr 26 12:32:25 2017 [try http://www.rsyslog.com/e/2007 ]

Apr 26 12:30:55 raspiMeteo weewx[2490]: wmr200: MainThread: I genStartup() 
Yielded 9 packets in 480 sec  between these dates 2017-04-26 14:19:14 CEST 
(1493209154) ==> 2017-04-26 14:27:14 CEST (1493209634)

Apr 26 12:30:55 raspiMeteo weewx[2490]: wmr200: MainThread: I genStartup() 
Average packets per minute:1.125000

Apr 26 12:30:55 raspiMeteo weewx[2490]: engine: Starting main packet loop.

Apr 26 12:31:19 raspiMeteo weewx[2490]: manager: Added record 2017-04-26 
14:31:00 CEST (1493209860) to database 'weewx.sdb'

Apr 26 12:31:19 raspiMeteo weewx[2490]: manager: Added record 2017-04-26 
14:31:00 CEST (1493209860) to daily summary in 'weewx.sdb'

Apr 26 12:31:49 raspiMeteo weewx[2490]: cheetahgenerator: Generated 14 
files for report StandardReport in 28.43 seconds

Apr 26 12:31:54 raspiMeteo weewx[2490]: imagegenerator: Generated 12 images 
for StandardReport in 4.01 seconds

Apr 26 12:31:54 raspiMeteo weewx[2490]: copygenerator: copied 9 files to 
/var/www/html/weewx

Apr 26 12:32:15 raspiMeteo weewx[2490]: manager: Added record 2017-04-26 
14:32:00 CEST (1493209920) to database 'weewx.sdb'

Apr 26 12:32:15 raspiMeteo weewx[2490]: manager: Added record 2017-04-26 
14:32:00 CEST (1493209920) to daily summary in 'weewx.sdb'

Apr 26 12:32:26 raspiMeteo weewx[2490]: cheetahgenerator: Generated 14 
files for report StandardReport in 8.97 seconds


So there is still an issue... And in addition, some records were lost, the 
ones from 14:28, 14:29 and 14:30.

I would really appreciate if someone could help.

Patrick 

-- 
You received this message because you are 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: Oregon WMR200 initial load issues

[Patrick J]

I just checked, and NTP is configured on the pi:

ntpq> pe

 remote   refid  st t when poll reach   delay   offset  
jitter

==

+bb8.dousse.eu   212.83.179.156   3 u  905 1024  377   21.599   -1.943   
4.789

-62-210-28-176.r 84.255.209.794 u  812 1024  377   17.188   -1.550   
8.901

*mica.ad-notam.n 131.188.3.2202 u   92 1024  375   70.345   22.372  
21.989

+194.177.34.116  163.172.61.210   3 u  917 1024  373   19.044   -1.883   
9.531

This explains why the "date" command displays the correct time. The fake hw 
clock is still running on the pi, but as I didn't so far run weewx as a 
service, but rather launched it manually, NTP has done its job before weewx 
starts processing archive records, so this should not be an issue.

I installed weewx with the "setup.py" method. As I don't know what else to 
try, I will fully uninstall it and try the debian package method...

Patrick

-- 
You received this message because you are 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: Oregon WMR200 initial load issues

[Patrick J]

My pi does not have a real clock. I did not remove the fake hardware clock, 
nor did I configure NTP, as I thought it was already included in Raspbian. 
Indeed, when I type "date" on the Linux command prompt, the current exact 
date is returned. But I will in any case check these points.

The database is in fact empty. I installed sqlite on the pi, I have zero 
records in the archive table. Weewx rejects systematically all the history 
records that come from the weather station...

Patrick 

On Wednesday, April 26, 2017 at 7:28:50 AM UTC+2, mwall wrote:
>
> On Tuesday, April 25, 2017 at 8:38:50 AM UTC-4, Patrick J wrote:
>>
>> After a while, there is no more output from weewx, but in the log I can 
>> see this type of lines: "wmr200: MainThread: I genStartup() Discarding 
>> received archive record exceeding archive interval cnt:10 threshold:604800 
>> timestamp:2017-04-22 11:07:27 UTC (1492859247)".
>>
>> It seems that it has now reached the records corresponding to my usage, 
>> but it is discarding them... What should I do to get things right?
>>
>
> does your pi have a real clock on it?  (you would have to have added it 
> one - they do not come with a clock)
>
> did you remove the fake hardware clock software?
>
> is the pi configured to use ntp?
>
> your weewx database is probably full of data with wonky timestamps.  you 
> can start over by doing this:
>
> 1) stop weewx
> sudo /etc/init.d/weewx stop
>
> 2) move the database aside
> sudo mv /home/weewx/archive/weewx.sdb /home/weewx/archive/weewx.sdb.bak
>
> 3) start weewx
> sudo /etc/init.d/weewx start
>
> it could take awhile to read all of the records from the wmr200 logger, so 
> be patient and watch the log.
>
> 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: Oregon WMR200 initial load issues

[Patrick J]

It may be useful to list what is in the beginning of the log (debug = 1):

Apr 25 15:37:15 raspiMeteo weewx[906]: engine: Initializing weewx version 
3.7.1
Apr 25 15:37:15 raspiMeteo weewx[906]: engine: Using Python 2.7.9 (default, 
Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
Apr 25 15:37:15 raspiMeteo weewx[906]: engine: Platform 
Linux-4.4.50+-armv6l-with-debian-8.0
Apr 25 15:37:15 raspiMeteo weewx[906]: engine: Locale is 'en_GB.UTF-8'
Apr 25 15:37:15 raspiMeteo weewx[906]: engine: Using configuration file 
/home/weewx/weewx.conf
Apr 25 15:37:15 raspiMeteo weewx[906]: engine: debug is 1
Apr 25 15:37:15 raspiMeteo weewx[906]: engine: Initializing engine
Apr 25 15:37:15 raspiMeteo weewx[906]: engine: Loading station type WMR200 
(weewx.drivers.wmr200)
Apr 25 15:37:15 raspiMeteo weewx[906]: wmr200: MainThread: I driver version 
is 3.3.1
Apr 25 15:37:15 raspiMeteo weewx[906]: wmr200: MainThread: I sensor map is 
{'outTempBatteryStatus': 'battery_status_out', 'outHumidity': 'humidity_1', 
'rainRate': 'rain_rate', 'heatindex4': 'heatindex_5', 'rainTotal': 
'rain_total', 'rainBatteryStatus': 'battery_status_rain', 'heatindex6': 
'heatindex_7', 'extraTemp5': 'temperature_6', 'uvFault': 'uv_fault', 
'extraTemp2': 'temperature_3', 'heatindex': 'heatindex_1', 'extraTemp3': 
'temperature_4', 'rain24': 'rain_24', 'inHeatindex': 'heatindex_0', 
'inTemp': 'temperature_0', 'extraTemp1': 'temperature_2', 'hourRain': 
'rain_hour', 'windFault': 'wind_fault', 'windchill': 'windchill', 
'clockUnsynchronized': 'clock_unsynchronized', 'extraTemp7': 
'temperature_8', 'rain': 'rain', 'forecastIcon': 'forecast_icon', 
'pressure': 'pressure', 'extraHumid4': 'humidity_5', 'extraHumid5': 
'humidity_6', 'extraHumid2': 'humidity_3', 'extraHumid3': 'humidity_4', 
'extraHumid1': 'humidity_2', 'extraTemp6': 'temperature_7', 'heatindex5': 
'heatindex_6', 'extraTemp4': 'temperature_5', 'heatindex7': 'heatindex_8', 
'altimeter': 'altimeter', 'heatindex1': 'heatindex_2', 'heatindex2': 
'heatindex_3', 'heatindex3': 'heatindex_4', 'extraHumid6': 'humidity_7', 
'extraHumid7': 'humidity_8', 'windBatteryStatus': 'battery_status_wind', 
'UV': 'uv', 'rainFault': 'rain_fault', 'windDir': 'wind_dir', 'outTemp': 
'temperature_1', 'windSpeed': 'wind_speed', 'inHumidity': 'humidity_0', 
'outTempFault': 'out_fault', 'windGust': 'wind_gust', 'uvBatteryStatus': 
'battery_status_uv'}
Apr 25 15:37:15 raspiMeteo weewx[906]: wmr200: MainThread: I Created 
watchdog thread to poke for live data every 30 seconds
Apr 25 15:37:15 raspiMeteo weewx[906]: wmr200: MainThread: I Created USB 
polling thread to read block on device
Apr 25 15:37:15 raspiMeteo weewx[906]: wmr200: MainThread: I Reset console 
device
Apr 25 15:37:15 raspiMeteo weewx[906]: wmr200: Thread-2: I USB polling 
device thread for live data launched
Apr 25 15:37:15 raspiMeteo weewx[906]: wmr200: Thread-2: I USB polling 
device thread signaled to start
Apr 25 15:37:16 raspiMeteo weewx[906]: wmr200: MainThread: D Configuration 
setup
Apr 25 15:37:16 raspiMeteo weewx[906]: wmr200: MainThread: D   Log sensor 
faults: True
Apr 25 15:37:16 raspiMeteo weewx[906]: wmr200: MainThread: D   Using PC 
Time: True
Apr 25 15:37:16 raspiMeteo weewx[906]: wmr200: MainThread: D   Erase 
archive data: False
Apr 25 15:37:16 raspiMeteo weewx[906]: wmr200: MainThread: D   Archive 
interval: 300
Apr 25 15:37:16 raspiMeteo weewx[906]: wmr200: MainThread: D   Archive 
threshold: 604800
Apr 25 15:37:16 raspiMeteo weewx[906]: wmr200: Thread-1: I Started watchdog 
thread live data
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: Loading service 
weewx.engine.StdTimeSynch
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: Loading service 
weewx.engine.StdConvert
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: StdConvert target unit is 0x1
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: Finished loading service 
weewx.engine.StdConvert
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: Loading service 
weewx.engine.StdCalibrate
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: Finished loading service 
weewx.engine.StdCalibrate
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: Loading service 
weewx.engine.StdQC
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: Finished loading service 
weewx.engine.StdQC
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Apr 25 15:37:16 raspiMeteo weewx[906]: wxcalculate: The following values 
will be calculated: barometer=prefer_hardware, windchill=hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=hardware, 
windrun=prefer_hardware, heatindex=hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Apr 25 15:37:16 raspiMeteo weewx[906]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA,