[weewx-user] Re: How to change frequency of realtime.txt updates

[Andrew Milner]

I see from the web that on the envoy the barometer only updates every 
minute - do not know if this is significant or not.



On Tuesday, 26 March 2019 00:25:01 UTC+2, gjr80 wrote:
>
> Hi,
>
> If you are using a Davis Vantage station and the crt extension is bound to 
> loop then you should be seeing realtime.txt being generated every 2.5 odd 
> seconds. If you have changed the binding to archive then based on the 
> weewx.conf extract you provided it should be generated every 5minutes. I 
> am not sure where the one minute update you mention comes from, it should 
> not be happening. How are you checking how often realtime.txt is 
> generated? Are you checking the file on the WeeWX machine or are you 
> checking on a web server or some other server? If you are checking on a 
> machine other than the WeeWX machine remember that there must be some 
> mechanism to transfer realtime.txt from the WeeWX machine to the remote 
> server and it may be that transfer mechanism that is only occurring every 
> minute.
>
> Unfortunately the crt extension does not give us too much extra debug info 
> but it may help to get a clearer picture of what is going on if you post a 
> debug log extract. To do this edit weewx.conf, set debug=1, save 
> weewx.conf and then restart WeeWX. Let WeeWX run for at least 10 minutes 
> and then take a log extract showing the entire WeeWX startup and the 
> following 10 minutes of log activity. The log should be in /var/log/syslog 
> unless you have changed it. Post the log extract without any changes.
>
> At the end of the day though you will have two choices in terms of 
> realtime.txt update period, either on every loop packet (2.5 odd seconds) 
> or every archive interval (currently 5 minutes).
>
> Gary
>
> On Tuesday, 26 March 2019 06:16:32 UTC+10, G400 wrote:
>>
>> Davis Vantage2 getting data from Weather Envoy USD->Serial
>>
>> This is my current setting:
>> StdArchive]
>> 
>> # If the station hardware supports data logging then the archive 
>> interval
>> # will be downloaded from the station. Otherwise, specify it (in 
>> seconds).
>> archive_interval = 300
>>
>>
>> Currently realtime.txt is created every 60s.
>> How do I relate this to archive interval?
>>
>> I want realtime.txt to be updated every 10s.
>>
>>
>> On Monday, March 25, 2019 at 8:41:25 PM UTC+1, Andrew Milner wrote:
>>>
>>> according to the wiki the generation can be tied to loop or archive - 
>>> which is yours tied to?  It should be to loop (which is the default) if you 
>>> want it creating more often than the archive interval.
>>>
>>> if to loop then it depends on your station type - what kind of station 
>>> do you have?  Some stations (eg FineOffset) cannot produce loop data any 
>>> faster than say  every 48 seconds
>>>
>>> if to archive then changing the archive interval will also change the 
>>> frequency of creating the file.
>>>
>>> On Monday, 25 March 2019 21:34:37 UTC+2, G400 wrote:

 How can I modify the frequency of Cumulus formatted raltime.txt output 
 file using crt plugin (https://github.com/weewx/weewx/wiki/crt)?
 G400

>>>

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

Re: [weewx-user] unsupported locale setting

[Thomas Keffer]

To start, take a look at my Python 3 transition document
.

If you do not understand the difference between byte strings and unicode,
don't do anything before reading this old, but still very useful, article

.

-tk

On Mon, Mar 25, 2019 at 6:23 PM Pat  wrote:

> I missed this one, but just caught it. Thanks for the tips.
>
> #1. Yes, it's a hack. So much so that in the comment above it I gave
> credit to the original source. :) For Python3, do you have an example I
> could look at? I'm not familiar with reading the byte strings as you've
> mentioned. TBH, locale is a newer topic for me to work with.
> #2. Ok, thanks I'll update that
>
>
>
> On Saturday, March 23, 2019 at 9:51:32 PM UTC-4, Thomas Keffer wrote:
>>
>> I suspect one of your "LC" settings is missing. Run the command "locale"
>> (without the -a flag). You should see something like:
>> LANG=en_US.UTF-8
>> LANGUAGE=
>> LC_CTYPE="en_US.UTF-8"
>> LC_NUMERIC="en_US.UTF-8"
>> LC_TIME="en_US.UTF-8"
>> LC_COLLATE="en_US.UTF-8"
>> LC_MONETARY="en_US.UTF-8"
>> LC_MESSAGES="en_US.UTF-8"
>> LC_PAPER="en_US.UTF-8"
>> LC_NAME="en_US.UTF-8"
>> LC_ADDRESS="en_US.UTF-8"
>> LC_TELEPHONE="en_US.UTF-8"
>> LC_MEASUREMENT="en_US.UTF-8"
>> LC_IDENTIFICATION="en_US.UTF-8"
>> LC_ALL=
>>
>> Having said this, Pat, if you're listening, two issues:
>>
>>1. The Belchertown skins sets a default encoding by reloading sys,
>>then making use of the otherwise hidden function
>>sys.setdefaultencoding(). This is a hack, and won't work under Python
>>3. Instead, you need to read byte strings in and explicitly decode them
>>(instead of relying on a default encoding).
>>2. The line locale.setlocale(locale.LC_ALL, "") should not be
>>necessary. This is already done in user/extensions.py.
>>
>> -tk
>>
>>
>>
>>
>>
>> On Sat, Mar 23, 2019 at 11:00 AM G400  wrote:
>>
>>> reportengine: Caught unrecoverable exception in generator
>>> 'weewx.cheetahgenerator.CheetahGenerator'
>>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]:   unsupported
>>> locale setting
>>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]:   Traceback
>>> (most recent call last):
>>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]: File
>>> "/home/weewx/bin/weewx/reportengine.py", line 204, in run
>>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]: 
>>> obj.start()
>>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]: File
>>> "/home/weewx/bin/weewx/reportengine.py", line 300, in start
>>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]: 
>>> self.run()
>>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]: File
>>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 157, in run
>>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]: 
>>> self.initExtensions(gen_dict[section_name])
>>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]: File
>>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 199, in initExtensions
>>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]:   class_
>>> = weeutil.weeutil._get_object(x)
>>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]: File
>>> "/home/weewx/bin/weeutil/weeutil.py", line 1130, in _get_object
>>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]:   mod =
>>> __import__(module)
>>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]: File
>>> "/home/weewx/bin/user/belchertown.py", line 26, in 
>>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]: 
>>> locale.setlocale(locale.LC_ALL, "")
>>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]: File
>>> "/usr/lib/python2.7/locale.py", line 581, in setlocale
>>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]:   return
>>> _setlocale(category, locale)
>>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]:   Error:
>>> unsupported locale setting
>>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]:   Generator
>>> terminated
>>>
>>> My locale settings are as follows:
>>> locale -a
>>> C
>>> C.UTF-8
>>> en_US.utf8
>>> POSIX
>>>
>>> Content of /etc/default/locale
>>> #  File generated by update-locale
>>> LANG=en_US.UTF-8
>>>
>>> What else do I need to check to fix this error?
>>>
>>> --
>>> You received this message because you are subscribed 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.
>>> 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...@googlegr

Re: [weewx-user] unsupported locale setting

[Pat]

I missed this one, but just caught it. Thanks for the tips.

#1. Yes, it's a hack. So much so that in the comment above it I gave credit 
to the original source. :) For Python3, do you have an example I could look 
at? I'm not familiar with reading the byte strings as you've mentioned. 
TBH, locale is a newer topic for me to work with. 
#2. Ok, thanks I'll update that



On Saturday, March 23, 2019 at 9:51:32 PM UTC-4, Thomas Keffer wrote:
>
> I suspect one of your "LC" settings is missing. Run the command "locale" 
> (without the -a flag). You should see something like:
> LANG=en_US.UTF-8
> LANGUAGE=
> LC_CTYPE="en_US.UTF-8"
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_PAPER="en_US.UTF-8"
> LC_NAME="en_US.UTF-8"
> LC_ADDRESS="en_US.UTF-8"
> LC_TELEPHONE="en_US.UTF-8"
> LC_MEASUREMENT="en_US.UTF-8"
> LC_IDENTIFICATION="en_US.UTF-8"
> LC_ALL=
>
> Having said this, Pat, if you're listening, two issues:
>
>1. The Belchertown skins sets a default encoding by reloading sys, 
>then making use of the otherwise hidden function 
>sys.setdefaultencoding(). This is a hack, and won't work under Python 
>3. Instead, you need to read byte strings in and explicitly decode them 
>(instead of relying on a default encoding).
>2. The line locale.setlocale(locale.LC_ALL, "") should not be 
>necessary. This is already done in user/extensions.py.
>
> -tk
>
>
>
>
>
> On Sat, Mar 23, 2019 at 11:00 AM G400 > 
> wrote:
>
>> reportengine: Caught unrecoverable exception in generator 
>> 'weewx.cheetahgenerator.CheetahGenerator'
>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]:   unsupported 
>> locale setting
>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]:   Traceback 
>> (most recent call last):
>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]: File 
>> "/home/weewx/bin/weewx/reportengine.py", line 204, in run
>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]:   
>> obj.start()
>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]: File 
>> "/home/weewx/bin/weewx/reportengine.py", line 300, in start
>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]:   
>> self.run()
>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]: File 
>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 157, in run
>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]:   
>> self.initExtensions(gen_dict[section_name])
>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]: File 
>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 199, in initExtensions
>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]:   class_ = 
>> weeutil.weeutil._get_object(x)
>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]: File 
>> "/home/weewx/bin/weeutil/weeutil.py", line 1130, in _get_object
>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]:   mod = 
>> __import__(module)
>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]: File 
>> "/home/weewx/bin/user/belchertown.py", line 26, in 
>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]:   
>> locale.setlocale(locale.LC_ALL, "")
>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]: File 
>> "/usr/lib/python2.7/locale.py", line 581, in setlocale
>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]:   return 
>> _setlocale(category, locale)
>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]:   Error: 
>> unsupported locale setting
>> Mar 23 18:54:54 aad-raspberry-01 weewx[10423]:   Generator 
>> terminated
>>
>> My locale settings are as follows:
>> locale -a
>> C
>> C.UTF-8
>> en_US.utf8
>> POSIX
>>
>> Content of /etc/default/locale
>> #  File generated by update-locale
>> LANG=en_US.UTF-8
>>
>> What else do I need to check to fix this error?
>>
>> -- 
>> You received this message because you are subscribed 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 .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

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

