Re: [weewx-user] PWSWeather suddenly stopped working

[vince]

There is a massive AWS outage on the east coast, so it's very possible 
that's the cause...

-- 
You received this message because you are 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/411591ef-8982-43da-a83d-8c0da4fcef27n%40googlegroups.com.

[weewx-user] Can't get weewx working on a new server

[kiwigander]

Hi all, I'm trying to move weewx to a new computer but getting nowhere fast.

The weather station is a Vantage Pro2 with serial data logger (not USB) 
communicating with an RS232 port on my old Dell D520 running Linux Mint 
17.  I'm shifting my server functions to a new fanless mini-PC with RS232 
ports.

The old setup was installed around 2012 and I don't recall updating it 
(other than the OS) since.  

The new installation is weewx 4.2.0.  I tried the .deb package; when I 
couldn't get it working I purged it and tried again with the setup.py 
method and Python 3.  The file structure now looks rather like the old 
setup.

Anyway, I can't get the new installation to work.  No html page is 
created.  Here is a snippet of output from dmesg:

Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.drivers.vantage: 
Get_data_with_crc16; try #1 failed: Expected to read 3 chars; got 2 instead
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.drivers.vantage: Timeout in 
get_data_with_crc16
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.drivers.vantage: Gentle wake up 
of console successful
Nov 26 15:56:23 XCY weewx[3380] ERROR weewx.drivers.vantage: No  
received from console
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.drivers.vantage: Rude wake up 
of console successful
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.drivers.vantage: ISS ID is 1
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.drivers.vantage: Hardware name: 
Vantage Pro2
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Loading service 
weewx.engine.StdTimeSynch
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdTimeSynch
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Loading service 
weewx.engine.StdConvert
Nov 26 15:56:23 XCY weewx[3380] INFO weewx.engine: StdConvert target unit 
is 0x1
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdConvert
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Loading service 
weewx.engine.StdCalibrate
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdCalibrate
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Loading service 
weewx.engine.StdQC
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdQC
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Loading service 
weewx.wxservices.StdWXCalculate
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.manager: Daily summary version 
is 2
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Finished loading 
service weewx.wxservices.StdWXCalculate
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdWXXTypes
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdWXXTypes
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdPressureCooker
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdPressureCooker
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdRainRater
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdRainRater
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Loading service 
weewx.engine.StdArchive
Nov 26 15:56:23 XCY weewx[3380] INFO weewx.engine: Archive will use data 
binding wx_binding
Nov 26 15:56:23 XCY weewx[3380] INFO weewx.engine: Record generation will 
be attempted in 'hardware'
Nov 26 15:56:23 XCY weewx[3380] ERROR weewx.engine: The archive interval in 
the configuration file (300) does not match the station hardware interval 
(60).
Nov 26 15:56:23 XCY weewx[3380] INFO weewx.engine: Using archive interval 
of 60 seconds (specified by hardware)
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Use LOOP data in hi/low 
calculations: 1
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdArchive
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Loading service 
weewx.restx.StdStationRegistry
Nov 26 15:56:23 XCY weewx[3380] INFO weewx.restx: StationRegistry: 
Registration not requested.
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdStationRegistry
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Loading service 
weewx.restx.StdWunderground
Nov 26 15:56:23 XCY weewx[3380] INFO weewx.restx: Wunderground: Posting not 
enabled.
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdWunderground
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Loading service 
weewx.restx.StdPWSweather
Nov 26 15:56:23 XCY weewx[3380] INFO weewx.restx: PWSweather: Posting not 
enabled.
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdPWSweather
Nov 26 15:56:23 XCY weewx[3380] DEBUG weewx.engine: Loading service 
weewx.restx.StdCWOP
Nov 26 15:56:23 XCY weewx[3380] INFO weewx.restx: CWOP: Posting not enabled.

[weewx-user] Re: Errors started today?

[iain MacDonnell]

https://status.aerisweather.com/

~iain


On Wednesday, November 25, 2020 at 5:43:33 PM UTC-8 blu...@gmail.com wrote:

