[weewx-user] Re: FTP Upload

[michael.k...@gmx.at]

Ich kenne keine Details, wie die WH2600 zu installieren ist. Hier eine 
Diskussion zum Thema:  
https://groups.google.com/g/weewx-user/c/wBDA8fdJD3w/m/6bhErnnmAwAJ 
Der Autor hört sich deutschsprachig an, vielleicht erreichst du ihn ja.

Sorry, I don't know any details about the WH2600, there is a thread 
concerning this type of stations: 
https://groups.google.com/g/weewx-user/c/wBDA8fdJD3w/m/6bhErnnmAwAJ 

renato...@gmail.com schrieb am Donnerstag, 4. Februar 2021 um 19:03:39 
UTC+1:

> Hallo Michael.
>
> Danke schon mal für die Hilfe. Hat geklappt. Werden dann nächstens 
> versuchen meine Wetterstation WH2600 einzubinden. 
> Könnte wahrscheinlich auch nicht so einfach sein, da diese an einem Router 
> hängt und kein USB Anschluss hat.
> Hast du eventuell einen Tipp welchen Treiber ich da installieren sollte?
> Danke.
>
> Hi Michael. Thank you in advance for the help. It worked. Will try to 
> integrate my weather station WH2600 next. Could probably not be that easy 
> either, since it is connected to a router and has no USB port. Do you 
> have a tip which driver I should install there? Thank you. 
> michael.k...@gmx.at schrieb am Donnerstag, 4. Februar 2021 um 17:47:12 
> UTC+1:
>
>> Ich gehe davon aus, das bei dir dann  
>> path = /html# The destination directory, e.g., /weather  
>> funktionieren müsste
>>
>> Please try 
>> path = /html# The destination directory, e.g., /weather
>>
>>
>> renato...@gmail.com schrieb am Donnerstag, 4. Februar 2021 um 16:43:07 
>> UTC+1:
>>
>>> Hallo Michael
>>>
>>> Ich habe gerade versucht mit dem FTP Programm mir die Schreibrechte zu 
>>> geben, hat aber leider nicht funktioniert. Schreibrechte kann ich erst im 
>>> Unterodner \html geben. Sollte ich somit die config Position  " path = 
>>> / " auf "path = /html" umstellen? 
>>>
>>> michael.k...@gmx.at schrieb am Donnerstag, 4. Februar 2021 um 16:18:44 
>>> UTC+1:
>>>
 Hallo Renato,

 der FTP-Benutzer hat auf dem Ordner, wo die Dateien hochgeladen werden 
 sollen, keine Schreibrechte "Permission Denied" => "Zugriff verweigert". 
 Wer hat dir den Ordner erstellt bzw. den Benutzer erstellt? Derjenige 
 müsste dir für den Benutzer und den Ordner Schreibrechte geben.

 Most likely the FTP-user has noch write permission to the upload Folder.

 renato...@gmail.com schrieb am Donnerstag, 4. Februar 2021 um 16:13:09 
 UTC+1:

> Hallo zusammen.
> Ich bin ein Anfänger mit Linux.
> Ich habe erfolgreich Weewx auf meine RasbeeryPi installiert. Es 
> funtioniert auch mit dem Simulator und dem Apache Server. Webseite wird 
> angezeit.
> Leider gelingt es mir nicht FTP zum laufen zu bringen. Ich habe den 
> Auschnitt der Config sowie das Log angehängt.
>
>
> Translate with Google:
>
> Hello everybody. I am a beginner with Linux. I have successfully 
> installed Weewx on my RasbeeryPi. It also works with the simulator 
> and the Apache server. Website is displayed. Unfortunately, I am 
> unable to get FTP running. I have attached the excerpt from the 
> config and the log.
>
> Thanks. Renato
>
>

-- 
You received this message because you are subscribed to the Google 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/c4fc13b1-bf1f-4dfd-80ec-11ca66880b0cn%40googlegroups.com.

[weewx-user] Re: belchertown skin

[joh....@gmail.com]

Hi,

I have the same issue. but no solution so far
ord...@billandcorena.com schrieb am Dienstag, 26. Januar 2021 um 18:06:56 
UTC+1:

> Hi what would be causing all this as I get a good webpage to display after 
> each update but with this in log every loop?
>
>  
>
>  
>
>  
>
>  
>
> an 26 08:22:02 
>
> raspberrypi weewx[5] INFO weewx.restx: Wunderground:Posting not 
> enabled. Jan 26 08:22:02 raspberrypi weewx[5] INFOweewx.restx: 
>
> PWSweather: Posting not enabled. Jan 26 08:22:02 raspberrypi 
> weewx[5]INFO weewx.restx: 
>
> CWOP: Posting not enabled.
>
> Jan 26 08:22:02 raspberrypi weewx[5] INFO weewx.restx: WOW: Posting 
> not enabled. Jan 26 08:22:02 raspberrypi weewx[5] INFO weewx.restx:
>
> AWEKAS: Posting not enabled. Jan 26 08:22:02 raspberrypi weewx[5] INFO 
> __main__: Starting up weewx version 4.3.0 Jan 26 08:22:03 raspberrypi 
> weewx[5] INFO weewx.engine: Clock error is 3.18 seconds (positive is 
> fast) Jan 26 08:22:03 raspberrypi weewx[5] INFO
>
> weewx.engine: Using binding 'wx_binding' to database 'weewx.sdb' Jan 26
>
> 08:22:03 raspberrypi weewx[5] INFO weewx.manager: Starting backfill of 
> daily summaries Jan 26 08:22:05 raspberrypi weewx[5] INFO
>
> weewx.engine: Starting main packet loop. Jan 26 08:25:14 raspberrypi 
> weewx[5] INFO weewx.manager: Added record 2021-01-26 08:25:00 MST
>
> (1611674700) to database 'weewx.sdb' Jan 26 08:25:14 raspberrypi 
> weewx[5] INFO weewx.manager: Added record 2021-01-26 08:25:00 MST
>
> (1611674700) to daily summary in 'weewx.sdb' Jan 26 08:25:17 raspberrypi 
> weewx[5] INFO weewx.cheetahgenerator: Generated 8 files for report 
> SeasonsReport in 1.77 seconds Jan 26 08:25:17 raspberrypi weewx[5] INFO 
> weewx.imagegenerator: Generated 15 images for report SeasonsReport in 0.67 
> seconds Jan 26 08:25:17 raspberrypi weewx[5] INFO weewx.reportengine: 
> Copied 5 files to /var/www/html/weewx Jan 26
>
> 08:25:17 raspberrypi weewx[5] INFO user.belchertown: version 1.2 Jan 
> 26 08:25:17 raspberrypi weewx[5] ERROR user.belchertown: Error getting 
> AQI from Aeris weather. The error was:#012list index out of range#012The 
> response from the Aeris AQI server was:#012[{'success':
>
> True, 'error': {'code': 'warn_no_data', 'description': 'Valid request.
>
> No results available based on your query parameters.'}, 'response':
>
> []}]#012The URL being used
>
> is:#012
> https://api.aerisapi.com/airquality/closest?p=42.8375,-103.0094=json=50mi=1_id=***
>
> Jan 26 08:25:18 raspberrypi weewx[5] ERROR user.belchertown: Error 
> getting AQI from Aeris weather. The error was:#012list index out of 
> range#012The response from the Aeris AQI server was:#012[{'success':
>
> True, 'error': {'code': 'warn_no_data', 'description': 'Valid request.
>
> No results available based on your query parameters.'}, 'response':
>
> []}]#012The URL being used
>
> is:#012
> https://api.aerisapi.com/airquality/closest?p=42.8375,-103.0094=json=50mi=1_id=*
>
> getting AQI from Aeris weather. The error was:#012list index out of 
> range#012The response from the Aeris AQI server was:#012[{'success':
>
> True, 'error': {'code': 'warn_no_data', 'description': 'Valid request.
>
> No results available based on your query parameters.'}, 'response':
>
> []}]#012The URL being used
>
> is:#012
> https://api.aerisapi.com/airquality/closest?p=42.8375,-103.0094=json=50mi=1_id=
>
> Jan 26 08:25:19 raspberrypi weewx[5] ERROR user.belchertown: Error 
> getting AQI from Aeris weather. The error was:#012list index out of 
> range#012The response from the Aeris AQI server was:#012[{'success':
>
> True, 'error': {'code': 'warn_no_data', 'description': 'Valid request.
>
> No results available based on your query parameters.'}, 'response':
>
> []}]#012The URL being used
>
> is:#012
> https://api.aerisapi.com/airquality/closest?p=42.8375,-103.0094=json=50mi=1_id=**
>
> Jan 26 08:25:19 raspberrypi weewx[5] ERROR user.belchertown: Error 
> getting AQI from Aeris weather. The error was:#012list index out of 
> range#012The response from the Aeris AQI server was:#012[{'success':
>
> True, 'error': {'code': 'warn_no_data', 'description': 'Valid request.
>
> No results available based on your query parameters.'}, 'response':
>
> []}]#012The URL being used
>
> is:#012
> https://api.aerisapi.com/airquality/closest?p=42.8375,-103.0094=json=50mi=1_id=*
>
> Jan 26 08:25:19 raspberrypi weewx[5] ERROR user.belchertown: Error 
> getting AQI from Aeris weather. The error was:#012list index out of 
> range#012The response from the Aeris AQI server was:#012[{'success':
>
> True, 'error': {'code': 'warn_no_data', 'description': 'Valid request.
>
> No results available based on your query parameters.'}, 'response':
>
> []}]#012The URL being used
>
> is:#012
> 

Re: [weewx-user] Re: Graph not update

[ginfo...@gmail.com]

Obviously I'm talking about the graphs, if you look closely, those of the 
day are still.
They should update every 5 minutes ...

Il giorno venerdì 5 febbraio 2021 alle 07:48:05 UTC+1 ginfo...@gmail.com ha 
scritto:

> If I delete the browser cache, it updates regularly, but then remains 
> blocked there
>
> Il giorno venerdì 5 febbraio 2021 alle 07:45:10 UTC+1 ginfo...@gmail.com 
> ha scritto:
>
>> Yes, the station updates regularly and transmits data.
>> These are the graphics that are not transmitted and updated on the site.
>> I checked the local and remote folder, and the graphs are regularly 
>> updated.
>> It appears to be a cache problem.
>>
>> Il giorno venerdì 5 febbraio 2021 alle 07:35:50 UTC+1 graha...@gmail.com 
>> ha scritto:
>>
>>> is this the correct target ftp location?
>>>
>>> On 5 Feb 2021, at 5:24 pm, ginfo...@gmail.com  
>>> wrote:
>>>
>>> Feb  5 05:55:32 raspberrypi weewx[7414] DEBUG weeutil.ftpupload: 
>>> Connected to it31.siteground.eu
>>> Feb  5 05:55:32 raspberrypi weewx[7414] DEBUG weeutil.ftpupload: 
>>> Uploaded file /home/weewx/public_html/favicon.ico to /public_html/
>>> www.meteomestre.it/favicon.ico
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google 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/ce846c4d-e7f4-4162-ad40-efe9b73282d5n%40googlegroups.com.

Re: [weewx-user] Re: Graph not update

[ginfo...@gmail.com]

If I delete the browser cache, it updates regularly, but then remains 
blocked there

Il giorno venerdì 5 febbraio 2021 alle 07:45:10 UTC+1 ginfo...@gmail.com ha 
scritto:

> Yes, the station updates regularly and transmits data.
> These are the graphics that are not transmitted and updated on the site.
> I checked the local and remote folder, and the graphs are regularly 
> updated.
> It appears to be a cache problem.
>
> Il giorno venerdì 5 febbraio 2021 alle 07:35:50 UTC+1 graha...@gmail.com 
> ha scritto:
>
>> is this the correct target ftp location?
>>
>> On 5 Feb 2021, at 5:24 pm, ginfo...@gmail.com  wrote:
>>
>> Feb  5 05:55:32 raspberrypi weewx[7414] DEBUG weeutil.ftpupload: 
>> Connected to it31.siteground.eu
>> Feb  5 05:55:32 raspberrypi weewx[7414] DEBUG weeutil.ftpupload: Uploaded 
>> file /home/weewx/public_html/favicon.ico to /public_html/
>> www.meteomestre.it/favicon.ico
>>
>>
>>

-- 
You received this message because you are subscribed to the Google 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/822faac5-80e2-42ea-9ce2-572426613abbn%40googlegroups.com.

Re: [weewx-user] Re: Graph not update

[ginfo...@gmail.com]

Yes, the station updates regularly and transmits data.
These are the graphics that are not transmitted and updated on the site.
I checked the local and remote folder, and the graphs are regularly updated.
It appears to be a cache problem.

Il giorno venerdì 5 febbraio 2021 alle 07:35:50 UTC+1 graha...@gmail.com ha 
scritto:

> is this the correct target ftp location?
>
> On 5 Feb 2021, at 5:24 pm, ginfo...@gmail.com  wrote:
>
> Feb  5 05:55:32 raspberrypi weewx[7414] DEBUG weeutil.ftpupload: Connected 
> to it31.siteground.eu
> Feb  5 05:55:32 raspberrypi weewx[7414] DEBUG weeutil.ftpupload: Uploaded 
> file /home/weewx/public_html/favicon.ico to /public_html/
> www.meteomestre.it/favicon.ico
>
>
>

-- 
You received this message because you are subscribed to the Google 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/99b95e09-dfa8-455d-90d9-35ebafaaaeccn%40googlegroups.com.

Re: [weewx-user] Re: Graph not update

[Graham Eddy]

is this the correct target ftp location?