Re: [weewx-user] Re: weewx-realtime_gauge-data not working

[gjr80]

I've had a look at your logs and site and it appears that an error is 
occurring on your web server when the http post is attempted. I can see 
post_gauge-data.php on your website so I suspect the issue may well be one 
of permissions on your web server. Unfortunately I am pushed for time at 
the moment and won't be able to get back to this until later today. In the 
meantime it may help to have some details of your WeeWX config. Could you 
please use the wee_debug utility 
 to produce a 
wee_debug report and post the report here. Before posting just check the 
output for any sensitive info, wee_debug will attempt to mask sensitive 
data such as passwords, user names etc but it is not perfect.

One other thing, you will note that your gauges will be updating every 5 
minutes, that is because whilst the http post using post_gauge-data.php is 
failing gauge-data.txt is still being uploaded every 5 minutes via FTP. We 
can fix that once we get the http post working.

Gary

On Tuesday, 26 March 2019 07:55:45 UTC+10, Andrea Cecilia wrote:
>
> it is already set in debug=1 mode!
>
> Il giorno lunedì 25 marzo 2019 22:09:57 UTC+1, Tom Robertson ha scritto:
>
> We will need to wait for Gary.  I suggest you set debug=1 in the weewx 
> config file, restart weewx and then post the results.
>
> -
> Tom
>
> On Mar 25, 2019, at 3:50 PM, Andrea Cecilia  wrote:
>
> Hi Tom,
> I didn't make the HTTP POST configuration, because it is written that it 
> is optional. Anyway, now I have followed the instructions 
>  
> for setting it, but it's still not working. You can see the attached log. 
> In particular, I put the post_gauge-data.php in weewx/ss path on my web 
> server, id est the steel series directory, ensuring that it has read/write 
> permissions.  I also commented out the [CheetahGenerator] [[ToDate]] lines 
> in $SKIN_ROOT/ss/skin.conf, so that steel series driver won't generate 
> gauge-data.txt file. 
>
>
> Mar 25 21:45:15 raspberrypi-romaeur weewx[11030]: vantage: Getting archive 
> packets since 2019-03-25 21:40:00 CET (1553546400)
> Mar 25 21:45:15 raspberrypi-romaeur weewx[11030]: rtgdthread: Failed to 
> post data: Unexpected response
> Mar 25 21:45:15 raspberrypi-romaeur weewx[11030]: vantage: Gentle wake up 
> of console successful
> Mar 25 21:45:17 raspberrypi-romaeur weewx[11030]: vantage: Retrieving 1 
> page(s); starting index= 0
> Mar 25 21:45:17 raspberrypi-romaeur weewx[11030]: manager: Added record 
> 2019-03-25 21:45:00 CET (1553546700) to database 'weewx.sdb'
> Mar 25 21:45:17 raspberrypi-romaeur weewx[11030]: manager: Added record 
> 2019-03-25 21:45:00 CET (1553546700) to daily summary in 'weewx.sdb'
> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: vantage: Empty record 
> page 0; index 1
> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: reportengine: Running 
> reports for latest time in the database.
> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: vantage: Requesting 200 
> LOOP packets.
> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: reportengine: Running 
> report 'StandardReport'
> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: reportengine: Found 
> configuration file /home/weewx/skins/Standard/skin.conf for report 
> 'StandardReport'
> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: cheetahgenerator: using 
> search list ['weewx.cheetahgenerator.Almanac', 
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
> 'weewx.cheetahgenerator.Extras']
> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: manager: Daily summary 
> version is 2.0
> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: vantage: Gentle wake up 
> of console successful
> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: restx: Wunderground-PWS: 
> Published record 2019-03-25 21:45:00 CET (1553546700)
> Mar 25 21:45:21 raspberrypi-romaeur weewx[11030]: rtgdthread: Failed to 
> post data: Unexpected response
> Mar 25 21:45:21 raspberrypi-romaeur weewx[11030]: rtgdthread: Failed to 
> post data: Unexpected response
> Mar 25 21:45:22 raspberrypi-romaeur weewx[11030]: cheetahgenerator: 
> Generated 15 files for report StandardReport in 1.54 seconds
> Mar 25 21:45:22 raspberrypi-romaeur weewx[11030]: manager: Daily summary 
> version is 2.0
> Mar 25 21:45:25 raspberrypi-romaeur weewx[11030]: rtgdthread: Failed to 
> post data: Unexpected response
> Mar 25 21:45:25 raspberrypi-romaeur weewx[11030]: rtgdthread: Failed to 
> post data: Unexpected response
> Mar 25 21:45:25 raspberrypi-romaeur weewx[11030]: imagegenerator: 
> Generated 13 images for StandardReport in 3.74 seconds
> Mar 25 21:45:25 raspberrypi-romaeur weewx[11030]: copygenerator: copied 0 
> files to /home/weewx/public_html
> Mar 25 21:45:25 raspberrypi-romaeur weewx[11030]: reportengine: Running 
> report 'FTP'
> Mar 25 21:45:25 raspberryp

[weewx-user] Re: How to change frequency of realtime.txt updates

[gjr80]

Hi,

If you are using a Davis Vantage station and the crt extension is bound to 
loop then you should be seeing realtime.txt being generated every 2.5 odd 
seconds. If you have changed the binding to archive then based on the 
weewx.conf extract you provided it should be generated every 5minutes. I am 
not sure where the one minute update you mention comes from, it should not 
be happening. How are you checking how often realtime.txt is generated? Are 
you checking the file on the WeeWX machine or are you checking on a web 
server or some other server? If you are checking on a machine other than 
the WeeWX machine remember that there must be some mechanism to transfer 
realtime.txt from the WeeWX machine to the remote server and it may be that 
transfer mechanism that is only occurring every minute.

Unfortunately the crt extension does not give us too much extra debug info 
but it may help to get a clearer picture of what is going on if you post a 
debug log extract. To do this edit weewx.conf, set debug=1, save weewx.conf 
and then restart WeeWX. Let WeeWX run for at least 10 minutes and then take 
a log extract showing the entire WeeWX startup and the following 10 minutes 
of log activity. The log should be in /var/log/syslog unless you have 
changed it. Post the log extract without any changes.

At the end of the day though you will have two choices in terms of 
realtime.txt update period, either on every loop packet (2.5 odd seconds) 
or every archive interval (currently 5 minutes).

Gary