>
>- Station hardware: Vantage Vue
>- WeeWX version: 4.2.0
>- Belchertown Skin Version: 1.2b6
>
>
> On Wednesday, November 25, 2020 at 8:38:06 PM UTC-5 blu...@gmail.com 
> wrote:
>
>> I've been running for months, with no problems.  All of a sudden I'm 
>> seeing this in log:
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine: Caught 
>> unrecoverable exception in generator 
>> 'weewx.cheetahgenerator.CheetahGenerator'
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>> list indices must be integers, not str
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>> Traceback (most recent call last):
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/reportengine.py", line 196, in run
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>> obj.start()
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/reportengine.py", line 281, in start
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>> self.run()
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 149, in run
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>> ngen = self.generate(gen_dict[section_name], self.gen_ts)
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 219, in generate
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>> ngen += self.generate(section[subsection], gen_ts)
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 219, in generate
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>> ngen += self.generate(section[subsection], gen_ts)
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 308, in generate
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>> default_binding)
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 379, in 
>> _getSearchList
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>> searchList += obj.get_extension_list(timespan, db_lookup)
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/user/belchertown.py", line 880, in 
>> get_extension_list
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>> current_obs_summary = aeris_coded_weather( 
>> data["current"][0]["response"]["ob"]["weatherPrimaryCoded"] )
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>> TypeError: list indices must be integers, not str
>>
>> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>> Generator terminated
>>
>

-- 
You received this message because you are 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/1d19b7c4-9f68-4499-acb4-4e2a8e173004n%40googlegroups.com.

[weewx-user] Re: Errors started today?

[blu...@gmail.com]

   
   - Station hardware: Vantage Vue
   - WeeWX version: 4.2.0
   - Belchertown Skin Version: 1.2b6


On Wednesday, November 25, 2020 at 8:38:06 PM UTC-5 blu...@gmail.com wrote:

> I've been running for months, with no problems.  All of a sudden I'm 
> seeing this in log:
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine: Caught 
> unrecoverable exception in generator 
> 'weewx.cheetahgenerator.CheetahGenerator'
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
> list indices must be integers, not str
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
> Traceback (most recent call last):
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>   File "/usr/share/weewx/weewx/reportengine.py", line 196, in run
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
> obj.start()
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>   File "/usr/share/weewx/weewx/reportengine.py", line 281, in start
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
> self.run()
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 149, in run
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
> ngen = self.generate(gen_dict[section_name], self.gen_ts)
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 219, in generate
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
> ngen += self.generate(section[subsection], gen_ts)
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 219, in generate
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
> ngen += self.generate(section[subsection], gen_ts)
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 308, in generate
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
> default_binding)
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 379, in 
> _getSearchList
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
> searchList += obj.get_extension_list(timespan, db_lookup)
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
>   File "/usr/share/weewx/user/belchertown.py", line 880, in 
> get_extension_list
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
> current_obs_summary = aeris_coded_weather( 
> data["current"][0]["response"]["ob"]["weatherPrimaryCoded"] )
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
> TypeError: list indices must be integers, not str
>
> Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
> Generator terminated
>

-- 
You received this message because you are 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/b959cf5a-83a9-4341-a2f0-a4dc6da521c7n%40googlegroups.com.

[weewx-user] Errors started today?

[blu...@gmail.com]

I've been running for months, with no problems.  All of a sudden I'm seeing 
this in log:

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 
'weewx.cheetahgenerator.CheetahGenerator'

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
list indices must be integers, not str

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
Traceback (most recent call last):

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/reportengine.py", line 196, in run

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine: 
  obj.start()

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/reportengine.py", line 281, in start

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine: 
  self.run()

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/cheetahgenerator.py", line 149, in run

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine: 
  ngen = self.generate(gen_dict[section_name], self.gen_ts)

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/cheetahgenerator.py", line 219, in generate

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine: 
  ngen += self.generate(section[subsection], gen_ts)

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/cheetahgenerator.py", line 219, in generate

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine: 
  ngen += self.generate(section[subsection], gen_ts)

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/cheetahgenerator.py", line 308, in generate

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine: 
  default_binding)

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/cheetahgenerator.py", line 379, in 
_getSearchList

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine: 
  searchList += obj.get_extension_list(timespan, db_lookup)

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine: 
File "/usr/share/weewx/user/belchertown.py", line 880, in get_extension_list

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine: 
  current_obs_summary = aeris_coded_weather( 
data["current"][0]["response"]["ob"]["weatherPrimaryCoded"] )

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
TypeError: list indices must be integers, not str