> On 5 Feb 2021, at 5:24 pm, ginfo...@gmail.com  wrote:
> 
> Feb  5 05:55:32 raspberrypi weewx[7414] DEBUG weeutil.ftpupload: Connected to 
> it31.siteground.eu 
> Feb  5 05:55:32 raspberrypi weewx[7414] DEBUG weeutil.ftpupload: Uploaded 
> file /home/weewx/public_html/favicon.ico to 
> /public_html/www.meteomestre.it/favicon.ico 
> 

-- 
You received this message because you are subscribed to the Google 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/38B1C430-4128-4CE9-8080-DE96FB9D97F5%40gmail.com.

[weewx-user] Re: Graph not update

[gjr80]

Hmm, you missed the WeeWX startup in your log extract and only showed 23 
seconds of log rather than 15 minutes. Nonetheless I suspect you may be 
suffering from corrupt station memory. Try working through the steps under 
Corrupt 
station memory 

 
in the Troubleshooting Davis stations wiki entry 
.
 
If the problem remains after working through those steps please restart 
WeeWX again and let it run for 15 minutes. After 15 minutes take a log 
extract this time make sure you capture the WeeWX startup and the full 15 
minutes of log entries. Post the log extract here.

Gary 

On Friday, 5 February 2021 at 15:49:14 UTC+10 ginfo...@gmail.com wrote:

> Feb  5 06:10:14 raspberrypi weewx[7414] DEBUG weewx.drivers.vantage: 
> Getting archive packets since 2021-02-05 06:05:00 CET (1612501500)
> Feb  5 06:10:14 raspberrypi weewx[7414] DEBUG weewx.drivers.vantage: 
> Gentle wake up of console successful
> Feb  5 06:10:14 raspberrypi weewx[7414] DEBUG weewx.drivers.vantage: 
> Retrieving 1 page(s); starting index= 3
> Feb  5 06:10:14 raspberrypi weewx[7414] INFO weewx.manager: Added record 
> 2021-02-05 06:10:00 CET (1612501800) to database 'weewx.sdb'
> Feb  5 06:10:14 raspberrypi weewx[7414] INFO weewx.manager: Added record 
> 2021-02-05 06:10:00 CET (1612501800) to daily summary in 'weewx.sdb'
> Feb  5 06:10:15 raspberrypi weewx[7414] DEBUG weewx.drivers.vantage: 
> DMPAFT complete: page timestamp 2021-01-27 08:55:00 CET (1611734100) less 
> than final timestamp 2021-02-05 06:10:00 CET (1612501800)
> Feb  5 06:10:15 raspberrypi weewx[7414] DEBUG weewx.drivers.vantage: Catch 
> up complete.
> Feb  5 06:10:15 raspberrypi weewx[7414] DEBUG weewx.reportengine: Running 
> reports for latest time in the database.
> Feb  5 06:10:15 raspberrypi weewx[7414] DEBUG weewx.reportengine: Running 
> report 'SeasonsReport'
> Feb  5 06:10:15 raspberrypi weewx[7414] DEBUG weewx.drivers.vantage: 
> Requesting 200 LOOP packets.
> Feb  5 06:10:15 raspberrypi weewx[7414] DEBUG weewx.reportengine: Found 
> configuration file /home/weewx/skins/Seasons/skin.conf for report 
> 'SeasonsReport'
> Feb  5 06:10:15 raspberrypi weewx[7414] DEBUG weewx.cheetahgenerator: 
> Using search list ['weewx.cheetahgenerator.Almanac', 
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
> 'weewx.cheetahgenerator.Extras']
> Feb  5 06:10:15 raspberrypi weewx[7414] DEBUG weewx.drivers.vantage: 
> Gentle wake up of console successful
> Feb  5 06:10:15 raspberrypi weewx[7414] DEBUG weewx.manager: Daily summary 
> version is 1.0
> Feb  5 06:10:15 raspberrypi weewx[7414] INFO weewx.restx: 
> Wunderground-PWS: Published record 2021-02-05 06:10:00 CET (1612501800)
> Feb  5 06:10:17 raspberrypi weewx[7414] INFO weewx.cheetahgenerator: 
> Generated 8 files for report SeasonsReport in 1.68 seconds
> Feb  5 06:10:17 raspberrypi weewx[7414] DEBUG weewx.manager: Daily summary 
> version is 1.0
> Feb  5 06:10:18 raspberrypi weewx[7414] INFO weewx.imagegenerator: 
> Generated 14 images for report SeasonsReport in 1.17 seconds
> Feb  5 06:10:18 raspberrypi weewx[7414] INFO weewx.reportengine: Copied 0 
> files to /home/weewx/public_html
> Feb  5 06:10:18 raspberrypi weewx[7414] DEBUG weewx.reportengine: Report 
> 'SmartphoneReport' not enabled. Skipping.
> Feb  5 06:10:18 raspberrypi weewx[7414] DEBUG weewx.reportengine: Report 
> 'MobileReport' not enabled. Skipping.
> Feb  5 06:10:18 raspberrypi weewx[7414] DEBUG weewx.reportengine: Running 
> report 'StandardReport'
> Feb  5 06:10:18 raspberrypi weewx[7414] DEBUG weewx.reportengine: Found 
> configuration file /home/weewx/skins/neowx/skin.conf for report 
> 'StandardReport'
> Feb  5 06:10:18 raspberrypi weewx[7414] DEBUG weewx.cheetahgenerator: 
> Using search list ['weewx.cheetahgenerator.Almanac', 
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
> 'weewx.cheetahgenerator.Extras']
> Feb  5 06:10:18 raspberrypi weewx[7414] DEBUG weewx.manager: Daily summary 
> version is 1.0
> Feb  5 06:10:19 raspberrypi weewx[7414] INFO weewx.cheetahgenerator: 
> Generated 9 files for report StandardReport in 1.64 seconds
> Feb  5 06:10:19 raspberrypi weewx[7414] DEBUG weewx.manager: Daily summary 
> version is 1.0
> Feb  5 06:10:23 raspberrypi weewx[7414] INFO weewx.imagegenerator: 
> Generated 12 images for report StandardReport in 3.10 seconds
> Feb  5 06:10:23 raspberrypi weewx[7414] INFO weewx.reportengine: Copied 17 
> files to /home/weewx/public_html
> Feb  5 06:10:23 raspberrypi weewx[7414] DEBUG weewx.reportengine: Running 
> report 'FTP'
> Feb  5 06:10:23 raspberrypi weewx[7414] DEBUG weewx.reportengine: Found 
> configuration file /home/weewx/skins/Ftp/skin.conf for 

[weewx-user] Re: Graph not update

[ginfo...@gmail.com]

Feb  5 06:10:14 raspberrypi weewx[7414] DEBUG weewx.drivers.vantage: 
Getting archive packets since 2021-02-05 06:05:00 CET (1612501500)
Feb  5 06:10:14 raspberrypi weewx[7414] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful
Feb  5 06:10:14 raspberrypi weewx[7414] DEBUG weewx.drivers.vantage: 
Retrieving 1 page(s); starting index= 3
Feb  5 06:10:14 raspberrypi weewx[7414] INFO weewx.manager: Added record 
2021-02-05 06:10:00 CET (1612501800) to database 'weewx.sdb'
Feb  5 06:10:14 raspberrypi weewx[7414] INFO weewx.manager: Added record 
2021-02-05 06:10:00 CET (1612501800) to daily summary in 'weewx.sdb'
Feb  5 06:10:15 raspberrypi weewx[7414] DEBUG weewx.drivers.vantage: DMPAFT 
complete: page timestamp 2021-01-27 08:55:00 CET (1611734100) less than 
final timestamp 2021-02-05 06:10:00 CET (1612501800)
Feb  5 06:10:15 raspberrypi weewx[7414] DEBUG weewx.drivers.vantage: Catch 
up complete.
Feb  5 06:10:15 raspberrypi weewx[7414] DEBUG weewx.reportengine: Running 
reports for latest time in the database.
Feb  5 06:10:15 raspberrypi weewx[7414] DEBUG weewx.reportengine: Running 
report 'SeasonsReport'
Feb  5 06:10:15 raspberrypi weewx[7414] DEBUG weewx.drivers.vantage: 
Requesting 200 LOOP packets.
Feb  5 06:10:15 raspberrypi weewx[7414] DEBUG weewx.reportengine: Found 
configuration file /home/weewx/skins/Seasons/skin.conf for report 
'SeasonsReport'
Feb  5 06:10:15 raspberrypi weewx[7414] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras']
Feb  5 06:10:15 raspberrypi weewx[7414] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful
Feb  5 06:10:15 raspberrypi weewx[7414] DEBUG weewx.manager: Daily summary 
version is 1.0
Feb  5 06:10:15 raspberrypi weewx[7414] INFO weewx.restx: Wunderground-PWS: 
Published record 2021-02-05 06:10:00 CET (1612501800)
Feb  5 06:10:17 raspberrypi weewx[7414] INFO weewx.cheetahgenerator: 
Generated 8 files for report SeasonsReport in 1.68 seconds
Feb  5 06:10:17 raspberrypi weewx[7414] DEBUG weewx.manager: Daily summary 
version is 1.0
Feb  5 06:10:18 raspberrypi weewx[7414] INFO weewx.imagegenerator: 
Generated 14 images for report SeasonsReport in 1.17 seconds
Feb  5 06:10:18 raspberrypi weewx[7414] INFO weewx.reportengine: Copied 0 
files to /home/weewx/public_html
Feb  5 06:10:18 raspberrypi weewx[7414] DEBUG weewx.reportengine: Report 
'SmartphoneReport' not enabled. Skipping.
Feb  5 06:10:18 raspberrypi weewx[7414] DEBUG weewx.reportengine: Report 
'MobileReport' not enabled. Skipping.
Feb  5 06:10:18 raspberrypi weewx[7414] DEBUG weewx.reportengine: Running 
report 'StandardReport'
Feb  5 06:10:18 raspberrypi weewx[7414] DEBUG weewx.reportengine: Found 
configuration file /home/weewx/skins/neowx/skin.conf for report 
'StandardReport'
Feb  5 06:10:18 raspberrypi weewx[7414] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras']
Feb  5 06:10:18 raspberrypi weewx[7414] DEBUG weewx.manager: Daily summary 
version is 1.0
Feb  5 06:10:19 raspberrypi weewx[7414] INFO weewx.cheetahgenerator: 
Generated 9 files for report StandardReport in 1.64 seconds
Feb  5 06:10:19 raspberrypi weewx[7414] DEBUG weewx.manager: Daily summary 
version is 1.0
Feb  5 06:10:23 raspberrypi weewx[7414] INFO weewx.imagegenerator: 
Generated 12 images for report StandardReport in 3.10 seconds
Feb  5 06:10:23 raspberrypi weewx[7414] INFO weewx.reportengine: Copied 17 
files to /home/weewx/public_html
Feb  5 06:10:23 raspberrypi weewx[7414] DEBUG weewx.reportengine: Running 
report 'FTP'
Feb  5 06:10:23 raspberrypi weewx[7414] DEBUG weewx.reportengine: Found 
configuration file /home/weewx/skins/Ftp/skin.conf for report 'FTP'
Feb  5 06:10:23 raspberrypi weewx[7414] DEBUG weeutil.ftpupload: Attempting 
connection to it31.siteground.eu
Feb  5 06:10:23 raspberrypi weewx[7414] DEBUG weeutil.ftpupload: Connected 
to it31.siteground.eu
Feb  5 06:10:23 raspberrypi weewx[7414] DEBUG weeutil.ftpupload: Uploaded 
file /home/weewx/public_html/daywindvec.png to 
/public_html/www.meteomestre.it/daywindvec.png
Feb  5 06:10:23 raspberrypi weewx[7414] DEBUG weeutil.ftpupload: Uploaded 
file /home/weewx/public_html/dayhumidity.png to 
/public_html/www.meteomestre.it/dayhumidity.png
Feb  5 06:10:24 raspberrypi weewx[7414] DEBUG weeutil.ftpupload: Uploaded 
file /home/weewx/public_html/daytempfeel.png to 
/public_html/www.meteomestre.it/daytempfeel.png
Feb  5 06:10:24 raspberrypi weewx[7414] DEBUG weeutil.ftpupload: Uploaded 
file /home/weewx/public_html/dayinside.png to 
/public_html/www.meteomestre.it/dayinside.png
Feb  5 06:10:24 raspberrypi weewx[7414] DEBUG weeutil.ftpupload: Uploaded 

[weewx-user] Re: DP1500/GW1000, missing sensors and values WH31 / WN51

[gjr80]

Hi,

Short answer is it depends. Two key points are the driver you are using 
(there are two drivers that support the GW1000) and what database schema 
you are using. Could I ask you to run wee_debug --info 
 and post the output 
here so that we can have some understanding of how your system is 
configured and provide appropriate advice. Before posting the wee_debug 
output do check it for any sensitive information such as user names, 
passwords, API keys etc. wee_debug should obfuscate such information but it 
is not perfect.

Gary

On Wednesday, 3 February 2021 at 19:10:21 UTC+10 Thomas Hackler wrote:

>
> Hello,
>
> I am using weewx with raspberry pi 3, WeeWX version 4.2.0. I have a 
> froggit DP1500/GW1000 with a WH3000 and four DP50/WH31 temp/humidity 
> sensors and one DP100/WN51 for moisture. Weewx only show me three of the 
> WH31 without humidity. 
>
> How can I add the missing WH31 and WN51 and the humidity values from the 
> WH31? 
>
> With ecowitt or WU I can see all the sensors and all values.
>
> I think I have to add the missing sensors somewhere in the configuration 
> file but I don’t know where?
>
> Which information from the files do you need?
>
> Thank you!
>
> [image: weewx.JPG]
>

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