On Tuesday, 26 March 2019 06:16:32 UTC+10, G400 wrote:
>
> Davis Vantage2 getting data from Weather Envoy USD->Serial
>
> This is my current setting:
> StdArchive]
> 
> # If the station hardware supports data logging then the archive 
> interval
> # will be downloaded from the station. Otherwise, specify it (in 
> seconds).
> archive_interval = 300
>
>
> Currently realtime.txt is created every 60s.
> How do I relate this to archive interval?
>
> I want realtime.txt to be updated every 10s.
>
>
> On Monday, March 25, 2019 at 8:41:25 PM UTC+1, Andrew Milner wrote:
>>
>> according to the wiki the generation can be tied to loop or archive - 
>> which is yours tied to?  It should be to loop (which is the default) if you 
>> want it creating more often than the archive interval.
>>
>> if to loop then it depends on your station type - what kind of station do 
>> you have?  Some stations (eg FineOffset) cannot produce loop data any 
>> faster than say  every 48 seconds
>>
>> if to archive then changing the archive interval will also change the 
>> frequency of creating the file.
>>
>> On Monday, 25 March 2019 21:34:37 UTC+2, G400 wrote:
>>>
>>> How can I modify the frequency of Cumulus formatted raltime.txt output 
>>> file using crt plugin (https://github.com/weewx/weewx/wiki/crt)?
>>> G400
>>>
>>

-- 
You received this message because you are subscribed to the Google 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: No html reports any more - ValueError: Empty module name

[gjr80]

Hi,

Indeed the problem was some corruption in your skin.conf:

Mar 25 16:40:22 DietPi weewx[421]: cheetahgenerator: using search list [
'weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', u'u', u
's', u'e', u'r', u'.', u'h', u'i', u's', u't', u'o', u'r', u'y', u'g', u'e', 
u'n', u'e', u'r', u'a', u't', u'o', u'r', u'.', u'M', u'y', u'X', u'S', u'e'
, u'a', u'r', u'c', u'h']

indicates that the search_list_extensions setting was somehow corrupted and 
it had WeeWX looking for all sorts of search list extensions that do not 
exist, hence the ValueError: Empty module name error.

Gary

On Tuesday, 26 March 2019 04:36:26 UTC+10, Copain wrote:
>
> SOLVED!
>
> I recreated the skin.conf file from backup and the additions in the 
> 'ToDate' section. Thereafter it worked immediately.
> There may have been some space or tab character at a wrong position, which 
> blocked the execution of 'user.historygenerator.MyXSearch'.
>
> So, as usual in Linux systems: be careful while typing ...
>
>
>
> Am Montag, 25. März 2019 17:03:43 UTC+1 schrieb Copain:
>
>> My weewx runs on RPi 3B with dietpi.
>>
>> I created the custom report 'forecast.html.tmpl', which I added to the 
>> 'CheetahGenerator' section of skin.conf (niculskin) as follows:
>>
>> [[ToDate]]
>> [[[forecast]]]
>> template = forecast.html.tmpl
>>
>> Now, I don't get any html reports any more and the attached log file 
>> shows 'ValueError: Empty module name'.
>>
>> How can I resolve this issue?
>>
>> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx-realtime_gauge-data not working

[Andrea Cecilia]

it is already set in debug=1 mode!

Il giorno lunedì 25 marzo 2019 22:09:57 UTC+1, Tom Robertson ha scritto:
>
> We will need to wait for Gary.  I suggest you set debug=1 in the weewx 
> config file, restart weewx and then post the results.
>
> -
> Tom
>
> On Mar 25, 2019, at 3:50 PM, Andrea Cecilia  > wrote:
>
> Hi Tom,
> I didn't make the HTTP POST configuration, because it is written that it 
> is optional. Anyway, now I have followed the instructions 
>  
> for setting it, but it's still not working. You can see the attached log. 
> In particular, I put the post_gauge-data.php in weewx/ss path on my web 
> server, id est the steel series directory, ensuring that it has read/write 
> permissions.  I also commented out the [CheetahGenerator] [[ToDate]] lines 
> in $SKIN_ROOT/ss/skin.conf, so that steel series driver won't generate 
> gauge-data.txt file. 
>
>
> Mar 25 21:45:15 raspberrypi-romaeur weewx[11030]: vantage: Getting archive 
> packets since 2019-03-25 21:40:00 CET (1553546400)
> Mar 25 21:45:15 raspberrypi-romaeur weewx[11030]: rtgdthread: Failed to 
> post data: Unexpected response
> Mar 25 21:45:15 raspberrypi-romaeur weewx[11030]: vantage: Gentle wake up 
> of console successful
> Mar 25 21:45:17 raspberrypi-romaeur weewx[11030]: vantage: Retrieving 1 
> page(s); starting index= 0
> Mar 25 21:45:17 raspberrypi-romaeur weewx[11030]: manager: Added record 
> 2019-03-25 21:45:00 CET (1553546700) to database 'weewx.sdb'
> Mar 25 21:45:17 raspberrypi-romaeur weewx[11030]: manager: Added record 
> 2019-03-25 21:45:00 CET (1553546700) to daily summary in 'weewx.sdb'
> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: vantage: Empty record 
> page 0; index 1
> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: reportengine: Running 
> reports for latest time in the database.
> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: vantage: Requesting 200 
> LOOP packets.
> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: reportengine: Running 
> report 'StandardReport'
> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: reportengine: Found 
> configuration file /home/weewx/skins/Standard/skin.conf for report 
> 'StandardReport'
> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: cheetahgenerator: using 
> search list ['weewx.cheetahgenerator.Almanac', 
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
> 'weewx.cheetahgenerator.Extras']
> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: manager: Daily summary 
> version is 2.0
> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: vantage: Gentle wake up 
> of console successful
> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: restx: Wunderground-PWS: 
> Published record 2019-03-25 21:45:00 CET (1553546700)
> Mar 25 21:45:21 raspberrypi-romaeur weewx[11030]: rtgdthread: Failed to 
> post data: Unexpected response
> Mar 25 21:45:21 raspberrypi-romaeur weewx[11030]: rtgdthread: Failed to 
> post data: Unexpected response
> Mar 25 21:45:22 raspberrypi-romaeur weewx[11030]: cheetahgenerator: 
> Generated 15 files for report StandardReport in 1.54 seconds
> Mar 25 21:45:22 raspberrypi-romaeur weewx[11030]: manager: Daily summary 
> version is 2.0
> Mar 25 21:45:25 raspberrypi-romaeur weewx[11030]: rtgdthread: Failed to 
> post data: Unexpected response
> Mar 25 21:45:25 raspberrypi-romaeur weewx[11030]: rtgdthread: Failed to 
> post data: Unexpected response
> Mar 25 21:45:25 raspberrypi-romaeur weewx[11030]: imagegenerator: 
> Generated 13 images for StandardReport in 3.74 seconds
> Mar 25 21:45:25 raspberrypi-romaeur weewx[11030]: copygenerator: copied 0 
> files to /home/weewx/public_html
> Mar 25 21:45:25 raspberrypi-romaeur weewx[11030]: reportengine: Running 
> report 'FTP'
> Mar 25 21:45:25 raspberrypi-romaeur weewx[11030]: reportengine: Found 
> configuration file /home/weewx/skins/Ftp/skin.conf for report 'FTP'
> Mar 25 21:45:25 raspberrypi-romaeur weewx[11030]: ftpupload: Attempting 
> connection to ftp.romaeurmeteo.it
> Mar 25 21:45:26 raspberrypi-romaeur weewx[11030]: ftpupload: Connected to 
> ftp.romaeurmeteo.it
> Mar 25 21:45:26 raspberrypi-romaeur weewx[11030]: ftpupload: Uploaded file 
> /romaeurmeteo.it/weewx/daypond.png
> Mar 25 21:45:26 raspberrypi-romaeur weewx[11030]: ftpupload: Uploaded file 
> /romaeurmeteo.it/weewx/dayradiation.png
> Mar 25 21:45:26 raspberrypi-romaeur weewx[11030]: ftpupload: Uploaded file 
> /romaeurmeteo.it/weewx/index.html
> Mar 25 21:45:26 raspberrypi-romaeur weewx[11030]: ftpupload: Uploaded file 
> /romaeurmeteo.it/weewx/dayrain.png
> Mar 25 21:45:27 raspberrypi-romaeur weewx[11030]: ftpupload: Uploaded file 
> /romaeurmeteo.it/weewx/gauge-data.txt
> Mar 25 21:45:27 raspberrypi-romaeur weewx[11030]: ftpupload: Uploaded file 
> /romaeurmeteo.it/weewx/daywinddir.png
> Mar 25 21:45:27 raspberrypi-romaeur weewx[11030]: ftpupload: Uploaded file 
> /roma

[weewx-user] Re: How to change frequency of realtime.txt updates

[G400]

Davis Vantage2 getting data from Weather Envoy USD->Serial

This is my current setting:
StdArchive]

# If the station hardware supports data logging then the archive 
interval
# will be downloaded from the station. Otherwise, specify it (in 
seconds).
archive_interval = 300


Currently realtime.txt is created every 60s.
How do I relate this to archive interval?

I want realtime.txt to be updated every 10s.


On Monday, March 25, 2019 at 8:41:25 PM UTC+1, Andrew Milner wrote:
>
> according to the wiki the generation can be tied to loop or archive - 
> which is yours tied to?  It should be to loop (which is the default) if you 
> want it creating more often than the archive interval.
>
> if to loop then it depends on your station type - what kind of station do 
> you have?  Some stations (eg FineOffset) cannot produce loop data any 
> faster than say  every 48 seconds
>
> if to archive then changing the archive interval will also change the 
> frequency of creating the file.
>
> On Monday, 25 March 2019 21:34:37 UTC+2, G400 wrote:
>>
>> How can I modify the frequency of Cumulus formatted raltime.txt output 
>> file using crt plugin (https://github.com/weewx/weewx/wiki/crt)?
>> G400
>>
>

-- 
You received this message because you are subscribed to the Google 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: How to change frequency of realtime.txt updates

[Andrew Milner]

according to the wiki the generation can be tied to loop or archive - which 
is yours tied to?  It should be to loop (which is the default) if you want 
it creating more often than the archive interval.

if to loop then it depends on your station type - what kind of station do 
you have?  Some stations (eg FineOffset) cannot produce loop data any 
faster than say  every 48 seconds

if to archive then changing the archive interval will also change the 
frequency of creating the file.

On Monday, 25 March 2019 21:34:37 UTC+2, G400 wrote:
>
> How can I modify the frequency of Cumulus formatted raltime.txt output 
> file using crt plugin (https://github.com/weewx/weewx/wiki/crt)?
> G400
>

-- 
You received this message because you are subscribed to the Google 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] How to change frequency of realtime.txt updates

[G400]

How can I modify the frequency of Cumulus formatted raltime.txt output file 
using crt plugin (https://github.com/weewx/weewx/wiki/crt)?
G400

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

Re: [weewx-user] Re: Belchertown skin 0.9 now available

[Patrick Tranchant]

ok
so does that mean it has nothing to do with the fact that I use the 
Belchertown skin?
true
Patrick

On Monday, March 25, 2019 at 8:04:22 PM UTC+1, Pat wrote:
>
> A lot of labels can be changed by following this guide 
> . 
> Anything that is not covered here that you need to change will have to be 
> done by editing the skin files directly. 
>
>
> On Monday, March 25, 2019 at 2:22:35 PM UTC-4, Patrick Tranchant wrote:
>>
>> hello PAT
>>
>> in which files I can translate the names in french, see capture in attach 
>> ( dewpoint, heat index etc etc )
>> thanks
>>
>> Patrick
>>
>> On Tuesday, March 19, 2019 at 2:47:29 PM UTC+1, Pat wrote:
>>>
>>> That’s a darksky setting, not the skin. The skin shows what DarkSky is 
>>> giving it. You’ll need to contact them if you need more clarity on the 
>>> observations. 
>>>
>>>  
>>>
>>>  
>>>
>>> *From:* weewx...@googlegroups.com [mailto:weewx...@googlegroups.com] *On 
>>> Behalf Of *Adnan Mumtaz
>>> *Sent:* Monday, March 18, 2019 2:39 PM
>>> *To:* weewx-user 
>>> *Subject:* [weewx-user] Re: Belchertown skin 0.9 now available
>>>
>>>  
>>>
>>> Noticed that  during haze/dusty weather the skin shows Foggy, 
>>>
>>> On Monday, 18 March 2019 01:57:11 UTC+3, Pat wrote:
>>>
>>> Thanks I'll look into it
>>>
>>> On Sunday, March 17, 2019 at 5:26:17 PM UTC-4, Adnan Mumtaz wrote:
>>>
>>> https://www.airvisual.com/air-pollution-data-api
>>>
>>>
>>>
>>> On Sunday, 17 March 2019 20:54:21 UTC+3, Pat wrote:
>>>
>>> Do you have a source where we can get air quality data?
>>>
>>> On Sunday, March 17, 2019 at 1:03:37 PM UTC-4, Adnan Mumtaz wrote:
>>>
>>> Wow :) I will definitely then wait for 1.0. 
>>>
>>>
>>> Will try to use the beta.
>>>
>>>  
>>>
>>> Thanks a million once again. 
>>>
>>>  
>>>
>>> One suggestion, if instead of Earth Quake you can add an option of Air 
>>> Quality would be great, we have more issues of air quality than earth 
>>> quakes :)
>>>
>>> On Sunday, 17 March 2019 19:25:09 UTC+3, Pat wrote:
>>>
>>> Skin version 1.0 offers an entire new way to customize charts. From 
>>> re-ordering, to adding custom observations, to multiple yAxis. 
>>>
>>>  
>>>
>>> If you're OK with staying on a skin version that works for you, then 
>>> that would be great. That way I don't have to release a 0.9.2 when 1.0 is 
>>> only a couple of weeks away. 
>>>
>>>  
>>>
>>> If you want to test 1.0 now, you can download the development branch 
>>> zip file  
>>> of the skin. Be warned it's *very beta* with little documentation right 
>>> now. The only documentation is in skin.conf currently. And I'm pushing 
>>> updates to the skin daily. If you test it, and find something wrong, let me 
>>> know so I can update it :)
>>>
>>>
>>> On Sunday, March 17, 2019 at 12:15:16 PM UTC-4, Adnan Mumtaz wrote:
>>>
>>> Hi ,
>>>
>>>  
>>>
>>> Many thanks for your hardwork, I upgraded to the latest Belchertown 
>>> template 0.9.1 after upgrading weewx, everything seems working fine, I can 
>>> see intemp showing in temp chart, I tried to disable intemp from the 
>>> weewx.conf and after doing that the temp chart goes upside down it shows 
>>> years instead of hours and doesnt show graph, i also tried to change the 
>>> rainplot to humidity after doing that Rain chart as well as Solar chart 
>>> disappeared, I dont see any errors in the syslog, I reverted back all the 
>>> changes though . Mayb you can simulate these in your test environment?
>>>
>>> thank you,
>>> Adnan
>>>
>>>  
>>>
>>>
>>>
>>> On Friday, 1 March 2019 03:50:34 UTC+3, Pat wrote:
>>>
>>> I've just released Belchertown skin 0.9. You can read the updates and 
>>> download it here: https://github.com/poblabs/weewx-belchertown/releases
>>>
>>>  
>>>
>>> A lot of work went into this release. I've learned a lot through 
>>> feedback on the skin. 
>>>
>>>  
>>>
>>> This release fixes a major bug with the rain charts which were taking a 
>>> very long time to generate. This release also brings a lot of updates to 
>>> locale formats. 
>>>
>>>  
>>>
>>> *There's 1 breaking change if you are upgrading*. Please take special 
>>> note to a few MQTT variable names which have changed to mqtt_websockets_. 
>>> This is to reduce confusion and offer clarity on new user installations. 
>>>
>>>  
>>>
>>> Please let me know if you've upgraded and share your site. I'd love to 
>>> see it out there!
>>>
>>>  
>>>
>>> -- 
>>> 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/yOHpHCu0jAA/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> weewx-user+...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

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