Nov 25 20:35:21 acer weewx[19864] ERROR weewx.reportengine:   
Generator terminated

-- 
You received this message because you are 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/7e5579c7-91d1-4e8f-993e-dfa0308806e6n%40googlegroups.com.

Re: [weewx-user] PWSWeather suddenly stopped working

[Tom Keffer]

Just took a look, and mine is doing the same: The log looks normal, but the
station is appearing as "inactive" on their website.

I also checked their HTTP Response to see if maybe they changed their
protocol for posting failures, but it is unchanged.

Seems to be a problem on their end.

-tk

On Wed, Nov 25, 2020 at 5:10 PM dse...@dseven.org  wrote:

>
> Suddenly PWSWeather is showing my station as inactive. It shows data up to
> 10:20am PDT today (Nov 2th). I noticed because my "current" icon in
> Belchertown (using Aeris) stopped working. My log still shows the usual
> updates every 5 mins:
>
> Nov 25 17:05:23 4c8abe33c977 weewx[4488] INFO weewx.restx: PWSWeather:
> Published record 2020-11-25 17:05:00 PST (1606352700)
>
> Either weewx is not catching some error, or PWSWeather is accepting the
> data but not processing it, I guess?
>
> Anyone else pushing to PWSWeather?
>
> ~iain
>
>
>
>
> --
> You received this message because you are 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/9a2ef53f-b49c-4f59-8114-db3972e68892n%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/CAPq0zECs_EDVTo%3DmVG%3DS2d_OGLhY-w4_Xj-rOOM0fjA3Vd7-DA%40mail.gmail.com.

[weewx-user] PWSWeather suddenly stopped working

[dse...@dseven.org]

Suddenly PWSWeather is showing my station as inactive. It shows data up to 
10:20am PDT today (Nov 2th). I noticed because my "current" icon in 
Belchertown (using Aeris) stopped working. My log still shows the usual 
updates every 5 mins:

Nov 25 17:05:23 4c8abe33c977 weewx[4488] INFO weewx.restx: PWSWeather: 
Published record 2020-11-25 17:05:00 PST (1606352700)

Either weewx is not catching some error, or PWSWeather is accepting the 
data but not processing it, I guess?

Anyone else pushing to PWSWeather?

~iain




-- 
You received this message because you are 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/9a2ef53f-b49c-4f59-8114-db3972e68892n%40googlegroups.com.

[weewx-user] Re: upload issue with steelseriesgauges

[gjr80]

Hi,

If you are using the WeeWX SteelSeries Weather Gauges extension 
 then gauge-data.txt (the 
data file used by the SteelSeries Weather Gauges) is only generated every 
archive period (for example, every five minutes). The setting you refer to 
in gauges.is is how often the SteelSeries Weather Gauges code reads 
gauge-data.txt and refreshes the displayed gauges. This means your gauges 
effectively update once per archive period irrespective of the setting in 
gauges.js, there is nothing you can you about this with this setup.

You can use the weewx-rtgd extension 
 to generate a loop 
based gauge-data.txt which will allow your gauges to effectively update 
whenever your station emits loop data.

Gary

On Wednesday, 25 November 2020 at 23:59:14 UTC+10 hobbyl...@gmail.com wrote:

> i have setting in steelseriesgauges in gauge.js uploading in 48 seconds, 
> but data uploading every 5 minutes , like stantard pages of weewx.i have 
> the 4.2.0 version of weewx. thank you.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/facc6cf5-88ba-4297-85d8-1cfdea519been%40googlegroups.com.