[weewx-user] Re: Graph not update

[gjr80]

Hi,

Could be any of a number of issues, we are going to need to see the log to 
work out exactly what is going on. Can you edit weewx.conf, set debug = 1, 
save weewx.conf and then restart WeeWX. Let WeeWX run for 15 minutes or so 
then take a copy of the log from when you restarted WeeWX through until the 
15 minutes have passed. Post the log extract here making sure you capture 
the full WeeWX startup.

Gary

On Friday, 5 February 2021 at 00:36:44 UTC+10 ginfo...@gmail.com wrote:

> [image: Schermata 2021-02-04 alle 15.35.30.png]Hello and congratulations 
> on this fantastic forum.
> My weather station is a Davis Vantage Vue and updates regularly.
> I have always had problems with the graphics, however, they do not update 
> for a long time and sometimes I have to clear the cache.
> How can I solve?
> Thank you
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2af96f4b-f836-47f5-87d8-4a0040369677n%40googlegroups.com.

Re: [weewx-user] Re: WEEWX-WD and Weewx 4.2 to 4.4

[Tom Keffer]

That station (using the ip100 driver) does not support hardware record
generation, so WeeWX will fall back on software record generation. If you
are still getting 5 minute updates despite setting archive_interval to 120,
then one of two things is happening:

   1. weewxd is using a different configuration file than you think it is;
   or
   2. You didn't restart weewxd after changing the value.

If neither of those are true, then we will need to see the log. Set
debug=1, restart weewx, post the log from startup through the first
reporting cycle.

tk

On Thu, Feb 4, 2021 at 5:41 PM Tim  wrote:

> Tom,
>
> The station is a RainWise MK-III with an IP-100.
>
> Regards,
>
> Tim
>
> Sent from my Hi-Tech Etch-A-Sketch
>
>
> On Feb 4, 2021, at 14:20, Tom Keffer  wrote:
>
> 
> You didn't say what kind of weather station you are using, but for
> stations that support hardware logging and if you specify hardware record
> generation,  then weewx will use the interval specified in your hardware.
>
> If this is the case, then to change use the wee_device utility with the
> --set-interval option. For example, to change to two minutes:
>
> *wee_device --set-interval=2*
>
> -tk
>
>
>
> On Thu, Feb 4, 2021 at 9:12 AM tim lambert 
> wrote:
>
>> Hi Gary,
>>
>> I'm taking things in baby steps.
>>
>> Earlier this week I successfully upgraded from weewx 4.2 to weewx 4.4
>> (which was surprisingly easy with how weewx addresses upgrades).
>> Everything is stable, so I'm moving onward to the next steps.
>>
>> I've taken the route to implement WeeWX SteelSeries Weather Gauges
>> extension (not real-time yet) and WeeWX-WD v2.1.2 -- everything installed
>> and I can see the SteelGauge info on my remotely hosted website, as well as
>> see the clientraw.text and other key files for Saratoga Templates on the
>> remotely hosted server.
>>
>> However, even though I have the archive_interval in weewx.conf set to 120
>> (seconds) the FTP of the files generated by weewx is occurring every 300
>> seconds (5 minutes) -- which I confirmed from reviewing the log files.
>> How can I get the FTP to execute every 120 seconds?
>>
>> FYI, weewx.conf for Standard Archive is
>>
>>
>>
>>
>>
>>
>> *[StdArchive]archive_interval = 120record_generation =
>> hardwareloop_hilo = Truedata_binding = wx_binding*
>>
>> Should I change the record_generation to software?   Noting the Rainwise
>> IP-100 is inserting records into the MySQL database tables every minute --
>> which is what I want.
>>
>> Thanks in Advance for your guidance!
>>
>> -- Tim
>>
>> On Saturday, January 30, 2021 at 8:35:31 PM UTC-8 tim lambert wrote:
>>
>>> Thanks Gary for the insight and guidance.
>>>
>>>
>>>
>>>
>>>
>>> Sent from Mail  for
>>> Windows 10
>>>
>>>
>>>
>>> *From: *gjr80
>>> *Sent: *Saturday, January 30, 2021 7:58 PM
>>> *To: *weewx-user
>>> *Subject: *[weewx-user] Re: WEEWX-WD and Weewx 4.2 to 4.4
>>>
>>>
>>>
>>> Hi,
>>>
>>>
>>>
>>> I wouldn't be using WeeWX-WD from bitbucket, it has not been touched for
>>> some years now. WeeWX-WD on github
>>>  is more up to date, the
>>> current version is v2.1.2 from November 2020. It should have no problems
>>> running on WeeWX v4.x under python 2 or python3. The SteelSeries
>>> Weather Gauges 
>>> have directly supported WeeWX of v2.5.0 (of the SteelSeries Weather Gauges)
>>> or for about six years, and there is now a WeeWX SteelSeries Gauges
>>> extension  that
>>> installs the necessary skin to support the SteelSeries Weather Gauges (this
>>> is the preferred means of providing the SteelSeries Weather Gauges,
>>> WeeWX-WD did support the SteelSeries Weather Gauges via the WD
>>> customclientraw.txt but since the advent of direct WeeWX support and
>>> the WeeWX extension the SteelSeries Weather Gauges support has been
>>> deprecated in WeeWX-WD). You should find the WeeWX extension will work
>>> under WeeWX v4.x and python2 or python3.
>>>
>>>
>>>
>>> I would suggest that you upgrade to WeeWX v4.4.0 and get WeeWX running
>>> to your satisfaction before installing either WeeWX-WD v2.1.2 or the WeeWX
>>> SteelSeries Weather Gauges extension (in whatever order suits). Once you
>>> have the SteelSeries Weather Gauges extension running OK you can, if you
>>> want, look at installing the Realtime gauge-data extension
>>>  which will allow
>>> the gauges to update on every loop packet rather than on each report cycle
>>> (how often they will update will depend on how often your station emits
>>> loop packets, for your Rainwise this should be up to every couple of
>>> seconds).
>>>
>>>
>>>
>>> Gary
>>>
>>>
>>>
>>> On Sunday, 31 January 2021 at 13:15:24 UTC+10 tim lambert wrote:
>>>
>>> Gang,
>>>
>>>
>>>
>>> Currently running weewx 4.2 (will be upgrading in the next few days to
>>> 4.4) 

Re: [weewx-user] Re: WEEWX-WD and Weewx 4.2 to 4.4

[Tim]

Tom,

The station is a RainWise MK-III with an IP-100.

Regards,

Tim

Sent from my Hi-Tech Etch-A-Sketch


> On Feb 4, 2021, at 14:20, Tom Keffer  wrote:
> 
> 
> You didn't say what kind of weather station you are using, but for stations 
> that support hardware logging and if you specify hardware record generation,  
> then weewx will use the interval specified in your hardware.
> 
> If this is the case, then to change use the wee_device utility with the 
> --set-interval option. For example, to change to two minutes:
> 
> wee_device --set-interval=2
> 
> -tk
> 
> 
> 
>> On Thu, Feb 4, 2021 at 9:12 AM tim lambert  wrote:
>> Hi Gary,
>> 
>> I'm taking things in baby steps. 
>> 
>> Earlier this week I successfully upgraded from weewx 4.2 to weewx 4.4 (which 
>> was surprisingly easy with how weewx addresses upgrades).   Everything is 
>> stable, so I'm moving onward to the next steps.
>> 
>> I've taken the route to implement WeeWX SteelSeries Weather Gauges extension 
>> (not real-time yet) and WeeWX-WD v2.1.2 -- everything installed and I can 
>> see the SteelGauge info on my remotely hosted website, as well as see the 
>> clientraw.text and other key files for Saratoga Templates on the remotely 
>> hosted server.   
>> 
>> However, even though I have the archive_interval in weewx.conf set to 120 
>> (seconds) the FTP of the files generated by weewx is occurring every 300 
>> seconds (5 minutes) -- which I confirmed from reviewing the log files.   How 
>> can I get the FTP to execute every 120 seconds?
>> 
>> FYI, weewx.conf for Standard Archive is
>> 
>> [StdArchive]
>> 
>> archive_interval = 120
>> record_generation = hardware
>> loop_hilo = True
>> data_binding = wx_binding
>> 
>> Should I change the record_generation to software?   Noting the Rainwise 
>> IP-100 is inserting records into the MySQL database tables every minute -- 
>> which is what I want.
>> 
>> Thanks in Advance for your guidance!
>> 
>> -- Tim
>> 
>>> On Saturday, January 30, 2021 at 8:35:31 PM UTC-8 tim lambert wrote:
>>> Thanks Gary for the insight and guidance.
>>> 
>>>  
>>> 
>>>  
>>> 
>>> Sent from Mail for Windows 10
>>> 
>>>  
>>> 
>>> From: gjr80
>>> Sent: Saturday, January 30, 2021 7:58 PM
>>> To: weewx-user
>>> Subject: [weewx-user] Re: WEEWX-WD and Weewx 4.2 to 4.4
>>> 
>>>  
>>> 
>>> Hi,
>>> 
>>>  
>>> 
>>> I wouldn't be using WeeWX-WD from bitbucket, it has not been touched for 
>>> some years now. WeeWX-WD on github is more up to date, the current version 
>>> is v2.1.2 from November 2020. It should have no problems running on WeeWX 
>>> v4.x under python 2 or python3. The SteelSeries Weather Gauges have 
>>> directly supported WeeWX of v2.5.0 (of the SteelSeries Weather Gauges) or 
>>> for about six years, and there is now a WeeWX SteelSeries Gauges extension 
>>> that installs the necessary skin to support the SteelSeries Weather Gauges 
>>> (this is the preferred means of providing the SteelSeries Weather Gauges, 
>>> WeeWX-WD did support the SteelSeries Weather Gauges via the WD 
>>> customclientraw.txt but since the advent of direct WeeWX support and the 
>>> WeeWX extension the SteelSeries Weather Gauges support has been deprecated 
>>> in WeeWX-WD). You should find the WeeWX extension will work under WeeWX 
>>> v4.x and python2 or python3.
>>> 
>>>  
>>> 
>>> I would suggest that you upgrade to WeeWX v4.4.0 and get WeeWX running to 
>>> your satisfaction before installing either WeeWX-WD v2.1.2 or the WeeWX 
>>> SteelSeries Weather Gauges extension (in whatever order suits). Once you 
>>> have the SteelSeries Weather Gauges extension running OK you can, if you 
>>> want, look at installing the Realtime gauge-data extension which will allow 
>>> the gauges to update on every loop packet rather than on each report cycle 
>>> (how often they will update will depend on how often your station emits 
>>> loop packets, for your Rainwise this should be up to every couple of 
>>> seconds).
>>> 
>>>  
>>> 
>>> Gary
>>> 
>>>  
>>> 
>>> On Sunday, 31 January 2021 at 13:15:24 UTC+10 tim lambert wrote:
>>> 
>>> Gang,
>>> 
>>>  
>>> 
>>> Currently running weewx 4.2 (will be upgrading in the next few days to 4.4) 
>>> on a Raspberry Pi 4 (32-bit OS) with a Rainwise MK-III and IP-100 providing 
>>> station data -- everything has been working properly for several weeks and 
>>> is populating a remote MySQL DB.
>>> 
>>>  
>>> 
>>> Once I upgrade weewx, I'd like to incorporate using Steel Gauges and 
>>> Saratoga Templates, hence my query:  Can I utilize the WEEWX-WD as outlined 
>>> BitBucket Weewx-WD?
>>> 
>>>  
>>> 
>>> The Steel Gauges and Saratoga Templates will be hosted on a remote, public 
>>> accessible server -- so I'll be sending the clientraw and testtag files via 
>>> FTP.
>>> 
>>>  
>>> 
>>> Thanks in Advance!
>>> 
>>>  
>>> 
>>> - Tim
>>> 
>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, 

Re: [weewx-user] Re: NOAA report with dust sensor

[Tom Keffer]

Is the page on the web? If not, can you post it?

On Thu, Feb 4, 2021 at 3:26 PM bgra...@umw.edu  wrote:

> Tom,
> It shows up in Edge, Chrome, and Firefox.  All I changed was the "encoding
> = utf8" for the NOAA reports (cheetagenerator in skin.conf) as was
> discussed in this thread.
> I don't have any special characters in use but now see the degree symbol
> along with the other odd addition   (°F) .
> Thanks.
> BG
> see* http://grattans.org/wx * under month of
> Feb.  It's not showing in Jan as that report was created before my change
> to utf8.
> On Thursday, February 4, 2021 at 5:37:23 PM UTC-5 tke...@gmail.com wrote:
>
>> Are you seeing this in a browser? If so, this is generally caused by the
>> browser using the wrong encoding. For example, it's probably expecting
>> Latin-1 (or Windows-1252) instead of the actual utf-8.
>>
>> As for why, did you add anything else to your NOAA page? Such, as an
>> encoding directive?
>>
>> If no encoding directive, then which browser are you using? Chrome
>> autodetects the encoding, but generally gets it right. For others, you must
>> set the encoding manually.
>>
>> -tk
>>
>> On Thu, Feb 4, 2021 at 2:15 PM bgra...@umw.edu  wrote:
>>
>>> Gary,
>>> My upgrade to 4.4.0 was not a new install and I need to change manually
>>> to utf8. I made changes in skin.conf but must have missed something. My
>>> NOAA daily now shows:
>>> TEMPERATURE (°F), RAIN (in), WIND SPEED (mph)
>>>
>>> old form with html_entities encoding was:
>>> TEMPERATURE (F), RAIN (in), WIND SPEED (mph)
>>>
>>> Is there something I need to delete and rebuild?
>>>
>>> Thanks
>>> BG
>>>
>>>
>>>
>>> On Wednesday, February 3, 2021 at 1:53:47 AM UTC-5 gjr80 wrote:
>>>
 Just by way of background up until v4.3.0 WeeWX shipped with
 strict_ascii encoding for NOAA reports. v4.4.0 changed that to utf8 but for
 new installs only, upgrades or earlier versions need to be changed 
 manually.

 Gary

 On Wednesday, 3 February 2021 at 16:27:31 UTC+10 calo@gmail.com
 wrote:

> Hi Gary,
>
> thanks again. Works now.
> [image: DustPM10.png]
>
> On Wednesday, February 3, 2021 at 7:18:43 AM UTC+1 Calo Geyer wrote:
>
>> Hi Gary,
>>
>> thanks. Yes, you are right. Got this in my skins.conf and it is even
>> written in the explanation. Will change and report back.
>>
>>
>> [CheetahGenerator]
>>
>> # Possible encodings are 'html_entities', 'utf8', or
>> 'strict_ascii'
>> encoding = html_entities
>>
>> [[SummaryByMonth]]
>> # Reports that summarize "by month"
>> [[[NOAA_month]]]
>> encoding = strict_ascii
>> template = NOAA/NOAA-%Y-%m.txt.tmpl
>>
>> [[SummaryByYear]]
>> # Reports that summarize "by year"
>> [[[NOAA_year]]]
>> encoding = strict_ascii
>> template = NOAA/NOAA-%Y.txt.tmpl
>>
>> On Wednesday, February 3, 2021 at 7:11:51 AM UTC+1 gjr80 wrote:
>>
>>> Hi,
>>>
>>> What encoding are you using for the NOAA format reports in your
>>> skin.conf? If you have the old encoding = strict_ascii then no you won’t
>>> see the mu character, you should see it though if you have encoding = 
>>> utf8.
>>>
>>> Gary
>>>
>>> On Wednesday, 3 February 2021 at 16:00:13 UTC+10 calo@gmail.com
>>> wrote:
>>>
 Hi, I added my SDS011 data (which I read-in using file-pile)
 however the unit in the header is not shows as microgramm per cubic 
 meter.
 I changed the unit in units.py to see if it also is adapted in the 
 report
 and was working however using the default pm10_0 unit shows as g/m
 This is my entry in .tmpl
 DUST PM10 ($unit.label.SDS011_PM10.strip())


  [image: NOAA Dust PM10.png]

 Any idea?

>>> --
>>> You received this message because you are subscribed 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/e8c77f07-a140-4cd0-a5c4-23d80dc182f0n%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/37264028-a1af-4424-8a78-ed39f0adcb13n%40googlegroups.com
> 

Re: [weewx-user] Re: NOAA report with dust sensor

[bgra...@umw.edu]

Tom,
It shows up in Edge, Chrome, and Firefox.  All I changed was the "encoding 
= utf8" for the NOAA reports (cheetagenerator in skin.conf) as was 
discussed in this thread.
I don't have any special characters in use but now see the degree symbol 
along with the other odd addition   (°F) .
Thanks.
BG
see* http://grattans.org/wx* under month of Feb.  It's not showing in Jan 
as that report was created before my change to utf8.
On Thursday, February 4, 2021 at 5:37:23 PM UTC-5 tke...@gmail.com wrote:

> Are you seeing this in a browser? If so, this is generally caused by the 
> browser using the wrong encoding. For example, it's probably expecting 
> Latin-1 (or Windows-1252) instead of the actual utf-8.
>
> As for why, did you add anything else to your NOAA page? Such, as an 
> encoding directive? 
>
> If no encoding directive, then which browser are you using? Chrome 
> autodetects the encoding, but generally gets it right. For others, you must 
> set the encoding manually.
>
> -tk
>
> On Thu, Feb 4, 2021 at 2:15 PM bgra...@umw.edu  wrote:
>
>> Gary,
>> My upgrade to 4.4.0 was not a new install and I need to change manually 
>> to utf8. I made changes in skin.conf but must have missed something. My 
>> NOAA daily now shows:
>> TEMPERATURE (°F), RAIN (in), WIND SPEED (mph) 
>>
>> old form with html_entities encoding was:
>> TEMPERATURE (F), RAIN (in), WIND SPEED (mph)
>>
>> Is there something I need to delete and rebuild?
>>
>> Thanks
>> BG
>>
>>
>>
>> On Wednesday, February 3, 2021 at 1:53:47 AM UTC-5 gjr80 wrote:
>>
>>> Just by way of background up until v4.3.0 WeeWX shipped with 
>>> strict_ascii encoding for NOAA reports. v4.4.0 changed that to utf8 but for 
>>> new installs only, upgrades or earlier versions need to be changed manually.
>>>
>>> Gary
>>>
>>> On Wednesday, 3 February 2021 at 16:27:31 UTC+10 calo@gmail.com 
>>> wrote:
>>>
 Hi Gary,

 thanks again. Works now.
 [image: DustPM10.png]

 On Wednesday, February 3, 2021 at 7:18:43 AM UTC+1 Calo Geyer wrote:

> Hi Gary,
>
> thanks. Yes, you are right. Got this in my skins.conf and it is even 
> written in the explanation. Will change and report back.
>
>
> [CheetahGenerator]
>
> # Possible encodings are 'html_entities', 'utf8', or 'strict_ascii'
> encoding = html_entities
>
> [[SummaryByMonth]]
> # Reports that summarize "by month"
> [[[NOAA_month]]]
> encoding = strict_ascii
> template = NOAA/NOAA-%Y-%m.txt.tmpl
>
> [[SummaryByYear]]
> # Reports that summarize "by year"
> [[[NOAA_year]]]
> encoding = strict_ascii
> template = NOAA/NOAA-%Y.txt.tmpl
>
> On Wednesday, February 3, 2021 at 7:11:51 AM UTC+1 gjr80 wrote:
>
>> Hi,
>>
>> What encoding are you using for the NOAA format reports in your 
>> skin.conf? If you have the old encoding = strict_ascii then no you won’t 
>> see the mu character, you should see it though if you have encoding = 
>> utf8.
>>
>> Gary
>>
>> On Wednesday, 3 February 2021 at 16:00:13 UTC+10 calo@gmail.com 
>> wrote:
>>
>>> Hi, I added my SDS011 data (which I read-in using file-pile) however 
>>> the unit in the header is not shows as microgramm per cubic meter. I 
>>> changed the unit in units.py to see if it also is adapted in the report 
>>> and 
>>> was working however using the default pm10_0 unit shows as g/m
>>> This is my entry in .tmpl
>>> DUST PM10 ($unit.label.SDS011_PM10.strip())
>>>
>>>
>>>  [image: NOAA Dust PM10.png]
>>>
>>> Any idea?
>>>
>> -- 
>> You received this message because you are subscribed 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/e8c77f07-a140-4cd0-a5c4-23d80dc182f0n%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/37264028-a1af-4424-8a78-ed39f0adcb13n%40googlegroups.com.

Re: [weewx-user] Re: NOAA report with dust sensor

[Tom Keffer]

Are you seeing this in a browser? If so, this is generally caused by the
browser using the wrong encoding. For example, it's probably expecting
Latin-1 (or Windows-1252) instead of the actual utf-8.

As for why, did you add anything else to your NOAA page? Such, as an
encoding directive?

If no encoding directive, then which browser are you using? Chrome
autodetects the encoding, but generally gets it right. For others, you must
set the encoding manually.

-tk

On Thu, Feb 4, 2021 at 2:15 PM bgra...@umw.edu  wrote:

> Gary,
> My upgrade to 4.4.0 was not a new install and I need to change manually to
> utf8. I made changes in skin.conf but must have missed something. My NOAA
> daily now shows:
> TEMPERATURE (°F), RAIN (in), WIND SPEED (mph)
>
> old form with html_entities encoding was:
> TEMPERATURE (F), RAIN (in), WIND SPEED (mph)
>
> Is there something I need to delete and rebuild?
>
> Thanks
> BG
>
>
>
> On Wednesday, February 3, 2021 at 1:53:47 AM UTC-5 gjr80 wrote:
>
>> Just by way of background up until v4.3.0 WeeWX shipped with strict_ascii
>> encoding for NOAA reports. v4.4.0 changed that to utf8 but for new installs
>> only, upgrades or earlier versions need to be changed manually.
>>
>> Gary
>>
>> On Wednesday, 3 February 2021 at 16:27:31 UTC+10 calo@gmail.com
>> wrote:
>>
>>> Hi Gary,
>>>
>>> thanks again. Works now.
>>> [image: DustPM10.png]
>>>
>>> On Wednesday, February 3, 2021 at 7:18:43 AM UTC+1 Calo Geyer wrote:
>>>
 Hi Gary,

 thanks. Yes, you are right. Got this in my skins.conf and it is even
 written in the explanation. Will change and report back.


 [CheetahGenerator]

 # Possible encodings are 'html_entities', 'utf8', or 'strict_ascii'
 encoding = html_entities

 [[SummaryByMonth]]
 # Reports that summarize "by month"
 [[[NOAA_month]]]
 encoding = strict_ascii
 template = NOAA/NOAA-%Y-%m.txt.tmpl

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

 On Wednesday, February 3, 2021 at 7:11:51 AM UTC+1 gjr80 wrote:

> Hi,
>
> What encoding are you using for the NOAA format reports in your
> skin.conf? If you have the old encoding = strict_ascii then no you won’t
> see the mu character, you should see it though if you have encoding = 
> utf8.
>
> Gary
>
> On Wednesday, 3 February 2021 at 16:00:13 UTC+10 calo@gmail.com
> wrote:
>
>> Hi, I added my SDS011 data (which I read-in using file-pile) however
>> the unit in the header is not shows as microgramm per cubic meter. I
>> changed the unit in units.py to see if it also is adapted in the report 
>> and
>> was working however using the default pm10_0 unit shows as g/m
>> This is my entry in .tmpl
>> DUST PM10 ($unit.label.SDS011_PM10.strip())
>>
>>
>>  [image: NOAA Dust PM10.png]
>>
>> Any idea?
>>
> --
> You received this message because you are subscribed to the Google 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/e8c77f07-a140-4cd0-a5c4-23d80dc182f0n%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/CAPq0zEC7JwUTan7EyXSUU8icF-%2BuVXo8Rhy5qsQAimfwkVmStw%40mail.gmail.com.

Re: [weewx-user] Re: WEEWX-WD and Weewx 4.2 to 4.4

[Tom Keffer]

You didn't say what kind of weather station you are using, but for stations
that support hardware logging and if you specify hardware record
generation,  then weewx will use the interval specified in your hardware.

If this is the case, then to change use the wee_device utility with the
--set-interval option. For example, to change to two minutes:

*wee_device --set-interval=2*

-tk



On Thu, Feb 4, 2021 at 9:12 AM tim lambert  wrote:

> Hi Gary,
>
> I'm taking things in baby steps.
>
> Earlier this week I successfully upgraded from weewx 4.2 to weewx 4.4
> (which was surprisingly easy with how weewx addresses upgrades).
> Everything is stable, so I'm moving onward to the next steps.
>
> I've taken the route to implement WeeWX SteelSeries Weather Gauges
> extension (not real-time yet) and WeeWX-WD v2.1.2 -- everything installed
> and I can see the SteelGauge info on my remotely hosted website, as well as
> see the clientraw.text and other key files for Saratoga Templates on the
> remotely hosted server.
>
> However, even though I have the archive_interval in weewx.conf set to 120
> (seconds) the FTP of the files generated by weewx is occurring every 300
> seconds (5 minutes) -- which I confirmed from reviewing the log files.
> How can I get the FTP to execute every 120 seconds?
>
> FYI, weewx.conf for Standard Archive is
>
>
>
>
>
>
> *[StdArchive]archive_interval = 120record_generation = hardware
> loop_hilo = Truedata_binding = wx_binding*
>
> Should I change the record_generation to software?   Noting the Rainwise
> IP-100 is inserting records into the MySQL database tables every minute --
> which is what I want.
>
> Thanks in Advance for your guidance!
>
> -- Tim
>
> On Saturday, January 30, 2021 at 8:35:31 PM UTC-8 tim lambert wrote:
>
>> Thanks Gary for the insight and guidance.
>>
>>
>>
>>
>>
>> Sent from Mail  for
>> Windows 10
>>
>>
>>
>> *From: *gjr80
>> *Sent: *Saturday, January 30, 2021 7:58 PM
>> *To: *weewx-user
>> *Subject: *[weewx-user] Re: WEEWX-WD and Weewx 4.2 to 4.4
>>
>>
>>
>> Hi,
>>
>>
>>
>> I wouldn't be using WeeWX-WD from bitbucket, it has not been touched for
>> some years now. WeeWX-WD on github
>>  is more up to date, the
>> current version is v2.1.2 from November 2020. It should have no problems
>> running on WeeWX v4.x under python 2 or python3. The SteelSeries Weather
>> Gauges  have
>> directly supported WeeWX of v2.5.0 (of the SteelSeries Weather Gauges) or
>> for about six years, and there is now a WeeWX SteelSeries Gauges
>> extension  that
>> installs the necessary skin to support the SteelSeries Weather Gauges (this
>> is the preferred means of providing the SteelSeries Weather Gauges,
>> WeeWX-WD did support the SteelSeries Weather Gauges via the WD
>> customclientraw.txt but since the advent of direct WeeWX support and the
>> WeeWX extension the SteelSeries Weather Gauges support has been deprecated
>> in WeeWX-WD). You should find the WeeWX extension will work under WeeWX
>> v4.x and python2 or python3.
>>
>>
>>
>> I would suggest that you upgrade to WeeWX v4.4.0 and get WeeWX running to
>> your satisfaction before installing either WeeWX-WD v2.1.2 or the WeeWX
>> SteelSeries Weather Gauges extension (in whatever order suits). Once you
>> have the SteelSeries Weather Gauges extension running OK you can, if you
>> want, look at installing the Realtime gauge-data extension
>>  which will allow
>> the gauges to update on every loop packet rather than on each report cycle
>> (how often they will update will depend on how often your station emits
>> loop packets, for your Rainwise this should be up to every couple of
>> seconds).
>>
>>
>>
>> Gary
>>
>>
>>
>> On Sunday, 31 January 2021 at 13:15:24 UTC+10 tim lambert wrote:
>>
>> Gang,
>>
>>
>>
>> Currently running weewx 4.2 (will be upgrading in the next few days to
>> 4.4) on a Raspberry Pi 4 (32-bit OS) with a Rainwise MK-III and IP-100
>> providing station data -- everything has been working properly for several
>> weeks and is populating a remote MySQL DB.
>>
>>
>>
>> Once I upgrade weewx, I'd like to incorporate using Steel Gauges and
>> Saratoga Templates, hence my query:  Can I utilize the WEEWX-WD as outlined 
>> BitBucket
>> Weewx-WD ?
>>
>>
>>
>> The Steel Gauges and Saratoga Templates will be hosted on a remote,
>> public accessible server -- so I'll be sending the clientraw and testtag
>> files via FTP.
>>
>>
>>
>> Thanks in Advance!
>>
>>
>>
>> - Tim
>>
>> --
>> 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/gvReyZeqOJQ/unsubscribe.
>> To unsubscribe 