Re: [weewx-user] Re: Belchertown skin 0.9 now available

[Pat]

A lot of labels can be changed by following this guide 
. Anything 
that is not covered here that you need to change will have to be done by 
editing the skin files directly. 


On Monday, March 25, 2019 at 2:22:35 PM UTC-4, Patrick Tranchant wrote:
>
> hello PAT
>
> in which files I can translate the names in french, see capture in attach 
> ( dewpoint, heat index etc etc )
> thanks
>
> Patrick
>
> On Tuesday, March 19, 2019 at 2:47:29 PM UTC+1, Pat wrote:
>>
>> That’s a darksky setting, not the skin. The skin shows what DarkSky is 
>> giving it. You’ll need to contact them if you need more clarity on the 
>> observations. 
>>
>>  
>>
>>  
>>
>> *From:* weewx...@googlegroups.com [mailto:weewx...@googlegroups.com] *On 
>> Behalf Of *Adnan Mumtaz
>> *Sent:* Monday, March 18, 2019 2:39 PM
>> *To:* weewx-user 
>> *Subject:* [weewx-user] Re: Belchertown skin 0.9 now available
>>
>>  
>>
>> Noticed that  during haze/dusty weather the skin shows Foggy, 
>>
>> On Monday, 18 March 2019 01:57:11 UTC+3, Pat wrote:
>>
>> Thanks I'll look into it
>>
>> On Sunday, March 17, 2019 at 5:26:17 PM UTC-4, Adnan Mumtaz wrote:
>>
>> https://www.airvisual.com/air-pollution-data-api
>>
>>
>>
>> On Sunday, 17 March 2019 20:54:21 UTC+3, Pat wrote:
>>
>> Do you have a source where we can get air quality data?
>>
>> On Sunday, March 17, 2019 at 1:03:37 PM UTC-4, Adnan Mumtaz wrote:
>>
>> Wow :) I will definitely then wait for 1.0. 
>>
>>
>> Will try to use the beta.
>>
>>  
>>
>> Thanks a million once again. 
>>
>>  
>>
>> One suggestion, if instead of Earth Quake you can add an option of Air 
>> Quality would be great, we have more issues of air quality than earth 
>> quakes :)
>>
>> On Sunday, 17 March 2019 19:25:09 UTC+3, Pat wrote:
>>
>> Skin version 1.0 offers an entire new way to customize charts. From 
>> re-ordering, to adding custom observations, to multiple yAxis. 
>>
>>  
>>
>> If you're OK with staying on a skin version that works for you, then that 
>> would be great. That way I don't have to release a 0.9.2 when 1.0 is only a 
>> couple of weeks away. 
>>
>>  
>>
>> If you want to test 1.0 now, you can download the development branch zip 
>> file  of 
>> the skin. Be warned it's *very beta* with little documentation right 
>> now. The only documentation is in skin.conf currently. And I'm pushing 
>> updates to the skin daily. If you test it, and find something wrong, let me 
>> know so I can update it :)
>>
>>
>> On Sunday, March 17, 2019 at 12:15:16 PM UTC-4, Adnan Mumtaz wrote:
>>
>> Hi ,
>>
>>  
>>
>> Many thanks for your hardwork, I upgraded to the latest Belchertown 
>> template 0.9.1 after upgrading weewx, everything seems working fine, I can 
>> see intemp showing in temp chart, I tried to disable intemp from the 
>> weewx.conf and after doing that the temp chart goes upside down it shows 
>> years instead of hours and doesnt show graph, i also tried to change the 
>> rainplot to humidity after doing that Rain chart as well as Solar chart 
>> disappeared, I dont see any errors in the syslog, I reverted back all the 
>> changes though . Mayb you can simulate these in your test environment?
>>
>> thank you,
>> Adnan
>>
>>  
>>
>>
>>
>> On Friday, 1 March 2019 03:50:34 UTC+3, Pat wrote:
>>
>> I've just released Belchertown skin 0.9. You can read the updates and 
>> download it here: https://github.com/poblabs/weewx-belchertown/releases
>>
>>  
>>
>> A lot of work went into this release. I've learned a lot through feedback 
>> on the skin. 
>>
>>  
>>
>> This release fixes a major bug with the rain charts which were taking a 
>> very long time to generate. This release also brings a lot of updates to 
>> locale formats. 
>>
>>  
>>
>> *There's 1 breaking change if you are upgrading*. Please take special 
>> note to a few MQTT variable names which have changed to mqtt_websockets_. 
>> This is to reduce confusion and offer clarity on new user installations. 
>>
>>  
>>
>> Please let me know if you've upgraded and share your site. I'd love to 
>> see it out there!
>>
>>  
>>
>> -- 
>> 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/yOHpHCu0jAA/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

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

Re: [weewx-user] Re: question regarding graphs

[Thomas Keffer]

The easy way to do this is to just override the plot options in skin.conf.
I don't know what variable name you are using, but assuming it is 'rssi',
it would look something like:

[[[dayrssi]]]
rssi
  y_label = dBm
  y_label_format=%.1f

-tk

On Mon, Mar 25, 2019 at 11:33 AM parallelsys 
wrote:

> Does this look about right?
>
> weewx.units.USUnits['group_decibels'] = 'decibels'
> weewx.units.MetricUnits['group_concentration'] = 'decibels'
> weewx.units.MetricWXUnits['group_decibels'] = 'decibels'
> weewx.units.default_unit_format_dict['decibels'] = ' N/A'
> weewx.units.default_unit_label_dict['decibels']  = ' dBm'
>
>
> On Monday, March 25, 2019 at 12:11:56 PM UTC-5, parallelsys wrote:
>>
>> I am able to graph rssi signal from my device. What I would like to do is
>> add a new symbol (dBm) so it can have the right symbol display on the graph.
>> Right now I am using percent but I want to do it the right way :)
>>
>> See the attached screenshoot
>>
>> How can I change that percent symbol to dBm?
>>
>>
>> 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.
> For more options, visit https://groups.google.com/d/optout.
>

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

[weewx-user] Re: No html reports any more - ValueError: Empty module name

[Copain]

SOLVED!

I recreated the skin.conf file from backup and the additions in the 
'ToDate' section. Thereafter it worked immediately.
There may have been some space or tab character at a wrong position, which 
blocked the execution of 'user.historygenerator.MyXSearch'.

So, as usual in Linux systems: be careful while typing ...



Am Montag, 25. März 2019 17:03:43 UTC+1 schrieb Copain:

> My weewx runs on RPi 3B with dietpi.
>
> I created the custom report 'forecast.html.tmpl', which I added to the 
> 'CheetahGenerator' section of skin.conf (niculskin) as follows:
>
> [[ToDate]]
> [[[forecast]]]
> template = forecast.html.tmpl
>
> Now, I don't get any html reports any more and the attached log file 
> shows 'ValueError: Empty module name'.
>
> How can I resolve this issue?
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: question regarding graphs

[parallelsys]

Does this look about right?

weewx.units.USUnits['group_decibels'] = 'decibels'
weewx.units.MetricUnits['group_concentration'] = 'decibels'
weewx.units.MetricWXUnits['group_decibels'] = 'decibels'
weewx.units.default_unit_format_dict['decibels'] = ' N/A'
weewx.units.default_unit_label_dict['decibels']  = ' dBm'


On Monday, March 25, 2019 at 12:11:56 PM UTC-5, parallelsys wrote:
>
> I am able to graph rssi signal from my device. What I would like to do is 
> add a new symbol (dBm) so it can have the right symbol display on the graph.
> Right now I am using percent but I want to do it the right way :)
>
> See the attached screenshoot
>
> How can I change that percent symbol to dBm?
>
>
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown skin 0.9 now available

[Patrick Tranchant]

hello PAT

in which files I can translate the names in french, see capture in attach ( 
dewpoint, heat index etc etc )
thanks

Patrick