[weewx-user] Re: Steps to upgrade Weewx 3.9.2 to 4.2

[vince]

On Wednesday, November 25, 2020 at 7:50:02 AM UTC-8 fvirg...@gmail.com 
wrote:

> I would like to upgrade my weewx version 3.9.2 to 4.2.
> I downloaded version 4.2 in the / home folder and here I stopped. Could 
> you help me with the next steps?
>
>
http://www.weewx.com/docs/upgrading.htm

-- 
You received this message because you are 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/82d756c1-2d87-4754-8239-32496ebdc99en%40googlegroups.com.

[weewx-user] Steps to upgrade Weewx 3.9.2 to 4.2

[Francesco Fasano]

Hello,
I would like to upgrade my weewx version 3.9.2 to 4.2.
Is the Python version 2.7.16 okay or does it need version 3?
my weew is currently installed in / home / weewx and the same path appears 
in the setup.cfg file.
I downloaded version 4.2 in the / home folder and here I stopped. Could you 
help me with the next steps?
Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6ba2e811-87dc-4dfa-a556-45d5210dea76n%40googlegroups.com.

Re: [weewx-user] Questions about weewx-loopdata

[geoffs...@gmail.com]

Awesome! This is sort of what I suspected that most use cases, NULL is a 
problem. I can just hard code the entire Davis loop which will work for my 
needs.

Thanks you,

Geoff

On Wednesday, November 25, 2020 at 6:45:44 AM UTC-8 jo...@johnkline.com 
wrote:

> In the general case, including keys in the loop packet for non-existent 
> data is not a good idea.  This would break existing code (e.g., JavaScript 
> code I use in my skins).
>
> You could easily fork the extension and add in what you need.  At line 
> 736, right before write_packet_to_file is called, simply check for the keys 
> you need to exist, and add them if they are not there. The following should 
> work.  Just replace the keys I’ve listed with the ones you need in the 
> packet.
>
> must_have_keys = [ 'current.outTemp', 'current.outHumidity' ]
> for must_have_key in must_have_keys:
> if must_have_key not in loopdata_pkt:
> loopdata_pkt[must_have_key] = None
>
> If you don’t want to hard code the keys, you’ll have a bigger task; but 
> you could just copy the code used to process the ‘fields’ entry in the 
> LoopData section of weewx.conf.
>
> Cheers,
> John
>
> On Nov 24, 2020, at 8:54 PM, geoffs...@gmail.com  
> wrote:
>
> Hi John,
>
>
> This is a great extension. I'm wondering if there is a way to be able to 
> include sending data that is null  or none for a particular key? I'm using 
> a davis vantage pro2, weewx 4.2. I'd like to use this to make a JSON output 
> that can be ingested into a home automation system. So far it works great 
> as long as the data is available to be sent, but I have not figured out how 
> to send a key with a Null or none value. It looks like a key with a null or 
> none value gets cleaved off the JSON output. If a battery dies on a sensor 
> and it just disappears from the JSON output, that is much harder for the HA 
> system to handle than a null, none or zero value. 
>
> On Monday, November 16, 2020 at 2:57:13 PM UTC-8 jo...@johnkline.com 
> wrote:
>
>> A fix is released (v2.7.2).  There is no hurry to install the new 
>> release; but once you’ve installed it, you can remove the field I asked you 
>> to add to weewx.conf.
>>
>> On Nov 16, 2020, at 9:04 AM, Geni  wrote:
>>
>> Ok, works
>>
>>
>> Thank you
>>
>> jo...@johnkline.com schrieb am Montag, 16. November 2020 um 16:05:21 
>> UTC+1:
>>
>>> I can duplicate this problem and will issue a fix.
>>>
>>> In the meantime, you can add:
>>> rainyear.outTemp.max
>>> to the fields clause in the LoopData section of weewx.conf?
>>>
>>> That will stop this problem.  If you get similar errors for other 
>>> periods where you have no fields listed, you’ll have to temporarily add a 
>>> field for those periods also.
>>>
>>> I should have a fix shortly.  I don’t know that this is related to WeeWX 
>>> 4.2, not that that really matters. 
>>>
>>> On Nov 16, 2020, at 2:45 AM, Geni  wrote:
>>>
>>> 
>>>
>>>
>>> Hi john
>>> since weewx 4.2.0 the loop-data.txt is no longer generated?
>>> regards Geni
>>>
>>>
>>> -- 
>>> You received this message because you are 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/3f89791f-c06b-43d1-beac-0afa58df59d6n%40googlegroups.com
>>>  
>>> 
>>> .
>>> 
>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/0f6cb227-1cdd-4fbb-9cf9-6f4c59521262n%40googlegroups.com
>>  
>> 
>> .
>>
>> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/0611c189-0c9f-4ab6-b6be-4d797e80bb96n%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 