[weewx-user] Re: NOAA report with dust sensor

[bgra...@umw.edu]

Gary,
My upgrade to 4.4.0 was not a new install and I need to change manually to 
utf8. I made changes in skin.conf but must have missed something. My NOAA 
daily now shows:
TEMPERATURE (°F), RAIN (in), WIND SPEED (mph) 

old form with html_entities encoding was:
TEMPERATURE (F), RAIN (in), WIND SPEED (mph)

Is there something I need to delete and rebuild?

Thanks
BG



On Wednesday, February 3, 2021 at 1:53:47 AM UTC-5 gjr80 wrote:

> Just by way of background up until v4.3.0 WeeWX shipped with strict_ascii 
> encoding for NOAA reports. v4.4.0 changed that to utf8 but for new installs 
> only, upgrades or earlier versions need to be changed manually.
>
> Gary
>
> On Wednesday, 3 February 2021 at 16:27:31 UTC+10 calo@gmail.com wrote:
>
>> Hi Gary,
>>
>> thanks again. Works now.
>> [image: DustPM10.png]
>>
>> On Wednesday, February 3, 2021 at 7:18:43 AM UTC+1 Calo Geyer wrote:
>>
>>> Hi Gary,
>>>
>>> thanks. Yes, you are right. Got this in my skins.conf and it is even 
>>> written in the explanation. Will change and report back.
>>>
>>>
>>> [CheetahGenerator]
>>>
>>> # Possible encodings are 'html_entities', 'utf8', or 'strict_ascii'
>>> encoding = html_entities
>>>
>>> [[SummaryByMonth]]
>>> # Reports that summarize "by month"
>>> [[[NOAA_month]]]
>>> encoding = strict_ascii
>>> template = NOAA/NOAA-%Y-%m.txt.tmpl
>>>
>>> [[SummaryByYear]]
>>> # Reports that summarize "by year"
>>> [[[NOAA_year]]]
>>> encoding = strict_ascii
>>> template = NOAA/NOAA-%Y.txt.tmpl
>>>
>>> On Wednesday, February 3, 2021 at 7:11:51 AM UTC+1 gjr80 wrote:
>>>
 Hi,

 What encoding are you using for the NOAA format reports in your 
 skin.conf? If you have the old encoding = strict_ascii then no you won’t 
 see the mu character, you should see it though if you have encoding = utf8.

 Gary

 On Wednesday, 3 February 2021 at 16:00:13 UTC+10 calo@gmail.com 
 wrote:

> Hi, I added my SDS011 data (which I read-in using file-pile) however 
> the unit in the header is not shows as microgramm per cubic meter. I 
> changed the unit in units.py to see if it also is adapted in the report 
> and 
> was working however using the default pm10_0 unit shows as g/m
> This is my entry in .tmpl
> DUST PM10 ($unit.label.SDS011_PM10.strip())
>
>
>  [image: NOAA Dust PM10.png]
>
> Any idea?
>


-- 
You received this message because you are subscribed to the Google 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/e8c77f07-a140-4cd0-a5c4-23d80dc182f0n%40googlegroups.com.

[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent

[vince]

On Thursday, February 4, 2021 at 11:50:29 AM UTC-8 kk44...@gmail.com wrote:

> As I did not really know how to update an extension,
>

Just install the new one.
 

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

[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent

[Karen K]

I am looking for the thumb-up smiley.

As I did not really know how to update an extension, I uninstalled the old 
version first. After that I installed the version 2.0.0-rc04. That process 
removed part of the configuration data, but no problem, there was a backup.

Now I see values every archive interval as expected. I checked that for 
about half an hour by now. There are values in the loop record, when the 
MQTT messages arrive, and additionally in every archive record. No error 
messages at all.

Do you need any debugging output? I did not switch on debug logging as 
there were no errors.
bell...@gmail.com schrieb am Mittwoch, 3. Februar 2021 um 19:00:04 UTC+1:

> Karen,
> Without doing a deep analysis on your log, I can't explain what you are 
> seeing. I am pretty sure that the problem is a mismatch of the cache key, 
> resulting in nothing being cached. I have created a release with an update 
> that should fix this. It can be found here, 
> https://github.com/bellrichm/WeeWX-MQTTSubscribe/releases/tag/v2.0.0-rc04 Let 
> me know how it goes.
> Thanks for your help debugging this. - rich
>
> On Tuesday, 2 February 2021 at 09:29:46 UTC-5 kk44...@gmail.com wrote:
>
>> I looked at it again, and I think, I found something. 
>>
>> This is a list of the archive records, and whether the MQTT data are 
>> included or not:
>>
>> 15:15:14 included
>> 15:10  missing
>> 15:05:16 included
>> 15:00:14 included
>> 14:55   missing
>> 14:50:16 included
>> 15:45:14 included
>> 15:40   missing
>> 14:35:16 included
>> 14:30:14 included
>> 14:25  missing
>> 14:20:16 included
>> 14:15:14 included
>> 14:10  missing
>> 14:05:16 included
>> 14:00:16 included
>> 13:55  missing
>> 13:50:16 included
>> 13:45:16 included
>> 13:40  missing
>> 13:35:16 included
>>
>> The MQTT message is published within the minute after a full quarter of 
>> the hour.
>>
>> So maybe, it is cached for 10 minutes, only, irrespective of the setting. 
>> Does that make sense to you?
>>
>> Karen K schrieb am Montag, 1. Februar 2021 um 21:42:33 UTC+1:
>>
>>> I looked for all messages that contain self.cached_fields. 
>>>
>>> /var/log/syslog.2.gz:Jan 30 16:51:45 LokalWiki weewx[1003818] DEBUG 
>>> user.MQTTSubscribe: (Service) TopicManager self.cached_fields is {}
>>> /var/log/syslog.2.gz:Jan 30 17:07:40 LokalWiki weewx[1004756] DEBUG 
>>> user.MQTTSubscribe: (Service) TopicManager self.cached_fields is {} 
>>> /var/log/syslog.2.gz:Jan 30 17:32:18 LokalWiki weewx[1005876] DEBUG 
>>> user.MQTTSubscribe: (Service) TopicManager self.cached_fields is {} 
>>> /var/log/syslog:Feb 1 21:15:42 LokalWiki weewx[1121713] DEBUG 
>>> user.MQTTSubscribe: (Service) TopicManager self.cached_fields is 
>>> {'pegel/566055/W_cm': {'expires_after': 4000.0}, 'pegel/566055/Q': 
>>> {'expires_after': 4000.0}, 'pegel/567470/W_cm': {'expires_after': 4000.0}, 
>>> 'pegel/567470/Q': {'expires_after': 4000.0}}
>>>
>>> I guess the only difference in configuration is setting that 
>>> use_topic_as_fieldname option.
>>>
>>> Much more occurences are for archive_field_cache_dict is None:
>>>
>>> /var/log/syslog:Feb 1 17:11:37 LokalWiki weewx[752] INFO 
>>> user.MQTTSubscribe: (Service) archive_field_cache_dict is None 
>>> /var/log/syslog:Feb 1 17:57:17 LokalWiki weewx[1113838] INFO 
>>> user.MQTTSubscribe: (Service) archive_field_cache_dict is None 
>>> /var/log/syslog:Feb 1 21:15:42 LokalWiki weewx[1121713] INFO 
>>> user.MQTTSubscribe: (Service) archive_field_cache_dict is None 
>>> /var/log/syslog.1:Jan 31 18:51:39 LokalWiki weewx[1062223] INFO 
>>> user.MQTTSubscribe: (Service) archive_field_cache_dict is None 
>>> /var/log/syslog.2.gz:Jan 30 11:41:20 LokalWiki weewx[991980] INFO 
>>> user.MQTTSubscribe: (Service) archive_field_cache_dict is None 
>>> /var/log/syslog.2.gz:Jan 30 16:22:32 LokalWiki weewx[1002371] INFO 
>>> user.MQTTSubscribe: (Service) archive_field_cache_dict is None 
>>> /var/log/syslog.2.gz:Jan 30 16:37:01 LokalWiki weewx[1002967] INFO 
>>> user.MQTTSubscribe: (Service) archive_field_cache_dict is None 
>>> /var/log/syslog.2.gz:Jan 30 16:48:04 LokalWiki weewx[1003591] INFO 
>>> user.MQTTSubscribe: (Service) archive_field_cache_dict is None 
>>> /var/log/syslog.2.gz:Jan 30 16:51:45 LokalWiki weewx[1003818] INFO 
>>> user.MQTTSubscribe: (Service) archive_field_cache_dict is None 
>>> /var/log/syslog.2.gz:Jan 30 16:52:35 LokalWiki weewx[1003948] INFO 
>>> user.MQTTSubscribe: (Service) archive_field_cache_dict is None 
>>> /var/log/syslog.2.gz:Jan 30 16:56:06 LokalWiki weewx[1004173] INFO 
>>> user.MQTTSubscribe: (Service) archive_field_cache_dict is None 
>>> /var/log/syslog.2.gz:Jan 30 17:01:36 LokalWiki weewx[1004468] INFO 
>>> user.MQTTSubscribe: (Service) archive_field_cache_dict is None 
>>> /var/log/syslog.2.gz:Jan 30 17:07:40 LokalWiki weewx[1004756] INFO 
>>> user.MQTTSubscribe: (Service) archive_field_cache_dict is None 
>>> /var/log/syslog.2.gz:Jan 30 17:09:27 LokalWiki weewx[1004999] INFO 
>>> user.MQTTSubscribe: (Service) 

Re: [weewx-user] Bootstrap skin update preview

[Δημήτρης Βήχος]

very good work! beautifull skin. looks geat on chromium 88 with arch linux

Στις Πέμπτη, 4 Φεβρουαρίου 2021 στις 5:24:30 μ.μ. UTC+2, ο χρήστης 
michael.k...@gmx.at έγραψε:

> I didn't change anything in the meantime, so I don't know what caused the 
> initial error. "Looks great" => thank you very much, hearing this from Mr. 
> weewx himself, really is delightful :)
>
> I forget to mention: The charts and gauges are Apache eCharts. Almost 
> infinite possibilities!
> tke...@gmail.com schrieb am Donnerstag, 4. Februar 2021 um 13:33:20 UTC+1:
>
>> Don't know what happened, but now it works for me with no errors.
>>
>> Looks great!
>>
>> On Wed, Feb 3, 2021 at 8:48 PM michael.k...@gmx.at  
>> wrote:
>>
>>> Hello Tom,
>>>
>>> The error with the /favicon.ico is a simple one: there is no such file. 
>>> The other errors I couldn't reproduce, even trying with different browser 
>>> on different computers and phones. Isn't weewxData.js there, when you try 
>>> to load it? It's referenced on line 144 of the HTML.
>>> What browser on what system are you using?
>>> I got it working with Windows: Firefox, Brave, Edge, Chrome, Raspbian 
>>> with Chromium, Android 10 Chrome, Brave, Firefox. Android 7.0 Chrome. I've 
>>> encountered some Problems with the connection to the MQTT broker while 
>>> using the companies VPN and and some weird rendering of the gauges an 
>>> images using the edge version 44, pre-chromium) browser that is installed 
>>> at the companies computer and no displaying of the gauges and charts with 
>>> the internet explorer (an there are no plans to get this working)
>>> tke...@gmail.com schrieb am Mittwoch, 3. Februar 2021 um 23:57:25 UTC+1:
>>>
 Hi, Michael.

 I got several errors when I tried to see your live version:

 Uncaught SyntaxError: Unexpected end of input
 site.js:1 Uncaught ReferenceError: weewxData is not defined
 at site.js:1
 gauges.js:3 Uncaught ReferenceError: weewxData is not defined
 at gauges.js:3
 charts.js:2 Uncaught ReferenceError: weewxData is not defined
 at charts.js:2
 /favicon.ico:1 Failed to load resource: the server responded with a 
 status of 404 (Not Found)


 On Wed, Feb 3, 2021 at 1:12 PM michael.k...@gmx.at  
 wrote:

> A couple of weeks ago, I asked Nick, the author of the bootstrap skin, 
> if he could help me taking his skin, that I am very fond of, to the next 
> level. As a first step we developed an optional live view with browser 
> rendered gauges and charts, using MQTT for the almost-real-time 
> rendering. 
> Everything is still under heavy development, but still, I think time has 
> come to show a first preview. Whoever wants to check it out, this is the 
> development branch:
>
> https://github.com/brewster76/fuzzy-archer/tree/liveCharts
>
> Be careful, not production ready!
>
> For those who want to see it in action:
>
> https://www.kainzbauer.net/weather/Rif-Tempest/live.html
>
> The Weatherflow Tempest is really great for such fancy almost-realtime 
> sites with it's 3 second wind/windDir update interval.
>
> -- 
> You received this message because you are subscribed 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/bd8b0eb8-f803-43e9-9f7b-077dc4b79f1dn%40googlegroups.com
>  
> 
> .
>
 -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/9ad6d9d4-38d8-4503-ba91-a7adb5652c13n%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/566f2451-f932-4eba-b8fb-3098531519c9n%40googlegroups.com.

[weewx-user] Re: FTP Upload

[Renato Brigger]

Hallo Michael.

Danke schon mal für die Hilfe. Hat geklappt. Werden dann nächstens 
versuchen meine Wetterstation WH2600 einzubinden. 
Könnte wahrscheinlich auch nicht so einfach sein, da diese an einem Router 
hängt und kein USB Anschluss hat.
Hast du eventuell einen Tipp welchen Treiber ich da installieren sollte?
Danke.

Hi Michael. Thank you in advance for the help. It worked. Will try to 
integrate my weather station WH2600 next. Could probably not be that easy 
either, since it is connected to a router and has no USB port. Do you have 
a tip which driver I should install there? Thank you. 
michael.k...@gmx.at schrieb am Donnerstag, 4. Februar 2021 um 17:47:12 
UTC+1:

> Ich gehe davon aus, das bei dir dann  
> path = /html# The destination directory, e.g., /weather  
> funktionieren müsste
>
> Please try 
> path = /html# The destination directory, e.g., /weather
>
>
> renato...@gmail.com schrieb am Donnerstag, 4. Februar 2021 um 16:43:07 
> UTC+1:
>
>> Hallo Michael
>>
>> Ich habe gerade versucht mit dem FTP Programm mir die Schreibrechte zu 
>> geben, hat aber leider nicht funktioniert. Schreibrechte kann ich erst im 
>> Unterodner \html geben. Sollte ich somit die config Position  " path = / 
>> " auf "path = /html" umstellen? 
>>
>> michael.k...@gmx.at schrieb am Donnerstag, 4. Februar 2021 um 16:18:44 
>> UTC+1:
>>
>>> Hallo Renato,
>>>
>>> der FTP-Benutzer hat auf dem Ordner, wo die Dateien hochgeladen werden 
>>> sollen, keine Schreibrechte "Permission Denied" => "Zugriff verweigert". 
>>> Wer hat dir den Ordner erstellt bzw. den Benutzer erstellt? Derjenige 
>>> müsste dir für den Benutzer und den Ordner Schreibrechte geben.
>>>
>>> Most likely the FTP-user has noch write permission to the upload Folder.
>>>
>>> renato...@gmail.com schrieb am Donnerstag, 4. Februar 2021 um 16:13:09 
>>> UTC+1:
>>>
 Hallo zusammen.
 Ich bin ein Anfänger mit Linux.
 Ich habe erfolgreich Weewx auf meine RasbeeryPi installiert. Es 
 funtioniert auch mit dem Simulator und dem Apache Server. Webseite wird 
 angezeit.
 Leider gelingt es mir nicht FTP zum laufen zu bringen. Ich habe den 
 Auschnitt der Config sowie das Log angehängt.


 Translate with Google:

 Hello everybody. I am a beginner with Linux. I have successfully 
 installed Weewx on my RasbeeryPi. It also works with the simulator and 
 the Apache server. Website is displayed. Unfortunately, I am unable to 
 get FTP running. I have attached the excerpt from the config and the 
 log.

 Thanks. Renato



-- 
You received this message because you are subscribed to the Google 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/6d2c9630-17b7-4a9d-9f83-ae3eaca732f4n%40googlegroups.com.

[weewx-user] Re: Can I subscribe to weatherdata?

[michael.k...@gmx.at]

"With my WS-2810 this would be about every 3 seconds" => make that 30 
seconds :) 

michael.k...@gmx.at schrieb am Donnerstag, 4. Februar 2021 um 17:52:47 
UTC+1:

> You can install https://github.com/weewx/weewx/wiki/mqtt and subscribe to 
> e.g. weather/loop (or whatever your topic is) and extract windSpeed. You 
> will receive windSpeed every time your hardware send loop data to weewx. 
> With my WS-2810 this would be about every 3 seconds, my weatherflow tempest 
> provides windSpeed every 3 seconds. Your switching device need to be mqtt 
> enabled, you need a broker as well.
> Other than that there are several other ways to let weewx do something 
> when specific loop data arrives.
> rainer@gmail.com schrieb am Donnerstag, 4. Februar 2021 um 17:35:31 
> UTC+1:
>
>> Hi,
>> I want that in a certain weather condition, e.g. wind > 50 km/h I switch 
>> a relais to turn something on or off. To write the code for switching the 
>> realais, I have everything I need. But this code needs as an input the wind 
>> speed. Can my program somehow subscribe to Weewx and get the wind data 
>> constantly?
>> Thanks, Rainer
>>
>

-- 
You received this message because you are subscribed to the Google 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/b1c60766-429d-4fb2-8444-e26e2e42c9e8n%40googlegroups.com.

[weewx-user] Re: Can I subscribe to weatherdata?

[Rainer Halanek]

Thanks for the quick and very helpful answers!

Cheers, Rainer

On Thursday, February 4, 2021 at 5:52:47 PM UTC+1 michael.k...@gmx.at wrote:

> You can install https://github.com/weewx/weewx/wiki/mqtt and subscribe to 
> e.g. weather/loop (or whatever your topic is) and extract windSpeed. You 
> will receive windSpeed every time your hardware send loop data to weewx. 
> With my WS-2810 this would be about every 3 seconds, my weatherflow tempest 
> provides windSpeed every 3 seconds. Your switching device need to be mqtt 
> enabled, you need a broker as well.
> Other than that there are several other ways to let weewx do something 
> when specific loop data arrives.
> rainer@gmail.com schrieb am Donnerstag, 4. Februar 2021 um 17:35:31 
> UTC+1:
>
>> Hi,
>> I want that in a certain weather condition, e.g. wind > 50 km/h I switch 
>> a relais to turn something on or off. To write the code for switching the 
>> realais, I have everything I need. But this code needs as an input the wind 
>> speed. Can my program somehow subscribe to Weewx and get the wind data 
>> constantly?
>> Thanks, Rainer
>>
>

-- 
You received this message because you are subscribed to the Google 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/46cab94b-a69f-4371-ac88-5880e0bde58dn%40googlegroups.com.

Re: [weewx-user] Re: WEEWX-WD and Weewx 4.2 to 4.4

[tim lambert]

Hi Gary,

I'm taking things in baby steps. 

Earlier this week I successfully upgraded from weewx 4.2 to weewx 4.4 
(which was surprisingly easy with how weewx addresses upgrades).   
Everything is stable, so I'm moving onward to the next steps.

I've taken the route to implement WeeWX SteelSeries Weather Gauges 
extension (not real-time yet) and WeeWX-WD v2.1.2 -- everything installed 
and I can see the SteelGauge info on my remotely hosted website, as well as 
see the clientraw.text and other key files for Saratoga Templates on the 
remotely hosted server.   

However, even though I have the archive_interval in weewx.conf set to 120 
(seconds) the FTP of the files generated by weewx is occurring every 300 
seconds (5 minutes) -- which I confirmed from reviewing the log files.   
How can I get the FTP to execute every 120 seconds?

FYI, weewx.conf for Standard Archive is






*[StdArchive]archive_interval = 120record_generation = hardware
loop_hilo = Truedata_binding = wx_binding*

Should I change the record_generation to software?   Noting the Rainwise 
IP-100 is inserting records into the MySQL database tables every minute -- 
which is what I want.

Thanks in Advance for your guidance!

-- Tim

On Saturday, January 30, 2021 at 8:35:31 PM UTC-8 tim lambert wrote:

> Thanks Gary for the insight and guidance.
>
>  
>
>  
>
> Sent from Mail  for 
> Windows 10
>
>  
>
> *From: *gjr80
> *Sent: *Saturday, January 30, 2021 7:58 PM
> *To: *weewx-user
> *Subject: *[weewx-user] Re: WEEWX-WD and Weewx 4.2 to 4.4
>
>  
>
> Hi,
>
>  
>
> I wouldn't be using WeeWX-WD from bitbucket, it has not been touched for 
> some years now. WeeWX-WD on github 
>  is more up to date, the current 
> version is v2.1.2 from November 2020. It should have no problems running on 
> WeeWX v4.x under python 2 or python3. The SteelSeries Weather Gauges 
>  have directly 
> supported WeeWX of v2.5.0 (of the SteelSeries Weather Gauges) or for about 
> six years, and there is now a WeeWX SteelSeries Gauges extension 
>  that installs the 
> necessary skin to support the SteelSeries Weather Gauges (this is the 
> preferred means of providing the SteelSeries Weather Gauges, WeeWX-WD did 
> support the SteelSeries Weather Gauges via the WD customclientraw.txt but 
> since the advent of direct WeeWX support and the WeeWX extension the 
> SteelSeries Weather Gauges support has been deprecated in WeeWX-WD). You 
> should find the WeeWX extension will work under WeeWX v4.x and python2 or 
> python3.
>
>  
>
> I would suggest that you upgrade to WeeWX v4.4.0 and get WeeWX running to 
> your satisfaction before installing either WeeWX-WD v2.1.2 or the WeeWX 
> SteelSeries Weather Gauges extension (in whatever order suits). Once you 
> have the SteelSeries Weather Gauges extension running OK you can, if you 
> want, look at installing the Realtime gauge-data extension 
>  which will allow the 
> gauges to update on every loop packet rather than on each report cycle (how 
> often they will update will depend on how often your station emits loop 
> packets, for your Rainwise this should be up to every couple of seconds).
>
>  
>
> Gary
>
>  
>
> On Sunday, 31 January 2021 at 13:15:24 UTC+10 tim lambert wrote:
>
> Gang,
>
>  
>
> Currently running weewx 4.2 (will be upgrading in the next few days to 
> 4.4) on a Raspberry Pi 4 (32-bit OS) with a Rainwise MK-III and IP-100 
> providing station data -- everything has been working properly for several 
> weeks and is populating a remote MySQL DB.
>
>  
>
> Once I upgrade weewx, I'd like to incorporate using Steel Gauges and 
> Saratoga Templates, hence my query:  Can I utilize the WEEWX-WD as outlined 
> BitBucket 
> Weewx-WD ?
>
>  
>
> The Steel Gauges and Saratoga Templates will be hosted on a remote, public 
> accessible server -- so I'll be sending the clientraw and testtag files via 
> FTP.
>
>  
>
> Thanks in Advance!
>
>  
>
> - Tim
>
> -- 
> 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/gvReyZeqOJQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/6942d0aa-94bf-46e9-bb56-8232a425f95fn%40googlegroups.com
>  
> 
> .
>
>  
>

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

[weewx-user] Re: Can I subscribe to weatherdata?

[michael.k...@gmx.at]

You can install https://github.com/weewx/weewx/wiki/mqtt and subscribe to 
e.g. weather/loop (or whatever your topic is) and extract windSpeed. You 
will receive windSpeed every time your hardware send loop data to weewx. 
With my WS-2810 this would be about every 3 seconds, my weatherflow tempest 
provides windSpeed every 3 seconds. Your switching device need to be mqtt 
enabled, you need a broker as well.
Other than that there are several other ways to let weewx do something when 
specific loop data arrives.
rainer@gmail.com schrieb am Donnerstag, 4. Februar 2021 um 17:35:31 
UTC+1:

> Hi,
> I want that in a certain weather condition, e.g. wind > 50 km/h I switch a 
> relais to turn something on or off. To write the code for switching the 
> realais, I have everything I need. But this code needs as an input the wind 
> speed. Can my program somehow subscribe to Weewx and get the wind data 
> constantly?
> Thanks, Rainer
>

-- 
You received this message because you are subscribed to the Google 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/731b7cb6-cd65-41b1-8af0-02bb0914f77cn%40googlegroups.com.

[weewx-user] Re: Can I subscribe to weatherdata?

[vince]

Output your data to MQTT and have your code subscribe to MQTT for that 
topic.

On Thursday, February 4, 2021 at 8:35:31 AM UTC-8 rainer@gmail.com 
wrote:

> Hi,
> I want that in a certain weather condition, e.g. wind > 50 km/h I switch a 
> relais to turn something on or off. To write the code for switching the 
> realais, I have everything I need. But this code needs as an input the wind 
> speed. Can my program somehow subscribe to Weewx and get the wind data 
> constantly?
> Thanks, Rainer
>

-- 
You received this message because you are subscribed to the Google 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/20ac5eaa-202f-4f1d-9a7d-6a6cf9270b02n%40googlegroups.com.

[weewx-user] Re: FTP Upload

[michael.k...@gmx.at]

Ich gehe davon aus, das bei dir dann  
path = /html# The destination directory, e.g., /weather  
funktionieren müsste

Please try 
path = /html# The destination directory, e.g., /weather


renato...@gmail.com schrieb am Donnerstag, 4. Februar 2021 um 16:43:07 
UTC+1:

> Hallo Michael
>
> Ich habe gerade versucht mit dem FTP Programm mir die Schreibrechte zu 
> geben, hat aber leider nicht funktioniert. Schreibrechte kann ich erst im 
> Unterodner \html geben. Sollte ich somit die config Position  " path = / 
> " auf "path = /html" umstellen? 
>
> michael.k...@gmx.at schrieb am Donnerstag, 4. Februar 2021 um 16:18:44 
> UTC+1:
>
>> Hallo Renato,
>>
>> der FTP-Benutzer hat auf dem Ordner, wo die Dateien hochgeladen werden 
>> sollen, keine Schreibrechte "Permission Denied" => "Zugriff verweigert". 
>> Wer hat dir den Ordner erstellt bzw. den Benutzer erstellt? Derjenige 
>> müsste dir für den Benutzer und den Ordner Schreibrechte geben.
>>
>> Most likely the FTP-user has noch write permission to the upload Folder.
>>
>> renato...@gmail.com schrieb am Donnerstag, 4. Februar 2021 um 16:13:09 
>> UTC+1:
>>
>>> Hallo zusammen.
>>> Ich bin ein Anfänger mit Linux.
>>> Ich habe erfolgreich Weewx auf meine RasbeeryPi installiert. Es 
>>> funtioniert auch mit dem Simulator und dem Apache Server. Webseite wird 
>>> angezeit.
>>> Leider gelingt es mir nicht FTP zum laufen zu bringen. Ich habe den 
>>> Auschnitt der Config sowie das Log angehängt.
>>>
>>>
>>> Translate with Google:
>>>
>>> Hello everybody. I am a beginner with Linux. I have successfully 
>>> installed Weewx on my RasbeeryPi. It also works with the simulator and 
>>> the Apache server. Website is displayed. Unfortunately, I am unable to 
>>> get FTP running. I have attached the excerpt from the config and the 
>>> log.
>>>
>>> Thanks. Renato
>>>
>>>

-- 
You received this message because you are subscribed to the Google 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/33b865b2-65dc-47e0-9168-e395f39283a5n%40googlegroups.com.

[weewx-user] Can I subscribe to weatherdata?

[Rainer Halanek]

Hi,
I want that in a certain weather condition, e.g. wind > 50 km/h I switch a 
relais to turn something on or off. To write the code for switching the 
realais, I have everything I need. But this code needs as an input the wind 
speed. Can my program somehow subscribe to Weewx and get the wind data 
constantly?
Thanks, Rainer

-- 
You received this message because you are subscribed to the Google 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/32322be3-1853-4fd4-b45f-3c073df9ec37n%40googlegroups.com.

[weewx-user] Re: FTP Upload

[Renato Brigger]

Hallo Michael

Ich habe gerade versucht mit dem FTP Programm mir die Schreibrechte zu 
geben, hat aber leider nicht funktioniert. Schreibrechte kann ich erst im 
Unterodner \html geben. Sollte ich somit die config Position  " path = / " 
auf "path = /html" umstellen? 

michael.k...@gmx.at schrieb am Donnerstag, 4. Februar 2021 um 16:18:44 
UTC+1:

> Hallo Renato,
>
> der FTP-Benutzer hat auf dem Ordner, wo die Dateien hochgeladen werden 
> sollen, keine Schreibrechte "Permission Denied" => "Zugriff verweigert". 
> Wer hat dir den Ordner erstellt bzw. den Benutzer erstellt? Derjenige 
> müsste dir für den Benutzer und den Ordner Schreibrechte geben.
>
> Most likely the FTP-user has noch write permission to the upload Folder.
>
> renato...@gmail.com schrieb am Donnerstag, 4. Februar 2021 um 16:13:09 
> UTC+1:
>
>> Hallo zusammen.
>> Ich bin ein Anfänger mit Linux.
>> Ich habe erfolgreich Weewx auf meine RasbeeryPi installiert. Es 
>> funtioniert auch mit dem Simulator und dem Apache Server. Webseite wird 
>> angezeit.
>> Leider gelingt es mir nicht FTP zum laufen zu bringen. Ich habe den 
>> Auschnitt der Config sowie das Log angehängt.
>>
>>
>> Translate with Google:
>>
>> Hello everybody. I am a beginner with Linux. I have successfully 
>> installed Weewx on my RasbeeryPi. It also works with the simulator and 
>> the Apache server. Website is displayed. Unfortunately, I am unable to 
>> get FTP running. I have attached the excerpt from the config and the log.
>>
>> Thanks. Renato
>>
>>

-- 
You received this message because you are subscribed to the Google 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/b75d3498-16aa-4ef6-80c4-e5b5a16b0d5bn%40googlegroups.com.

Re: [weewx-user] Bootstrap skin update preview

[michael.k...@gmx.at]

I didn't change anything in the meantime, so I don't know what caused the 
initial error. "Looks great" => thank you very much, hearing this from Mr. 
weewx himself, really is delightful :)

I forget to mention: The charts and gauges are Apache eCharts. Almost 
infinite possibilities!
tke...@gmail.com schrieb am Donnerstag, 4. Februar 2021 um 13:33:20 UTC+1:

> Don't know what happened, but now it works for me with no errors.
>
> Looks great!
>
> On Wed, Feb 3, 2021 at 8:48 PM michael.k...@gmx.at  
> wrote:
>
>> Hello Tom,
>>
>> The error with the /favicon.ico is a simple one: there is no such file. 
>> The other errors I couldn't reproduce, even trying with different browser 
>> on different computers and phones. Isn't weewxData.js there, when you try 
>> to load it? It's referenced on line 144 of the HTML.
>> What browser on what system are you using?
>> I got it working with Windows: Firefox, Brave, Edge, Chrome, Raspbian 
>> with Chromium, Android 10 Chrome, Brave, Firefox. Android 7.0 Chrome. I've 
>> encountered some Problems with the connection to the MQTT broker while 
>> using the companies VPN and and some weird rendering of the gauges an 
>> images using the edge version 44, pre-chromium) browser that is installed 
>> at the companies computer and no displaying of the gauges and charts with 
>> the internet explorer (an there are no plans to get this working)
>> tke...@gmail.com schrieb am Mittwoch, 3. Februar 2021 um 23:57:25 UTC+1:
>>
>>> Hi, Michael.
>>>
>>> I got several errors when I tried to see your live version:
>>>
>>> Uncaught SyntaxError: Unexpected end of input
>>> site.js:1 Uncaught ReferenceError: weewxData is not defined
>>> at site.js:1
>>> gauges.js:3 Uncaught ReferenceError: weewxData is not defined
>>> at gauges.js:3
>>> charts.js:2 Uncaught ReferenceError: weewxData is not defined
>>> at charts.js:2
>>> /favicon.ico:1 Failed to load resource: the server responded with a 
>>> status of 404 (Not Found)
>>>
>>>
>>> On Wed, Feb 3, 2021 at 1:12 PM michael.k...@gmx.at  
>>> wrote:
>>>
 A couple of weeks ago, I asked Nick, the author of the bootstrap skin, 
 if he could help me taking his skin, that I am very fond of, to the next 
 level. As a first step we developed an optional live view with browser 
 rendered gauges and charts, using MQTT for the almost-real-time rendering. 
 Everything is still under heavy development, but still, I think time has 
 come to show a first preview. Whoever wants to check it out, this is the 
 development branch:

 https://github.com/brewster76/fuzzy-archer/tree/liveCharts

 Be careful, not production ready!

 For those who want to see it in action:

 https://www.kainzbauer.net/weather/Rif-Tempest/live.html

 The Weatherflow Tempest is really great for such fancy almost-realtime 
 sites with it's 3 second wind/windDir update interval.

 -- 
 You received this message because you are subscribed 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/bd8b0eb8-f803-43e9-9f7b-077dc4b79f1dn%40googlegroups.com
  
 
 .

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/9ad6d9d4-38d8-4503-ba91-a7adb5652c13n%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/53e3df75-15e3-49fe-9310-7dc9efff0a2dn%40googlegroups.com.

[weewx-user] Re: FTP Upload

[michael.k...@gmx.at]

Hallo Renato,

der FTP-Benutzer hat auf dem Ordner, wo die Dateien hochgeladen werden 
sollen, keine Schreibrechte "Permission Denied" => "Zugriff verweigert". 
Wer hat dir den Ordner erstellt bzw. den Benutzer erstellt? Derjenige 
müsste dir für den Benutzer und den Ordner Schreibrechte geben.

Most likely the FTP-user has noch write permission to the upload Folder.

renato...@gmail.com schrieb am Donnerstag, 4. Februar 2021 um 16:13:09 
UTC+1:

> Hallo zusammen.
> Ich bin ein Anfänger mit Linux.
> Ich habe erfolgreich Weewx auf meine RasbeeryPi installiert. Es 
> funtioniert auch mit dem Simulator und dem Apache Server. Webseite wird 
> angezeit.
> Leider gelingt es mir nicht FTP zum laufen zu bringen. Ich habe den 
> Auschnitt der Config sowie das Log angehängt.
>
>
> Translate with Google:
>
> Hello everybody. I am a beginner with Linux. I have successfully 
> installed Weewx on my RasbeeryPi. It also works with the simulator and 
> the Apache server. Website is displayed. Unfortunately, I am unable to 
> get FTP running. I have attached the excerpt from the config and the log.
>
> Thanks. Renato
>
>

-- 
You received this message because you are subscribed to the Google 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/b3d13453-6a87-4dcb-9805-bb8c8f428c78n%40googlegroups.com.

[weewx-user] FTP Upload

[Renato Brigger]

Hallo zusammen.
Ich bin ein Anfänger mit Linux.
Ich habe erfolgreich Weewx auf meine RasbeeryPi installiert. Es funtioniert 
auch mit dem Simulator und dem Apache Server. Webseite wird angezeit.
Leider gelingt es mir nicht FTP zum laufen zu bringen. Ich habe den 
Auschnitt der Config sowie das Log angehängt.


Translate with Google:

Hello everybody. I am a beginner with Linux. I have successfully installed 
Weewx on my RasbeeryPi. It also works with the simulator and the Apache 
server. Website is displayed. Unfortunately, I am unable to get FTP running. I 
have attached the excerpt from the config and the log.

Thanks. Renato

-- 
You received this message because you are subscribed to the Google 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/ed4180c1-17a7-437a-8eda-00225693b347n%40googlegroups.com.
Feb  4 11:30:16 raspberrypi weewx[17225] INFO weewx.manager: Added record 
2021-02-04 11:30:00 GMT (1612438200) to database 'weewx.sdb'
Feb  4 11:30:16 raspberrypi weewx[17225] INFO weewx.manager: Added record 
2021-02-04 11:30:00 GMT (1612438200) to daily summary in 'weewx.sdb'
Feb  4 11:30:18 raspberrypi weewx[17225] INFO weewx.cheetahgenerator: Generated 
8 files for report SeasonsReport in 1.77 seconds
Feb  4 11:30:18 raspberrypi weewx[17225] INFO weewx.imagegenerator: Generated 
15 images for report SeasonsReport in 0.56 seconds
Feb  4 11:30:18 raspberrypi weewx[17225] INFO weewx.reportengine: Copied 5 
files to /var/www/html/weewx
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weeutil.ftpupload: Failed 
uploading /var/www/html/weewx/yearbarometer.png to server login-75.hoststar.ch. 
Reason: '550 /yearbarometer.png: Permission denied'
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine: 
ftpgenerator: (0): caught exception '': 550 
/yearbarometer.png: Permission denied
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
 Traceback (most recent call last):
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
   File "/usr/share/weewx/weewx/reportengine.py", line 331, in run
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
 n = ftp_data.run()
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
   File "/usr/share/weewx/weeutil/ftpupload.py", line 163, in run
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
 ftp_server.storbinary(stor_cmd, fd)
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
   File "/usr/lib/python3.7/ftplib.py", line 504, in storbinary
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
 with self.transfercmd(cmd, rest) as conn:
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
   File "/usr/lib/python3.7/ftplib.py", line 399, in transfercmd
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
 return self.ntransfercmd(cmd, rest)[0]
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
   File "/usr/lib/python3.7/ftplib.py", line 365, in ntransfercmd
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
 resp = self.sendcmd(cmd)
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
   File "/usr/lib/python3.7/ftplib.py", line 273, in sendcmd
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
 return self.getresp()
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
   File "/usr/lib/python3.7/ftplib.py", line 246, in getresp
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
 raise error_perm(resp)
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
 ftplib.error_perm: 550 /yearbarometer.png: Permission denied
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weeutil.ftpupload: Failed 
uploading /var/www/html/weewx/yearbarometer.png to server login-75.hoststar.ch. 
Reason: '550 /yearbarometer.png: Permission denied'
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine: 
ftpgenerator: (1): caught exception '': 550 
/yearbarometer.png: Permission denied
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
 Traceback (most recent call last):
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
   File "/usr/share/weewx/weewx/reportengine.py", line 331, in run
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
 n = ftp_data.run()
Feb  4 11:30:19 raspberrypi weewx[17225] ERROR weewx.reportengine:  
   File "/usr/share/weewx/weeutil/ftpupload.py", line 163, in run
Feb  4 11:30:19 raspberrypi 

[weewx-user] Graph not update

[ginfo...@gmail.com]

[image: Schermata 2021-02-04 alle 15.35.30.png]Hello and congratulations on 
this fantastic forum.
My weather station is a Davis Vantage Vue and updates regularly.
I have always had problems with the graphics, however, they do not update 
for a long time and sometimes I have to clear the cache.
How can I solve?
Thank you

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

Re: [weewx-user] Version 4.4.0

[Karen K]