On Tuesday, March 19, 2019 at 2:47:29 PM UTC+1, Pat wrote:
>
> That’s a darksky setting, not the skin. The skin shows what DarkSky is 
> giving it. You’ll need to contact them if you need more clarity on the 
> observations. 
>
>  
>
>  
>
> *From:* weewx...@googlegroups.com  [mailto:
> weewx...@googlegroups.com ] *On Behalf Of *Adnan Mumtaz
> *Sent:* Monday, March 18, 2019 2:39 PM
> *To:* weewx-user >
> *Subject:* [weewx-user] Re: Belchertown skin 0.9 now available
>
>  
>
> Noticed that  during haze/dusty weather the skin shows Foggy, 
>
> On Monday, 18 March 2019 01:57:11 UTC+3, Pat wrote:
>
> Thanks I'll look into it
>
> On Sunday, March 17, 2019 at 5:26:17 PM UTC-4, Adnan Mumtaz wrote:
>
> https://www.airvisual.com/air-pollution-data-api
>
>
>
> On Sunday, 17 March 2019 20:54:21 UTC+3, Pat wrote:
>
> Do you have a source where we can get air quality data?
>
> On Sunday, March 17, 2019 at 1:03:37 PM UTC-4, Adnan Mumtaz wrote:
>
> Wow :) I will definitely then wait for 1.0. 
>
>
> Will try to use the beta.
>
>  
>
> Thanks a million once again. 
>
>  
>
> One suggestion, if instead of Earth Quake you can add an option of Air 
> Quality would be great, we have more issues of air quality than earth 
> quakes :)
>
> On Sunday, 17 March 2019 19:25:09 UTC+3, Pat wrote:
>
> Skin version 1.0 offers an entire new way to customize charts. From 
> re-ordering, to adding custom observations, to multiple yAxis. 
>
>  
>
> If you're OK with staying on a skin version that works for you, then that 
> would be great. That way I don't have to release a 0.9.2 when 1.0 is only a 
> couple of weeks away. 
>
>  
>
> If you want to test 1.0 now, you can download the development branch zip 
> file  of 
> the skin. Be warned it's *very beta* with little documentation right now. 
> The only documentation is in skin.conf currently. And I'm pushing updates 
> to the skin daily. If you test it, and find something wrong, let me know so 
> I can update it :)
>
>
> On Sunday, March 17, 2019 at 12:15:16 PM UTC-4, Adnan Mumtaz wrote:
>
> Hi ,
>
>  
>
> Many thanks for your hardwork, I upgraded to the latest Belchertown 
> template 0.9.1 after upgrading weewx, everything seems working fine, I can 
> see intemp showing in temp chart, I tried to disable intemp from the 
> weewx.conf and after doing that the temp chart goes upside down it shows 
> years instead of hours and doesnt show graph, i also tried to change the 
> rainplot to humidity after doing that Rain chart as well as Solar chart 
> disappeared, I dont see any errors in the syslog, I reverted back all the 
> changes though . Mayb you can simulate these in your test environment?
>
> thank you,
> Adnan
>
>  
>
>
>
> On Friday, 1 March 2019 03:50:34 UTC+3, Pat wrote:
>
> I've just released Belchertown skin 0.9. You can read the updates and 
> download it here: https://github.com/poblabs/weewx-belchertown/releases
>
>  
>
> A lot of work went into this release. I've learned a lot through feedback 
> on the skin. 
>
>  
>
> This release fixes a major bug with the rain charts which were taking a 
> very long time to generate. This release also brings a lot of updates to 
> locale formats. 
>
>  
>
> *There's 1 breaking change if you are upgrading*. Please take special 
> note to a few MQTT variable names which have changed to mqtt_websockets_. 
> This is to reduce confusion and offer clarity on new user installations. 
>
>  
>
> Please let me know if you've upgraded and share your site. I'd love to see 
> it out there!
>
>  
>
> -- 
> 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/yOHpHCu0jAA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx-user+...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout.
>

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

[weewx-user] Re: Weewx und WH2600

[Joerg Reinisch]

What I can say with certainty now:
As soon as I switch my weather station completely to US values ​​(station 
settings), all values ​​are displayed correctly.
In order to get the display in metric values, I change the information in 
the weewx.conf under Groups.
Thus, I can take out all the corrections in the weewx.conf.
I will try again later with the calculations of you. Then I could also look 
at the live values ​​in metric data.
I will put pictures and data online later.
But so far already thanks for the food for thought.

Jörg

Am Sonntag, 24. März 2019 21:06:53 UTC+1 schrieb Tolip Wen:
>
> My last post contains a math error in the example labeled "2)"
>
> it should be 
> "ex: (for temp)  tempC + 32 x 0.555 = tempF."
>
> I mixed up the multiplier  tempF - 32 x 1.8 = tempC
>
> On Saturday, March 16, 2019 at 3:09:31 PM UTC-5, Joerg Reinisch wrote:
>>
>> Hallo,
>> mein Problem bezieht sich auf Weewx (Ver. 3.8.2) mit meiner WH2600. 
>> Momentan läuft Weewx auf einem Raspi und dazu hab ich mir den ObserverIp 
>> Treiber 0.1 geladen.
>> Die Daten werden eigentlich alle wunderbar in Weewx angezeigt, was aber 
>> nicht angezeigt wird, ist der Luftdruck.
>> Im Terminal bekomme ich folgende Meldungen:
>>
>> Mär 16 20:00:32 pi-drei weewx[25310]: copygenerator: copied 0 files to 
>> /var/www/html/weewx
>> Mär 16 20:00:32 pi-drei weewx[25310]: reportengine: Report 
>> 'SmartphoneReport' not enabled. Skipping.
>> Mär 16 20:00:32 pi-drei weewx[25310]: reportengine: Report 'MobileReport' 
>> not enabled. Skipping.
>> Mär 16 20:00:32 pi-drei weewx[25310]: reportengine: Report 
>> 'StandardReport' not enabled. Skipping.
>> Mär 16 20:00:32 pi-drei weewx[25310]: reportengine: Report 'FTP' not 
>> enabled. Skipping.
>> Mär 16 20:00:32 pi-drei weewx[25310]: reportengine: Report 'RSYNC' not 
>> enabled. Skipping.
>> Mär 16 20:00:57 pi-drei weewx[25310]: observerip: packet interval 31
>> Mär 16 20:00:57 pi-drei weewx[25310]: engine: 2019-03-16 20:00:58 CET 
>> (1552762858) LOOP value 'pressure' 955.0 outside limits (25.100489375, 
>> 32.48298625)
>> Mär 16 20:01:28 pi-drei weewx[25310]: observerip: packet interval 30
>> Mär 16 20:01:28 pi-drei weewx[25310]: engine: 2019-03-16 20:01:28 CET 
>> (1552762888) LOOP value 'pressure' 955.0 outside limits (25.100489375, 
>> 32.48298625)
>>
>> Ok, das sagt mir immerhin dass der Druck wegen der falschen Einstellung 
>> in der weewx.conf nicht angezeigt werden kann.
>> Aber sobald ich dann in der weewx.conf die Einstellung dementsprechend 
>> abändere, bekomme ich überhaupt keine Anzeigen mehr, das kann es ja wohl 
>> nicht sein.
>>
>> Die Daten werden aber bei WU (wunderground.com) richtig angezeigt und 
>> auch beim direkten auslesen der Daten im Terminal bekomme ich alle Daten 
>> angezeigt.
>> Nur lediglich bei Weewx, da wird der Druck eben nicht angezeigt und das 
>> macht mich total verrückt.
>>
>> Vielleicht kann mir ja jemand von euch helfen. 
>> Wenn es vielleicht nicht anders geht, werde ich den ganzen Text auch 
>> Übersetzen lassen, denn so gut ist mein englisch jetzt auch nicht mehr. 
>> ;-)
>> Die weewx.conf kann ich momentan nicht mit anhängen da ich momentan nicht 
>> auf meinen Server zugreifen kann.
>> Aber für jede Hilfe bin ich mehr als dankbar.
>>
>>

-- 
You received this message because you are subscribed to the Google 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] question regarding graphs

[parallelsys]

I am able to graph rssi signal from my device. What I would like to do is 
add a new symbol (dBm) so it can have the right symbol display on the graph.
Right now I am using percent but I want to do it the right way :)

See the attached screenshoot

How can I change that percent symbol to dBm?


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

[weewx-user] No html reports any more - ValueError: Empty module name

[Copain]

My weewx runs on RPi 3B with dietpi.

I created the custom report 'forecast.html.tmpl', which I added to the 
'CheetahGenerator' section of skin.conf (niculskin) as follows:

[[ToDate]]
[[[forecast]]]
template = forecast.html.tmpl

Now, I don't get any html reports any more and the attached log file 
shows 'ValueError: Empty module name'.