Re: [weewx-user] VantagePro 2 No longer connecting after S/W Update

[tomn...@frontier.com]

I think you might need one of 
these:  https://www.abelectronics.co.uk/p/51/serial-pi-plus
The RPi's don't have an RS232 port, which is what the weather station is 
expecting to be hooked to.
I use one of the linked items with no trouble, twice actually.

Chris

On Tuesday, November 24, 2020 at 8:00:35 PM UTC-7 gct3...@gmail.com wrote:

> Hi,
> Thanks for the quick reply!
> You must see the code and/or these log messages in your sleep, I didn't 
> see anything that even mentioned WRD.  I confirmed with minicom that I am 
> not getting a response when I send out a WRD.  
>
> I appreciate the work around, but before I use it I need to understand why 
> the WRD is not working otherwise I have no idea what else is going wrong 
> and my brain will start to itch.  
>
> FYI, the serial connection is three wires connected from the serial port 
> on the PI to the serial port on the VP2.  The cable ends do not appear to 
> have been moved but it is certainly not robust. I had to move my hardware 
> to perform the upgrade and if things were not shut down properly I suppose 
> I could have damaged something.  Not sure why the WRD was impacted put the 
> TEST, LAMP, VER, NVER commands were not impacted.  Of course different 
> parts of the underlying circuits could have been damaged.
>
> Again thanks very much.
>
> Cheers! 
>
>
>
> On Tuesday, November 24, 2020 at 5:32:11 PM UTC-7 tke...@gmail.com wrote:
>
>> You didn't say much about your direct serial connection to the console, 
>> but it is not properly emulating the Davis WRD command. This command 
>> returns the hardware type (VantageVue, VantagePro, etc.)
>>
>> If all else fails, you can hard set it in the driver. At line 494 (or 
>> thereabouts), change this
>>
>> self.hardware_type = None
>>
>>
>> to this
>>
>> self.hardware_type = 16
>>
>>
>> That may fix things, but there are likely to be other problems. You'll 
>> have to do this every time you upgrade. Or, get the serial connection fixed!
>>
>>
>>
>> On Tue, Nov 24, 2020 at 4:20 PM Chip Towner  wrote:
>>
>>> Hi,
>>> I have been using Weewx since 2014 on a RaspberryPi 2.  My weather 
>>> station is a VantagePro2 and the connection is a straight serial connection 
>>> (no data logger).  Weewx has worked well for this entire time.
>>>
>>> This year after a failed update (mirror sites no longer exist),  I 
>>> decided I would take a chance and upgrade to the latest version of the 
>>> Raspbian OS (Buster I beleive).  I backed up my Weewx data as directed 
>>> prior to the update.  Then I updated the OS and took the opportunity to 
>>> also update Weewx to the latest/greatest.
>>>
>>> Unfortunately Weewx is now unable to connect to the VP2.  
>>>
>>> Since I originally configured this connection in 2014 it is possible 
>>> (perhpas eve likely) that I have missed something or even damaged the VP2 
>>> (hope not).  
>>>
>>>- I have dug into the User Guide and believe I have things 
>>>configured properly.
>>>- I have used minicom and screen to confirm that my RPi can in fact 
>>>talk to the VP2.   
>>>- Used TEST and received the expected reply
>>>   - Used LAMP 1 and turned the display light on
>>>- I attempted to use wee_device to turn on the VP2 lamp. It did not 
>>>work. 
>>>   - I copied the results into the file weeDeviceLog.txt in case it 
>>>   might be helpful 
>>>- I edited the weewx.conf that was installed and did my best to 
>>>configure things as they were previously (attached is weewxCurrent.conf, 
>>> a 
>>>renamed version of this document with some passwords removed)
>>>   - I have updated the weewx.conf file to use software based record 
>>>   generation.
>>>   - The port settings appear to be correct - even when comparing to 
>>>   my previous weewx.conf file.
>>>
>>> I am attaching a portion of the tail of the syslog file. I stopped weewx 
>>> and then started it to show what happens. 
>>>
>>> Because it appears that I can communicate with the VP2 using minicom and 
>>> screen I am hoping this means my RPI & VP2 are healthy and that this is 
>>> some weewx configuration issue I have missed.
>>>
>>> Any help is appreciated!
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/e9bf7d61-7762-4853-b8be-4805299e7536n%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 