Meanwhile I would add, that the update was without problems in my case 
(Ubuntu apt-get upgrade). I use Belchertown skin and some additional 
uploaders.

Vetti52 schrieb am Donnerstag, 4. Februar 2021 um 11:04:43 UTC+1:

> Hi,
> maybe a new thread would be helpful, because the issue is/was very special 
> and might not be a problem with version 4.4.0:
>
> After I realized, that weewx could be run manually, I was inspecting, what 
> was the difference. I had updated to version 4.4.0 and also had an update 
> for my Zigbee device driver (deCONZ). Then I had to reboot the Raspberry Pi 
> and after that the error occured. Finally I realized, that, the 
> /etc/init.d/weewx 
> start failed, with code=exited but no success. I misinterpreted this as 
> that weewx was not running, since there were no syslog entries at all. 
> Repeating to start weewx using the previous interceptor driver did not work 
> either. So I decided to let it run with gw1000 driver, but started it 
> manually with sudo weewxd /etc/weewx/weewx.conf >nul &.  This was 
> successful, and went to sleep
> Today I decided to look at this issue again and, instead of killing the 
> manually started weexd properly, I accidently used /etc/init.d/weewx stop, 
> which indeed stopped weewx, but the manually started weewxd continued. 
> After I stopped this too, I realized, that weewx had in fact been started 
> autmatically after reboot, but got stuck, as you say, because of the gw1000 
> driver. What I did not expect, is, that weewx then did not exit. Any 
> additional starting command therefore failed. I was cind of silly, not to 
> look at that, sorry. After stopping the hanging weewx, I could start weewx 
> as expected, and now it works without any issues. Maybe, it would be better 
> not to start weewx with its init.d script, but with systemctl using a 
> separate weewx.service file which should contain a stanza like
>
> [Unit]
> After=network-online.target
>
> that would avoid to start weewx before network is up, which seems to be a 
> crucial step for gw1000. But this should be another thread, I think.
>
> Thanks 
> Peter
> gjr80 schrieb am Mittwoch, 3. Februar 2021 um 20:33:21 UTC+1:
>
>> Ok, can you please set debug=1, restart WeeWX as a daemon and post in a 
>> new thread the log through until the failure occurs.
>>
>> Gary
>>
>> On Thursday, 4 February 2021 at 05:28:00 UTC+10 Vetti52 wrote:
>>
>>> just to narrow down my problem:
>>>
>>> When starting manually 
>>>  weewxd /etc/weewx/weewx.conf
>>> it works. Starting with
>>> systemctl start weewx, 
>>> it fails.
>>> Maybe, I will find out, what makes the difference. But, just in case, 
>>> someone knows the trick, please tell!
>>>
>>> Thanks
>>> -Peter
>>>
>>> Vetti52 schrieb am Mittwoch, 3. Februar 2021 um 18:20:07 UTC+1:
>>>
 Typo: Upgrade from 4.3.0 to 4.4.0.
 Version 4.3.0 had no issues so far.

 Vetti52 schrieb am Mittwoch, 3. Februar 2021 um 18:17:46 UTC+1:

> Just upgraded from 4.4.3 to 4.4.0, but it fails.
> got this in systemctl status weewx.service:
> Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
> weewx.engine:   debug_wind=self.debug_wind)
> Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
> weewx.engine: File "/usr/share/weewx/user/gw1000.py", line 
> 2166, in __init__
> Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
> weewx.engine:   
> lost_contact_log_period=lost_contact_log_period)
> Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
> weewx.engine: File "/usr/share/weewx/user/gw1000.py", line 
> 2915, in __init__
> Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
> weewx.engine:   ip_port_list = self.discover()
> Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
> weewx.engine: File "/usr/share/weewx/user/gw1000.py", line 
> 3005, in discover
> Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
> weewx.engine:   socket_obj.sendto(packet, 
> (self.broadcast_address, self.broadcast_port))
> Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
> weewx.engine:   OSError: [Errno 101] Das Netzwerk ist nicht 
> erreichbar
> Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL __main__: 
> Unable to load driver: [Errno 101] Das Netzwerk ist nicht erreichbar
> Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
> __main__:   Exiting...
>
> Hopefully someone knows, what to do.
>
> Thanks
> -Peter
>
> n0...@n0nb.us schrieb am Dienstag, 2. Februar 2021 um 03:48:05 UTC+1:
>
>> Updated this morning on Debian 10.7 and after several minutes of 
>> updating the DB, everything came up working smooth as silk. 
>>
>> Good show! 
>>
>> - Nate 
>>
>> -- 
>>
>> "The optimist proclaims that we live in the best 

[weewx-user] Raspberry PI 4 without RTC - delayed start

['plin...@googlemail.com' via weewx-user]

Hello!

I am about to install weewx on a Raspberry Pi 4.
The Raspberry has no RTC, but synchronization using systemd-timesyncd

A note on the delayed start of weewx after timesync is stored in the wiki.


Added 25-Nov-2019. 
The article How can I delay the startup of systemd services until the 
datetime is set 
(no RTC on the Raspberry Pi) has some very useful hints on a more elegant 
solution
https://raspberrypi.stackexchange.com/questions/94635/how-can-i-delay-the-startup-of-systemd-services-until-the-datetime-is-set-no-rt


Does anyone have that going?
Is it stable and reliable with this method to delay the start of weewx to 
avoid incorrect timestamps?

Thank you for your answers
Pline

-- 
You received this message because you are subscribed to the Google 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/d74c6f3a-a39c-4aaa-8700-fe6903366264n%40googlegroups.com.

Re: [weewx-user] Bootstrap skin update preview

[Tom Keffer]

Don't know what happened, but now it works for me with no errors.

Looks great!

On Wed, Feb 3, 2021 at 8:48 PM michael.k...@gmx.at <
michael.kainzba...@gmx.at> wrote:

> Hello Tom,
>
> The error with the /favicon.ico is a simple one: there is no such file.
> The other errors I couldn't reproduce, even trying with different browser
> on different computers and phones. Isn't weewxData.js there, when you try
> to load it? It's referenced on line 144 of the HTML.
> What browser on what system are you using?
> I got it working with Windows: Firefox, Brave, Edge, Chrome, Raspbian with
> Chromium, Android 10 Chrome, Brave, Firefox. Android 7.0 Chrome. I've
> encountered some Problems with the connection to the MQTT broker while
> using the companies VPN and and some weird rendering of the gauges an
> images using the edge version 44, pre-chromium) browser that is installed
> at the companies computer and no displaying of the gauges and charts with
> the internet explorer (an there are no plans to get this working)
> tke...@gmail.com schrieb am Mittwoch, 3. Februar 2021 um 23:57:25 UTC+1:
>
>> Hi, Michael.
>>
>> I got several errors when I tried to see your live version:
>>
>> Uncaught SyntaxError: Unexpected end of input
>> site.js:1 Uncaught ReferenceError: weewxData is not defined
>> at site.js:1
>> gauges.js:3 Uncaught ReferenceError: weewxData is not defined
>> at gauges.js:3
>> charts.js:2 Uncaught ReferenceError: weewxData is not defined
>> at charts.js:2
>> /favicon.ico:1 Failed to load resource: the server responded with a
>> status of 404 (Not Found)
>>
>>
>> On Wed, Feb 3, 2021 at 1:12 PM michael.k...@gmx.at 
>> wrote:
>>
>>> A couple of weeks ago, I asked Nick, the author of the bootstrap skin,
>>> if he could help me taking his skin, that I am very fond of, to the next
>>> level. As a first step we developed an optional live view with browser
>>> rendered gauges and charts, using MQTT for the almost-real-time rendering.
>>> Everything is still under heavy development, but still, I think time has
>>> come to show a first preview. Whoever wants to check it out, this is the
>>> development branch:
>>>
>>> https://github.com/brewster76/fuzzy-archer/tree/liveCharts
>>>
>>> Be careful, not production ready!
>>>
>>> For those who want to see it in action:
>>>
>>> https://www.kainzbauer.net/weather/Rif-Tempest/live.html
>>>
>>> The Weatherflow Tempest is really great for such fancy almost-realtime
>>> sites with it's 3 second wind/windDir update interval.
>>>
>>> --
>>> You received this message because you are subscribed 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/bd8b0eb8-f803-43e9-9f7b-077dc4b79f1dn%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/9ad6d9d4-38d8-4503-ba91-a7adb5652c13n%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/CAPq0zEAsVBtGhTb2-m_7dFuU9RvoFFuC2G-Q0dhBjVqSPdzq%2Bw%40mail.gmail.com.

Re: [weewx-user] Version 4.4.0

[Vetti52]

Hi,
maybe a new thread would be helpful, because the issue is/was very special 
and might not be a problem with version 4.4.0:

After I realized, that weewx could be run manually, I was inspecting, what 
was the difference. I had updated to version 4.4.0 and also had an update 
for my Zigbee device driver (deCONZ). Then I had to reboot the Raspberry Pi 
and after that the error occured. Finally I realized, that, the 
/etc/init.d/weewx 
start failed, with code=exited but no success. I misinterpreted this as 
that weewx was not running, since there were no syslog entries at all. 
Repeating to start weewx using the previous interceptor driver did not work 
either. So I decided to let it run with gw1000 driver, but started it 
manually with sudo weewxd /etc/weewx/weewx.conf >nul &.  This was 
successful, and went to sleep
Today I decided to look at this issue again and, instead of killing the 
manually started weexd properly, I accidently used /etc/init.d/weewx stop, 
which indeed stopped weewx, but the manually started weewxd continued. 
After I stopped this too, I realized, that weewx had in fact been started 
autmatically after reboot, but got stuck, as you say, because of the gw1000 
driver. What I did not expect, is, that weewx then did not exit. Any 
additional starting command therefore failed. I was cind of silly, not to 
look at that, sorry. After stopping the hanging weewx, I could start weewx 
as expected, and now it works without any issues. Maybe, it would be better 
not to start weewx with its init.d script, but with systemctl using a 
separate weewx.service file which should contain a stanza like

[Unit]
After=network-online.target

that would avoid to start weewx before network is up, which seems to be a 
crucial step for gw1000. But this should be another thread, I think.

Thanks 
Peter
gjr80 schrieb am Mittwoch, 3. Februar 2021 um 20:33:21 UTC+1:

> Ok, can you please set debug=1, restart WeeWX as a daemon and post in a 
> new thread the log through until the failure occurs.
>
> Gary
>
> On Thursday, 4 February 2021 at 05:28:00 UTC+10 Vetti52 wrote:
>
>> just to narrow down my problem:
>>
>> When starting manually 
>>  weewxd /etc/weewx/weewx.conf
>> it works. Starting with
>> systemctl start weewx, 
>> it fails.
>> Maybe, I will find out, what makes the difference. But, just in case, 
>> someone knows the trick, please tell!
>>
>> Thanks
>> -Peter
>>
>> Vetti52 schrieb am Mittwoch, 3. Februar 2021 um 18:20:07 UTC+1:
>>
>>> Typo: Upgrade from 4.3.0 to 4.4.0.
>>> Version 4.3.0 had no issues so far.
>>>
>>> Vetti52 schrieb am Mittwoch, 3. Februar 2021 um 18:17:46 UTC+1:
>>>
 Just upgraded from 4.4.3 to 4.4.0, but it fails.
 got this in systemctl status weewx.service:
 Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
 weewx.engine:   debug_wind=self.debug_wind)
 Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
 weewx.engine: File "/usr/share/weewx/user/gw1000.py", line 
 2166, in __init__
 Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
 weewx.engine:   
 lost_contact_log_period=lost_contact_log_period)
 Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
 weewx.engine: File "/usr/share/weewx/user/gw1000.py", line 
 2915, in __init__
 Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
 weewx.engine:   ip_port_list = self.discover()
 Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
 weewx.engine: File "/usr/share/weewx/user/gw1000.py", line 
 3005, in discover
 Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
 weewx.engine:   socket_obj.sendto(packet, 
 (self.broadcast_address, self.broadcast_port))
 Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL 
 weewx.engine:   OSError: [Errno 101] Das Netzwerk ist nicht 
 erreichbar
 Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL __main__: 
 Unable to load driver: [Errno 101] Das Netzwerk ist nicht erreichbar
 Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL __main__: 
   Exiting...

 Hopefully someone knows, what to do.

 Thanks
 -Peter

 n0...@n0nb.us schrieb am Dienstag, 2. Februar 2021 um 03:48:05 UTC+1:

> Updated this morning on Debian 10.7 and after several minutes of 
> updating the DB, everything came up working smooth as silk. 
>
> Good show! 
>
> - Nate 
>
> -- 
>
> "The optimist proclaims that we live in the best of all 
> possible worlds. The pessimist fears this is true." 
>
> Web: https://www.n0nb.us 
> Projects: https://github.com/N0NB 
> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 
>
>

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

[weewx-user] Re: WMR200: Speed up record-reading

[michael.k...@gmx.at]

I guess the speed-issues are driver specific. I don't know what rate of 
backfilling records is to be expected with your station.
But the best advice I can give you: don't rely on a SD-Card, it's not built 
for many write operations. You will see the new card crashing again. Use a 
SSD instead.

peredst...@gmail.com schrieb am Donnerstag, 4. Februar 2021 um 08:38:58 
UTC+1:

>
> I had a SD-card crash so the weewx-server was offline for quite a while. 
> Now that I managed to recover the database and transfer all customized 
> files to the new installation I get issues with the catching up.
>
> Weewx is only reading stored records a bit faster than live so this will 
> take months. And during this time there are no new images created - it is 
> just waiting for the stored records to be read.
>
> How can I speed up the reading and storing of records?
>

-- 
You received this message because you are subscribed to the Google 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/f1aa0db0-ccdc-4151-8a32-2314f54d28ben%40googlegroups.com.