Re: [weewx-user] Belchertown MQTT live stats problem

[Chotechai Piyavongsiri]

So it could be something changed on the public mqtt end.

On Wednesday, 29 July 2020 at 11:18:21 UTC+7 Chotechai Piyavongsiri wrote:

> Running fine with local mqtt broker, with or without encryption.
>
> On Wednesday, 29 July 2020 at 03:10:28 UTC+7 vince wrote:
>
>> On Tuesday, July 28, 2020 at 1:07:05 PM UTC-7, Scott Grayban wrote:
>>>
>>> I opened a issue ticket at 
>>> https://github.com/poblabs/weewx-belchertown/issues/344
>>>
>>>
>> I did a clean install on weewx v4 and belchertown latest, both with 
>> python3.
>> Live stats works just fine for me, without MQTT encryption being enabled.
>>
>>

-- 
You received this message because you are 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/ab123d4e-3e2c-45f1-9724-397962a5fc62n%40googlegroups.com.

Re: [weewx-user] Belchertown MQTT live stats problem

[Chotechai Piyavongsiri]

Running fine with local mqtt broker, with or without encryption.

On Wednesday, 29 July 2020 at 03:10:28 UTC+7 vince wrote:

> On Tuesday, July 28, 2020 at 1:07:05 PM UTC-7, Scott Grayban wrote:
>>
>> I opened a issue ticket at 
>> https://github.com/poblabs/weewx-belchertown/issues/344
>>
>>
> I did a clean install on weewx v4 and belchertown latest, both with 
> python3.
> Live stats works just fine for me, without MQTT encryption being enabled.
>
>

-- 
You received this message because you are 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/4ffb64a0-52be-4830-ac0e-d0cbc9f65ce1n%40googlegroups.com.

[weewx-user] weewx 4.1.1, Belchertown skin, and Weatherflow Tempest issues

[gjr80]

I would say that line 71 in the Belchertown skin.conf might be a good place to 
start.

Jul 29 10:50:19 bthoven-3020M weewx[56935] ERROR weewx.reportengine: 
  Parsing failed with several errors.#012First error at line 71.

Gary

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

[weewx-user] weewx 4.1.1, Belchertown skin, and Weatherflow Tempest issues

[Chotechai Piyavongsiri]

I've been running weewx 3.xx and the excellent Belchertown skin on my 
ubuntu 18.04 without any problem. My source sensors is Aercus Weathersleuth 
equivalent (Misol brand) sending data to Ecowitt GW1000.

I've set up another Ubuntu 20.04 server for some other testing and now I 
get the Weatherflow Tempest. I installed weewx latest 4.1.1, python3, 
Belchertown skin, and the latest Weewx UDP driver for Weatherflow. Weewx 
can generate standard reports without any issues; but the Belchertown skin 
generates a lot of errors. The weewx config on the Belchertown part is more 
or less the same (except the website root directory). Data in weewx.sdb 
seems populated fine.

This is the errors generated:

Jul 29 10:50:10 bthoven-3020M weewx[56935] INFO weewx.restx: MQTT: 
Published record 2020-07-29 10:50:07 +07 (1595994607)
Jul 29 10:50:16 bthoven-3020M weewx[56935] INFO weewx.restx: MQTT: 
Published record 2020-07-29 10:50:13 +07 (1595994613)
Jul 29 10:50:19 bthoven-3020M weewx[56935] INFO weewx.restx: MQTT: 
Published record 2020-07-29 10:50:16 +07 (1595994616)
Jul 29 10:50:19 bthoven-3020M weewx[56935] INFO weewx.manager: Added record 
2020-07-29 10:50:00 +07 (1595994600) to database 'weewx.sdb'
Jul 29 10:50:19 bthoven-3020M weewx[56935] INFO weewx.manager: Added record 
2020-07-29 10:50:00 +07 (1595994600) to daily summary in 'weewx.sdb'
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.reportengine: 
Running reports for latest time in the database.
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.reportengine: 
Running report 'SeasonsReport'
Jul 29 10:50:19 bthoven-3020M /weewxd: weatherflowudp: MainThread: 
Listening for UDP broadcasts to IP address  on port 50222, with 
timeout 90 and share_socket True...
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Seasons/skin.conf for report 
'SeasonsReport'
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.cheetahgenerator: 
Using search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras']
Jul 29 10:50:19 bthoven-3020M weewx[56935] INFO weewx.restx: MQTT: 
Published record 2020-07-29 10:50:00 +07 (1595994600)
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.manager: Daily 
summary version is 2.0
Jul 29 10:50:19 bthoven-3020M weewx[56935] INFO weewx.cheetahgenerator: 
Generated 8 files for report SeasonsReport in 0.23 seconds
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.manager: Daily 
summary version is 2.0
Jul 29 10:50:19 bthoven-3020M weewx[56935] INFO weewx.imagegenerator: 
Generated 15 images for report SeasonsReport in 0.17 seconds
Jul 29 10:50:19 bthoven-3020M weewx[56935] INFO weewx.reportengine: Copied 
0 files to /var/www/html/weewx
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.reportengine: Report 
'SmartphoneReport' not enabled. Skipping.
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.reportengine: Report 
'MobileReport' not enabled. Skipping.
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.reportengine: Report 
'StandardReport' not enabled. Skipping.
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.reportengine: 
Running report 'Belchertown'
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Belchertown/skin.conf for report 
'Belchertown'
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.cheetahgenerator: 
Using search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras', 'user.belchertown.getData']
Jul 29 10:50:19 bthoven-3020M weewx[56935] DEBUG weewx.manager: Daily 
summary version is 2.0
Jul 29 10:50:19 bthoven-3020M weewx[56935] ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 
'weewx.cheetahgenerator.CheetahGenerator'
Jul 29 10:50:19 bthoven-3020M weewx[56935] ERROR weewx.reportengine:
   Parsing failed with several errors.#012First error at line 71.
Jul 29 10:50:19 bthoven-3020M weewx[56935] ERROR weewx.reportengine:
   Traceback (most recent call last):
Jul 29 10:50:19 bthoven-3020M weewx[56935] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
Jul 29 10:50:19 bthoven-3020M weewx[56935] ERROR weewx.reportengine:
   obj.start()
Jul 29 10:50:19 bthoven-3020M weewx[56935] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/reportengine.py", line 280, in start
Jul 29 10:50:19 bthoven-3020M weewx[56935] ERROR weewx.reportengine:
   self.run()
Jul 29 10:50:19 bthoven-3020M weewx[56935] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 150, in run
Jul 29 

Re: [weewx-user] Re: New GW1000 Driver available for testing

[gjr80]

I have added a page to the GW1000 driver wiki 
 with details of the battery 
state information provided by the driver. The details on the page a a 
combination of details specified in the API, information posted on 
wxforum.net and anecdotal evidence obtained during development of the 
driver. Please let me know if you observe/notice any discrepancies.

On Wednesday, 29 July 2020 08:13:10 UTC+10, gjr80 wrote:
>
> I will put a battery state table in the driver wiki today.
>
> Gary
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/83400714-45ef-46fb-86e8-b5b3a7ee277co%40googlegroups.com.

Re: [weewx-user] Re: wind chill for Vantage Pro 2

[Tom Keffer]

>
> @tkeffer. Tom, I see the vantage driver does not log what format loop
> packet is being used, perhaps it should?
>

I was just thinking the same. Commit bb12695

.

-tk

-- 
You received this message because you are 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/CAPq0zEAhQ8EOhyOMzkYRYqFJp7%3DQDT27MYSvKeueueaQAvXhJQ%40mail.gmail.com.

Re: [weewx-user] Re: wind chill for Vantage Pro 2

[gjr80]

On Wednesday, 29 July 2020 10:00:01 UTC+10, brisguy foo wrote:
>
> UPDATE:
>
> Changed by weewx,conf file to read:
> [Vantage]
> ...
> # Use LOOP2 data in order to get access to wind_chill
> loop_request = 2
>
> Restarted weewx
>
> After only an hour or so, I saw that my console was reporting wind-chill 
> that was 2 to 3 degrees lower than outside temp, but the weewx graph showed 
> no difference.
>

Using the plots to check what is happening can give misleading results; not 
saying that is the case here but some plots are not generated every cycle 
and there can be caching issues. Best evidence is to look at what is in the 
database or loop packets/archive records or look at the database.
 

>
> Checked the syslog file today, and at the time of the restart found the 
> following odd statement:
> 16:40:18 raspberrypi weewx[30378]: wxcalculate: The following values will 
> be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
> dewpoint=prefer_hardware, appTemp=prefer_hardware, 
> rainRate=prefer_hardware, windrun=prefer_hardware, 
> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
> humidex=prefer_hardware, pressure=prefer_hardware, 
> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
> cloudbase=prefer_hardware
>
> It seems odd that weewx would report it is calculating values that have 
> been set to 'prefer_hardware', plus I only used that for five parameters, 
> and weewx is reporting it has been set for several more.
>
> So now I have two issues:
> 1. How can I tell whether LOOP2 packets ate being used (the graph 
> indicates they are not)
>

There is no direct way that I know of. I would stop WeeWX and then run it 
directly so you see the loop packets and archive records on the console. 
What do you see in the loop packets (lines starting with LOOP:) and archive 
records (lines starting REC:) on the console? How does windchill compare to 
outTemp? If you are seeing THSW in the loop packets then WeeWX is receiving 
the LOOP2 format loop packet, if THSW is not there then I suspect you are 
still using the LOOP format loop packets. 
 

> 2. Why is weewx reporting it is calculating values that have been set to 
> 'prefer_hardware'?
>

If WeeWX is calculating windchill it is most likely because windchill is 
not being received by WeeWX. Change 'prefer_hardware' to 'hardware' for 
windchill and restart/reload WeeWX. If windchill disappears it will be 
because WeeWX is not receiving windchill which implies you are still using 
LOOP format loop packets.

@tkeffer. Tom, I see the vantage driver does not log what format loop 
packet is being used, perhaps it should?

Gary

