[weewx-user] Re: sftp upload not working

[Fam de Munck]

It seems you are confusing sftp and ftps.

Please have a look at:
https://github.com/weewx/weewx/wiki
http://www.weewx.com/docs/usersguide.htm#config_FTP


Op dinsdag 30 juni 2020 17:21:05 UTC+2 schreef Andre:
>
> I have problems to upload with sftp from my RPi to my new vServer.
>
> Jun 30 16:56:28 weewx weewx[2174] DEBUG weewx.reportengine: Running 
> report 'FTP'
> Jun 30 16:56:28 weewx weewx[2174] DEBUG weewx.reportengine: Found 
> configuration file /etc/weewx/skins/Ftp/skin.conf for report 'FTP'
> Jun 30 16:56:28 weewx weewx[2174] DEBUG weeutil.ftpupload: Attempting 
> secure connection to x.xx.xxx.xxx
> Jun 30 16:56:29 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:29 CEST (1593528989)
> Jun 30 16:56:31 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:31 CEST (1593528991)
> Jun 30 16:56:33 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:33 CEST (1593528993)
> Jun 30 16:56:35 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:35 CEST (1593528995)
> Jun 30 16:56:37 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:37 CEST (1593528997)
> Jun 30 16:56:39 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:39 CEST (1593528999)
> Jun 30 16:56:41 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:41 CEST (1593529001)
> Jun 30 16:56:43 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:43 CEST (1593529003)
> Jun 30 16:56:45 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:45 CEST (1593529005)
> Jun 30 16:56:47 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:47 CEST (1593529007)
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine: ftpgenerator: 
> (0): caught exception '': timed out
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:   
> Traceback (most recent call last):
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>File "/usr/share/weewx/weewx/reportengine.py", line 330, in run
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>  n = ftp_data.run()
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>File "/usr/share/weewx/weeutil/ftpupload.py", line 127, in run
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>  ftp_server.connect(self.server, self.port)
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>File "/usr/lib/python3.7/ftplib.py", line 155, in connect
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>  self.welcome = self.getresp()
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>File "/usr/lib/python3.7/ftplib.py", line 236, in getresp
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>  resp = self.getmultiline()
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>File "/usr/lib/python3.7/ftplib.py", line 226, in getmultiline
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>  nextline = self.getline()
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>File "/usr/lib/python3.7/ftplib.py", line 204, in getline
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>  line = self.file.readline(self.maxline + 1)
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>File "/usr/lib/python3.7/socket.py", line 589, in readinto
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>  return self._sock.recv_into(b)
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>  socket.timeout: timed out
> Jun 30 16:56:48 weewx weewx[2174] DEBUG weeutil.ftpupload: Attempting 
> secure connection to x.xx.xxx.xxx
>
> [[FTP]]
> # FTP'ing the results to a webserver is treated as just another 
> report,
> # albeit one with an unusual report generator!
> skin = Ftp
> 
> # If you wish to use FTP, set "enable" to "true", then
> # fill out the next four lines.
> # Use quotes around passwords to guard against parsing errors.
> enable = true
> user = username
> password = "password"
> server = x.xx.xxx.xxx# The ftp server name, e.g, 
> www.myserver.org
> path = /var/www/html/www.doamainname.com/public_html# The 
> destination directory, e.g., /weather
> 
> # Set to True for an FTP over TLS (FTPS) connection. Not all 
> servers
> # support this.
> secure_ftp = true
> 
> # To upload files from something other than what HTML_ROOT is set
> # to above, specify a different HTML_ROOT here.
> HTML_ROOT = /var/www/ht

[weewx-user] Weewx 4.1 or later mqtt client

['ml' via weewx-user]

Hello, is it possible to publish the weather data via MQTT also with 
weewx4.x ?

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/b920335d-e93a-4374-9bd5-f175dc36563eo%40googlegroups.com.

[weewx-user] Decimal comma in xml files bug?

[Michael Meyer]

Hello, I'm running weewx 4.1.1 on Rpi 3b installed with setup.py.  To get a 
clean installation I installed buster from scratch. 
Before I had installed version 3xxx on the same Rpi with Jessie running.
With a xml.tmpl I grabed the datas to work with them on my smart home 
system Domoticz.
With the new installation a problem popped up. The xml file have decimal 
comma instead of decimal points. It's not just my template is also eg. 
/home/weewx/public_html/rss.xml.
As I read in www decimal point for xml is necessary. My question is it a 
bug or is there something wrong within my system what I can change.
Any help appreciate
Michael

-- 
You received this message because you are subscribed to the Google 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/2544a5c5-d34d-426d-b5ad-d544cc5b6792n%40googlegroups.com.

[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

[gjr80]

Just to close this off I installed the updated vantage driver on my system 
and sunrise/sunset from the console is spot on today. If the anomaly 
bothers you and you can't wait for 4.1.2 to be released you can download 
the patched vantage driver here 
.
 
Just use 

$ wget -P /var/tmp https:
//raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/vantage.py

to download to /var/tmp and then copy in place of the existing driver (
/home/weewx/bin/weewx/drivers/vantage.py or 
/usr/share/weewx/weewx/drivers/vantage.py) and restart WeeWX. You will need 
to run WeeWX directly and observer the sunrise/sunset values in the loop 
packets or use some other means to view the loop data as WeeWX does not 
normally display/use the console provided sunrise/sunset times.

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/672bf2e7-4403-47d9-8bef-5a763ae618f1o%40googlegroups.com.

Re: [weewx-user] Re: Newbie Looking For Hardware Recommendations

[Anthony Hoppe]

Ooo.  That is *very* nice to know.  Thanks for sharing!  I very well may
start with the Ecowitt HP2551...

On 6/30/20 5:16 PM, galfert wrote:
> The Ecowitt HP2551 has a "Customized" server upload feature. You can use
> that to point to your WeeWX system and then the WeeWX system with the
> Interceptor driver installed will pick up the data directly from the
> console.
> 
> -- 
> 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/8Ym49pN2Gq8/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/67b2697c-20aa-4d90-9966-9966ec8cf2e0o%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/ee521350-6bc9-bba4-98c2-920bae6fc91f%40vofr.net.

Re: [weewx-user] Re: Newbie Looking For Hardware Recommendations

[galfert]

The Ecowitt HP2551 has a "Customized" server upload feature. You can use 
that to point to your WeeWX system and then the WeeWX system with the 
Interceptor driver installed will pick up the data directly from the 
console.

-- 
You received this message because you are subscribed to the Google 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/67b2697c-20aa-4d90-9966-9966ec8cf2e0o%40googlegroups.com.

[weewx-user] Re: Import of driver failed [Interceptor]

[Zsolt Máté]

Did anyone find a fix for this?
I'm in the same boat. Fresh raspberry pi image, clean install.

sudo PYTHONPATH=/usr/share/weewx python 
/usr/share/weewx/user/interceptor.py --device=observer --mode=sniff 
--iface=wlan0 --filter="src 10.3.141.115 and dst port 80"
mapped packet: {'barometer': 29.986, 'windchill': 45.5, 'dewpoint': 39.7, 
'pressure': 30.024, 'outHumidity': 77.0, 'UV': 1.0, 'radiation': 105.33, 
'rain': None, 'dateTime': 1593561263, 'windDir': 244.0, 'outTemp': 46.6, 
'windSpeed': 3.4, 'inHumidity': 44.0, 'inTemp': 69.6, 'windGust': 4.5, 
'usUnits': 1}


Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine: 
>>   Observer.Parser(), handler=Observer.Handler, **stn_dict)
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/user/interceptor.py", line 427, in __init__
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine: 
>>   iface, pcap_filter, promiscuous)
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/user/interceptor.py", line 469, in __init__
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine: 
>>   self.sniffer.open_live(iface, snaplen, pval, timeout_ms)
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine: 
>> File "/usr/lib/python2.7/dist-packages/pcap.py", line 108, in open_live
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine: 
>>   def open_live(self, *args): return _pcap.pcapObject_open_live(self, *args)
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
>> TypeError: in method 'pcapObject_open_live', argument 2 of type 'char *'
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL __main__: Unable to load 
>> driver: in method 'pcapObject_open_live', argument 2 of type 'char *'
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL __main__:   
>> Exiting...
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c16c9c11-7dac-41b9-b73f-79ee2e856edco%40googlegroups.com.

Re: [weewx-user] Re: Issue with NOAA Template when trying to add additional fields

[gjr80]

There is nothing that will directly give you the first of the month. The 
closest you can do is $days_ago:

$day($data_binding=‘some binding’, $days_ago=20).outTemp.maxtime

But of course as we move through the month the actual day provided will change. 
You could use a little in-line python in your template to calculate an offset 
based on the current day of month to use with the number of days ago and then 
use that in the tag, eg (untested):

#set $offset = (some calculation)
$day($data_binding=‘some binding’, $days_ago=$offset).outTemp.maxtime
$day($data_binding=‘some binding’, $days_ago=$offset+1).outTemp.maxtime

Not sure how well that will work (not sure if in-line calculation is supported 
in $day() tags) and it’s starting to get complex and messy.