Re: [weewx-user] Re: Peet Bros with Davis wind vane

[Chris Thompstone]

sorry for the slow response, got dealing with other stuff.

The Peet Bros wind vane, looks fine from the ground.  However the wind 
direction is normally wrong.  But sometimes right (often when very windy), 
but then wrong later again etc etc.
The wind speed seems OK...  Although it does sound a bit rattlely.

So the peet bros wind vane is difficult to get in the UK and it hasn't been 
up for very long before it starting playing up.
So thought maybe I could change to a davis one and use that with the peet 
bros kit, however that sounds like it wont work.
Chris

On Friday, 20 November 2020 at 00:46:27 UTC daleea...@gmail.com wrote:

> Indeed, I may have jumped to a wrong conclusion, also.
>
>
> I should have clarified.  My response was based on getting a whole 
> sensor unit, windspeed and wind direction, replaced.
>
>
> If it is just a mechanical problem (broken  nose or fin) on the Peet 
> wind direction unit, then as Tom suggests a bit of work with epoxy and 
> re-inforcement mesh works wonders.
>
>
> I have just finished fixing the nose of my Peet unit that arrived with 
> the nosepiece broken off and a little of the screw pointing through.  
> Very easy to do.
>
>
> I have made numerous repairs to the wind direction vane on the Texas 
> Weather Instruments sender because it is notoriously weak where the bolt 
> attaches the vane to the encoder.
>
>
> Please indicate what you are wanting to replace:  The whole unit with a 
> Davis, or just the VANE that turns the cap with the magnet inside of it.
>
>
> Dale
>
>
>  (very sorry if I gave wrong advice)
>
>

-- 
You received this message because you are 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/e00652d6-1d0d-4240-a5a2-70d1cd03ecdcn%40googlegroups.com.

[weewx-user] upload issue with steelseriesgauges

[hobbyl...@gmail.com]

i have setting in steelseriesgauges in gauge.js uploading in 48 seconds, 
but data uploading every 5 minutes , like stantard pages of weewx.i have 
the 4.2.0 version of weewx. thank you.

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

Re: [weewx-user] VantagePro 2 No longer connecting after S/W Update

[Tom Keffer]

It's not quite that simple. The command is "WRD\x12\x4d". That is, it's the
characters WRD, followed by two bytes with values 0x12 and 0x4d.
Unfortunately, I don't know of any easy way to transmit special characters
using minicom. But, here's a little program that will do it:

import serial
import time

# open up the serial port. Your port may differ.
s = serial.Serial('/dev/ttyUSB0', 19200)
# Wake up the console
s.write(b"\n\n")
time.sleep(0.2)
# Query for the hardware type
s.write(b"WRD\x12\x4d\n")
# Wait a bit for the console to respond
time.sleep(0.2)
# Get the response
b = s.read(4)
print(b)

When I run this program on my machine, I get:
b'\n\r\x06\x10'

The \x06 is the  character.