>
> Thanks,  Stan
>
>
> On Monday, July 27, 2020 at 4:47:41 PM UTC-7, brisguy foo wrote:
>>
>> Thanks for the replies guys!
>>
>> I did update my conf file as suggested, however I am confused by the 
>> comment that wind chill "is not in the LOOP or archive record from the 
>> console".
>>
>> I know I was able to see wind chill in historical data downloaded from 
>> the console logger and displayed using WeatherLink. If you are referring to 
>> the weewx archive, then I am concerned that the not all LOOP 2 data is 
>> being stored.
>>
>> Please help me understand if you don't mind. I should be able to see the 
>> result in a few days anyway, but I'd like to know how this works.
>>
>> Thanks!
>>
>>
>>
>> On Friday, July 24, 2020 at 5:21:48 PM UTC-7, Tom Keffer wrote:
>>>
>>> Geez, Gary, you're right! So, you would also have to specify LOOP2 
>>> packets. See the section [Vantage] 
>>>  in the User's 
>>> Guide.
>>>
>>> [Vantage]
>>>   loop_request = 2
>>>
>>>
>>> -tk
>>>
>>> On Fri, Jul 24, 2020 at 5:13 PM gjr80  wrote:
>>>
 Windchill is only in included in the Davis LOOP2 packet, it’s not in 
 the LOOP packet or archive record (the defaults) from the console. So 
 unless you have set WeeWX to use the LOOP2 packet WeeWX will never see 
 windchill from the console, irrespective of StdWXCalculate settings.

 Gary

 -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to weewx...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/9a8a0b4e-4b27-404b-aec4-72cd8dbc7331o%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/30f4bc94-007a-43d2-873c-67c5419ba72do%40googlegroups.com.

Re: [weewx-user] Re: wind chill for Vantage Pro 2

[brisguy foo]

UPDATE:

Changed by weewx,conf file to read:
[Vantage]
...
# Use LOOP2 data in order to get access to wind_chill
loop_request = 2

Restarted weewx

After only an hour or so, I saw that my console was reporting wind-chill 
that was 2 to 3 degrees lower than outside temp, but the weewx graph showed 
no difference.

Checked the syslog file today, and at the time of the restart found the 
following odd statement:
16:40:18 raspberrypi weewx[30378]: wxcalculate: The following values will 
be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware

It seems odd that weewx would report it is calculating values that have 
been set to 'prefer_hardware', plus I only used that for five parameters, 
and weewx is reporting it has been set for several more.

So now I have two issues:
1. How can I tell whether LOOP2 packets ate being used (the graph indicates 
they are not)
2. Why is weewx reporting it is calculating values that have been set to 
'prefer_hardware'?

Thanks,  Stan


On Monday, July 27, 2020 at 4:47:41 PM UTC-7, brisguy foo wrote:
>
> Thanks for the replies guys!
>
> I did update my conf file as suggested, however I am confused by the 
> comment that wind chill "is not in the LOOP or archive record from the 
> console".
>
> I know I was able to see wind chill in historical data downloaded from the 
> console logger and displayed using WeatherLink. If you are referring to the 
> weewx archive, then I am concerned that the not all LOOP 2 data is being 
> stored.
>
> Please help me understand if you don't mind. I should be able to see the 
> result in a few days anyway, but I'd like to know how this works.
>
> Thanks!
>
>
>
> On Friday, July 24, 2020 at 5:21:48 PM UTC-7, Tom Keffer wrote:
>>
>> Geez, Gary, you're right! So, you would also have to specify LOOP2 
>> packets. See the section [Vantage] 
>>  in the User's Guide.
>>
>> [Vantage]
>>   loop_request = 2
>>
>>
>> -tk
>>
>> On Fri, Jul 24, 2020 at 5:13 PM gjr80  wrote:
>>
>>> Windchill is only in included in the Davis LOOP2 packet, it’s not in the 
>>> LOOP packet or archive record (the defaults) from the console. So unless 
>>> you have set WeeWX to use the LOOP2 packet WeeWX will never see windchill 
>>> from the console, irrespective of StdWXCalculate settings.
>>>
>>> Gary
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/9a8a0b4e-4b27-404b-aec4-72cd8dbc7331o%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/2c55be9f-6f74-4873-b9e4-dcfee794940bo%40googlegroups.com.

Re: [weewx-user] Re: weatherflowudp crash

[Jamie Stephens]

I didn’t do the setup.py method.   I’m still a Linux newb haha

-- 
You received this message because you are 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/CABWMpWQabfj5ffFHg4htTkPt28vDdjddeD-r_FzM6fG78XeDLw%40mail.gmail.com.

[weewx-user] Re: weatherflowudp crash

[vince]

On Tuesday, July 28, 2020 at 4:49:50 PM UTC-7, vince wrote:
>
> FWIW, I'm using driver 1.1, weewx 4.1.1, python 3.5.3 on a somewhat dated 
> pi3plus (Debian 9), with weewx installed using python3 and setup.py method.
>

doh - Belchertown 1.1, mqtt 0.23, and weatherflowudp 1.10 that is 

-- 
You received this message because you are 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/fded43a0-4da0-451f-844a-74614398f360o%40googlegroups.com.

[weewx-user] Re: weatherflowudp crash

[vince]

FWIW, I'm using driver 1.1, weewx 4.1.1, python 3.5.3 on a somewhat dated 
pi3plus (Debian 9), with weewx installed using python3 and setup.py method.

-- 
You received this message because you are 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/c59ec025-03fb-499c-8dc8-0c3f26dd9b3eo%40googlegroups.com.

[weewx-user] Re: weatherflowudp crash

[Jamie Stephens]

thanks Vince using 1.10 

might start disabling stuff and see if i can figure it out.

On Tuesday, July 28, 2020 at 7:06:27 PM UTC-4 vince wrote:

> On Tuesday, July 28, 2020 at 3:38:39 PM UTC-7, Jamie Stephens wrote:
>>
>> another crash, any ideas?
>>
>>
> First guess is a python2/python3 thing.   Are you on the latest version of 
> the driver ? 
>

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

[weewx-user] Re: weatherflowudp crash

[vince]

On Tuesday, July 28, 2020 at 3:38:39 PM UTC-7, Jamie Stephens wrote:
>
> another crash, any ideas?
>
>
First guess is a python2/python3 thing.   Are you on the latest version of 
the driver ? 

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

Re: [weewx-user] FTP Stopped Working After Updating Station Hardware

[Tom Keffer]

OK, seeing as how that's the only value in the database, let's start
afresh. Can you delete the database, then restart weewx? Keep debug=2. Post
the log from the restart for the first couple of report cycles (10 minutes
or so).

-tk

On Tue, Jul 28, 2020 at 3:33 PM Pat W.  wrote:

> Affirmative.
>
>
> On Tuesday, July 28, 2020 at 3:55:25 PM UTC-5, Tom Keffer wrote:
>>
>> That's the only value in the database?
>>
>> On Tue, Jul 28, 2020 at 1:24 PM Pat W.  wrote:
>>
>>> The problem seems consistent. DB query here:
>>>
>>> sqlite> select datetime(dateTime,'unixepoch','localtime') from archive
>>> order by dateTime desc limit 10;
>>> 2020-07-26 16:05:00
>>>
>>>
>>>
>>> On Tuesday, July 28, 2020 at 8:59:43 AM UTC-5, Tom Keffer wrote:

 Could you please post the results of the database query? I want to
 compare the timestamps with the raw data output of the WeatherFlow.

 Also, is this problem consistent? Or, does it come and go?

 -tk

 On Mon, Jul 27, 2020 at 1:16 PM Pat W.  wrote:

> Tom,
>
> 1. Using your sqlite commands (thanks!) I see only one entry in the
> database, and its from yesterday when I was fiddling with things.
>
> 2. Same here, html and png files were created at least once yesterday.
> Nothing today.
>
> Pat W.
>
> On Sunday, July 26, 2020 at 6:22:11 PM UTC-5, Tom Keffer wrote:
>>
>> I have my suspicions about what's going on here, but first let me ask
>> you two questions.
>>
>> 1. Is there any evidence that anything is getting stored in the
>> database? Take a look in your database. This will show the timestamps of
>> the last 10 records that have been stored in the database:
>>
>> *sqlite3 /var/lib/weewx/weewx.sdb*
>> sqlite> *select datetime(dateTime,'unixepoch','localtime') from
>> archive order by dateTime desc limit 10;*
>>
>> 2. Is there any evidence that reports have been generated at all (let
>> alone FTP'd)?
>>
>>
>> *ls -l /var/www/html/weewx*
>>
>> -tk
>>
>> On Sun, Jul 26, 2020 at 3:24 PM Pat W.  wrote:
>>
>>> Hi All,
>>>
>>> I've been using weewx for a couple years with an old WMR-918 and all
>>> works fine, including an FTP upload to my personal web page every five
>>> minutes. Recently bought a Weatherflow Tempest and installed the
>>> WeatherFlowUDP extension. Weewx appears to be receiving data from the
>>> station properly, but the FTP function has stopped working and I can't 
>>> find
>>> any references to it in the syslog. I reinstalled weewx from scratch
>>> (installed via apt-get on Raspberry Pi 4) after the hardware change to 
>>> no
>>> avail.
>>>
>>> I'm a linux novice but can find my way around. This one has me
>>> stumped. Any help is appreciated. mylog and wee_debug files attached
>>>
>>> Pat W.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it,
>>> send an email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/d5cd1209-4b4c-4165-b857-39f237300f8co%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google
> Groups "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to weewx...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/c74fba6c-92cf-49aa-8732-9302e8ff8525o%40googlegroups.com
> 
> .
>
 --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/7d99645c-d737-4d32-87f6-7b1377ea7881o%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/53e8e5ea-74d2-402b-91f8-63886ea38a87o%40googlegroups.com
> 

[weewx-user] Re: weatherflowudp crash

[Jamie Stephens]

another crash, any ideas?

Jul 28 08:20:26 weewx weewx[6505] DEBUG weewx.restx: CWOP: Connected to 
server cwop.aprs.net:14580
  GNU nano 4.8  
syslog  
 Modified  
Jul 28 17:58:23 weewx weewx[6505] CRITICAL __main__: File 
"/usr/share/weewx/user/weatherflowudp.py", line 312, in genLoopPackets
Jul 28 17:58:23 weewx weewx[6505] CRITICAL __main__:   m0 = 
m[0].replace(",null",",None") # Python 2
Jul 28 17:58:23 weewx weewx[6505] CRITICAL __main__:   TypeError: a 
bytes-like object is required, not 'str'   
Jul 28 17:58:23 weewx weewx[6505] CRITICAL __main__:   Exiting.

On Monday, July 27, 2020 at 9:49:32 AM UTC-4 Jamie Stephens wrote:

> [WeatherFlowUDP]
> driver = user.weatherflowudp
> log_raw_packets = False
> udp_address = 
> # udp_address = 0.0.0.0
> # udp_address = 255.255.255.255
> udp_port = 50222
> udp_timeout = 90
> share_socket = False
>
> [[sensor_map]]
> outTemp = air_temperature.ST-00015203.obs_st
> outHumidity = relative_humidity.ST-00015203.obs_st
> pressure = station_pressure.ST-00015203.obs_st
> #lightning_strikes =  lightning_strike_count.ST-00015203.obs_st
> #avg_distance =  lightning_strike_avg_distance.ST-00015203.obs_st
> outTempBatteryStatus = battery.ST-00015203.obs_st
> windSpeed = wind_speed.ST-00015203.rapid_wind
> windDir = wind_direction.ST-00015203.rapid_wind
> #luxXXX = illuminance.ST-00015203.obs_st
> UV = uv.ST-00015203.obs_st
> rain = rain_accumulated.ST-00015203.obs_st
> windBatteryStatus = battery.ST-00015203.obs_st
> radiation = solar_radiation.ST-00015203.obs_st
> #lightningXXX = distance.ST-00015203.evt_strike
> #lightningYYY = energy.ST-00015203.evt_strike
>
> ##
>
> On Monday, July 27, 2020 at 9:38:42 AM UTC-4 Jamie Stephens wrote:
>
>> adter a couple day weewx will shutdown this is what i see in the logs. it 
>> will run anywhere from 1-3 days before this happens
>>
>> running Ubuntu 20.04 on a VM
>> last successful update before crash was at 755 am
>> Jul 27 07:55:25 weewx weewx[4992] INFO weewx.manager: Added record 
>> 2020-07-27 07:55:00 EDT (1595850900) to daily summary in 'weewx.sdb'
>> Jul 27 07:55:25 weewx weewx[4992] DEBUG weewx.reportengine: Running 
>> reports for latest time in the database.
>> Jul 27 07:55:25 weewx /weewxd: weatherflowudp: MainThread: Listening for 
>> UDP broadcasts to IP address  on port 50222, with timeout 90 and 
>> share>
>> Jul 27 07:55:25 weewx weewx[4992] DEBUG weewx.restx: StationRegistry: 
>> wait interval (69600 < 604800) has not passed for record 2020-07-27 
>> 07:55:00 EDT (15>
>> Jul 27 07:55:25 weewx weewx[4992] DEBUG weewx.reportengine: Running 
>> report 'SeasonsReport'
>> Jul 27 07:55:25 weewx weewx[4992] DEBUG weewx.reportengine: Found 
>> configuration file /etc/weewx/skins/Seasons/skin.conf for report 
>> 'SeasonsReport'
>> Jul 27 07:55:25 weewx weewx[4992] DEBUG weewx.cheetahgenerator: Using 
>> search list ['weewx.cheetahgenerator.Almanac', 
>> 'weewx.cheetahgenerator.Station', 'we>
>> Jul 27 07:55:25 weewx weewx[4992] DEBUG weewx.manager: Daily summary 
>> version is 2.0
>> Jul 27 07:55:25 weewx weewx[4992] DEBUG weewx.restx: CWOP: Connected to 
>> server cwop.aprs.net:14580
>> Jul 27 07:55:25 weewx weewx[4992] INFO weewx.restx: PWSWeather: Published 
>> record 2020-07-27 07:55:00 EDT (1595850900)
>> Jul 27 07:55:25 weewx weewx[4992] INFO weewx.restx: CWOP: Published 
>> record 2020-07-27 07:55:00 EDT (1595850900)
>> Jul 27 07:55:25 weewx weewx[4992] INFO weewx.restx: Wunderground-PWS: 
>> Published record 2020-07-27 07:55:00 EDT (1595850900)
>> Jul 27 07:55:27 weewx weewx[4992] INFO weewx.cheetahgenerator: Generated 
>> 8 files for report SeasonsReport in 1.84 seconds
>> Jul 27 07:55:27 weewx weewx[4992] DEBUG weewx.manager: Daily summary 
>> version is 2.0
>> Jul 27 07:55:27 weewx weewx[4992] INFO weewx.imagegenerator: Generated 15 
>> images for report SeasonsReport in 0.51 seconds
>> Jul 27 07:55:27 weewx weewx[4992] INFO weewx.reportengine: Copied 0 files 
>> to /var/www/html/
>> Jul 27 07:55:27 weewx weewx[4992] DEBUG weewx.reportengine: Report 
>> 'SmartphoneReport' not enabled. Skipping.
>> Jul 27 07:55:27 weewx weewx[4992] DEBUG weewx.reportengine: Report 
>> 'MobileReport' not enabled. Skipping.
>> Jul 27 07:55:27 weewx weewx[4992] DEBUG weewx.reportengine: Report 
>> 'StandardReport' not enabled. Skipping.
>> Jul 27 07:55:27 weewx weewx[4992] DEBUG weewx.reportengine: Running 
>> report 'Belchertown'
>> Jul 27 07:55:28 weewx weewx[4992] DEBUG weewx.reportengine: Found 
>> configuration file /etc/weewx/skins/Belchertown/skin.conf for report 
>> 'Belchertown'
>> Jul 27 07:55:28 weewx weewx[4992] 

Re: [weewx-user] FTP Stopped Working After Updating Station Hardware

[Pat W.]

Affirmative.


On Tuesday, July 28, 2020 at 3:55:25 PM UTC-5, Tom Keffer wrote:
>
> That's the only value in the database?
>
> On Tue, Jul 28, 2020 at 1:24 PM Pat W. > 
> wrote:
>
>> The problem seems consistent. DB query here:
>>
>> sqlite> select datetime(dateTime,'unixepoch','localtime') from archive 
>> order by dateTime desc limit 10;
>> 2020-07-26 16:05:00
>>
>>
>>
>> On Tuesday, July 28, 2020 at 8:59:43 AM UTC-5, Tom Keffer wrote:
>>>
>>> Could you please post the results of the database query? I want to 
>>> compare the timestamps with the raw data output of the WeatherFlow.
>>>
>>> Also, is this problem consistent? Or, does it come and go?
>>>
>>> -tk
>>>
>>> On Mon, Jul 27, 2020 at 1:16 PM Pat W.  wrote:
>>>
 Tom,

 1. Using your sqlite commands (thanks!) I see only one entry in the 
 database, and its from yesterday when I was fiddling with things.

 2. Same here, html and png files were created at least once yesterday. 
 Nothing today.

 Pat W.

 On Sunday, July 26, 2020 at 6:22:11 PM UTC-5, Tom Keffer wrote:
>
> I have my suspicions about what's going on here, but first let me ask 
> you two questions.
>
> 1. Is there any evidence that anything is getting stored in the 
> database? Take a look in your database. This will show the timestamps of 
> the last 10 records that have been stored in the database:
>
> *sqlite3 /var/lib/weewx/weewx.sdb*
> sqlite> *select datetime(dateTime,'unixepoch','localtime') from 
> archive order by dateTime desc limit 10;*
>
> 2. Is there any evidence that reports have been generated at all (let 
> alone FTP'd)? 
>
>
> *ls -l /var/www/html/weewx*
>
> -tk
>
> On Sun, Jul 26, 2020 at 3:24 PM Pat W.  wrote:
>
>> Hi All,
>>
>> I've been using weewx for a couple years with an old WMR-918 and all 
>> works fine, including an FTP upload to my personal web page every five 
>> minutes. Recently bought a Weatherflow Tempest and installed the 
>> WeatherFlowUDP extension. Weewx appears to be receiving data from the 
>> station properly, but the FTP function has stopped working and I can't 
>> find 
>> any references to it in the syslog. I reinstalled weewx from scratch 
>> (installed via apt-get on Raspberry Pi 4) after the hardware change to 
>> no 
>> avail. 
>>
>> I'm a linux novice but can find my way around. This one has me 
>> stumped. Any help is appreciated. mylog and wee_debug files attached
>>
>> Pat W.
>>
>> -- 
>> You received this message because you are subscribed to the Google 
>> Groups "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, 
>> send an email to weewx...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/d5cd1209-4b4c-4165-b857-39f237300f8co%40googlegroups.com
>>  
>> 
>> .
>>
> -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to weewx...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/c74fba6c-92cf-49aa-8732-9302e8ff8525o%40googlegroups.com
  
 
 .

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/7d99645c-d737-4d32-87f6-7b1377ea7881o%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/53e8e5ea-74d2-402b-91f8-63886ea38a87o%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

[gjr80]

I will put a battery state table in the driver wiki today.

Gary

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

Re: [weewx-user] FTP Stopped Working After Updating Station Hardware

[Tom Keffer]

That's the only value in the database?

On Tue, Jul 28, 2020 at 1:24 PM Pat W.  wrote:

> The problem seems consistent. DB query here:
>
> sqlite> select datetime(dateTime,'unixepoch','localtime') from archive
> order by dateTime desc limit 10;
> 2020-07-26 16:05:00
>
>
>
> On Tuesday, July 28, 2020 at 8:59:43 AM UTC-5, Tom Keffer wrote:
>>
>> Could you please post the results of the database query? I want to
>> compare the timestamps with the raw data output of the WeatherFlow.
>>
>> Also, is this problem consistent? Or, does it come and go?
>>
>> -tk
>>
>> On Mon, Jul 27, 2020 at 1:16 PM Pat W.  wrote:
>>
>>> Tom,
>>>
>>> 1. Using your sqlite commands (thanks!) I see only one entry in the
>>> database, and its from yesterday when I was fiddling with things.
>>>
>>> 2. Same here, html and png files were created at least once yesterday.
>>> Nothing today.
>>>
>>> Pat W.
>>>
>>> On Sunday, July 26, 2020 at 6:22:11 PM UTC-5, Tom Keffer wrote:

 I have my suspicions about what's going on here, but first let me ask
 you two questions.

 1. Is there any evidence that anything is getting stored in the
 database? Take a look in your database. This will show the timestamps of
 the last 10 records that have been stored in the database:

 *sqlite3 /var/lib/weewx/weewx.sdb*
 sqlite> *select datetime(dateTime,'unixepoch','localtime') from
 archive order by dateTime desc limit 10;*

 2. Is there any evidence that reports have been generated at all (let
 alone FTP'd)?


 *ls -l /var/www/html/weewx*

 -tk

 On Sun, Jul 26, 2020 at 3:24 PM Pat W.  wrote:

> Hi All,
>
> I've been using weewx for a couple years with an old WMR-918 and all
> works fine, including an FTP upload to my personal web page every five
> minutes. Recently bought a Weatherflow Tempest and installed the
> WeatherFlowUDP extension. Weewx appears to be receiving data from the
> station properly, but the FTP function has stopped working and I can't 
> find
> any references to it in the syslog. I reinstalled weewx from scratch
> (installed via apt-get on Raspberry Pi 4) after the hardware change to no
> avail.
>
> I'm a linux novice but can find my way around. This one has me
> stumped. Any help is appreciated. mylog and wee_debug files attached
>
> Pat W.
>
> --
> You received this message because you are subscribed to the Google
> Groups "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to weewx...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/d5cd1209-4b4c-4165-b857-39f237300f8co%40googlegroups.com
> 
> .
>
 --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/c74fba6c-92cf-49aa-8732-9302e8ff8525o%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/7d99645c-d737-4d32-87f6-7b1377ea7881o%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/CAPq0zEA%2BzaA-r3qrr_%3D6SX8Pds2eOgDrt2MECAEZ_XtLmpvYKg%40mail.gmail.com.

Re: [weewx-user] Weewx unable to recognize hardware (vantage.py) error (Vantage Vue)

[Lodewyk Jansen]

Hi Thanks, Tom - I did an uninstall and reinstall but still didn't work so 
I formated the SD and started from scratch - all works again.
Technology hey it does what it does. 

Regards

On Tuesday, 28 July 2020 13:58:29 UTC+12, Tom Keffer wrote:
>
> Somehow, you ended up with an old copy of the Vantage driver (v3.9.2 or 
> earlier) in a modern copy of WeeWX. This old version was not ported to 
> Python 3, so the Python 3 interpreter you are using is complaining.
>
> Try reinstalling WeeWX.
>
> -tk
>
> On Mon, Jul 27, 2020 at 5:12 PM Lodewyk Jansen  > wrote:
>
>> Hi all and thank you for everyone's reply's in advance. 
>>
>> First off - i have a Raspberry Pi Model 3B+ with USB Davis Vantage Vue 
>> and Weewx is installed through python.
>>
>> Initially Weewx worked and there were no erros. However since then i 
>> might have deleted something or done something wrong to cause the errors. 
>>
>> [copied from the command "service weewx status"]
>>
>> pi@raspberrypi:~ $ service weewx status
>> * weewx.service - LSB: weewx weather system
>>Loaded: loaded (/etc/init.d/weewx; generated)
>>Active: active (exited) since Tue 2020-07-28 12:02:32 NZST; 7min ago
>>  Docs: man:systemd-sysv-generator(8)
>>   Process: 1921 ExecStart=/etc/init.d/weewx start (code=exited, 
>> status=0/SUCCESS)
>>
>> Jul 28 12:02:32 raspberrypi weewxd[1936]: weewx[1936] CRITICAL __main__:  
>>  engine = weewx.engine.StdEngine(config_dict)
>> Jul 28 12:02:32 raspberrypi weewxd[1936]: weewx[1936] CRITICAL __main__:  
>>File "/home/weewx/bin/weewx/engine.py", line 69, in __init__
>> Jul 28 12:02:32 raspberrypi weewxd[1936]: weewx[1936] CRITICAL __main__:  
>>  self.setupStation(config_dict)
>> Jul 28 12:02:32 raspberrypi weewxd[1936]: weewx[1936] CRITICAL __main__:  
>>File "/home/weewx/bin/weewx/engine.py", line 92, in setupStation
>> Jul 28 12:02:32 raspberrypi weewxd[1936]: weewx[1936] CRITICAL __main__:  
>>  __import__(driver)
>> Jul 28 12:02:32 raspberrypi weewxd[1936]: weewx[1936] CRITICAL __main__:  
>>File "/home/weewx/bin/weewx/drivers/vantage.py", line 86
>> Jul 28 12:02:32 raspberrypi weewxd[1936]: weewx[1936] CRITICAL __main__:  
>>  print "Unable to wake up console... sleeping"
>> Jul 28 12:02:32 raspberrypi weewxd[1936]: weewx[1936] CRITICAL __main__:  
>>  ^
>> Jul 28 12:02:32 raspberrypi weewxd[1936]: weewx[1936] CRITICAL __main__:  
>>  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
>> print("Unable to wake up console... sleeping")?
>> Jul 28 12:02:32 raspberrypi weewxd[1936]: weewx[1936] CRITICAL __main__:  
>>  Exiting.
>>
>> ___
>> Also attached is the system log file for reference...
>>
>> Anyone that can point me into the right direction to get weeewx to run 
>> without erros? 
>>
>> Regards,
>> LJ
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/1455495f-c421-41b0-98a9-df78f2dce835o%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/b797e619-1fff-4327-92b1-b5d0b0f1a54do%40googlegroups.com.

Re: [weewx-user] FTP Stopped Working After Updating Station Hardware

[Pat W.]

The problem seems consistent. DB query here:

sqlite> select datetime(dateTime,'unixepoch','localtime') from archive 
order by dateTime desc limit 10;
2020-07-26 16:05:00



On Tuesday, July 28, 2020 at 8:59:43 AM UTC-5, Tom Keffer wrote:
>
> Could you please post the results of the database query? I want to compare 
> the timestamps with the raw data output of the WeatherFlow.
>
> Also, is this problem consistent? Or, does it come and go?
>
> -tk
>
> On Mon, Jul 27, 2020 at 1:16 PM Pat W. > 
> wrote:
>
>> Tom,
>>
>> 1. Using your sqlite commands (thanks!) I see only one entry in the 
>> database, and its from yesterday when I was fiddling with things.
>>
>> 2. Same here, html and png files were created at least once yesterday. 
>> Nothing today.
>>
>> Pat W.
>>
>> On Sunday, July 26, 2020 at 6:22:11 PM UTC-5, Tom Keffer wrote:
>>>
>>> I have my suspicions about what's going on here, but first let me ask 
>>> you two questions.
>>>
>>> 1. Is there any evidence that anything is getting stored in the 
>>> database? Take a look in your database. This will show the timestamps of 
>>> the last 10 records that have been stored in the database:
>>>
>>> *sqlite3 /var/lib/weewx/weewx.sdb*
>>> sqlite> *select datetime(dateTime,'unixepoch','localtime') from archive 
>>> order by dateTime desc limit 10;*
>>>
>>> 2. Is there any evidence that reports have been generated at all (let 
>>> alone FTP'd)? 
>>>
>>>
>>> *ls -l /var/www/html/weewx*
>>>
>>> -tk
>>>
>>> On Sun, Jul 26, 2020 at 3:24 PM Pat W.  wrote:
>>>
 Hi All,

 I've been using weewx for a couple years with an old WMR-918 and all 
 works fine, including an FTP upload to my personal web page every five 
 minutes. Recently bought a Weatherflow Tempest and installed the 
 WeatherFlowUDP extension. Weewx appears to be receiving data from the 
 station properly, but the FTP function has stopped working and I can't 
 find 
 any references to it in the syslog. I reinstalled weewx from scratch 
 (installed via apt-get on Raspberry Pi 4) after the hardware change to no 
 avail. 

 I'm a linux novice but can find my way around. This one has me stumped. 
 Any help is appreciated. mylog and wee_debug files attached

 Pat W.

 -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to weewx...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/d5cd1209-4b4c-4165-b857-39f237300f8co%40googlegroups.com
  
 
 .

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/c74fba6c-92cf-49aa-8732-9302e8ff8525o%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/7d99645c-d737-4d32-87f6-7b1377ea7881o%40googlegroups.com.

Re: [weewx-user] Re: wind chill for Vantage Pro 2

[Tom Keffer]

I think Gary was referring to "LOOP" packets as opposed to "LOOP2" packets.
They are two different kinds of packets the Vantage series is capable of
emitting. Only the latter, LOOP2, has windchill.

On Mon, Jul 27, 2020 at 4:47 PM brisguy foo  wrote:

> Thanks for the replies guys!
>
> I did update my conf file as suggested, however I am confused by the
> comment that wind chill "is not in the LOOP or archive record from the
> console".
>
> I know I was able to see wind chill in historical data downloaded from the
> console logger and displayed using WeatherLink. If you are referring to the
> weewx archive, then I am concerned that the not all LOOP 2 data is being
> stored.
>
> Please help me understand if you don't mind. I should be able to see the
> result in a few days anyway, but I'd like to know how this works.
>
> Thanks!
>
>
>
> On Friday, July 24, 2020 at 5:21:48 PM UTC-7, Tom Keffer wrote:
>>
>> Geez, Gary, you're right! So, you would also have to specify LOOP2
>> packets. See the section [Vantage]
>>  in the User's Guide.
>>
>> [Vantage]
>>   loop_request = 2
>>
>>
>> -tk
>>
>> On Fri, Jul 24, 2020 at 5:13 PM gjr80  wrote:
>>
>>> Windchill is only in included in the Davis LOOP2 packet, it’s not in the
>>> LOOP packet or archive record (the defaults) from the console. So unless
>>> you have set WeeWX to use the LOOP2 packet WeeWX will never see windchill
>>> from the console, irrespective of StdWXCalculate settings.
>>>
>>> Gary
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/9a8a0b4e-4b27-404b-aec4-72cd8dbc7331o%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/80976d1d-89f9-45b5-a2e0-14b5794b4f7co%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/CAPq0zEDKNqhboo9yE3XtkQOr5xSA%3Df5NHrta3wXUkwGyx9AgSA%40mail.gmail.com.

Re: [weewx-user] Belchertown MQTT live stats problem

[vince]

On Tuesday, July 28, 2020 at 1:07:05 PM UTC-7, Scott Grayban wrote:
>
> I opened a issue ticket at 
> https://github.com/poblabs/weewx-belchertown/issues/344
>
>
I did a clean install on weewx v4 and belchertown latest, both with python3.
Live stats works just fine for me, without MQTT encryption being enabled.

-- 
You received this message because you are 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/94ce63fc-5bfe-4036-abfc-2a3f80a0e75bo%40googlegroups.com.

Re: [weewx-user] Belchertown MQTT live stats problem

[Scott Grayban]

I opened a issue ticket 
at https://github.com/poblabs/weewx-belchertown/issues/344

-- 
You received this message because you are 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/63664098-0586-42d1-b26c-045fdde4cf47o%40googlegroups.com.

Re: [weewx-user] Belchertown MQTT live stats problem

[Scott Grayban]

@pat Can you give some help here?

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ebcf7172-45c8-4e54-9dd8-29a5f638a8a4o%40googlegroups.com.

Re: [weewx-user] Translation into german

['Hans Cilker' via weewx-user]

Thanks Michael


Michael schrieb am Dienstag, 28. Juli 2020 um 20:16:47 UTC+2:

> take a look into index.html.tmpl, near Line 36
>
> Michael
>

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

Re: [weewx-user] Translation into german

[Michael]

take a look into index.html.tmpl, near Line 36

Michael

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/eae12f85-7ecd-44e9-bd9d-76b4ec04b405o%40googlegroups.com.

Re: [weewx-user] Translation into german

['Hans Cilker' via weewx-user]

https://wetter.hcc-verl.de/index.html
Most is woking fine, but i did not manage to Find " History:   Day Week 
Month Year". The only word i could find looks like key words.  They don't 
look like Header or Text. 

Hans Cilker schrieb am Dienstag, 28. Juli 2020 um 17:50:41 UTC+2:

> Oh, and look in the "NOAA" subdirectory as well. 
> I've taken a look there, at the moment, i have problems there wit german 
> Ü,Ö, Ä .
> Then the hedlines, is it a problem if i need more signs then at the 
> Moment? for example: AVG will become Durchschnitt?
>
>
> Vetti52 schrieb am Montag, 27. Juli 2020 um 20:57:02 UTC+2:
>
>> And you will have to look into weewx.conf. Here are my adoptions:
>>
>> [Station]
>> # Start of week (0=Monday, 6=Sunday)
>> week_start = 0
>>
>> [StdReport]
>> ...
>> [[Defaults]]
>>
>> [[[Units]]]
>> ...
>> Labels
>> day = " Tag", " Tage"  
>> hour = " Stunde", " Stunden"
>> minute = " Minute", " Minuten"
>> second = " Sekunde", " Sekunden"
>> ...
>> [[[Labels]]]
>>
>> # Set to hemisphere abbreviations suitable for your location:
>> hemispheres = N, S, O, W
>>  
>> # Generic labels, keyed by an observation type.
>> Generic
>> barometer = Barometer
>> dewpoint = Taupunkt
>> ET = ET
>> heatindex = Hitzeindex
>> inHumidity = Innenluftfeuchte
>> inTemp = Innentemperatur
>> outHumidity = Luftfeuchte
>> outTemp = Außentemperatur
>> radiation = Sonnenstrahlung
>> rain = Regen
>> rainRate = Regenrate
>> UV = UV Index
>> windDir = Windrichtung
>> windGust = Böen
>> windGustDir = Böenrichtung
>> windSpeed = Windgeschwindigkeit
>> windchill = Windchill
>> windgustvec = Böenvektor
>> windvec = Windvektor
>>
>>   [[[Almanac]]]
>>
>> # The labels to be used for the phases of the moon:
>> moon_phases = Neumond, zunehmende Sichel, zunehmender 
>> Halbmond, zweites Viertel, Vollmond, drittes Viertel, abnehmender Halbmond, 
>> abnehmende Sichel
>>
>> All of the rest I found in the skin files, so far I could find it.
>> Hope, that helps
>>
>> -Peter
>>
>> Am Montag, 27. Juli 2020 20:24:22 UTC+2 schrieb Tom Keffer:
>>
>>> Oh, and look in the "NOAA" subdirectory as well. That would be 
>>> /etc/weewx/skins/Seasons/NOAA or /home/weewx/skins/Seasons/NOAA.
>>>
>>> On Mon, Jul 27, 2020 at 11:22 AM Tom Keffer  wrote:
>>>
>> If you are localizing the *Seasons* skin, the files would be found in 
 /etc/weewx/skins/Seasons if you did a package install. They would be found 
 in /home/weewx/skins/Seasons if you did a setup.py install.

 Look for files with suffixes of ".inc" and ".tmpl".

 -tk

 On Mon, Jul 27, 2020 at 11:18 AM 'Hans Cilker' via weewx-user <
 weewx...@googlegroups.com> wrote:

>>> yea, that i found, but not where to change the Headlines and the parts 
> above, sorry may be thats to high for me. I was looking for : Monthly 
> Reports as an example, this i did not founf, also Current Conditions  and 
> so on, but i think its me who is not able to find that points, therefore 
> the question if ther is a place where i can found all together, or where 
> all files are written i have to change.
>
> tke...@gmail.com schrieb am Montag, 27. Juli 2020 um 19:27:00 UTC+2:
>
>> Hello, Hans
>>
>> Did you look at the section *Localization 
>> * in the 
>> Customizing Guide? 
>>
>> On Mon, Jul 27, 2020 at 9:32 AM 'Hans Cilker' via weewx-user <
>> weewx...@googlegroups.com> wrote:
>>
>>>
>>> Hallo together, i've taken a look at the doc's and i did a search in 
>>> the net, but nothing fit to my ideas. I want to translate the standard 
>>> output into german, but i find not everything i want to translate. Is 
>>> there 
>>> inside the doc's a place, where i can find in which files i ve to look 
>>> for 
>>> finding whats to translate? For example, i found nothing wher to 
>>> translat " 
>>> Monthly Reports: and Yearly Report. Thanks a lot
>>> Hans
>>>
>>> -- 
>>> You received this message because you are 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/c02044f3-2aa2-4931-9e07-1e83e019b1d9n%40googlegroups.com
>>>  
>>> 

Re: [weewx-user] Belchertown MQTT live stats problem

[Don Roberts]

Using developer mode, it looks like the MQTT server sends the string “Hello”, 
which causes the following line to crash:

data = jQuery.parseJSON( data );

Don’t know if jQuery has changed recently, or the MQTT protocol. I’m not a 
webservices guru by any means.

don

> On Jul 28, 2020, at 7:55 AM, Graham Eddy  wrote:
> 
> maybe they turned off unencrypted mode.
> try turning on SSL and use encrypted websockets port (8081 on 
> test.mosquitto.org )
> 
> re logs, need option in mosquitto.conf ‘log_type all’ (or at least ‘log_type 
> websockets’) plus (i haven’t tried this) ‘websockets_log_level {some flags}’ 
> - latter defaults to off
> 
>> On 28 Jul 2020, at 10:30 pm, Don Roberts > > wrote:
>> 
>> I'm experiencing this same thing, and I'm using a public MQTT broker. Didn't 
>> change anything.
>> 
>> don
>> 
>> On Friday, July 24, 2020 at 11:26:40 PM UTC-5, Scott Grayban wrote:
>> For over a year my live stats has been working flawlessly until recently. 
>> Now it says Failed connecting to the weather station
>> 
>> Looking at the dev console in chrome I am seeing this for the error and not 
>> sure how to test this out to see what is going on.
>> 
>> mqttws31.min.js:36 WebSocket connection to 'ws://X.X.X.X:9001/mqtt 
>> ' failed: Connection closed before receiving a 
>> handshake response
>> 
>> The MQTT logs are only showing connections via port 1883.
>> 
>> -- 
>> You received this message because you are 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/73f84443-63ed-452f-8f2d-2cf65bfa0405o%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/7D44F99A-801E-46F6-8BE1-1B048F7CA890%40gmail.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/F51A8256-F654-444D-B686-C071780439CB%40gmail.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

['NanoG5Kite' via weewx-user]

Battery status on different devices:

https://www.wxforum.net/index.php?topic=37373.msg408190#msg408190

Matthias

Am Dienstag, 28. Juli 2020 18:34:34 UTC+2 schrieb NanoG5Kite:
>
> Regarding Evowitt Battery Status. There are new Sensors like the WH 57 
> which report the battery status from 0-5 (5=fully charged), but former 
> sensors like the 7in1 with 0 or 1 (1=empty, to be replaced asap). There was 
> a useful threat in the wxforum.net telleing which sensors show which kind 
> of level, but can‘t find it back currently...
>
> Am Dienstag, 28. Juli 2020 18:04:55 UTC+2 schrieb Paul Anderson:
>>
>> Gary
>> First just a note that I was running v0.1.0b6 as a service and my GW1000 
>> lost it's WIFI connection. Actual dropped WIFI connecting by the GW1000.
>> Looking at the log I see that  the driver worked perfectly, it logged a 
>> connection failure after 3 attempts, but weewx itself kept running so that 
>> only the supplemental data from the GW1000 was lost. Once I relocated the 
>> GW1000 to a better location , without restarting WeeWX, the GW1000 data 
>> started flowing again. Perfect just the behavior I would want.
>>
>> Just updated to v0.1.0b7 here is what is returned for battery status:
>> wh31_ch2_batt: 0, wh31_ch4_batt: 0, wh31_ch5_batt: 0, wh31_ch7_batt: 0, 
>> wh57_batt: 5
>> So all sensors recognized, not sure of the meaning of "0" and "5" and why 
>> wh57 returns "5" All sensors installed with new batteries 3 days ago .
>>
>> On Tue, Jul 28, 2020 at 9:52 AM gjr80  wrote:
>>
>>> I have released v0.1.0b7 on Github 
>>> . b7 adds the battery 
>>> states to the default field map which should see battery states appear in 
>>> the loop packets. I expect there will still be some naming issues, 
>>> especially with WH65 and WH32. b7 also fixes a n issue where wind direction 
>>> was wrongly decoded..
>>>
>>> Those that have already installed the driver can download and install 
>>> v0.1.0b7 using the following commands depending on your WeeWX install type:
>>>
>>> for setup.py installs:
>>>
>>> $ sudo mv /home/weewx/bin/user/gw1000.py /home/weewx/bin/user/
>>> gw1000_orig.py
>>> $ sudo wget -P /home/weewx/bin/user https://
>>> raw.githubusercontent.com/gjr80/weewx-gw1000/v0.1.0b7/bin/user/gw1000.py 
>>> 
>>>
>>> for package installs:
>>>
>>> $ sudo mv /usr/share/weewx/user/gw1000.py /usr/share/weewx/user/
>>> gw1000_orig.py
>>> $ sudo wget -P /usr/share/weewx/user https://
>>> raw.githubusercontent.com/gjr80/weewx-gw1000/v0.1.0b7/bin/user/gw1000.py 
>>> 
>>>
>>> There has been no change to the [GW1000] structure so you can just 
>>> restart WeeWX/run v0.1.0b7 directly without further changes.
>>>
>>> Gary
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/4636d1ee-f397-4679-907c-45981a165199o%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/3a110944-2de1-4c17-8fec-df056ddfd6ffo%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

['NanoG5Kite' via weewx-user]

Regarding Evowitt Battery Status. There are new Sensors like the WH 57 
which report the battery status from 0-5 (5=fully charged), but former 
sensors like the 7in1 with 0 or 1 (1=empty, to be replaced asap). There was 
a useful threat in the wxforum.net telleing which sensors show which kind 
of level, but can‘t find it back currently...

Am Dienstag, 28. Juli 2020 18:04:55 UTC+2 schrieb Paul Anderson:
>
> Gary
> First just a note that I was running v0.1.0b6 as a service and my GW1000 
> lost it's WIFI connection. Actual dropped WIFI connecting by the GW1000.
> Looking at the log I see that  the driver worked perfectly, it logged a 
> connection failure after 3 attempts, but weewx itself kept running so that 
> only the supplemental data from the GW1000 was lost. Once I relocated the 
> GW1000 to a better location , without restarting WeeWX, the GW1000 data 
> started flowing again. Perfect just the behavior I would want.
>
> Just updated to v0.1.0b7 here is what is returned for battery status:
> wh31_ch2_batt: 0, wh31_ch4_batt: 0, wh31_ch5_batt: 0, wh31_ch7_batt: 0, 
> wh57_batt: 5
> So all sensors recognized, not sure of the meaning of "0" and "5" and why 
> wh57 returns "5" All sensors installed with new batteries 3 days ago .
>
> On Tue, Jul 28, 2020 at 9:52 AM gjr80 > 
> wrote:
>
>> I have released v0.1.0b7 on Github 
>> . b7 adds the battery 
>> states to the default field map which should see battery states appear in 
>> the loop packets. I expect there will still be some naming issues, 
>> especially with WH65 and WH32. b7 also fixes a n issue where wind direction 
>> was wrongly decoded..
>>
>> Those that have already installed the driver can download and install 
>> v0.1.0b7 using the following commands depending on your WeeWX install type:
>>
>> for setup.py installs:
>>
>> $ sudo mv /home/weewx/bin/user/gw1000.py /home/weewx/bin/user/gw1000_orig
>> .py
>> $ sudo wget -P /home/weewx/bin/user https://
>> raw.githubusercontent.com/gjr80/weewx-gw1000/v0.1.0b7/bin/user/gw1000.py 
>> 
>>
>> for package installs:
>>
>> $ sudo mv /usr/share/weewx/user/gw1000.py /usr/share/weewx/user/
>> gw1000_orig.py
>> $ sudo wget -P /usr/share/weewx/user https://
>> raw.githubusercontent.com/gjr80/weewx-gw1000/v0.1.0b7/bin/user/gw1000.py 
>> 
>>
>> There has been no change to the [GW1000] structure so you can just 
>> restart WeeWX/run v0.1.0b7 directly without further changes.
>>
>> Gary
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/4636d1ee-f397-4679-907c-45981a165199o%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/3d61d7d9-8ba1-4095-9d05-0d3101afba33o%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

[Paul R Anderson]

Gary
First just a note that I was running v0.1.0b6 as a service and my GW1000
lost it's WIFI connection. Actual dropped WIFI connecting by the GW1000.
Looking at the log I see that  the driver worked perfectly, it logged a
connection failure after 3 attempts, but weewx itself kept running so that
only the supplemental data from the GW1000 was lost. Once I relocated the
GW1000 to a better location , without restarting WeeWX, the GW1000 data
started flowing again. Perfect just the behavior I would want.

Just updated to v0.1.0b7 here is what is returned for battery status:
wh31_ch2_batt: 0, wh31_ch4_batt: 0, wh31_ch5_batt: 0, wh31_ch7_batt: 0,
wh57_batt: 5
So all sensors recognized, not sure of the meaning of "0" and "5" and why
wh57 returns "5" All sensors installed with new batteries 3 days ago .

On Tue, Jul 28, 2020 at 9:52 AM gjr80  wrote:

> I have released v0.1.0b7 on Github
> . b7 adds the battery
> states to the default field map which should see battery states appear in
> the loop packets. I expect there will still be some naming issues,
> especially with WH65 and WH32. b7 also fixes a n issue where wind direction
> was wrongly decoded..
>
> Those that have already installed the driver can download and install
> v0.1.0b7 using the following commands depending on your WeeWX install type:
>
> for setup.py installs:
>
> $ sudo mv /home/weewx/bin/user/gw1000.py /home/weewx/bin/user/gw1000_orig.
> py
> $ sudo wget -P /home/weewx/bin/user https://
> raw.githubusercontent.com/gjr80/weewx-gw1000/v0.1.0b7/bin/user/gw1000.py
> 
>
> for package installs:
>
> $ sudo mv /usr/share/weewx/user/gw1000.py /usr/share/weewx/user/
> gw1000_orig.py
> $ sudo wget -P /usr/share/weewx/user https://
> raw.githubusercontent.com/gjr80/weewx-gw1000/v0.1.0b7/bin/user/gw1000.py
> 
>
> There has been no change to the [GW1000] structure so you can just
> restart WeeWX/run v0.1.0b7 directly without further changes.
>
> Gary
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/4636d1ee-f397-4679-907c-45981a165199o%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/CAOAVAedB3RQLG80PLywoTPiz%3Dombk0AJcN8iUiX8CXUzyir6ag%40mail.gmail.com.

Re: [weewx-user] Re: DIY weather station + Weewx on Raspberry Pi - how to join them?

[Greg Troxel]

Tomasz Lewicki  writes:

> I don't know yet how my setup will work during winter. I live on latitude 
> of 51 N . 

I'm only at 42N, but find that here (Massachusetts) there is plenty of
sun in winter.   You do need a clear souhern horizon.

The advice that you may need a bigger panel is wise.  If you have a
battery that will run the station for a week, and a panel that will
recharge the battery in one sunny day, you will probably be ok.

-- 
You received this message because you are 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/rmid04ffxev.fsf%40s1.lexort.com.

Re: [weewx-user] Translation into german

['Hans Cilker' via weewx-user]

 Oh, and look in the "NOAA" subdirectory as well. 
I've taken a look there, at the moment, i have problems there wit german 
Ü,Ö, Ä .
Then the hedlines, is it a problem if i need more signs then at the Moment? 
for example: AVG will become Durchschnitt?


Vetti52 schrieb am Montag, 27. Juli 2020 um 20:57:02 UTC+2:

> And you will have to look into weewx.conf. Here are my adoptions:
>
> [Station]
> # Start of week (0=Monday, 6=Sunday)
> week_start = 0
>
> [StdReport]
> ...
> [[Defaults]]
>
> [[[Units]]]
> ...
> Labels
> day = " Tag", " Tage"  
> hour = " Stunde", " Stunden"
> minute = " Minute", " Minuten"
> second = " Sekunde", " Sekunden"
> ...
> [[[Labels]]]
>
> # Set to hemisphere abbreviations suitable for your location:
> hemispheres = N, S, O, W
>  
> # Generic labels, keyed by an observation type.
> Generic
> barometer = Barometer
> dewpoint = Taupunkt
> ET = ET
> heatindex = Hitzeindex
> inHumidity = Innenluftfeuchte
> inTemp = Innentemperatur
> outHumidity = Luftfeuchte
> outTemp = Außentemperatur
> radiation = Sonnenstrahlung
> rain = Regen
> rainRate = Regenrate
> UV = UV Index
> windDir = Windrichtung
> windGust = Böen
> windGustDir = Böenrichtung
> windSpeed = Windgeschwindigkeit
> windchill = Windchill
> windgustvec = Böenvektor
> windvec = Windvektor
>
>   [[[Almanac]]]
>
> # The labels to be used for the phases of the moon:
> moon_phases = Neumond, zunehmende Sichel, zunehmender 
> Halbmond, zweites Viertel, Vollmond, drittes Viertel, abnehmender Halbmond, 
> abnehmende Sichel
>
> All of the rest I found in the skin files, so far I could find it.
> Hope, that helps
>
> -Peter
>
> Am Montag, 27. Juli 2020 20:24:22 UTC+2 schrieb Tom Keffer:
>
>> Oh, and look in the "NOAA" subdirectory as well. That would be 
>> /etc/weewx/skins/Seasons/NOAA or /home/weewx/skins/Seasons/NOAA.
>>
>> On Mon, Jul 27, 2020 at 11:22 AM Tom Keffer  wrote:
>>
> If you are localizing the *Seasons* skin, the files would be found in 
>>> /etc/weewx/skins/Seasons if you did a package install. They would be found 
>>> in /home/weewx/skins/Seasons if you did a setup.py install.
>>>
>>> Look for files with suffixes of ".inc" and ".tmpl".
>>>
>>> -tk
>>>
>>> On Mon, Jul 27, 2020 at 11:18 AM 'Hans Cilker' via weewx-user <
>>> weewx...@googlegroups.com> wrote:
>>>
>> yea, that i found, but not where to change the Headlines and the parts 
 above, sorry may be thats to high for me. I was looking for : Monthly 
 Reports as an example, this i did not founf, also Current Conditions  and 
 so on, but i think its me who is not able to find that points, therefore 
 the question if ther is a place where i can found all together, or where 
 all files are written i have to change.

 tke...@gmail.com schrieb am Montag, 27. Juli 2020 um 19:27:00 UTC+2:

> Hello, Hans
>
> Did you look at the section *Localization 
> * in the 
> Customizing Guide? 
>
> On Mon, Jul 27, 2020 at 9:32 AM 'Hans Cilker' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>>
>> Hallo together, i've taken a look at the doc's and i did a search in 
>> the net, but nothing fit to my ideas. I want to translate the standard 
>> output into german, but i find not everything i want to translate. Is 
>> there 
>> inside the doc's a place, where i can find in which files i ve to look 
>> for 
>> finding whats to translate? For example, i found nothing wher to 
>> translat " 
>> Monthly Reports: and Yearly Report. Thanks a lot
>> Hans
>>
>> -- 
>> You received this message because you are 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/c02044f3-2aa2-4931-9e07-1e83e019b1d9n%40googlegroups.com
>>  
>> 
>> .
>>
> -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.

>>> To unsubscribe from this group and stop receiving emails from it, send 
 an email to weewx...@googlegroups.com.
>>>
>>>
 To view this discussion on the web visit 
 

Re: [weewx-user] Re: DIY weather station + Weewx on Raspberry Pi - how to join them?

[Tomasz Lewicki]

W dniu wtorek, 28 lipca 2020 16:29:06 UTC+2 użytkownik Norbert F napisał:
>
> I dont think its enough if you are in a area with "Winter", you have very 
> short and flat sun and sometimes weeks with cloudy sky and nebula. I think 
> you need a big panel and strong akkus.


I don't know yet how my setup will work during winter. I live on latitude 
of 51 N . 

-- 
You received this message because you are 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/940af59f-40a6-47ac-8a80-80dd774a52e1o%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

[gary....@gmail.com]

My wind results have been corrected.

On Tuesday, July 28, 2020 at 9:55:22 AM UTC-4 gjr80 wrote:

> Bill, the incorrect wind direction decode likely accounts for your wind 
> direction discrepancies. Not sure about the pressure issues, as far as I am 
> aware pressure is being correctly decoded. I will look into it further in 
> the morning.
>
> Gary
>
> On Monday, 27 July 2020 20:03:01 UTC+10, Bill Arthur wrote:
>>
>> Thanks Gary.  
>> Your instructions worked perfectly.
>>
>> I'm still seeing a couple of things. Here are links to two reporting 
>> stations. They both receive data from the same GW-1000
>> The -1 station uses the old push method. The -5 station uses the new API 
>> method.  I'm seeing differences in wind direction and barometer
>> -1 Station 
>> -5 Station 
>>
>

-- 
You received this message because you are 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/640a1857-01a3-498d-9819-ab152372ae2fn%40googlegroups.com.

Re: [weewx-user] Re: DIY weather station + Weewx on Raspberry Pi - how to join them?

[spydr]

I have a similar setup.  Multiple esp8266’s. Posting data to mqtt broker hosted 
on the rpi.  From there you need the mqtt driver to get the data into weewx.  I 
can troubleshoot the mqtt data with MQTTool.  There are others.

-- 
You received this message because you are 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/f602511b-a9a7-46aa-a741-f019f6f244aco%40googlegroups.com.

Re: [weewx-user] Re: DIY weather station + Weewx on Raspberry Pi - how to join them?

[Norbert F]

I dont think its enough if you are in a area with "Winter", you have very short 
and flat sun and sometimes weeks with cloudy sky and nebula. I think you need a 
big panel and strong akkus.

-- 
You received this message because you are 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/8c6821a3-9476-4bdf-ae68-a760ac6ce9e9o%40googlegroups.com.

Re: [weewx-user] Re: DIY weather station + Weewx on Raspberry Pi - how to join them?

[Tomasz Lewicki]

W dniu wtorek, 28 lipca 2020 15:49:24 UTC+2 użytkownik Norbert F napisał:
>
> Its USB powered because in Winter there is snow on the panel in my area 
> and so solar dosent work.


Yes, I'm afraid of this too. But I will install the station in such manner 
that I could remove the snow easily from the solar panel. Now I'm testing 
it at home, in the room, trying to "deep sleep" ESP8266 for 1 minutre, then 
wake, send the data and sleep again. 

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

Re: [weewx-user] FTP Stopped Working After Updating Station Hardware

[Tom Keffer]

Could you please post the results of the database query? I want to compare
the timestamps with the raw data output of the WeatherFlow.

Also, is this problem consistent? Or, does it come and go?

-tk

On Mon, Jul 27, 2020 at 1:16 PM Pat W.  wrote:

> Tom,
>
> 1. Using your sqlite commands (thanks!) I see only one entry in the
> database, and its from yesterday when I was fiddling with things.
>
> 2. Same here, html and png files were created at least once yesterday.
> Nothing today.
>
> Pat W.
>
> On Sunday, July 26, 2020 at 6:22:11 PM UTC-5, Tom Keffer wrote:
>>
>> I have my suspicions about what's going on here, but first let me ask you
>> two questions.
>>
>> 1. Is there any evidence that anything is getting stored in the database?
>> Take a look in your database. This will show the timestamps of the last 10
>> records that have been stored in the database:
>>
>> *sqlite3 /var/lib/weewx/weewx.sdb*
>> sqlite> *select datetime(dateTime,'unixepoch','localtime') from archive
>> order by dateTime desc limit 10;*
>>
>> 2. Is there any evidence that reports have been generated at all (let
>> alone FTP'd)?
>>
>>
>> *ls -l /var/www/html/weewx*
>>
>> -tk
>>
>> On Sun, Jul 26, 2020 at 3:24 PM Pat W.  wrote:
>>
>>> Hi All,
>>>
>>> I've been using weewx for a couple years with an old WMR-918 and all
>>> works fine, including an FTP upload to my personal web page every five
>>> minutes. Recently bought a Weatherflow Tempest and installed the
>>> WeatherFlowUDP extension. Weewx appears to be receiving data from the
>>> station properly, but the FTP function has stopped working and I can't find
>>> any references to it in the syslog. I reinstalled weewx from scratch
>>> (installed via apt-get on Raspberry Pi 4) after the hardware change to no
>>> avail.
>>>
>>> I'm a linux novice but can find my way around. This one has me stumped.
>>> Any help is appreciated. mylog and wee_debug files attached
>>>
>>> Pat W.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/d5cd1209-4b4c-4165-b857-39f237300f8co%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/c74fba6c-92cf-49aa-8732-9302e8ff8525o%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/CAPq0zECbFKxGD%3DpFBgkB1hSHaGfQiGLMoXuh-tv8x8m1kM2P-A%40mail.gmail.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

[gjr80]

Bill, the incorrect wind direction decode likely accounts for your wind 
direction discrepancies. Not sure about the pressure issues, as far as I am 
aware pressure is being correctly decoded. I will look into it further in 
the morning.

Gary

On Monday, 27 July 2020 20:03:01 UTC+10, Bill Arthur wrote:
>
> Thanks Gary.  
> Your instructions worked perfectly.
>
> I'm still seeing a couple of things. Here are links to two reporting 
> stations. They both receive data from the same GW-1000
> The -1 station uses the old push method. The -5 station uses the new API 
> method.  I'm seeing differences in wind direction and barometer
> -1 Station 
> -5 Station 
>

-- 
You received this message because you are 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/5d0095b0-4d36-499b-be81-53c83a48a0b1o%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

[gjr80]

I have released v0.1.0b7 on Github 
. b7 adds the battery 
states to the default field map which should see battery states appear in 
the loop packets. I expect there will still be some naming issues, 
especially with WH65 and WH32. b7 also fixes a n issue where wind direction 
was wrongly decoded..

Those that have already installed the driver can download and install 
v0.1.0b7 using the following commands depending on your WeeWX install type:

for setup.py installs:

$ sudo mv /home/weewx/bin/user/gw1000.py /home/weewx/bin/user/gw1000_orig.py
$ sudo wget -P /home/weewx/bin/user https://
raw.githubusercontent.com/gjr80/weewx-gw1000/v0.1.0b7/bin/user/gw1000.py 


for package installs:

$ sudo mv /usr/share/weewx/user/gw1000.py /usr/share/weewx/user/gw1000_orig.
py
$ sudo wget -P /usr/share/weewx/user https://
raw.githubusercontent.com/gjr80/weewx-gw1000/v0.1.0b7/bin/user/gw1000.py 


There has been no change to the [GW1000] structure so you can just restart 
WeeWX/run v0.1.0b7 directly without further changes.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4636d1ee-f397-4679-907c-45981a165199o%40googlegroups.com.

Re: [weewx-user] Re: DIY weather station + Weewx on Raspberry Pi - how to join them?

[Norbert F]

Its USB powered because in Winter there is snow on the panel in my area and so 
solar dosent work.

-- 
You received this message because you are 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/4bd91266-5198-4567-bf74-8315b391f057o%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

[gjr80]

Thanks Ian, that confirms the last one.

Gary

On Tuesday, 28 July 2020 16:41:53 UTC+10, steeple ian wrote:
>
> Gary,
>
> This is my output (my GW1000 is 868MHz): -
>
> Using configuration file /home/weewx/weewx.conf
>
> Interrogating GW1000 at 192.168.1.234:45000
>
> GW1000 frequency: 1 (Unknown)
> GW1000 sensor type: 1 (WH65)
> GW1000 decoded UTC: 2020-07-28 07:37:39 UTC (1595921859)
> GW1000 timezone: 39
>
>
>
> On Tue, 28 Jul 2020 at 02:41, gjr80  wrote:
>
>> Yes, not surprised, am still working through sensor names and the API to 
>> get the code right. Fortunately, this disconnect does not affect the 
>> observational data only battery state field names and some of the 
>> 'informational' commands such as --system-params. Once I get the battery 
>> states into the loop packets they can be easily fixed (temporarily) with a 
>> few field map extensions.
>>
>> Gary
>>
>> On Tuesday, 28 July 2020 11:04:45 UTC+10, gary@gmail.com wrote:
>>>
>>> Though this is not a WH65
>>>
>>> I have a GW1000, WS68, WH40, WH32-EP, WH32B
>>>
>>> On Monday, July 27, 2020 at 8:58:54 PM UTC-4 gary@gmail.com wrote:
>>>
 This is a 915 MHz unit

 Interrogating GW1000 at 10.10.100.125:45000

 GW1000 frequency: 2 (Unknown)
 GW1000 sensor type: 1 (WH65)
 GW1000 decoded UTC: 2020-07-27 20:57:43 UTC (1595883463)
 GW1000 timezone: 19


 On Monday, July 27, 2020 at 8:53:36 PM UTC-4 gjr80 wrote:

> v0.1.0b6 added the --system-params command line option to the driver 
> to display a number of GW1000 system parameters, eg:
>
> GW1000 frequency: 0 (433MHz)
> GW1000 sensor type: 0 (WH24)
> GW1000 decoded UTC: 2020-07-28 10:31:46 UTC (1595932306)
> GW1000 timezone: 94
>
> Whilst I know which byte to look at for the frequency, and what value 
> represents 433MHz as used on my GW1000, I do not know what value is used 
> to 
> represent operation on 868MHZ and 915MHz. Was wondering if any users of 
> v0.1.0b6 that use a GW1000 operating on 868MHz or 915MHZ could post the 
> frequency their GW1000 uses as well as the output from the following 
> command (adjusting python version and path as required):
>
> $ PYTHONPATH=/home/weewx/bin python -m user.gw1000 --system-params
>
> I don't believe any of the information is particularly sensitive, but 
> if you are concerned I really just need to know the frequncy your GW1000 
> operates on as well as the line starting 'GW1000 frequency'. If you don't 
> know what frequency your GW1000 operates on it should be printed on the 
> back of your GW1000 (well at least mine is like that!)
>
> thanks,
> Gary
>
 -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/d6b32000-d7a8-483d-9822-6b47d24e1b23o%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/40dfa6ce-c878-42b4-aa9b-ea72730acf29o%40googlegroups.com.

Re: [weewx-user] Re: DIY weather station + Weewx on Raspberry Pi - how to join them?

[Tomasz Lewicki]

W dniu wtorek, 28 lipca 2020 15:31:22 UTC+2 użytkownik Norbert F napisał:
>
> I use a ESP8266 with "tasmota" for my homemade Weatherstation. Its easy to 
> configure, didnt need much power, sends mqtt. Tasmota knows the most 
> Sensors by default and send all mqtt via wifi to weewx-mqttSubscribe driver.


I use ESPEasy instead of Tasmota but basically it is the same. Is your 
station powered by USB or solar panel?

-- 
You received this message because you are 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/a07b05d7-05f4-4eed-9105-36fcb0de0bf3o%40googlegroups.com.

Re: [weewx-user] Re: DIY weather station + Weewx on Raspberry Pi - how to join them?

[Norbert F]

I use a ESP8266 with "tasmota" for my homemade Weatherstation. Its easy to 
configure, didnt need much power, sends mqtt. Tasmota knows the most Sensors by 
default and send all mqtt via wifi to weewx-mqttSubscribe driver.

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

Re: [weewx-user] Re: Belchertown MQTT live stats problem

[Graham Eddy]

maybe they turned off unencrypted mode.
try turning on SSL and use encrypted websockets port (8081 on 
test.mosquitto.org )

re logs, need option in mosquitto.conf ‘log_type all’ (or at least ‘log_type 
websockets’) plus (i haven’t tried this) ‘websockets_log_level {some flags}’ - 
latter defaults to off

> On 28 Jul 2020, at 10:30 pm, Don Roberts  wrote:
> 
> I'm experiencing this same thing, and I'm using a public MQTT broker. Didn't 
> change anything.
> 
> don
> 
> On Friday, July 24, 2020 at 11:26:40 PM UTC-5, Scott Grayban wrote:
> For over a year my live stats has been working flawlessly until recently. Now 
> it says Failed connecting to the weather station
> 
> Looking at the dev console in chrome I am seeing this for the error and not 
> sure how to test this out to see what is going on.
> 
> mqttws31.min.js:36 WebSocket connection to 'ws://X.X.X.X:9001/mqtt' failed: 
> Connection closed before receiving a handshake response
> 
> The MQTT logs are only showing connections via port 1883.
> 
> -- 
> You received this message because you are 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/73f84443-63ed-452f-8f2d-2cf65bfa0405o%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/7D44F99A-801E-46F6-8BE1-1B048F7CA890%40gmail.com.

[weewx-user] Re: Belchertown MQTT live stats problem

[Don Roberts]

I'm experiencing this same thing, and I'm using a public MQTT broker. 
Didn't change anything.

don

On Friday, July 24, 2020 at 11:26:40 PM UTC-5, Scott Grayban wrote:
>
> For over a year my live stats has been working flawlessly until recently. 
> Now it says *Failed connecting to the weather station*
>
> Looking at the dev console in chrome I am seeing this for the error and 
> not sure how to test this out to see what is going on.
>
> mqttws31.min.js:36 WebSocket connection to 'ws://X.X.X.X:9001/mqtt' 
> failed: Connection closed before receiving a handshake response
>
> The MQTT logs are only showing connections via port 1883.
>

-- 
You received this message because you are 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/73f84443-63ed-452f-8f2d-2cf65bfa0405o%40googlegroups.com.

Re: [weewx-user] Re: DIY weather station + Weewx on Raspberry Pi - how to join them?

[Rob Shorrock]

Thanks , now that you showed me it's possible to get data into weewx I feel
a zeropi weather station is the way to go. The zeropi would have to be
located outside on the mast  with  the sensors and powered with a solar
battery.  It might be a challenge getting an indoor temp sensor connected.







On Tue, 28 Jul 2020 at 10:16, Michael Bruski 
wrote:

>
> First of all you need to write some code on the Raspberry to get your
> sensor data from the Thingspeak channel they are written to.   This link
> 
> will give you an idea how to do that on the pi.  Once you are able to read
> all of your channels, you can write them to a temporary file and use the
> WeeWX extension fileParser to pick it up.   Check out this link
> 
> for details.   I used it to setup a fileParser to collect my sensor info so
> that WeeWX could reap it and found the method works well.   My setup is
> somewhat different than yours in that I have my sensors connected directly
> to the RPi so I simply use my sensor program to read the data and then
> write it to a file.   WeeWX knows where to find that file and grabs it at
> the interval specified.  The author gives you a sample python program to
> create a data file containing your sensor data.
>
> Hope that helps.
>
> On Friday, July 24, 2020 at 4:03:15 AM UTC-4, Tomasz Lewicki wrote:
>>
>> Dear Weewx users.
>> It's my first post. I looked into wiki and docs but still are stuck so I
>> ask here.
>>
>> My configuration is as follows:
>>
>> 1. DIY solar powered WiFi weather station (built from here:
>> https://www.instructables.com/id/Solar-Powered-WiFi-Weather-Station-V20/
>> 
>> - the project known to some of you, I suppose), based on Wemos D1 Mini Pro
>> (ESP8266) with own IP address in local network
>>
>> 2. Raspberry Pi 3 used as cheap airplane tracking station (ADS-B stick).
>>
>> Now I want to extend RPi with Weewx fed and weather station data.
>>
>> Because my station is hand-made, I can't use any of standard hardware
>> drivers. As far I installed Weewx with Simulator driver and it works -
>> http://stationIP/weewx shows many plots and data. I was even able to
>> send it periodically to my other, public available, webserver by FTP.
>>
>> But of course I don't need fake, static data. I want to RPi with Weewx to
>> communicate periodically with weather station, grab the data (or weather
>> station push it periodically to RPi, which is the same, I suppose) and view
>> it live via the webserver.
>>
>> So finally I come to the important question: is such connection possible?
>> I suppose yes, but my experience with such hardware is very poor and I
>> don't know where should I go. I'm experienced Linux user so it is no
>> problem in this field. I only expect that someone will point me in the
>> right direction, some keyword to look for. Maybe someone has similar
>> configuration and could help?
>>
> --
> 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/MwNOPj7is6E/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/a72d2d1d-7852-4be0-a8a7-71cd6b8a7722o%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/CANqgCAaxkLeLcXsY-JHWgX%2BJ_oXr0rzDWgmo8-WF%3DrUDKKejvQ%40mail.gmail.com.

[weewx-user] Re: DIY weather station + Weewx on Raspberry Pi - how to join them?

[Tomasz Lewicki]

Thank you all for the answers and tips. The right answer was MQTT and 
topics around it :)

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6d6fd554-3d2a-45dd-911f-5e37b193feb1o%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

[steeple ian]

So with a modification to the parameters section I get: -

Using configuration file /home/weewx/weewx.conf

Interrogating GW1000 at 192.168.1.234:45000

GW1000 frequency: 1 (868Mhz)
GW1000 sensor type: 1 (WH65)
GW1000 decoded UTC: 2020-07-28 07:52:28 UTC (1595922748)
GW1000 timezone: 39


On Tue, 28 Jul 2020 at 07:41, steeple ian  wrote:

> Gary,
>
> This is my output (my GW1000 is 868MHz): -
>
> Using configuration file /home/weewx/weewx.conf
>
> Interrogating GW1000 at 192.168.1.234:45000
>
> GW1000 frequency: 1 (Unknown)
> GW1000 sensor type: 1 (WH65)
> GW1000 decoded UTC: 2020-07-28 07:37:39 UTC (1595921859)
> GW1000 timezone: 39
>
>
>
> On Tue, 28 Jul 2020 at 02:41, gjr80  wrote:
>
>> Yes, not surprised, am still working through sensor names and the API to
>> get the code right. Fortunately, this disconnect does not affect the
>> observational data only battery state field names and some of the
>> 'informational' commands such as --system-params. Once I get the battery
>> states into the loop packets they can be easily fixed (temporarily) with a
>> few field map extensions.
>>
>> Gary
>>
>> On Tuesday, 28 July 2020 11:04:45 UTC+10, gary@gmail.com wrote:
>>>
>>> Though this is not a WH65
>>>
>>> I have a GW1000, WS68, WH40, WH32-EP, WH32B
>>>
>>> On Monday, July 27, 2020 at 8:58:54 PM UTC-4 gary@gmail.com wrote:
>>>
 This is a 915 MHz unit

 Interrogating GW1000 at 10.10.100.125:45000

 GW1000 frequency: 2 (Unknown)
 GW1000 sensor type: 1 (WH65)
 GW1000 decoded UTC: 2020-07-27 20:57:43 UTC (1595883463)
 GW1000 timezone: 19


 On Monday, July 27, 2020 at 8:53:36 PM UTC-4 gjr80 wrote:

> v0.1.0b6 added the --system-params command line option to the driver
> to display a number of GW1000 system parameters, eg:
>
> GW1000 frequency: 0 (433MHz)
> GW1000 sensor type: 0 (WH24)
> GW1000 decoded UTC: 2020-07-28 10:31:46 UTC (1595932306)
> GW1000 timezone: 94
>
> Whilst I know which byte to look at for the frequency, and what value
> represents 433MHz as used on my GW1000, I do not know what value is used 
> to
> represent operation on 868MHZ and 915MHz. Was wondering if any users of
> v0.1.0b6 that use a GW1000 operating on 868MHz or 915MHZ could post the
> frequency their GW1000 uses as well as the output from the following
> command (adjusting python version and path as required):
>
> $ PYTHONPATH=/home/weewx/bin python -m user.gw1000 --system-params
>
> I don't believe any of the information is particularly sensitive, but
> if you are concerned I really just need to know the frequncy your GW1000
> operates on as well as the line starting 'GW1000 frequency'. If you don't
> know what frequency your GW1000 operates on it should be printed on the
> back of your GW1000 (well at least mine is like that!)
>
> thanks,
> Gary
>
 --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/d6b32000-d7a8-483d-9822-6b47d24e1b23o%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/CADASSaQBfUKcoBGaCz9aSQXdCXyHisWMujCMqRefMmh5qjYkKg%40mail.gmail.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

[steeple ian]

Gary,

This is my output (my GW1000 is 868MHz): -

Using configuration file /home/weewx/weewx.conf

Interrogating GW1000 at 192.168.1.234:45000

GW1000 frequency: 1 (Unknown)
GW1000 sensor type: 1 (WH65)
GW1000 decoded UTC: 2020-07-28 07:37:39 UTC (1595921859)
GW1000 timezone: 39



On Tue, 28 Jul 2020 at 02:41, gjr80  wrote:

> Yes, not surprised, am still working through sensor names and the API to
> get the code right. Fortunately, this disconnect does not affect the
> observational data only battery state field names and some of the
> 'informational' commands such as --system-params. Once I get the battery
> states into the loop packets they can be easily fixed (temporarily) with a
> few field map extensions.
>
> Gary
>
> On Tuesday, 28 July 2020 11:04:45 UTC+10, gary@gmail.com wrote:
>>
>> Though this is not a WH65
>>
>> I have a GW1000, WS68, WH40, WH32-EP, WH32B
>>
>> On Monday, July 27, 2020 at 8:58:54 PM UTC-4 gary@gmail.com wrote:
>>
>>> This is a 915 MHz unit
>>>
>>> Interrogating GW1000 at 10.10.100.125:45000
>>>
>>> GW1000 frequency: 2 (Unknown)
>>> GW1000 sensor type: 1 (WH65)
>>> GW1000 decoded UTC: 2020-07-27 20:57:43 UTC (1595883463)
>>> GW1000 timezone: 19
>>>
>>>
>>> On Monday, July 27, 2020 at 8:53:36 PM UTC-4 gjr80 wrote:
>>>
 v0.1.0b6 added the --system-params command line option to the driver
 to display a number of GW1000 system parameters, eg:

 GW1000 frequency: 0 (433MHz)
 GW1000 sensor type: 0 (WH24)
 GW1000 decoded UTC: 2020-07-28 10:31:46 UTC (1595932306)
 GW1000 timezone: 94

 Whilst I know which byte to look at for the frequency, and what value
 represents 433MHz as used on my GW1000, I do not know what value is used to
 represent operation on 868MHZ and 915MHz. Was wondering if any users of
 v0.1.0b6 that use a GW1000 operating on 868MHz or 915MHZ could post the
 frequency their GW1000 uses as well as the output from the following
 command (adjusting python version and path as required):

 $ PYTHONPATH=/home/weewx/bin python -m user.gw1000 --system-params

 I don't believe any of the information is particularly sensitive, but
 if you are concerned I really just need to know the frequncy your GW1000
 operates on as well as the line starting 'GW1000 frequency'. If you don't
 know what frequency your GW1000 operates on it should be printed on the
 back of your GW1000 (well at least mine is like that!)

 thanks,
 Gary

>>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/d6b32000-d7a8-483d-9822-6b47d24e1b23o%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/CADASSaTz_2cwJWpabn%2BLpG8wdt%3D-QEVijSUkE_XbDmXWYpZw6g%40mail.gmail.com.