How can I resolve this issue?

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.
For more options, visit https://groups.google.com/d/optout.
Mar 25 16:40:00 DietPi weewx[421]: te923: read: address 0x020001
Mar 25 16:40:01 DietPi weewx[421]: te923: read: 5a 17 a2 43 97 c0 49 0a 00 0a 
0a 00 0a 0a 00 0a 0a 00 0a ff ff a0 3f 04 28 c1 42 00 29 00 0b 80 00 20
Mar 25 16:40:01 DietPi weewx[421]: te923: read: address 0x4c
Mar 25 16:40:01 DietPi weewx[421]: te923: read: 5a ff ff ff ff ff ff ff ff ff 
ff ff ff ff 54 c2 01 04 39 ff ff 13 25 16 03 9d 3f 9a 3f 9e 3f a0 3f 15
Mar 25 16:40:11 DietPi weewx[421]: te923: read: address 0x020001
Mar 25 16:40:11 DietPi weewx[421]: te923: read: 5a 17 a2 43 97 c0 49 0a 00 0a 
0a 00 0a 0a 00 0a 0a 00 0a ff ff a0 3f 04 28 c1 42 00 29 00 0b 80 00 20
Mar 25 16:40:11 DietPi weewx[421]: te923: read: address 0x4c
Mar 25 16:40:11 DietPi weewx[421]: te923: read: 5a ff ff ff ff ff ff ff ff ff 
ff ff ff ff 54 c2 01 04 39 ff ff 13 25 16 03 9d 3f 9a 3f 9e 3f a0 3f 15
Mar 25 16:40:21 DietPi weewx[421]: te923: read: address 0x020001
Mar 25 16:40:21 DietPi weewx[421]: te923: read: 5a 17 a2 43 97 c0 49 0a 00 0a 
0a 00 0a 0a 00 0a 0a 00 0a ff ff a0 3f 04 28 c1 42 00 29 00 0b 80 00 20
Mar 25 16:40:21 DietPi weewx[421]: te923: read: address 0x4c
Mar 25 16:40:21 DietPi weewx[421]: te923: read: 5a ff ff ff ff ff ff ff ff ff 
ff ff ff ff 54 c2 01 04 39 ff ff 13 25 16 03 9d 3f 9a 3f 9e 3f a0 3f 15
Mar 25 16:40:21 DietPi weewx[421]: manager: Added record 2019-03-25 16:40:00 
CET (1553528400) to database 'weewx.sdb'
Mar 25 16:40:21 DietPi weewx[421]: manager: Added record 2019-03-25 16:40:00 
CET (1553528400) to daily summary in 'weewx.sdb'
Mar 25 16:40:22 DietPi weewx[421]: reportengine: Running reports for latest 
time in the database.
Mar 25 16:40:22 DietPi weewx[421]: te923: read: address 0x020001
Mar 25 16:40:22 DietPi weewx[421]: reportengine: Running report 
'niculskinReport'
Mar 25 16:40:22 DietPi weewx[421]: reportengine: Found configuration file 
/etc/weewx/skins/niculskin/skin.conf for report 'niculskinReport'
Mar 25 16:40:22 DietPi weewx[421]: translategenerator.pyc: Language is german
Mar 25 16:40:22 DietPi weewx[421]: cheetahgenerator: using search list 
['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', u'u', u's', 
u'e', u'r', u'.', u'h', u'i', u's', u't', u'o', u'r', u'y', u'g', u'e', u'n', 
u'e', u'r', u'a', u't', u'o', u'r', u'.', u'M', u'y', u'X', u'S', u'e', u'a', 
u'r', u'c', u'h']
Mar 25 16:40:22 DietPi weewx[421]: te923: read: 5a 17 a2 43 97 c0 49 0a 00 0a 
0a 00 0a 0a 00 0a 0a 00 0a ff ff a0 3f 04 28 c1 42 00 29 00 0b 80 00 20
Mar 25 16:40:22 DietPi weewx[421]: te923: read: address 0x4c
Mar 25 16:40:22 DietPi weewx[421]: manager: Daily summary version is 2.0
Mar 25 16:40:22 DietPi weewx[421]: reportengine: Caught unrecoverable exception 
in generator 'user.translategenerator.CheetahGeneratorTranslated'
Mar 25 16:40:22 DietPi weewx[421]:   Empty module name
Mar 25 16:40:22 DietPi weewx[421]:   Traceback (most recent call 
last):
Mar 25 16:40:22 DietPi weewx[421]: File 
"/usr/share/weewx/weewx/reportengine.py", line 204, in run
Mar 25 16:40:22 DietPi weewx[421]:   obj.start()
Mar 25 16:40:22 DietPi weewx[421]: File 
"/usr/share/weewx/weewx/reportengine.py", line 300, in start
Mar 25 16:40:22 DietPi weewx[421]:   self.run()
Mar 25 16:40:22 DietPi weewx[421]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 157, in run
Mar 25 16:40:22 DietPi weewx[421]:   
self.initExtensions(gen_dict[section_name])
Mar 25 16:40:22 DietPi weewx[421]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 199, in initExtensions
Mar 25 16:40:22 DietPi weewx[421]:   class_ = 
weeutil.weeutil._get_object(x)
Mar 25 16:40:22 DietPi weewx[421]: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1130, in _get_object
Mar 25 16:40:22 DietPi weewx[421]:   mod = __import__(module)
Mar 25 16:40:22 DietPi weewx[421]:   ValueError: Empty module name
Mar 25 16:40:22 DietPi weewx[421]:   Generator terminated
Mar 25 16:40:22 DietPi weewx[421]: manager: Daily summary version is 2.0
Mar 25 16:40:22 Die

Re: [weewx-user] Re: weewx-realtime_gauge-data not working

[Tom Robertson]

Did you set the path under [RealtimeGaugeData] in weewx.config and put the 
post_gauge-data.php in the directory on your remote server?  I believe using 
HTTP POST is the only practical way to get realtime gauge data if you are 
uploading to a remote server.

   # Remote URL to which the gauge-data.txt data will be posted via HTTP POST.
# Optional, omit to disable HTTP POST.
remote_server_url = http://remote/address
-
Tom

> On Mar 25, 2019, at 9:41 AM, Andrea Cecilia  wrote:
> 
> Hi Gary, 
> thank you for helping me. Neither I know why software generation was set; now 
> I changed it in hardware generation and that error seems to be disappeared. 
> But gauges aren't still getting live updated: they receive an update every 5 
> minutes, id est the archive interval, and every time they get the previous 
> update (for example, at 15:35 they get updated at 15:30).  This is the log 
> now:
> 
> Mar 25 15:31:35 raspberrypi-romaeur weewx[10234]: engine: Using configuration 
> file /home/weewx/weewx.conf
> Mar 25 15:31:35 raspberrypi-romaeur weewx[10234]: engine: Debug is 1
> Mar 25 15:31:35 raspberrypi-romaeur weewx[10234]: engine: Initializing engine
> Mar 25 15:31:35 raspberrypi-romaeur weewx[10234]: engine: Loading station 
> type Vantage (weewx.drivers.vantage)
> Mar 25 15:31:35 raspberrypi-romaeur weewx[10234]: vantage: Driver version is 
> 3.1.1
> Mar 25 15:31:35 raspberrypi-romaeur weewx[10234]: vantage: Opened up ethernet 
> host 192.168.0.11 on port 2. timeout=35.0, tcp_send_delay=0.5
> Mar 25 15:31:36 raspberrypi-romaeur weewx[10234]: vantage: Gentle wake up of 
> console successful
> Mar 25 15:31:37 raspberrypi-romaeur weewx[10234]: vantage: Hardware type is 17
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: vantage: ISS ID is 1
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: vantage: Hardware name: 
> Vantage Vue
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Loading service 
> weewx.engine.StdTimeSynch
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Finished loading 
> service weewx.engine.StdTimeSynch
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Loading service 
> weewx.engine.StdConvert
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: StdConvert target 
> unit is 0x10
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Finished loading 
> service weewx.engine.StdConvert
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Loading service 
> weewx.engine.StdCalibrate
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Finished loading 
> service weewx.engine.StdCalibrate
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Loading service 
> weewx.engine.StdQC
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Finished loading 
> service weewx.engine.StdQC
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Loading service 
> weewx.wxservices.StdWXCalculate
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: wxcalculate: The following 
> values will be calculated: barometer=prefer_hardware, 
> windchill=prefer_hardware, dewpoint=prefer_hardware, appTemp=prefer_hardware, 
> rainRate=prefer_hardware, windrun=prefer_hardware, heatindex=prefer_hardware, 
> maxSolarRad=prefer_hardware, humidex=prefer_hardware, 
> pressure=prefer_hardware, inDewpoint=prefer_hardware, ET=prefer_hardware, 
> altimeter=prefer_hardware, cloudbase=prefer_hardware
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: wxcalculate: The following 
> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Finished loading 
> service weewx.wxservices.StdWXCalculate
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Loading service 
> weewx.engine.StdArchive
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Archive will use 
> data binding wx_binding
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Record generation 
> will be attempted in 'hardware'
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Using archive 
> interval of 300 seconds (specified by hardware)
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Use LOOP data in 
> hi/low calculations: 1
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: manager: Daily summary 
> version is 2.0
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Using binding 
> 'wx_binding' to database 'weewx.sdb'
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: manager: Starting backfill 
> of daily summaries
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Finished loading 
> service weewx.engine.StdArchive
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Loading service 
> weewx.restx.StdStationRegistry
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: restx: StationRegistry: 
> Registration not requested.
> Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Finished loading 
> service weewx.restx.StdStationR

[weewx-user] Re: How to Include Modern XTide in Forecasting Extension?

[V. Kelly Bellis]

Matt - How's it going?

One thought that keeps coming up, are any of your tests being done on a 
system where the only xtide installation is v2.15.2?


On Friday, March 22, 2019 at 1:08:39 PM UTC-4, mwall wrote:
>
>
> yay!  i see exactly the same output when i run tide with those options, 
> whether i use tide 2.11 or tide 2.15.2
>
> but your weewx-forecast still gets nothing.  on the other hand, my 
> weewx-forecast *does* see the output and happily parses it.
>
> so the obvious difference is still not so obvious.
>
> please try the attached forecast code to see if that will shed any more 
> light.  it has some additional generate/parse debug output, as well as 
> python3-readiness (not that that will help you, but since i'm in the code, 
> we may as well take care of everything and test tom's python3 changes.  it 
> has been running fine for me.)
>
> after you download forecast-3.4.0rc1.py to the Downloads folder on the 
> pi, the process looks something like this:
>
> sudo mv /usr/share/weewx/user/forecast.py /usr/share/weewx/user/
> forecast-3.2.2.py
> sudo cp ~/Downloads/forecast-3.4.0rc1.py /usr/share/weewx/user/forecast.py
> sudo /etc/init.d/weewx stop
> sudo /etc/init.d/weewx start
>
> 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: weewx-realtime_gauge-data not working

[Andrea Cecilia]

Hi Gary, 
thank you for helping me. Neither I know why software generation was set; 
now I changed it in hardware generation and that error seems to be 
disappeared. But gauges aren't still getting live updated: they receive an 
update every 5 minutes, id est the archive interval, and every time they 
get the previous update (for example, at 15:35 they get updated at 15:30).  
This is the log now:

Mar 25 15:31:35 raspberrypi-romaeur weewx[10234]: engine: Using 
configuration file /home/weewx/weewx.conf
Mar 25 15:31:35 raspberrypi-romaeur weewx[10234]: engine: Debug is 1
Mar 25 15:31:35 raspberrypi-romaeur weewx[10234]: engine: Initializing 
engine
Mar 25 15:31:35 raspberrypi-romaeur weewx[10234]: engine: Loading station 
type Vantage (weewx.drivers.vantage)
Mar 25 15:31:35 raspberrypi-romaeur weewx[10234]: vantage: Driver version 
is 3.1.1
Mar 25 15:31:35 raspberrypi-romaeur weewx[10234]: vantage: Opened up 
ethernet host 192.168.0.11 on port 2. timeout=35.0, tcp_send_delay=0.5
Mar 25 15:31:36 raspberrypi-romaeur weewx[10234]: vantage: Gentle wake up 
of console successful
Mar 25 15:31:37 raspberrypi-romaeur weewx[10234]: vantage: Hardware type is 
17
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: vantage: ISS ID is 1
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: vantage: Hardware name: 
Vantage Vue
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Loading service 
weewx.engine.StdTimeSynch
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Finished loading 
service weewx.engine.StdTimeSynch
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Loading service 
weewx.engine.StdConvert
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: StdConvert target 
unit is 0x10
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Finished loading 
service weewx.engine.StdConvert
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Loading service 
weewx.engine.StdCalibrate
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Finished loading 
service weewx.engine.StdCalibrate
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Loading service 
weewx.engine.StdQC
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Finished loading 
service weewx.engine.StdQC
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: wxcalculate: The 
following values will be calculated: barometer=prefer_hardware, 
windchill=prefer_hardware, dewpoint=prefer_hardware, 
appTemp=prefer_hardware, rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: wxcalculate: The 
following algorithms will be used for calculations: altimeter=aaNOAA, 
maxSolarRad=RS
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Finished loading 
service weewx.wxservices.StdWXCalculate
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Loading service 
weewx.engine.StdArchive
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Archive will use 
data binding wx_binding
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Record generation 
will be attempted in 'hardware'
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Using archive 
interval of 300 seconds (specified by hardware)
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Use LOOP data in 
hi/low calculations: 1
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: manager: Daily summary 
version is 2.0
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: manager: Starting 
backfill of daily summaries
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Finished loading 
service weewx.engine.StdArchive
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Loading service 
weewx.restx.StdStationRegistry
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: restx: StationRegistry: 
Registration not requested.
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Finished loading 
service weewx.restx.StdStationRegistry
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Loading service 
weewx.restx.StdWunderground
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: restx: WU essentials: {}
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: restx: Wunderground-PWS: 
Data for station ILAZIORO81 will be posted
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Finished loading 
service weewx.restx.StdWunderground
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: engine: Loading service 
weewx.restx.StdPWSweather
Mar 25 15:31:40 raspberrypi-romaeur weewx[10234]: restx: PWSweather: 
Posting not enabled.
Mar 25 15:31:40 raspberrypi-romaeur weewx

[weewx-user] Re: Add additional rain gauge via second data source

[gjr80]

The vantage driver is somewhat complex. How the vantage driver operates 
depends on whether hardware or software record generation is in use. If 
software record generation is in use then the vantage driver obtains loop 
packets from the console (using the LOOP command) and the loop packets are 
then passed to WeeWX. This goes on continuously. WeeWX accumulates the loop 
packets and at the end of each archive interval WeeWX synthesises an 
archive record from the accumulated loop packets. This archive record is 
then further processed by various services, saved to database and used as 
necessary in report generation.

If hardware record generation is in use then the same loop packet processes 
occur as for software record generation (ie the driver passes loop packets 
to WeeWX and WeeWX accumulates them) but at the end of the archive interval 
instead of WeeWX synthesising an archive record from the accumulated loop 
packets, WeeWX asks the driver to obtain an archive record from the 
console. The driver uses the DMPAFT command to obtain the archive record 
and this archive record is passed back to WeeWX. This hardware archive 
record is further processed by various services, saved to database and used 
as necessary in report generation.

As far as I know the DMPAFT command is only used at the end of the archive 
interval (eg every 5 minutes) and not very few seconds. I think to dig any 
further into the issue would take some detailed analysis of how the 
WeatherDuino responds to various commands. I suspect that somewhere the 
behaviour when the WeatherDuino receives the DMPAFT command is slightly 
different to the Davis console/logger. You should be able to instrument the 
vantage driver to log anything from raw data from the console/logger 
through to the decoded observations and packets/records. The good thing is 
the Davis protocols are documented and in the public domain so it should be 
easy to compare actual and expected responses.

Gary

On Sunday, 24 March 2019 09:03:28 UTC+10, engolling wrote:
>
> Hi Gary,
> I checked the emulation of the WeatherDuino in the code and from my point 
> of view it seems to be implemented as in the protocol description.
> Nevertheless it might differ in any behaviour which is not exactly defined 
> in the description.
>
> It's very hard for me to understand the python code of the vantage driver 
> since I am not familiar with the language.
> I estimate that the vantage driver make the weewx engine to save an 
> archive record each time it gets one from the hardware.
> According to my observations und the upper preconditions it seems that 
> archive records are received in the same frequency as the LOOP packets.
> This would mean that the vantage driver polls with a DMPAFT command each 
> view seconds.
> Do you have any knowledge about this matter and do you know how it should 
> work correctly?
>
> To get this issue solved I think it would be necessary to get a serial 
> sniffer in place to be able to see the communications between both devices.
> Can I simply add some logs in the source of the vantage driver, like I did 
> in my data service? 
>
> Regards,
> engolling
>
> Am Freitag, 22. März 2019 00:48:49 UTC+1 schrieb gjr80:
>>
>> It seems that the WeatherDuino emulation of the Davis logger may still 
>> have some issues. It's possible that the WeeWX vantage driver has some 
>> issues but the driver is mature and has been in use for many years 
>> communicating with actual Davis hardware without issue. One thing I have 
>> noticed with some of the other PWS software packages is that they seem to 
>> operate using the vantage loop packets only, whereas WeeWX has the option 
>> of operating with loop packets only (record_generation=software) or a 
>> combination of loop packets and hardware archive records (
>> record_generation=hardware). That may explain why no one else sees this 
>> issue. I am certain I have seen another WeeWX user who was using the 
>> WeatherDuino as a Davis emulator and there were some clear issues with the 
>> emulator. Unfortunately I cannot find that thread.
>>
>> You can obtain extra debug info in the log by setting debug=1 in 
>> weewx.conf, though for the vantage driver I doubt this will give you too 
>> much more information. The vantage driver does not have the debug 
>> capabilities that some other driver have so that you can see individual 
>> commands and responses. 
>>
>> Gary
>>
>> On Wednesday, 20 March 2019 08:26:33 UTC+10, engolling wrote:
>>>
>>> Hi Gary,
>>>
>>> I disabled my data service and the errors still were there. See the 
>>> logfile in attachment.
>>>
>>> So I assumed that there is a problem with the vantage driver in 
>>> combination with my hardware.
>>> So I changed in weewx.conf to
>>> # If possible, new archive records are downloaded from the station
>>> # hardware. If the hardware does not support this, then new archive
>>> # records will be generated in software.
>>> # Set the following to "so

[weewx-user] Re: weewx-realtime_gauge-data not working

[gjr80]

Hi,

I suspect that for some reason your station is not including the field 
rxCheckPercent in the archive records (well at least the archive record in 
the log extract). We can look into that further to see if that is the 
indeed the case. In the meantime you can turn off the lost contact check 
off by setting the ignore_lost_contact option. In weewx.conf locate the 
[RealtimeGaugeData] stanza and insert an entry ignore_lost_contact = True, 
it should look something like this:

[RealtimeGaugeData]

ignore_lost_contact = True


Save weewx.conf then restart WeeWX or do a config reload. If your gauges do 
not update as expected we need to take a step back and confirm that 
gauge-data.txt is being generated and is being updated as it should. This 
needs to be done on your WeeWX machine. If gauge-data.txt is being 
regularly generated check that it is being uploaded/transferred to your web 
server. 

As for the possible rxCheckPercent issue, you are running the vantage 
driver in software record generation, whereas as most folks tend to use 
hardware record generation with the Davis stations. You also appear to be 
using the IP logger. neither of these should make any difference though.

Does the '*Could not determine sensor contact state'* message appear on 
every archive record (ie every 5 minutes in the log), or just now and then? 
Could you try running WeeWX directly, this will cause the loop packets 
(indicated by lines starting with LOOP:) and archive records (indicated by 
lines starting with REC:) to be displayed on screen. Is the field 
RxCheckPercent appearing in each archive record? Post a screen capture 
showing 2 or 3 REC: lines if you can.

Gary

On Monday, 25 March 2019 21:44:29 UTC+10, Andrea Cecilia wrote:
>
> Hi,
>
> I'm trying to install realtime_gauge-data 
> , without good 
> results. I followed the instruction reported in the linked page: as 
> prerequisite, I had installed steel series gauges, and I verifyed they were 
> working. Then, I installed weewx-realtime_gauge-data following the 
> instructions for automatic installation (with wee_extensions). Everything 
> good. But I don't see the gauges updating in real time! This is a log in 
> debug mode. I highlighted the line where I think there is the problem.
>
> Can you help me?
>
>
> Mar 25 12:39:27 raspberrypi-romaeur weewx[9561]: engine: Using 
> configuration file /home/weewx/weewx.conf
> Mar 25 12:39:27 raspberrypi-romaeur weewx[9561]: engine: Debug is 1
> Mar 25 12:39:27 raspberrypi-romaeur weewx[9561]: engine: Initializing 
> engine
> Mar 25 12:39:27 raspberrypi-romaeur weewx[9561]: engine: Loading station 
> type Vantage (weewx.drivers.vantage)
> Mar 25 12:39:27 raspberrypi-romaeur weewx[9546]: Starting weewx weather 
> system: weewx.
> Mar 25 12:39:27 raspberrypi-romaeur systemd[1]: Started LSB: weewx weather 
> system.
> Mar 25 12:39:27 raspberrypi-romaeur weewx[9561]: vantage: Driver version 
> is 3.1.1
> Mar 25 12:39:27 raspberrypi-romaeur weewx[9561]: vantage: Opened up 
> ethernet host 192.168.0.11 on port 2. timeout=35.0, tcp_send_delay=0.5
> Mar 25 12:39:27 raspberrypi-romaeur weewx[9561]: vantage: Gentle wake up 
> of console successful
> Mar 25 12:39:28 raspberrypi-romaeur weewx[9561]: vantage: Hardware type is 
> 17
> Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: vantage: ISS ID is 1
> Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: vantage: Hardware name: 
> Vantage Vue
> Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Loading service 
> weewx.engine.StdTimeSynch
> Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Finished loading 
> service weewx.engine.StdTimeSynch
> Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Loading service 
> weewx.engine.StdConvert
> Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: StdConvert target 
> unit is 0x10
> Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Finished loading 
> service weewx.engine.StdConvert
> Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Loading service 
> weewx.engine.StdCalibrate
> Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Finished loading 
> service weewx.engine.StdCalibrate
> Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Loading service 
> weewx.engine.StdQC
> Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Finished loading 
> service weewx.engine.StdQC
> Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Loading service 
> weewx.wxservices.StdWXCalculate
> Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: wxcalculate: The 
> following values will be calculated: barometer=prefer_hardware, 
> windchill=prefer_hardware, dewpoint=prefer_hardware, 
> appTemp=prefer_hardware, rainRate=prefer_hardware, windrun=prefer_hardware, 
> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
> humidex=prefer_hardware, pressure=prefer_hardware, 
> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=