The \x10 is the code for the type of Davis console. \x10 is a VantagePro2.
\x11 would be a VantageVue.

As for why this worked before, but not now, I don't know what version of
WeeWX you were running. It's possible very old versions did not query for
hardware type, but I really don't remember.

-tk



On Tue, Nov 24, 2020 at 7:00 PM Chip Towner  wrote:

> Hi,
> Thanks for the quick reply!
> You must see the code and/or these log messages in your sleep, I didn't
> see anything that even mentioned WRD.  I confirmed with minicom that I am
> not getting a response when I send out a WRD.
>
> I appreciate the work around, but before I use it I need to understand why
> the WRD is not working otherwise I have no idea what else is going wrong
> and my brain will start to itch.
>
> FYI, the serial connection is three wires connected from the serial port
> on the PI to the serial port on the VP2.  The cable ends do not appear to
> have been moved but it is certainly not robust. I had to move my hardware
> to perform the upgrade and if things were not shut down properly I suppose
> I could have damaged something.  Not sure why the WRD was impacted put the
> TEST, LAMP, VER, NVER commands were not impacted.  Of course different
> parts of the underlying circuits could have been damaged.
>
> Again thanks very much.
>
> Cheers!
>
>
>
> On Tuesday, November 24, 2020 at 5:32:11 PM UTC-7 tke...@gmail.com wrote:
>
>> You didn't say much about your direct serial connection to the console,
>> but it is not properly emulating the Davis WRD command. This command
>> returns the hardware type (VantageVue, VantagePro, etc.)
>>
>> If all else fails, you can hard set it in the driver. At line 494 (or
>> thereabouts), change this
>>
>> self.hardware_type = None
>>
>>
>> to this
>>
>> self.hardware_type = 16
>>
>>
>> That may fix things, but there are likely to be other problems. You'll
>> have to do this every time you upgrade. Or, get the serial connection fixed!
>>
>>
>>
>> On Tue, Nov 24, 2020 at 4:20 PM Chip Towner  wrote:
>>
>>> Hi,
>>> I have been using Weewx since 2014 on a RaspberryPi 2.  My weather
>>> station is a VantagePro2 and the connection is a straight serial connection
>>> (no data logger).  Weewx has worked well for this entire time.
>>>
>>> This year after a failed update (mirror sites no longer exist),  I
>>> decided I would take a chance and upgrade to the latest version of the
>>> Raspbian OS (Buster I beleive).  I backed up my Weewx data as directed
>>> prior to the update.  Then I updated the OS and took the opportunity to
>>> also update Weewx to the latest/greatest.
>>>
>>> Unfortunately Weewx is now unable to connect to the VP2.
>>>
>>> Since I originally configured this connection in 2014 it is possible
>>> (perhpas eve likely) that I have missed something or even damaged the VP2
>>> (hope not).
>>>
>>>- I have dug into the User Guide and believe I have things
>>>configured properly.
>>>- I have used minicom and screen to confirm that my RPi can in fact
>>>talk to the VP2.
>>>- Used TEST and received the expected reply
>>>   - Used LAMP 1 and turned the display light on
>>>- I attempted to use wee_device to turn on the VP2 lamp. It did not
>>>work.
>>>   - I copied the results into the file weeDeviceLog.txt in case it
>>>   might be helpful
>>>- I edited the weewx.conf that was installed and did my best to
>>>configure things as they were previously (attached is weewxCurrent.conf, 
>>> a
>>>renamed version of this document with some passwords removed)
>>>   - I have updated the weewx.conf file to use software based record
>>>   generation.
>>>   - The port settings appear to be correct - even when comparing to
>>>   my previous weewx.conf file.
>>>
>>> I am attaching a portion of the tail of the syslog file. I stopped weewx
>>> and then started it to show what happens.
>>>
>>> Because it appears that I can communicate with the VP2 using minicom and
>>> screen I am hoping this means my RPI & VP2 are healthy and that this is
>>> some weewx configuration issue I have missed.
>>>
>>> Any help is appreciated!
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and