For info detail on aggregate tag usage can be found in the Customization Guide 
(http://weewx.com/docs/customizing.htm#general_aggregation_periods).

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/d284759c-a6d0-4796-93b9-f5ddadd82ebbo%40googlegroups.com.

[weewx-user] sftp upload not working

[Andre]

I have problems to upload with sftp from my RPi to my new vServer.

Jun 30 16:56:28 weewx weewx[2174] DEBUG weewx.reportengine: Running report 
'FTP'
Jun 30 16:56:28 weewx weewx[2174] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Ftp/skin.conf for report 'FTP'
Jun 30 16:56:28 weewx weewx[2174] DEBUG weeutil.ftpupload: Attempting 
secure connection to x.xx.xxx.xxx
Jun 30 16:56:29 weewx weewx[2174] INFO weewx.restx: MQTT: Published record 
2020-06-30 16:56:29 CEST (1593528989)
Jun 30 16:56:31 weewx weewx[2174] INFO weewx.restx: MQTT: Published record 
2020-06-30 16:56:31 CEST (1593528991)
Jun 30 16:56:33 weewx weewx[2174] INFO weewx.restx: MQTT: Published record 
2020-06-30 16:56:33 CEST (1593528993)
Jun 30 16:56:35 weewx weewx[2174] INFO weewx.restx: MQTT: Published record 
2020-06-30 16:56:35 CEST (1593528995)
Jun 30 16:56:37 weewx weewx[2174] INFO weewx.restx: MQTT: Published record 
2020-06-30 16:56:37 CEST (1593528997)
Jun 30 16:56:39 weewx weewx[2174] INFO weewx.restx: MQTT: Published record 
2020-06-30 16:56:39 CEST (1593528999)
Jun 30 16:56:41 weewx weewx[2174] INFO weewx.restx: MQTT: Published record 
2020-06-30 16:56:41 CEST (1593529001)
Jun 30 16:56:43 weewx weewx[2174] INFO weewx.restx: MQTT: Published record 
2020-06-30 16:56:43 CEST (1593529003)
Jun 30 16:56:45 weewx weewx[2174] INFO weewx.restx: MQTT: Published record 
2020-06-30 16:56:45 CEST (1593529005)
Jun 30 16:56:47 weewx weewx[2174] INFO weewx.restx: MQTT: Published record 
2020-06-30 16:56:47 CEST (1593529007)
Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine: ftpgenerator: (0
): caught exception '': timed out
Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:   
Traceback (most recent call last):
Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/reportengine.py", line 330, in run
Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:    
   n = ftp_data.run()
Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine: 
File "/usr/share/weewx/weeutil/ftpupload.py", line 127, in run
Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:    
   ftp_server.connect(self.server, self.port)
Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine: 
File "/usr/lib/python3.7/ftplib.py", line 155, in connect
Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:    
   self.welcome = self.getresp()
Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine: 
File "/usr/lib/python3.7/ftplib.py", line 236, in getresp
Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:    
   resp = self.getmultiline()
Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine: 
File "/usr/lib/python3.7/ftplib.py", line 226, in getmultiline
Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:    
   nextline = self.getline()
Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine: 
File "/usr/lib/python3.7/ftplib.py", line 204, in getline
Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:    
   line = self.file.readline(self.maxline + 1)
Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine: 
File "/usr/lib/python3.7/socket.py", line 589, in readinto
Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:    
   return self._sock.recv_into(b)
Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
 socket.timeout: timed out
Jun 30 16:56:48 weewx weewx[2174] DEBUG weeutil.ftpupload: Attempting 
secure connection to x.xx.xxx.xxx

[[FTP]]
# FTP'ing the results to a webserver is treated as just another 
report,
# albeit one with an unusual report generator!
skin = Ftp

# If you wish to use FTP, set "enable" to "true", then
# fill out the next four lines.
# Use quotes around passwords to guard against parsing errors.
enable = true
user = username
password = "password"
server = x.xx.xxx.xxx# The ftp server name, e.g, 
www.myserver.org
path = /var/www/html/www.doamainname.com/public_html# The 
destination directory, e.g., /weather

# Set to True for an FTP over TLS (FTPS) connection. Not all servers
# support this.
secure_ftp = true

# To upload files from something other than what HTML_ROOT is set
# to above, specify a different HTML_ROOT here.
HTML_ROOT = /var/www/html/weewx/belchertown

# Most FTP servers use port 21
port = 22

# Set to 1 to use passive mode, zero for active mode
passive = 1


With sftp client I could transfer files to target machine without any 
issues.
Any ideas what can I check or doing for solving the problems?

-- 
You received this message because you are subscribed to the Google

Re: [weewx-user] Re: Newbie Looking For Hardware Recommendations

[Anthony Hoppe]

I will definitely look into this one.  Thanks for sharing, galfert.
When pulling data from the HP2551, are you able to pull data locally, or
do you have to pull it from one of the hosted services it reports to?


On 6/29/20 5:33 PM, galfert wrote:
> I think you should strongly consider the Ecowitt HP2551.
> Greatly expandable to even more fun and sensors later on. 
> 

-- 
You received this message because you are subscribed to the Google 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/efc4415e-6e78-9567-61cc-8e6419a3f7d4%40vofr.net.

Re: Fwd: Re: [weewx-user] Newbie Looking For Hardware Recommendations

[Anthony Hoppe]

Thanks for the information, Andy!  When you pull data using the AcuRite
1035, does it pull data locally (like, do you have WeeWX pointed to its
local IP and/or directly connected to some serial/USB adapter?) or are
you pulling data from one of the hosted services it reports to?


On 6/29/20 1:49 PM, VE4PER / Andy wrote:
> FYI for the group
> 
> 
> 
>  Forwarded Message 
> Subject:  Re: [weewx-user] Newbie Looking For Hardware Recommendations
> Date: Mon, 29 Jun 2020 15:31:02 -0500
> From: VE4PER / Andy 
> To:   Anthony 
> 
> 
> 
> Anthony,
> 
> I am using an AcuRite 1035 5 in 1 sensor system here and weewx linux
> software. The system has been fairly reliable for the price (about $135
> - $155 for display/usb comm unit and outdoor mast sensor unit freight
> included) The only problem I have with it is the wind speed anemometer
> cups got broken on a battery change session and I ordered a whole
> replacement 5 in 1 sensor unit to replace it through amazon and they
> sent two units, supposedly new , that were both U/S. One had no 433 MHz
> RF output to talk to display unit and 2nd one had RF but no data stream.
> So sent both back. While waiting to sort it out I came across
> replacement cups that were inexpensive (less than $15 Cdn) free shipping
> if combined with something else so I ordered a set and repaired my
> current 5 in 1 sensor and it is back online now. It feeds CWOP, AWEKAS,
> WeatherUnderground as well as my own web site in addition to WEEWX
> site/maps.
> 
> I am a radio amateur and only interested in it from CANWARN/SKYWARN
> perspective so am not into as much data manipulation or coding of
> presentations. I have it running and feeding a MySQL/MariadB  on the
> same UbuntuStudio 20.04LTS machine. I like that optionas I can access
> the data with LibreOffice Base report generators and/or MS Access odbc
> connections and use it as interface to generate reports from there as
> well. I have been planning to have the SQL dB run on a separate
> dedicated server box, fortunately I have been a little slow in
> implementing that as vers 20.04LTS recent updates have made some changes
> that would affect the operation of the nfs-kernel-server such that it
> does not start without errors now and thus not a reliable connection
> resource for weewx.  dB resident on same machine as weewx avoids that so
> something to keep in mind.
> 
> Libre Office base is not yet as mature and super user intuitive and
> friendly as Access esp when using visual design views to run different
> types of queries easily. SELECT ones are OK but if you want to do UPDATE
> or other types the visual tools aren't there yet and one has to fall
> back on pure SQL text strings to do the job which isn't super convenient.
> 
> I don't have lightning sensors either but would definitely be of use to me.
> 
> When AWEKAS emails failure reports to me troubleshooting the comm link
> between the sensor and display unit is great help; I am using an RSP1A
> SDR receiver that can tune up into the 433 MHz freq band and sees the RF
> signals and rich T in a couple of previous posts here in the last couple
> of days has a way to decode those signals so you can see the actual real
> data sent from the sensor to the display to confirm it is serviceable.
> 
> If your interest lies in coding a bit with different skins etc to
> manipulate the interpretations of a lot of the data them probably await
> comments from a few others in the group here.
> 
> Cheers and good luck deciding  ---> choices are as wide and they are
> long LOL
> 
> 
> On 2020-06-29 2:16 p.m., Anthony wrote:
>> Hello!
>>
>> I am interested in starting down the rabbit hole that is weather
>> stations and data logging.  I've had a simple weather station for
>> about 10 years (a simple indoor and outdoor temperature probe setup
>> with standalone display), but this weather station recently bit the
>> dust.  I figure it's time to step up.  I'm a geek/nerd by nature
>> (sysadmin by trade) and the idea that I can build a WeeWX server and
>> collect local weather data sounds like a lot of fun.
>>
>> I'm looking at the list of supported hardware
>> (http://weewx.com/hardware.html) and my head is starting to spin,
>> heh.  I'm hoping the fine folks of this list can help point me in a
>> direction.
>>
>> I'm looking for a setup that meets the following requirements:
>>
>>     - A "dummy resistant" local display for the family.
>>     - Multiple datapoints...Temp, wind speed, wind direction, rain
>> gauge, relative humidity
>>     - The ability to collect data "off the grid".  Meaning, I don't
>> want to be dependent on any sort of "cloud" service.
>>
>> Some things that would be nice, but are definitely not required:
>>
>>     - Lightning detection would be neat, I think.  Or at least the
>> ability to *add* a lightning detection sensor.
>>     - Hard-wired sensor array (I am no stranger to pulling cable).  My
>> philosophy is that if it's a fixed device, it i

Re: [weewx-user] Re: Issue with NOAA Template when trying to add additional fields

[Rahul Bedi]

BTW if I was to manually replace $day with a variable that is, say, the
first day of the month ? How would I do that ?

I am trying to remove the loop and replace that with 31 lines that will be
one for each possible date.

Thx.

- Rahul

On Tue, Jun 30, 2020 at 7:28 PM Rahul Bedi  wrote:

> Thanks Tom and Gary. The only other way I can think of is to do the kludgy
> way of removing the loop altogether and doing it 31 times for the month :(.
> Not pretty but had to do that in hilo.inc
>
> - Rahul
>
> On Tue, Jun 30, 2020 at 7:14 PM Tom Keffer  wrote:
>
>> Yes, this is a limitation in the iterators: they cannot use a data
>> binding. There's probably a workaround, but I'd have to think about it a
>> bit.
>>
>> In the meantime, I've put up issue #580
>>  to track.
>>
>> Probably related to issue #384
>>  as well.
>>
>> -tk
>>
>> On Tue, Jun 30, 2020 at 6:16 AM Rahul Bedi  wrote:
>>
>>> Tried. I get a similar error:
>>>
>>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>>> weewx.cheetahgenerator: Generate failed with exception '>> 'exceptions.TypeError'>'
>>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>>> weewx.cheetahgenerator:  Ignoring template
>>> /etc/weewx/skins/Seasons/NOAA/NOAA--MM.txt.tmpl
>>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>>> weewx.cheetahgenerator:  Reason: 'TimespanBinder' object is not callable
>>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>>> weewx.cheetahgenerator:   Traceback (most recent call last):
>>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>>> weewx.cheetahgenerator: File
>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate
>>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>>> weewx.cheetahgenerator:   unicode_string =
>>> compiled_template.respond()
>>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>>> weewx.cheetahgenerator: File
>>> "cheetah__etc_weewx_skins_Seasons_NOAA_NOAA__MM_txt_tmpl_1593522919_43_84946.py",
>>> line 479, in respond
>>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>>> weewx.cheetahgenerator: File
>>> "cheetah__etc_weewx_skins_Seasons_NOAA_NOAA__MM_txt_tmpl_1593522919_43_84946.py",
>>> line 252, in __errorCatcher27
>>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>>> weewx.cheetahgenerator: File "", line 1, in 
>>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>>> weewx.cheetahgenerator:   TypeError: 'TimespanBinder' object is not
>>> callable
>>>
>>> On Tue, Jun 30, 2020 at 6:10 PM gjr80  wrote:
>>>
 Hi,

 Try using:

 $day($data_binding='purpleair_binding').pm2_5_atm.maxtime.format($Time)
 $day($data_binding='purpleair_binding').pm2_5_atm.max.nolabel($Count,
 $NONE)

 Gary


 On Tuesday, 30 June 2020 22:32:23 UTC+10, Rahul Bedi wrote:
>
> Hi,
>
> I have been trying to update the NOAA template to incorporate the air
> quality data in the monthly report, but when I added the two entries (in
> red)  in the file  NOAA--MM.txt.tmpl, I an error (attached at the 
> end).
> Interestingly the same two entries, in the hilo.inc file in the
> Seasons skin work fine.
>
> Even more interestingly, the same two entries placed just before the
> "MONTHLY ..." line, work just fine.
>
> Any idea about what am I doing wrong ?
>
> Thanks.
>
> - Rahul
>
>
> #errorCatcher Echo
> #set $YM="%Y %m"
> #set $D=" %d"
> #set $M=" %b"
> #set $Time=" %H:%M"
> #set $NODAY=" N/A"
> #set $Temp="%6.1f"
> #set $Wind="%6.1f"
> #set $Dir="%6.0f"
> #set $Count="%6d"
> #set $NONE="   N/A"
> #if $unit.unit_type_dict.group_rain == "mm"
> #set $Rain="%6.1f"
> #else
> #set $Rain="%6.2f"
> #end if
>
>
>MONTHLY CLIMATOLOGICAL SUMMARY for $month_name
> $year_name
>
>
> NAME: $station.location
> ELEV: $station.altitudeLAT:
> $station.latitude[0]-$station.latitude[1] $station.latitude[2]LONG:
> $station.longitude[0]-$station.longitude[1] $station.longitude[2]
>
>
>TEMPERATURE ($unit.label.outTemp.strip()), RAIN
> ($unit.label.rain.strip()), WIND SPEED ($unit.label.windSpeed.strip())
>
>  HEAT   COOL AVG
>   MEAN   DEGDEG  WIND
>  DOM
> DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED
>  HIGH   TIMEDIR
>
> ---
> #for $day in $month.days
> #if $day.barometer.count.raw
> $day.dateTime.format($D) $day.outTemp.avg.nolabel($Temp,$NONE)
> $day.outTemp.max.nolabel($Temp,$NONE) $day.outT

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

weeutil.RsyncUpload was expecting a string for port.  I was passing it an int.

I didn’t catch this as I was not specifying a port.  This should now be fixed 
in 1.3.1.  Would you please give it a try?

> On Jun 30, 2020, at 1:32 AM, Geni 0815  wrote:
> 
> 
>> 
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:   
>> Traceback (most recent call last):
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>  File "/usr/share/weewx/user/loopdata.py", line 521, in process_queue
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>self.compose_and_write_packet(pkt)
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>  File "/usr/share/weewx/user/loopdata.py", line 541, in 
>> compose_and_write_packet
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>self.write_packet(selective_pkt)
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>  File "/usr/share/weewx/user/loopdata.py", line 555, in write_packet
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>self.rsync_data(pkt['dateTime'])
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>  File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>rsync_upload.run()
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>  File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>if self.port is not None and len(self.port.strip()) > 0:
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:   
>> AttributeError: 'int' object has no attribute 'strip'
>> 
>> 
> Am Dienstag, 30. Juni 2020 09:47:44 UTC+2 schrieb Geni 0815:
>> 
>> @John: I have the following entry in the syslog, what is not suitable?
>> 
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>>> barometer_rate_secs: 10800
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>>> wind_rose_secs : 86400
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>>> wind_rose_points   : 16
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>> Traceback (most recent call last):
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>>   File "/usr/share/weewx/user/loopdata.py", line 521, in process_queue
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>> self.compose_and_write_packet(pkt)
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>>   File "/usr/share/weewx/user/loopdata.py", line 541, in 
>>> compose_and_write_packet
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>> self.write_packet(selective_pkt)
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>>   File "/usr/share/weewx/user/loopdata.py", line 555, in write_packet
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>> self.rsync_data(pkt['dateTime'])
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>>   File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>> rsync_upload.run()
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>>   File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>> if self.port is not None and len(self.port.strip()) > 0:
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>> AttributeError: 'int' object has no attribute 'strip'
>>> 
>> 
>>  
>> 
>> Am Samstag, 27. Juni 2020 21:18:06 UTC+2 schrieb John Kline:
>>> 
>>> I just now updated this extension to 1.1.  I would try it before resorting 
>>> to a clean install.
>>> 
 On Jun 27, 2020, at 12:16 PM, Michael Meyer  wrote:
 
 
 Hello John, I did grep and get some results. Next time I used grep again 
 no results. I uninstalled weewx because I did the first installation with 
 Debian. I did installation weewx with setup py. Again no loop_data.txt 
 created. I will do a fresh Buster light image next. After that I will do 
 also a complete new weewx installation. I will let you know if 
 successfully. Thx for your help!
 Michael
 
 John Kline  schrieb am Fr., 26. Juni 2020, 20:54:
> Well, I see loopdata in the log snippet you just sent.
> 
> Would you try the grep again?
> grep loopdata /var/log/syslog
> 
> And look for the loopdata file again?
> 
>> On Jun 26, 202

Re: [weewx-user] Re: Issue with NOAA Template when trying to add additional fields

[Rahul Bedi]

Thanks Tom and Gary. The only other way I can think of is to do the kludgy
way of removing the loop altogether and doing it 31 times for the month :(.
Not pretty but had to do that in hilo.inc

- Rahul

On Tue, Jun 30, 2020 at 7:14 PM Tom Keffer  wrote:

> Yes, this is a limitation in the iterators: they cannot use a data
> binding. There's probably a workaround, but I'd have to think about it a
> bit.
>
> In the meantime, I've put up issue #580
>  to track.
>
> Probably related to issue #384 
> as well.
>
> -tk
>
> On Tue, Jun 30, 2020 at 6:16 AM Rahul Bedi  wrote:
>
>> Tried. I get a similar error:
>>
>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>> weewx.cheetahgenerator: Generate failed with exception '> 'exceptions.TypeError'>'
>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>> weewx.cheetahgenerator:  Ignoring template
>> /etc/weewx/skins/Seasons/NOAA/NOAA--MM.txt.tmpl
>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>> weewx.cheetahgenerator:  Reason: 'TimespanBinder' object is not callable
>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>> weewx.cheetahgenerator:   Traceback (most recent call last):
>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>> weewx.cheetahgenerator: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate
>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>> weewx.cheetahgenerator:   unicode_string =
>> compiled_template.respond()
>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>> weewx.cheetahgenerator: File
>> "cheetah__etc_weewx_skins_Seasons_NOAA_NOAA__MM_txt_tmpl_1593522919_43_84946.py",
>> line 479, in respond
>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>> weewx.cheetahgenerator: File
>> "cheetah__etc_weewx_skins_Seasons_NOAA_NOAA__MM_txt_tmpl_1593522919_43_84946.py",
>> line 252, in __errorCatcher27
>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>> weewx.cheetahgenerator: File "", line 1, in 
>> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
>> weewx.cheetahgenerator:   TypeError: 'TimespanBinder' object is not
>> callable
>>
>> On Tue, Jun 30, 2020 at 6:10 PM gjr80  wrote:
>>
>>> Hi,
>>>
>>> Try using:
>>>
>>> $day($data_binding='purpleair_binding').pm2_5_atm.maxtime.format($Time)
>>> $day($data_binding='purpleair_binding').pm2_5_atm.max.nolabel($Count,
>>> $NONE)
>>>
>>> Gary
>>>
>>>
>>> On Tuesday, 30 June 2020 22:32:23 UTC+10, Rahul Bedi wrote:

 Hi,

 I have been trying to update the NOAA template to incorporate the air
 quality data in the monthly report, but when I added the two entries (in
 red)  in the file  NOAA--MM.txt.tmpl, I an error (attached at the end).
 Interestingly the same two entries, in the hilo.inc file in the Seasons
 skin work fine.

 Even more interestingly, the same two entries placed just before the
 "MONTHLY ..." line, work just fine.

 Any idea about what am I doing wrong ?

 Thanks.

 - Rahul


 #errorCatcher Echo
 #set $YM="%Y %m"
 #set $D=" %d"
 #set $M=" %b"
 #set $Time=" %H:%M"
 #set $NODAY=" N/A"
 #set $Temp="%6.1f"
 #set $Wind="%6.1f"
 #set $Dir="%6.0f"
 #set $Count="%6d"
 #set $NONE="   N/A"
 #if $unit.unit_type_dict.group_rain == "mm"
 #set $Rain="%6.1f"
 #else
 #set $Rain="%6.2f"
 #end if


MONTHLY CLIMATOLOGICAL SUMMARY for $month_name
 $year_name


 NAME: $station.location
 ELEV: $station.altitudeLAT:
 $station.latitude[0]-$station.latitude[1] $station.latitude[2]LONG:
 $station.longitude[0]-$station.longitude[1] $station.longitude[2]


TEMPERATURE ($unit.label.outTemp.strip()), RAIN
 ($unit.label.rain.strip()), WIND SPEED ($unit.label.windSpeed.strip())

  HEAT   COOL AVG
   MEAN   DEGDEG  WIND
  DOM
 DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED
  HIGH   TIMEDIR

 ---
 #for $day in $month.days
 #if $day.barometer.count.raw
 $day.dateTime.format($D) $day.outTemp.avg.nolabel($Temp,$NONE)
 $day.outTemp.max.nolabel($Temp,$NONE) $day.outTemp.maxtime.format($Time)
 $day.outTemp.min.nolabel($Temp,$NONE) $day.outTemp.mintime.format($Time)
 $day.heatdeg.sum.nolabel($Temp,$NONE) $day.cooldeg.sum.nolabel($Temp,$NONE)
 $day.rain.sum.nolabel($Rain,$NONE) $day.wind.avg.nolabel($Wind,$NONE)
 $day.wind.max.nolabel($Wind,$NONE) $day.wind.maxtime.format($Time)
 $day.wind.vecdir.nolabel($Dir,$NONE) 
 $day('purpleair_binding').pm2_5_atm.maxtime.format($

Re: [weewx-user] Re: Issue with NOAA Template when trying to add additional fields

[Tom Keffer]

Yes, this is a limitation in the iterators: they cannot use a data binding.
There's probably a workaround, but I'd have to think about it a bit.

In the meantime, I've put up issue #580
 to track.

Probably related to issue #384 
as well.

-tk

On Tue, Jun 30, 2020 at 6:16 AM Rahul Bedi  wrote:

> Tried. I get a similar error:
>
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
> weewx.cheetahgenerator: Generate failed with exception ' 'exceptions.TypeError'>'
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
> weewx.cheetahgenerator:  Ignoring template
> /etc/weewx/skins/Seasons/NOAA/NOAA--MM.txt.tmpl
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
> weewx.cheetahgenerator:  Reason: 'TimespanBinder' object is not callable
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
> weewx.cheetahgenerator:   Traceback (most recent call last):
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
> weewx.cheetahgenerator: File
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
> weewx.cheetahgenerator:   unicode_string =
> compiled_template.respond()
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
> weewx.cheetahgenerator: File
> "cheetah__etc_weewx_skins_Seasons_NOAA_NOAA__MM_txt_tmpl_1593522919_43_84946.py",
> line 479, in respond
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
> weewx.cheetahgenerator: File
> "cheetah__etc_weewx_skins_Seasons_NOAA_NOAA__MM_txt_tmpl_1593522919_43_84946.py",
> line 252, in __errorCatcher27
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
> weewx.cheetahgenerator: File "", line 1, in 
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
> weewx.cheetahgenerator:   TypeError: 'TimespanBinder' object is not
> callable
>
> On Tue, Jun 30, 2020 at 6:10 PM gjr80  wrote:
>
>> Hi,
>>
>> Try using:
>>
>> $day($data_binding='purpleair_binding').pm2_5_atm.maxtime.format($Time)
>> $day($data_binding='purpleair_binding').pm2_5_atm.max.nolabel($Count,
>> $NONE)
>>
>> Gary
>>
>>
>> On Tuesday, 30 June 2020 22:32:23 UTC+10, Rahul Bedi wrote:
>>>
>>> Hi,
>>>
>>> I have been trying to update the NOAA template to incorporate the air
>>> quality data in the monthly report, but when I added the two entries (in
>>> red)  in the file  NOAA--MM.txt.tmpl, I an error (attached at the end).
>>> Interestingly the same two entries, in the hilo.inc file in the Seasons
>>> skin work fine.
>>>
>>> Even more interestingly, the same two entries placed just before the
>>> "MONTHLY ..." line, work just fine.
>>>
>>> Any idea about what am I doing wrong ?
>>>
>>> Thanks.
>>>
>>> - Rahul
>>>
>>>
>>> #errorCatcher Echo
>>> #set $YM="%Y %m"
>>> #set $D=" %d"
>>> #set $M=" %b"
>>> #set $Time=" %H:%M"
>>> #set $NODAY=" N/A"
>>> #set $Temp="%6.1f"
>>> #set $Wind="%6.1f"
>>> #set $Dir="%6.0f"
>>> #set $Count="%6d"
>>> #set $NONE="   N/A"
>>> #if $unit.unit_type_dict.group_rain == "mm"
>>> #set $Rain="%6.1f"
>>> #else
>>> #set $Rain="%6.2f"
>>> #end if
>>>
>>>
>>>MONTHLY CLIMATOLOGICAL SUMMARY for $month_name
>>> $year_name
>>>
>>>
>>> NAME: $station.location
>>> ELEV: $station.altitudeLAT:
>>> $station.latitude[0]-$station.latitude[1] $station.latitude[2]LONG:
>>> $station.longitude[0]-$station.longitude[1] $station.longitude[2]
>>>
>>>
>>>TEMPERATURE ($unit.label.outTemp.strip()), RAIN
>>> ($unit.label.rain.strip()), WIND SPEED ($unit.label.windSpeed.strip())
>>>
>>>  HEAT   COOL AVG
>>>   MEAN   DEGDEG  WIND
>>>DOM
>>> DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED
>>>  HIGH   TIMEDIR
>>>
>>> ---
>>> #for $day in $month.days
>>> #if $day.barometer.count.raw
>>> $day.dateTime.format($D) $day.outTemp.avg.nolabel($Temp,$NONE)
>>> $day.outTemp.max.nolabel($Temp,$NONE) $day.outTemp.maxtime.format($Time)
>>> $day.outTemp.min.nolabel($Temp,$NONE) $day.outTemp.mintime.format($Time)
>>> $day.heatdeg.sum.nolabel($Temp,$NONE) $day.cooldeg.sum.nolabel($Temp,$NONE)
>>> $day.rain.sum.nolabel($Rain,$NONE) $day.wind.avg.nolabel($Wind,$NONE)
>>> $day.wind.max.nolabel($Wind,$NONE) $day.wind.maxtime.format($Time)
>>> $day.wind.vecdir.nolabel($Dir,$NONE) 
>>> $day('purpleair_binding').pm2_5_atm.maxtime.format($Time)
>>> $day('purpleair_binding').pm2_5_atm.max.nolabel($Count,$NONE)
>>> #else
>>> $day.dateTime.format($D)
>>> #end if
>>> #end for
>>>
>>> ---
>>> $month.outTemp.avg.nolabel($Temp,$NONE)
>>> $month.outTemp.max.nolabel($Temp,$NONE)
>>> $month.outTemp.maxtime.format($D) $month.outTemp.min.nolabel($Tem

Re: [weewx-user] Re: Issue with NOAA Template when trying to add additional fields

[gjr80]

I think I see what is going on. Normally you can pass a $data_binding to a 
$day tag to pull an aggregate from another database. However, in this case 
the $day tag is not a normal $day tag but rather it comes from iterating 
over all of the days in the month (for $day in $month.days) and you can't 
pass a $data_binding to that $day (I suspect you can pass it to $month but 
that is going to apply the same data binding to all $day tags). So I can't 
see how it can be done (short of putting you air quality data in the same 
database). Might be worth waiting till Tom looks at this, he may have some 
cunning magic he can perform.

Gary

On Tuesday, 30 June 2020 23:16:31 UTC+10, Rahul Bedi wrote:
>
> Tried. I get a similar error:
>
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator: Generate failed with exception ' 'exceptions.TypeError'>'
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator:  Ignoring template 
> /etc/weewx/skins/Seasons/NOAA/NOAA--MM.txt.tmpl
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator:  Reason: 'TimespanBinder' object is not callable
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator:   Traceback (most recent call last):
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator:   unicode_string = 
> compiled_template.respond()
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator: File 
> "cheetah__etc_weewx_skins_Seasons_NOAA_NOAA__MM_txt_tmpl_1593522919_43_84946.py",
>  
> line 479, in respond
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator: File 
> "cheetah__etc_weewx_skins_Seasons_NOAA_NOAA__MM_txt_tmpl_1593522919_43_84946.py",
>  
> line 252, in __errorCatcher27
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator: File "", line 1, in 
> Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator:   TypeError: 'TimespanBinder' object is not 
> callable
>
>

-- 
You received this message because you are subscribed to the Google 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/19af6989-e959-4141-9075-ca31b2a34ef7o%40googlegroups.com.

Re: [weewx-user] Re: Issue with NOAA Template when trying to add additional fields

[Rahul Bedi]

Tried. I get a similar error:

Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
weewx.cheetahgenerator: Generate failed with exception ''
Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
weewx.cheetahgenerator:  Ignoring template
/etc/weewx/skins/Seasons/NOAA/NOAA--MM.txt.tmpl
Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
weewx.cheetahgenerator:  Reason: 'TimespanBinder' object is not callable
Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
weewx.cheetahgenerator:   Traceback (most recent call last):
Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
weewx.cheetahgenerator: File
"/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate
Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
weewx.cheetahgenerator:   unicode_string =
compiled_template.respond()
Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
weewx.cheetahgenerator: File
"cheetah__etc_weewx_skins_Seasons_NOAA_NOAA__MM_txt_tmpl_1593522919_43_84946.py",
line 479, in respond
Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
weewx.cheetahgenerator: File
"cheetah__etc_weewx_skins_Seasons_NOAA_NOAA__MM_txt_tmpl_1593522919_43_84946.py",
line 252, in __errorCatcher27
Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
weewx.cheetahgenerator: File "", line 1, in 
Jun 30 18:45:19 PrideWeatherStation weewx[23078] ERROR
weewx.cheetahgenerator:   TypeError: 'TimespanBinder' object is not
callable

On Tue, Jun 30, 2020 at 6:10 PM gjr80  wrote:

> Hi,
>
> Try using:
>
> $day($data_binding='purpleair_binding').pm2_5_atm.maxtime.format($Time)
> $day($data_binding='purpleair_binding').pm2_5_atm.max.nolabel($Count,$NONE
> )
>
> Gary
>
>
> On Tuesday, 30 June 2020 22:32:23 UTC+10, Rahul Bedi wrote:
>>
>> Hi,
>>
>> I have been trying to update the NOAA template to incorporate the air
>> quality data in the monthly report, but when I added the two entries (in
>> red)  in the file  NOAA--MM.txt.tmpl, I an error (attached at the end).
>> Interestingly the same two entries, in the hilo.inc file in the Seasons
>> skin work fine.
>>
>> Even more interestingly, the same two entries placed just before the
>> "MONTHLY ..." line, work just fine.
>>
>> Any idea about what am I doing wrong ?
>>
>> Thanks.
>>
>> - Rahul
>>
>>
>> #errorCatcher Echo
>> #set $YM="%Y %m"
>> #set $D=" %d"
>> #set $M=" %b"
>> #set $Time=" %H:%M"
>> #set $NODAY=" N/A"
>> #set $Temp="%6.1f"
>> #set $Wind="%6.1f"
>> #set $Dir="%6.0f"
>> #set $Count="%6d"
>> #set $NONE="   N/A"
>> #if $unit.unit_type_dict.group_rain == "mm"
>> #set $Rain="%6.1f"
>> #else
>> #set $Rain="%6.2f"
>> #end if
>>
>>
>>MONTHLY CLIMATOLOGICAL SUMMARY for $month_name
>> $year_name
>>
>>
>> NAME: $station.location
>> ELEV: $station.altitudeLAT: $station.latitude[0]-$station.latitude[1]
>> $station.latitude[2]LONG: $station.longitude[0]-$station.longitude[1]
>> $station.longitude[2]
>>
>>
>>TEMPERATURE ($unit.label.outTemp.strip()), RAIN
>> ($unit.label.rain.strip()), WIND SPEED ($unit.label.windSpeed.strip())
>>
>>  HEAT   COOL AVG
>>   MEAN   DEGDEG  WIND
>>DOM
>> DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED
>>  HIGH   TIMEDIR
>>
>> ---
>> #for $day in $month.days
>> #if $day.barometer.count.raw
>> $day.dateTime.format($D) $day.outTemp.avg.nolabel($Temp,$NONE)
>> $day.outTemp.max.nolabel($Temp,$NONE) $day.outTemp.maxtime.format($Time)
>> $day.outTemp.min.nolabel($Temp,$NONE) $day.outTemp.mintime.format($Time)
>> $day.heatdeg.sum.nolabel($Temp,$NONE) $day.cooldeg.sum.nolabel($Temp,$NONE)
>> $day.rain.sum.nolabel($Rain,$NONE) $day.wind.avg.nolabel($Wind,$NONE)
>> $day.wind.max.nolabel($Wind,$NONE) $day.wind.maxtime.format($Time)
>> $day.wind.vecdir.nolabel($Dir,$NONE) 
>> $day('purpleair_binding').pm2_5_atm.maxtime.format($Time)
>> $day('purpleair_binding').pm2_5_atm.max.nolabel($Count,$NONE)
>> #else
>> $day.dateTime.format($D)
>> #end if
>> #end for
>>
>> ---
>> $month.outTemp.avg.nolabel($Temp,$NONE)
>> $month.outTemp.max.nolabel($Temp,$NONE)
>> $month.outTemp.maxtime.format($D) $month.outTemp.min.nolabel($Temp,$NONE)
>>   $month.outTemp.mintime.format($D) $month.heatdeg.sum.nolabel($Temp,$NONE)
>> $month.cooldeg.sum.nolabel($Temp,$NONE)
>> $month.rain.sum.nolabel($Rain,$NONE) $month.wind.avg.nolabel($Wind,$NONE)
>> $month.wind.max.nolabel($Wind,$NONE)$month.wind.maxtime.format($D)
>> $month.wind.vecdir.nolabel($Dir)
>>
>>
>>
>> Error log:
>>
>> Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR
>> weewx.cheetahgenerator: Generate failed with exception '> 'exceptions.TypeError'>'
>> Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR
>> weewx.chee

[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

[gjr80]

Fixed at commit e8a5015 

.

Gary

On Tuesday, 30 June 2020 22:55:52 UTC+10, gjr80 wrote:
>
> Ah, well spotted. This will be a python2/python3 issue. In python 2 / is 
> integer division if both operands are integers. But in python3 / is 
> floating point division irrespective of the operands. So the vantage driver 
> would have worked correctly for WeeWX v3.x as well as for v4.x under 
> python2. WeeWX v4.x under python3 will exhibit the incorrect behaviour. 
> Guess a change is in order.
>
> Gary
>
> On Tuesday, 30 June 2020 22:47:25 UTC+10, Jacques Terrettaz wrote:
>>
>> HI,
>>
>> I checked with my Davis station and I am observing exactly the same kind 
>> of differences. I think the problem is coming from the vantage weewx driver 
>> :
>>
>> Here are my data concerning sunrise :
>>
>>- the console displays 05:46 for sunrise. This is correct
>>- the raw loop data for sunrise, as received by Weewx , is 546 
>>- weewx vantage driver is converting the raw loop data into seconds 
>>using this function 
>>'sunrise' : lambda p, k: 3600 * (p[k] / 100) + 60 * (p[k] % 
>>100),
>> giving :  3600 * (546/100) + 60 * 46 =* 22416*.   This is wrong, it 
>>should be 3600 * (*500*/100) + 60 * 46 = *20760*
>>
>> Should the right formulas be :
>> 'sunrise' : lambda p, k: 3600 * (p[k] // 100) + 60 * (p[k] % 100),
>> 'sunset'  : lambda p, k: 3600 * (p[k] // 100) + 60 * (p[k] % 100),
>>
>>
>> ?
>>
>

-- 
You received this message because you are subscribed to the Google 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/8134d389-5c93-4249-938b-0842eef57374o%40googlegroups.com.

[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

[gjr80]

Ah, well spotted. This will be a python2/python3 issue. In python 2 / is 
integer division if both operands are integers. But in python3 / is 
floating point division irrespective of the operands. So the vantage driver 
would have worked correctly for WeeWX v3.x as well as for v4.x under 
python2. WeeWX v4.x under python3 will exhibit the incorrect behaviour. 
Guess a change is in order.

Gary

On Tuesday, 30 June 2020 22:47:25 UTC+10, Jacques Terrettaz wrote:
>
> HI,
>
> I checked with my Davis station and I am observing exactly the same kind 
> of differences. I think the problem is coming from the vantage weewx driver 
> :
>
> Here are my data concerning sunrise :
>
>- the console displays 05:46 for sunrise. This is correct
>- the raw loop data for sunrise, as received by Weewx , is 546 
>- weewx vantage driver is converting the raw loop data into seconds 
>using this function 
>'sunrise' : lambda p, k: 3600 * (p[k] / 100) + 60 * (p[k] % 100
>),
> giving :  3600 * (546/100) + 60 * 46 =* 22416*.   This is wrong, it 
>should be 3600 * (*500*/100) + 60 * 46 = *20760*
>
> Should the right formulas be :
> 'sunrise' : lambda p, k: 3600 * (p[k] // 100) + 60 * (p[k] % 100),
> 'sunset'  : lambda p, k: 3600 * (p[k] // 100) + 60 * (p[k] % 100),
>
>
> ?
>
>
> Le mardi 30 juin 2020 13:03:37 UTC+2, Constantine Samaklis a écrit :
>>
>> I did what you suggested (settings where fine to begin with) but still 
>> getting 20min discrepancies which are not explained by the loss of accuracy 
>> on the lon/lat.
>>
>> Wondering what to try next.
>>
>> On Tuesday, June 30, 2020 at 6:44:53 AM UTC-4, gjr80 wrote:
>>>
>>> No problems, it's just that sunrise/sunset can come from up to three 
>>> different sources and you need to to know which source is the problem in 
>>> order to troubleshoot.
>>>
>>> You are right that the sunrise/sunset in loop packets comes from the 
>>> console.  So in this case pyephem does not come into play nor does the 
>>> lat/long settings in weewx.conf. You need to check/set the lat/long 
>>> settings in your console, either via the console buttons or through use of 
>>> the wee_device  
>>> utility (note the if using wee_device you need to stop WeeWX first). From 
>>> memory the console (via buttons or wee_device) accepts decimal degrees with 
>>> a max resolution of 0.1 degree. Not sure a 0.1 degree resolution should 
>>> result in an inaccuracy of 20+ minutes though. 
>>>
>>> Gary
>>>
>>> On Tuesday, 30 June 2020 20:19:21 UTC+10, Constantine Samaklis wrote:

 My bad, I should have been more thorough with details. I was under the 
 impression that the sunrise/sunset times were provided directly by the 
 Davis console and not calculated.

 The values I am getting are coming from the LOOP when running weewxd

 LOOP:   2020-06-30 06:07:56 EDT (1593511676) altimeter: 
 29.887106231687923, barometer: 29.88, cloudbase: 1238.2237428350452, 
 consBatteryVoltage: 3.75, dateTime: 1593511676, dayET: 0.0, dayRain: 0.0, 
 dewpoint: 64.5434155315258, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 
 0, 
 extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
 extraAlarm8: 0, forecastIcon: 6, forecastRule: 45, heatindex: 69.6, 
 inDewpoint: 45.1326136300073, inHumidity: 53.0, insideAlarm: 0, inTemp: 
 62.5, leafWet4: 0.0, monthET: 0.0, monthRain: 1.89, outHumidity: 84.0, 
 outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 69.6, pressure: 
 29.788405301826174, rain: 0.0, rainAlarm: 0, rainRate: 0.0, 
 soilLeafAlarm1: 
 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 
 0.0, 
 sunrise: 1593510480.0, sunset: 1593564480.0, txBatteryStatus: 0, 
 usUnits: 1, windchill: 69.6, windDir: None, windGust: 0.0, windGustDir: 
 None, windSpeed: 0.0, windSpeed10: 1.0, yearET: 0.0, yearRain: 14.08

 I do have the following version of ephem: python3-ephem 
3.7.6.0-7+b1 

 Weewx is running on Python 3.7 

 # Latitude and longitude in decimal degrees
 latitude = 40.624573
 longitude = -74.012931

 On Monday, June 29, 2020 at 10:23:36 PM UTC-4, gjr80 wrote:
>
> Hi,
>
> I think we need to sort the apples from the oranges and bananas. 
> Exactly what are you showing us? Is that the sunrise/sunset times as 
> displayed on the console or as displayed in loop packet/archive record or 
> as returned by a tag in a report? What latitude/longitude do you have set 
> in your console and in weewx.conf? Do you have pyephem installed for 
> the version of python that WeeWX is being run under?
>
> Sorry for the questions, but it's a bit like the 'pressures'; there 
> are a number of moving parts to this and unless you know exactly what is 
> being looked at it is hard to give a meaningful answer.
>>

[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

[Jacques Terrettaz]

HI,

I checked with my Davis station and I am observing exactly the same kind of 
differences. I think the problem is coming from the vantage weewx driver :

Here are my data concerning sunrise :

   - the console displays 05:46 for sunrise. This is correct
   - the raw loop data for sunrise, as received by Weewx , is 546 
   - weewx vantage driver is converting the raw loop data into seconds 
   using this function 
   'sunrise' : lambda p, k: 3600 * (p[k] / 100) + 60 * (p[k] % 100),
giving :  3600 * (546/100) + 60 * 46 =* 22416*.   This is wrong, it 
   should be 3600 * (*500*/100) + 60 * 46 = *20760*

Should the right formulas be :
'sunrise' : lambda p, k: 3600 * (p[k] // 100) + 60 * (p[k] % 100),
'sunset'  : lambda p, k: 3600 * (p[k] // 100) + 60 * (p[k] % 100),


?


Le mardi 30 juin 2020 13:03:37 UTC+2, Constantine Samaklis a écrit :
>
> I did what you suggested (settings where fine to begin with) but still 
> getting 20min discrepancies which are not explained by the loss of accuracy 
> on the lon/lat.
>
> Wondering what to try next.
>
> On Tuesday, June 30, 2020 at 6:44:53 AM UTC-4, gjr80 wrote:
>>
>> No problems, it's just that sunrise/sunset can come from up to three 
>> different sources and you need to to know which source is the problem in 
>> order to troubleshoot.
>>
>> You are right that the sunrise/sunset in loop packets comes from the 
>> console.  So in this case pyephem does not come into play nor does the 
>> lat/long settings in weewx.conf. You need to check/set the lat/long 
>> settings in your console, either via the console buttons or through use of 
>> the wee_device  
>> utility (note the if using wee_device you need to stop WeeWX first). From 
>> memory the console (via buttons or wee_device) accepts decimal degrees with 
>> a max resolution of 0.1 degree. Not sure a 0.1 degree resolution should 
>> result in an inaccuracy of 20+ minutes though. 
>>
>> Gary
>>
>> On Tuesday, 30 June 2020 20:19:21 UTC+10, Constantine Samaklis wrote:
>>>
>>> My bad, I should have been more thorough with details. I was under the 
>>> impression that the sunrise/sunset times were provided directly by the 
>>> Davis console and not calculated.
>>>
>>> The values I am getting are coming from the LOOP when running weewxd
>>>
>>> LOOP:   2020-06-30 06:07:56 EDT (1593511676) altimeter: 
>>> 29.887106231687923, barometer: 29.88, cloudbase: 1238.2237428350452, 
>>> consBatteryVoltage: 3.75, dateTime: 1593511676, dayET: 0.0, dayRain: 0.0, 
>>> dewpoint: 64.5434155315258, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
>>> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
>>> extraAlarm8: 0, forecastIcon: 6, forecastRule: 45, heatindex: 69.6, 
>>> inDewpoint: 45.1326136300073, inHumidity: 53.0, insideAlarm: 0, inTemp: 
>>> 62.5, leafWet4: 0.0, monthET: 0.0, monthRain: 1.89, outHumidity: 84.0, 
>>> outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 69.6, pressure: 
>>> 29.788405301826174, rain: 0.0, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 
>>> 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 0.0, 
>>> sunrise: 1593510480.0, sunset: 1593564480.0, txBatteryStatus: 0, 
>>> usUnits: 1, windchill: 69.6, windDir: None, windGust: 0.0, windGustDir: 
>>> None, windSpeed: 0.0, windSpeed10: 1.0, yearET: 0.0, yearRain: 14.08
>>>
>>> I do have the following version of ephem: python3-ephem 
>>>3.7.6.0-7+b1 
>>>
>>> Weewx is running on Python 3.7 
>>>
>>> # Latitude and longitude in decimal degrees
>>> latitude = 40.624573
>>> longitude = -74.012931
>>>
>>> On Monday, June 29, 2020 at 10:23:36 PM UTC-4, gjr80 wrote:

 Hi,

 I think we need to sort the apples from the oranges and bananas. 
 Exactly what are you showing us? Is that the sunrise/sunset times as 
 displayed on the console or as displayed in loop packet/archive record or 
 as returned by a tag in a report? What latitude/longitude do you have set 
 in your console and in weewx.conf? Do you have pyephem installed for 
 the version of python that WeeWX is being run under?

 Sorry for the questions, but it's a bit like the 'pressures'; there are 
 a number of moving parts to this and unless you know exactly what is being 
 looked at it is hard to give a meaningful answer.

 Gary




 On Tuesday, 30 June 2020 11:16:33 UTC+10, Constantine Samaklis wrote:
>
> Wondering if anyone is having the same issue. In the last 3-4 days my 
> Vantage pro is showing the wrong sunrise and sunset times. I am in NY and 
> the console is set to EST daylight savings and the current time value is 
> displayed correctly. 
>
> For sunset I get: 1593478080, which is 8:48PM EST and for sunrise I 
> get: 1593424080 which is 5:48am EST.
>
> These timings are off by 20+ minutes. Not sure if this is something 
> that anyone el

[weewx-user] Re: Issue with NOAA Template when trying to add additional fields

[gjr80]

Hi,

Try using:

$day($data_binding='purpleair_binding').pm2_5_atm.maxtime.format($Time) $day
($data_binding='purpleair_binding').pm2_5_atm.max.nolabel($Count,$NONE)

Gary


On Tuesday, 30 June 2020 22:32:23 UTC+10, Rahul Bedi wrote:
>
> Hi,
>
> I have been trying to update the NOAA template to incorporate the air 
> quality data in the monthly report, but when I added the two entries (in 
> red)  in the file  NOAA--MM.txt.tmpl, I an error (attached at the end).
> Interestingly the same two entries, in the hilo.inc file in the Seasons 
> skin work fine.
>
> Even more interestingly, the same two entries placed just before the 
> "MONTHLY ..." line, work just fine.
>
> Any idea about what am I doing wrong ?
>
> Thanks.
>
> - Rahul
>
>
> #errorCatcher Echo
> #set $YM="%Y %m"
> #set $D=" %d"
> #set $M=" %b"
> #set $Time=" %H:%M"
> #set $NODAY=" N/A"
> #set $Temp="%6.1f"
> #set $Wind="%6.1f"
> #set $Dir="%6.0f"
> #set $Count="%6d"
> #set $NONE="   N/A"
> #if $unit.unit_type_dict.group_rain == "mm"
> #set $Rain="%6.1f"
> #else
> #set $Rain="%6.2f"
> #end if
>
>
>MONTHLY CLIMATOLOGICAL SUMMARY for $month_name 
> $year_name
>
>
> NAME: $station.location
> ELEV: $station.altitudeLAT: $station.latitude[0]-$station.latitude[1] 
> $station.latitude[2]LONG: $station.longitude[0]-$station.longitude[1] 
> $station.longitude[2]
>
>
>TEMPERATURE ($unit.label.outTemp.strip()), RAIN 
> ($unit.label.rain.strip()), WIND SPEED ($unit.label.windSpeed.strip())
>
>  HEAT   COOL AVG
>   MEAN   DEGDEG  WIND  
>  DOM
> DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED   HIGH  
>  TIMEDIR
>
> ---
> #for $day in $month.days
> #if $day.barometer.count.raw
> $day.dateTime.format($D) $day.outTemp.avg.nolabel($Temp,$NONE) 
> $day.outTemp.max.nolabel($Temp,$NONE) $day.outTemp.maxtime.format($Time) 
> $day.outTemp.min.nolabel($Temp,$NONE) $day.outTemp.mintime.format($Time) 
> $day.heatdeg.sum.nolabel($Temp,$NONE) $day.cooldeg.sum.nolabel($Temp,$NONE) 
> $day.rain.sum.nolabel($Rain,$NONE) $day.wind.avg.nolabel($Wind,$NONE) 
> $day.wind.max.nolabel($Wind,$NONE) $day.wind.maxtime.format($Time) 
> $day.wind.vecdir.nolabel($Dir,$NONE) 
> $day('purpleair_binding').pm2_5_atm.maxtime.format($Time) 
> $day('purpleair_binding').pm2_5_atm.max.nolabel($Count,$NONE)
> #else
> $day.dateTime.format($D)
> #end if
> #end for
>
> ---
> $month.outTemp.avg.nolabel($Temp,$NONE) 
> $month.outTemp.max.nolabel($Temp,$NONE)
> $month.outTemp.maxtime.format($D) $month.outTemp.min.nolabel($Temp,$NONE)  
>   $month.outTemp.mintime.format($D) $month.heatdeg.sum.nolabel($Temp,$NONE) 
> $month.cooldeg.sum.nolabel($Temp,$NONE) 
> $month.rain.sum.nolabel($Rain,$NONE) $month.wind.avg.nolabel($Wind,$NONE) 
> $month.wind.max.nolabel($Wind,$NONE)$month.wind.maxtime.format($D) 
> $month.wind.vecdir.nolabel($Dir)
>
>
>
> Error log:
>
> Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator: Generate failed with exception ' 'exceptions.TypeError'>'
> Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator:  Ignoring template 
> /etc/weewx/skins/Seasons/NOAA/NOAA--MM.txt.tmpl
> Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator:  Reason: 'TimespanBinder' object is not callable
> Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator:   Traceback (most recent call last):
> Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate
> Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator:   unicode_string = 
> compiled_template.respond()
> Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator: File 
> "cheetah__etc_weewx_skins_Seasons_NOAA_NOAA__MM_txt_tmpl_1593519917_36_48096.py",
>  
> line 525, in respond
> Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator: File 
> "cheetah__etc_weewx_skins_Seasons_NOAA_NOAA__MM_txt_tmpl_1593519917_36_48096.py",
>  
> line 336, in __errorCatcher39
> Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator: File "", line 1, in 
> Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
> weewx.cheetahgenerator:   TypeError: 'TimespanBinder' object is not 
> callable
> Jun 30 17:55:26 PrideWeatherStation weewx[23078] INFO weewx.reportengine: 
> Copied 0 files to /var/www/html/weewx
> Jun 30 17:55:27 PrideWeatherStation weewx[23078] INFO 
> weewx.cheetahgenerator: Generated 1 files for report wxobs in 0.57 seconds
> Jun 30 

[weewx-user] Issue with NOAA Template when trying to add additional fields

[Rahul Bedi]

Hi,

I have been trying to update the NOAA template to incorporate the air 
quality data in the monthly report, but when I added the two entries (in 
red)  in the file  NOAA--MM.txt.tmpl, I an error (attached at the end).
Interestingly the same two entries, in the hilo.inc file in the Seasons 
skin work fine.

Even more interestingly, the same two entries placed just before the 
"MONTHLY ..." line, work just fine.

Any idea about what am I doing wrong ?

Thanks.

- Rahul


#errorCatcher Echo
#set $YM="%Y %m"
#set $D=" %d"
#set $M=" %b"
#set $Time=" %H:%M"
#set $NODAY=" N/A"
#set $Temp="%6.1f"
#set $Wind="%6.1f"
#set $Dir="%6.0f"
#set $Count="%6d"
#set $NONE="   N/A"
#if $unit.unit_type_dict.group_rain == "mm"
#set $Rain="%6.1f"
#else
#set $Rain="%6.2f"
#end if


   MONTHLY CLIMATOLOGICAL SUMMARY for $month_name $year_name


NAME: $station.location
ELEV: $station.altitudeLAT: $station.latitude[0]-$station.latitude[1] 
$station.latitude[2]LONG: $station.longitude[0]-$station.longitude[1] 
$station.longitude[2]


   TEMPERATURE ($unit.label.outTemp.strip()), RAIN 
($unit.label.rain.strip()), WIND SPEED ($unit.label.windSpeed.strip())

 HEAT   COOL AVG
  MEAN   DEGDEG  WIND  
 DOM
DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED   HIGH  
 TIMEDIR
---
#for $day in $month.days
#if $day.barometer.count.raw
$day.dateTime.format($D) $day.outTemp.avg.nolabel($Temp,$NONE) 
$day.outTemp.max.nolabel($Temp,$NONE) $day.outTemp.maxtime.format($Time) 
$day.outTemp.min.nolabel($Temp,$NONE) $day.outTemp.mintime.format($Time) 
$day.heatdeg.sum.nolabel($Temp,$NONE) $day.cooldeg.sum.nolabel($Temp,$NONE) 
$day.rain.sum.nolabel($Rain,$NONE) $day.wind.avg.nolabel($Wind,$NONE) 
$day.wind.max.nolabel($Wind,$NONE) $day.wind.maxtime.format($Time) 
$day.wind.vecdir.nolabel($Dir,$NONE) 
$day('purpleair_binding').pm2_5_atm.maxtime.format($Time) 
$day('purpleair_binding').pm2_5_atm.max.nolabel($Count,$NONE)
#else
$day.dateTime.format($D)
#end if
#end for
---
$month.outTemp.avg.nolabel($Temp,$NONE) 
$month.outTemp.max.nolabel($Temp,$NONE)
$month.outTemp.maxtime.format($D) $month.outTemp.min.nolabel($Temp,$NONE)  
  $month.outTemp.mintime.format($D) $month.heatdeg.sum.nolabel($Temp,$NONE) 
$month.cooldeg.sum.nolabel($Temp,$NONE) 
$month.rain.sum.nolabel($Rain,$NONE) $month.wind.avg.nolabel($Wind,$NONE) 
$month.wind.max.nolabel($Wind,$NONE)$month.wind.maxtime.format($D) 
$month.wind.vecdir.nolabel($Dir)



Error log:

Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
weewx.cheetahgenerator: Generate failed with exception ''
Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
weewx.cheetahgenerator:  Ignoring template 
/etc/weewx/skins/Seasons/NOAA/NOAA--MM.txt.tmpl
Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
weewx.cheetahgenerator:  Reason: 'TimespanBinder' object is not callable
Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
weewx.cheetahgenerator:   Traceback (most recent call last):
Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
weewx.cheetahgenerator: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate
Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
weewx.cheetahgenerator:   unicode_string = 
compiled_template.respond()
Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
weewx.cheetahgenerator: File 
"cheetah__etc_weewx_skins_Seasons_NOAA_NOAA__MM_txt_tmpl_1593519917_36_48096.py",
 
line 525, in respond
Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
weewx.cheetahgenerator: File 
"cheetah__etc_weewx_skins_Seasons_NOAA_NOAA__MM_txt_tmpl_1593519917_36_48096.py",
 
line 336, in __errorCatcher39
Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
weewx.cheetahgenerator: File "", line 1, in 
Jun 30 17:55:19 PrideWeatherStation weewx[23078] ERROR 
weewx.cheetahgenerator:   TypeError: 'TimespanBinder' object is not 
callable
Jun 30 17:55:26 PrideWeatherStation weewx[23078] INFO weewx.reportengine: 
Copied 0 files to /var/www/html/weewx
Jun 30 17:55:27 PrideWeatherStation weewx[23078] INFO 
weewx.cheetahgenerator: Generated 1 files for report wxobs in 0.57 seconds
Jun 30 17:55:27 PrideWeatherStation weewx[23078] INFO weewx.reportengine: 
Copied 0 files to /var/www/html/weewx/wxobs
Jun 30 17:55:27 PrideWeatherStation weewx[23078] INFO user.stackedwindrose: 
Generated 2 images for StackedWindRose in 0.41 seconds



-- 
You received this message because you are subscribed to the Google 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 d

[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

[gjr80]

Not much else to check, timezone and daylight saving could affect it but 
you would expect to see variations of an hour (or perhaps 30 minutes if you 
are in a weird timezone).

Out of interest I just checked the loop sunrise and sunset values for my 
console. Sunrise according to the console is 7:00:48am and dateandtime.com 
and pyephem both say it is 6:38am. Sunset is a little better, according to 
the console it is 5:08:00pm and dateandtime.com and pyephem both agree it 
is 5:05pm. So it sounds like it could be a case of the console not being 
that accurate. Must admit I have never ever looked at, much less used, the 
console figures, I always use the pyephem figures and have found them to 
always be within a few seconds.

Gary

On Tuesday, 30 June 2020 21:03:37 UTC+10, Constantine Samaklis wrote:
>
> I did what you suggested (settings where fine to begin with) but still 
> getting 20min discrepancies which are not explained by the loss of accuracy 
> on the lon/lat.
>
> Wondering what to try next.
>
> On Tuesday, June 30, 2020 at 6:44:53 AM UTC-4, gjr80 wrote:
>>
>> No problems, it's just that sunrise/sunset can come from up to three 
>> different sources and you need to to know which source is the problem in 
>> order to troubleshoot.
>>
>> You are right that the sunrise/sunset in loop packets comes from the 
>> console.  So in this case pyephem does not come into play nor does the 
>> lat/long settings in weewx.conf. You need to check/set the lat/long 
>> settings in your console, either via the console buttons or through use of 
>> the wee_device  
>> utility (note the if using wee_device you need to stop WeeWX first). From 
>> memory the console (via buttons or wee_device) accepts decimal degrees with 
>> a max resolution of 0.1 degree. Not sure a 0.1 degree resolution should 
>> result in an inaccuracy of 20+ minutes though. 
>>
>> Gary
>>
>> On Tuesday, 30 June 2020 20:19:21 UTC+10, Constantine Samaklis wrote:
>>>
>>> My bad, I should have been more thorough with details. I was under the 
>>> impression that the sunrise/sunset times were provided directly by the 
>>> Davis console and not calculated.
>>>
>>> The values I am getting are coming from the LOOP when running weewxd
>>>
>>> LOOP:   2020-06-30 06:07:56 EDT (1593511676) altimeter: 
>>> 29.887106231687923, barometer: 29.88, cloudbase: 1238.2237428350452, 
>>> consBatteryVoltage: 3.75, dateTime: 1593511676, dayET: 0.0, dayRain: 0.0, 
>>> dewpoint: 64.5434155315258, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
>>> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
>>> extraAlarm8: 0, forecastIcon: 6, forecastRule: 45, heatindex: 69.6, 
>>> inDewpoint: 45.1326136300073, inHumidity: 53.0, insideAlarm: 0, inTemp: 
>>> 62.5, leafWet4: 0.0, monthET: 0.0, monthRain: 1.89, outHumidity: 84.0, 
>>> outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 69.6, pressure: 
>>> 29.788405301826174, rain: 0.0, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 
>>> 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 0.0, 
>>> sunrise: 1593510480.0, sunset: 1593564480.0, txBatteryStatus: 0, 
>>> usUnits: 1, windchill: 69.6, windDir: None, windGust: 0.0, windGustDir: 
>>> None, windSpeed: 0.0, windSpeed10: 1.0, yearET: 0.0, yearRain: 14.08
>>>
>>> I do have the following version of ephem: python3-ephem 
>>>3.7.6.0-7+b1 
>>>
>>> Weewx is running on Python 3.7 
>>>
>>> # Latitude and longitude in decimal degrees
>>> latitude = 40.624573
>>> longitude = -74.012931
>>>
>>> On Monday, June 29, 2020 at 10:23:36 PM UTC-4, gjr80 wrote:

 Hi,

 I think we need to sort the apples from the oranges and bananas. 
 Exactly what are you showing us? Is that the sunrise/sunset times as 
 displayed on the console or as displayed in loop packet/archive record or 
 as returned by a tag in a report? What latitude/longitude do you have set 
 in your console and in weewx.conf? Do you have pyephem installed for 
 the version of python that WeeWX is being run under?

 Sorry for the questions, but it's a bit like the 'pressures'; there are 
 a number of moving parts to this and unless you know exactly what is being 
 looked at it is hard to give a meaningful answer.

 Gary




 On Tuesday, 30 June 2020 11:16:33 UTC+10, Constantine Samaklis wrote:
>
> Wondering if anyone is having the same issue. In the last 3-4 days my 
> Vantage pro is showing the wrong sunrise and sunset times. I am in NY and 
> the console is set to EST daylight savings and the current time value is 
> displayed correctly. 
>
> For sunset I get: 1593478080, which is 8:48PM EST and for sunrise I 
> get: 1593424080 which is 5:48am EST.
>
> These timings are off by 20+ minutes. Not sure if this is something 
> that anyone else is experiencing. 
>


-- 
You received this message becau

[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

[Constantine Samaklis]

I did what you suggested (settings where fine to begin with) but still 
getting 20min discrepancies which are not explained by the loss of accuracy 
on the lon/lat.

Wondering what to try next.

On Tuesday, June 30, 2020 at 6:44:53 AM UTC-4, gjr80 wrote:
>
> No problems, it's just that sunrise/sunset can come from up to three 
> different sources and you need to to know which source is the problem in 
> order to troubleshoot.
>
> You are right that the sunrise/sunset in loop packets comes from the 
> console.  So in this case pyephem does not come into play nor does the 
> lat/long settings in weewx.conf. You need to check/set the lat/long 
> settings in your console, either via the console buttons or through use of 
> the wee_device  utility 
> (note the if using wee_device you need to stop WeeWX first). From memory 
> the console (via buttons or wee_device) accepts decimal degrees with a max 
> resolution of 0.1 degree. Not sure a 0.1 degree resolution should result in 
> an inaccuracy of 20+ minutes though. 
>
> Gary
>
> On Tuesday, 30 June 2020 20:19:21 UTC+10, Constantine Samaklis wrote:
>>
>> My bad, I should have been more thorough with details. I was under the 
>> impression that the sunrise/sunset times were provided directly by the 
>> Davis console and not calculated.
>>
>> The values I am getting are coming from the LOOP when running weewxd
>>
>> LOOP:   2020-06-30 06:07:56 EDT (1593511676) altimeter: 
>> 29.887106231687923, barometer: 29.88, cloudbase: 1238.2237428350452, 
>> consBatteryVoltage: 3.75, dateTime: 1593511676, dayET: 0.0, dayRain: 0.0, 
>> dewpoint: 64.5434155315258, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
>> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
>> extraAlarm8: 0, forecastIcon: 6, forecastRule: 45, heatindex: 69.6, 
>> inDewpoint: 45.1326136300073, inHumidity: 53.0, insideAlarm: 0, inTemp: 
>> 62.5, leafWet4: 0.0, monthET: 0.0, monthRain: 1.89, outHumidity: 84.0, 
>> outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 69.6, pressure: 
>> 29.788405301826174, rain: 0.0, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 
>> 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 0.0, 
>> sunrise: 1593510480.0, sunset: 1593564480.0, txBatteryStatus: 0, 
>> usUnits: 1, windchill: 69.6, windDir: None, windGust: 0.0, windGustDir: 
>> None, windSpeed: 0.0, windSpeed10: 1.0, yearET: 0.0, yearRain: 14.08
>>
>> I do have the following version of ephem: python3-ephem   
>>  3.7.6.0-7+b1 
>>
>> Weewx is running on Python 3.7 
>>
>> # Latitude and longitude in decimal degrees
>> latitude = 40.624573
>> longitude = -74.012931
>>
>> On Monday, June 29, 2020 at 10:23:36 PM UTC-4, gjr80 wrote:
>>>
>>> Hi,
>>>
>>> I think we need to sort the apples from the oranges and bananas. Exactly 
>>> what are you showing us? Is that the sunrise/sunset times as displayed on 
>>> the console or as displayed in loop packet/archive record or as returned by 
>>> a tag in a report? What latitude/longitude do you have set in your console 
>>> and in weewx.conf? Do you have pyephem installed for the version of 
>>> python that WeeWX is being run under?
>>>
>>> Sorry for the questions, but it's a bit like the 'pressures'; there are 
>>> a number of moving parts to this and unless you know exactly what is being 
>>> looked at it is hard to give a meaningful answer.
>>>
>>> Gary
>>>
>>>
>>>
>>>
>>> On Tuesday, 30 June 2020 11:16:33 UTC+10, Constantine Samaklis wrote:

 Wondering if anyone is having the same issue. In the last 3-4 days my 
 Vantage pro is showing the wrong sunrise and sunset times. I am in NY and 
 the console is set to EST daylight savings and the current time value is 
 displayed correctly. 

 For sunset I get: 1593478080, which is 8:48PM EST and for sunrise I 
 get: 1593424080 which is 5:48am EST.

 These timings are off by 20+ minutes. Not sure if this is something 
 that anyone else is experiencing. 

>>>

-- 
You received this message because you are subscribed to the Google 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/9deecd62-c5bc-4095-8ccf-6f0bcbf7f0e2o%40googlegroups.com.

[weewx-user] Re: One chart with two different time periods

[gjr80]

Pull requests are always welcome :)

Gary

On Tuesday, 30 June 2020 20:38:01 UTC+10, Janne Prokkola wrote:
>
> Hi,
>
> that would be a nice feature to add.
>
> Janne
>
> torstai 18. kesäkuuta 2020 2.56.32 UTC+3 gjr80 kirjoitti:
>>
>> Hi,
>>
>> The WeeWX plot engine does not support this feature. I can't speak for 
>> other 3rd party extensions/add ons.
>>
>> Gary
>>
>> On Thursday, 18 June 2020 01:53:16 UTC+10, Michael wrote:
>>>
>>> Hello,
>>> I am looking for a way to create a chart from two different time 
>>> periods. For example, temperatures today compared to yesterday. Or current 
>>> week with previous week...
>>> Is this possible with weewx in Skin Seasons, or with Belchertown. Or 
>>> outside weewx with grafana?
>>> Any ideas or suggestions?
>>>
>>> Michael
>>>
>>

-- 
You received this message because you are subscribed to the Google 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/f1b45f11-9387-4b09-923b-bd715deaec25o%40googlegroups.com.

[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

[gjr80]

No problems, it's just that sunrise/sunset can come from up to three 
different sources and you need to to know which source is the problem in 
order to troubleshoot.

You are right that the sunrise/sunset in loop packets comes from the 
console.  So in this case pyephem does not come into play nor does the 
lat/long settings in weewx.conf. You need to check/set the lat/long 
settings in your console, either via the console buttons or through use of 
the wee_device  utility 
(note the if using wee_device you need to stop WeeWX first). From memory 
the console (via buttons or wee_device) accepts decimal degrees with a max 
resolution of 0.1 degree. Not sure a 0.1 degree resolution should result in 
an inaccuracy of 20+ minutes though. 

Gary

On Tuesday, 30 June 2020 20:19:21 UTC+10, Constantine Samaklis wrote:
>
> My bad, I should have been more thorough with details. I was under the 
> impression that the sunrise/sunset times were provided directly by the 
> Davis console and not calculated.
>
> The values I am getting are coming from the LOOP when running weewxd
>
> LOOP:   2020-06-30 06:07:56 EDT (1593511676) altimeter: 
> 29.887106231687923, barometer: 29.88, cloudbase: 1238.2237428350452, 
> consBatteryVoltage: 3.75, dateTime: 1593511676, dayET: 0.0, dayRain: 0.0, 
> dewpoint: 64.5434155315258, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
> extraAlarm8: 0, forecastIcon: 6, forecastRule: 45, heatindex: 69.6, 
> inDewpoint: 45.1326136300073, inHumidity: 53.0, insideAlarm: 0, inTemp: 
> 62.5, leafWet4: 0.0, monthET: 0.0, monthRain: 1.89, outHumidity: 84.0, 
> outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 69.6, pressure: 
> 29.788405301826174, rain: 0.0, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 
> 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 0.0, 
> sunrise: 1593510480.0, sunset: 1593564480.0, txBatteryStatus: 0, usUnits: 
> 1, windchill: 69.6, windDir: None, windGust: 0.0, windGustDir: None, 
> windSpeed: 0.0, windSpeed10: 1.0, yearET: 0.0, yearRain: 14.08
>
> I do have the following version of ephem: python3-ephem   
>  3.7.6.0-7+b1 
>
> Weewx is running on Python 3.7 
>
> # Latitude and longitude in decimal degrees
> latitude = 40.624573
> longitude = -74.012931
>
> On Monday, June 29, 2020 at 10:23:36 PM UTC-4, gjr80 wrote:
>>
>> Hi,
>>
>> I think we need to sort the apples from the oranges and bananas. Exactly 
>> what are you showing us? Is that the sunrise/sunset times as displayed on 
>> the console or as displayed in loop packet/archive record or as returned by 
>> a tag in a report? What latitude/longitude do you have set in your console 
>> and in weewx.conf? Do you have pyephem installed for the version of 
>> python that WeeWX is being run under?
>>
>> Sorry for the questions, but it's a bit like the 'pressures'; there are a 
>> number of moving parts to this and unless you know exactly what is being 
>> looked at it is hard to give a meaningful answer.
>>
>> Gary
>>
>>
>>
>>
>> On Tuesday, 30 June 2020 11:16:33 UTC+10, Constantine Samaklis wrote:
>>>
>>> Wondering if anyone is having the same issue. In the last 3-4 days my 
>>> Vantage pro is showing the wrong sunrise and sunset times. I am in NY and 
>>> the console is set to EST daylight savings and the current time value is 
>>> displayed correctly. 
>>>
>>> For sunset I get: 1593478080, which is 8:48PM EST and for sunrise I get: 
>>> 1593424080 which is 5:48am EST.
>>>
>>> These timings are off by 20+ minutes. Not sure if this is something that 
>>> anyone else is experiencing. 
>>>
>>

-- 
You received this message because you are subscribed to the Google 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/e1524fe6-0cb2-4f96-8886-c49c0cfb69f6o%40googlegroups.com.

[weewx-user] Re: One chart with two different time periods

[Janne Prokkola]

Hi,

that would be a nice feature to add.

Janne

torstai 18. kesäkuuta 2020 2.56.32 UTC+3 gjr80 kirjoitti:
>
> Hi,
>
> The WeeWX plot engine does not support this feature. I can't speak for 
> other 3rd party extensions/add ons.
>
> Gary
>
> On Thursday, 18 June 2020 01:53:16 UTC+10, Michael wrote:
>>
>> Hello,
>> I am looking for a way to create a chart from two different time periods. 
>> For example, temperatures today compared to yesterday. Or current week with 
>> previous week...
>> Is this possible with weewx in Skin Seasons, or with Belchertown. Or 
>> outside weewx with grafana?
>> Any ideas or suggestions?
>>
>> Michael
>>
>

-- 
You received this message because you are subscribed to the Google 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/a491dffb-cb57-4981-8acf-3331d9758c78o%40googlegroups.com.

[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

[Constantine Samaklis]

My bad, I should have been more thorough with details. I was under the 
impression that the sunrise/sunset times were provided directly by the 
Davis console and not calculated.

The values I am getting are coming from the LOOP when running weewxd

LOOP:   2020-06-30 06:07:56 EDT (1593511676) altimeter: 29.887106231687923, 
barometer: 29.88, cloudbase: 1238.2237428350452, consBatteryVoltage: 3.75, 
dateTime: 1593511676, dayET: 0.0, dayRain: 0.0, dewpoint: 64.5434155315258, 
extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: 0, 
extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, 
forecastIcon: 6, forecastRule: 45, heatindex: 69.6, inDewpoint: 
45.1326136300073, inHumidity: 53.0, insideAlarm: 0, inTemp: 62.5, leafWet4: 
0.0, monthET: 0.0, monthRain: 1.89, outHumidity: 84.0, outsideAlarm1: 0, 
outsideAlarm2: 0, outTemp: 69.6, pressure: 29.788405301826174, rain: 0.0, 
rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, 
soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1593510480.0, 
sunset: 1593564480.0, txBatteryStatus: 0, usUnits: 1, windchill: 69.6, 
windDir: None, windGust: 0.0, windGustDir: None, windSpeed: 0.0, 
windSpeed10: 1.0, yearET: 0.0, yearRain: 14.08

I do have the following version of ephem: python3-ephem 
   3.7.6.0-7+b1 

Weewx is running on Python 3.7 

# Latitude and longitude in decimal degrees
latitude = 40.624573
longitude = -74.012931

On Monday, June 29, 2020 at 10:23:36 PM UTC-4, gjr80 wrote:
>
> Hi,
>
> I think we need to sort the apples from the oranges and bananas. Exactly 
> what are you showing us? Is that the sunrise/sunset times as displayed on 
> the console or as displayed in loop packet/archive record or as returned by 
> a tag in a report? What latitude/longitude do you have set in your console 
> and in weewx.conf? Do you have pyephem installed for the version of 
> python that WeeWX is being run under?
>
> Sorry for the questions, but it's a bit like the 'pressures'; there are a 
> number of moving parts to this and unless you know exactly what is being 
> looked at it is hard to give a meaningful answer.
>
> Gary
>
>
>
>
> On Tuesday, 30 June 2020 11:16:33 UTC+10, Constantine Samaklis wrote:
>>
>> Wondering if anyone is having the same issue. In the last 3-4 days my 
>> Vantage pro is showing the wrong sunrise and sunset times. I am in NY and 
>> the console is set to EST daylight savings and the current time value is 
>> displayed correctly. 
>>
>> For sunset I get: 1593478080, which is 8:48PM EST and for sunrise I get: 
>> 1593424080 which is 5:48am EST.
>>
>> These timings are off by 20+ minutes. Not sure if this is something that 
>> anyone else is experiencing. 
>>
>

-- 
You received this message because you are subscribed to the Google 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/20e36ef4-2d97-4b49-9064-44820203d815o%40googlegroups.com.

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

>
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   Traceback (most recent call last):
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 521, in process_queue
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   self.compose_and_write_packet(pkt)
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 541, in 
> compose_and_write_packet
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   self.write_packet(selective_pkt)
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 555, in write_packet
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   self.rsync_data(pkt['dateTime'])
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   rsync_upload.run()
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   if self.port is not None and len(self.port.strip()) > 0:
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   AttributeError: 'int' object has no attribute 'strip'
>
>
> Am Dienstag, 30. Juni 2020 09:47:44 UTC+2 schrieb Geni 0815:
>
> @John: I have the following entry in the syslog, what is not suitable?
>
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>> barometer_rate_secs: 10800
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>> wind_rose_secs : 86400
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>> wind_rose_points   : 16
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   Traceback (most recent call last):
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 521, in process_queue
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   self.compose_and_write_packet(pkt)
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 541, in 
>> compose_and_write_packet
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   self.write_packet(selective_pkt)
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 555, in write_packet
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   self.rsync_data(pkt['dateTime'])
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   rsync_upload.run()
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   if self.port is not None and len(self.port.strip()) > 0:
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   AttributeError: 'int' object has no attribute 'strip'
>>
>> [image: belch09.jpg]
>  
>
> Am Samstag, 27. Juni 2020 21:18:06 UTC+2 schrieb John Kline:
>>
>> I just now updated this extension to 1.1.  I would try it before 
>> resorting to a clean install.
>>
>> On Jun 27, 2020, at 12:16 PM, Michael Meyer  wrote:
>>
>> 
>> Hello John, I did grep and get some results. Next time I used grep again 
>> no results. I uninstalled weewx because I did the first installation with 
>> Debian. I did installation weewx with setup py. Again no loop_data.txt 
>> created. I will do a fresh Buster light image next. After that I will do 
>> also a complete new weewx installation. I will let you know if 
>> successfully. Thx for your help!
>> Michael
>>
>> John Kline  schrieb am Fr., 26. Juni 2020, 20:54:
>>
>>> Well, I see loopdata in the log snippet you just sent.
>>>
>>> Would you try the grep again?
>>> grep loopdata /var/log/syslog
>>>
>>> And look for the loopdata file again?
>>>
>>> On Jun 26, 2020, at 11:48 AM, Michael Meyer  wrote:
>>>
>>> 
>>> Yes I stopped, start and restart. 
>>> I will try to find out how to send files.
>>> 
>>>
>>>
>>> jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 20:28:49 UTC+2:
>>>
 Not sure how to post files; but since you are running WeeWX 4 and 
 Python 3.  Did you restart WeeWX after you installed loop

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

>
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
>   Traceback (most recent call last):
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 507, in process_queue
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
>   self.convert_units(pkt, obstype)
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 735, in convert_units
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
>   self.convert_hi_lo_sum_units(pkt, obstype, unit_type, unit_group)
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 677, in 
> convert_hi_lo_sum_units
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
>   pkt['FMT_SUM_%s' % obstype] = self.cfg.formatter.toString((sum, 
> unit_type, unit_group))
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
> File "/usr/share/weewx/weewx/units.py", line 758, in toString
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
>   time.localtime(val_t[0]))
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
>   OverflowError: timestamp out of range for platform time_t
>
>
> Am Dienstag, 30. Juni 2020 09:47:44 UTC+2 schrieb Geni 0815:
>
> @John: I have the following entry in the syslog, what is not suitable?
>
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>> barometer_rate_secs: 10800
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>> wind_rose_secs : 86400
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>> wind_rose_points   : 16
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   Traceback (most recent call last):
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 521, in process_queue
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   self.compose_and_write_packet(pkt)
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 541, in 
>> compose_and_write_packet
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   self.write_packet(selective_pkt)
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 555, in write_packet
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   self.rsync_data(pkt['dateTime'])
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   rsync_upload.run()
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   if self.port is not None and len(self.port.strip()) > 0:
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   AttributeError: 'int' object has no attribute 'strip'
>>
>> [image: belch09.jpg]
>  
>
> Am Samstag, 27. Juni 2020 21:18:06 UTC+2 schrieb John Kline:
>>
>> I just now updated this extension to 1.1.  I would try it before 
>> resorting to a clean install.
>>
>> On Jun 27, 2020, at 12:16 PM, Michael Meyer  wrote:
>>
>> 
>> Hello John, I did grep and get some results. Next time I used grep again 
>> no results. I uninstalled weewx because I did the first installation with 
>> Debian. I did installation weewx with setup py. Again no loop_data.txt 
>> created. I will do a fresh Buster light image next. After that I will do 
>> also a complete new weewx installation. I will let you know if 
>> successfully. Thx for your help!
>> Michael
>>
>> John Kline  schrieb am Fr., 26. Juni 2020, 20:54:
>>
>>> Well, I see loopdata in the log snippet you just sent.
>>>
>>> Would you try the grep again?
>>> grep loopdata /var/log/syslog
>>>
>>> And look for the loopdata file again?
>>>
>>> On Jun 26, 2020, at 11:48 AM, Michael Meyer  wrote:
>>>
>>> 
>>> Yes I stopped, start and restart. 
>>> I will try to find out how to send files.
>>> 
>>>
>>>
>>> jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 20:28:49 UTC+2:
>>>
 Not sure how to post files; but since you are running WeeWX 4 and 
 Python 3.  Did you restart WeeWX after you installed loopdata?

 It’s to imagine why you don’t see any occurrence of loopdata in the 
 log?  Do you see other weewx messages in the log?

 On Jun 26, 2020, at 10:40 AM, Michael Meyer

[weewx-user] Re: Interceptor setup

[Zsolt Máté]

There was a typo in the wiki, edited it.
Instead of domain_name_servers there was domain_name_server.



On Tuesday, June 30, 2020 at 7:39:11 PM UTC+12, Zsolt Máté wrote:
>
> Did anything change with the latest raspberry pi images? I'm trying to do 
> a clean install, downloaded the last image (based on Debian Buster), 
> installed and configured hostapd as per wiki.
> Now the DNS is not resolving any address. I can ping external IP addresses 
> while I'm connected to the pi via LAN or WLAN.
>

-- 
You received this message because you are subscribed to the Google 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/f27fbef2-f041-4617-9654-4c80259fa7d9o%40googlegroups.com.

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

@John: I have the following entry in the syslog, what is not suitable?

Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
> barometer_rate_secs: 10800
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
> wind_rose_secs : 86400
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
> wind_rose_points   : 16
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   Traceback (most recent call last):
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 521, in process_queue
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   self.compose_and_write_packet(pkt)
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 541, in 
> compose_and_write_packet
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   self.write_packet(selective_pkt)
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 555, in write_packet
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   self.rsync_data(pkt['dateTime'])
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   rsync_upload.run()
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
> File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   if self.port is not None and len(self.port.strip()) > 0:
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   AttributeError: 'int' object has no attribute 'strip'
>
> [image: belch09.jpg]
 

Am Samstag, 27. Juni 2020 21:18:06 UTC+2 schrieb John Kline:
>
> I just now updated this extension to 1.1.  I would try it before resorting 
> to a clean install.
>
> On Jun 27, 2020, at 12:16 PM, Michael Meyer  > wrote:
>
> 
> Hello John, I did grep and get some results. Next time I used grep again 
> no results. I uninstalled weewx because I did the first installation with 
> Debian. I did installation weewx with setup py. Again no loop_data.txt 
> created. I will do a fresh Buster light image next. After that I will do 
> also a complete new weewx installation. I will let you know if 
> successfully. Thx for your help!
> Michael
>
> John Kline > schrieb am Fr., 26. Juni 
> 2020, 20:54:
>
>> Well, I see loopdata in the log snippet you just sent.
>>
>> Would you try the grep again?
>> grep loopdata /var/log/syslog
>>
>> And look for the loopdata file again?
>>
>> On Jun 26, 2020, at 11:48 AM, Michael Meyer > > wrote:
>>
>> 
>> Yes I stopped, start and restart. 
>> I will try to find out how to send files.
>> 
>>
>>
>> jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 20:28:49 UTC+2:
>>
>>> Not sure how to post files; but since you are running WeeWX 4 and Python 
>>> 3.  Did you restart WeeWX after you installed loopdata?
>>>
>>> It’s to imagine why you don’t see any occurrence of loopdata in the 
>>> log?  Do you see other weewx messages in the log?
>>>
>>> On Jun 26, 2020, at 10:40 AM, Michael Meyer  wrote:
>>>
>>> 
>>>
>>> Weewx 4.1.1 is running I have Python 3.7 on my rpi.
>>> Any idea why I can't post the created myfile here? I just can post 
>>> pictures but no files! I can create an attachment but couldn't send?
>>>
>>> jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 18:19:36 UTC+2:
>>>
 It appears that loopdata isn’t running.

 Let’s start with the obvious.  As stated in the README:

 This extension requires Python 3 and WeeWX 4.

 Are you running WeeWX 4.x?  Are you running Python 3?

 If are on WeeWX 4.x and Python 3, use the following guide to post the 
 log and I’ll have a look.

 https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user

 Cheers,
 John

 On Jun 26, 2020, at 8:27 AM, Michael Meyer  wrote:

 

 Hi John,
 thx for your help! grep loopdata /var/log/syslog doesn't deliver 
 anything. With "where is" I get zero result in var/log/syslog. 

 


 
 
 Cheers,
 Michael

 -- 
 You received this message because you are subscribed 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/d261b8ee-957e-4158-9b80-dcbe21fcc3f5n%40googlegroups.com
  
 

[weewx-user] Re: Interceptor setup

[Zsolt Máté]

Did anything change with the latest raspberry pi images? I'm trying to do a 
clean install, downloaded the last image (based on Debian Buster), 
installed and configured hostapd as per wiki.
Now the DNS is not resolving any address. I can ping external IP addresses 
while I'm connected to the pi via LAN or WLAN.

-- 
You received this message because you are subscribed to the Google 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/6908abaa-d068-42da-a291-420581309a05o%40googlegroups.com.