[weewx-user] Re: Error with forecast.html

[Yves Martin]

Right, I'm using the Bootstrap, modified for my uses and forecast.html stop 
working from the last update.

forecast table is:

## forecast display for weewx - Copyright 2012-2013 Matthew Wall
## $Id: forecast_table.inc 1965 2014-01-27 19:26:24Z mwall $
## Include this file to display forecast data.  This file uses icons from 
the
## forecast icon set.

## version = 0.1

(...)

Yves,
YMartin.com/meteo

Le dimanche 17 mars 2019 11:59:27 UTC-4, Pat a écrit :
>
> Andrew, good point. I just looked through Bootstrap and don't see the 
> forecast.html that's referenced. 
>
> Maybe it's the forecasting extension 
> ? If so, looks like 
> matthew updated it recently.
>
> On Sunday, March 17, 2019 at 11:51:35 AM UTC-4, Andrew Milner wrote:
>>
>> I do not believe the bootstrap skin includes a forecast page as standard 
>> - so the template in use is a big unknown...
>>
>> On Sunday, 17 March 2019 17:40:37 UTC+2, Pat wrote:
>>>
>>> We need more information from you in order to help. 
>>>
>>> Looks like you are using the Bootstrap skin 
>>> ?
>>>  
>>> If so, you might need to contact the author if there's no progress in this 
>>> thread. 
>>>
>>> I think this might be the repo for the Bootstrap 
>>> 
>>>  
>>> skin?
>>>
>>>
>>> On Saturday, March 16, 2019 at 8:51:14 AM UTC-4, Yves Martin wrote:

 Hi,

 I have an error with the forecast here. I have to disabled it to make 
 weewx working correctly. Any idea ?

 (...)

 Mar 16 08:46:24 meteo-raspi weewx[23094]: GaugeGenerator: Generated 4 
 images for StandardReport in 7.59 seconds
 Mar 16 08:46:24 meteo-raspi weewx[23094]: cheetahgenerator: using 
 search list ['weewx.cheetahgenerator.Almanac', 
 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator$ (...)
 Mar 16 08:46:24 meteo-raspi weewx[23094]: manager: Daily summary 
 version is 1.0
 Mar 16 08:46:28 meteo-raspi weewx[23094]: cheetahgenerator: Generate 
 failed with exception ''
 Mar 16 08:46:28 meteo-raspi weewx[23094]: cheetahgenerator:  
 Ignoring template /etc/weewx/skins/Bootstrap/forecast.html.tmpl
 Mar 16 08:46:28 meteo-raspi weewx[23094]: cheetahgenerator:  
 Reason: cannot find 'wloc'
 Mar 16 08:46:28 meteo-raspi weewx[23094]:   Traceback (most recent 
 call last):
 Mar 16 08:46:28 meteo-raspi weewx[23094]: File 
 "/usr/share/weewx/weewx/cheetahgenerator.py", line 332, in generate
 Mar 16 08:46:28 meteo-raspi weewx[23094]:   
 fd.write(str(compiled_template))
 Mar 16 08:46:28 meteo-raspi weewx[23094]: File 
 "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
 __str__
 Mar 16 08:46:28 meteo-raspi weewx[23094]:   rc = getattr(self, 
 mainMethName)()
 Mar 16 08:46:28 meteo-raspi weewx[23094]: File 
 "_etc_weewx_skins_Bootstrap_forecast_html_tmpl.py", line 177, in respond
 Mar 16 08:46:28 meteo-raspi weewx[23094]: File 
 "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1615, in 
 _handleCheetahInclude
 Mar 16 08:46:28 meteo-raspi weewx[23094]:   
 self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
 Mar 16 08:46:28 meteo-raspi weewx[23094]: File 
 "_etc_weewx_skins_Bootstrap_inc_forecast_table_inc.py", line 855, in 
 respond
 Mar 16 08:46:28 meteo-raspi weewx[23094]:   NotFound: cannot find 
 'wloc'
 Mar 16 08:46:28 meteo-raspi weewx[23094]: cheetahgenerator: Generated 
 15 files for report StandardReport in 4.23 seconds
 Mar 16 08:46:28 meteo-raspi weewx[23094]: manager: Daily summary 
 version is 1.0
 Mar 16 08:46:34 meteo-raspi weewx[23094]: imagegenerator: Generated 25 
 images for StandardReport in 5.35 seconds
 Mar 16 08:46:34 meteo-raspi weewx[23094]: copygenerator: copied 0 files 
 to /var/www/weewx
 Mar 16 08:46:34 meteo-raspi weewx[23094]: reportengine: Running report 
 'wxobs'
 Mar 16 08:46:34 meteo-raspi weewx[23094]: reportengine: Found 
 configuration file /etc/weewx/skins/wxobs/skin.conf for report 'wxobs'

 (...)

 Yves,
 YMartin.com/meteo

>>>

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

[weewx-user] Re: weewx - interceptor - acurite access

[rich T]

Thanks, will give it a try this evening.

On Monday, March 25, 2019 at 12:52:24 AM UTC-4, mwall wrote:
>
> On Sunday, March 24, 2019 at 10:59:25 PM UTC-4, rich T wrote:
>>
>> Was wondering, before I go crazy, if the weewx-interceptor driver works 
>> with the Acurite Access. 
>>
>
> try using device_type=wu-client
>
> the smarthub protocol is not the same as the wu protocol, and the access 
> uses the wu protocol
>
>  
>

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

[weewx-user] weewx-realtime_gauge-data not working

[Andrea Cecilia]

Hi,

I'm trying to install realtime_gauge-data 
, without good results. 
I followed the instruction reported in the linked page: as prerequisite, I 
had installed steel series gauges, and I verifyed they were working. Then, 
I installed weewx-realtime_gauge-data following the instructions for 
automatic installation (with wee_extensions). Everything good. But I don't 
see the gauges updating in real time! This is a log in debug mode. I 
highlighted the line where I think there is the problem.

Can you help me?


Mar 25 12:39:27 raspberrypi-romaeur weewx[9561]: engine: Using 
configuration file /home/weewx/weewx.conf
Mar 25 12:39:27 raspberrypi-romaeur weewx[9561]: engine: Debug is 1
Mar 25 12:39:27 raspberrypi-romaeur weewx[9561]: engine: Initializing engine
Mar 25 12:39:27 raspberrypi-romaeur weewx[9561]: engine: Loading station 
type Vantage (weewx.drivers.vantage)
Mar 25 12:39:27 raspberrypi-romaeur weewx[9546]: Starting weewx weather 
system: weewx.
Mar 25 12:39:27 raspberrypi-romaeur systemd[1]: Started LSB: weewx weather 
system.
Mar 25 12:39:27 raspberrypi-romaeur weewx[9561]: vantage: Driver version is 
3.1.1
Mar 25 12:39:27 raspberrypi-romaeur weewx[9561]: vantage: Opened up 
ethernet host 192.168.0.11 on port 2. timeout=35.0, tcp_send_delay=0.5
Mar 25 12:39:27 raspberrypi-romaeur weewx[9561]: vantage: Gentle wake up of 
console successful
Mar 25 12:39:28 raspberrypi-romaeur weewx[9561]: vantage: Hardware type is 
17
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: vantage: ISS ID is 1
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: vantage: Hardware name: 
Vantage Vue
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Loading service 
weewx.engine.StdTimeSynch
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Finished loading 
service weewx.engine.StdTimeSynch
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Loading service 
weewx.engine.StdConvert
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: StdConvert target 
unit is 0x10
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Finished loading 
service weewx.engine.StdConvert
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Loading service 
weewx.engine.StdCalibrate
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Finished loading 
service weewx.engine.StdCalibrate
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Loading service 
weewx.engine.StdQC
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Finished loading 
service weewx.engine.StdQC
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: wxcalculate: The following 
values will be calculated: barometer=prefer_hardware, 
windchill=prefer_hardware, dewpoint=prefer_hardware, 
appTemp=prefer_hardware, rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Finished loading 
service weewx.wxservices.StdWXCalculate
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Loading service 
weewx.engine.StdArchive
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Archive will use 
data binding wx_binding
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Record generation 
will be attempted in 'software'
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Using archive 
interval of 300 seconds (software record generation)
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Use LOOP data in 
hi/low calculations: 1
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: manager: Daily summary 
version is 2.0
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: manager: Starting backfill 
of daily summaries
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Finished loading 
service weewx.engine.StdArchive
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Loading service 
weewx.restx.StdStationRegistry
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: restx: StationRegistry: 
Registration not requested.
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Finished loading 
service weewx.restx.StdStationRegistry
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: engine: Loading service 
weewx.restx.StdWunderground
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: restx: WU essentials: {}
Mar 25 12:39:32 raspberrypi-romaeur weewx[9561]: restx: Wunderground-PWS: 
Data for station ILAZIORO81 will be posted
Mar 25 12:39:32 raspberrypi-romaeur weew